# US 2003/0204791 A1 · Rules-based configuration problem detection

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2003/0204791 A1
- Document ID: US20030204791A1
- Status: Published application
- Kind: A1
- Application number: 10/135,483
- Filed: 2002-04-30
- Published: 2003-10-30
- Earliest claimed: 2002-04-30
- Assignees: Sun Microsystems, Inc.
- Inventors: Matthew J. Helgren; Michael E. Little; Paris E. Bingham JR.; Rex G. Martin; Alan J. Treece
- Web page: https://patentgrep.com/patent/US20030204791A1

## CPC

- G06N 5/00: Computing arrangements using knowledge-based models
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS

## Abstract

A system and method for identifying problems with a system configuration may evaluate system configuration information against one or more configuration recommendations or rules. The evaluated system configuration may include various types of software and hardware components which may impact the operations of the computer system. Rules may be any information identifying an issue or describing a recommended configuration for the software or hardware component. A knowledge-based language or a programming language analyzer may be used to specify the rules. In one embodiment, a rules engine may be used as part of the problem detection application to evaluate configuration data against associated rules. A rules engine may be any mechanism used to recognize, interpret and process the configuration data against the rules. The results of the evaluation process may be stored for further analysis.

## Claims

### Claim 1

A system, comprising:
a processor;
a memory accessible by the processor and configured to store program instructions executable by the processor to implement a problem detection application, wherein the problem detection application comprises:
a rules engine configured to access configuration and rules data, wherein the configuration data comprises information about components configured for a computer system and the rules data comprises rules for identifying system configuration issues;
wherein the rules engine is configured to evaluate the rules from the rules data against the configuration data and generate a result of any configuration issues for the computer system.

### Claim 2 (depends on 1)

The system as recited in claim 1, wherein the configuration data comprises information about software components installed on the computer system.

### Claim 3 (depends on 1)

The system as recited in claim 1, wherein in the configuration data comprises information about hardware components installed in or connected to the computer system.

### Claim 4 (depends on 1)

The system as recited in claim 1, wherein the rules data comprises a rule to determine whether or not an unsupported device is connected to the computer system.

### Claim 5 (depends on 1)

The system as recited in claim 1, wherein the configuration issues comprise whether or not incorrect firmware is installed for a device attached to the computer system.

### Claim 6 (depends on 1)

The system as recited in claim 1, wherein the configuration issues identify if a newer version is available for a component installed on or connected to the computer system.

### Claim 7 (depends on 1)

The system as recited in claim 1, wherein the configuration issues identify known bugs for a component installed on or connected to the computer system.

### Claim 8 (depends on 1)

The system as recited in claim 1, wherein the configuration issues comprise whether or not a current operating system patch is installed on the computer system.

### Claim 9 (depends on 1)

The system as recited in claim 1, wherein the configuration issues comprise data affecting reliability, availability or serviceability for the computer system.

### Claim 10 (depends on 1)

The system as recited in claim 1, wherein the rules from the rules data are written in an interpreted rules language including operators and predicates for identifying the configuration issues, wherein the rules engine is configured to interpret the rules language.

### Claim 11 (depends on 1)

The system as recited in claim 1, wherein the rules engine is configured to access the configuration data from a configuration source stored on a storage device for the computer system.

### Claim 12 (depends on 1)

The system as recited in claim 1, wherein the problem detection application further comprises a configuration explorer to collect configuration data for the computer system.

### Claim 13 (depends on 1)

The system as recited in claim 1, wherein the problem detection application is configured to receive the configuration data over a network connection.

### Claim 14 (depends on 1)

The system as recited in claim 1, wherein the problem detection application is configured to receive a request to validate the computer system's configuration, wherein the request identifies a source for the configuration data and a source for the rules data.

### Claim 15 (depends on 1)

The system as recited in claim 1, wherein the wherein the rules data is stored on a storage device for the computer system.

### Claim 16 (depends on 15)

The system as recited in claim 15, wherein the rules data is configured to be updated over a network connection.

### Claim 17 (depends on 1)

The system as recited in claim 1, wherein the problem detection application further comprises a user interface configured to display the result generated by the rules engine.

### Claim 18 (depends on 1)

The system as recited in claim 1, wherein the problem detection application further comprises a user interface configured to request configuration data from a user.

### Claim 19 (depends on 18)

The system as recited in claim 18, wherein the rules engine is configured to evaluate configuration data against the rules while concurrently receiving and evaluating configuration data input through the user interface against the rules.

### Claim 20 (depends on 19)

The system as recited in claim 19, wherein one or more of the rules indicate configuration data to be requested from the user through the user interface.

### Claim 21 (depends on 1)

The system as recited in claim 1, wherein the problem detection application further comprises a user interface to update the rules data and rules engine.

### Claim 22

A method for identifying issues with a system configuration, comprising:
receiving a request to validate the system configuration, wherein the system configuration comprises components in a computer system;
receiving rules data comprising one or more rules for identifying issues in the system configuration;
receiving configuration data comprising information about the system configuration;
a rules engine evaluating the rules data against the configuration data to identify issues in the system configuration; and
generating a result of any issues identified in the system configuration.

### Claim 23 (depends on 22)

The method as recited in claim 22, wherein the configuration data comprises information about software components installed on the computer system.

### Claim 24 (depends on 22)

The method as recited in claim 22, wherein the configuration data comprises information about hardware components installed in or connected to the computer system.

### Claim 25 (depends on 22)

The method as recited in claim 22, wherein the rules data comprises a rule to determine whether or not an unsupported device is connected to the computer system.

### Claim 26 (depends on 22)

The method as recited in claim 22, wherein the rules data comprises a rule to determine whether or not incorrect firmware is installed for a device attached to the computer system.

### Claim 27 (depends on 22)

The method as recited in claim 22, wherein the rules data comprises a rule to identify if a newer version is available for a component installed on or connected to the computer system.

### Claim 28 (depends on 22)

The method as recited in claim 22, wherein the rules data comprises a rule to identify known bugs for a component installed on or connected to the computer system.

### Claim 29 (depends on 22)

The method as recited in claim 22, wherein the rules data comprises a rule to determine whether or not a current operating system patch is installed on the computer system.

### Claim 30 (depends on 22)

The method as recited in claim 22, wherein the rules data comprises a rule to identify an issue affecting reliability, availability or serviceability for the computer system.

### Claim 31 (depends on 22)

The method as recited in claim 22, wherein the rules from the rules data are written in an interpreted rules language including operators and predicates for identifying issues in the system configuration, wherein the rules engine evaluating the rules comprises the rules engine interpreting the rules according to the rules language.

### Claim 32 (depends on 22)

The method as recited in claim 22, wherein said receiving the configuration data comprises receiving the configuration data from a configuration source stored on a storage device for the computer system.

### Claim 33 (depends on 22)

The method as recited in claim 22, further comprising:
a configuration explorer collecting configuration information for the computer system;
wherein said receiving the configuration data comprises receiving the configuration information from the configuration explorer.

### Claim 34 (depends on 33)

The method as recited in claim 33, wherein said receiving the configuration data comprises receiving the configuration data over a network connection.

### Claim 35 (depends on 22)

The method as recited in claim 22, wherein the request to validate the system configuration identifies a source for the configuration data and a source for the rules data.

### Claim 36 (depends on 22)

The method as recited in claim 22, wherein said receiving rules data comprises receiving the rules data from a storage device for the computer system.

### Claim 37 (depends on 36)

The method as recited in claim 36, further comprising: updating the rules data over a network connection.

### Claim 38 (depends on 22)

The method as recited in claim 22, further comprising displaying, through a user interface, the result of any issues identified in the system configuration.

### Claim 39 (depends on 22)

The method as recited in claim 22, wherein one or more of the rules indicate a portion of the configuration data to be requested from a user through a user interface, the method further comprising:
requesting the indicated portion of the configuration data from the user through the user interface; and
the user interface receiving the indicated portion of the configuration data.

### Claim 40 (depends on 39)

The method as recited in claim 39, wherein said rules engine evaluating comprises the rules engine evaluating a portion of the configuration data not requested from the user against the rules data while waiting for the user interface to receive the portion of the configuration data indicated by one or more of the rules to be requested from the user.

### Claim 41 (depends on 22)

The method as recited in claim 22, further comprising receiving a request from a user interface to update the rules data and rules engine.
