公开(公告)号：US11765077B1

公开(公告)日：2023-09-19

申请号：US17719016

申请日：2022-04-12

Applicant: Juniper Networks, Inc.

Inventor： Kapil Arora ,  Samson P Ninan ,  Shraddha Hegde

IPC: H04L45/50 ,  H04L45/00 ,  H04L45/02

CPC classification number: H04L45/50 ,  H04L45/02 ,  H04L45/04 ,  H04L45/22

Abstract: 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.

公开(公告)号：US11025522B2

公开(公告)日：2021-06-01

申请号：US16403540

申请日：2019-05-04

Applicant: Juniper Networks, Inc.

Inventor： Kapil Arora ,  Shraddha Hegde

IPC: H04L12/26 ,  H04L12/751 ,  H04L12/723

Abstract: 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.

公开(公告)号：US10917337B1

公开(公告)日：2021-02-09

申请号：US16250631

申请日：2019-01-17

Applicant: Juniper Networks, Inc.

Inventor： Kapil Arora ,  Shraddha Hegde

IPC: H04L12/723 ,  H04L12/721 ,  H04L12/841 ,  H04L12/733

Abstract: 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.

公开(公告)号：US10567279B2

公开(公告)日：2020-02-18

申请号：US16100565

申请日：2018-08-10

Applicant: Juniper Networks, Inc.

Inventor： Kapil Arora ,  Nitin Singh ,  Sunil Kumar Malali ,  Vikram Nagarajan

IPC: H04L12/723 ,  H04L12/24 ,  H04L12/18 ,  H04L12/46 ,  H04L12/751 ,  H04L12/761 ,  H04L12/707 ,  H04L12/703 ,  H04L12/721

Abstract: 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.

公开(公告)号：US20190007309A1

公开(公告)日：2019-01-03

申请号：US16100565

申请日：2018-08-10

Applicant: Juniper Networks, Inc.

Inventor： Kapil Arora ,  Nitin Singh ,  Sunil Kumar Malali ,  Vikram Nagarajan

IPC: H04L12/723 ,  H04L12/721 ,  H04L12/703 ,  H04L12/707 ,  H04L12/761 ,  H04L12/18 ,  H04L12/24 ,  H04L12/46 ,  H04L12/751

CPC classification number: H04L45/50 ,  H04L12/18 ,  H04L12/1886 ,  H04L12/4641 ,  H04L41/0654 ,  H04L45/02 ,  H04L45/16 ,  H04L45/22 ,  H04L45/28 ,  H04L45/66

Abstract: 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.

公开(公告)号：US11381501B2

公开(公告)日：2022-07-05

申请号：US16947453

申请日：2020-08-03

Applicant: Juniper Networks, Inc.

Inventor： Vikram Nagarajan ,  Robert W. Kebler ,  Kapil Arora ,  Himanshu Agarwal ,  Soumyodeep Joarder

IPC: H04L45/00 ,  H04L12/46 ,  H04L41/0813

Abstract: 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.

公开(公告)号：US11336569B2

公开(公告)日：2022-05-17

申请号：US16787911

申请日：2020-02-11

Applicant: Juniper Networks, Inc.

Inventor： Kapil Arora ,  Samson P. Ninan ,  Shraddha Hegde

IPC: H04L12/723 ,  H04L12/707 ,  H04L12/751 ,  H04L12/715 ,  H04L45/50 ,  H04L45/00 ,  H04L45/02

Abstract: 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.

公开(公告)号：US10693679B2

公开(公告)日：2020-06-23

申请号：US16127101

申请日：2018-09-10

Applicant: Juniper Networks, Inc.

Inventor： Wen Lin ,  Pankaj Kumar Gupta ,  Babu Singarayan ,  Sharmila Koppula ,  Manish Gupta ,  Kapil Arora

IPC: G06F15/16 ,  H04L12/46 ,  H04L12/703 ,  H04L12/709 ,  H04L12/723 ,  H04L12/26 ,  H04L12/721

Abstract: 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.

公开(公告)号：US10291433B2

公开(公告)日：2019-05-14

申请号：US15644274

申请日：2017-07-07

Applicant: Juniper Networks, Inc.

Inventor： Vikram Nagarajan ,  Robert W. Kebler ,  Kapil Arora ,  Naveen Ashik

IPC: H04L12/707 ,  H04L12/46 ,  H04L12/761 ,  H04L12/721 ,  H04L12/741 ,  H04L12/18 ,  H04L12/703 ,  H04L12/723

Abstract: In some examples, a customer edge device (CE) is configured to receive configuration data for multi-homed connectivity for a local layer 2 (L2) network with a L2 virtual private network (L2VPN) for a layer 3 (L3) network for switching L2 packet data units (PDUs) among two or more L2 networks connected to the L3 network including the local L2 network, wherein the configuration data for multi-homed connectivity configures the CE with a primary attachment circuit to a primary neighbor provider edge device (PE) for the L2VPN and with a backup attachment circuit to a backup neighbor PE for the L2VPN; and generate and send, in response to snooping a multicast join message indicating a multicast group, a control plane message via the backup attachment circuit to the backup neighbor PE for the L2VPN, wherein the control plane message is destined for the backup neighbor PE for the L2VPN.

公开(公告)号：US20180287946A1

公开(公告)日：2018-10-04

申请号：US15655210

申请日：2017-07-20

Applicant: Juniper Networks, Inc.

Inventor： Vikram Nagarajan ,  Wen Lin ,  Robert W. Kebler ,  Princy T. Elizabeth ,  Kapil Arora

IPC: H04L12/801 ,  H04L29/06 ,  G06F9/54

CPC classification number: H04L47/15 ,  G06F9/542 ,  H04L12/18 ,  H04L47/125 ,  H04L63/0272 ,  H04L65/4076

Abstract: In general, techniques are described for load-balancing responsibility for forwarding of multicast traffic into an active-active Ethernet segment between two or more multi-homed provider edge (PE) routers in an Ethernet Virtual Private Network (EVPN). In one example, a PE router may receive an Internet Group Management Protocol (IGMP) join report for a multicast group. The PE router may send join synch routes used to synchronize the join report for the multicast group across the Ethernet segment. The PE router may deterministically determine whether the PE router is configured to be an elected multicast forwarder for one of a plurality of multicast groups. If the PE router is elected a multicast forwarder, the PE router may configure a forwarding state of the PE router to ignore a designated forwarder calculation and to forward the multicast traffic into the Ethernet segment regardless of whether the PE router is a designated forwarder.