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: 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 method includes determining, by a network controller, based on a high-level data model, vendor-agnostic device information for a first network device, translating the vendor-agnostic device information into vendor-specific device information, sending, to the first network device, first configuration information included in the vendor-specific device information to cause the first network device to switch into a maintenance mode and enable diversion of network traffic from the first network device to a second network device, responsive to verifying that the first network device has diverted the traffic, initiating maintenance procedures on the first network device while the first network device is in the maintenance mode, and sending, to the first network device, second configuration information included in the vendor-specific device information to cause the first network device to switch out of the maintenance mode and enable reversion of network traffic from the second device to the first network

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 method includes identifying, based on a received indication, at least a first network device that is to be placed in the maintenance mode, determining device information for the first network device, sending, to the first network device, first configuration information included in the device information to cause the first network device to switch into a maintenance mode and enable diversion of network traffic from the first network device to a second network device, responsive to verifying that the first network device has diverted the traffic, initiating maintenance procedures on the first network device while the first network device is in the maintenance mode, and sending, to the first network device, second configuration information included in the device information to cause the first network device to switch out of the maintenance mode and enable reversion of network traffic from the second device to the first network device.

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: An example method includes determining, by a network controller, based on a high-level data model, vendor-agnostic device information for a first network device, translating the vendor-agnostic device information into vendor-specific device information, sending, to the first network device, first configuration information included in the vendor-specific device information to cause the first network device to switch into a maintenance mode and enable diversion of network traffic from the first network device to a second network device, responsive to verifying that the first network device has diverted the traffic, initiating maintenance procedures on the first network device while the first network device is in the maintenance mode, and sending, to the first network device, second configuration information included in the vendor-specific device information to cause the first network device to switch out of the maintenance mode and enable reversion of network traffic from the second device to the first network

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: A services management system includes a services data retrieval module configured to communicate electronically with one or more data storage devices to obtain services data originating from one or more service management organizations or service providers based on services provided by the service providers to recipients of the services. The system includes a plurality of summary tables, each of the summary tables having a predetermined size less than a threshold size corresponding to a predetermined threshold time required to search data in a respective summary table among the plurality of summary tables. The system includes a user interface and a services data graphical user interface (GUI) generator to generate display data to display on the user interface graphics configured to be selected by a user to display analysis data corresponding to a summary table associated with the graphics selected by the user.