JPH10240705A - Fault integrated managing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily cope with fault occurrence by retrieving data from a 1st and a 2nd data base and informing a fault monitor staff of fault handing information on an occurring fault. SOLUTION: The 1st data base 15 manages the correspondence relation between fault information that a display means 13 displays and fault handling information inputted from a 1st input means 14 by using data that fault information has as a key. The 2nd data base 17 manages the correspondence relation between the fault information and fault handling information managed by the 1st data base 15 so that they are made to correspond to know-how key data inputted by a 2nd input means 16. Then a retrieval means retrieves data from the 1st and 2nd data bases 15 and 17 and informs the fault monitor staff of the fault handling information on an occurring fault. Consequently, the fault occurrence can easily be coped with.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a fault integrated management device for integrally managing faults occurring in a plurality of information communication processing devices connected via a network, and more particularly, to easily cope with a fault occurrence. The present invention relates to a fault integrated management device having a function to make it possible.

[0002]

2. Description of the Related Art There is a data processing system configured by connecting a plurality of information communication processing devices via a network.

[0005] Such a data processing system usually employs a configuration in which information communication processing devices of different manufacturers are mixedly used. From now on, such a data processing system has not conventionally adopted a configuration in which generated fault information is centrally managed.

[0004]

However, according to such a conventional technique, there has been a problem that failure information generated in such a data processing system cannot be centrally stored as know-how.

[0005] Therefore, when a new fault occurs, there is a problem that the fault monitoring personnel does not know what action to take, and it is not easy to deal with the fault occurrence.

SUMMARY OF THE INVENTION The present invention has been made in view of the above circumstances, and has been made in consideration of the above-described configuration in which a failure that occurs in a plurality of information communication processing apparatuses connected via a network is integratedly managed. On the other hand, it is an object of the present invention to provide a new fault integrated management device having a function of enabling easy handling.

[0007]

FIG. 1 shows the principle configuration of the present invention. In the figure, reference numeral 1 denotes a fault integrated management device equipped with the present invention, which integrally manages faults occurring in a plurality of information communication processing devices 3 connected via a network 2, and 4 denotes a fault integrated management device 1. , Which serves as a device for interacting with fault monitoring personnel.

The integrated fault management device 1 includes a receiving unit 10
Conversion means 11, determination means 12, display means 13
And first input means 14 and first database 15
, A second input means 16 and a second database 17
, Registration means 18 and search means 19.

[0009] The receiving means 10 receives the fault information notified from the information communication processing device 3. The conversion unit 11 converts the failure information notified from the information communication processing device 3 into a unified format when the information communication processing device 3 is configured by a different system. The determination unit 12 determines whether the failure information notified from the information communication processing device 3 needs to be dealt with. The display means 13 displays the fault information to the fault monitoring personnel by displaying the fault information on the display of the terminal 4 when the fault information is notified from the information communication processing device 3.

[0010] The first input means 14 inputs fault handling information from fault monitoring personnel which is input in response to the display processing of the display means 13. The first database 15 manages the correspondence between the failure information displayed by the display unit 13 and the failure handling information input by the first input unit 14 using the data of the failure information as a key.

The second input means 16 is a first input means 1
The know-how key data that is input in association with the failure handling information input by the user and is associated with the key data of the first database 15 is input. Second database 17
Manages the correspondence between the failure information managed by the first database 15 and the failure handling information in association with the know-how key data input by the second input means 16.

The registration means 18 executes a process for registering data in the first and second databases 15 and 17. The search unit 19 notifies the fault monitoring personnel of fault handling information for the fault that has occurred by searching the data in the first and second databases 15 and 17.

In the fault integrated management device 1 of the present invention configured as described above, when the receiving means 10 receives the fault information,
The judging means 12 judges whether or not the received fault information needs to be dealt with, and in response, the display means 13 indicates that the received fault information needs to be dealt with. When it is determined that the fault information is displayed on the display of the terminal 4, the fault monitoring
Display the fault information.

In response to the display of the fault information, the fault monitoring personnel executes a fault handling process, and when the execution is completed, the fault handling information and the know-how key data associated with the key data of the fault information. Is input, the first input unit 14 inputs the input troubleshooting information, and in response, the registration unit 18
The correspondence between the displayed fault information and the input fault handling information is registered in the first database 15 using the data of the fault information as a key.

The second input means 16 inputs the input know-how key data, and in response to this, the registration means 18 stores the failure information and the failure handling information registered in the first database 15. Is registered in the second database 17 using the input know-how data as a key.

In this manner, the first database 15
The key data of the failure information is used as a key, and the correspondence between the failure information and the troubleshooting information is registered. The know-how key data associated with the key data of the first database 15 is stored in the second database 17 as a key. And the first
The correspondence between the failure information and the troubleshooting information registered in the database 15 is registered.

The first and second databases 15, 17
Then, when the failure information is displayed on the display of the terminal 4, the failure monitoring personnel issues a search request for the troubleshooting information using the key data and the know-how key data. In response to the search request, the first database 15 and the second database 17 are searched to obtain troubleshooting information corresponding to the generated fault information, and display the same on the display of the terminal 4. As a result, the fault monitoring personnel can quickly deal with the generated fault.

As described above, the fault integrated management device 1 of the present invention
When a failure occurs in a plurality of information communication processing devices 3 connected via a network, the failure monitoring staff can easily cope with the occurrence of the failure.

[0019]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail according to embodiments. FIG. 2 illustrates an embodiment of the present invention. In the figure, the same components as those described in FIG. 1 are denoted by the same reference numerals.

Here, the information communication processing device 3 (system)
Are prepared, for example, to carry out various tasks of one company.
As a result, systems of different manufacturers are used in a mixed manner, and these information communication processing devices 3 perform various different tasks.

The fault integrated management device 1 of the present invention according to the present embodiment is used for realizing integrated management of faults occurring in the information communication processing device 3 in order to monitor information communication processing device 3
The information communication processing device 3 which is provided in association with
A first monitoring program 20 for monitoring whether or not a failure has occurred in the information communication processing device 3; a second monitoring program 21 for determining whether or not a failure that has occurred in the information communication processing device 3 needs to be dealt with; A database 2 that manages the correspondence between fault information that has occurred in the information communication processing device 3 and how to deal with it.
2 (to be described later, a main database 220 and a know-how database 221), a management program 23 for managing the database 22, and fault information generated in the information communication processing device 3 to the terminal 4. A display program 24 to be displayed, a dialogue program 25 for inputting a method of handling a failure occurring in the information communication processing device 3 in accordance with an interactive process between the failure monitoring personnel, and a failure handling method required by the failure monitoring personnel Search program 26 for searching for information, and a fault information registration table 2 for managing information necessary for the monitoring process of the first monitoring program 20
7 and a failure information selection table 28 for managing information necessary for the judgment processing of the second monitoring program 21.

The failure information registration table 27 specifically manages the message ID of the failure message for the information communication processing device 3 having the message ID, as shown in FIG. As for the information communication processing device 3 having no message ID, as shown in FIG. 3B, for example, when “the column 10 to 30 of the message indicates that a failure has occurred, the message ID“ AAA001 ”is added at the beginning of the message. To manage what part of the message is going to be the failure message and what kind of message ID is added at that time. to manage.

On the other hand, specifically, as shown in FIG. 4, the fault information selection table 28 stores the message indicated by the message ID and the system name ( It manages what the status of the information communication processing device 3 is and what the error message needs to be dealt with.

For example, when the message ID is "ID1", when the system name transmitted in association with the message indicates "operation", it is managed as a trouble message that needs to be dealt with. ID
Is "ID2" and the system name sent in association with the message indicates "operation 1",
Columns 1-3 of the text part of the message are "ON
When the job name “L” is displayed, it is managed as a failure message that needs to be dealt with, or the message I is displayed.
D is “ID3”, the system name sent in association with the message indicates “operation 2”, the third token in the text portion of the message indicates “abnormal”, and When "real" is displayed in the 21st to 23rd columns, it is managed as a failure message that needs to be dealt with.

FIG. 5 shows an embodiment of a processing flow executed by the first monitoring program 20, FIG. 6 shows an embodiment of a processing flow executed by the second monitoring program 21, and FIG. FIG. 8 shows an embodiment of a processing flow executed by the interactive program 25, and FIG. 9 shows an embodiment of a processing flow executed by the search program 26. Next, the present invention will be described in detail according to these processing flows.

When the information communication processing device 3 transmits the message of the operation information, the first monitoring program 20 provided in association with the information communication processing device 3 is activated. 1 monitoring program 2
As shown in the processing flow of FIG. 5, first, in step 1, a message of the operation information and a system name transmitted in association with the message are fetched.

Here, the message sent from the information communication processing device 3 includes a job name, a system type (online / batch distinction), a device address, and the like. The system name is sent separately from the message in association with the message. Although not shown in FIG. 2, a table for managing the correspondence between the device address and the device name is prepared, so that the device from which the message is issued is DASD, Stations can be identified.

In step 1, the operation information message and the system name are fetched. Then, in step 2, by referring to the failure information registration table 27, it is determined whether the message is a failure information message. Then, in the subsequent step 3, when it is determined that the message is not a failure information message according to this determination processing, the processing is terminated without performing any processing.

On the other hand, when it is determined in step 3 that the message is a message of failure information, the process proceeds to step 4 and the failure message from the information communication processing device 3 having no message ID is stored in the failure information registration table 2.
By adding a message ID in accordance with the instruction of the management data of No. 7, the fetched fault message is converted into a unified fault message.

To explain with reference to the example shown in FIG.
When it is determined that the message is a failure message by indicating that a failure has occurred in columns 10 to 30 of the message fetched from the information communication processing device 3 having no message ID, the message ID “AAA001” is added to the head of the failure message. Is converted to a message having the same format as the fault message from the information communication processing device 3 having the message ID.

When the conversion process in step 4 is completed, the process proceeds to step 5, where the second monitoring program 21
To transfer the failure information. In this way, the first monitoring program 20 monitors whether or not a failure has occurred in the information communication processing device 3 by monitoring the message issued by the information communication processing device 3, and the failure has occurred. To determine this, processing is performed to transfer the failure information to the second monitoring program 21.

When the failure information is transferred from the first monitoring program 20, the second monitoring program 21
As shown in the processing flow of FIG.
Then, the message of the failure information and the system name transferred from the first monitoring program 20 are fetched.

Subsequently, in step 2, by referring to the failure information selection table 28, it is determined whether or not the message of the acquired failure information is of a failure that needs to be dealt with. When it is determined that the message is not a failure message that needs to be dealt with according to this determination processing, the processing ends without performing any processing.

On the other hand, if it is determined in step 3 that the message is a failure message that needs to be dealt with, step 4
To the management program 23, and the message
The system name transmitted in association with this is transferred, and the process is terminated.

Thus, the second monitoring program 2
1 monitors the failure information message passed from the first monitoring program 21 to determine whether a failure requiring a response has occurred, and determines that a failure requiring a response has occurred. In some cases, processing is performed so that a failure message that needs to be dealt with and the system name sent in association with the failure message are transferred to the management program 23.

Since the message of the fault information is converted into a unified format according to the processing of the first monitoring program 20, the second monitoring program 21 sends the message to the information communication processing device 3 to be monitored. And the failure information selection table 28 is also prepared as a common one for the information communication processing device 3 to be monitored.

When the management program 23 transfers the message of the fault that needs to be dealt with and the system name sent in association with the message from the second monitoring program 21, it is shown in the processing flow of FIG. As described above, first, in step 1, the information is fetched.

Subsequently, in step 2, the display program 2
By instructing the failure monitoring unit 4 to display a message of the captured failure information and the system name on the display of the terminal 4, the failure monitoring staff is notified of the occurrence of a failure that needs to be dealt with. At this time, by adopting a configuration in which a list of the information communication processing devices 3 to be monitored is displayed and processing is performed so as to clearly indicate the information communication processing device 3 in which a failure has occurred, which information communication processing device 3 It is preferable because it is possible to see at a glance whether a failure has occurred.

Subsequently, in step 3, the message of the fault information which needs to be dealt with and the system name received from the second monitoring program 21 are registered in the database 22 (registered in the main database 220 described later). In step 4, a message ID, a job name, a device name (specified from the device address), and the like are extracted from the message of the registered fault information, and the registered fault information is used by using the system name and the cut-out data as keys. Performs processing to associate with the message of

As described above, the management program 23
Upon receiving the trouble message and the system name that need to be dealt with from the second monitoring program 21, they are registered in the main database 220 of the database 22, as shown in FIG. Alternatively, a job name, a device name, and the like are extracted, and the system name and the extracted data are used as keys to perform processing so as to be associated with the registered failure message.

Here, when registering a fault message in the main database 220, processing is performed so as to register the date and time of occurrence of the fault message as shown in FIG.

When the management program 23 displays the fault message on the display of the terminal 4, the fault monitoring personnel operating the terminal 4 inputs the phenomena summary and detailed information on the fault indicated by the displayed fault message. When this information is input, the interactive program 25 firstly, in a step 1, as shown in the processing flow of FIG. Capture information.

Here, the information of the phenomena summary and the phenomena details include the fault classification, the investigation department, the subsystem name, the business name, the issue classification, the responder, the installation location, the degree of influence, and the like. There are correspondence status, manufacturer name and the like.

Subsequently, in step 2, the management program 2
By instructing the trouble message, the information of the phenomena and the details of the phenomena are registered in the main database 220 in correspondence with the trouble message.

As described above, the interactive program 25
When the failure monitoring staff inputs information on the phenomena and details of the phenomena of the failure indicated by the failure message, the information is registered in the main database 220 while corresponding to the failure message, as shown in FIG. Will be processed as follows.

Since the main database 220 serves as history information of faults of the information communication processing device 3, fault monitoring personnel can refer to the main database 220 to specify a specific information communication processing device 3. It is possible to accurately grasp the state of occurrence of various types of failures such as occurrence of many failures, failure of the information communication processing device 3 of a specific manufacturer, and failure of a specific job.

Further, when the management program 23 displays the fault message on the display of the terminal 4, the fault monitoring personnel operating the terminal 4 takes action for the fault indicated by the fault message, and obtains information on the countermeasures. When the user inputs the key data, another key data (referred to as know-how key data) corresponding to the key data of the trouble message and to which the coping method can be applied is input. Then, as shown in the processing flow of FIG. 8B, the dialogue program 26 first fetches the input coping information in step 1.

Subsequently, in step 2, the management program 2
3 instructs the acquired response information to the main database 220 while corresponding to the failure message.
Register with. According to the registration process, as shown in the main database 220 shown in FIG. 12, the handling information of the fault is registered in the main database 220 in association with the fault information registered in the main database 220.

Subsequently, in step 3, the input know-how key data is fetched. Then, in step 4,
By instructing the management program 23, the acquired know-how key data is used as a key, and the know-how database 221 as shown in FIG.

The process of constructing the know-how database 221 specifically includes, as shown in FIG. 12, copying the message, system name, and handling information of the fault information, and copying the know-how key data to the copied data. This is performed by setting the pointer to point. Since the message, system name, and handling information of the failure information are registered in the know-how database 221 by the copying process, no data registration error occurs in the know-how database 221.

Thus, the interactive program 25
When fault monitoring personnel enters know-how key data,
Correspondence relationship between failure information and response information registered in main database 220 (searchable by key data)
Know-how database 221 that is a generalization of
To be constructed.

When the know-how database 221 is used, when the know-how key data is given, it is possible to search the correspondence between the trouble information indicated by the know-how key data and the coping information,
As a result, it becomes possible to know how to deal with the fault that has occurred. The search program 26 executes this search process.

That is, when the failure message is displayed on the display of the terminal 4 and the failure monitoring staff specifies key data (know-how key data) and issues a search request for a solution to the failure, the search program 26, first, as shown in the processing flow of FIG.
In step 1, the input key data (know-how key data) is fetched.

Here, when the trouble message is displayed, there is a possibility that the trouble message has been issued in the past and a countermeasure is being taken against it. from now on,
When the trouble message is displayed, the trouble monitoring personnel first issues a search request by specifying the key data of the main database 220, and when it is found that the key data is not registered in the main database 220, Subsequently, a search request is issued by specifying the know-how key data of the know-how database 221 in order to refer to a measure for a similar failure that has occurred in the past.

In the following step 2, by instructing the management program 23, it is determined whether or not the fetched key data is registered in the main database 220. When it is determined that the key data is registered in the main database 220, the process proceeds to step 6, where the action information indicated by the key data registered in the main database 220 is read and displayed on the display of the terminal 3.

As a result, the fault monitoring personnel can know the countermeasures taken in the past for the fault, and can immediately cope with the fault that has occurred according to this countermeasure.

On the other hand, when it is determined that the input key data is not registered in the main database 220 in accordance with the determination processing of step 3, step 4
Then, by instructing the management program 23, it is determined whether or not the fetched key data (know-how key data) is registered in the main database 220. Subsequently, in step 5, when it is determined that the information is not registered in the know-how database 221 according to this determination processing, the processing is terminated as it is, and when it is determined that the information is registered, the process proceeds to step 6, where the know-how database The coping information indicated by the key data (know-how key data) registered in the terminal 221 is read and displayed on the display of the terminal 3.

As a result, the fault monitoring personnel can know the countermeasures taken in the past for similar faults, and can quickly cope with the fault that has occurred according to this countermeasure.

For example, if the failure monitoring personnel determines the message ID
When the coping method a is applied to the fault A having “IO0001E”, if it is determined that the coping method a is also effective for the fault having the message ID “IO0002E”, the message ID “IO0002E” Is input as know-how key data.

As a result, as shown in FIG. 13, the message ID “IO” is stored in the know-how database 221.
0002E "points to" correspondence relationship between the message of the fault A and the countermeasure a ".

From now on, the fault monitoring personnel will send message I
When a failure having the D “IO0002E” occurs, by searching the know-how database 221 using the message ID “IO0002E”, “correspondence relationship between the message of the failure A and the coping method a” can be obtained. ,
As a result, for the fault that has occurred, the message ID
It is possible to know that it is effective to perform the coping method a performed in the case of the failure A having “IO001E”.

Further, for example, if the fault monitoring personnel changes the device name α
If the countermeasure c is performed on the failure C that occurred in
When it is determined that the countermeasure method c is also effective for a fault occurring in the device name β, the device β is input as know-how key data.

As a result, as shown in FIG. 14, it is registered in the know-how database 221 that the device name β points to “correspondence between the message of failure C and the coping method c”.

From this, when a fault occurs in the device name β, the fault monitoring personnel searches the know-how database 221 using the device name β to obtain the “correspondence relationship between the message of the fault C and the coping method c. As a result, it is possible to know that it is effective to apply the countermeasure c performed when the failure C occurs in the device name α.

[0065]

As described above, when the fault integrated management device of the present invention is used, a method for coping with a fault occurring in an information communication processing device connected via a network is integrated as know-how. Therefore, when a fault occurs in a plurality of information communication processing devices connected via a network, the fault monitoring personnel can accurately and easily deal with the fault occurrence.

When the integrated fault management device of the present invention is used, it is possible to execute unified fault processing at one place for information communication processing devices of different types such as different manufacturers.

When the fault integrated management device of the present invention is used, a method is adopted in which only fault information that needs to be dealt with is taken and the solution is taken, so that efficient fault management can be executed.

[Brief description of the drawings]

FIG. 1 is a principle configuration diagram of the present invention.

FIG. 2 is an embodiment of the present invention.

FIG. 3 is a data structure diagram of a failure information registration table.

FIG. 4 is a data structure diagram of a failure information selection table.

FIG. 5 is a processing flow executed by a first monitoring program.

FIG. 6 is a processing flow executed by a second monitoring program.

FIG. 7 is a processing flow executed by a management program.

FIG. 8 is a processing flow executed by the interactive program.

FIG. 9 is a processing flow executed by a search program.

FIG. 10 is an explanatory diagram of a database.

FIG. 11 is an explanatory diagram of a main database.

FIG. 12 is an explanatory diagram of a database.

FIG. 13 is an explanatory diagram of a use form of a know-how database.

FIG. 14 is an explanatory diagram of a use form of a know-how database.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Fault integrated management apparatus 2 Network 3 Information communication processing apparatus 4 Terminal 10 Receiving means 11 Conversion means 12 Judgment means 13 Display means 14 First input means 15 First database 16 Second input means 17 Second database 18 Registration Means 19 Search means

Claims (4)

[Claims] 1. A fault integrated management device for integrally managing faults occurring in a plurality of information communication processing devices connected via a network, wherein when the fault information is notified from the information communication processing device, the fault integrated management device performs the fault management. Display means for displaying information on a display, first input means for inputting troubleshooting information input in response to the display processing of the display means, and a correspondence relationship between the troubleshooting information and the troubleshooting information, A first database that manages the data of the failure information as keys, a second input unit that inputs know-how key data that is input in association with the troubleshooting information and is associated with the key data, A second database for managing a correspondence relationship between the failure information and the troubleshooting information in association with the know-how key data; Joint management device. 2. The integrated fault management device according to claim 1, further comprising: a determination unit configured to determine whether or not the failure information notified from the information communication processing device needs to be dealt with. An integrated fault management device, characterized in that the fault information is processed to be displayed on a display on condition that the determining means determines that the fault information needs to be dealt with. 3. The fault integrated management device according to claim 2, wherein when the information communication processing device is configured by a different system, the fault information notified from the information communication processing device is converted into a unified format. Conversion means, wherein the determination means processes the failure information converted by the conversion means as a determination target so as to determine whether or not the failure information notified from the information communication processing device needs to be dealt with. An integrated fault management device. 4. The fault integrated management apparatus according to claim 1, wherein when the key data is input, the first and second databases are searched to register the key data in the database. A failure integrated management device comprising: a search unit that reads failure handling information indicated by the key data when determining whether the key data has been registered.