Juniper Networks, Inc.

Kapil Arora

Vikram Nagarajan

Shraddha Hegde

Robert W Kebler

Princy T Elizabeth

Soumyodeep Joarder

Sunil Kumar Malali

Wen Lin

Nitin Singh

Samson P Ninan

Ramesh Kandula

Manish Satyapal Gupta

John E Drake

Babu Singarayan

Sharmila Koppula

Himanshu Agarwal

Pankaj Kumar Gupta

Eric C Rosen

Santosh Pallagatti Kotrabasappa

Sachin S Natu

Levinh Hoang

Naveen Ashik

Raj Chetan Boddireddy

Goutham Patil R

Echo or traceroute functionality is supported in a path spanning multiple autonomous systems (ASes) having segment routing (SR) enabled, the path including an ingress node and an egress node, by: (a) obtaining a return label stack to reach the ingress node from either (A) the egress node, or (B) a transit node in the path; (b) obtaining a label stack to reach, from the ingress node, either (A) the egress node, or (B) the transit node; (c) generating a request message including the return label stack; and (d) sending the request message towards either (A) the egress node, or (B) the transit node using the label stack. The example method may further include: (e) receiving, by either (A) the egress node, or (B) the transit node, the request message, wherein the request message includes information for performing a validity check; (f) performing a validity check using the information included in the request message to generate validity information; (g) generating a reply message including the validity information and information from the return label stack; and (h) sending the reply message towards the ingress node using information from the return label stack included in the request message.

Path monitoring system (PMS) controller or ingress node based multiprotocal label switching (MPLS) ping and traceroute in inter-autonomous system (AS) segment routing (SR) networks

Ping or traceroute functionality is supported in a path spanning multiple autonomous systems (ASes) having segment routing (SR) enabled, the path including an ingress node in a first autonomous system (AS) and an egress node in an AS other than the first AS, using a reverse path label pair including (1) a node segment identifier (SID) corresponding to an AS Border Router (ASBR) of the second AS (second ASBR), and (2) an egress peer engineering (EPE) SID corresponding to a segment between the second ASBR to an ASBR of the first AS (first ASBR). Responsive to receiving a ping or traceroute request by a router in the second AS, the router generates a ping or traceroute reply including the reverse path label pair. The ping or traceroute reply is forwarded to the second ASBR using the node SID of the reverse path label pair. The ping or traceroute reply is then forwarded from the second ASBR to the first ASBR using the EPE SID of the reverse path label pair. Finally, the ping or traceroute reply can be forwarded (e.g., using standard IP forwarding) from the first ASBR to the headend router.

Ping and traceroute in inter-autonomous system (AS) segment routing (SR) networks without requiring headend router or path monitoring system (PMS) controller knowledge of topology outside of origin AS

An improved traceroute mechanism for use in a label-switched path (LSP) is provided by (a) receiving, by a device in the LSP, an echo request message, wherein the echo request includes a label stack having a least one label, and wherein each of the at least one label has an associated time-to-live (TTL) value; (b) responsive to receiving the echo request, determining by the device, whether or not the device is a penultimate hop popping (PHP) device for the outermost label of the label stack; and (c) responsive to determining that the device is the PHP device for the outermost label of the label stack, (1) generating an echo reply message corresponding to the echo request message, wherein the echo reply message is encoded to indicate that the device is the PHP device for the outermost label of the label stack, and (2) sending the echo reply message back towards a source of the echo request message. Responsive to receiving the echo reply message by the ingress of the LSP defined by the outermost label of the label stack, the ingress may (a) determine whether or not the received echo reply message was sourced from the PHP of the LSP defined by the outermost label of the label stack, and (b) responsive to a determination that the received echo reply message was sourced from the PHP of the LSP defined by the outermost label of the label stack, (1) generate a next echo request in which the TTL value associated with the outermost label in the label stack is increased and in which the TTL value associated with a next to outermost label, if any, in the label stack is incremented, and (2) send the next echo request message on the LSP defined by the outermost label of the label stack.

Time-to-live (TTL) handing for segment routing ping/traceroute

A device may store first information regarding a first pseudowire connection with a first device, wherein the first pseudowire connection provides access to an Ethernet virtual private network (EVPN) to communicate with a host device. The device may store second information regarding a second pseudowire connection with a second device, wherein the second pseudowire connection provides access to the EVPN to communicate with the host device. The device may receive a message that includes a configuration identifier and identify the configuration identifier. The device may change a first characteristic of the first pseudowire connection based on the configuration identifier. The device may change a second characteristic of the second pseudowire connection based on the configuration identifier. The device may receive data from the host device based on changing the first characteristic of the first pseudowire connection and changing the second characteristic of the second pseudowire connection.

Coordinating pseudowire connection characteristics and multi-homed provider edge device capabtilities

Techniques are described for facilitating node protection for Broadcast, unknown Unicast, and Multicast (BUM) traffic for a multi-homed node failure. For example, each VTEP (e.g., PE device) may advertise a protected VTEP address that indicates an IP address of a remote PE device that is to be protected in the event of a node failure. In the event a multi-homed PE device fails, the ingress PE device sends a BUM packet including the protected VTEP address for the failed node. When an egress PE device receives the BUM packet, the egress PE device determines whether the BUM packet includes the protected VTEP address and whether the egress PE device is operating as a backup designated forwarder (DF). If the BUM packet includes the protected VTEP address and the egress PE device is a backup DF, the egress PE device forwards the BUM traffic to the ESI.

Node protection for bum traffic for multi-homed node failure

Ping and traceroute in inter-autonomous system (AS) segment routing (SR) networks without requiring headend router or path monitoring system (PMS) controller knowledge of topology outside of origin as

Techniques are described for selectively pinging certain devices along a segment routing label switched path (LSP) to detect failures in the segment routing LSP. For example, an ingress device comprises one or more processors operably coupled to a memory that are configured to: in response to a request to verify connectivity of a segment routing LSP, configure a FEC stack specifying a stack of segment routing labels for the segment routing LSP; for each of the one or more devices identified from the FEC stack: generate a respective MPLS connectivity request packet for a respective device identified from an outermost FEC of the FEC stack; send the MPLS connectivity request packet to the respective device; receive an MPLS connectivity response packet that verifies connectivity of the respective device; and in response, update the FEC stack by removing the outermost FEC of the FEC stack that identifies the respective device.

Segmented traceroute for segment routing traffic engineering

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

Path monitoring system (PMS) controller or ingress node based multiprotocal label switching (MPLS) ping and traceroute in inter- autonomous system (AS) segment routing (SR) networks

Techniques are described for facilitating node protection for Broadcast, unknown Unicast, and Multicast (BUM) traffic for a multi-homed node failure. For example, multi-homed provider edge (PE) devices each advertise egress node protection labels to an ingress PE device. In the event one of the multi-homed PE devices fails, the ingress PE device sends a BUM packet including the egress node protection labels for the failed node. When an egress PE device receives the BUM packet, the egress PE device determines whether the BUM packet includes the egress node protection labels and whether the egress PE device is operating as a backup designated forwarder (DF) on an Ethernet segment identifier (ESI) for which the failed node was the DF. If the BUM packet includes the egress node protection labels and the egress PE device is operating as a backup DF, the egress PE device forwards the BUM traffic to the ESI.

Time to live (TTL) handing for segment routing ping/traceroute

Coordinating pseudowire connection characteristics and multi-homed provider edge device capabilities

A first network device permits a bidirectional forwarding detection (BFD) session with a second network device. The first network device is a designated forwarder for a third network device, a first link is provided between the first network device and the third network device, the second network device is a backup designated forwarder for the third network device, a second link is provided between the second network device and the third network device. The first network device detects a link failure associated with the first link between the first network device and the third network device, and provides, via the BFD session, a BFD message to the second network device. The BFD message includes an indication of the link failure, and the BFD message is to cause the second network device to be a new designated forwarder for the third network device.

Reducing traffic loss during link failure in an ethernet virtual private network multihoming topology

A first device may receive network traffic including a first label. The first label may be an inclusive multicast label associated with a second device. The second device may be a designated forwarder for an Ethernet segment. The first device may determine a second label based on receiving the network traffic including the first label. The second label may be used to route the network traffic to a customer edge device, via a third device, rather than the second device. The third device may be a non-designated forwarder for the Ethernet segment. The first device may provide the network traffic, including the second label, to the third device to permit the third device to provide, via the Ethernet segment, the network traffic to the customer edge device based on the second label when a failure occurs in association with the second device.

Growing community of inventors

Bengaluru, India

Kapil Arora