Abstract:
Techniques are presented to signal where a virtual machine (host) has moved in a data center networking environment. These techniques use Multiprotocol Border Gateway Protocol (MP BGP) alone, and are particularly useful in a multi-vendor environment using existing standards. Reverse Address Resolution Protocol (RARP) broadcast is not needed, therefore, no L2 extension is needed across a data center interface for tenants that do not require L2 extension for purposes other than a host move. This scheme works for both inter- and intra-fabric moves.
Abstract:
A method includes generating a visual representation of one or more multicast data trees over a service provider network, each multicast data tree exchanging data between two or more of a plurality of nodes of an entity operating over the service provider network; determining a respective network bandwidth usage over each of the one or more multicast data trees and a network bandwidth waste based on current bandwidth usage of existing data tunnels of one or more multicast data trees and replication distances associated with the plurality of nodes; modifying the one or more multicast data trees based on at least the respective network bandwidth usage over each of the one or more multicast data trees to yield a modification; generating a traffic routing policy to implement the modification; and transmitting a notification to a subset of the plurality of nodes affected by the traffic routing policy.
Abstract:
Techniques for generating and utilizing overlay-based Border Gateway Protocol (BGP) Operations, Administration, and Maintenance (OAM) packets to detect issues with an underlay network. The techniques may include receiving, from a BGP peer device via a control plane path, an OAM probe indicating a forwarding path to be used for sending the traffic to a destination associated with a prefix. The techniques may also include determining, based at least in part on the OAM probe, that a next-hop device is incapable of being utilized to forward the traffic to the destination, the next-hop device determined based on an origination of the prefix. The techniques may further include performing a policy-based action based at least in part on determining that the next-hop device is incapable of being utilized to forward the traffic to the destination.
Abstract:
Techniques for determining that a configuration change in configurations for a network device has occurred to result in changed configurations for the network device. The techniques include creating a policy for the network device by a network controller that manages one or more network devices. The network controller may obtain data from the network device, and update the network device policy based on the obtained data. In some examples, the network controller may compare the network device configurations state with the network controller intent to determine if an Out-of-Band (OOB) configuration change has occurred in the configuration of the network device. Finally, the controller may synchronize the network device to the controller based on the updated policy.
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. Network deviations from the intended fabric policies are addressed by the provision of one or more configuration lines to be deployed onto or removed from the connected network devices to bring the network state in agreement with the set of expected configuration.
Abstract:
Systems and techniques are provided for synchronizing DHCP snoop information. In some examples, a method can include, performing, by a first PE device from a plurality of PE devices, DHCP snooping of a first plurality of DHCP messages between a DHCP client and a DHCP server, wherein the plurality of PE devices is part of an ethernet segment for multihoming the DHCP client. In some aspects, the method includes determining, based on snooping the first plurality of DHCP messages, an association between an IP address corresponding to the DHCP client and a MAC address corresponding to the DHCP client. In some examples, the method includes sending, by the first PE device to at least one other PE device from the plurality of PE devices, a first route advertisement that includes the association between the IP address corresponding to the DHCP client and the MAC address corresponding to the DHCP client.
Abstract:
Techniques for utilizing a Software-Defined-Networking (SDN) controller and/or a Data Center Network Manager (DCNM) and network border gateway switches associated with a multi-site cloud computing network to provide reachability data indicating physical links between the border gateways disposed in different sites of the multi-site network to establish secure connection tunnels utilizing the physical links and unique encryption keys. The SDN controller and/or DCNM may be configured to generate a physical underlay model representing the physical underlay, or network transport capabilities, and/or a logical overlay model representing a logical overlay, or overlay control-plane, of the multi-site network. The SDN controller may also generate an encryption key model representing the associations between the encryption keys and the physical links between the associated network border gateway switches. The SDN controller may utilize the models to determine route paths for transmitting network traffic spanning over different sites of the multi-site network at line speed.
Abstract:
A system and method are disclosed for enabling interoperability between asymmetric and symmetric Integrated Routing and Bridging (IRB) modes. A system is configured to receive a route advertisement, examine the label fields of the route advertisement, and determine whether Layer 2 or Layer 3 information is conveyed. The system is further configured to build a route advertisement to advertise to a second device based on whether Layer 2 or Layer 3 information is conveyed in the first route advertisement.
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 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.