Cisco Technology, Inc.

Lukas Krattiger

Shyam N Kapadia

Samir D Thoria

Jason David Notari

Ali Sajassi

Liqin Dong

Mankamana Prasad Mishra

Uffaz Nathaniel

Neeraj Malhotra

Manoj Kumar Pandey

Patnala Debashis Rao

Manish Chandra Agrawal

Rajesh Sharma

Sathish Srinivasan

Vrishab Sikand

Aakruthi Ramkumar Gopisetty

Nitin Kumar

Rajagopalan Janakiraman

Massimiliano Ardica

Suresh Pasupula

Kesavan Thiruvenkatasamy

Aparna Pattekar

Richard Lam

Manju Ramesh

Christophe Paggen

Huyen Trung Duong

Ijsbrand Wijnands

Samar Sharma

Yibin Yang

Lifen Tian

Munish Mehta

Satya Ranjan Mohanty

Vrishabha Sikand

Mohammed Javed Asghar

Deepak Kumar

Xinggang Zhou

Di Jin

Rohit Mendiratta

Subhav Mital

Siu-Man Leung

Sundeep Kumar Singh

Brian Christopher Farnham

Wing Hon Yeung

Shankar Gopalkrishnan

Indrajanti Pallikala

This disclosure describes techniques for enabling interoperability between asymmetric and symmetric Integrated Routing and Bridging (IRB) modes. An interfacing component may be configured to receive a first route advertisement from a first edge node in a Layer-2 (L2) fabric. The first route advertisement may correspond to an asymmetric format route, for instance. The interfacing component may be further configured to receive a second route advertisement from a second edge node in a L2/Layer-3 (L3) fabric. The second edge node may be configured for symmetric integrated routing and bridging (IRB). The interfacing component may be configured to re-originate the first route and the second route such that the interfacing component is included as a hop in the resultant routes between the L2 fabric and the L2/L3 fabric.

Multiple network interfacing

In an example method, a head node connected to a source device transmits a multicast data flow from the source device to receiving devices connected to tail nodes using Default MDT. The example method further includes determining that requirements have been met to begin transmitting the multicast data flow using Data MDT. The method may further include determining whether the tail nodes are able to receive the multicast data flow using Data MDT. In response to determining that all the tail nodes are able to receive the multicast data flow using Data MDT, switch to transmitting the multicast data flow to the tail nodes using Data MDT. In response to determining that at least one of the tail nodes is unable to receive the multicast data flow using the Data MDT, continue transmitting the multicast data flow using Data MDT.

Constraint-based underlay tree allocation for data centers

In one embodiment, a device may receive a multicast path trace request for a multicast tree, wherein the device is a mid-node in the multicast tree. The device may perform, based on the device being a mid-node in the multicast tree, an upstream trace of network topology of the multicast tree from the device to a head-node of the multicast tree and a downstream trace of network topology of the multicast tree from the device to at least one tail-node. The device may generate an end-to-end visible topology of the multicast tree based on the upstream trace and the downstream trace. The device may provide the end-to-end visible topology of the multicast tree to an observability manager.

Multicast path traces

Techniques for using more-specific routing to perform scalable Layer-2 (L2) stretching of subnets across hybrid-cloud environments. Routing tables in a public cloud may allow for routes that are more specific than the default local route, and the more-specific routes may be used to send all traffic to a dedicated, cloud router. The more-specific routes are set up for a VPC where a subnet resides such that the more specific-routes cover at least a portion of subnet range. The next hop for the more-specific routes point to the cloud router which is capable of doing host routing and segmentation extension. Thus, traffic originating from endpoints in a VPC is routed to the cloud router, and the cloud router determines whether the traffic is to be re-routed back to a destination endpoint in the VPC (or another cloud location), or sent to a destination endpoint residing in the on-premises site.

Specifying routes to enable Layer-2 mobility in hybrid-cloud environments

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.

Synchronizing dynamic host configuration protocol snoop information

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.

Multi-fabric deployment and management platform

Specifying routes to enable layer-2 mobility in hybrid-cloud environments

Disclosed are systems, apparatuses, methods, and computer-readable media for providing interoperable heterogenous networks. A method comprises configuring a logical network with a first network and a second network; receiving a request message from a source device by the first border device in the first network, wherein the request message includes a related to a media access control (MAC) address associated with a destination device in the second network; sending a proxy message to the second border device based on the request message, the proxy message having a source address that identifies an external IP address associated with the first border device; receiving a response message including the MAC address of the destination device, wherein the response message is addressed to the external address of the first border device; and sending a border gateway protocol (BGP) update including the MAC address of the destination device.

Seamless coexistence of heterogenous networks

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.

Monitoring interface configurations for network devices in fabrics

A method is performed at a provider edge node configured to communicate with remote provider edge nodes over an Ethernet virtual private network. The method includes receiving, from the remote provider edge nodes, route advertisements for a common subnet hosted on the remote provider edge nodes. The route advertisements include distinct remote route distinguishers, a common IP prefix for the common subnet, and remote paths for the common subnet. The method further includes determining whether there are at least a predetermined number of the remote paths preferred over a local path for the common subnet hosted on the provider edge node based on the remote route distinguishers and a local route distinguisher for the local path. The method includes, when there are at least the predetermined number of the remote paths preferred over the local path, suppressing sending of a route advertisement for the local path for the common subnet.

Integrated routing and bridging route reduction in ethernet virtual private network

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.

Interoperability between symmetric and asymmetric EVPN IRB modes

The present technology provides a system, method and computer-readable medium for configuration pattern recognition and inference, directed to a device with an existing configuration, through an extensible policy framework. The policy framework uses a mixture of python template logic and CLI micro-templates as a mask to infer the intent behind an existing device configuration in a bottom-up learning inference process. Unique values for device/network identifiers and addresses as well as other resources are extracted and accounted for. The consistency of devices within the fabric is checked based on the specific policies built into the extensible framework definition. Any inconsistencies found are flagged for user correction or automatically remedied by a network controller. This dynamic configuration pattern recognition ability allows a fabric to grow without being destroyed and re-created, thus new devices with existing configurations may be added and automatically configured to grow a Brownfield fabric.

Learning by inference from previous deployments

Growing community of inventors

Pleasanton, CA, United States of America

Lukas Krattiger