Failure detection for tunneled label-switched paths

• US 8,472,346 B1
• Filed: 05/09/2011
• Issued: 06/25/2013
• Est. Priority Date: 06/08/2007
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Bahadur, Nitin, Kompella, Kireeti
• Primary Examiner(s): Sefcheck, Gregory
• Assistant Examiner(s): YOUNG, STEVE R
• Application Number:
  US13/103,838
• Time in Patent Office: 778 Days
• Field of Search: None
• US Class Current: 370/254
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 49/555 Error detection

Abstract

In general, principles of the invention relate to techniques for detecting data plane failures in Multi-Protocol Label Switching (MPLS) Label-Switched Paths (LSPs) that may be tunneled over one or more other LSPs. More specifically, the techniques described herein allow for testing connectivity of an LSP that is tunneled through at least one other LSP, and testing connectivity of an inter-autonomous system LSP. For example, a method comprises providing, with an intermediate label-switching router (LSR) of an LSP, instructions to an ingress LSR of the LSP to modify a forwarding equivalence class (FEC) stack of MPLS echo request packets. The intermediate LSR may provide the instructions within an MPLS echo reply packet.

Claims

1. A router that operates as an ingress label-switching router (LSR) of a first label-switched path (LSP), the router comprising:

a processor;

a protocol module executing on the processor;

wherein the protocol module tests connectivity of the first LSP by sending a Multi-Protocol Label Switching (MPLS) echo request packet that includes both a label stack having a label for directing the MPLS echo request packet along the first LSP and a forwarding equivalence class (FEC) stack specifying a FEC identifying the first LSP, and

wherein the protocol module receives from an intermediate LSR of the first LSP in response to the MPLS echo request packet, an MPLS echo reply packet that includes information that instructs the ingress LSR to modify the FEC stack specified within subsequent MPLS echo request packets to be sent by the ingress LSR for testing connectivity of the first LSP.

2. The router of claim 1, wherein the intermediate LSR is an ingress LSR of a second LSP over which a portion of the first LSP is tunneled, and

wherein the MPLS echo reply packet includes information that specifies a FEC that identifies the second LSP and instructs the ingress LSR of the first LSP to add to the FEC stack of the subsequent MPLS echo request packets the FEC that identifies the second LSP.

3. The router of claim 2, wherein the MPLS echo reply packet includes information that specifies a position indicator that indicates a position within the FEC stack specified within the subsequent MPLS echo request packets at which to place the FEC that identifies the second LSP.

4. The router of claim 2, wherein the intermediate LSR is an egress LSR of the second LSP, and

wherein the MPLS echo reply packet includes information that specifies a FEC that identifies the second LSP and instructs the ingress LSR of the first LSP to remove from the FEC stack of the subsequent MPLS echo request packets the FEC that identifies the second LSP.

5. The router of claim 2, wherein the first LSP is of a different type than the second LSP.

6. The router of claim 5, wherein the first LSP is a label distribution protocol (LDP) LSP, and wherein the second LSP is a Resource Reservation Protocol (RSVP) LSP.

7. The router of claim 1, wherein the intermediate LSR is an ingress LSR of a second LSP to which the first LSP is stitched, and

wherein the MPLS echo reply packet includes information that specifies a FEC that identifies the second LSP and instructs the ingress LSR of the first LSP to change the FEC in the FEC stack of the subsequent MPLS echo request packets that identifies the first LSP to the FEC that identifies the second LSP.

8. The router of claim 7, wherein the first LSP is associated with a first autonomous system;

wherein the second LSP is associated with a second autonomous system, wherein the first LSP and the second LSP are stitched together to form an end-to-end LSP;

wherein the ingress LSR of the first LSP comprises an ingress LSR of the end-to-end LSP that tests connectivity of the end-to-end LSP by sending the MPLS echo request packet.

9. The router of claim 8, wherein the MPLS echo reply packet includes information that specifies a FEC identifying the second LSP, wherein the information instructs the ingress LSR to modify the FEC stack of the subsequent MPLS echo request packets by replacing the FEC identifying the first LSP with the FEC identifying the second LSP.

10. The router of claim 1, wherein the protocol module of the ingress LSR sends subsequent MPLS echo request packets for testing connectivity of the LSP,

wherein the subsequent MPLS echo request packets include a modified FEC stack in accordance with the information included in the MPLS echo reply packet received from the intermediate LSR.

11. The router of claim 1, wherein the information that instructs the ingress LSR to modify the FEC stack comprises a FEC specified within a TLV sub-field of the MPLS echo reply.

12. The router of claim 1, wherein the FEC identifying the first LSP comprises a single element that captures one of an Internet Protocol (IP) prefix, a Virtual Private Network (VPN) IP prefix, a Label Distribution Protocol (LDP) prefix sub-TLV, a CR-LDP LSP identifier, a L2 VPN endpoint, a FEC pseudowire, and a Resource Reservation Protocol (RSVP) IP session.

13. A router that operates as a label-switching router (LSR) of a first label-switched path (LSP), the router comprising:

a processor; and

a protocol module executing on the processor;

wherein the protocol module tests connectivity of the first LSP by receiving from an ingress LSR of the first LSP a Multi-Protocol Label Switching (MPLS) echo request packet that includes both a label stack having a label for directing the MPLS echo request packet along the first LSP and a forwarding equivalence class (FEC) stack specifying a FEC identifying the first LSP, and

wherein the protocol module sends an MPLS echo reply packet to the ingress LSR in response to the MPLS echo request packet, the MPLS echo reply packet including information that instructs the ingress LSR to modify the FEC stack specified within subsequent MPLS echo request packets to be sent by the ingress LSR for testing connectivity of the first LSP.

14. The router of claim 13, wherein the LSR is an ingress LSR of a second LSP over which a portion of the first LSP is tunneled, and

wherein the MPLS echo reply packet includes information that specifies a FEC that identifies the second LSP and instructs the ingress LSR of the first LSP to add to the FEC stack of the subsequent MPLS echo request packets the FEC that identifies the second LSP.

15. The router of claim 14, wherein the protocol module constructs the MPLS echo reply packet to include information that specifies a position indicator that indicates a position within the FEC stack specified within the subsequent MPLS echo request packets at which to place the FEC that identifies the second LSP.

16. The router of claim 14, wherein the LSR is an egress LSR of the second LSP, and

wherein the MPLS echo reply packet includes information that specifies a FEC that identifies the second LSP and instructs the ingress LSR of the first LSP to remove from the FEC stack of the subsequent MPLS echo request packets the FEC that identifies the second LSP.

17. The router of claim 14, wherein the first LSP is of a different type than the second LSP.

18. The router of claim 17, wherein the first LSP is a label distribution protocol (LDP) LSP, and wherein the second LSP is a Resource Reservation Protocol (RSVP) LSP.

19. The router of claim 13, wherein the LSR determines whether the LSR is one of an ingress LSR or an egress LSR of a second LSP over which a portion of the first LSP is tunneled based on information within a control plane portion of the MPLS echo request packet and information within a data plane portion of the MPLS echo request packet and based on a downstream topology of a network traversed by the first LSP.

20. The router of claim 13, wherein the LSR is an ingress LSR of a second LSP to which the first LSP is stitched, and

wherein the MPLS echo reply packet includes information that specifies a FEC that identifies the second LSP and instructs the ingress LSR of the first LSP to change the FEC in the FEC stack of the subsequent MPLS echo request packets that identifies the first LSP to the FEC that identifies the second LSP.

21. The router of claim 20, wherein the first LSP is associated with a first autonomous system;

wherein the second LSP is associated with a second autonomous system, wherein the first LSP and the second LSP are stitched together to form an end-to-end LSP;

wherein the ingress LSR of the first LSR comprises an ingress LSR of the end-to-end LSP that tests connectivity of the end-to-end LSP by sending the MPLS echo request packet.

22. The router of claim 21, wherein the MPLS echo reply packet includes information that specifies a FEC identifying the second LSP,

wherein the information instructs the ingress LSR to modify the FEC stack of the subsequent MPLS echo request packets by replacing the FEC identifying the first LSP with the FEC identifying the second LSP.

23. The router of claim 20, wherein the LSR is an egress LSR of the first LSP.

24. The router of claim 20, wherein the LSR is an ingress LSR of the second LSP.

25. The router of claim 20, wherein the LSR determines whether the LSR is one of an egress LSR of the first LSP or an ingress LSR of the second LSP based on information within a control plane portion of the MPLS echo request packet and information within a data plane portion of the MPLS echo request packet and based on a downstream topology of a network traversed by the end-to-end LSP.

26. The router of claim 13, wherein the protocol module of the ingress LSR receives subsequent MPLS echo request packets for testing connectivity of the LSP,

wherein the subsequent MPLS echo request packets include a modified FEC stack in accordance with the information included in the MPLS echo reply packet received from the LSR.

27. The router of claim 13, wherein the information that instructs the ingress LSR to modify the FEC stack comprises a FEC specified within a TLV sub-field of the MPLS echo reply.

28. The router of claim 13, wherein the FEC identifying the first LSP comprises a single element that captures one of an Internet Protocol (IP) prefix, a Virtual Private Network (VPN) IP prefix, a Label Distribution Protocol (LDP) prefix sub-TLV, a CR-LDP LSP identifier, a L2 VPN endpoint, a FEC pseudowire, and a Resource Reservation Protocol (RSVP) IP session.