Method and system for managing failure information

• US 7,493,525 B2
• Filed: 09/21/2005
• Issued: 02/17/2009
• Est. Priority Date: 09/21/2005
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Schaefer, Carl, Wigley, Lane Cameron
• Primary Examiner(s): Lohn; Joshua A
• Application Number:
  US11/232,756
• Publication Number:
  US 20070067675A1
• Time in Patent Office: 1,245 Days
• Field of Search: 714/18, 714/19, 714/26, 714/37, 714/45, 714/57, 702/187
• US Class Current: 714/45
• CPC Class Codes: G06F 11/0748 in a remote unit communicating with a single-box computer node experiencing an error/fault remote testing G06F11/2294
• CPC Class Codes: G06F 11/0787 Storage of error reports, e.g. persistent data storage, storage using memory protection
• CPC Class Codes: G06F 11/273 Tester hardware, i.e. output processing circuits G06F11/263 takes precedence
• 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/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/16 Threshold monitoring

Abstract

A method, system and apparatus for managing data pertaining to the failure of a network device are provided. The data is stored in a memory, and access to the stored data is provided. The memory is a non-volatile memory. Access is provided to a failure analysis team, which uses the data to analyze the causes of the failure of the network device.

Claims

1. A method for managing data pertaining to a failure of a network device, the method comprising:

collecting the data for storage in a non-volatile memory of the network device, the data being collected in a boot log record, a runtime log record, a failure event data portion, and an environmental data portion;

storing the boot log record, wherein the boot log record pertains to a boot history of the network device;

storing the failure event data and the environmental data portions, wherein the failure event data portion indicates a hardware failure of the network device, and wherein the environmental data portion includes environmental information pertaining to the network device;

storing the runtime log record when the network device is restarted, wherein the runtime log record pertains to an operational history of the network device; and

providing access to the data stored in the non-volatile memory.

2. The method of claim 1, further comprising compressing the data for the storage in the non-volatile memory.

3. The method of claim 1,

further comprising storing data pertaining to a crash of the network device when the network device is restarted due to the crash.

4. The method of claim 1, wherein the failure event data portion further comprises data pertaining to a connectivity failure of hardware of the network device.

5. The method of claim 1, wherein the failure event data portion further includes a time of the failure of the network device.

6. The method of claim 1, further comprising consolidating the data based on free space available in the non-volatile memory.

7. The method of claim 6, wherein the consolidating the data comprises deleting obsolete data stored in the non-volatile memory.

8. The method of claim 6, wherein the consolidating the data comprises replacing the data stored in the non-volatile memory with new data having a time of failure later than the time of failure of the data stored in the non-volatile memory.

9. The method of claim 6, wherein the consolidating the data comprises grouping the data based on a type of the failure.

10. The method of claim 1, wherein the providing access to the data comprises providing a command line interface (CLI) for analyzing the cause of failure of the network device.

11. The method of claim 1, wherein the non-volatile memory is embedded on a component of the network device, the component being selected from a group consisting of router processors, line cards, fabric cards, fan modules and power supplies.

12. A system for managing data pertaining to a failure of a network device, the system comprising:

means for collecting the data for storage in a non-volatile memory of the network device, the data being collected in a boot log record, a runtime log record, a failure event data portion, and an environmental data portion;

means for storing the boot log record, wherein the boot log record pertains to a boot history of the network device;

means for storing the failure event data and the environmental data portions, wherein the failure event data portion indicates a hardware failure of the network device, and wherein the environmental data portion includes environmental information pertaining to the network device;

means for storing the runtime log record when the network device is restarted, wherein the runtime log record pertains to an operational history of the network device; and

means for providing access to the data stored in the non-volatile memory.

13. The system of claim 12, further comprising means for consolidating the data in the non-volatile memory based on free space available in the non-volatile memory.

14. The system of claim 12, wherein the means for providing the access comprises providing a command line interface (CLI).

15. The system of claim 12, further comprising means for storing data pertaining to a crash of the network device when the network device is restarted due to the crash.

16. A system for managing data pertaining to a failure of a network device, the system comprising:

a non-volatile memory of the network device for storing the data;

a programmatic interface for accessing the data; and

a data manager for facilitating storing of the data in the non-volatile memory, wherein the data manager is operable to;

collect the data for storage in a non-volatile memory of the network device, the data being collected in a boot log record, a runtime log record, a failure event data portion, and an environmental data portion;

store the boot log record, wherein the boot log record pertains to a boot history of the network device;

store the failure event data and the environmental data portions, wherein the failure event data portion indicates a hardware failure of the network device, and wherein the environmental data portion includes environmental information pertaining to the network device; and

store the runtime log record when the network device is restarted, wherein the runtime log record pertains to an operational history of the network device.

17. The system of claim 16, wherein the data manager is further operable to consolidate the data in the non-volatile memory based on free space available in the non-volatile memory.

18. The system of claim 17, wherein the data consolidation comprises a replacement of the data stored in the non-volatile memory with new data having a time of failure later than the time of failure of the data stored in the non-volatile memory.

19. The system of claim 16, wherein the programmatic interface comprises a command line interface (CLI).

20. The system of claim 16, wherein the data manager is further operable to store data pertaining to a crash of the network device when the network device is restarted due to the crash.