Juniper Networks, Inc.

SelvaKumar Sivaraj

Sushant Kumar

Wen Lin

John E Drake

Ravi Shekhar

Aldrin Isaac

Vamshi Krishna Voruganti

Prasad Miriyala

Sunesh Rustagi

Tapraj Singh

Suresh Palguna Krishnan

Vasudevan Venkatraman

Mukesh Kumar

Sean A Mentzer

Yi Zheng

Vikram Nagarajan

Princy T Elizabeth

Rukesh Dorai

Xichun Hong

Ajay V Gaonkar

Bharat M Gaonkar

Zhaohui Zhang

Reji Thomas

Rajagopalan Subbiah

Eswaran Srinivasan

Jagadish Narasimha Grandhi

Prabhu Raj V K

Ryan Bickhart

Soumyodeep Joarder

Vrishabha Sikand

Ramesh Kandula

Kumuthini Ratnasingham

Debi Prasad Sahoo

Channasangamesh S Hugar

Ragupathi J

Prabakaran Thirumali Sampath

Pratibha Goel

Naveen Ashik

Prabakaran Arumugam

Avijit Basu

Biswajit Mandal

Gowri Shankar Ramanarayanan

Sharan Rachanagouda Bhadragoudar

Binu S

Madhu N Kopalle

MooJin Jeong

Ming Qiao

Praful Lalchandani

Candida M Bayross

Deepti J Chandra

Vishal Garg

Muniyappan Suruttaiyan

M Ganesh Prasad

Pavana C V

Kranthi Kumar Katam

Moo Jin Jeong

In an Ethernet Virtual Private Network (EVPN) with a multi-homed Ethernet Segment (MHES), potential problems of core isolation are avoided in a way that also avoids the potential 'split brain' problems.

Reducing convergence time and/or avoiding split-brain in multi-homed ethernet segment deployments, such as esi-lag deployments

A method for use in a system including an Ethernet Virtual Private Network (EVPN) core network and a VXLAN data plane, a first gateway device GW1 and a second gateway device GW2 operating in an all-active multihoming mode to interconnect the EVPN core network and VXLAN data plane, is described. The method includes establishing, by the second gateway device GW2, a VXLAN tunnel to a remote VTEP X before traffic is sent by the remote VTEP X and received by the second gateway device GW2, but after traffic is sent by the remote VTEP X and received by the first gateway device GW1. wherein the first and second gateway devices GW1 and GW2 use an anycast IP address as a source address for VTEP X.

Avoiding traffic flooding for known unicast traffic when an EVPN is inter-connected to a data plane VXLAN in all-active mode

A controller device receives, from a plurality of assisted replication network devices, respective utilization information associated with the plurality of assisted replication network devices. The controller device generates, based on the respective utilization information associated with the plurality of assisted replication network devices, load balancing information for a network device associated with two or more assisted replication network devices of the plurality of assisted replication network devices, and sends, to the network device, the load balancing information. The network selects, based on the load balancing information, a particular assisted replication network device of the two or more assisted replication network devices. The network device receives a traffic flow that is to be multicast and sends the traffic flow to the particular assisted replication network device, wherein sending the traffic flow to the particular assisted replication network device permits the particular assisted replication network device to multicast the traffic flow.

Load balancing of assisted replication network devices

In some implementations, a provider edge device associated with a link aggregation group (LAG) may maintain, according to a link aggregation control protocol (LACP), a set of links that connect the PE device to a consumer edge device. The provider edge device may determine that the provider edge device and another provider edge device associated with the LAG are not receiving link aggregation control protocol data units (LACPDUs) from the consumer edge device. The provider edge device may cause the set of links to have a maintain LAG status, which causes the provider edge device to keep up the set of links and to cease maintaining the set of links according to the LACP. The provider edge device may route, based on causing the set of links to have the maintain LAG status, one or more packets to or from the consumer edge device via the set of links.

Maintaining a set of links associated with a link aggregation group to facilitate provisioning or updating of a customer edge device

A first provider edge device may receive device information from a second provider edge device included in an Ethernet virtual private network (EVPN). The device information may identify a media access control (MAC) address and may indicate that the device is connected to the second provider edge device. The first provider edge device may receive data transmitted by the device and may determine, based on information included in the data, that the device has moved from the second provider edge device to the first provider edge device. The first provider edge device may generate a data packet including mobility information indicating that the device has moved to the first provider edge device. The first provider edge device may transmit, via a data plane of the EVPN, the data packet to the second provider edge device to permit the second provider edge device to update routing information for the device.

Fast convergence for MAC mobility

A plurality of switches may be arranged according to a spine and leaf topology in which each spine switch is connected to all leaf switches. A leaf switch includes a memory configured to store a plurality of policies, each of the plurality of policies being associated with a respective source identifier value and a respective destination address; a network interface communicatively coupled to one of the spine switches; and a processor implemented in circuitry and configured to: receive a packet from the spine switch via the network interface, the packet being encapsulated with a Virtual Extensible Local Area Network (VXLAN) header; extract a source identifier value from the VXLAN header; determine a destination address for the packet; determine a policy of the plurality of policies to apply to the packet according to the source identifier value and the destination address; and apply the policy to the packet.

Policy enforcement for bare metal servers by top of rack switches

Techniques are described for providing fast reroute for traffic in EVPN-VXLAN. For example, a backup PE device of an Ethernet segment is configured with an additional tunnel endpoint address ('reroute tunnel endpoint address') for a backup path associated with a second split-horizon group that is different than a tunnel endpoint address and first split-horizon group for another path used for normal traffic forwarding. The backup PE device sends the reroute tunnel endpoint address to a primary PE device of the Ethernet segment, which uses the reroute tunnel endpoint address to configure a backup path to the backup PE device over the core network. For example, the primary PE device may install the reroute tunnel endpoint address within its forwarding plane and one or more operations to cause the primary PE device to encapsulate a VXLAN header including the reroute tunnel endpoint address when rerouting the packet along the backup path.

Fast reroute for ethernet virtual private networks—virtual extensible local area network

An example network device includes memory, a communication unit, and processing circuitry coupled to the memory and the communication unit. The processing circuitry is configured to receive first samples of flows from an interface of another network device sampled at a first sampling rate and determine a first parameter based on the first samples. The processing circuitry is configured to receive second samples of flows from the interface sampled at a second sampling rate, wherein the second sampling rate is different than the first sampling rate and determine a second parameter based on the second samples. The processing circuitry is configured to determine a third sampling rate based on the first parameter and the second parameter, control the communication unit to transmit a signal indicative of the third sampling rate to the another network device; and receive third samples of flows from the interface sampled at the third sampling rate.

Adaptive flow monitoring

A method includes receiving, by a network analyzer implemented in circuitry, from a network device of a plurality of network devices, a sensor message for telemetry flow data. The sensor message indicates an interface index for a network interface, a virtual network identifier associated with a virtual network, and an IP address. The method further includes receiving, by the network analyzer, from the network device, a telemetry flow message for the telemetry flow data. The method further includes, in response to determining that the telemetry flow message includes an indication of an interface index that matches the interface index of the sensor message and that the telemetry flow message includes an indication of a virtual network identifier that matches the virtual network identifier of the sensor message, setting, by the network analyzer, the IP address as the source of the telemetry flow data.

Path flow of telemetry flow data for bare metal servers

Fast reroute for ethernet virtual private networks&#x2014;virtual extensible local area network

Techniques are described for providing security extensions to neighbor discovery in Ethernet Virtual Private Network (EVPN). For example, a network device that implements Ethernet Virtual Private Network (EVPN) receives a neighbor discovery response message including a nonce originated by a second network device and not originated by the first network device. The network device processes the neighbor discovery response message including the nonce originated by the second network device and not originated by the first network device.

Deploying secure neighbor discovery in EVPN

Techniques are described for managing a split-brain scenario in a multihomed environment by exchanging isolation information between a leaf device and two or more spine devices to which the leaf device is multihomed via a link aggregation group (LAG). The techniques include selecting one of the spine devices as a primary spine device and determining, based on the isolation information, whether the spine devices are isolated from each other. In the split-brain scenario in which all of the spine devices are isolated from each other, the primary spine device is configured to maintain the LAG with the leaf device while the other spine devices mark the LAG with the leaf device as down. In this way, in the split-brain scenario, the leaf device may continue to send traffic to other leaf devices in the leaf layer using the LAG to the primary spine device.

Managing split-brain scenario in multi-homed environment

Growing community of inventors

Sunnyvale, CA, United States of America

SelvaKumar Sivaraj