JP2003152722A - Fault information display system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a fault information display system that can prevent screen display from being complicated due to duplicate displays of fault occurrence notices of subordinate network devices on the occurrence of a fault in a host network device. SOLUTION: The fault information display system includes: steps c1 to c9 of storing a resource name (identification information) of a network device in which a fault takes place to a fault information list table 10, temporarily inhibiting fault display of network devices whose resource names are host resource names of the faulty network device; and steps c11 to c15 of deleting the fault information of the network device whose fault is restored from the fault information list table 10 and executing again the fault display of the network devices whose resource names are host resource names of the faulty network device. Thus, the system can prevent the fault occurrence notice of the subordinate network device from being displayed in duplicate with the fault occurrence notice of the host network devices and displays the fault occurrence notice of the subordinate network device once more after the fault of the host network devices is recovered.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an improvement of a fault information display system for informing an operator of a fault occurring in a network device connected on a network.

[0002]

2. Description of the Related Art As a fault information display system of this type, a system for collectively displaying all fault information notified from a network device to a monitoring terminal on the network has already been disclosed in, for example, Japanese Patent Laid-Open No. 59-154558. Proposed.

[0003]

However, in general, in a network device connected to a computer network, a large number of devices are hierarchically connected in a master-slave relationship, and a fault occurs in a network device higher in the hierarchy. When an error occurs, the error is usually detected in the lower network device due to the error.

In the conventional fault information display system as disclosed in Japanese Patent Laid-Open No. 59-154558, all the fault occurrence notifications output from each network device are collectively displayed on the monitoring terminal. As mentioned above, even if the lower network device fails due to the failure of the upper network device, there is no problem in itself in the many lower network devices. The fault will be displayed on the monitoring terminal,
In some cases, the number of failure notifications displayed in a batch becomes too large, making it difficult to identify a network device that actually has a problem.

[0005]

SUMMARY OF THE INVENTION Therefore, an object of the present invention is to solve the above-mentioned drawbacks of the prior art and to display a large amount of failure occurrence notifications of lower network devices when a higher network device fails. It is to provide a fault information display system capable of preventing the screen display from becoming complicated.

[0006]

The present invention is a fault information display system for detecting a fault in a network device connected to a computer network. In order to achieve the above object, the present invention is particularly connected to a network. A configuration information database that stores the master-slave relationship of network devices according to the correspondence relationship of the identification information of each network device, a failure occurrence notification and a failure recovery notification output together with the identification information from the network device, and the failure occurrence notification is received. If the identification information of the network device on the upper side of the network device having the received identification information exists, the presence or absence of the identification information of the network device on the upper side is received. The specified identification information and the identification information of the higher-level network device and a failure notification. On the other hand, if there is no identification information of the higher-level network device, the received identification information and failure occurrence notification are output, and if a failure recovery notification is received, the received identification information and failure recovery notification are output. A fault information management unit, a fault information list table that stores the identification information of the faulty network device, the identification information of the higher-level network device, and the execution / non-execution of the fault occurrence display, and the fault information management. When the failure occurrence notification and the failure recovery notification output from the unit are received and the failure occurrence notification is received, it is determined whether or not the failure occurrence notification is accompanied by the identification information of the higher-level network device. However, if the identification information of the network device on the upper side is attached, the received identification information and the identification information of the network device on the upper side are associated with each other, and the failure information list table is displayed. The execution information of failure occurrence display is stored by adding to the failure information display table, while the received identification information is added to the failure information list table while the execution information of failure occurrence display is stored However, whether or not the identification information of the network device storing the received identification information as the identification information of the upper network device is stored in the failure information list table regardless of the presence or absence of the identification information of the upper network device. Of the network device that stores the received identification information as the identification information of the higher-level network device, and stores the received identification information as the identification information of the higher-side network device, if the identification information of the network device is stored. It stores the non-execution of the failure occurrence display corresponding to the identification information, and when the failure recovery notification is received. The identification information of the network device that deletes the data related to the identification information stored in the failure information list table by using the received identification information as the identification information, and stores the received identification information as the identification information of the upper network device. Is stored in the failure information list table, and if the received identification information is stored as the identification information of the upper network device, the received identification information is stored in the higher order. A failure display determination unit that stores the execution of the failure occurrence display corresponding to the identification information stored in the failure information list table as the identification information of the network device on the side, and the execution of the failure occurrence display is stored from the failure information list table. It is characterized in that a failure display section for displaying only the identified identification information and displaying the failure occurrence notification on the display means is provided. It has a configuration to be.

First, when a failure occurs in a network device connected on the network, this network device outputs a failure occurrence notification together with identification information. Then
The fault information management unit that receives the identification information and the fault occurrence notification from the network device searches the configuration information database that stores the master-slave relationship of the network devices connected to the network by the correspondence relationship of the identification information of each network device, The presence / absence of the identification information of the network device on the upper side of the network device having the received identification information is determined. Then, if there is the identification information of the upper network device, the failure information management unit outputs the received identification information, the identification information of the upper network device, and the failure occurrence notification, and also identifies the upper network device. If there is no information, the failure information management unit outputs the received identification information and failure occurrence notification. Next, the failure display determination unit that has received the failure occurrence notification from the failure information management unit determines whether or not the identification information of the higher-order network device is attached to this failure occurrence notification, and If the identification information is attached, the received identification information and the identification information of the upper network device are associated with each other and added to the fault information list table to store the execution of the fault occurrence display. If the identification information is not added, the received identification information is added to the failure information list table and the execution of the failure occurrence display is stored. The failure display determination unit further determines whether or not the identification information of the network device in which the received identification information is stored as the identification information of the higher-level network device is stored in the failure information list table,
If the identification information of the network device that stores the received identification information as the identification information of the higher-level network device is stored, the received identification information is used as the identification information of the network device that is stored as the identification information of the higher-level network device. The non-execution of the failure occurrence display is stored correspondingly. As a result, of the network devices that have been stored as faulty until then, the fault occurrence display of the lower network device that is confirmed to have a fault in the upper network device is temporarily prohibited. It on the other hand,
When the fault of the network device connected on the network is recovered, the fault recovery notification is output from this network device together with the identification information, and the fault information management unit that receives this outputs the identification information and the fault recovery notification. Next, the failure display determination unit that has received the failure recovery notification from the failure information management unit deletes the data related to the identification information stored in the failure information list table using the received identification information as the identification information. As a result, the failure recovery of the network device corresponding to the received identification information is stored in the failure information list table. The failure display determination unit further determines whether or not the identification information of the network device in which the received identification information is stored as the identification information of the higher-level network device is stored in the failure information list table. Then, if the identification information of the network device that stores the received identification information as the identification information of the upper network device is stored, the failure display determination unit determines the received identification information as the identification information of the upper network device. The execution of the failure occurrence display is stored in association with the identification information stored in the failure information list table. As a result, the fault occurrence display of the lower network device of the fault-restored network device is allowed again. Then, finally, the failure display unit selects only all the identification information in which the execution of the failure occurrence display is stored from the failure information list table and displays the failure occurrence notification on the display unit. As described above, of the network devices that have a master-slave relationship, if a failure of the upper network device is detected after the failure of the lower network device, a failure of the lower network device is detected. Occurrence indication is temporarily prohibited and only the fault occurrence indication of the upper network device is executed, and when the fault of the upper network device is recovered, the fault occurrence indication of the upper network device is terminated and the Since the failure occurrence of the upper network device is re-displayed, it is possible to hide the failure occurrence notification of the lower network device due to the failure of the upper network device and prevent the screen display from becoming complicated. it can.

Further, it is desirable that the failure display section is provided with a failure display automatic updating function for automatically updating the display of the failure occurrence notification on the display means after the failure display determination section is activated.

By applying such a configuration, the failure occurrence notification of the display means is automatically transmitted in real time in synchronization with the operation of the failure indication determination unit, that is, the output of the failure occurrence notification or the failure recovery notification from the network device. You will be able to update.

Further, the fault display section can be provided with a fault collective display function for selecting all of the identification information stored in the fault information list table and displaying a fault occurrence notice on the display means.

By adding such a function, even before the failure of the network device on the upper side is recovered, the failure occurrence notification from the network device on the lower side detected in advance is transmitted by the conventional failure. It is possible to confirm with the same screen display as the information display system.

The configuration information database, the failure information management unit, the failure information list table, the failure display determination unit, and the failure display unit may be provided in a single computer connected to the network.

When such a configuration is applied, there is an advantage that the hardware resources required for constructing the fault information display system are saved.

Further, the configuration information database and the failure information management unit are arranged in the first computer connected to the network, and the failure information list table, the failure display determination unit and the failure display unit are connected to the network. The configuration may be such that it is deployed in the second computer.

When such a configuration is applied, the load on the first and second computers constructing the fault information display system is reduced, so that it is possible to handle a large-scale network system without difficulty. Become.

[0016]

DETAILED DESCRIPTION OF THE INVENTION Embodiments of the present invention will be described in detail below with reference to the drawings. FIG. 1 is a functional block diagram showing an outline of a fault information display system of an embodiment to which the present invention is applied.

The fault information display system 1 of this embodiment is
As shown in FIG. 1, a first computer 3 (hereinafter referred to as a manager) connected to a computer network 2, a second computer 4 (hereinafter referred to as a monitoring terminal), and a monitoring terminal 4 are connected. The display means 5 such as a CRT display is used.

Each of the manager 3 and the monitoring terminal 4 is a CPU as a calculation means, a ROM storing a starting program, a RAM for temporarily storing calculation data, a hard disk used for storing an OS and storing data and the like. It can be constituted by an ordinary personal computer provided with the non-volatile storage means, or a workstation or the like.

Of these, in the non-volatile storage means of the manager 3, the master-slave relationship between other computers connected to the computer network 2 and network devices A, B, C, ... A configuration information database 6 stored according to the correspondence of identification information of A, B, C, ... (Hereinafter, referred to as resource name) is stored.

Here, an example of the master-slave relationship of the network devices A, B, C, ... Connected on the computer network 2 is shown in FIG. 2, and the configuration information database 6 corresponding to the master-slave relationship of FIG. An example is shown in FIG.

In the example shown in FIG. 2, network devices A, F and I are connected to the highest layer connected to the computer network 2, network devices B and C are further subordinate to the network device A, and network devices are further connected to the network. Device C
Network devices D and E are connected to the lower level of.
Further, network devices G and H are connected to the subordinate of the network device F, network devices J and M are connected to the subordinate of the network device I, and network devices K and L are further subordinate to the network device J. It is connected.

The configuration information database 6 which stores these master-slave relationships stores only the master-slave relationship between the two network devices which are immediately adjacent to each other vertically when the hierarchy is vertically divided as shown in FIG. 3, for example. . That is, according to the storage method of FIG. 3, there is no network device located above the network device A, the network device A is located above the network devices B and C, and above the network devices D and E. Means that the network device C is located.

Further, as shown in FIG. 1, each of the network devices A, B, C, ... Has a fault detection section 7 for detecting the occurrence and restoration of a fault in each network device, and a fault detection unit. An agent 8 for outputting a failure occurrence notification or a failure recovery notification together with a resource name specific to the network device A, B, C, ... According to the operating state of the unit 7 is provided. The failure detection unit 7 is substantially configured by a self-diagnosis program or the like that is repeatedly executed by the OS or application program of each network device A, B, C, ... Each network device A, B, C, ...
Is a part of the OS, and is repeatedly executed at predetermined intervals by the processing on the OS side.

FIG. 4 is a flow chart showing an outline of the fault notification processing executed by the agent 8.

First, each network device A, B,
In the state where no fault has occurred in C, ..., The value of the fault detection flag F is held in the reset state. Therefore, the agent 8 makes a determination in step a1 and step a5 in the fault notification process in each predetermined cycle. The process is only executed repeatedly, and no substantial process is performed.

Here, the network device A,
When a failure such as B, C, ..., For example, a failure such as a bad response of an internal device or a bus error is detected, the agent 8 detects the failure from the failure detection unit 7 in the determination processing of step a1. Receive notifications.

Next, the agent 8 judges whether or not the failure detection flag F is set (step a
2) Only when the failure detection flag F is not set, the resource name unique to the network device A, B, C, ... And the failure occurrence notification are output to the manager 3 (step a3). The failure detection flag F is set (step a4).

After that, the determination result of step a1 continues to be true until the failure is recovered. However, at this stage, the failure detection flag F has already been set, so that the resource name for one failure occurs. The failure notification will not be output twice.

When the fault is recovered by the fault recovery work by the operator or the self-repair work (restart process at the time of abnormality detection), the agent 8 performs the fault recovery from the fault detection unit 7 in the determination process of step a1. Receive notifications.

Next, the agent 8 determines whether or not the failure detection flag F is set (step a5), but the failure detection flag F is held in the set state immediately after the failure recovery. Therefore, the agent 8 outputs the resource name and the failure recovery notification unique to the network devices A, B, C, ... To the manager 3 (step a6) and resets the failure detection flag F (step a6). a7) Then, the process again returns to the initial standby state of waiting for the failure detection by the failure detection unit 7, that is, the repetition of the determination process of steps a1 and a5.

On the other hand, the fault information management section 9 of the manager 3
Is substantially configured by a failure management process that the CPU of the manager 3 repeatedly executes at predetermined intervals.

FIG. 5 is a flow chart showing an outline of the failure management processing executed by the CPU of the manager 3 functioning as the failure information management unit 9 at predetermined intervals.

Each network device A, B, C, ...
Since no failure occurrence notification or failure recovery notification from the network devices A, B, C, ... Is detected in the state where no failure has occurred in, the CPU of the manager 3 that functions as the failure information management unit 9 Step b1, for each predetermined cycle
Only the determination process of step b7 is repeatedly executed, and no substantial process is performed.

Here, the network devices A, B, C, ...
.. When the failure occurrence notification output from and the input of the unique resource name are detected in the determination processing in step b1, C of the manager 3 functioning as the failure information management unit 9 is detected.
The PU reads this resource name (step b2),
By searching the configuration information database 6 as shown in FIG. 3 (step b3), it is determined whether or not the resource name of the higher-level network device corresponding to the network device of the input resource name is stored ( Step b
4).

If the resource name of the higher-level network device is stored in the configuration information database 6,
CPU of manager 3 functioning as fault information management unit 9
Outputs the resource name read in the process of step b2, the resource name of the upper network device detected in the process of step b3, and the failure occurrence notification to the monitoring terminal 4 (step b5), while outputting the upper network If the resource name of the device is not stored in the configuration information database 6, only the resource name read in the process of step b2 and the failure occurrence notification are output to the monitoring terminal 4 (step b6).

Therefore, for example, when the fault occurrence notification and the unique resource name B are input from the network device B having the network device A on the upper side, step b2
Resource name B read in the process of step b3 and step b3
The resource name A of the network device on the upper side and the fault occurrence notification detected by the processing of step 1 are output to the monitoring terminal 4, and the fault notification and the unique occurrence notification are issued from the network device A not equipped with the network device on the upper side. When the resource name A is input, only the resource name A read in the process of step b2 and the failure occurrence notification are output to the monitoring terminal 4.

On the other hand, network devices A, B,
When it is detected in the determination processing in step b7 that the failure recovery notification output from C, ... And the unique resource name are input, the CPU of the manager 3 that functions as the failure information management unit 9 This resource name is read (step b8), and the resource name read in the process of step b8 and the failure recovery notice are output to the monitoring terminal 4 (step b9).

In the nonvolatile storage means of the monitoring terminal 4, the resource name of the faulty network device and the resource name of the network device located on the upper side of the faulty network device and the fault occurrence display are executed.
A failure information list table 10 for storing non-execution in association with each other is provided.

FIG. 7A is a conceptual diagram showing an example of the failure information list table 10. The fault information list table 10 is stored in a resource name column for storing a resource name of a network device in which a fault has occurred, and a resource name column, as shown in FIG. 7A, for example. A high-level resource name column for storing the resource name of the network device located on the high-order side of the network device, and a display for storing execution / non-execution of the fault occurrence display of the network device stored in the resource name column The necessary number of pieces of information of one record composed of three data fields in the mark field is stored. Further, rewriting of information in each data field, batch deletion of data in a specific record, and the like are executed according to a command from the CPU of the monitoring terminal 4.

The monitoring terminal 4 further stores the failure occurrence and restoration status related to the network devices A, B, C, ... The failure information determination unit 11 for performing file operations required to store execution / non-execution of display, and only the resource name of the record in which execution of failure display is stored are displayed in the failure information list table 1
A failure display section 12 for selecting from 0 and displaying on the display means 5 is provided. The failure display determination unit 11 and the failure display unit 12 are substantially configured by a failure display process repeatedly executed by the CPU of the monitoring terminal 4 in every predetermined cycle.

FIG. 6 is a flow chart showing an outline of the failure display processing executed by the CPU of the monitoring terminal 4 functioning as the failure display determination section 11 and the failure display section 12 at predetermined intervals.

First, when the failure occurrence notification or the failure recovery notification from the manager 3 is not input, the CPU of the monitoring terminal 4 functioning as the failure display judging section 11 makes the judgment processing in steps c1, c11 and c16. Is only repeatedly executed, and no substantial processing is performed.

When it is detected in step c1 that the failure notification is input from the manager 3, the CPU of the monitoring terminal 4 functioning as the failure display judging section 11 reads this resource name. (Step c
2), step c2 in the resource name column of the latest record of the failure information list table 10 as shown in FIG.
The resource name read in the processing of 1 is additionally stored (step c3), and the execution of the failure occurrence display is stored in the display mark column of this record (step c4).

Next, the CPU of the monitoring terminal 4 which functions as the failure display judging section 11 judges whether or not the resource name read in the process of step c2 and the resource name of the higher-order network device are added ( Step c
5) Only when the resource name of the higher-level network device is attached, the resource name of the higher-level network device is stored in the higher-level resource name column in the same record (step c6). If the resource name of the higher-level network device is not added, the process of step c6 is not executed.

FIG. 7A shows an example in which a fault occurrence notification is input from the network device B. Since the fault occurrence notification of the network device B is given the resource name A of the higher-level network device by the process of the manager 3, the determination result of step c6 is true, and the resource of the latest record of the fault information list table 10 is set. The resource name B is stored in the name column, and the resource name A is stored in the upper resource name column of this record.
The execution of the failure occurrence display is stored in the display mark column of this record.

Next, the CPU of the monitoring terminal 4 functioning as the failure display judging section 11 searches the upper resource name column of all the records in the failure information list table 10 (step c7) and reads it in the processing of step c2. However, it is determined whether or not there is a record in which the resource name, that is, the resource name corresponding to the network device in which the failure has been detected in this processing is stored as the higher-level resource name (step c8). Then, only when a record in which the resource name corresponding to the network device in which the failure has been detected is stored as the upper resource name is detected in this process, all records in which this resource name is stored as the upper resource name are detected. The non-execution of the failure occurrence display is stored in the display mark column (step c9). If no record is stored in which the resource name corresponding to the network device in which the failure has been detected in this process is stored as the higher-level resource name, the process in step c9 is not executed.

In the example of FIG. 7A, the resource name corresponding to the network device in which the failure has been detected in this process, that is, the record in which the resource name B is stored in the upper resource name column is not detected. , Step c9 is not executed.

Next, the CPU of the monitoring terminal 4 functioning as means for realizing the function of automatically updating the failure display of the failure display unit 12,
The resource of the record for which all records in the failure information list table 10 are searched, the record in which the execution of the failure occurrence display is stored in the column of the display mark is selected, and the execution of the failure occurrence display is stored in the column of the display mark Only the resource name stored in the name column is displayed on the display means 5 as the network device in which the failure has occurred (step c10).

As the comment displayed on the display means 5,
For example, it is possible to use a "resource name X" failure occurrence ". Here, the "resource name X" is a variable, and the single or plural resource names selected in the process of step c10 are substituted into this variable. Figure 7
In the example of (a), the only record in which the execution of the failure occurrence display is stored in the display mark column is the first record,
Since the resource name stored in the resource name column of the first record is the resource name B, the comment "resource name B failure has occurred" is displayed on the display means 5.

After that, if the failure occurrence notification and the failure recovery notification are not input again from the manager 3, the CPU of the monitoring terminal 4 functioning as the failure display determination unit 11 performs the step c1 in the failure display process in the same manner as described above. Since only the determination process of step c11 and step c16 is repeatedly executed, the display state of the display unit 5 does not change, and, for example, a comment such as “resource name B failure occurred” continues to be displayed.

While the CPU of the monitoring terminal 4 repeatedly executes only the determination processes of steps c1, c11 and c16 in this way, the fact that the fault occurrence notification is input from the manager 3 is input again at step c1. When detected by the determination processing, the CPU of the monitoring terminal 4 that functions as the failure display determination unit 11 repeatedly executes the same processing as described above. Here, as an example, the network device B
A case will be described in which a failure occurrence notification is input from the network device A located on the upper side of the.

When the failure occurrence notification is input from the network device A, the CPU of the monitoring terminal 4 functioning as the failure display determination unit 11 reads the resource name A (step c2) and updates the latest record in the failure information list table 10. The resource name A read in the process of step c2 is added and stored in the resource name column of step (c3), and the execution of the failure occurrence display is stored in the display mark column of this record (step c4). .

Next, the CPU of the monitoring terminal 4 functioning as the failure display judging section 11 judges whether or not the resource name A read in the process of step c2 is added with the resource name of the higher-level network device. (Step c
5). However, since the fault occurrence notification of the network device A is not added with the resource name of the higher-level network device by the process of the manager 3, the determination result of step c5 is false and the process of step c6 is not executed. Thus, the upper resource name column in the latest record is held in a blank state as shown in FIG. 7 (b).

Next, the CPU of the monitoring terminal 4 functioning as the failure display determination section 11 searches the upper resource name column of all records in the failure information list table 10 (step c7), and reads it in the processing of step c2. However, it is determined whether or not there is a record in which the resource name, that is, the resource name A corresponding to the network device in which the failure has been detected in this processing is stored in the upper resource name column (step c8).

In this case, since the resource name A is already stored in the upper resource name column of the first record, the judgment result in step c8 becomes true, and as shown in FIG. In the display mark column of the first record in which the resource name A corresponding to the network device in which the occurrence of a fault is detected is stored in the upper resource name column, non-execution of the fault occurrence display is stored (step c9). ).

Next, the CPU of the monitoring terminal 4 functioning as means for realizing the failure display automatic update function of the failure display unit 12
All the records in the failure information list table 10 are searched, and all the records in which the execution of the failure occurrence display is stored in the display mark column are selected, and the records of which the execution of the failure occurrence display is stored in the display mark column are selected. Only the resource name stored in the resource name column is displayed on the display means 5 as the network device in which the failure has occurred (step c1).
0).

In this case, as shown in FIG. 7C, the second record is the only record in which the execution of the failure occurrence display is stored in the display mark column, and the resource name column of this second record is stored. Since the resource name A is stored, the resource name A displayed up to that time is displayed by the process of step c10 executed by the CPU of the monitoring terminal 4 that functions as the failure display automatic update function implementing means of the failure display unit 12. The comment “B failure occurred” is automatically deleted, and instead, the comment “Resource name A failure occurred” is displayed on the display unit 5.

After that, if the failure occurrence notification and the failure recovery notification from the manager 3 are not input again, the CPU of the monitoring terminal 4 functioning as the failure display determination section 11 performs the steps c1, c11 and step in the same manner as described above. c
Since only the determination process of 16 is repeatedly executed, the display state of the display unit 5 does not change, and the comment of “resource name A failure has occurred” continues to be displayed.

Then, in this way, the CP of the monitoring terminal 4 is
When the determination processing of step c11 detects that the failure recovery notification from the manager 3 is input while U repeatedly executes only the determination processing of steps c1, c11, and c16, the failure display determination unit 11 The CPU of the monitoring terminal 4 that functions as the resource name reads the resource name (step c12), and uses the resource name read in the process of step c12 from the failure information list table 10 as shown in FIG. The data of the records stored in the column are collectively deleted (step c13).

FIG. 7D shows an example in the case where a failure recovery notice is input from the network device A. In this case, the failure information list table in the state as shown in FIG. 7C. The data included in the second record in which the resource name A is stored in the resource name column from 10 is collectively deleted, and the contents of the failure information list table 10 are changed to those in FIG.
It will be updated to the state as shown in (d).

Next, the CPU of the monitoring terminal 4 functioning as the failure display judging section 11 searches the upper resource name column of all the records in the failure information list table 10, and reads the resource name read in the processing of step c12, that is, Then, it is judged whether or not there is a record in which the resource name corresponding to the network device in which the failure recovery is detected in this processing is stored in the upper resource name field (step c14), and the failure recovery is performed in this processing. Only when a record in which the resource name corresponding to the detected network device is stored in the upper resource name column is detected, the failure display is displayed in the display mark column of the record in which this resource name is stored as the upper resource name. The execution is stored (step c15). If no record is stored in which the resource name corresponding to the network device in which the restoration of the failure is detected in this process is stored as the higher-level resource name, the process in step c15 is not executed.

In the example of FIG. 7D, the resource name corresponding to the network device in which the restoration of the fault is detected in this process, that is, the record in which the resource name A is stored in the upper resource name column is the fault information list. Since it exists in the first record of the table 10, execution of the failure occurrence display is stored in the display mark column of this first record, as shown in FIG. 7 (e).

Next, the CPU of the monitoring terminal 4 which functions as means for realizing the function of automatically updating the failure display of the failure display unit 12,
The resource of the record in which the execution of the failure occurrence display is stored in the display mark column is selected by searching all the records in the failure information list table 10 Only the resource name stored in the name column is displayed on the display means 5 as the network device in which the failure has occurred (step c10).

In this case, as shown in FIG. 7E, the record in which the execution of the failure occurrence display is stored in the column of the display mark is only the first record, and the column of the resource name of this first record is shown. Since the resource name B is stored, the resource name B that has been displayed until then is displayed by the process of step c10 executed by the CPU of the monitoring terminal 4 that functions as the failure display automatic update function realizing means of the failure display unit 12. The comment “A failure has occurred” is automatically deleted, and instead, the comment “Resource name B failure has occurred” is displayed on the display means 5.

Thereafter, if the failure occurrence notification or the failure recovery notification from the manager 3 is not input again, the CPU of the monitoring terminal 4 functioning as the failure display determination section 11 performs the step c1 in the failure display processing in the same manner as described above. Since only the determination process of step c11 and step c16 is repeatedly executed, the display state of the display unit 5 does not change, and, for example, a comment such as “resource name B failure occurred” continues to be displayed.

Here, if the cause of the failure of the network device B is the failure of the upper network device A, the failure of the network device A is automatically recovered by the failure recovery of the network device A. May be recovered.

In such a case, the failure recovery notification and the resource name B input from the network device B to the monitoring terminal 4 via the manager 3 are detected by the CPU of the monitoring terminal 4 in the judgment processing of step c11 in the failure display processing. Therefore, the data of the first record in which the resource name B is stored in the resource name column is collectively deleted from the failure information list table 10 in the state as shown in FIG. By the process of step c10 performed with reference to the list table 10, the comment "resource name B failure has occurred" is automatically deleted from the screen of the display unit 5.

Thereafter, in the same manner as described above, when it is detected in the determination processing in step c1 that the failure occurrence notification from the manager 3 is input, the CPU of the monitoring terminal 4 functioning as the failure display determination unit 11 In the same manner as described above, the processes of steps c2 to c9 are repeatedly executed, and when it is detected in the determination process of step c11 that the failure recovery notification from the manager 3 is input, the failure display determination unit C of the monitoring terminal 4 functioning as 11
The PU repeatedly executes the processing in steps c12 to c15 in the same manner as described above. Then, every time the processing by the failure display determination unit 11 is executed in this way, the CPU of the monitoring terminal 4 functioning as the failure display automatic update function realizing means of the failure display unit 12 performs the failure information list in the processing of step c10. The table 10 is searched, and only the resource name stored in the resource name column of the record in which the display of the fault occurrence display is stored in the display mark column is re-displayed as the faulty network device on the display means 5 again. It is displayed and the failure notification of the display means 5 is automatically updated in real time.

Therefore, in the case where a fault occurs in the higher-order network device next to the fault occurrence in the lower-order network device among the network devices having the master-slave relationship, the fault occurrence in the lower-order network device occurs. When the display is temporarily prohibited and only the failure display of the upper network device is executed, and when the failure of the upper network device is recovered, the failure of the lower network device that was prohibited until then The occurrence display will be executed again.

In this way, by not displaying the failure occurrence notification of the lower network device due to the failure of the upper network device, the screen display on the display means 5 is prevented from being complicated. The operator can promptly check the occurrence status of the failure.

Further, when the fault of the upper network device is restored, the fault of the lower network device is displayed again, and further, the fault of the lower network device is recovered by the fault recovery of the upper network device. Since the failure display of No. 1 is automatically deleted, the operator can accurately specify the actual network device having the problem and perform the recovery work.

The general procedure for recovery work in this type of network system is to remove the fault of the upper network equipment that may affect the lower network equipment, and operate the upper network equipment normally. After doing so, it is normal to check the presence or absence of failures in individual network devices located on the lower side,
As in the present embodiment, a failure in which the failure occurrence of the network device located on the upper side in the master-slave relationship of the network connection is preferentially displayed and the failure of the network device on the lower side is again displayed after the failure is recovered. The information display system 1 is easy to use from the viewpoint of actual operation.

Further, in the fault information display system 1 of the present embodiment, if necessary, similar to the conventional fault information display system, a list display of all the network devices having a fault at that time is displayed. It is also possible.

In this case, the operator uses the keyboard or the like provided in the monitoring terminal 4 and the C of the monitoring terminal 4 which functions as a means for implementing the failure batch display function of the failure display unit 12.
Input the command for displaying all records to PU.

The command for displaying all cases is the CP of the monitoring terminal 4 in the judgment processing of step c16 in the failure display processing of FIG.
The CPU detected by U and detecting this refers to the failure information list table 10 and displays the resource name field of each record in the resource name field regardless of whether or not the execution of the failure occurrence display is stored in the display mark field. All the stored resource names are displayed on the display means 5 (step c17).

Therefore, for example, the failure information list table 1
When the content of 0 is under the situation as shown in FIG. 7C, that is, the failure of the upper network device A is detected after the failure of the lower network device B, and only the failure of the network device A is detected. If the operator inputs a command for displaying all records under the situation where is displayed, "resource name B failure occurred" and "resource name B failure occurred" are displayed instead of the comment "resource name A failure occurred" that was displayed up to that point. Resource name A
The comment "occurrence of failure" is simultaneously displayed on the display means 5.

As described above, as one embodiment, the manager 3 and the monitoring terminal 4 constitute the failure information display system 1, and the manager 3 has the configuration information database 6 and the failure information management unit 9 while the monitoring terminal 4 An example in which the failure information list table 10, the failure display determination unit 11, and the failure display unit 12 are provided on the side and the display means 5 is connected has been described.
Configuration information database 6, failure information management unit 9, failure information list table 10, failure display determination unit 11, failure display unit 1
All of the two 2 are arranged in a single computer (for example, the monitoring terminal 4) on the computer network 2 and the display means 5 is provided.
May be connected.

In this case, the configuration information database 6 and the fault information list table 10 are built in the non-volatile storage means of the single computer, and the fault management of FIG. The processing and the failure display processing of FIG. 6 for realizing the functions of the failure display determination unit 11 and the failure display unit 12 are performed by the CPU of the single computer.
Will be executed substantially in parallel as the multi-task processing. Regarding the transfer of data from the failure information management unit 9 to the failure display determination unit 11, the output target data of steps b5, b6, and b9 in the failure management process is stored in the RAM of the single computer (hereinafter referred to as a data storage area). In the sense that both the failure information management unit 9 and the failure display determination unit 11 can access it, this data storage area is temporarily held in a shared RAM), and the failure display is executed in the processing cycle. In the processing of steps c1 and c11 in the processing, the above-mentioned output target data is read from the shared RAM, the failure display processing is executed in the same manner as described above, and the data in the shared RAM is erased at the end of the failure display processing in the processing cycle. You can do it.

Configuration information database 6, failure information management section 9, failure information list table 10, failure display determination section 11,
If the configuration in which all of the failure display unit 12 is centrally deployed in a single computer on the computer network 2 is applied, there is an advantage that the hardware resources required for constructing the failure information display system 1 are saved. ,Also,
Configuration information database 6, failure information management unit 9, failure information list table 10, failure display determination unit 11, failure display unit 1
When the configuration in which 2 is distributed to a plurality of computers is applied, there is an advantage that the load of the computer configuring the fault information display system 1 is reduced and a large-scale network system can be dealt with.

[0080]

According to the fault information display system of the present invention, when a fault occurs in a higher-order network device after a fault occurs in a lower-order network device among network devices having a master-slave relationship, Temporarily prohibit the fault occurrence display of the lower network device and execute only the fault occurrence display of the upper network device, and the fault of the lower network device occurs after the fault of the upper network device is recovered. Since it is prevented from being complicated by displaying the failure notification screen again, the operator can promptly check the failure occurrence status.

Further, since the display of the failure occurrence notification on the display means is automatically updated every time the failure occurrence notification or the failure recovery notification is confirmed, the failure occurrence notification or the failure recovery notification from the network device is transmitted. It is possible to check the failure occurrence status in real time by linking with the output. Especially, when the failure of the lower network device is automatically recovered in conjunction with the recovery of the failure of the upper network device, the lower network device whose failure is recovered by the failure recovery of the upper network device Since the failure display of is also automatically deleted, it is possible to accurately identify the network device that actually has the problem and perform the recovery work.

Further, since it is possible to collectively display all the failure information regardless of the master-slave relationship of the connection of the network equipment, even if the failure of the network equipment on the upper side is not recovered, it is detected in advance. It is possible to confirm the failure occurrence notification from the lower network device on the same screen display as the conventional failure information display system.

Further, by configuring the fault information display system by a single computer connected on the network, the hardware resources necessary for constructing the system can be saved, and the fault information display system can be displayed by a plurality of computers. By configuring the system, it is possible to reduce the load on each computer that configures the failure information display system and handle a large-scale network system.

[Brief description of drawings]

FIG. 1 is a functional block diagram showing an outline of a fault information display system of an embodiment to which the present invention is applied.

FIG. 2 is a conceptual diagram showing an example of a master-slave relationship between network devices connected on a computer network.

FIG. 3 is a conceptual diagram showing an example of a configuration information database.

FIG. 4 is a flowchart showing an outline of a fault notification process executed by an agent of a network device.

FIG. 5 is a flowchart showing an outline of failure management processing executed by a failure information management unit of the manager.

FIG. 6 is a flowchart showing an outline of fault display processing executed by the CPU of the monitoring terminal.

FIG. 7 is a conceptual diagram showing an example of a failure information list table.

[Explanation of symbols]

1 Fault information display system 2 computer network 3 Manager (first computer) 4 Monitoring terminal (second computer) 5 Display means 6 Configuration information database 7 Fault detector 8 agents 9 Fault Information Management Department 10 Fault information list table 11 Fault display determination unit 12 Fault display A to L network equipment

Claims (5)

[Claims] 1. A fault information display system for detecting a fault of a network device connected to a computer network, wherein a master-slave relationship of network devices connected to the network is determined by a correspondence relationship of identification information of each network device. A configuration information database to be stored, a failure occurrence notification and a failure recovery notification output together with the identification information from the network device, and when the failure occurrence notification is received, the configuration information database is searched and received. The presence or absence of the identification information of the upper network device of the network device having the identified identification information, and if there is the identification information of the upper network device, the received identification information and the identification information of the upper network device and the failure occurrence notification Is output, the identification information of the network device on the upper side must be output. Outputting the identification information and failure notifications field received, and when a failure recovery notification has been received,
The failure information management unit that outputs the received identification information and failure recovery notification, and the identification information of the failed network device and the identification information of the upper network device and the execution / non-execution of the failure occurrence display are stored in association with each other. The failure information list table to be received, the failure occurrence notification and the failure recovery notification output from the failure information management unit, and when the failure occurrence notification is received, the failure occurrence notification indicates the network device on the upper side. It is determined whether or not the identification information is attached, and if the identification information of the upper network device is attached, the received identification information and the identification information of the upper network device are associated with each other in the failure information list table. While additionally storing the execution of the failure occurrence display, if the identification information of the upper network device is not attached, the received identification information is used as the failure information. The identification information of the network device that stores the execution of the failure occurrence display in addition to the list table and stores the received identification information as the identification information of the upper network device regardless of the presence or absence of the identification information of the upper network device. Is stored in the failure information list table, and if the received identification information is stored as the identification information of the upper network device, the received identification information is stored in the higher order. The non-execution of the failure occurrence display is stored corresponding to the identification information of the network device stored as the identification information of the network device on the side, and when the failure recovery notification is received, the received identification information is used as the identification information. Data related to the identification information stored in the failure information list table is deleted, and the received identification information is stored in the upper side network. Network device identification information stored as network device identification information is determined in the failure information list table, and the received identification information is stored as higher-level network device identification information. If the information is stored, the received identification information as the identification information of the higher-level network device is associated with the identification information stored in the failure information list table, and a failure display determination unit that stores the execution of the failure occurrence display, A fault information display system, comprising: a fault display unit that selects only the identification information in which execution of fault display is stored from the fault information list table and displays a fault notification on the display means. 2. The fault display section is provided with a fault display automatic update function for automatically updating the display of the fault occurrence notification of the display means after the fault display determination section is activated. The fault information display system described in 1. 3. The failure display unit has a failure batch display function of selecting all the identification information stored in the failure information list table and displaying a failure occurrence notification on the display means. The fault information display system according to claim 1 or 2. 4. The configuration information database, the failure information management unit, the failure information list table, the failure display determination unit, and the failure display unit are arranged in a single computer connected to the network. Claim 1, Claim 2
Alternatively, the fault information display system according to claim 3. 5. The configuration information database and the failure information management unit are provided in a first computer connected to the network, and the failure information list table, the failure display determination unit and the failure display unit are provided on the network. The fault information display system according to claim 1, wherein the fault information display system is provided in a second computer connected to the.