System and method for providing error analysis and correlation in a network element

• US 7,082,554 B2
• Filed: 10/22/2002
• Issued: 07/25/2006
• Est. Priority Date: 01/24/2002
• Status: Active Grant

• Current Assignee: WSOU Investments, LLC (WSOU Holdings, LLC)
• Original Assignee: Alcatel Canada Inc. (Nokia Corporation)
• Inventors: Poulin, Andre, Wilson, Karen Margaret, Wang, Jiang
• Primary Examiner(s): Baderman, Scott
• Assistant Examiner(s): Chu, Gabriel L.
• Application Number:
  US10/274,900
• Publication Number:
  US 20030145249A1
• Time in Patent Office: 1,372 Days
• Field of Search: 714/43, 370/217, 370/244
• US Class Current: 714/43
• 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 41/065 involving logical or physical relationship, e.g. grouping and hierarchies
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

The present invention provides method and system for identifying a faulty component in a group of components, the group comprising in a connected configuration at least a first component connected to a second component, and further connected to at least a third component. In an embodiment, the method comprises: (i) monitoring for at least one fault at a component connection interface; and (ii) upon detection of a fault, identifying the faulty component utilising information from the fault and at least one rule for identifying the faulty component. The rules are defined from at least one characteristic of the fault, such as location and frequency, and at least one characteristic of the configuration.

Claims

1. A method isolating the source of a fault detected in a group of interconnected components forming part of a communications network carrying data traffic, said method comprising:

(i) monitoring individual components of said group to detect errors in said data traffic;

(ii) reporting errors detected at each of said components to a common error administrator for said group of interconnected components;

(iii) maintaining a record of an error status of said components at said common error administrator; and

(iv) performing a rule-based analysis at said common error administrator based on an overall knowledge of the error status of the group of components to correlate error reports collected by said common error administrator so as to isolate the probable source of an error reported to said administrator by any one of said components;

wherein said error administrator classifies reported errors into related categories, and errors in different categories are correlated independently; and

wherein said categories are selected from the group consisting of;

datapath interface errors, control path interface errors, and connectivity errors.

2. The method of claim 1, wherein said error administrator maintains a record of demerit points for each of said components, and said error administrator assigns or removes demerit points for said components in accordance with the result of step (iv) as part of maintaining the record of the error status of said components.

3. The method of claim 1, wherein in response the receipt of a new error report from a particular component, said error administrator first determines whether said particular component, or another component supplying data traffic to said particular component, has already been identified as faulty, and if so said error administrator ignores said new error report.

4. The method of claim 1, wherein in response to the receipt of a new error report the error administrator enters a wait state for a predetermined period of time, and wherein said rule-based analysis is performed after the expiry of said predetermined period only if errors are still present.

5. The method of claim 1, wherein when a particular component reports a new error, said administrator determines whether said particular component is currently reporting more than one error, and in the event that said particular component is currently reporting more than one error, said error administrator identifies said particular component as the probable the source of the reported new error.

6. The method of claim 5, wherein if said particular component is not reporting more than one error, said error administrator determines whether another component supplying data traffic to said particular component has been identified as faulty, and if said another component has been identified as faulty, said error administrator identifies said another component as the probable source of said error for said particular component.

7. The method of claim 1, wherein said rule-based analysis utilizes component redundancy as a factor in isolating the probable source of the reported new error.

8. The method of claim 1, wherein said errors are detected at interfaces of said components.

9. A method isolating the source of a fault detected in a group of interconnected components forming part of a communications network carrying data traffic, said method comprising:

(i) monitoring interfaces of individual components of said group to detect errors in said data traffic;

(ii) reporting errors detected at each of said components to a common error administrator for said group of interconnected components;

(iii) maintaining a record of an error status of said components at said common error administrator; and

(iv) performing a rule-based analysis at said common error administrator based on an overall knowledge of the error status of the group of components so as to correlate error reports collected by said common error administrator to isolate the probable source of an error reported to said administrator by any one of said components; and

wherein said reported errors are selected from the group consisting of;

a parity error;

a loss of clock signal;

a frame misalignment;

a cell header check error;

a cell misalignment error; and

failure of a cell test diagnostic.

10. A system for isolating the source of a fault detected in a group of interconnected components forming part of a communications network carrying data traffic, said system comprising:

(i) a plurality of monitors for monitoring individual components forming part of said group for errors in said data traffic;

(ii) an error administrator receiving reports of errors detected by said monitors;

(iii) a storage medium for maintaining a record of the error status of said components at said error administrator; and

(iv) wherein said error administrator is configured to perform a rule-based analysis based on an overall knowledge of the error status of the group of components correlating error reports collected by said administrator so as to isolate the probable source of a new error reported to said administrator by any one of said components;

wherein said error administrator is configured to classify reported errors into related categories for correlation, and to correlate independently errors in different categories; and

wherein said categories are selected from the group consisting of;

datapath interface errors, control path interface errors, and connectivity errors.

11. The system of claim 10, wherein said error administrator is configured to maintain a record of demerit points for each of said components and to assign or remove demerit points for a said component identified as the probable source of said a said reported error.

12. The system of claim 10, wherein said error administrator is configured, in response to the receipt of a new error report from a particular component, to first determine whether said particular component, or another component supplying communications traffic to said particular component, have already been identified as faulty, and if so to ignore said new error report.

13. The system of claim 10, wherein in response to the receipt of a new error report the error administrator is configured to enter a wait state for a predetermined period of time and perform said rule-based analysis after the expiry of said predetermined period only if errors are still present.

14. The system of claim 10, wherein said error administrator is configured such that when a particular component reports a new error, said error administrator determines whether said particular component is currently reporting more than one error, and in the event that said particular component is currently reporting more than one error, said error administrator identifies said particular component as the probable the source of the reported new error.

15. The system of claim 14, wherein said error administrator is configured such that if said particular component is not reporting more than one error, said error administrator determines whether another component supplying communications traffic to said particular component has been identified as faulty, and if said another component has been identified as faulty, said error administrator identifies said another component as the source of said error for said particular component.

16. The system of claim 10, wherein said rule-based analysis utilizes component redundancy as a factor in isolating the probable source of the reported new error.