Simultaneously testing connectivity to multiple remote maintenance endpoints of the same maintenance association

• US 7,995,483 B1
• Filed: 03/02/2009
• Issued: 08/09/2011
• Est. Priority Date: 01/20/2009
• Status: Expired due to Fees

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Shukla, Pankaj, Bayar, Roopa, Mehta, Apurva, Rustagi, Sunesh
• Primary Examiner(s): Vu; Huy D
• Assistant Examiner(s): Chery; Dady
• Application Number:
  US12/396,138
• Time in Patent Office: 890 Days
• Field of Search: 370/241, 370/241.1, 370/242, 370/245, 370/252, 370/229, 370/230, 370/235
• US Class Current: 370/241.1
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/50 Testing arrangements
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

Abstract

In general, techniques are described for simultaneously testing connectivity to same or different remote maintenance endpoints of the same maintenance association. Specifically, a network device may include a control unit that simultaneously executes both a first and a second maintenance session. The control unit maintains first and second session identifiers that uniquely identifies the first and second maintenance sessions. The control unit receives via the first maintenance session input that specifies parameters for a maintenance message and generates the maintenance message in accordance with the parameters such that the maintenance message includes the first session identifier. The network device also includes an interface card that forwards the maintenance message to another network device in order to determine connectivity between these two network devices. By generating the maintenance message to include the first session identifier, the control unit may upon receiving a response to the maintenance message resolve to which of the maintenance session the response corresponds.

Claims

1. A method comprising:

simultaneously executing, with a first network device, a first maintenance session and a second maintenance session different from the first maintenance session for a same maintenance association, wherein the maintenance association comprises a logical grouping of at least the first network device and a second network device that are established to verify the integrity of a single service instance;

maintaining a first session identifier that uniquely identifies the first maintenance session within the first network device and a second session identifier that uniquely identifies the second maintenance session within the first network device;

generating, with the first network device, an outgoing maintenance message such that the outgoing maintenance message includes a session identifier field specifying the first session identifier when the outgoing maintenance message is associated with the first maintenance session and specifying the second session identifier when the outgoing maintenance message is associated with the second maintenance session, wherein the outgoing maintenance message conforms to a maintenance protocol that does not specify session identifiers for inclusion in the outgoing maintenance message;

transmitting, with the first network device, the outgoing maintenance message to a second network device included within the maintenance association;

receiving, with the first network device, a response maintenance message from the second network device in response to the outgoing maintenance message, wherein the response maintenance message includes the same session identifier field, unmodified by the second network device, specifying either the first or the second session identifier;

parsing, with the first network device, the response maintenance message to determine whether the session identifier field stores either the first or the second session identifier; and

forwarding, with the first network device, the response maintenance message to the first or the second maintenance session based on the determination.

2. The method of claim 1, further comprising:

receiving, with the first maintenance session, input that specifies parameters by which to generate the outgoing maintenance message,

wherein generating the outgoing maintenance message comprises generating the outgoing maintenance message in accordance with the parameters such that the maintenance message includes the first session identifier, and

wherein forwarding the outgoing maintenance message includes forwarding the outgoing maintenance message to the second network device in order to determine connectivity between the first and second network devices.

3. The method of claim 2, further comprising:

generating, with the first network device, maintenance information concerning receipt of the maintenance message, wherein parsing, with the first network device, the response maintenance message includes parsing the response maintenance message to determine the first session identifier; and

determining, with the first network device, that the response maintenance message and the maintenance information correspond to the first maintenance session based on the first session identifier parsed from the response maintenance message,

wherein forwarding the maintenance message comprises forwarding one or more of the response maintenance message and the maintenance information to the first maintenance session based on the determination.

4. The method of claim 2,

wherein receiving the input comprises receiving, with the first maintenance session, the input that specifies a first set of parameters by which to generate a first outgoing maintenance message,

wherein generating the maintenance message comprises generating the first outgoing maintenance message in accordance with the first set of parameters such that the first outgoing maintenance message includes the first session identifier, and

wherein the method further comprises:

receiving, with the second maintenance session, additional input that specifies a second set of parameters by which to generate a second outgoing maintenance message;

generating, with the first network device, the second outgoing maintenance message in accordance with the second set of parameters such that the second outgoing maintenance message includes the second session identifier; and

forwarding, with the first network device, the second outgoing maintenance message to either the second network device or a third network device in order to determine connectivity between the first and either the second or the third network device.

5. The method of claim 4, further comprising:

receiving, with the first network device, another response maintenance message in response to either the first or the second outgoing maintenance message that includes either the first or the second session identifier;

generating, with the first network device, additional maintenance information concerning receipt of the other maintenance message;

parsing, with the first network device, the other response maintenance message to determine whether the other maintenance message includes either the first or the second session identifier;

forwarding one or more of the other response maintenance message and the additional maintenance information to the first maintenance session based on a determination that the other response maintenance message includes the first session identifier; and

forwarding one or more of the other response maintenance message and the maintenance information to the second maintenance session based on a determination that the other response maintenance message includes the second session identifier.

6. The method of claim 2,

wherein receiving input that specifies the parameters comprises receiving, from a user, input that specifies the parameters defined by a loopback protocol, and

wherein the parameters include one or more of a Maintenance Domain (MD) level, a version, an OpCode, a plurality of flags, a first Type-Length Value (TLV) offset, additional OpCode related information and an end TLV.

7. The method of claim 2,

wherein generating the outgoing maintenance message comprises generating a LoopBack Message (LBM) in accordance with a LoopBack Protocol (LBP), wherein the LBM includes a header that stores one or more of the parameters and a session identifier (ID) Type-Length-Value (TLV) field that stores the first session identifier, and

wherein forwarding the outgoing maintenance message comprises forwarding the LBM to the second network device in order to determine the connectivity between the first and second network device.

8. The method of claim 7,

wherein receiving the response maintenance message comprises receiving, in response to the LBM, a LoopBack Response message (LBR) that transparently includes the first session identifier, and

the method further comprising generating, with the first network device, maintenance information concerning receipt of the LBR,

wherein parsing the maintenance message includes parsing the LBR to determine the first session identifier;

and

determining, with the first network device, that the LBR and the maintenance information correspond to the first maintenance session based on the first session identifier parsed from the LBR,

wherein forwarding the response maintenance message include forwarding one or more of the LBR and the maintenance information to the first maintenance session based on the determination.

9. The method of claim 7, further comprising:

receiving, with the first network device, configuration information that configures a maintenance endpoint to execute within the first network device, wherein the maintenance endpoint implements both a Continuity Check Protocol (CCP) and a LoopBack Protocol (LBP) and wherein the configuration information defines a list of at least one expected maintenance endpoint that belongs to the same maintenance association as that of the configured maintenance endpoint executing within the network device

generating, prior to generating the LBM, at least one Continuity Check Message (CCM);

forwarding, prior to generating the LBM, the at least one CCM to each of the at least one expected maintenance endpoints of the list;

receiving, with the first network device, at least one other CCM from the at least one expected maintenance endpoint of the list;

generating, with the first network device, another list indicating those of the at least one expected maintenance endpoints that are currently connected to the maintenance endpoint of the first network device based on the receipt of the at least one other CCM;

comparing the list of expected maintenance endpoints to the other list of currently connected maintenance endpoints to determine a connectivity fault; and

presenting the connectivity fault to a user prior to generating the LBM.

10. The method of claim 1,

wherein each of the first session and the second session are different software processes executed by an operating system of a control unit within the network devices, and

wherein maintaining the first session identifier and the second session identifier comprises maintaining the first session identifier and the second session identifiers as a first process identifier and a second process identifier assigned respectively by the operating system of the first network device to the first and second maintenance sessions.

11. The method of claim 1, wherein the first and second network devices each comprises one of a router or a bridge device.

12. The method of claim 1, further comprising presenting the maintenance message with either the first or the second maintenance session to a user.

13. A network device comprising:

a control unit that simultaneously executes a first maintenance session and a second maintenance session different from the first maintenance session for a same maintenance association, wherein the maintenance association comprises a logical grouping of at least the network device and another network device that are established to verify the integrity of a single service instance, maintains a first session identifier that uniquely identifies the first maintenance session within the first network device and a second session identifier that uniquely identifies the second maintenance session within the first network device and generates an outgoing maintenance message such that the outgoing maintenance message includes a session identifier field specifying the first session identifier when the outgoing maintenance message is associated with the first maintenance session and specifying the second session identifier when the outgoing maintenance message is associated with the second maintenance session, wherein the outgoing maintenance message conforms to a maintenance protocol that does not specify session identifiers for inclusion in the outgoing maintenance message; and

at least one interface card that transmits the outgoing maintenance message to the other network device included within the maintenance association and receives a response maintenance message from the other network device in response to the outgoing maintenance message, wherein the response maintenance message includes the same session identifier field, unmodified by the other network device, specifying either the first or the second session identifier,

wherein the control unit parses the response maintenance message to determine whether the session identifier field stores either the first or the second session identifier and forwards the response maintenance message to the first or the second maintenance session based on the determination.

14. The network device of claim 13,

wherein the control unit comprises a user interface module that presents the first and second maintenance sessions,

wherein the user interface module receives, with the first maintenance session, input that specifies parameters by which to generate the outgoing maintenance message,

wherein the control unit further comprises a maintenance endpoint (MEP) that generates the outgoing maintenance message in accordance with the parameters such that the maintenance message includes the first session identifier, and

wherein the at least one interface card forwards the outgoing maintenance message to the other network device in order to determine connectivity between the network devices.

15. The network device of claim 14, wherein the MEP further generates maintenance information concerning receipt of the maintenance message, parses the response maintenance message to determine the first session identifier, determines that the response maintenance message and the maintenance information correspond to the first maintenance session based on the first session identifier parsed from the response maintenance message, and forwards one or more of the response maintenance message and the maintenance information to the first maintenance session based on the determination.

16. The network device of claim 14,

wherein the user interface module receives via the first maintenance session the input that specifies a first set of parameters by which to generate a first outgoing maintenance message,

wherein the MEP generates the first outgoing maintenance message in accordance with the first set of parameters such that the first outgoing maintenance message includes the first session identifier,

wherein the user interface module further receives via the second maintenance session additional input that specifies a second set of parameters by which to generate a second outgoing maintenance message,

wherein the MEP further generates the second outgoing maintenance message in accordance with the second set of parameters such that the second outgoing maintenance message includes the second session identifier, and

wherein the at least one interface card forwards the second outgoing maintenance message to either the other network device or a third network device in order to determine connectivity between the network device and either the other or the third network device.

17. The network device of claim 16,

wherein the at least one interface card receives another response maintenance message in response to either the first or the second outgoing maintenance message that includes either the first or the second session identifier,

wherein the MEP generates additional maintenance information concerning receipt of the other maintenance message, parses the other response maintenance message to determine whether the other maintenance message includes either the first or the second session identifier, forwards one or more of the other response maintenance message and the additional maintenance information to the first maintenance session based on a determination that the other response maintenance message includes the first session identifier, and forwards one or more of the other response maintenance message and the maintenance information to the second maintenance session based on a determination that the other response maintenance message includes the second session identifier.

18. The network device of claim 14,

wherein the user interface module receives, from a user, input that specifies the parameters defined by a loopback protocol, and

wherein the parameters include one or more of a Maintenance Domain (MD) level, a version, an OpCode, a plurality of flags, a first Type-Length Value (TLV) offset, additional OpCode related information and an end TLV.

19. The network device of claim 14,

wherein the MEP includes a LoopBack Protocol (LBP) module that generates a LoopBack Message (LBM) in accordance with a LoopBack Protocol (LBP), wherein the LBM includes a header that stores one or more of the parameters and a session identifier (ID) Type-Length-Value (TLV) field that stores the first session identifier, and

wherein the at least one interface card forwards the LBM to the other network device in order to determine the connectivity between the network device and the other network device.

20. The network device of claim 19,

wherein the at least one interface card receives, in response to the LBM, a LoopBack Response message (LBR) that transparently includes the first session identifier, and

wherein the LBP generates maintenance information concerning receipt of the LBR, parses the LBR to determine the first session identifier, determines that the LBR and the maintenance information correspond to the first maintenance session based on the first session identifier parsed from the LBR, and forwards one or more of the LBR and the maintenance information to the first maintenance session based on the determination.

21. The network device of claim 19,

wherein the user interface module receives configuration information that configures the MEP to execute within the network device,

wherein the MEP includes both a Continuity Check Protocol (CCP) module and a LoobBack Protocol (LBP) module,

wherein the configuration information defines a list of at least one expected maintenance endpoint that belongs to the same maintenance association as that of the configured maintenance endpoint executing within the network device,

wherein the CCP module generates, prior to the LBP module generating the LBM, at least one Continuity Check Message (CCM),

wherein the at least one interface card forwards, prior to the LBP module generating the LBM, the at least one CCM to each of the at least one expected maintenance endpoints of the list and receives at least one other CCM from the at least one expected maintenance endpoint of the list,

wherein the CCP module generates another list indicating those of the at least one expected maintenance endpoints that are currently connected to the maintenance endpoint of the network device based on the receipt of the at least one other CCM, compares the list of expected maintenance endpoints to the other list of currently connected maintenance endpoints to determine a connectivity fault and generates the connectivity fault prior to generating the LBM based on the determination.

22. The network device of claim 13,

wherein the control unit further executes an operating system,

wherein each of the first session and the second session are different software processes executed by the operating system,

wherein the first session identifier and the second session identifier comprise a first process identifier and a second process identifier respectively, and

wherein the operating system assigns the first process identifier and the second process identifier to the first and second maintenance sessions, respectively.

23. The network device of claim 13, wherein the network device and the other network device each comprises one of a router or a bridge device.

24. The network device of claim 13, wherein the control unit includes a user interface module that presents the maintenance message with either the first or the second maintenance session to a user.

25. A network system comprising:

a first network that includes a first network device; and

a second network that includes a second network device,

wherein the first network device and the second network device logically belong to a maintenance association that enables the first network device to troubleshoot connectivity between the first network device and the second network device that belong to the same maintenance association,

wherein the first network device includes;

a first control unit that simultaneously executes a first maintenance session and a second maintenance session different from the first maintenance session for the same maintenance association, maintains a first session identifier that uniquely identifies the first maintenance session within the first network device and a second session identifier that uniquely identifies the second maintenance session within the first network device and generates an outgoing maintenance message such that the outgoing maintenance message includes a session identifier field specifying the first session identifier when the outgoing maintenance message is associated with the first maintenance session and specifying the second session identifier when the outgoing maintenance message is associated with the second maintenance session, wherein the outgoing maintenance message conforms to a maintenance protocol that does not specify session identifiers for inclusion in the outgoing maintenance message; and

a first interface card that transmits the outgoing maintenance message to the second network device included within the maintenance association,

wherein the second network device includes;

a second interface card that receives the outgoing maintenance message from the first network device, wherein the outgoing message includes a destination address identifying the second network device and a source address identifying the first network device; and

a second control unit that generates a response maintenance message to the outgoing maintenance message by swapping the destination address with the source address and changing an opcode to indicate a type of the message as a response message without further modifying the outgoing maintenance message,

wherein the second interface card forwards the response maintenance message to the first network device,

wherein the first interface card receives the response maintenance message from the second network device, wherein the response maintenance message includes the same session identifier field, unmodified by the second network device, specifying either the first or the second session identifier, and

wherein the first control unit parses the response maintenance message to determine whether the session identifier field stores either the first or the second session identifier and forwards the response maintenance message to the first or the second maintenance session based on the determination.

26. The network system of claim 25,

wherein the first network comprises a customer network,

wherein the first network device comprises a customer edge (CE) network device,

wherein the second network comprises a service provider network, and

wherein the second network device comprises a provider edge (PE) network device.

27. The network system of claim 25,

wherein the first network comprises a first customer network,

wherein the first network device comprises a first customer edge (CE) network device,

wherein the second network comprises a second customer network, and

wherein the second network device comprises a second customer edge (CE) network device.

28. The network system of claim 27, further comprising a service provider network that includes one or more provider edge (PE) network devices, wherein the service provider network interconnects the first and second customer networks via a service, wherein the service comprises one of a virtual private large area network (LAN) service (VPLS) or a virtual private network (VPN) service.

29. A non-transitory computer-readable storage medium comprising instructions that cause a programmable processor to:

simultaneously execute, with a first network device, a first maintenance session and a second maintenance session different from the first maintenance session for a same maintenance association, wherein the maintenance association comprises a logical grouping of at least the first network device and a second network device that are established to verify the integrity of a single service instance;

maintain a first session identifier that uniquely identifies the first maintenance session within the first network device and a second session identifier that uniquely identifies the second maintenance session within the first network device;

generate, with the first network device, an outgoing maintenance message such that the outgoing maintenance message includes a session identifier field specifying the first session identifier when the outgoing maintenance message is associated with the first maintenance session and specifying the second session identifier when the outgoing maintenance message is associated with the second maintenance session, wherein the outgoing maintenance message conforms to a maintenance protocol that does not specify session identifiers for inclusion in the outgoing maintenance message;

transmit, with the first network device, the outgoing maintenance message to a second network device included within the maintenance association;

receive, with the first network device, a response maintenance message from the second network device in response to the outgoing maintenance message, wherein the response maintenance message includes the same session identifier field, unmodified by the second network device, specifying either the first or the second session identifier;

parse, with the first network device, the response maintenance message to determine whether the session identifier field stores either the first or the second session identifier; and

forward, with the first network device, the response maintenance message to the first or the second maintenance session based on the determination.