Granted Patent B2

US 9,118,502 · App. 12/485,549 · Granted Aug 25, 2015

Abstract

Claims (63)

1. A method of determining at a service device, a root cause of a failure in a packet switching telecommunications network, the method comprising:

selecting a service access point (SAP);

constructing, from a network-aware management system, a network topology map relative to said SAP, wherein the network topology map comprises a hierarchical list of detected failures determined from an order of tests starting at a lowest level of a hierarchy and proceeding to higher levels based upon a probability of errors being detected;

analyzing the state of said SAP;

analyzing a physical access port associated with said SAP;

analyzing a virtual private network (VPN) service hosting said SAP;

analyzing a service binding associated with said VPN service;

analyzing a layer 2 access interface associated with said binding;

analyzing a layer 3 access interface associated with said binding;

analyzing all routing protocols associated with said VPN service;

determining the root cause by selecting a lowest level failure from the hierarchical list of detected failures; and

displaying a root cause analysis of said failure.

2. The method of claim 1 , further comprising:

determining an administrative state of said SAP;

determining an operational state of said SAP; and

determining an alarm state of said SAP.

3. The method of claim 1 , further comprising:

displaying a cause for a failure based on a hierarchical analysis of detected failures for said SAP.

4. The method of claim 1 , further comprising:

displaying to a user at said service device, a list of circuit identifiers configured on said network.

5. The method of claim 1 , further comprising:

finding the VPN service hosting said SAP;

finding the service binding correlating the SAP to said VPN service;

finding a service tunnel used by said service binding;

finding a Multi Protocol Label Switching/Label Switch Path (MPLS/LSP) used by said service tunnel;

finding the layer 3 access interface using said service binding and said service tunnel;

finding a Virtual Private Routed Network (VPRN) service hosting the layer 3 access interface;

finding all VPRN service sites for said VPRN service;

finding all L3 access interfaces for said VPRN service; and

finding all routing protocols associated with said VPRN service.

6. The method of claim 5 , further comprising:

analyzing said routing protocols for proper configuration across said VPRN service.

7. The method of claim 1 , wherein analyzing the physical access port associated with the SAP further comprises:

determining an administrative state of the physical access port;

determining an operational state of the physical access port; and

determining an alarm state of the physical access port.

8. The method of claim 1 , wherein analyzing the physical access port associated with the SAP further comprises:

checking a MTU size associated with the physical access port.

9. The method of claim 1 , wherein analyzing the VPN service hosting the SAP further comprises:

determining an administrative state of the VPN service;

determining an operational state of the VPN service; and

determining an alarm state of the VPN service.

10. The method of claim 1 , wherein analyzing the VPN service hosting the SAP further comprises:

checking a MTU size associated with the VPN service.

11. The method of claim 1 , wherein the VPN service is an Epipe service.

12. The method of claim 1 , wherein analyzing the service binding associated with the VPN service further comprises:

determining an administrative state of the service binding;

determining an operational state of the service binding; and

determining an alarm state of the service binding.

13. The method of claim 1 , further comprising:

analyzing a SDP service tunnel when the service binding is down.

14. The method of claim 13 , further comprising:

analyzing a Multi Protocol Label Switching/Label Switched Path (MPLS/LSP) when the SDP service tunnel is down.

15. The method of claim 13 , further comprising:

analyzing a VPRN service site.

16. A system for providing a root cause of a failure in a packet switching telecommunications network, the system comprising:

a network-aware management system in communication with said network;

a service device in communication with said network-aware management system;

a user interface that is configured to select a service access point (SAP);

a service application on said service device that is configured to construct a network topology map relative to said SAP, wherein the network topology map comprises a hierarchical list of detected failures determined from an order of tests starting at a lowest level of a hierarchy and proceeding to higher levels based upon a probability of errors being detected, analyzes the state of said SAP, analyzes a physical access port associated with said SAP, analyzes a virtual service hosting said SAP, analyzes a service binding associated with said virtual service, analyzes a layer 3access interface associated with said binding, determine the root cause by selecting a lowest level failure from a hierarchical list of detected failures, and display a root cause analysis of said failure.

17. The system of claim 16 , wherein said service application determines an administrative state of said SAP, determines an operational state of said SAP, and determines an alarm state of said SAP.

18. The system of claim 17 , wherein said service application finds the virtual service hosting said SAP, finds the service binding correlating the SAP to said virtual service, finds the service tunnel used by said service binding, finds the MPLS/LSP used by said service tunnel, finds the layer 3 access interface using said service binding and said service tunnel, finds a VPRN service hosting the layer 3 access interface, finds all the VPRN service sites for said VPRN service, and finds all the L3 access interfaces for said VPRN service.

19. A non-transitory medium embodying a program of instructions executable by a machine to perform the method of claim 1 .

Assignments (11)