Forwarding detection for point-to-multipoint label switched paths

• US 8,902,780 B1
• Filed: 09/26/2012
• Issued: 12/02/2014
• Est. Priority Date: 09/26/2012
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Hegde, Vikas, Kotrabasappa, Santosh Pallagatti, Ramachandran, Chandrasekar
• Primary Examiner(s): Jiang, Charles C
• Assistant Examiner(s): DEFAUW, THAD N
• Application Number:
  US13/627,660
• Time in Patent Office: 797 Days
• Field of Search: 370/252
• US Class Current: 370/252
• CPC Class Codes: H04L 41/0677 Localisation of faults
• 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/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 45/70 Routing based on monitoring results

Abstract

Techniques are described for verifying the connectivity status of multiple paths through a computer network. The techniques may be useful in testing the connectivity of label switched paths (LSPs), and particularly useful point-to-multipoint (P2MP) LSPs. In some embodiments, a P2MP label switched path (LSP) ping protocol may be used a first connectivity verification protocol for the P2MP LSP and a Multipoint Bidirectional Forwarding Detection (MP BFD) protocol may be used as a second connectivity verification protocol. In addition, use of the LSP ping protocol for connectivity testing of the P2MP LSP may be used to boot-strap session information for MP BFD sessions with egress devices of the P2MP LSP.

Claims

1. A method of verifying connectivity of paths through a computer network containing a plurality of network devices, the method comprising:

establishing a Multi-Protocol Label Switching (MPLS) point-to-multipoint (P2MP) label switched path (LSP) for transporting packets through a network, wherein the P2MP LSP includes a source device providing an ingress to the P2MP LSP and a plurality of destination devices providing a plurality of different egress devices from the P2MP LSP;

using a P2MP Label Switched Path (LSP) ping protocol, sending an LSP ping echo request along the P2MP LSP, wherein the LSP ping echo request embeds a discriminator to establish a Multipoint Bidirectional Forwarding Detection (MP BFD) session for testing connectivity of the P2MP LSP in accordance with a MP BFD protocol, and wherein the LSP ping echo request includes an indicator specifying that the egress devices of the P2MP LSP should not reply to the LSP ping echo request with an LSP ping echo reply to establish the MP BFD session; and

without receiving an LSP ping echo reply from the egress devices, initiating connectivity verification of the P2MP LSP by outputting BFD packets on the MP BFD session with the ingress device according to the MP BFD protocol.

2. The method of claim 1, wherein the source device and egress devices are members of a multicast virtual private network (MVPN), and wherein the P2MP LSP transports multicast data for the P2MP LSP.

3. The method of claim 1, wherein the LSP ping Echo request includes a type-length-value (TLV) to carry the discriminator for the MP BFD session.

4. The method of claim 1, further comprising:

receiving the BFD packets for the P2MP LSP with at least one of the egress devices prior to receiving the LSP ping echo request;

associating the BFD packets with a client-less BFD session; and

upon receiving the LSP ping echo request and without outputting an LSP ping echo reply, associating the BFD packets with the MP BFD session for the P2MP LSP.

5. The method of claim 1, further comprising:

receiving the BFD packets for the P2MP LSP with at least one of the egress devices prior to receiving the LSP ping echo request; and

rejecting the BFD packets for the P2MP LSP with the at least one of the egress devices until receiving the LSP ping echo request.

6. The method of claim 1,

wherein sending an LSP ping echo request along the P2MP LSP comprises periodically sending LSP ping echo requests along the P2MP LSP, and

wherein each of the LSP ping echo requests includes an indicator specifying that the egress devices of the P2MP LSP should not reply to the respective LSP ping echo request with an LSP ping echo reply to establish the MP BFD session.

7. The method of claim 1, further comprising:

detecting, with an application service executing within the computer network, a new egress device joining the application service and providing an egress to the P2MP LSP; and

with the application service, directing the source device to use the LSP ping protocol to send the LSP ping echo request along the P2MP LSP and addressed to the new egress device.

22. The method of claim 1, further comprising detecting, with one of the plurality of different egress devices, connectivity failure of the P2MP LSP using the MP BFD session without having output the LSP ping echo reply to establish the MP BFD session.

8. A method of verifying connectivity of paths through a computer network containing a plurality of network devices, the method comprising:

establishing a Multi-Protocol Label Switching (MPLS) point-to-multipoint (P2MP) label switched path (LSP) for transporting packets through a network, wherein the P2MP LSP includes a source device providing an ingress to the P2MP LSP and a plurality of destination devices providing a plurality of different egress devices from the P2MP LSP;

detecting, with an application service executing within the computer network, a new egress device joining the application service and providing an egress to the P2MP LSP;

with the application service, directing the source device to use a P2MP Label Switched Path (LSP) Ping protocol to send an LSP ping echo request along the P2MP LSP and addressed to the new egress device, wherein the LSP ping echo request embeds a discriminator to establish a Multipoint Bidirectional Forwarding Detection (MP BFD) session for testing connectivity of the P2MP LSP in accordance with the MP BFD protocol wherein the LSP ping echo request includes an indicator specifying that the egress devices of the P2MP LSP should not reply to the LSP ping echo request with an LSP ping echo reply to establish the MP BFD session; and

initiating connectivity verification of the P2MP LSP by outputting BFD packets, with the ingress device, on the MP BFD according to the MP BFD protocol.

9. The method of claim 8, wherein the application service comprises a multicast virtual private network (MVPN).

10. The method of claim 8,

wherein outputting BFD packets according to the MP BFD protocol comprises outputting the packets according to the Bidirectional Forwarding Detection protocol for the MP BFD session without receiving an LSP ping echo reply from the egress devices.

11. The method of claim 8, further comprising:

receiving the BFD packets for the P2MP LSP with at least one of the egress devices prior to receiving the LSP ping echo request;

associating the BFD packets with a client-less BFD session; and

upon receiving the LSP ping echo request and without outputting an LSP ping echo reply, associating the BFD packets with the MP BFD session for the P2MP LSP.

12. A network device comprising:

a control unit comprising hardware to execute a label distribution protocol to establish a Multi-Protocol Label Switching (MPLS) point-to-multipoint (P2MP) label switched path (LSP) for transporting packets through a network, wherein the P2MP LSP includes a source device providing an ingress to the P2MP LSP and a plurality of destination devices providing a plurality of different egress devices from the P2MP LSP;

an Label Switched Path (LSP) Ping protocol executing within the control unit to send an LSP ping echo request along the P2MP LSP, wherein the LSP ping echo request embeds a discriminator to establish a Multipoint Bidirectional Forwarding Detection (MP BFD) session for testing connectivity of the P2MP LSP in accordance with the MP BFD protocol, and wherein the LSP ping echo request includes an indicator specifying that the egress devices of the P2MP LSP should not reply to the LSP ping echo request with an LSP ping echo reply to establish the MP BFD session; and

a BFD protocol module executing within the control unit to, without receiving an LSP ping echo reply from the egress devices, initiating connectivity verification of the P2MP LSP by outputting BFD packets on the BFD session according to the MP BFD protocol.

13. The network device of claim 12, wherein the LSP ping Echo request includes a type-length-value (TLV) to carry the discriminator for the MP BFD session.

14. The network device of claim 12, wherein sending an LSP ping echo request along the P2MP LSP comprises periodically sending LSP ping echo requests along the P2MP LSP.

15. The network device of claim 12, wherein the MP BFD protocol module operates within a forwarding plane of the network device.

16. The network device of claim 12, further comprising:

an application service executing within the control unit, wherein the application service detects a new egress device joining the application service and directs the source device to use the LSP ping protocol to send the LSP ping echo request along the P2MP LSP and addressed to the new egress device.

17. The network device of claim 12, wherein the application service comprises a multicast virtual private network (MVPN).

18. A network device comprising:

a control unit comprising hardware to execute an application service, an Multi-Protocol Label Switching (MPLS) protocol, a point-to-multipoint (P2MP) Label Switched Path (LSP) Ping protocol, and a Multipoint Bidirectional Forwarding Detection (MP BFD) protocol module;

wherein the MPLS protocol establishes a Multi-Protocol Label Switching (MPLS) P2MP label switched path (LSP) for transporting packets for the application service through a network, wherein the P2MP LSP includes a source device providing an ingress to the P2MP LSP and a plurality of destination devices providing a plurality of different egress devices from the P2MP LSP;

wherein the application service detects a new egress device joining the application service and directs the source device to use the LSP ping protocol to send an LSP ping echo request along the P2MP LSP and addressed to the new egress device, wherein the LSP ping echo request embeds a discriminator to establish a Multipoint Bidirectional Forwarding Detection (MP BFD) session for testing connectivity of the P2MP LSP in accordance with the MP BFD protocol, and wherein the LSP ping echo request includes an indicator specifying that the egress devices of the P2MP LSP should not reply to the LSP ping echo request with an LSP ping echo reply to establish the MP BFD session; and

wherein the MP BFD protocol module, without receiving an LSP ping echo reply from the egress devices, initiating connectivity verification of the P2MP LSP by outputting BFD packets on the MP BFD session according to the Bidirectional Forwarding Detection protocol.

19. The network device of claim 18, wherein the LSP ping Echo request includes a type-length-value (TLV) to carry the discriminator for the MP BFD session.

20. The network device of claim 18, wherein the MP BFD protocol module operates within a forwarding plane of the network device.

21. The network device of claim 18, wherein the application service comprises a multicast virtual private network (MVPN).