Abstract: Techniques for a configuration change service to transition a network controller into a frozen state, causing network users submitting configuration changes associated with the network to refrain from deploying the configuration changes for a period of time are disclosed. A first user configured as a stager role may submit data representing a proposed change to the configuration change service, where the proposed change may be stored in association with a list of proposed changes. A second user configured as an approver role may submit data representing an approval or disapproval of the proposed changes to the configuration change service, where a modified list of proposed changes may be generated. A third user configured as an administrator role may submit data configured to transition the controller to an unfrozen state and/or deploy the changes included in the list of proposed changes to the network controller, subsequent to the period of time.

Abstract: A method is provided in one example embodiment and includes creating a segment organization, which includes a configuration profile. The method also includes attaching the configuration profile to a server in the segment organization. The method further includes sending the attached configuration profile to a database in a physical network.

Abstract: In one embodiment, a device obtains temperature and utilization measurements for a set of network interface transceivers in a network. The device computes, for each of the transceivers, a correlation coefficient between its temperature and utilization measurements. The device applies a k-nearest neighbor classifier to the correlation coefficients, to predict a correlation coefficient. The device uses the predicted correlation coefficient to determine an impact of temperature on utilization of a particular network interface transceiver. The device initiates a mitigation action, when the determined impact of temperature on the utilization of the particular network interface transceiver exceeds a predefined threshold.

Abstract: A network device is configured to establish a messaging bus with a container networking plug-in, which is associated with a container virtual network. The network device is also configured to obtain, via the messaging bus, networking information for one or more containers hosted at the at least one container-hosting computing device. Based on the networking information, the network device provides visibility of one or more containers below the network device.

Abstract: The disclosed technology relates to a load balancing system. A load balancing system is configured to receive health monitoring metrics, at a controller, from a plurality of leaf switches. The load balancing system is further configured to determine, based on the health monitoring metrics, that a server has failed and modify a load balancing configuration for the network fabric. The load balancing system is further configured to transmit the load balancing configuration to each leaf switch in the network fabric and update the tables in each leaf switch to reflect an available server.

Abstract: The present technology provides a framework for user-guided end-to-end automation of network deployment and management, that enables a user to guide the automation process for any kind of network deployment from the ground up, as well as offering network management, visibility, and compliance verification. The disclosed technology accomplishes this by creating a stateful and interactive virtual representation of a fabric using a customizable underlay fabric template instantiated with user-provided parameter values and network topology data computed from one or more connected network devices. A set of expected configurations corresponding to the user-specified underlay and overly fabric policies is then generated for deployment onto the connected network devices.

Abstract: A method is provided in one example embodiment and includes receiving at a controller an Address Resolution Protocol (“ARP”) packet from a source VXLAN Tunnel End Point (“VTEP”) serving a source host and identifying a destination, the source VTEP having assigned thereto a Virtual Network Identifier (“VNI”) identifying a VXLAN network to which the source VTEP and a plurality of other VTEPs belong, the ARP packet being received by the controller via a control plane; determining whether the received ARP packet is a request message; and, if the received ARP packet is a request message, determining whether address information for the identified destination is stored in a cache of the controller.

Abstract: A first network device advertises routes of locally connected routes/subnetworks based on the connectivity of the host with respect to peer network devices. The first network device establishes a virtual port channel associated with a virtual network address. The virtual port channel includes the first network device associated with a first network address and a second network device associated with a second network address. The first network device detects that a host is connected to the first network device and determines a next hop address to associate with the host. The next hop address is determined based on whether the host is also connected to the second network device of the virtual port channel. The first network device generates a route advertisement associating the next hop address with the host.

Abstract: Techniques for virtual workload deployment based on computing resource hardware load and associated network hardware load. For each of a plurality of computing resources within one or more data centers onto which a virtual workload can be deployed, a computing resource hardware load of the respective computing resource is determined. Network topology information is maintained for at least one network fabric of the one or more data centers, and an associated network hardware load of a network device communicatively connected to the respective computing resource is determined. Embodiments automatically select one or more computing resources. The virtual workload is deployed onto the automatically selected one or more computing resources.

Abstract: A first network device advertises routes of locally connected routes/subnetworks based on the connectivity of the host with respect to peer network devices. The first network device establishes a virtual port channel associated with a virtual network address. The virtual port channel includes the first network device associated with a first network address and a second network device associated with a second network address. The first network device detects that a host is connected to the first network device and determines a next hop address to associate with the host. The next hop address is determined based on whether the host is also connected to the second network device of the virtual port channel. The first network device generates a route advertisement associating the next hop address with the host.

Abstract: A first network node of a computer network discovers a host route by leveraging a temporary host route on the control plane of the computer network. The first network node receives, from a source host, a request for a host route associated with a destination host. The first network node determines that it has not previously stored the host route associated with the destination host, and generates a temporary host route associated with the destination host. The first network node propagates the temporary host route across the control plane of the computer network, causing each respective network node to discover if the destination host is connected to the respective network node.

Abstract: A network controller for a network implementing a virtual network overlay determines a network gateway via which a service appliance accesses the network. The network controller determines a network gateway via which an application server accesses the network. First policy data is distributed to the network gateway via which the service appliance accesses the network. This first policy data indicates that the network gateway via which the service appliance accesses the network forwards return packets addressed to a client device sent from an application server to the service appliance. Second policy data is distributed to the network gateway via which the application server accesses the network. This second policy data indicates the network gateway via which the application server accesses the network is configured to forward return packets addressed to the client device to the network gateway via which the service appliance accesses the network.

Abstract: In one implementation, a method performed by a first node with interfaces configured as IP unnumbered interfaces sharing a single IP address and to communicate with a DHCP-associated second node includes: obtaining a first message that indicates a configuration status of a third node at a respective interface; obtaining a second message for the third node from the DHCP-associated second node that includes a temporary IP address for the third node and an indicator of a file server; obtaining a third message associated with the third node that includes the temporary IP address, the third message requests address information for the file server; and configuring the third node by establishing a connection between the third node and the file server to transfer at least one configuration file, where configuring the third node includes providing the temporary IP address to the DHCP-associated second node via BGP.

Abstract: A method is provided in one example embodiment and includes creating a segment organization, which includes a configuration profile. The method also includes attaching the configuration profile to a server in the segment organization. The method further includes sending the attached configuration profile to a database in a physical network.

Abstract: Systems and methods are provided for a multicast based solution to solving the slow-start problem that ensures both optimal (1-hop) and in-sequence delivery of packets to the destination. Packets are hardware switched thereby completely eliminating the slow software switching path.

Abstract: A system and a method are disclosed for enabling interoperability between data plane learning endpoints and control plane learning endpoints in an overlay network environment. An exemplary method for managing network traffic in the overlay network environment includes receiving network packets in an overlay network from data plane learning endpoints and control plane learning endpoints, wherein the overlay network extends Layer 2 network traffic over a Layer 3 network; operating in a data plane learning mode when a network packet is received from a data plane learning endpoint; and operating in a control plane learning mode when the network packet is received from a control plane learning endpoint. Where the overlay network includes more than one overlay segment, the method further includes operating as an anchor node for routing inter-overlay segment traffic to and from hosts that operate behind the data plane learning endpoints.

Abstract: The present disclosure provides systems, methods, and non-transitory computer-readable storage media for determining container to leaf switch connectivity information in a data center in a presence of blade switches and servers. In one aspect of the present disclosure, a method of determining container to leaf switch connectivity information of a data center utilizing at least one blade switch and at least one blade server, includes receiving, at a network controller, link connectivity information that includes south-bound neighboring information between the at least one blade switch of the data center and the at least one blade server of the data center; determining, at the network controller, the container to leaf switch connectivity information of the data center, based on the link connectivity information; and generating a visual representation of a topology of the data center based on the container to leaf switch connectivity information.

Abstract: A method is provided in one example embodiment and includes creating a segment organization, which includes a configuration profile. The method also includes attaching the configuration profile to a server in the segment organization. The method further includes sending the attached configuration profile to a database in a physical network.

Abstract: A Location/Identifier Separation Protocol (LISP) mapping server, including: a network interface for communicating with a LISP-enabled network; a mapping database; an extranet policy table; and a shared subnetwork mapping engine (SSME), including at least a hardware platform, configured to: receive a map request from a first endpoint serviced by a first xTR, the first endpoint on a first subnetwork, the map request for a second endpoint; determine that the second endpoint is not a member of the first subnetwork; query the extranet policy table to identify a second subnetwork that the first subnetwork subscribes to, and to determine that the second endpoint is a member of the second subnetwork; and provide to the first subnetwork a routing locator (RLOC) of an xTR servicing the second endpoint.

Abstract: In one embodiment a method includes receiving a first message including information regarding a first host connected to a first tunnel endpoint in a first network domain, the received information being encoded in accordance with a control plane protocol of the first network domain; translating the received first message in accordance with an API and/or a database schema of a second network domain; and transmitting the translated first message to the second network domain. The method further includes receiving a second message comprising information regarding a second host connected to a second tunnel endpoint in the second network domain, the received information being encoded in accordance with the API and/or the database schema of the second network domain; translating the second received message in accordance with the control plane protocol of the first network domain; and transmitting the translated second message to the first network domain.