Method and apparatus for diagnosing a fault in a network path

• US 7,983,174 B1
• Filed: 12/19/2005
• Issued: 07/19/2011
• Est. Priority Date: 12/19/2005
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Aldrin, Sam K., Monaghan, John, Nadeau, Thomas D.
• Primary Examiner(s): Moe; Aung S
• Assistant Examiner(s): Louis; Vinncelas
• Application Number:
  US11/313,283
• Time in Patent Office: 2,038 Days
• Field of Search: 370/216, 370241-250, 370/351, 370/217, 714/25, 714/27, 714/43
• US Class Current: 370/242
• CPC Class Codes: H04L 43/0817 by checking functioning
• 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]

Abstract

A method of diagnosing a fault in a network path comprises the steps, performed at a diagnosing node, of initiating a path discovery test. The diagnosing node receives at least one path discovery test response and identifies the diagnosable node on the network path from a path discovery test response. The diagnosing node remotely accesses said diagnosable node and performs a diagnostic routine at said diagnosable node.

Claims

1. A method of diagnosing a fault in a Multi Protocol Label Switching (MPLS) network path comprising the steps, performed at a diagnosing node, of:

initiating a path discovery test to a destination node;

receiving at least one path discovery test response;

identifying a diagnosable node on the MPLS network path from the path discovery test response;

remotely accessing said diagnosable node; and

performing a diagnostic routine, using a layer two service of the Open System Interconnection (OSI) reference model, at said diagnosable node to at least determine whether an MPLS packet handled by said diagnosable node carried an incorrect header;

wherein the layer two service does not have information about an exchange of layer three routing information with a service provider;

in response to the diagnostic routine not diagnosing the fault at the diagnosable node, using the layer two service of the OSI reference model, the diagnosable node, from forwarding information at the diagnosable node, without sending a test packet, identifying a next-hop node along the MPLS network path to the destination node, and using the layer two service of the OSI reference model, remotely accessing the next-hop node along the MPLS network path to the destination node as a new diagnosable node and performing the diagnostic routine at said new diagnosable node;

wherein the method is performed by one or more computing devices;

wherein the method is performed in a-the layer two service of the OSI reference model.

2. A method as claimed in claim 1 further comprising, initiating a connectivity test prior to said path discovery test, and initiating said path discovery test if the connectivity fails.

3. A method as claimed in claim 1 in which the MPLS network path is an MPLS label switched path.

4. A method as claimed in claim 3 in which the label switched path is contained within a VPN.

5. A method as claimed in claim 3 in which the diagnostic routine includes at least one of identification of operator misconfiguration, identification of the failure of label distribution protocol, identification of a route installation problem, a label switch path black hole, a label switch path return path failure, label distribution protocol session failure;

label allocation failure;

route target mismatch;

or router line card failure.

6. A method as claimed in claim 1 further comprising displaying a diagnosis report.

7. A method as claimed in claim 6 in which the report comprises an observation identifying the MPLS network path and node characteristics.

8. A method as claimed in claim 6 further comprising displaying a log of diagnostic routine steps performed.

9. A method as claimed in claim 6 further comprising implementing a recommended fault correction action.

10. A method as claimed in claim 1 in which the diagnosing node comprises a network management system.

11. A method as claimed in claim 1 in which the path discovery test comprises one of a traceroute command or a PVP path trace.

12. A method as claimed in claim 1 in which the path discovery test is initiated at an ingress node of the MPLS network path.

13. A method as claimed in claim 1 in which the path discovery test is initiated at a network path image accessible at the diagnosing node.

14. A method as claimed in claim 1 in which the diagnosable node is identified as one of the furthest downstream node in the MPLS network path sending a path discovery test response or a node on the MPLS network path sending a fault path discovery test response.

15. A method as claimed in claim 1 further comprising initiating a path discovery test at each end node of the MPLS network path.

16. A method as claimed in claim 1 in which the path discovery test response includes a diagnosable node identifier, and the corresponding diagnosable node is identified at the diagnosing node from identification information accessible by the diagnosing node.

17. A method as claimed in claim 16 in which diagnosable node remote access data is obtained at the diagnosable node from information accessible by the diagnosable node.

18. A method as claimed in claim 1 performed in response to a notified connectivity change.

19. A method as claimed in claim 1 in which the diagnosable node comprises at least one of a router, a bridge or a switch.

20. A method as claimed in claim 1 in which the step of remotely accessing the diagnosable node comprises logging onto the diagnosable node.

21. A method of claim 1, wherein the identifying the diagnosable node on the MPLS network path from the path discovery test response comprises identifying the diagnosable node as either a last healthy node or a first node that returned an unhealthy response.

22. A computer readable volatile or non-volatile storage medium storing one or more sequences of instructions for diagnosing a fault in a Multi Protocol Label Switching (MPLS) network path which, when executed by one or more processors, cause the one or more processors to perform the steps of:

initiating a path discovery test to a destination node;

receiving at least one path discovery test response;

identifying a diagnosable node on the MPLS network path from the path discovery test response;

remotely accessing said diagnosable node; and

performing a diagnostic routine, using a layer two service of the Open System Interconnection (OSI) reference model, at said diagnosable node to at least determine whether an MPLS packet handled by said diagnosable node carried an incorrect header;

wherein the layer two service does not have information about an exchange of layer three routing information with a service provider, in response to the diagnostic routine not diagnosing the fault at the diagnosable node, using the layer two service of the OSI reference model, the diagnosable node, from forwarding information at the diagnosable node, without sending a test packet, identifying a next-hop node along the MPLS network path to the destination node, and using the layer two service of the OSI reference model, remotely accessing the next-hop node along the MPLS network path to the destination node as a new diagnosable node and performing the diagnostic routine at said new diagnosable node;

wherein the steps are performed in a-the layer two service of the OSI reference model.

23. A computer readable volatile or non-volatile storage medium of claim 22, wherein the identifying the diagnosable node on the MPLS network path from the path discovery test response comprises identifying the diagnosable node as either a last healthy node or a first node that returned an unhealthy response.

24. An apparatus for diagnosing a fault in a Multi Protocol Label Switching (MPLS) network path comprising:

one or more processors;

a network interface communicatively coupled to the one or more processors and configured to communicate one or more packet flows among the one or more processors in a network;

and

a computer readable volatile or non-volatile storage medium storing one or more sequences of instructions for diagnosing a fault in the MPLS network path which, when executed by the one or more processors, cause the one or more processors to perform;

initiating a path discovery test to a destination node;

receiving at least one path discovery test response;

identifying a diagnosable node on the MPLS network path from the path discovery test response;

remotely accessing said diagnosable node; and

performing a diagnostic routine, using a layer two service of the Open System Interconnection (OSI) reference model, at said diagnosable node to at least determine whether a-an MPLS packet handled by said diagnosable node carried an incorrect header;

wherein the layer two service does not have information about an exchange of layer three routing information with a service provider,

in response to the diagnostic routine not diagnosing the fault at the diagnosable node, using the layer two service of the OSI reference model, the diagnosable node, from forwarding information at the diagnosable node, without sending a test packet, identifying a next-hop node along the MPLS network path to the destination node, and using the layer two service of the OSI reference model, remotely accessing the next-hop node along the MPLS network path to the destination node as a new diagnosable node and performing the diagnostic routine at said new diagnosable node;

wherein the diagnostic routine is performed in a-the layer two service of the Open OSI reference model.

25. An apparatus of claim 24, wherein the identifying the diagnosable node on the MPLS network path from the path discovery test response comprises identifying the diagnosable node as either a last healthy node or a first node that returned an unhealthy response.