Knowledge based resource management

• US 5,568,491 A
• Filed: 04/20/1994
• Issued: 10/22/1996
• Est. Priority Date: 05/03/1991
• Status: Expired due to Fees

• Current Assignee: Storage Technology Corp (Oracle Corporation)
• Original Assignee: Storage Technology Corp (Oracle Corporation)
• Inventors: Stephens, Michael R., Hill, Fletcher L., Chikira, Joetta S., Beal, David G., Jurestovsky, Nancy R.
• Primary Examiner(s): Baker, Stephen M.
• Application Number:
  US08/230,329
• Time in Patent Office: 916 Days
• Field of Search: 371/15.1, 371/20.1, 395/183.02, 395/182.02
• US Class Current: 714/746
• CPC Class Codes: G05B 13/028 using expert systems only
• CPC Class Codes: G05B 23/0229 knowledge based, e.g. expert systems; genetic algorithms
• 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/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/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: G06F 11/2035 without idle spare hardware
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2205 using arrangements specific to the hardware being tested
• CPC Class Codes: G06F 11/2257 using expert systems

Abstract

The knowledge based system identifies the occurrence of a failure within the customer equipment and functions using its rules, hypotheses and collected data to isolate the functional resource which is the source of the error in the customer equipment and, whenever possible, "fence" or isolate the failed functional resource that has caused the error. In addition, the knowledge based system makes use of resource related rules to remove a resource or set of resources available for concurrent other failure management operations. The resource related rules allow resources to function in any one non-operational or operational mode or to functional simultaneously in multiple non-operational modes.

Claims

1. Apparatus for controllably isolating operational elements in a customer system, which customer system includes a plurality of operational elements, each interconnected to at least one other operational element via an interconnection path, comprising:

means for storing data identifying all said operational elements and said interconnection paths;

means for retrieving a portion of said data from said storing means to identify a subset of said operational elements and all said interconnection paths connected to said subset of operational elements;

means for identifying a selected subset of operational elements for testing;

means for verifying that said subset of operational elements is not in use;

means, responsive to said subset of operational elements not being in use, for identifying all said interconnection paths connected to said subset of operational elements;

means for writing data identifying said subset of operational elements and said identified interconnection paths connected to said subset of operational elements into said retrieving means to disable said identified subset of operational elements;

means for selectively disabling the use of said subset of operational elements, as identified by said retrieving means, by said customer system, comprising;

means for isolating said subset of operational elements by disabling any said interconnection paths connected to said subset of operational elements,

means for listing at least one fence mode operational on said subset of operational element in said portion of said data in said retrieving means to identify a mode in which said subset of operational elements is disabled,

means, responsive to said apparatus requesting application of a fence mode to one of said subset of operational elements for comparing said requested fence process with said at least one fence mode listed with said portion of said data,

means, responsive to said comparing means matching said requested fence mode with one of said listed modes, for accepting application of said requested fence to said mode requested operational element.

2. The apparatus of claim 1 further comprising:

means for detecting the presence of a failure in said associated customer system;

means for generating a failure report which contains data relevant to said detected failure, including an identification of the failure mode and all operational elements that were cooperatively operative during said detected failure;

means for storing said failure report;

means for maintaining a failure analysis history containing data identifying each of said operational elements and associated composite failure data representative of known operational element failures;

means for comparing said stored failure report with said failure analysis history, including;

means for generating a list of said operational elements which are common to a plurality of said failure reports,

means for mapping said identified failed operational elements to at least one field replaceable unit containing said listed failed operational elements;

means for identifying at least one failed operational element based on said comparison;

means, responsive to said identifying means, for writing data into a memory to identify said at least one failed operational element and said interconnection paths connected to said identified failed operational element.

3. A method for controllably isolating operational elements in a customer system, which customer system includes a plurality of operational elements, each interconnected to at least one other operational element via an interconnection path, comprising the steps of:

storing data in a memory identifying all said operational elements and interconnection paths;

retrieving a portion of said data from said memory to identify a subset of said operational elements and all said interconnection paths connected to said subset of operational elements;

identifying a selected subset of operational elements for testing;

verifying that said subset of operational elements is not in use;

identifying, in response to said subset of operational elements not being in use, all said interconnection paths connected to said subset of operational elements;

writing data identifying said subset of operational elements and said identified interconnection paths connected to said subset of operational elements into said memory to disable said identified subset of operational elements;

selectively disabling the use of said subset of operational elements, as identified by said memory, by said customer system, comprising;

isolating said subset of operational elements by disabling all said interconnection paths connected to said subset of operational elements,

listing at least one fence mode operational on said subset of operational element in said portion of said data in said memory to identify a mode in which said subset of operational elements is disabled,

comparing, in response to said apparatus requesting application of a fence mode to one of said subset of operational elements, said requested fence mode with said at least one fence mode listed with said portion of said data,

accepting, in response to said comparing means matching said requested fence mode with one of said listed modes, application of said requested fence mode to said requested operational element.

4. The method of claim 3 further comprising the steps of:

detecting the presence of a failure in said associated customer system;

generating a failure report which contains data relevant to said detected failure, including an identification of the failure mode and all operational elements that were cooperatively operative during said detected failure;

storing said failure report;

maintaining a failure analysis history containing data identifying each of said operational elements and associated composite failure data representative of known operational element failures;

comparing said stored failure report with said failure analysis history, including;

generating a list of said operational elements which are common to a plurality of said failure reports,

mapping said identified failed operational element to at least one field replaceable unit containing said listed failed operational elements;

identifying at least one failed operational element based on said comparison;

writing, in response to said identifying means, data into said memory to identify said at least one failed operational element and said interconnection paths connected to said identified failed operational element.