Computer assisted automatic error detection and diagnosis of file servers

• US 6,883,120 B1
• Filed: 12/03/1999
• Issued: 04/19/2005
• Est. Priority Date: 12/03/1999
• Status: Expired due to Fees

• Current Assignee: NetApp, Inc.
• Original Assignee: Network Appliance Incorporated (NetApp, Inc.)
• Inventors: Banga, Gaurav
• Primary Examiner(s): Beausoliel, Robert
• Assistant Examiner(s): Chu, Gabriel L.
• Application Number:
  US09/456,027
• Time in Patent Office: 1,964 Days
• Field of Search: 714/3, 714/4, 714/19, 714/20, 714/25, 714/26, 714/37, 714/47
• US Class Current: 714/47.1
• 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/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• 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: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3051 Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs verification or detection of system hardware configuration G06F11/2247
• CPC Class Codes: H04L 41/142 using statistical or mathematical methods

Abstract

A method and system for computer assisted automatic error detection and diagnosis of file servers. Software modules periodically and continuously review monitoring statistics gathered by the file server regarding its operation. The monitoring statistics are processed by a pattern matching system and a rule-based inference system. Software modules augment known network protocols, by manipulating parameters of lower-level protocols using different higher-level protocols. Using the higher-level protocols, software modules determine if the selected parameters for the lower-level protocols are correct. Software modules track hardware and software configuration changes to the file server, and relate changes in known monitoring statistics to timing of those hardware and software configuration changes.

Claims

1. A method, including steps of

repeatedly reviewing monitoring statistics regarding operation of a file server, said steps of reviewing being performed at least as often as a selected time period;

and

processing said monitoring statistics using a diagnostic software module on said file server, in response to said steps of repeatedly reviewing;

wherein said diagnostic software module diagnoses a behavior of said file server to determine a specific problem or problems by comparing said monitoring statistics to rules or patterns representing abnormal states of operation for said file server; and

wherein said monitoring statistics include information gathered by at least first and second software modules, said first and second software modules being disposed at differing protocol levels within an operating system of said file server.

2. A method as in claim 1, wherein said diagnostic software module includes a pattern matching system and a rule-based inference system.

3. A method as in claim 1, wherein said monitoring statistics include information gathered by at least one software module within an operating system of said file server.

4. A method as in claim 1, wherein said selected time period is less than 10 seconds.

5. A method as in claim 1, wherein said steps of processing are responsive to a usage profile for said file server.

6. A method as in claim 5, wherein said usage profile includes information regarding whether use of said file server includes usage as an ISP, a development environment, or a mail server.

7. A method as in claim 1, further including steps of

selecting parameters for said differing protocol levels;

using said diagnostic software module to determine a measure of efficiency for said file server using a higher one of said differing protocol levels; and

selecting new parameters for a lower one of said differing protocol levels in response to said measure of efficiency.

8. A method, including steps of

tracking configuration changes to a file server;

maintaining monitoring statistics for said file server;

identifying a relationship between changes in said monitoring statistics for said file server and timing of said configuration changes;

identifying possible errors or other faults for said server associated with relating said changes in said monitoring statistics to timing of said configuration changes;

determining, in response to said relationship between said changes in monitoring statistics and said timing of configuration changes, which of said possible errors or other faults is most likely; and

identifying, in response to which of said possible errors or other faults is most likely, one or more of said configuration changes.

9. A method as in claim 8, including steps of suggesting activities to reverse said configuration changes so as to place said file server in an operating state.

10. A method as in claim 8, wherein said configuration changes include hardware and software configuration changes.

11. A file server comprising:

an interface to a network;

mass storage accessible through said interface;

a processor that controls access to said mass storage; and

a memory that stores information including instructions executable by said processor, said instructions including steps of (a) repeatedly reviewing monitoring statistics regarding operation of said file server, said steps of reviewing being performed at least as often as a selected time period, and (b) processing said monitoring statistics using a diagnostic software module on said file server, in response to said steps of repeatedly reviewing;

wherein said diagnostic software module diagnoses a behavior of said file server to determine a specific problem or problems by comparing said monitoring statistics to rules or patterns representing abnormal states of operation for said file server; and

wherein said monitoring statistics include information gathered by at least first and second software modules, said first and second software modules being disposed at differing protocol levels within an operating system of said file server.

12. A file server as in claim 11, wherein said diagnostic software module includes a pattern matching system and a rule-based inference system.

13. A file server as in claim 11, wherein said monitoring statistics include information gathered by at least one software module within an operating system of said file server.

14. A file server as in claim 11, wherein said selected time period is less than 10 seconds.

15. A file server as in claim 11, wherein said steps of processing are responsive to a usage profile for said file server.

16. A file server as in claim 15, wherein said usage profile includes information regarding whether use of said file server includes usage as an ISP, a development environment, or a mail server.

17. A file server as in claim 11, said instructions further comprising steps of:

(c) selecting parameters for said differing protocol levels;

(d) using said diagnostic software module to determine a measure of efficiency for said file server using a higher one of said differing protocols levels; and

(e) selecting new parameters for a lower one of said differing protocol levels in response to said measure of efficiency.

18. A file server comprising:

an interface to a network;

mass storage accessible through said interface;

a processor that controls access to said mass storage; and

a memory that stores information including instructions executable by said processor, said instructions including steps of (a) tracking configuration changes to said file server, (b) maintaining monitoring statistics for said file server, (c) identifying a relationship between changes in said monitoring statistics for said file server and timing of said configuration changes, (d) identifying possible errors or other faults for said server associated with said changes in said monitoring statistics, (e) determining, in response to said relationship between said changes in monitoring statistics and said timing of configuration changes, which of said possible errors or other faults is most likely, and (f) identifying, in response to which of said possible errors or other faults is most likely, one or more of said configuration changes.

19. A file server as in claim 18, wherein said instructions further include steps of suggesting activities to reverse said configuration changes so as to place said file server in an operating state.

20. A file server as in claim 18, wherein said configuration changes include hardware and software configuration changes.

21. A memory storing information including instructions, the instructions executable by a processor to control a file server, the instructions including steps of

repeatedly reviewing monitoring statistics regarding operation of said file server, said steps of reviewing being performed at least as often as a selected time period;

and

processing said monitoring statistics using a diagnostic software module on said file server, in response to said steps of repeatedly reviewing;

wherein said diagnostic software module diagnoses a behavior of said file server to determine a specific problem or problems by comparing said monitoring statistics to rules or patterns representing abnormal states of operation for said file server; and

wherein said monitoring statistics include information gathered by at least first and second software modules, said first and second software modules being disposed at differing protocol levels within an operating system of said file server.

22. A memory as in claim 21, wherein said diagnostic software module includes a pattern matching system and a rule-based inference system.

23. A memory as in claim 21, wherein said monitoring statistics include information gathered by at least one software module within an operating system of said file server.

24. A memory as in claim 21, wherein said selected time period is less than 10 seconds.

25. A memory as in claim 21, wherein said steps of processing are responsive to a usage profile for said file server.

26. A memory as in claim 25, wherein said usage profile includes information regarding whether use of said file server includes usage as an ISP, a development environment, or a mail server.

27. A memory as in claim 21, the instructions further including steps of:

selecting parameters for said differing protocol levels;

using said diagnostic software module to determine a measure of efficiency for said file server using a higher one of said differing protocol levels; and

selecting new parameters for a lower one of said differing protocol levels in response to said measure of efficiency.

28. A memory storing information including instructions, the instructions executable by a processor to control a file server, the instructions including steps of

tracking configuration changes to a file server;

maintaining monitoring statistics for said file server;

identifying a relationship between changes in said monitoring statistics for said file server and timing of said configuration changes;

identifying possible errors or other faults for said server associated with said changes in said monitoring statistics;

determining in response to said relationship between said changes in monitoring statistics and said timing of configuration changes, which of said possible errors or other faults is most likely; and

identifying, in response to which of said possible errors or other faults is most likely, one or more of said configuration changes.

29. A memory as in claim 28, wherein said instructions further include steps of suggesting activities to reverse said configuration changes so as to place said file server in an operating state.

30. A memory as in claim 28, wherein said configuration changes include hardware and software configuration changes.