Abstract: Virtual network controllers are described that automatically generate policies and configuration data for routing traffic through physical network function (PNF) service chains in a multi-tenant data center. An example network controller includes a memory and processing circuitry configured to: automatically generate, for one or more integrated routing and bridging (IRB) units of corresponding virtual network forwarding tables of a switch of a switch fabric of a data center network, configuration information that, when deployed, causes the IRB units to direct data traffic conforming to multiple communication protocols and flowing over a plurality of virtual networks between a first set of server devices and a second set of server devices positioned outside of the switch fabric (i) toward a service device logically positioned outside of the switch fabric and coupled to the switch, and (ii) back from the service device into the switch fabric via the switch.

Abstract: Techniques are described in which a centralized controller constructs a service chain between a bare metal server (BMS) and a virtual execution element (e.g., virtual machine or container), or in some instances a remote BMS, across a plurality of networks. In some examples, the controller may construct a service chain between a BMS and a virtual execution element or remote BMS using Ethernet Virtual Private Network (EVPN)-Virtual Extensible Local Area Network (VXLAN) and Internet Protocol Virtual Private Networks (IP VPNs) such as BGP/Multiprotocol Label Switching (BGP/MPLS) IP VPNs.

Abstract: Virtual network controllers are described that automatically generate policies and configuration data for routing traffic through physical network function (PNF) service chains in a multi-tenant data center. An example network controller includes a memory and processing circuitry configured to: automatically generate, for one or more integrated routing and bridging (IRB) units of corresponding virtual network forwarding tables of a switch of a switch fabric of a data center network, configuration information that, when deployed, causes the IRB units to direct data traffic conforming to multiple communication protocols and flowing over a plurality of virtual networks between a first set of server devices and a second set of server devices positioned outside of the switch fabric (i) toward a service device logically positioned outside of the switch fabric and coupled to the switch, and (ii) back from the service device into the switch fabric via the switch.

Abstract: Techniques are described in which a centralized controller constructs a service chain between a bare metal server (BMS) and a virtual execution element (e.g., virtual machine or container), or in some instances a remote BMS, across a plurality of networks. In some examples, the controller may construct a service chain between a BMS and a virtual execution element or remote BMS using Ethernet Virtual Private Network (EVPN)-Virtual Extensible Local Area Network (VXLAN) and Internet Protocol Virtual Private Networks (IP VPNs) such as BGP/Multiprotocol Label Switching (BGP/MPLS) IP VPNs.

Abstract: Techniques are described in which a centralized controller constructs a service chain between a bare metal server (BMS) and a virtual execution element (e.g., virtual machine or container), or in some instances a remote BMS, across a plurality of networks. In some examples, the controller may construct a service chain between a BMS and a virtual execution element or remote BMS using Ethernet Virtual Private Network (EVPN)-Virtual Extensible Local Area Network (VXLAN) and Internet Protocol Virtual Private Networks (IP VPNs) such as BGP/Multiprotocol Label Switching (BGP/MPLS) IP VPNs.

Abstract: An example data center system includes server devices hosting data of a first tenant and a second tenant of the data center, network devices of an interconnected topology coupling the server devices including respective service virtual routing and forwarding (VRF) tables, and one or more service devices that communicatively couple the network devices, wherein the service devices include respective service VRF tables for the first set of server devices and the second set of server devices, and wherein the service devices apply services to network traffic flowing between the first set of server devices and the second set of server devices using the first service VRF table and the second service VRF table.

Abstract: In general, techniques are described for defining and executing device-independent commands on a network having a plurality of network devices. In some examples, a controller includes a graphical user interface. The controller displays, via the graphical user interface, network devices that support a device-independent command selected from one or more device-independent commands, wherein each device-independent command performs one or more operations on supported network devices. The controller receives, via the graphical user interface, user input selecting two or more of the displayed network devices and performs the one or more operations of the selected device-independent command on the selected network devices. In some examples, performing includes executing tasks associated with each network device, wherein the tasks, when executed, perform the one or more operations on each respective network device.

Abstract: Techniques are described in which a centralized controller constructs a service chain between a bare metal server (BMS) and a virtual execution element (e.g., virtual machine or container), or in some instances a remote BMS, across a plurality of networks. In some examples, the controller may construct a service chain between a BMS and a virtual execution element or remote BMS using Ethernet Virtual Private Network (EVPN)-Virtual Extensible Local Area Network (VXLAN) and Internet Protocol Virtual Private Networks (IP VPNs) such as BGP/Multiprotocol Label Switching (BGP/MPLS) IP VPNs.

Abstract: In general, techniques are described for defining and executing device-independent commands on a network having a plurality of network devices. In some examples, a controller includes a graphical user interface. The controller displays, via the graphical user interface, network devices that support a device-independent command selected from one or more device-independent commands, wherein each device-independent command performs one or more operations on supported network devices. The controller receives, via the graphical user interface, user input selecting two or more of the displayed network devices and performs the one or more operations of the selected device-independent command on the selected network devices. In some examples, performing includes executing tasks associated with each network device, wherein the tasks, when executed, perform the one or more operations on each respective network device.

Abstract: Virtual network controllers are described that automatically generate policies and configuration data for routing traffic through physical network function (PNF) service chains in a multi-tenant data center. An example network controller includes a memory and processing circuitry configured to: automatically generate, for one or more integrated routing and bridging (IRB) units of corresponding virtual network forwarding tables of a switch of a switch fabric of a data center network, configuration information that, when deployed, causes the IRB units to direct data traffic conforming to multiple communication protocols and flowing over a plurality of virtual networks between a first set of server devices and a second set of server devices positioned outside of the switch fabric (i) toward a service device logically positioned outside of the switch fabric and coupled to the switch, and (ii) back from the service device into the switch fabric via the switch.

Abstract: In general, techniques are described for managing, with a network controller for a computer network, the configuration of network devices within the computer network using one or more message buses. In some examples, a controller includes processing circuitry coupled to memory. The processing circuitry is configured to generate data for implementing a configuration change for a network device and store, to a configuration database, the data for implementing the configuration change for the network device. The processing circuitry is further configured to add, to a message queue of a message bus executed by one or more or more computing devices separate from the controller, an indication of the configuration change for the network device to cause the network device to obtain, from the configuration database, the data for implementing the configuration change for the network device.

Abstract: Techniques are described in which a centralized controller constructs a service chain between a bare metal server (BMS) and a virtual execution element (e.g., virtual machine or container), or in some instances a remote BMS, across a plurality of networks. In some examples, the controller may construct a service chain between a BMS and a virtual execution element or remote BMS using Ethernet Virtual Private Network (EVPN)—Virtual Extensible Local Area Network (VXLAN) and Internet Protocol Virtual Private Networks (IP VPNs) such as BGP/Multiprotocol Label Switching (BGP/MPLS) IP VPNs.

Abstract: In general, techniques are described for defining and executing device-independent commands on a network having a plurality of network devices. In some examples, a controller includes a graphical user interface. The controller displays, via the graphical user interface, network devices that support a device-independent command selected from one or more device-independent commands, wherein each device-independent command performs one or more operations on supported network devices. The controller receives, via the graphical user interface, user input selecting two or more of the displayed network devices and performs the one or more operations of the selected device-independent command on the selected network devices. In some examples, performing includes executing tasks associated with each network device, wherein the tasks, when executed, perform the one or more operations on each respective network device.

Abstract: An example data center system includes server devices hosting data of a first tenant and a second tenant of the data center, network devices of an interconnected topology coupling the server devices including respective service virtual routing and forwarding (VRF) tables, and one or more service devices that communicatively couple the network devices, wherein the service devices include respective service VRF tables for the first set of server devices and the second set of server devices, and wherein the service devices apply services to network traffic flowing between the first set of server devices and the second set of server devices using the first service VRF table and the second service VRF table.

Abstract: Techniques are disclosed for configuring multiple network devices implementing different protocols or techniques. For example, these techniques allow network devices configured with different protocols to co-exist within the same network, or for the network to seamlessly evolve from one protocol to the other. Techniques described herein provide for an SDN controller that may bridge a network system implementing different protocols, e.g., Open vSwitch Database (OVSDB) and Ethernet Virtual Private Network (EVPN), by translating high-level configuration data (e.g., desired state of the network at a high level of abstraction) that are protocol agnostic to low-level configuration data (e.g., desired state of the network at a low level of abstraction) that are protocol specific. That is, SDN controller may provide management, control, and analytics functions of a virtualized network configured to operate specifically within an OVSDB environment and/or an EVPN environment.

Abstract: Techniques are described in which a centralized controller constructs a service chain between a bare metal server (BMS) and a virtual execution element (e.g., virtual machine or container), or in some instances a remote BMS, across a plurality of networks. In some examples, the controller may construct a service chain between a BMS and a virtual execution element or remote BMS using Ethernet Virtual Private Network (EVPN)—Virtual Extensible Local Area Network (VXLAN) and Internet Protocol Virtual Private Networks (IP VPNs) such as BGP/Multiprotocol Label Switching (BGP/MPLS) IP VPNs.

Abstract: Techniques are disclosed for deploying software upgrades to a mixed network of In-Service Software Upgrade (ISSU)-capable and ISSU-incapable network devices without interrupting network traffic serviced by the mixed network. In one example, a centralized controller for a network determines that first network devices of a plurality of network devices for the network are In-Service Software Upgrade (ISSU)-capable and second network devices of the plurality of network devices are not ISSU-capable. The centralized controller transmits messages instructing the first network devices to perform an ISSU operation. Further, the centralized controller transmits messages instructing each network device of the second network devices to transmit a message to peer network devices of the network device, the message indicating that the network device is not ISSU-capable.

Abstract: Techniques are disclosed for extending scalable policy management to supporting network devices. A network device comprising a memory and a processor may perform various aspects of the techniques. The memory may be configured to store a policy. The processor may be configured to obtain the policy to be enforced by a supporting network device coupled to a server, and identify a port of the supporting network device to which the server is coupled via the switch fabric. The policy controller may also identify a workload executed by the server to which the policy is associated, and convert the policy into configuration data supported by the network device. The policy controller may further configure, based on the configuration data, the network device to enforce the policy with respect to network traffic received via the identified port.

Abstract: Techniques are disclosed for providing an inter-autonomous system (inter-AS) service between virtualized entities of one autonomous system with external entities of a different autonomous system. For example, a controller (e.g., software defined networking (SDN) controller) may provide multi-hop exterior Border Gateway Protocol (eBGP) redistribution of virtual private networking (VPN) labels between endpoints of different autonomous systems, otherwise referred to as “inter-AS option C.” As described in this disclosure, the SDN controller may facilitate the exchange of appropriate routing labels between endpoints of different autonomous systems to enable forwarding of traffic between the different autonomous systems.

Abstract: Techniques are disclosed for configuring multiple network devices implementing different protocols or techniques. For example, these techniques allow network devices configured with different protocols to co-exist within the same network, or for the network to seamlessly evolve from one protocol to the other. Techniques described herein provide for an SDN controller that may bridge a network system implementing different protocols, e.g., Open vSwitch Database (OVSDB) and Ethernet Virtual Private Network (EVPN), by translating high-level configuration data (e.g., desired state of the network at a high level of abstraction) that are protocol agnostic to low-level configuration data (e.g., desired state of the network at a low level of abstraction) that are protocol specific. That is, SDN controller may provide management, control, and analytics functions of a virtualized network configured to operate specifically within an OVSDB environment and/or an EVPN environment.