JPH1013538A - Fault history data structure and network management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a network management system in which whether or not processing has been applied already to a fault occurring in a managed equipment is immediately discriminated. SOLUTION: A fault management equipment 1 managing the operating state of the managed equipment generates fault history data and stores the data to a storage section 6 on the occurrence of a fault in the managed equipment and rewrites processed data into data denoting the fault countermeasure processing when the processing is applied to the object fault, and when the fault manager refers to the stored fault history data, the manager recognizes the presence of processing based on the processed data.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a fault history data structure stored in a fault management device for managing a history of faults of a managed device and a network management system.

[0002]

2. Description of the Related Art In a conventional network management system,
The failure history data has a structure including the date and time when the failure occurred, the number of the device in which the failure occurred, the type of the failure, and the like. The failure history data is stored in the storage unit in the order of the occurrence time. Are known.

[0003]

However, in the above-mentioned conventional case, since a fault is simply recorded and stored, a fault is actually occurring when the stored record is referred to. Not necessarily, there may be cases where a measure has already been taken and has already been treated. Therefore, the trouble manager takes time to check the presence or absence of the trouble, and cannot grasp the period in which the trouble has occurred. However, there is a problem that it is not possible to determine whether or not a plurality of faults are derived from one fault, because the relation of the fault history data is not known.

[0004]

Therefore, the present invention has a failure history data structure provided with a treated data area for storing the presence or absence of a treatment for a target failure. It should be noted that the treated data may be the treated date and time when the treatment for the target failure is performed. Further, the fault management device that manages the operation status of the managed device creates and stores fault history data in the storage unit when a fault occurs in the managed device, and takes measures for the target fault. When a failure is performed, the fact that the treatment was performed is written in the treated data area, and when the trouble manager refers to the accumulated trouble history data, it is possible to recognize the presence or absence of the treatment based on the treated data. Provide a network management system that can be used. The fault management device that manages the operation status of the managed device creates and stores fault history data in the storage unit when a fault occurs in the managed device, and takes measures for the target fault. When the failure is performed, the date and time when the measure was taken is written to the treated date and time data area, and when the trouble manager refers to the accumulated trouble history data, a measure is taken for the trouble based on the treated time and date data. The date and time of the application may be recognized.

[0005]

Embodiments of the present invention will be described below with reference to the drawings. 1. First Embodiment FIG. 1 is a block diagram of a system configuration. In the figure, a failure management device 1 manages a failure history and the like of a managed device 1, a managed device 2, a managed device 3, a managed device 4,... It is like that.

[0006] The fault management device 1 has a control unit 3 connected to each device of the managed device group 2. The control unit 3 controls the entire processing. Further, a failure information collecting unit 4, a failure history processing unit 5, a storage unit 6, and a display unit 7 are connected to the control unit 3. The failure information collection unit 4 collects failure information that has occurred in each device of the managed device group 2,
The fault information is sent to the fault history processing unit 5.

The failure history processing unit 5 edits the failure information as failure history data, stores and stores the failure information in the storage unit 6, and retrieves the failure history data stored in the storage unit 6 as described later. I do. The storage unit 6 includes:
It may be provided on an external storage device or a memory. Next, the failure history data will be described. FIG. 2 is a configuration diagram of the failure history data, and FIG. 3 is an exemplary diagram of the configuration of the failure history data.

In FIG. 2, the structure of the fault history data is composed of treated data, occurrence date and time data, generator data, and fault content data. Note that other data may be added. The treated data is data unique to the present invention, and indicates whether or not a treatment has been performed on a fault that has occurred. For example, if a treatment has been performed, “Y” indicates that the treatment has been performed. If not, "N" is assigned. The occurrence date and time data indicates the date and time when the failure occurred, for example, in the order of year, month, day, and time. The generation device data indicates the number of the device in which the failure has occurred, and is represented here by numerical data of “1”, “2”, “3”,. The fault content data indicates the type of fault that has occurred. For example, α, β, γ,
δ,... types of obstacles.

In FIG. 3, failure history data is assigned a failure history number in the order of occurrence of the failure, and is stored in the storage unit 6 in the order of the failure history data group. For example,
The failure history No. 1 is “Y / X, 1, 1, 13: 00/1 /
α ”, and the managed device at 13:00 on January 1, X
The alpha disorder that occurred in 1 indicates that it has already been treated. In addition, the expression of failure history No. 2 to failure history No. n is as follows.
The description is omitted because it is the same as the failure history No. 1.

Now, a failure management process in which the failure management device 1 manages the managed device group 2 will be described. When the failure management process is operating, the failure information collection unit 4 of the failure management device 1 monitors each device of the managed device group 2 via the control unit 3. That is, for example, the fault information collecting unit 4 sends a signal to each of the managed devices 1 to n at a fixed period, determines whether a fault has occurred by returning the signal, and determines whether the fault has occurred. Collects fault information sent from the managed device where the error has occurred. At this time, in the managed device in which the failure has occurred, the managed device itself may recognize the failure and transmit the failure information to the failure management device 1, or the administrator of the managed device may The failure information may be manually input and transmitted to the failure management device 1 side.

The fault information collecting unit 4 sends the received fault information to a fault history processing unit 5, which edits the fault information and creates the above-described fault history data.
The data is accumulated in the storage unit 6 as a failure history data group. At this time, if the failure has not been recovered, "N" is written in the treated data column as described above, and if the failure has been recovered, "Y" is written.

[0012] When "N" is written in the former treated data column, the corresponding managed device performs a treatment, and the managed device itself recognizes that the treatment has been completed. The administrator of the managed device inputs that processing has been completed, and sends the fact to the fault management device 1 side. Then, the control unit 3 issues a rewriting instruction of the corresponding processed data to the failure history processing unit 5. The failure history processing unit 5 sets the treated data of the corresponding failure history data from the storage unit 6 to “N”.
Is rewritten to “Y”.

On the other hand, the fault history data accumulated as described above can be read and confirmed at any time as follows. In the present invention, a special effect is produced at the time of this confirmation. That is, the failure manager operates an operation unit (not shown),
The display unit 7 displays the failure history data to be confirmed. For example, in FIG. 3, when the failure history data of the failure history No. 3 is displayed on the display unit 7, the fact that the treatment has been completed is displayed on the display unit 7. Further, when the failure history data of the failure history No. 4 is displayed on the display unit 7, it is displayed on the display unit 7 that the treatment has not been completed. For this reason, the failure manager can grasp the failure recovery status of each managed device only by the operation of searching for the failure history data.

According to the first embodiment, the fault manager immediately determines whether or not the fault has been dealt with only by searching for the fault history data.
The effect of being able to grasp the failure recovery status of each managed device is obtained. Further, by displaying the failure history data group and referring to the failure history data group as appropriate, an effect is obtained that a list of failures that need to be dealt with can be immediately grasped. Therefore, according to the present embodiment, it is possible to obtain an effect that the failure manager can quickly and accurately perform the failure management.

Second Embodiment In the above embodiment, as shown in FIG. 4, the configuration of fault history data is composed of treatment completed date / time data, occurrence date / time data, generator data, and fault content data. did.
In particular, the treatment completed date and time data is the date and time when the treatment was performed, and the managed device side has performed the treatment and grasps that the treatment has been completed by the managed device itself, or the administrator of the managed device has performed the treatment. Is input, the date and time when the treatment was performed is recognized by a timer (not shown) or is input by an administrator. Here, the treated date and time data is, for example, “Y, year, month, day, day and time” when the treatment is performed, and “N” when the treatment is performed.
Is given. The other data is the same as in the first embodiment, and a description thereof will not be repeated. The accumulation state of the failure history data is the same as that described with reference to FIG. The same elements will be described with the same reference numerals.

Next, a failure management process in which the failure management device 1 manages the managed device group 2 will be described. When the failure management process is operating, the failure information collection unit 4 of the failure management device 1 monitors each device of the managed device group 2 via the control unit 3. That is, for example, the fault information collecting unit 4 sends a signal to each of the managed devices 1 to n at a fixed period, determines whether a fault has occurred by returning the signal, and determines whether the fault has occurred. Collects fault information sent from the managed device where the error has occurred. At this time, in the managed device in which the failure has occurred, the managed device itself may recognize the failure and transmit the failure information to the failure management device 1, or the administrator of the managed device may The failure information may be manually input and transmitted to the failure management device 1 side.

The failure information collection unit 4 sends the received failure information to the failure history processing unit 5, which edits the failure information and creates the above-described failure history data.
The data is accumulated in the storage unit 6 as a failure history data group. At this time, if the failure has not been recovered, “N” is written in the treated date and time data column as described above, and if the failure has been recovered, the date and time when the treatment was performed, for example,
Write "Y, X, 2,14,24: 00" etc.

When "N" is written in the former treatment completed date / time data column, the corresponding managed device performs the treatment, and determines whether the managed device itself has completed the treatment. Alternatively, the administrator of the managed device inputs that the treatment has been completed, and the date and time when the treatment has been performed is recognized by a timer (not shown) or the administrator inputs the date and time, and the fact is transmitted to the failure management device 1 side. . Then, the control unit 3 issues a rewriting instruction of the corresponding processed date and time data to the failure history processing unit 5. The failure history processing unit 5 stores the processed data of the corresponding failure history data from the storage unit 6,
From "N", for example, "Y, X, 2,14,24: 00" is rewritten.

On the other hand, the fault history data accumulated as described above can be read and confirmed at any time as follows. In the present invention, a special effect is produced at the time of this confirmation. That is, the failure manager operates an operation unit (not shown),
The display unit 7 displays the failure history data to be confirmed. For example, in the case of failure history data that has been treated,
The display unit 7 displays that the treatment has been completed and the date and time of the treatment. If no treatment has been performed, a message indicating that the treatment has not been completed is displayed on the display unit 7. For this reason, the fault manager can grasp the fault recovery status of each managed device together with the recovery date and time only by the operation of searching for the fault history data.

According to the second embodiment, the fault manager immediately determines whether or not the fault has been dealt with only by searching for the fault history data.
The effect of being able to ascertain the failure recovery status of each managed device together with the recovery date and time is obtained, and by being able to ascertain the period during which a failure has occurred, anticipating problems that would have occurred during that period The effect that also becomes possible is acquired. Further, by displaying the failure history data group and referring to the failure history data group as appropriate, an effect is obtained that a list of failures that need to be dealt with can be immediately grasped. Therefore, according to the present embodiment, it is possible to obtain an effect that the failure manager can quickly and accurately perform the failure management.

[0021]

As described above, according to the present invention, the fault manager immediately determines whether or not the fault has been dealt with only by the operation of retrieving the fault history data. The effect of being able to grasp the failure recovery status of the device is obtained. Further, by displaying the failure history data group and referring to the failure history data group as appropriate, an effect is obtained that a list of failures that need to be dealt with can be immediately grasped. Therefore, according to the present embodiment, it is possible to obtain an effect that the failure manager can quickly and accurately perform the failure management. Further, even when there are a plurality of pieces of fault history data of the same managed device, the occurrence period of each fault can be grasped, so that it is possible to determine whether a plurality of faults are derived from one fault or not. The effect of being able to attach can be expected.

[Brief description of the drawings]

FIG. 1 is a block diagram of a system configuration according to an embodiment;

FIG. 2 is a configuration diagram of failure history data.

FIG. 3 is a view showing an example of the configuration of failure history data;

FIG. 4 is a configuration diagram of failure history data;

[Explanation of symbols]

 REFERENCE SIGNS LIST 1 failure management device 2 managed device group 3 control unit 4 failure information collection unit 5 failure history processing unit 6 storage unit 7 display unit

Claims (4)

[Claims] In a fault history data structure having an area for storing the type of fault, the date and time of occurrence of the fault, and the machine number of the managed device, the fault has occurred in any of a plurality of managed devices connected to the fault management device. A failure history data structure, comprising a treated data area for storing the presence or absence of a treatment for a failure. 2. The fault history data structure according to claim 1, wherein the treated data is treated date and time data when the treatment for the target trouble is performed. 3. The failure history data structure according to claim 1, wherein the failure management device that manages the operation status of the managed device creates and stores failure history data when a failure occurs in the managed device. When the fault is treated, the fact that the measure was taken is written to the treated data area, and when the fault manager refers to the stored fault history data A network management system wherein the presence or absence of a treatment can be recognized based on the treated data. 4. The failure history data structure according to claim 2, wherein the failure management device that manages the operation status of the managed device creates and stores failure history data when a failure occurs in the managed device. In addition, when a measure is taken for the target failure, the date and time when the measure was taken is written to the treated date and time data area, and the trouble manager refers to the accumulated trouble history data. At this time, a network management system characterized in that it is possible to recognize the date and time when a fault was treated based on the treated date and time data.