WO2008007442A1

WO2008007442A1 - System management program, system management device and system management method

Info

Publication number: WO2008007442A1
Application number: PCT/JP2006/314107
Authority: WO
Inventors: Masazumi Matsubara; Keiichi Oguro; Kuniaki Shimada
Original assignee: Fujitsu Limited
Priority date: 2006-07-14
Filing date: 2006-07-14
Publication date: 2008-01-17

Abstract

A subject matter is directed to a system management program, etc. that specify a symptom and autonomously perform processing to decide its measures in the case that a trouble occurs in a subject managed device, etc., wherein its problem to be solved is to easily register information for specifying the symptom not only by type but also by designating an individually managed subject. In order to solve this problem, items are provided to set up an applicable classification and a sort in a symptom database which is one for registering information to specify a symptoms of a managed subject, so that, in addition to designating “ a type” in the item of classification and setting a name to represent a sort of an applicable subject in the item of name, designating “an instance” in the item of classification and setting a name to represent an individually managed subject in the item of name can be set.

Description

Specification

System management program, system management apparatus, and system management method

[0001] The present invention relates to a system management program, a system management apparatus, and a system management method for identifying a symptom of a problem occurring in a management target and determining a countermeasure for solving the symptom. The present invention relates to a system management program, a system management apparatus, and a system management method that can be easily registered by specifying individual management targets, not just by type.

Background art

[0002] Conventionally, when a problem occurs in an information processing system, measures have been taken based on the know-how possessed by the person in charge such as a system administrator. These know-hows were often accumulated by each person in charge based on experience dealing with individual issues, and were often not shared well. As a result, the level of response to disabilities could vary greatly depending on the person in charge.

[0003] In order to eliminate such dependence on personal skills and to speed up and homogenize the handling of problems, standardize know-how related to various problems that occur in information systems and register them in the database. In addition, a technology has been proposed that uses this database to identify the symptoms of a problem and determine the corrective action corresponding to the specific symptoms.

[0004] For example, Patent Document 1 discloses a technique for automatically discovering a performance degradation problem in a network system, identifying the cause, and notifying the system administrator of the countermeasure. Non-Patent Document 1 discloses a technique in which an autonomous manager refers to a problem solving database and solves problems autonomously when a problem occurs.

Patent Document 1: Japanese Patent Application Laid-Open No. 2004-145536

Non-Patent Literature 1: An architectural blueprint for autonomic computing., [Online], IBM Corporation, [Search June 30, 2006], Internet URL: http: 〃 www- 03.ibm.com/autonomic/pdfs/ AC% 20Blueprint% 20White% 20Paper% 20V7.pdf> Disclosure of Invention Problems to be solved by the invention

[0006] However, the technology disclosed in Non-Patent Document 1 described above is a symptom to be managed only for each resource type, that is, in general units such as server devices in general and applications in general. It was not possible to specify the conditions for identifying the symptom, and it was not possible to set specific conditions for identifying the symptoms individually for each server device or service.

[0007] On the other hand, in the technique disclosed in Patent Document 1 described above, by adding a constraint such as “a server device under the control of a load balancer”, a condition for specifying a symptom by limiting a target is specified. Can be specified. This is made possible by having configuration information about the managed objects. However, in this way, the method that combines the conditions for identifying the symptoms and the constraints that limit the target has a problem that the setting contents are complicated and setting errors are likely to occur.

[0008] The present invention has been made in view of the above, and is a system capable of easily registering information for specifying a symptom by specifying an individual management target that is not limited to a unit of type. It is an object to provide a management program, a system management apparatus, and a system management method.

Means for solving the problem

[0009] In order to solve the above-described problems and achieve the object, in one aspect of the present invention, a symptom of a problem occurring in a management target is specified, and a countermeasure for solving the symptom is determined. A system management program for acquiring information indicating the status of the management target and information acquired by the information acquisition procedure for each entry as an individual management target or management target type A symptom identification procedure for identifying a symptom occurring in the management target by collating with a symptom database in which a symptom that may occur in the application target and a condition for determining the symptom are registered, and the symptom The symptom identified by the specific procedure is collated with the countermeasure database in which the symptom that may occur in the management target is associated with the countermeasure for solving the symptom. By Rukoto, characterized in that to execute the countermeasure decision procedure for determining the countermeasure for eliminating the symptoms occurring in the management target computer. [0010] Further, in another aspect of the present invention, there is provided a system management device that identifies a symptom of a problem occurring in a management target and determines a countermeasure for solving the symptom, wherein the management target Information acquisition means for acquiring information indicating the situation, and information acquired by the information acquisition means can be generated in the application target by applying individual management targets or types of management targets for each entry. The symptom identifying means for identifying the symptom occurring in the management target by collating with the symptom database in which the symptom and the judgment condition of the symptom are registered, and the symptom identified by the symptom identifying means, Symptoms occurring in the management target by collating with a countermeasure database in which symptoms that may occur in the management target and countermeasures for solving the symptoms are registered in association with each other Characterized in that a countermeasure determining unit for determining a countermeasure for order to overcome.

[0011] Further, in another aspect of the present invention, there is provided a system management method for identifying a symptom of a problem occurring in a management target and determining a countermeasure for eliminating the symptom. An information acquisition process for acquiring information indicating a situation, and the information acquired by the information acquisition process may be generated in the application target by applying an individual management target or a type of management target for each entry. A symptom identifying step for identifying a symptom occurring in the management target by collating with a symptom database in which a symptom and a condition for determining the symptom are registered, and the symptom identified by the symptom identifying step are Symptoms occurring in the management target by collating with a countermeasure database in which symptoms that may occur in the management target and countermeasures for solving the symptoms are registered in association with each other That contains a countermeasure determining step of determining a countermeasure for order to eliminate characterized.

[0012] According to the aspect of the present invention, in the symptom database in which information for identifying the symptom of the problem occurring in the management target is registered, whether the individual management target is to be applied for each entry. Or, because it is configured to be able to set whether to apply all management targets of the same type, it is easy to specify information for identifying symptoms by specifying individual management targets rather than by type. can do.

[0013] Further, in another aspect of the present invention, since the information acquired by the information acquisition procedure is insufficient according to the aspect of the invention described above, the information is referred to the symptom database. Even if combined, the symptom identification procedure identifies the symptom occurring in the management target. If this is not possible, the computer is further caused to execute an information supplement procedure for acquiring the information to be managed, which is insufficient.

[0014] In another aspect of the present invention, in the above aspect of the invention, since the information acquired by the information acquisition unit is insufficient, the information is compared with the symptom database. In this case, the symptom specifying means further comprises an information complementing means for acquiring information that is insufficient from the management target if the symptom occurring in the management target cannot be specified. Features.

[0015] According to this aspect of the present invention, when the symptom occurring in the management target cannot be specified only by the information acquired by the notification event or the like, the information necessary for the specification is actively acquired and complemented. Even if there is a small amount of information acquired by notification events, etc., it is possible to narrow down the symptoms that actually occur and determine appropriate countermeasures.

[0016] Further, in another aspect of the present invention, in the above aspect of the invention, the symptom specifying procedure lacks information acquired by the information acquiring procedure. If the symptom occurring in the managed object cannot be identified even after checking with the symptom database, the information related to the configuration of the managed object is insufficient with reference to the registered configuration management database. An information acquisition destination is specified, and the acquisition destination is specified to acquire information lacking in the information supplement procedure.

[0017] Further, in another aspect of the present invention, in the above aspect of the invention, the symptom specifying unit lacks information acquired by the information acquiring unit, and therefore the information is stored in the symptom database. If the symptom occurring in the management target cannot be identified even after collation, refer to the configuration management database in which information related to the configuration of the management target is registered, and obtain the missing information. A destination is specified, the acquisition destination is specified, and the information complementing means is made to acquire the missing information.

[0018] According to this aspect of the present invention, since the configuration is such that it is obtained by autonomously determining the acquisition destination of the information that is insufficient with reference to the configuration information, the content to be registered in the symptom database is stored. It can be simplified.

[0019] Further, in another aspect of the present invention, in the above aspect of the invention, the countermeasure determining procedure is as follows. Is a countermeasure that satisfies the application condition registered in association with the countermeasure when the countermeasure database includes a plurality of countermeasures corresponding to the symptom identified by the symptom identification procedure. Is determined as a countermeasure for resolving the symptom occurring in the management target.

[0020] According to this aspect of the present invention, in the countermeasure database, a plurality of countermeasures and their application conditions are registered for one symptom, and a countermeasure that satisfies the application conditions is selected. Therefore, it is possible to select an appropriate countermeasure according to the situation.

[0021] Further, in another aspect of the present invention, in the above aspect of the invention, the information complementing procedure is for determining whether or not the application condition registered in association with the countermeasure is satisfied. If the necessary information is insufficient, the information is acquired from the management target.

[0022] According to this aspect of the present invention, when a countermeasure cannot be selected only by information acquired by a notification event or the like, information necessary for selection is actively acquired and supplemented. Appropriate countermeasures can be determined even if only a small amount of information is acquired through notification events.

[0023] In another aspect of the present invention, in the above aspect of the invention, the countermeasure determining procedure determines whether or not an application condition registered in association with the countermeasure is satisfied. If there is not enough information required to identify the information to be acquired! It is characterized by having it acquired.

[0024] According to the aspect of the present invention, since the configuration is such that the acquisition destination of the information that is lacking with reference to the configuration information is autonomously determined and acquired, the content registered in the countermeasure database Can be simplified.

The invention's effect

[0025] According to one aspect of the present invention, in a symptom database in which information for specifying a symptom of a problem occurring in a management target is registered, an individual management target is set as an application target for each entry. Or all the management targets of the same type can be set as the application target. Therefore, it is possible to easily register by specifying individual management targets.

[0026] Further, according to another aspect of the present invention, only information acquired by a notification event or the like occurs in a management target! I can't identify the symptoms! In this case, it is configured to actively acquire and supplement the information necessary for specific identification, so even if there is only a small amount of information acquired by a notification event, etc., the symptoms that are actually occurring are narrowed down correctly. If you can decide on an appropriate countermeasure, it will be effective!

[0027] Further, according to another aspect of the present invention, since it is configured to autonomously determine and acquire the acquisition source of the missing information with reference to the configuration information, it is registered in the symptom database. There is an effect that can be simplified.

[0028] Further, according to another aspect of the present invention, in the countermeasure database, a plurality of countermeasures and their application conditions are registered for one symptom, and a countermeasure that satisfies the application conditions is selected. Thus, when an appropriate countermeasure can be selected according to the situation, it is effective.

[0029] Further, according to another aspect of the present invention, when a countermeasure cannot be selected only by information acquired by a notification event or the like, information necessary for selection is actively acquired and complemented. As a result, even if the information acquired by the notification event or the like is small, it is possible to determine an appropriate countermeasure.

[0030] Further, according to another aspect of the present invention, the configuration database is configured to autonomously determine and acquire the information acquisition destination that is insufficient with reference to the configuration information. There is an effect that the contents to be registered in can be simplified.

Brief Description of Drawings

FIG. 1 is a diagram illustrating an example of an information processing system to which a system management method according to the present embodiment is applied.

FIG. 2 is a functional block diagram showing a configuration of the system management apparatus shown in FIG.

FIG. 3 is a diagram showing an example of a symptom database.

[FIG. 4] FIG. 4 is a diagram showing an example of a countermeasure database.

FIG. 5 is a diagram showing an example of a performance requirement database. FIG. 6 is a diagram showing an example of a configuration management database.

[Fig. 7-1] Fig. 7-1 shows an example of a notification event.

[FIG. 7-2] FIG. 7-2 is a diagram showing another example of the notification event.

[FIG. 7-3] FIG. 7-3 is a diagram showing another example of the notification event.

FIG. 8 is a flowchart showing a processing procedure of the system management apparatus.

[FIG. 9] FIG. 9 is a flowchart showing a processing procedure of countermeasure execution processing.

FIG. 10 is a functional block diagram illustrating a computer that executes a system management program.

Explanation of symbols

10 network

20 server punore

100 System management unit

110 '1 B' | 5

111 Symptom Database

112 Solution database

113 Performance requirement database

114 Configuration management database

120 Control unit

121 Information Acquisition Department

122 Symptom identification part

123 Countermeasure decision section

124 Countermeasure execution part

125 Information Completion Department

126 Configuration information update part

201-, 206, 301-303

1000 computers

1010 CPU

1020 Input device 1030 monitor

1040 Media reader

1050 Network interface device

1060 RAM

1061 System management process

1070 Hard disk device

1071 System management program

1072 System management data

1080 pass

BEST MODE FOR CARRYING OUT THE INVENTION

Hereinafter, embodiments of a system management program, a system management apparatus, and a system management method according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

Example

First, an example of an information processing system to which the system management method according to the present embodiment is applied will be described. FIG. 1 is a diagram illustrating an example of an information processing system to which the system management method according to the present embodiment is applied.

[0035] The information processing system shown in the figure is configured by connecting a system management device 100, server devices 201 to 206, and server devices 301 to 303 via a network 10 such as 1 ^^ 00 & 1 Area Network). ing.

The system management device 100 is a device that executes the system management method according to the present embodiment. The system management device 100 monitors the server devices 201 to 206 and the server devices 301 to 303, and when a problem occurs in these devices or the services executed therein, the system management device 100 refers to the database provided by itself, Once you identify the symptoms, decide what to do about the identified symptoms, and take action!ヽぅ A series of processing is executed autonomously.

Server apparatuses 201 to 206 are server apparatuses that execute assigned predetermined services. In this example, server apparatuses 201 and 202 execute business A service, server apparatus 203 executes business B service, and server apparatuses 204 to 206 execute business C service. Is doing.

The server devices 301 to 303 are server devices to which no specific service is assigned, and belong to the server pool 20. The server pool means a set of server devices whose usage is not specified and can be used as needed.

[0039] The system management device 100 has some problem in any of the server devices 201 to 206, and needs to cope with the service assigned to the server device being executed by the other server device. If it is determined, one of the server devices belonging to the server pool 20 executes the service.

[0040] The server devices 301 to 303, which are server devices whose usages are not specified, can be executed by using the grid technology, for example. Since the grid technology is a publicly known technology, detailed description thereof is omitted here.

In the above example, a group of server devices that execute various business services is the management target of the system management method according to the present embodiment, but the system management method according to the present embodiment is not limited to this. In addition, various devices such as client terminals and communication control devices can be managed.

Next, the configuration of the system management apparatus that executes the system management method according to the present embodiment will be described. FIG. 2 is a functional block diagram showing the configuration of the system management apparatus 100 shown in FIG. As shown in the figure, the system management apparatus 100 includes a storage unit 110 and a control unit 120.

The storage unit 110 is a storage unit that stores various types of information, and includes a symptom database 111, a countermeasure database 112, a performance requirement database 113, and a configuration management database 114.

[0044] The symptom database 111 is a database in which information for identifying the symptom of the problem occurring in the management target is registered. An example of the symptom database 111 is shown in FIG. As shown in the figure, the symptom database 111 includes an entry number, a judgment condition, a symptom name, an applicable category and a name! It has two items.

[0045] The entry number is an identification number for identifying an entry. The judgment condition is a condition for identifying a symptom, and the symptom database 111 has a plurality of conditions in one entry. It is configured to be set in combination. The symptom name is a symptom identification name specified by the determination condition of the same entry.

The classification and name of the application target are information for limiting the target to which the determination condition of the same entry is applied, and the classification takes a value of either “type” or “instance”. When the value of the category is “Type”, the type of the target to which the judgment condition of the same entry is applied is set in the name. On the other hand, when the value of the category is “instance”, the name of a specific server device or service to which the same entry determination condition is applied is set as the name.

[0047] For example, the entry identified by the entry number "A001" includes "CPU temperature> 80 ° C" as the determination condition, "high fever" as the symptom name, "type" and "type" as the application target category and name. And “Sano” is set. This entry is used for any management target that falls under the category “Sano” and the CPU (Central Processing Unit) temperature exceeds 80 ° C. "Indicates that the symptom identified by the name is identified and identified.

[0048] In addition, the entry identified by the entry number "B001" has "CPU usage rate> 70%" and "service response time> 0.5 seconds" as judgment conditions, and "Server A high load" as a symptom name. ”,“ Instance ”and“ Server A ”are set as the category and name of the application target. This entry is used to manage a specific management target named “Server A” when the CPU usage rate exceeds 70% and the service response time exceeds 0.5 seconds. “Server A high load” for the target ヽぅ Indicates that the symptom identified by name has occurred and is identified.

[0049] In addition, the entry identified by the entry number "B002" t, "CPU usage rate> 80%" as the judgment condition, "Server B high load" as the symptom name, as the classification and name of the application target "Instance" and "Server B" are set. This entry is identified by the name “Server B high load” when the CPU usage rate exceeds 80% for a specific management target named “Server B”. Indicates that the symptom to be identified is identified as occurring.

[0050] In addition, the entry identified by the entry number "C001" has "authentication error> 100 times Z minutes" as the judgment condition, "unauthorized access" as the symptom name, and the applicable category and name. "Type" and "Service" are set. This entry is used for any of the management targets that fall under the category of “service”, and if the number of occurrences of authentication errors exceeds 100 per minute, the entry is “illegal access”. This indicates that the symptoms identified by the name are identified as occurring.

[0051] In addition, the entry identified by the entry number "D001" includes "service response time> 1 second" as the judgment condition, "operation C high load" as the symptom name, and "instance" as the applicable target category and name. And "Business C service" is set. This entry is for a specific managed object with the name “Business C Service” and the response time of the service exceeds 1 second.示し Indicates that a symptom identified by name has occurred!

[0052] As described above, the symptom database 111 designates a type such as a server device or service as an application target, sets a determination condition common to management targets included in the type, and sets each server device or service individually. It is possible to specify both and set specific judgment conditions individually. In addition, since the application target only needs to be set by the category and name of the application target, it can be set easily and setting errors are unlikely to occur.

If there are a plurality of determination conditions for specifying the same symptom, an entry can be provided for each determination pattern in the symptom database 111 and the determination condition can be registered. In this case, the same name is set as the symptom name of multiple entries.

[0054] The countermeasure database 112 is a database in which countermeasures for solving the specified symptoms and countermeasure selection rules are registered. An example of the countermeasure database 112 is shown in FIG. As shown in the figure, the countermeasure database 112 has items such as symptom name, classification and name of application target, countermeasure, application condition, effectiveness, and side effects. It is configured to register multiple side effect combinations.

[0055] The symptom name is an identification name indicating the symptom occurring in the management target, and corresponds to the symptom name in the symptom database 111. The category and name of the target of application indicate the subject where the symptom occurs, and the same value as the item of the same name in the symptom database 111 is set. The workaround is The countermeasures that can be applied to resolve the symptoms and return the management target to normal are shown, and the application conditions indicate the conditions for applying the countermeasures. The effectiveness indicates the effectiveness of the countermeasure, and the side effect indicates the magnitude of the effect produced by the countermeasure. The secondary effect means the effect on equipment and services other than the target where the problem occurs when the countermeasure is implemented.

[0056] When the side effect takes a positive value, it means that a favorable effect is produced by the countermeasure, and when the side effect takes a negative value, an undesirable effect is produced by the countermeasure. Means that. By registering the magnitude of the effect directly obtained by the countermeasure as the effectiveness and separately registering the magnitude of the secondary effect as a side effect, the intention to evaluate the countermeasure is clarified, and the countermeasure Misassessment is less likely to occur when reviewing

[0057] The first entry in Fig. 4 can apply the action of "slow clock" to the symptom identified by the name "high fever", and the conditions for applying this action are in particular The effectiveness of Naguco's countermeasure is “10” and the side effect is “0”. If no application condition is set, it is interpreted that the application condition of the countermeasure is always satisfied in the process of determining the countermeasure.

[0058] In addition, the third entry in the same figure is for the symptom identified by the name "Server B high load", "add server" t, corrective action and "restrict transactions" t indicates that the countermeasure can be applied. The condition for applying the “add server” countermeasure is particularly low. The effectiveness of this countermeasure is “8” and the side effect is “1”. Also, in order to apply the “restrict transaction” countermeasure, it is necessary that the performance requirements of the service are not met. The effectiveness of this countermeasure is “7” and the side effect is “1”. ”

[0059] The service performance requirement is a performance requirement that is required to satisfy the service operation, and is registered in the performance requirement database 113 for each service. In FIG. 2, the symptom database 111 and the countermeasure database 112 are configured independently, but it is possible to merge these two databases into one database. [0060] The performance requirement database 113 is a database in which performance requirements required to satisfy the service are registered. An example of the performance requirement database 113 is shown in FIG. As shown in the figure, the performance requirement database 113 has one item: service name, service content, and performance requirement.

[0061] The service name is an identification name for identifying the service executed on the server device, the service content is a comment indicating the content of the service, and the performance requirement may be satisfied by the service. This is a required performance requirement.

[0062] The first entry in Figure 5 is the service identified by the name “Business A Service”, which is a web service, which processes more than 3000 transactions per minute. Indicates that it is required for performance. In the second entry, the content of the service identified by the name “Business B service” is a customer management service, and this service is required to respond to the request within 1 second in terms of performance. It shows that it is.

[0063] In this example, only one requirement is set for each service. However, a plurality of requirements can be set for one service.

The configuration management database 114 is a database in which information related to the configuration to be monitored is registered. An example of the configuration management database 114 is shown in FIG. As shown in the figure, the configuration management database 114 has items such as resource name, specification, and usage.

[0065] The resource name is the name of the resource to be managed, the specification is the specification of the resource, and the usage is the usage of the resource.

[0066] The first entry in FIG. 6 indicates that the resource identified by the name “Server A” has a CPU of type A and 2 gigabytes of memory and is used for “Business A Service”. It is shown. The second entry also indicates that the resource identified by the name “Server B” has a Type B CPU and 512 MB of memory and is used for “Business B Service”. .

[0067] In the figure, the name of the server device is set as the resource name, the name of the service executed on the server device is set as the usage, and the correspondence between the server device and the service is registered in the configuration management database 114. Force indicating the pipe connection, for example, device connection Various types of information related to the configuration of the management target can be registered in the configuration management database 114.

The control unit 120 is a control unit that controls the system management apparatus 100 as a whole, and includes an information acquisition unit 121, a symptom identification unit 122, a countermeasure determination unit 123, a countermeasure execution unit 124, and information supplement Unit 125 and configuration information updating unit 126. The information acquisition unit 121 is a processing unit that acquires information indicating the status of the management target by receiving a notification event transmitted from the management target.

[0069] Power to be managed An example of a notification event to be transmitted is shown in FIGS. 7-1 to 7-3. As shown in the figure, the notification event has items such as event ID, management target type, management target name, and phenomenon. The event ID is an identification number for identifying the notification event. The management target type is the type of management target for which the notification event notifies the status, and the management target name is a specific name of the management target. The phenomenon indicates a specific situation occurring in the management target.

[0070] If the situation indicated by the phenomenon item relates to the server device, "Sano" is set as the management target type, and the host name of the server device is set as the management target name. If the status indicated by the item is related to a service, “service” is set as the management target type, and the name of the service is set as the management target name.

[0071] It should be noted that the transmission of the notification event to the system management apparatus 100 may also be performed in order to notify the contents when a specific phenomenon occurs in the management target. It may also be a regular notification of a defined event. In addition, the information acquisition unit 121 may be configured to actively collect information by inquiring the status of the management target, or the system administrator may receive a notification event via an input device such as a keyboard. It may be configured to input corresponding information to the information acquisition unit 121! /.

[0072] The symptom identification unit 122 is a processing unit that collates information indicating the status of the management target acquired by the information acquisition unit 121 with the symptom database 111 and identifies a symptom occurring in the management target. is there. The identification of the symptom is based on whether or not the information acquired by the information acquisition unit 121 indicates the status of the application target registered in the symptom database 111, and whether or not the information is registered in the same entry. By judging whether or not the power to satisfy It is done.

[0073] As described above, the symptom database 111 is configured so that symptoms can be specified by a combination of a plurality of determination conditions, and a plurality of determinations can be made only by information included in the notification event. It may not be possible to determine whether a condition is satisfied for some of the condition combinations.

[0074] Therefore, the symptom specifying unit 122 is insufficient in some cases when the information acquisition unit 121 cannot determine the suitability Z nonconformity of a part of the combination of the plurality of judgment conditions only by the information acquired by the information acquisition unit 121. !, Request the information complementing unit 125 to complement the information.

[0075] In requesting supplementation of information, the symptom identification unit 122 refers to the configuration management database 114 as necessary, and determines where to obtain force information. For example, if the information acquisition unit 121 indicates the status of the information power server device, and if the information is insufficient, the information is executed on the server device! The symptom identification unit 122 is executed on the server device with reference to the configuration management database 114 !, acquires information on the service and requests the information completion unit 125 to acquire the status of the service. .

[0076] Depending on the information that is lacking, the information may be obtained by referring to the configuration management database 114. In such a case, the information that the symptom specifying unit 122 itself lacks is obtained.

[0077] The countermeasure determining unit 123 compares the symptom identified by the symptom identifying unit 122 with the countermeasure database 112 to determine a countermeasure for solving the symptom occurring in the management target. Is a processing unit.

[0078] When a plurality of countermeasures are registered in the countermeasure database 112 for the symptom identified by the symptom identifying section 122, the countermeasure determining unit 123 sets the effectiveness and side effect for each countermeasure. The value is added, and the larger the added value, the higher the priority. Then, the countermeasure determining unit 123 verifies the application conditions of each countermeasure in descending order of priority, and first determines that the countermeasure satisfying the application conditions should be implemented.

[0079] Meet the performance requirements of the service conditions registered in the countermeasure database 112 In the case of verifying whether or not the power is to be supported, the countermeasure determining unit 123 acquires the requirements set in the performance requirements from the performance requirement database 113 and verifies whether or not the power is satisfied. To do.

[0080] Note that the countermeasure determining unit 123 may not be able to determine conformity Z nonconformity only by information included in the notification event when verifying the application condition. In such a case, the countermeasure determining unit 123 requests the information supplementing unit 125 to supplement the missing information.

[0081] In requesting supplementation of information, the countermeasure determining unit 123 refers to the configuration management database 114 as necessary to determine where to acquire information. For example, it indicates the status of the information power server device acquired by the information acquisition unit 121, and if the insufficient information indicates the status of the service executed by the server device, The symptom identification unit 122 refers to the configuration management database 114, acquires information on services executed on the server device, and requests the information complementing unit 125 to acquire the status of the services.

[0082] Depending on the missing information, the information may be obtained by referring to the configuration management database 114. In such a case, the countermeasure determining unit 123 itself obtains the missing information. .

The countermeasure execution unit 124 is a processing unit that executes the countermeasure determined by the countermeasure determination unit 123. The information complementing unit 125 is a processing unit that queries the management target for the information requested to be supplemented by the symptom specifying unit 122 or the countermeasure determining unit 123, and also dynamically acquires information indicating the status of the management target. is there.

[0084] The configuration information update unit 126 is a processing unit that, when the configuration to be managed is changed by the countermeasure determined by the countermeasure determination unit 123, reflects the change contents in the configuration management database 114. . For example, when the countermeasure determined by the countermeasure determining unit 123 is to add a server device that executes a service, the configuration information updating unit 126 may newly execute the service. Set the name of the service to be executed in the use field.

As described above, in the system management method according to the present embodiment, the information complementing unit 125 actively acquires information that is insufficient and necessary as necessary. Acquired Even if there is only a small amount of information, it is possible to correctly narrow down whether the symptoms are actually occurring and take appropriate measures. In addition, since symptoms are identified and countermeasures are determined using the minimum necessary information, even if the number of management targets increases, there will be no significant load due to information collection.

Next, the processing procedure of the system management apparatus 100 shown in FIG. 2 will be described. FIG. 8 is a flowchart showing the processing procedure of the system management apparatus 100. This figure shows a processing procedure after the system management apparatus 100 receives a notification event of the management target power.

[0087] As shown in the figure, when the information acquisition unit 121 acquires information indicating the status of the management target from the received notification event (step S101), the symptom identification unit 122 reads an entry in the symptom database 111. (Step S102). If all entries have been read (Yes at step S103), it is determined that there is no problem with the management target and the process ends.

[0088] When an unprocessed entry can be read from the symptom database 111 (No at step S103), the management target information acquired by the information acquisition unit 121 indicates the status of the target of application of the read entry. Verify whether it is a thing. If it does not indicate the status of the application target (No at Step S104), the process returns to Step S102 and proceeds to the processing of the next entry.

[0089] If the information of the management target acquired by the information acquisition unit 121 indicates the status of the application target of the read entry (Yes in step S104), the symptom specifying unit 122 sends the information to the information acquisition unit 121. Check whether the management target information obtained in this way matches all or part of the judgment criteria of the read entry. If the determination condition is not met at all (Yes at Step S105), the process returns to Step S102 and proceeds to the processing of the next entry.

[0090] On the other hand, if the information ability of the management target acquired by the information acquisition unit 121 matches all or part of the judgment conditions of the lead entry (No at step S105), the judgment conditions are satisfied. If there is a shortage of information necessary to determine whether or not it is possible (Yes in step S 1 06), obtain configuration information from the configuration management database 114 as necessary to obtain information. The destination is determined (step S107), and the information supplement unit 125 is instructed to actively acquire the missing information (step S108).

[0091] Then, it is confirmed that the determination condition is satisfied with all necessary information. If this is the case (Yes in step S109), the symptom identifying unit 122 identifies that the symptom indicated by the symptom name of the entry has occurred in the management target (step S110), and the system management apparatus 100 executes the countermeasure described later. Processing is executed (step S111).

[0092] If it is confirmed that all the necessary information has been collected and the determination condition is not satisfied (No in step S109), the symptom specifying unit 122 returns to step S102 and returns to the next entry. Transition to processing.

FIG. 9 is a flowchart showing a processing procedure for countermeasure execution processing. As shown in the figure, the countermeasure determining unit 123 reads the entry of the countermeasure database 112 corresponding to the symptom identified by the symptom identifying unit 122 (step S 201), and based on the effectiveness and the side effect value. Then, the priority of each countermeasure is calculated (step S202).

Then, the countermeasure determining unit 123 selects one countermeasure with the highest priority among unselected countermeasures (step S 203). Here, if all countermeasures have been selected (Yes in step S204), the process is terminated assuming that there is no effective countermeasure.

[0095] If an unselected countermeasure can be selected (No at Step S204), if there is not enough information (Yes at Step S205) to determine whether the applicable condition is satisfied or not, If necessary, obtain the configuration information from the configuration management database 114 to determine the information acquisition destination (step S206), and instruct the information complementing unit 125 to actively acquire the missing information (step S206). S 207).

[0096] Then, when it is confirmed that the application condition is satisfied with all necessary information being prepared (Yes at Step S208), the countermeasure determining unit 123 sets the countermeasure to the countermeasure executing unit 124 〖. This is executed (step S209), and if necessary, the configuration information update unit 126 is made to update the configuration management database 114 (step S210). On the other hand, if it is confirmed that the application condition is not satisfied (No at Step S208), the countermeasure determining unit 123 returns to Step S203 and proceeds to the processing of the next countermeasure.

Next, a specific operation example of the system management apparatus 100 will be described by taking as an example the case where the information acquisition unit 121 receives each notification event shown in FIGS. 7-1 to 7-3. The notification event shown in Figure 7-1 indicates that the CPU usage is 73% for server devices with host names “Server A” and “!”. [0098] In order to identify the symptom indicated by this information, the symptom identification unit 122 reads an entry in the symptom database 111 and examines the application target and the determination condition. Among the entries in the example of the symptom data base 111 shown in Fig. 3, the notification event shown in Fig. 7-1 corresponds to the condition to be applied because it applies to all server devices. An entry with the number “A001” and an entry with the entry number “B001” that applies to the management target having the name “Server A”.

[0099] Of these two entries, the determination condition of the entry with the entry number “A001” is related to the CPU temperature and has nothing to do with the notified information. Judged not to exist.

On the other hand, the determination condition of the entry “B001” relates to the CPU usage rate and the service response time, and the notified information satisfies the CPU usage rate condition. Therefore, the symptom specifying unit 122 instructs the information complementing unit 125 to provide the missing information, specifically, “response of the service executed on the server device having the server Aj t ヽぅ host name”. At this time, referring to the configuration management database 114, the symptom specifying unit 122 is executed on the server device having the host name “Server A”, and the service is executed. This information is checked and the service is designated to the information complementing unit 125.

If the missing information is acquired, the symptom specifying unit 122 determines whether or not the determination condition for the entry with the entry number “B001” is satisfied. Here, if the acquired service response time is 2 seconds, for example, the determination condition of this entry is completely satisfied, and the symptom specifying unit 122 has a server having the host name “server A”. In the device, “Server A high load” 症状 A symptom corresponding to the symptom name has occurred! / Specify to speak.

[0102] After the symptom is identified in this manner, the countermeasure determining unit 123 refers to the countermeasure database 112 and determines the countermeasure. In the entry of the symptom name “Server A high load” in the example of the countermeasure database 112 shown in FIG. 4, “add server” t, only the countermeasure is registered, and no applicable condition is specified. The measure determining unit 123 determines to execute this countermeasure.

Then, the countermeasure determining unit 123 causes the countermeasure executing unit 124 to execute “add server”, and the configuration management database 1 indicates that the service is being executed on the added server. The configuration information update unit 126 is instructed to be reflected in 14.

As described above, in the system management method according to the present embodiment, information on the specific symptoms related to individual server devices, etc. that are not classified by type is registered in the symptom database 111, and individual information is registered. Appropriate problems can be dealt with according to the specifications of the equipment and usage.

[0105] The notification event shown in Figure 7-2 shows that the server usage with the host name “Server B” is V, and the CPU usage rate is 88%! /,! /, The

[0106] In order to identify the symptom indicated by this information, the symptom identification unit 122 reads an entry in the symptom database 111 and examines the application target and the determination condition. Of the entries in the example of symptom data base 111 shown in Fig. 3, the notification event shown in Fig. 7-2 corresponds to the conditions to be applied. An entry with the number “A001” and an entry with the entry number “B002” to which the management target having the name “Server B” is applied.

[0107] Of these two entries, the entry criteria "A001" entry judgment condition is related to CPU temperature and has nothing to do with the notified information. Judged not to exist.

On the other hand, the determination condition of the entry “B002” relates to the CPU usage rate, and the notified information satisfies the CPU usage rate condition. Therefore, as shown in this entry, the symptom identification unit 122 generates a symptom corresponding to the “server B high load” ヽぅ symptom name in the server device having the host name “server B”! / Specify to speak.

Thus, after the symptom is identified, the countermeasure determining unit 123 refers to the countermeasure database 112 and determines the countermeasure. In the entry of the symptom name “Server B high load” in the example of the countermeasure database 112 shown in FIG. 4, two countermeasures are registered. Here, the sum of the effectiveness and side effects of the countermeasure “Add server” is 5, and the sum of the effectiveness and side effects of the countermeasure “Restrict transactions” is 6. 123 determines that the latter countermeasure is higher and has priority.

Then, the countermeasure determining unit 123 determines the application condition of the countermeasure “limit the transaction”. Here, the application condition is that the performance requirements of the service are not met. Therefore, the countermeasure determining unit 123 refers to the configuration management database 114, and the service executed by the server device having the host name “Server B” is “Business B service”. Recognize that it exists, and refer to the performance requirement database 113 to obtain the performance requirement of the service “Operation B service”.

[0111] As a result, the performance requirement of “service response time ≤ 1 second” is acquired. Since the service response time is not included in the notification event, this information is acquired by instructing the information supplement unit 125. Let If the acquired service response time does not satisfy the performance requirement, the countermeasure determining unit 123 determines “limit the transaction” as a countermeasure and causes the countermeasure executing unit 124 to execute it.

[0112] As described above, in the system management method according to the present embodiment, by using the information registered in the configuration management database 114 and the performance requirement database 113, a rule for selecting an appropriate countermeasure can be simplified. Can be set to

[0113] The notification event shown in Figure 7-3 shows that the service response time of the service named “Business C service” is 2 seconds.

[0114] In order to identify the symptom indicated by this information, the symptom identification unit 122 reads an entry in the symptom database 111 and examines the application target and the determination condition. Among the entries in the example of the symptom data base 111 shown in Fig. 3, the notification event shown in Fig. 7-3 corresponds to the applicable conditions. It is an entry of “C001” and an entry number “D001” that applies to the management target having the name “Business C Service”.

[0115] Of these two entries, the entry criteria "C001" entry judgment condition is related to the authentication error and has nothing to do with the notified information. It is judged that there is no.

On the other hand, the determination condition of the entry “D001” relates to the service response time, and the notified information satisfies the service response time condition. Therefore, the symptom identification unit 122 identifies that the symptom corresponding to the symptom name “Business C high load” is occurring in the service named “Business C service”.

[0117] After the symptom is identified in this way, the countermeasure determining unit 123 stores the countermeasure database 112. Refer to to determine the countermeasure. In the entry for the symptom name “Business C high load” in the example of the countermeasure database 112 shown in FIG. 4, only the countermeasure “add server” is registered, and no application condition is specified. The decision unit 123 decides to execute this countermeasure.

[0118] The countermeasure determining unit 123 then causes the countermeasure executing unit 124 to execute "add server" and reflect that the service is being executed on the added server in the configuration management database 1 14 The configuration information update unit 126 is instructed to do so.

As described above, in the system management method according to the present embodiment, information is registered in the symptom database 111 in accordance with the symptom of the service executed on the server device that is not per server. In addition, appropriate problems can be dealt with for problems that occur in the service.

[0120] In the description of the above processing procedure, for simplification of explanation, when the countermeasure is determined, the classification and name of the application target of the countermeasure database 112 are the classification of the application target of the identified symptom. The explanation of verifying whether or not the force matches the name is omitted. The same symptom name may be set for different application targets. It goes without saying that it is preferable to verify name matches.

Note that the configuration of the system management apparatus 100 according to the present embodiment shown in FIG. 2 can be variously changed without departing from the gist of the present invention. For example, a function equivalent to that of the system management apparatus 100 can be realized by mounting the function of the control unit 120 of the system management apparatus 100 as software and executing the function by a computer. An example of a computer that executes a system management program 1071 in which the function of the control unit 120 is implemented as software is shown below.

FIG. 10 is a functional block diagram showing the computer 1000 that executes the system management program 1071. The computer 1000 includes a CPU 1010 that executes various arithmetic processes, an input device 1020 that receives input of data from a user, a monitor 1030 that displays various information, a medium reader 1040 that reads a recording medium force program, and the like. A network interface that exchanges data with other computers via a network. An ace device 1050, a RAM (Random Access Memory) 1060 for temporarily storing various information, and a hard disk device 1070 are connected by a bus 1080.

The hard disk device 1070 corresponds to a system management program 1071 having the same function as the control unit 120 shown in FIG. 2 and various databases stored in the storage unit 110 shown in FIG. System management data 1072 is stored. Note that the system management data 1072 can be appropriately distributed and stored in other computer connected via the network.

Then, the CPU 1010 reads the system management program 1071 from the hard disk device 1070 and expands it in the RAM 1060, whereby the system management program 1071 functions as the system management process 1061. Then, the system management process 1061 appropriately expands information read from the system management data 1072 to an area allocated to itself on the RAM 1060, and executes various data processing based on the expanded data. .

Note that the system management program 1071 does not necessarily need to be stored in the hard disk device 1070 so that the computer 1000 reads out and executes this program stored in a storage medium such as a CD-ROM. Also good. The program is stored in another computer (or sano) connected to the computer 1000 via a public line, the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), etc. The 1000 may also read and execute these programs.

Industrial applicability

[0126] As described above, the system management program, the system management apparatus, and the system management method according to the present invention autonomously identify a symptom occurring in a management target and determine a countermeasure corresponding to the symptom. This is especially useful when it is necessary to easily register information for identifying symptoms by specifying individual management targets rather than by type.

Claims

The scope of the claims

[1] A system management program that identifies the symptoms of a problem that occurs in the management target and decides the corrective action to resolve the symptoms.

An information acquisition procedure for acquiring information indicating the status of the management target;

A symptom in which information acquired by the information acquisition procedure is registered for each entry, and the symptom that may occur in the application target and the criteria for determining the symptom are registered for each management target or the type of management target A symptom identification procedure for identifying a symptom occurring in the management object by collating with a database;

By comparing the symptom identified by the symptom identification procedure with a countermeasure database in which a symptom that may occur in the management target and a countermeasure for solving the symptom are associated and registered, the management target To determine the corrective action to resolve the symptoms

A system management program for causing a computer to execute.

[2] Since the information acquired by the information acquisition procedure is insufficient, the symptom specifying procedure specifies the symptom occurring in the management target even if the information is collated with the symptom database. 2. The system management program according to claim 1, further causing a computer to execute an information supplement procedure for acquiring information that is insufficient from the management target in a case where the information cannot be obtained.

[3] Since the symptom identification procedure lacks information acquired by the information acquisition procedure! /, The symptom occurring in the management target even if the information is checked against the symptom database. When it is not possible to identify the information source, the configuration management database in which the information related to the configuration to be managed is registered is referred to. 3. The system management program according to claim 2, wherein information that is lacking in the procedure is acquired.

[4] The countermeasure determining procedure is registered in association with the countermeasure when a plurality of countermeasures corresponding to the symptom identified by the symptom identifying procedure are included in the countermeasure database. The system according to claim 2, wherein a countermeasure that satisfies the application condition is determined as a countermeasure for solving the symptom occurring in the management target. System management program.

[5] The information supplement procedure is registered in association with the countermeasure, and is insufficient when information necessary to determine whether the applicable condition is satisfied is insufficient. 5. The system management program according to claim 4, wherein the management target power is acquired.

[6] When the countermeasure determination procedure is registered in association with the countermeasure, and there is insufficient information necessary to determine whether or not the applicable condition is satisfied, 6. The system management program according to claim 5, wherein a shortage of information acquisition destination is specified, the acquisition destination is specified, and the information supplement procedure is insufficient to acquire the information.

[7] Since the symptom identification procedure lacks information acquired by the information acquisition procedure! /, The symptom occurring in the management target even if the information is checked against the symptom database. 4. The system management program according to claim 3, wherein when the information cannot be specified, the system management program acquires a shortage of information by referring to the configuration management database.

[8] A system management device that identifies the symptom of a problem that is occurring in the management target and decides a countermeasure to resolve the symptom.

Information acquisition means for acquiring information indicating the status of the management target;

A symptom in which information acquired by the information acquisition means is registered for each entry, and the symptom that can occur in the application target and the criteria for determining the symptom are registered for each entry. A symptom identifying means for identifying a symptom occurring in the management target by collating with a database;

By comparing the symptom specified by the symptom specifying means with a countermeasure database in which a symptom that may occur in the management target and a countermeasure for solving the symptom are associated and registered, the management target Measures to determine measures to resolve the symptoms that occur

A system management apparatus comprising:

[9] Since the information acquired by the information acquisition unit is insufficient, the symptom specifying unit specifies the symptom occurring in the management target even if the information is collated with the symptom database. If this is not possible, the information that is missing is collected from the management target. 9. The system management apparatus according to claim 8, further comprising information complementing means to obtain.

[10] Since the information acquired by the information acquisition unit is insufficient, the symptom specifying unit specifies a symptom occurring in the management target even if the information is checked against the symptom database. If it is not possible, refer to the configuration management database in which the information related to the configuration to be managed is registered, identify the acquisition source of the missing information, specify the acquisition destination, and the information supplement means is insufficient 10. The system management apparatus according to claim 9, wherein the information is acquired.

[11] The countermeasure determining means is registered in association with the countermeasure when a plurality of countermeasures corresponding to the symptom identified by the symptom identifying means are included in the countermeasure database. 10. The system management apparatus according to claim 9, wherein a countermeasure that satisfies an application condition is determined as a countermeasure for resolving a symptom occurring in the management target.

[12] The information complementing means may provide information that is insufficient when information necessary for determining whether or not an application condition registered in association with the countermeasure is satisfied is insufficient. 12. The system management apparatus according to claim 11, wherein the system management device is acquired from the management target.

[13] The countermeasure determining means is insufficient when information necessary for determining whether or not the application condition registered in association with the countermeasure is satisfied is insufficient. 13. The system management apparatus according to claim 12, wherein the information acquisition destination is specified, the acquisition destination is specified, and the information supplement means is insufficient to acquire the information.

[14] A system management method for identifying a symptom of a problem occurring in a management target and determining a countermeasure for solving the symptom,

An information acquisition step of acquiring information indicating the status of the management target;

Symptoms in which the information acquired by the information acquisition process is registered for each entry, and the symptom that can occur in the application target and the criteria for determining the symptom are registered for each entry. A symptom identification step for identifying the symptoms that occur in the management target! By comparing the symptom identified in the symptom identification step with a countermeasure database in which a symptom that may occur in the management target and a countermeasure for solving the symptom are associated and registered, the management target A countermeasure determination process to determine a countermeasure to resolve the symptoms

System management method characterized by including.

[15] Since the information acquired by the information acquisition step is insufficient, the symptom specifying step specifies the symptom occurring in the management target even if the information is collated with the symptom database. 15. The system management method according to claim 14, further comprising an information supplementing step of acquiring information that is insufficient in some cases from the management target.

[16] In the symptom specifying step, because the information acquired by the information acquiring step is insufficient! /, The symptom occurring in the management target even if the information is checked against the symptom database. When it is not possible to identify the information source, the configuration management database in which the information related to the configuration to be managed is registered is referred to. 16. The system management method according to claim 15, wherein information lacking in the process is acquired.

[17] The countermeasure determining step is registered in association with the countermeasure when the countermeasure database includes a plurality of countermeasures corresponding to the symptom identified by the symptom identifying process. 16. The system management method according to claim 15, wherein a countermeasure that satisfies an application condition is determined as a countermeasure for resolving a symptom occurring in the management target.

[18] The information complementing step is performed when the information necessary for determining whether or not the application condition registered in association with the countermeasure is satisfied is insufficient. The system management method according to claim 17, wherein the management target power is also acquired.

[19] The countermeasure determining step is insufficient when information necessary for determining whether or not the application condition registered in association with the countermeasure is satisfied is insufficient. The information acquisition destination is specified, the acquisition destination is specified, and the information supplement process is insufficient. 19. The system management method according to claim 18, wherein information is acquired.