System and Method for Determining Fault Isolation in an Enterprise Computing System

• US 20080133978A1
• Filed: 02/14/2008
• Published: 06/05/2008
• Est. Priority Date: 03/20/2003
• Status: Active Grant

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: Cox, Robert V., Heracleous, Stephanos S., Angamuthu, Karthikeyan
• Granted Patent: US 7,664,986 B2
• Time in Patent Office: Days
• US Class Current: 714/39
• CPC Class Codes: G06F 11/0727 in a storage system, e.g. in a DASD or network based storage system drivers for digital recording or reproducing units G06F3/06; circuits for error detection or correction within digital recording or reproducing units G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097
• 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/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/0645 by additionally acting on or stimulating the network after receiving notifications

Abstract

A system and method for determining fault isolation in an enterprise computing system is disclosed. A method includes automatically troubleshooting errors in an enterprise computing system that receives at an analyzer engine a status notification from a first component. In response to receiving the status notification, the method automatically selects a first analyzer policy file from a set of analyzer policy files based on the status notification received at the analyzer engine, wherein the analyzer policy file contains troubleshooting logic for determining root causes for errors. The method automatically attempts to communicate with a second component based on the troubleshooting logic within the first analyzer policy file. The method automatically determines a root cause for the status notification based on the troubleshooting logic in the selected analyzer policy file and based on information obtained in connection with the attempt to communicate with the second component.

Claims

1-20. -20. (canceled)

21. A method for automatically troubleshooting errors in a computing system, the method comprising:

receiving an error notification associated with the computing system;

automatically selecting an analyzer policy file for determining a cause of the received error notification;

wherein the selected analyzer policy file has a predefined protocol identifying a set of analyzer modules usable by the selected analyzer policy file for determining the cause of the error notification;

determining a configuration change to the computing system; and

in response to determining the configuration change to the computing system, automatically modifying the predefined protocol for the selected analyzer policy file to modify the set of analyzer modules usable by the selected analyzer policy file for determining a cause for a subsequent error notification.

22. The method of claim 21, wherein determining a configuration change to the computing system comprises detecting a new computer component or utility.

23. The method of claim 21, wherein automatically modifying the selected analyzer policy file comprises developing or reconfiguring the selected analyzer policy file.

24. The method of claim 21, further comprising:

receiving the error notification from a first component of the computing system;

automatically attempting to communicate with a second component of the computing system based on troubleshooting logic within the selected analyzer policy file; and

automatically determining a cause for the error notification based on the troubleshooting logic in the selected analyzer policy file and based on information obtained in connection with the attempt to communicate with the second component of the computing system.

25. The method of claim 21, wherein the error notification comprises simple network management protocol (SNMP) traps.

26. The method of claim 21, wherein the error notification comprises network (NT) events.

27. The method of claim 21, further comprising providing output for a user that identifies the cause of the error notification.

28. The method of claim 21, further comprising, in response to determining the cause for the error notification, identifying corrective steps for the computing system.

29. A fault isolation troubleshooting system for use in a computing system, comprising:

a plurality of analyzer policy files, each analyzer policy file including troubleshooting logic for determining causes of errors associated with the computing system;

an analyzer engine operable to receive an error notification, select the analyzer policy file based on the received error notification, and use the troubleshooting logic of the selected analyzer policy file to identify the cause of the error notification; and

an updating engine operable to determine a configuration change to the computing system, and in response to determining the configuration change to the computing system, automatically modify the troubleshooting logic of the selected analyzer policy file.

30. The system of claim 29, wherein determining a configuration change to the computing system comprises detecting a new computer component or utility.

31. The system of claim 29, wherein:

the selected analyzer policy file has a predefined protocol identifying a set of analyzer modules usable by the selected analyzer policy file for determining a cause of an error notification; and

automatically modifying the troubleshooting logic of the selected analyzer policy file comprises modifying the set of analyzer modules usable by the selected analyzer policy file for determining a cause of an error notification.

32. The system of claim 29, wherein the error notification comprises simple network management protocol (SNMP) traps.

33. The system of claim 29, wherein the error notification comprises network (NT) events.

34. The system of claim 29, further comprising a user interface for providing output to a user that identifies the cause of the error notification.

35. The system of claim 29, wherein the analyzer engine is further operable to identifying corrective steps for the computing system regarding the identified cause of the error notification.

36. A method for automatically troubleshooting errors in a computing system, the method comprising:

receiving a first error notification associated with the computing system;

from a plurality of analyzer policy files for determining causes of error notifications, automatically selecting a first analyzer policy file based at least on the received first error notification, the first analyzer policy file having a predefined protocol identifying a first set of analyzer modules usable by the first analyzer policy file for determining the cause of the first error notification;

automatically determining a cause for the first error notification using the first set of analyzer modules associated with the first analyzer policy file;

receiving a second error notification associated with the computing system;

from the plurality of analyzer policy files for determining causes of error notifications, automatically selecting a second analyzer policy file based at least on the received second error notification, the second analyzer policy file having a predefined protocol identifying a second set of analyzer modules usable by the second analyzer policy file for determining the cause of the second error notification, second set of analyzer modules having at least one different analyzer module than the first set of analyzer modules; and

automatically determining a cause for the second error notification using the second set of analyzer modules associated with the second analyzer policy file.

37. The method of claim 36, further comprising:

determining a configuration change to the computing system; and

in response to determining the configuration change to the computing system, automatically modifying the predefined protocol for at least one of the first and second analyzer policy files to modify the set of analyzer modules usable by at least one of the first and second analyzer policy files for determining a cause for a subsequent error notification.

38. The method of claim 37, wherein determining a configuration change to the computing system comprises detecting a new computer component or utility.