Juniper Networks, Inc.

Cisco Technology, Inc.

Siva Gaggara

Nitin Kumar

Kireeti Kompella

Kaushik Ghosh

Steven Lin

Nikhil Gopinath Shetty

Prashanth Venugopal

Sarat Kamisetty

Ravindra Nandalal Rathi

Sanjay Thyamagundalu

Fritz Budiyanto

Jialin Song

Mahesh Shirshyad

A first network device receives a first data packet from a registry device. The first data packet includes a destination of a first host coupled to the first network device and reachability information for a second host coupled to a second network device. The first network device stores the reachability information for the second host, which indicates that the second host is coupled to the second network device. The first network device transmits the first data packet without the reachability information to the first host. Using the reachability information for the second host, a tunnel is created from the first network device to the second network device.

Scalable dynamic overlay tunnel management

An example method for to inter-pod traffic redirection and handling in a multi-pod network environment is provided and includes receiving a packet with an overlay header outgoing from a first pod, identifying the packet as redirected based on a source address in the overlay header indicating a second pod and a destination address in the overlay header indicating a third pod, the first pod being distinct from the second pod and the third pod, setting a redirection bit in the overlay header tagging the packet as redirected, and transmitting the packet to the third pod.

Inter-pod traffic redirection and handling in a multi-pod network environment

An example method for to multicast traffic distribution in a multi-pod network environment is provided and includes provisioning a block of multicast group addresses for broadcast, unknown unicast and multicast (BUM) traffic distribution between pods in the multi-pod network, calculating a hash corresponding to a bridge domain (BD) extending across a plurality of pods in the multi-pod network, the hash being identically calculated at each one of the plurality of pod, indexing with the hash into the block of multicast group addresses designated for inter-pod BUM traffic to derive a global multicast group identical for the broadcast domain across the plurality of pods, and associating a local multicast group at the translator with the derived global multicast group.

Multicast traffic distribution in a multi-pod network environment

A route for a data unit through a network may be defined based on a number of next hops. Exemplary embodiments described herein may implement a router forwarding table as a chained list of references to next hops. In one implementation, a device includes a forwarding table that includes: a first table configured to store, for each of a plurality of routes for data units in a network, a chain of links to next hops for the routes; and a second table configured to store the next hops. The device also includes a forwarding engine configured to assemble the next hops for the data units based on using the chain of links in the first table to retrieve the next hops in the second table and to forward the data units in the network based on the assembled next hops.

Next hop chaining for forwarding data in a network switching device

A method is provided for handling member link state changes in an aggregate interface. An aggregate interface may be established to include a number of member links. A mask may be associated with the aggregate interface, where the mask identifies a current state of each member link in the aggregate interface. The mask is retrieved and used to identify active links in the aggregate interface when packets are received for forwarding on the aggregate interface.

Member link status change handling for aggregate interfaces

Growing community of inventors

Sunnyvale, CA, United States of America

Siva Gaggara