Cisco Technology, Inc.

Nicira, Inc.

Mehak Mahajan

Ayan Banerjee

Raghava Kodigenahalli Sivaramu

Srinivasan Ramabadran

Shyam N Kapadia

Samir D Thoria

Nataraj Bacthu

Vengada Prasad Govindan

Nataraj Batchu

Santa Dasu

Sandeep Subramaniam

Sanjay Basavanakattimatha

Abhayraj Kuldip Gidwani

Mudigonda Jwala Mallik

Teemu Koponen

Pankaj Thakkar

Ronghua Zhang

Martin Casado

Justin Pettit

Keith Eric Amidon

Ramana Mellacheruvu

Jesse Ernest Gross, Iv

Daniel J Wendlandt

Raja Rao Tadimeti

Swaminathan Narayanan

Madhava Rao Cheethirala

Ambrish Niranjan Mehta

Shiv Saini

Jesse E Gross Iv

Jesse Gross Iv

Ambrish Mehta

In accordance with one example embodiment, a system configured for programming a network layer multicast address entry in a routing table of an ingress line card module is disclosed. The network layer multicast address entry includes a network layer address associated with at least one egress line card. The system is further configured for programming a data link layer multicast routing address entry in a routing table of a fabric card module in which the data link layer multicast routing address entry corresponds to the network layer multicast address entry.

Multicast routing

Disclosed are systems, methods, and computer-readable storage media for synchronizing the secondary vPC node to the primary vPC node in a BFD protocol over a VxLAN channel with a remote node. In some embodiments of the present technology a primary vPC node can receive a packet from the remote node. The primary vPC node can then determine the packet includes either a MAC address corresponding to the primary vPC node or a secondary vPC node, and at least one inner packet identifier. Additionally, the primary networking switch can identify an access control list (ACL) entry from a set of ACL entries based on the at least one inner packet identifier. Subsequently, based on the ACL entry, the primary vPC node can generate a copy of the packet. After which, the primary vPC node can transmit the packet to the secondary vPC node.

BFD over VxLAN on vPC uplinks

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 (&#x201c;VNI&#x201d;) 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.

Control plane based technique for handling multi-destination traffic in overlay networks

Systems, methods, and computer-readable storage media for configuring a virtual port channel (VPC) domain. The disclosed technology involves determining that a first switch and a second switch are connected in a VPC domain, determining that the first switch is in a primary role, and determining a unique identifier for the first switch, a VPC portchannel number for the first switch, and an orphan port number for the first switch. Also, the first switch receives a unique identifier, a VPC portchannel number, and an orphan port number for the second switch. The first switch can associate the VPC portchannel number for the second switch and the VPC portchannel number for the first switch with a unified VPC portchannel number and create a first unique orphan port number for the first switch and a second unique orphan port number for the second switch.

Managing virtual port channel switch peers from software-defined network controller

In one embodiment an approach is provided to efficiently program routes on line cards and fabric modules in a modular router to avoid hot spots and thus avoid undesirable packet loss. Each fabric module includes two separate processors or application specific integrated circuits (ASICs). In another embodiment, each fabric module processor is replaced by a pair of fabric module processors arranged in series with each other, and each processor is responsible for routing only, e.g., IPv4 or IPv6 traffic. The pair of fabric module processors communicates with one another via a trunk line and any packet received at either one of the pair is passed to the other of the pair before being passed back to a line card.

Router table scaling in modular platforms

A plurality of line cards with each line card having a respective network forwarding engine and a respective outgoing interface (OIF) list and at least one fabric module communicatively coupled with each line card with each fabric module can have a respective network forwarding engine. The local OIF list can be asymmetrically programmed. The network forwarding engine of a line card can be configured to receive a multicast packet, compare a multicast address associate with the received multicast packet with entries in the local OIF list of the line card and forward the received multicast packet to at least one interface associated with the multicast address in response to the comparison resulting in a match.

Increasing multicast scale via localization of indices

A novel method for configuring first and second managed forwarding elements to perform logical Lswitching and Lrouting is described. The method generates a first set of flow entries for configuring the first managed forwarding element to perform logical Lingress processing and Lrouting processing. The method generates a second set of flow entries for configuring the second managed forwarding element to performing logical Legress processing.

Distributed logical L3 routing

Growing community of inventors

Santa Clara, CA, United States of America

Mehak Mahajan