Juniper Networks, Inc.

Wen Lin

John E Drake

SelvaKumar Sivaraj

Ravi Shekhar

Ryan Bickhart

Vamshi Krishna Voruganti

Vikram Nagarajan

Kapil Arora

Kevin F Wang

Aldrin Isaac

Vasudevan Venkatraman

Satya Ranjan Mohanty

Kireeti Kompella

Manish P Gupta

Tapraj Singh

Pankaj Shukla

Princy T Elizabeth

Sharmila Koppula

Sean A Mentzer

Yi Zheng

Manish Satyapal Gupta

Zhaohui Zhang

Sunesh Rustagi

Babu Singarayan

Nitin Singh

Vinay K Nallamothu

Soumyodeep Joarder

Rukesh Dorai

Hassan C Hosseini

Xichun Hong

Mukesh Kumar

Pankaj Kumar Gupta

Shivakumar Channalli

Yakov Rekhter

Prasad Miriyala

Robert W Kebler

Yimin Shen

Manoj Sharma

Jagadish Narasimha Grandhi

Maruthi Kishore Tiruveedhula

Prabhu Raj V K

Vrishabha Sikand

Suresh Palguna Krishnan

Ramesh Kandula

Sunil Kumar Malali

Kumuthini Ratnasingham

Disha M Chopra

Channasangamesh S Hugar

Pratibha Goel

Ragupathi J

Naveen Ashik

Prabakaran Arumugam

Nadeem Mohammad

Michal Styszynski

Gowri Shankar Ramanarayanan

Praful Lalchandani

Muniyappan Suruttaiyan

Deepti J Chandra

Kranthi Kumar Katam

Moo Jin Jeong

Vishal Garg

Selvakumar Sivaraj

In some cases, once Fast Reroute (FRR) has taken place (e.g., for MPLS protection), a further FRR is undesirable, and even detrimental. A mechanism to prevent a further FRR, once such a further FRR is determined to be potentially harmful, is described.

Avoiding loops by preventing further fast reroute (FRR) after an earlier FRR

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

Techniques for EVPN Host Routed Bridging (HRB) and EVPN cloud-native data center with Host Routed Bridging (HRB) are described. A host computing device of a data center includes one or more containerized user-level applications. A cloud native virtual router is configured for dynamic deployment by the data center application orchestration engine and operable in a user space of the host computing device. Processing circuitry is configured for execution of the containerized user-level applications and the cloud native virtual router. The cloud native virtual router comprises a containerized routing protocol process configured to operate as a control plane, and a data plane for the containerized router. The data plane is configured to operate an ethernet virtual private network (EVPN) encapsulation/decapsulation data path of an overlay network for communicating layer two (L2) network traffic of the containerized user applications over a switch fabric of the data center.

EVPN host routed bridging (HRB) and EVPN cloud native data center

A network device may originate a route, and may designate the route as a first colored route having a first color. The network device may advertise the first colored route to a first intermediate network device to cause the first intermediate network device to propagate the first colored route to an ingress network device over a first colored border gateway protocol session. The network device may designate the route as a second colored route having a second color, and may advertise the second colored route to a second intermediate network device to cause the second intermediate network device to propagate the second colored route to the ingress network device over a second colored border gateway protocol session.

Providing border gateway protocol deterministic path forwarding

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

Techniques are described for providing fast reroute for BUM traffic in EVPN. For example, a first provider edge (PE) device, elected as a designated forwarder (DF) of an Ethernet segment, configures a backup path using a label received from a second PE device of the Ethernet segment (e.g., backup DF) that identifies the second PE device as a 'protector' of the Ethernet segment. For example, a routing component of the DF configures within a forwarding component a backup path to the second PE device, e.g., installing the label and operation(s) within the forwarding component to cause the forwarding component to add the label to BUM packets received from a core network. Therefore, when an access link to the local CE device has failed, the DF reroutes BUM packets from the core network via the backup path to the second PE device, which sends the BUM packets to the CE device.

Fast reroute for BUM traffic in ethernet virtual private networks

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

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

Growing community of inventors

Andover, MA, United States of America

Wen Lin