Abstract: Measures, including systems, methods and non-transitory computer-readable storage mediums, for use in operating a data center network, the data center network including an interconnect fabric including a plurality of spine switches, a plurality of top-of-rack switches and a plurality of compute servers. The interconnect fabric is configured to implement a plurality of independent spine switch planes. Each spine switch plane in the plurality of independent spine switch planes includes a different spine switch in the plurality of spine switches. The configuring includes configuring Layer 2 networking within each independent spine switch plane in the plurality of independent spine switch planes.

Abstract: Certain examples described herein provide a system and method for validating a routing function for a network device. In one example, a network device has a run-time policy engine, wherein the run-time policy engine implements a routing configuration file and the routing configuration file defines a routing function for network traffic. A file editor is also provided that loads the routing configuration file. The file editor has an editor policy engine that duplicates a functionality of the run-time policy engine. In one example, the routing configuration file has at least one validation portion that has one or more route statements with definitions indicative of expected routing function behavior. The file editor parses the routing configuration file by implementing the routing configuration file using the editor policy engine.

Abstract: Described herein is an inference-based approach to process network route definitions, e.g. routes received from other network devices according to a defined routing protocol. In examples, at least one proposition is defined that relates to at least one property of the route. Probabilities are also defined in association with the proposition. A first probability may be indicative of a randomly-selected network route and a second probability may be indicative of randomly-selected network route that is suitable for use in routing network traffic. In certain examples, a probability that a given route is malicious or erroneous may be computed. Probabilities may be calculated by processing historical routing data, such as network route definitions that are labelled as suitable for routing traffic. Probabilities may also be evaluated cumulatively over multiple routing policy elements. Final actions may be made by applying a configurable range or threshold to an output confidence value.

Abstract: Measures, including systems, methods and non-transitory computer-readable storage mediums, for use in operating a data center network, the data center network including an interconnect fabric including a plurality of spine switches, a plurality of top-of-rack switches and a plurality of compute servers. The interconnect fabric is configured to implement a plurality of independent spine switch planes. Each spine switch plane in the plurality of independent spine switch planes includes a different spine switch in the plurality of spine switches. The configuring includes configuring Layer 2 networking within each independent spine switch plane in the plurality of independent spine switch planes.

Abstract: Described herein is an inference-based approach to process network route definitions, e.g. routes received from other network devices according to a defined routing protocol. In examples, at least one proposition is defined that relates to at least one property of the route. Probabilities are also defined in association with the proposition. A first probability may be indicative of a randomly-selected network route and a second probability may be indicative of randomly-selected network route that is suitable for use in routing network traffic. In certain examples, a probability that a given route is malicious or erroneous may be computed. Probabilities may be calculated by processing historical routing data, such as network route definitions that are labelled as suitable for routing traffic. Probabilities may also be evaluated cumulatively over multiple routing policy elements. Final actions may be made by applying a configurable range or threshold to an output confidence value.

Abstract: Certain examples described herein provide a system and method for validating a routing function for a network device. In one example, a network device has a run-time policy engine, wherein the run-time policy engine implements a routing configuration file and the routing configuration file defines a routing function for network traffic. A file editor is also provided that loads the routing configuration file. The file editor has an editor policy engine that duplicates a functionality of the run-time policy engine. In one example, the routing configuration file has at least one validation portion that has one or more route statements with definitions indicative of expected routing function behavior. The file editor parses the routing configuration file by implementing the routing configuration file using the editor policy engine.