System and method for reported root cause analysis

• US 5,864,662 A
• Filed: 06/28/1996
• Issued: 01/26/1999
• Est. Priority Date: 06/28/1996
• Status: Expired due to Term

• Current Assignee: MCI Communications Corporation (Verizon Communications Inc.)
• Original Assignee: MCI Communications Corporation (Verizon Communications Inc.)
• Inventors: Brownmiller, Curtis, Tran, Minh T., Bencheck, Michael, DeMoss, Mark, Branton, Robert, Landon, Steve
• Primary Examiner(s): Decady, Albert
• Application Number:
  US08/670,844
• Time in Patent Office: 942 Days
• Field of Search: 395/183.01, 395/183.15, 395/183.11, 395/183.17, 395/183.19, 395/741, 395/742, 364/267, 364/267.7, 379/1, 379/32, 379/33
• US Class Current: 714/43
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/079 Root cause analysis, i.e. error or fault diagnosis in a hardware test environment G06F11/22; in a software test environment G06F11/36
• CPC Class Codes: H04L 41/0631 using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
• CPC Class Codes: H04L 43/0847 Transmission error

Abstract

A system and method for determining a root cause of error activity in a network is described herein. Root cause analysis includes the correlation between reported error activity for path, line and section entities along a provisioned channel in the network. Root causes can also be identified based upon the correlation of simultaneous error activity on various signal transport levels. Finally, root cause analysis can correlate error activity along various path entities.

Claims

1. A method for identifying a root cause of a problem in a provisioned channel in a network, the provisioned channel being routed through a plurality of network elements, the method comprising the steps of:

(1) receiving, in a layer of a network management system, a plurality of problem alert signals from a plurality of monitoring points, each of said plurality of monitoring points being associated with a network element in the network that is being monitored by said network management system, each of said plurality of problem alert signals being generated by a monitoring point based upon the analysis of performance monitoring data recorded for a section, line or path entity during a monitoring period; and

(2) identifying, in a layer of a network management system, a correlation between said plurality of problem alert signals to identify a root cause of a problem in the provisioned channel.

2. The method of claim 1, wherein said step (2) comprises the steps of:

(a) identifying a first problem alert signal at a first signal transport level from a first monitoring point associated with a network element in the circuit path;

(b) identifying a second problem alert signal at a second signal transport level, said second problem alert signal being generated by a second monitoring point associated with a second network element in the circuit path, wherein said first signal transport level is mapped into said second signal transport level; and

(c) identifying a third monitoring point upstream of said first monitoring point that reports a third problem alert signal corresponding to said second problem alert signal.

3. The method of claim 2, wherein said step (b) is repeated until a highest signal transport level is identified.

4. The method of claim 2, further comprising the step of discontinuing further processing for problem alert signals corresponding to said first problem alert signal that are received by the layer in the network management system from monitoring points downstream from said first monitoring point.

5. The method of claim 1, wherein said step (2) comprises the steps of:

(a) identifying a line problem alert signal that results from error activity in a line entity;

(b) determining whether said line entity includes a plurality of section entities;

(c) determining whether a monitoring point associated with a section entity within said line entity has reported a section problem alert signal; and

(d) initiating a problem handling process for said section entity, if a monitoring point associated with a section entity has reported a section problem alert signal.

6. The method of claim 5, further comprising the step of:

(e) initiating a problem handling process for said line entity, if a monitoring point associated with a section entity has not reported a section problem alert signal.

7. The method of claim 5, further comprising a step before said step (b) of determining the topology of the line entity.

8. The method of claim 1, wherein said step (2) comprises the steps of:

(a) identifying a path problem alert signal that results from error activity in a path entity;

(b) determining whether said path entity includes a plurality of line entities;

(c) determining whether a monitoring point associated with a line entity within said path entity has reported a line problem alert signal; and

(d) initiating a problem handling process for said line entity, if a monitoring point associated with a line entity has reported a line problem alert signal.

9. The method of claim 8, further comprising the step of:

(e) initiating a problem handling process for said path entity, if a monitoring point associated with a line entity has not reported a line problem alert signal.

10. The method of claim 9, further comprising a step before said step (b) of determining the topology of the path entity.

11. The method of claim 1, wherein said step (2) comprises the steps of:

(a) identifying a first and a second path problem alert signal that results from error activity in a first and a second path entities;

(b) determining whether said first and second path entities include a common line entity; and

(c) initiating a problem handling process for said common line entity, if a common line entity exists.

12. The method of claim 11, further comprising a step before said step

(b) of determining the topology of said first and second path entities.

13. The method of claim 1, wherein said step (1) comprises the step of receiving a problem alert signal, said problem alert signal indicating that a monitored parameter has exceeded a predefined threshold.

14. A system for identifying a root cause of a problem in a provisioned channel in a network, the provisioned channel being routed through a plurality of network elements, the system comprising:

means for receiving, in a layer of a network management system, a plurality of problem alert signals from a plurality of monitoring points, each of said plurality of monitoring points being associated with a network element in the network that is being monitored by said network management system, each of said plurality of problem alert signals being generated by a monitoring point based upon the analysis of performance monitoring data recorded for a section, line or path entity during a monitoring period; and

means for identifying, in a layer of a network management system, a correlation between said plurality of problem alert signals to identify a root cause of a problem in the provisioned channel.

15. The system of claim 14, wherein said means for identifying comprises:

means for identifying a first problem alert signal at a first signal transport level from a first monitoring point associated with a network element in the circuit path;

means for identifying a second problem alert signal at a second signal transport level, said second problem alert signal being generated by a second monitoring point associated with a second network element in the circuit path, wherein said first signal transport level is mapped into said second signal transport level; and

means for identifying a third monitoring point upstream of said first monitoring point that reports a third problem alert signal corresponding to said second problem alert signal.

16. The system of claim 15, further comprising means for identifying a highest signal transport level that reports a corresponding problem alert signal.

17. The system of claim 15, further comprising means for discontinuing further processing for problem alert signals corresponding to said first problem alert signal that are received by the layer in the network management system from monitoring points downstream from said first monitoring point.

18. The system of claim 14, wherein said means for identifying comprises:

means for identifying a line problem alert signal that results from error activity in a line entity;

means for determining whether said line entity includes a plurality of section entities;

means for determining whether a monitoring point associated with a section entity within said line entity has reported a section problem alert signal; and

means for initiating a problem handling process for said section entity, if a monitoring point associated with a section entity has reported a section problem alert signal.

19. The system of claim 18, further comprising means for initiating a problem handling process for said line entity, if a monitoring point associated with a section entity has not reported a section problem alert signal.

20. The system of claim 18, further comprising means for determining the topology of the line entity.

21. The system of claim 14, wherein said means for identifying comprises:

means for identifying a path problem alert signal that results from error activity in a path entity;

means for determining whether said path entity includes a plurality of line entities;

means for determining whether a monitoring point associated with a line entity within said path entity has reported a line problem alert signal; and

means for initiating a problem handling process for said line entity, if a monitoring point associated with a line entity has reported a line problem alert signal.

22. The system of claim 21, further comprising means for initiating a problem handling process for said path entity, if a monitoring point associated with a line entity has not reported a line problem alert signal.

23. The system of claim 22, further comprising means for determining the topology of the path entity.

24. The system of claim 14, wherein said means for identifying comprises:

means for identifying a first and a second path problem alert signal that results from error activity in a first and a second path entities;

means for determining whether said first and second path entities include a common line entity; and

means for initiating a problem handling process for said common line entity, if a common line entity exists.

25. The system of claim 24, further comprising means for determining the topology of said first and second path entities.

26. The system of claim 14, wherein said means for receiving receives a problem alert signal, said problem alert signal indicating that a monitored parameter has exceeded a predefined threshold.

27. A computer program product for use with a computer system, comprising:

a computer usable medium having computer readable program code means embodied in said medium that identifies a root cause of a problem in a provisioned channel in a network, the provisioned channel being routed through a plurality of network elements, said computer readable program code means comprising;

first computer readable program code means for enabling the computer system to effect a reception, in a layer of a network management system, of a plurality of problem alert signals from a plurality of monitoring points, each of said plurality of monitoring points being associated with a network element in the network that is being monitored by said network management system, each of said plurality of problem alert signals being generated by a monitoring point based upon the analysis of performance monitoring data recorded for a section, line or path entity during a monitoring period; and

second computer readable program code means for enabling the computer system to effect an identification, in a layer of a network management system, of a correlation between said plurality of problem alert signals to identify a root cause of a problem in the provisioned channel.