Transmitting packet label contexts within computer networks

• US 9,246,801 B1
• Filed: 04/07/2009
• Issued: 01/26/2016
• Est. Priority Date: 12/12/2008
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Kompella, Kireeti
• Primary Examiner(s): O'Connor, Brian
• Assistant Examiner(s): Preval, Lionel
• Application Number:
  US12/419,507
• Time in Patent Office: 2,485 Days
• Field of Search: 370/395.52, 370/386, 370/230, 370/395.5, 370/390, 370/389, 370/248, 370/400, 370/392, 370/252, 709/202
• US Class Current: 1/1
• CPC Class Codes: H04L 12/4645 Details on frame tagging routing of packets H04L45/00; support for virtual LAN H04L49/354
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 45/507 Label distribution
• CPC Class Codes: H04L 45/68 Pseudowire emulation, e.g. IETF WG PWE3
• CPC Class Codes: H04Q 2011/0077 Labelling aspects, e.g. multiprotocol label switching [MPLS], G-MPLS, MPAS

Abstract

In general, techniques are described for transmitting context information defining contexts for packet labels in a network. More specifically, a network device, e.g., a router, implements the context transmission techniques to facilitate debugging or troubleshooting of the network. The network device may comprise an interface card that receives a Multi-Protocol Label Switching (MPLS) data unit from another network device in accordance with a label switching protocol. The data unit may include a label stack affixed to a payload. The label stack may include one or more MPLS labels and context information associated with at least one of these labels, The interface card may, when forwarding the data unit, parse the data unit to determine the context information and then forward the data unit in accordance with these MPLS labels. A control unit included within the network device may record the forwarding of the data unit and the determined context information.

Claims

1. A method comprising:

receiving, with a first network device intermediately positioned along a label-switched path (LSP) through a network between an ingress to the LSP and an egress to the LSP, a Multi-Protocol Label Switching (MPLS) data unit from a second network device of the network in accordance with a label switching protocol, wherein the data unit includes a label stack affixed to a payload, wherein the label stack includes two or more MPLS labels used for forwarding the data unit through the network and context information associated with at least two of the MPLS labels of the label stack, wherein the context information is arranged in the label stack to alternate between entries containing individual ones of the two or more MPLS labels and entries containing portions of the context information that pertains to the preceding one of the MPLS labels in the label stack and provides a context unused to forward the MPLS data unit and for understanding the associated at least two MPLS labels of the label stack, and wherein the context information identifies a packet flow transported by the data unit by specifying a source address, a source port, a destination address, a destination port and a protocol associated with the payload contained within the data unit;

forwarding the data unit out an output interface of the first network device in accordance with the two or more MPLS labels of the label stack;

when forwarding the data unit, parsing, with the first network device, the data unit to determine the context information; and

recording, with the first network device, the forwarding of the data unit and the determined context information.

2. The method of claim 1, further comprising presenting a report to a user with the first network device, wherein the report provides an indication of the forwarded data unit and the determined context information.

3. The method of claim 1, wherein forwarding the data unit comprises:

swapping one of the labels with a new label identified in a forwarding table of a network device without modifying the context information of the label stack to associate the new label with any context information within the label stack associated with the swapped one of the labels; and

forwarding the data unit according to the new label.

4. The method of claim 1, wherein forwarding the data unit comprises:

after receiving the data unit, removing one of the labels from the label stack;

removing from the label stack any of the context information associated with the one of the labels removed from the label stack; and

forwarding the data unit according to a next one of the one or more labels within the label stack or, when all of the labels have been removed, a destination specified by the payload of the data unit.

5. The method of claim 1, further comprising prior to receiving the data unit, receiving a signaling message with the first network device in accordance with the label switching protocol to negotiate establishment of the label switched path, wherein the signaling message specifies the context information to be included within the network stack for at least one of the one or more labels.

6. The method of claim 5, wherein the signaling message specifies a data type for the context information to be included within the label stack.

7. The method of claim 6, wherein the data type specifies that the context information is to include the source address, the destination address, the source port, the destination port, and the protocol.

8. The method of claim 1, further comprising receiving configuration information from the user associating a set amount of context information with the at least one of the labels for which the context information defines the context and defines a type of the context information, wherein the types of context information include the source address, the destination address, the source port, the destination port and the protocol.

9. The method of claim 8,

wherein parsing the context information comprises parsing the set amount of context information from the data unit, and

the method further comprises presenting the set amount of context information alongside the type of the context information to a user to facilitate debugging of the network.

10. The method of claim 1,

wherein the network comprises a Multi-Protocol Label Switching (MPLS) network,

wherein the first network device comprises a Label Switching Router (LSR),

wherein the second network device comprises one of an LSR or a Label Edge Router (LER), and

wherein the label switching protocol comprises a Label Distribution Protocol (LDP).

11. A network device intermediately positioned along a label-switched path (LSP) through a network between an ingress to the LSP and an egress to the LSP comprising:

an interface card that receives a Multi-Protocol Label Switching (MPLS) data unit from a second network device of the network in accordance with a label switching protocol, wherein the data unit includes a label stack affixed to a payload, and wherein the label stack includes two or more MPLS labels used for forwarding the data unit through the network and context information associated with at least one of the labels of the label stack, wherein the context information is arranged in the label stack to alternate between entries containing individual ones of the two or more MPLS labels and entries containing portions of the context information that pertains to the preceding one of the labels in the label stack and provides a context unused to forward the MPLS data unit and for understanding the associated at least two of the MPLS labels of the label stack, and wherein the context information identifies a packet flow transported by the data unit by specifying a source address, a source port, a destination address, a destination port and a protocol associated with the payload contained within the data unit, forwards the data unit in accordance with the two or more MPLS labels of the label stack and, when forwarding the data unit, parses the data unit to determine the context information; and

a control unit that records the forwarding of the data unit and the determined context information.

12. The network device of claim 11, wherein the control unit further presents a report to a user, wherein the report provides an indication of the forwarded data unit and the determined context information.

13. The network device of claim 11, wherein the interface card maintains a forwarding table, swaps one of the labels with a new label identified in the forwarding table without modifying the context information of the label stack to associate the context information with the new label, and forwards the data unit according to the new label, and forwards the data unit according to the new label.

14. The network device of claim 11, wherein the interface card, after receiving the data unit, removes one of the labels from the label stack, removes from the label stack any of the context information associated with the one of the labels removed from the label stack and forwards the data unit according to a next one of the one or more labels within the label stack or, when all of the labels have been removed, a destination specified by the payload of the data unit.

15. The network device of claim 11, wherein the control unit includes an MPLS protocol module that, prior to receiving the data unit, receives a signaling message in accordance with the label switching protocol to negotiate establishment of the label switched path, wherein the signaling message specifies the context information to be included within the network stack for at least one of the one or more labels.

16. The network device of claim 15, wherein the signaling message specifies a data type for the context information to be included within the label stack.

17. The network device of claim 16, wherein the data type specifies that the context information is to include the source address, the destination address, the source port, the destination port, and the protocol.

18. The network device of claim 11, wherein the interface card further receives an Label Distribution Protocol (LDP) message in accordance with a LDP that defines a scope for the context information associated with the at least one of the labels for which the context information defines the context, wherein the scope defines a type and set amount of context information associated with the at least one of the labels, wherein the types of context information include the source address, the destination address, the source port, the destination port and the protocol.

19. The network device of claim 11, wherein the control unit includes a user interface module that presents a user interface by which a user may enter configuration information associating a scope for the context information with the at least one of the labels for which the context information defines the context, wherein the scope defines a type and set amount of the context information, and wherein the types of context information include at least one of a source address, a destination address, an ingress address, an egress address, a customer identifier, a virtual private large area network address, a source port, a destination port, an ingress port, and an egress port.

20. The network device of claim 19,

wherein the interface card parses the set amount of context information from the data unit, and

wherein the control unit includes a user interface module that presents the set amount of context information alongside the type of the context information to a user via a user interface to facilitate debugging of the network.

21. The network device of claim 11,

wherein the network comprises a Multi-Protocol Label Switching (MPLS) network,

wherein the first network device comprises a Label Switching Router (LSR),

wherein the second network device comprises one of an LSR or a Label Edge Router (LER), and

wherein the label switching protocol comprises a Label Distribution Protocol (LDP).

22. A network system comprising:

one or more customer networks; and

a network comprising;

at least two network devices that each reside at an edge of the network, wherein one of the at least two edge network devices couples to the one or more customer networks; and

a transit network device positioned between the at least two edge network devices, wherein the transit network device includes;

an interface card that receives a data unit from one of the edge network devices of the network in accordance with a label switching protocol, wherein the data unit includes one or more labels used for forwarding the data unit through the network and context information associated with at least one of the labels, wherein the context information is arranged in the label stack to alternate between entries containing individual ones of the two or more labels and entries containing portions of the context information that pertains to the preceding one of the labels in the label stack and provides a context unused to forward the MPLS data unit and for understanding the associated at least two of the labels of the label stack, and wherein the context information identifies a packet flow transported by the data unit by specifying a source address, a source port, a destination address, a destination port and a protocol associated with the payload contained within the data unit, and

wherein the interface card further parses the data unit to determine the context information; and

a control unit that presents the determined context information to a user.

23. The network system of claim 22,

wherein the interface card receives the data unit via a Label Switching Path (LSP) established in accordance with a Label Distribution Protocol (LDP) between the at least two edge network devices.

24. A network system comprising:

an ingress Label Switching Router (LSR) of a Multi-Protocol Label Switching (MPLS) network;

an egress LSR of the MPLS network; and

at least one intermediate LSR positioned between the ingress LSR and egress LSR of the MPLS network,

wherein the ingress LSR, the egress LSR and the at least one intermediate LSR all lie along a Label Switched Path (LSP) through the MPLS network,

wherein the ingress LSR, the egress LSR and the at least one intermediate LSR exchange one or more signaling messages in accordance with a label distribution protocol (LDP) to negotiate establishment of the LSP, and

wherein the one or more signaling messages each specifies context information unused to forward the MPLS data unit and to be included within a network stack for at least one of one or more labels when forwarding the MPLS packets along the LSP, and wherein the context information identifies a packet flow transported by the data unit by specifying a source address, a source port, a destination address, a destination port and a protocol associated with the payload contained within the data unit.

25. A non-transitory computer-readable medium comprising instructions for causing a programmable processor of a first network device to:

receive, along a label-switched path (LSP) through a network, a Multi-Protocol Label Switching (MPLS) data unit from a second network device of the network in accordance with a label switching protocol, wherein the data unit includes a label stack affixed to a payload, wherein the label stack includes two or more MPLS labels used for forwarding the data unit through the network and context information associated with at least one of the labels of the label stack, wherein the context information is arranged in the label stack to alternate between entries containing individual ones of the two or more MPLS labels and entries containing portions of the context information that pertains to the preceding one of the MPLS labels in the label stack and provides a context unused to forward the MPLS data unit and for understanding the associated at least two of the MPLS labels of the label stack, and wherein the context information identifies a packet flow transported by the data unit by specifying a source address, a source port, a destination address, a destination port and a protocol associated with the payload contained within the data unit, and wherein the first network device comprises a transit network device intermediately positioned between an ingress to the LSP and an egress to the LSP;

forward the data unit in accordance with the two or more MPLS labels of the label stack;

when forwarding the data unit, parse the data unit to determine the context information; and

record the forwarding of the data unit and the determined context information.

26. The non-transitory computer-readable medium of claim 25, wherein the instructions further cause the programmable processor to present a report to a user, wherein the report provides an indication of the forwarded data unit and the determined context information.

27. The non-transitory computer-readable medium of claim 25, wherein the instructions further cause the programmable processor to, prior to receiving the data unit, receive a signaling message with the network device in accordance with the label switching protocol to negotiate establishment of the label switched path, wherein the signaling message specifies the context information to be included within the network stack for at least one of the one or more labels.

28. A method comprising:

receiving, with a first ingress network device along a label-switched path (LSP) through a first network, a data unit from a second network device of a second network, wherein the data unit includes a header and a payload, but does not include a label stack;

inspecting, with the first ingress network device, the header and payload of the data unit to determine a forwarding equivalence class (FEC);

determining, with the first ingress network device, a label entry within a forwarding table based on the determined FEC, wherein the label entry defines a MultiProtocol Label Switching (MPLS) label and a scope of context information associated with the MPLS label to affix to the data unit, wherein the context information provides a context unused to forward the MPLS data unit, and wherein the context information identifies a packet flow transported by the data unit by specifying a source address, a source port, a destination address, a destination port and a protocol specified in the header of the data unit;

determining, with the first ingress network device, context information in accordance with the scope of the context information defined by the label entry;

affixing, with a first ingress network device, a label stack to the data unit in accordance with an MPLS protocol to generate an MPLS packet, wherein the label stack includes the MPLS label defined by the label entry and the determined context information; and

forwarding, with the first ingress network device, the MPLS packet out an output interface of the first ingress network device in accordance with the MPLS label of the label stack to a transit network device intermediately positioned between the first ingress network device to the LSP and an egress network device of the LSP so as to enable the transit network device to record the context information included in the label stack.