Juniper Networks, Inc.

Babu Singarayan

Vishnu Janardhanan S

Manish Satyapal Gupta

Nitin Kumar

Manish P Gupta

Sharmila Koppula

Sayantani Gupta

Raghavendra Mallya

Kaliraj Vairavakkalai

Jeyananth Minto Jeganathan

Ashutosh K Grewal

Channasangamesh S Hugar

Arun G Menon

Aman Kapoor

Wen Lin

Kapil Arora

Sunanda L Kommula

Soumyodeep Joarder

Sudhin Jacob

Pratibha Goel

Gaurav Ganeriwal

Pankaj Kumar Gupta

Jonathan C Barth

Swamy Sadashivaiah Renu Kananda

Tapraj Singh

Javier Antich

Sri Karthik Goud Gadela

Vikas Vidyalal Patel

Srikanth Subramanian

Puneet Kedia

Avijit Basu

Vijeyalakshumi Koteeswaran

Renuka Sri Harsha C H

Sukesh Kumar

Binu Shanmughan

Binu S

Techniques are described to provide layer 2 (L2) circuit failover in the event connectivity to an Ethernet Virtual Private Network (EVPN) instance is lost. For example, if one of multi-homed provider edge (PE) devices loses connectivity to the EVPN instance, the PE device may mark its customer-facing interface as down and propagate the interface status to the access node such that the access node may update its routing information to switch L2 circuits to another one of the multi-homed PE devices having reachability to the EVPN instance. In some examples, the plurality of PE devices may further implement Connectivity Fault Management (CFM) techniques to propagate the interface status to the access node such that the access node may update its forwarding information to send traffic on a different L2 circuit to another one of the multi-homed PE devices having reachability to the EVPN instance.

Core isolation for logical tunnels stitching multi-homed EVPN and L2 circuit

Techniques are disclosed for an Ethernet Virtual Private Network (EVPN) Virtual Private Wire Service (VPWS) network with service interface-aware forwarding. In one example, a first network device signals to a second network device, using EVPN route advertisements, a multi-service service tunnel to transport network packets for a plurality of services. The services are identifiable by virtual local area network (VLAN) identifiers in the packets. The first network device is configured with a single transport interface for the service tunnel and the single transport interface is configured with respective service interfaces for the services. The first network device detects failure of a failed service interface of the service interfaces and outputs, in response to the failure, an EVPN route withdrawal message for the service tunnel that identifies the service corresponding to the failed service interface.

Using multiple ethernet virtual private network (EVPN) routes for corresponding service interfaces of a subscriber interface

The techniques describe detecting connectivity failure of an aggregated interface. To monitor connectivity of the aggregated interface, a packet processor of a plurality of packet processors is set as a session master responsible for managing an active forwarding plane connectivity detection session with a peer session master node. The other local packet processors of the virtual network node are selected as session standby nodes that each have a passive forwarding plane connectivity detection session running to the peer session master node. If a session master node goes down (i.e., by link or node failure), one of the local session standby nodes may detect the failure and is set as a new session master node by activating its passive session having the same session parameters.

Forwarding detection of an aggregated interface

The techniques describe forwarding multicast traffic using a multi-level cache in a network device forwarding plane for determining a set of outgoing interfaces of the network device on which to forward the multicast traffic. For example, a multi-level cache is configured to store a multicast identifier of a multicast packet and multicast forwarding information associated with the multicast identifier, such as identification of one or more egress packet processors of the network device to which the multicast packet is to be sent for forwarding to the set of one or more egress network devices, and/or outgoing interfaces of the network device toward each egress network device of the set of one or more egress network devices. The multi-level cache is also configured to store respective multicast identifiers that are to be encapsulated with outgoing multicast packets that are forwarded to the set of one or more egress network devices.

Optimized multicast forwarding with a cache

The techniques describe a network device comprising one or more processors configured to: receive configuration data configuring a plurality of virtual network nodes, wherein the configuration data configures a virtual client node including a corresponding line card having a port connected to a first customer network device, and configures a virtual core node including a corresponding line card having a port connected to a core network; provision a layer-2 (L2) circuit that includes, as an access interface, an interface logically connecting the virtual client node and virtual core node, wherein the L2 circuit provides connectivity between the virtual client node and a remote virtual client node; and forward, via the L2 circuit, packets between the virtual client node and the remote virtual client node to realize a logical network between the first customer network device and a second customer network device connected to the remote virtual PE node.

Network as a service using virtual nodes

Techniques are described for providing targeted selection of cascade ports of an aggregation device. In one example, the disclosed techniques enable dynamic assignment of active and backup cascade ports of an aggregation device for each extended port of satellite devices. In this example, rather than allocating resources for each of the extended ports of the satellite devices on all of the cascade ports of the aggregation device, the aggregation device instead allocates resources for each of the extended port only on the assigned active and backup cascade ports for the respective one of the extended ports of the satellite devices. The techniques are also described for providing traffic steering to a backup cascade port in the event the assigned active cascade port is unreachable, and, if the cascade port remains unreachable for a specified duration, the aggregation device may assign new active and backup cascade ports for the extended port.

Targeted selection of cascade ports

A network device selects a primary source for multicast traffic and a secondary source for the multicast traffic, where the multicast traffic is provided to endpoint devices communicating with a network, and where the primary source and the secondary source are redundant sources. The network device provides a first join request that includes information that causes a primary path to be provided from the primary source through the network. The network device provides a second join request that includes information that causes a secondary path to be provided from the secondary source through the network. The network device receives the multicast traffic from the primary source via the primary path and the secondary source via the secondary path, and provides the multicast traffic received from the primary source to the endpoint devices. The network device prevents the multicast traffic received from the secondary source from reaching the endpoint devices.

Utilizing upstream routing of multicast traffic from redundant multicast sources to increase multicast resiliency and availability

The techniques describe adaptive load-balancing based on traffic feedback from packet processors. In one example, a source virtual network node of the network device may determine whether a particular destination packet processor is or may become oversubscribed. For example, source packet processors of the source virtual network node may exchange feedback messages including traffic flow rate information. The source virtual network node may compute a total traffic flow rate and compare the total traffic flow rate with a bandwidth of the particular destination packet processor. In response to determining that the bandwidth of the destination packet processor is oversubscribed, the source virtual network node may update a forwarding plane data structure to reduce a likelihood of selecting the destination packet processor to which to forward packet flows.

Adaptive load-balancing over a multi-point logical interface

The techniques describe packet reordering for packets flowing on a new path in response to a change in internal forwarding paths in a network device. For example, a network device may dynamically change the selection of an internal forwarding path to achieve fabric path optimization ('OFP') or to ensure optimized load balancing. Packets forwarded on the new path are buffered such that the transmission of packets forwarded on the new path are delayed for a buffering time period of at least the time in which a packet is being sent from the source packet processor to the initial destination packet processor.

Intelligent buffering for packet reordering by virtual nodes within a network device

The techniques describe directly forwarding a packet from an ingress packet forwarding engine to a particular destination packet forwarding engine (PFE) when internal packet load balancing may otherwise result in an increased number of fabric hops. For example, a source PFE may receive incoming packets destined for a router reachable only by a particular destination PFE (e.g., egress PFE). Rather than load balancing the incoming packets to a destination PFE that is likely to be a non-egress PFE, a source PFE obtains fabric path information associated with the egress PFE from a destination PFE such that source PFE may forward incoming packets directly to the egress PFE.

Optimizing fabric path forwarding for virtual nodes within an electronic device

In one example, a management component executing on a single-chassis network device configures a virtual node with an abstract fabric interface having, as a destination address, identifiers of packet processors (e.g., PTFE-IDs) assigned to the virtual node on the other end of the abstract fabric interface. The management component of the single-chassis network device pre-creates an underlay network by using the fabric links at the packet processor. When the management component creates and connects an abstract fabric interface on the virtual nodes, the management component forms an overlay network and attaches the overlay network to the underlay network, e.g., by programming the forwarding plane packet processor, to connect the virtual nodes. However, users of the network device, external devices, and routing protocols will not view the abstract fabric interface as an overlay interface, but as a regular Ethernet interface (e.g., a Gigabit Ethernet interface).

Connecting virtual nodes in a network device using abstract fabric interfaces

In one example, a network device includes an interface card comprising a physical network interface; a forwarding component associated with the interface card; a control unit comprising one or more processors, wherein the control unit is configured to program the forwarding component to configure sets of one or more valid media access control (MAC) addresses in association with respective logical interfaces of a plurality of logical interfaces configured for the physical interface, wherein the forwarding component is configured to identify a logical interface of the plurality of logical interfaces with which to process a packet received by the network device at the physical interface, and wherein the forwarding component is configured to, in response to a determination that the set of valid MAC addresses associated with the identified logical interface does not include a valid MAC address that matches a destination MAC address of the packet, drop the packet.

Destination MAC validation per logical interface of a network device

In some examples, a method includes selecting, by a first virtual routing node of a single-chassis network device having a plurality of forwarding components and a plurality of fabric links coupling respective pairs of the plurality of forwarding components at respective fabric interfaces of the plurality of forwarding components, a fabric interface of a forwarding component of the plurality of forwarding components that has an egress interface toward a network destination and that is associated with the first virtual routing node; advertising, to the second virtual routing node, the fabric interface as a next hop for the network destination and a label for use in establishing a transport label switched path (LSP); and computing, by the second virtual routing node, a path for the transport LSP to include the fabric interface, and establishing the transport LSP along the computed path.

Growing community of inventors

San Jose, CA, United States of America

Babu Singarayan