JPH1013536A - Fault information storage display system in network management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce the retrieval time in the case of retrieving fault information by storing fault information distinguished from each user to a server connecting to an exchange node. SOLUTION: A fault information storage database 12 for users A, B connecting to a network is provided to a server connecting to an exchange node and the fault information is stored in the database 12 distinguished from the users A, B. For example, a fault information storage processing section 11 of the user A references a fault display management table on the receipt of fault information and stores only the fault information registered in the table to the fault information storage database 12 for the user A. In the case of displaying the fault information by its own console of the users A, B, each of the users A, B accesses the fault information storage database 12 assigned to itself to display history of the fault information. Thus, in the case of retrieving the fault information from the console for each of the users A, B, each of the users A, B has only to access the database 12 assigned to itself.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for storing and displaying fault information of monitored nodes in a network management system.

[0002]

2. Description of the Related Art Conventionally, a network management system (Network) for monitoring a network node such as a switching device is known.
In the fault information display service in the Management System (hereinafter referred to as NMS), the NMS
The failure information history of the switching node detected in the communication processing between the server and the monitored switching node is stored in the NMS server on the NMS server.
Had accumulated on one database. In addition, a comment on how to deal with a failure has been added to the failure information of the switching node detected by the NMS server and displayed on the NMS console.

[0003]

However, in the above-described conventional network management system, since there is one failure information storage database on the NMS server,
Considering an operation mode in which a line on a switching node is allocated to each user and failure information of the switching node is managed for each user, when searching for failure information from the NMS console for each user, it takes time to search. . Also, when displaying the failure information of the same device on the NMS consoles of different users, the comments given by the NMS are the same.

[0004]

In order to solve the above-mentioned problems, the present invention provides a network management system for managing switching nodes, wherein the network management system displays fault information history for each user who uses the switching nodes. In a fault information storage / display method in a system, a fault information storage database is provided for each user who uses the switching node in a server connected to the switching node, and fault information is stored separately for each user. It is what it was.

[0005]

DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 is a block diagram of an NMS server showing an example of an embodiment of a failure information storage / display method of the present invention in a network management system, and FIG. 2 shows an example of an entire configuration of the network management system. FIG. 2 is a block diagram. First, the overall configuration of the network management system will be described with reference to FIG. Here, FIG. 2 shows a network management system for managing two switching nodes.

[0006] The switching nodes 1A, 1B and the NMS server 2,
NMS consoles 3a, 3b, 3c are Ethernet 4
It is assumed that it is connected to Switching nodes 1A and 1
B notifies the NMS server 2 of failure information using a communication protocol such as SNMP. NMS server 2
Indicates the failure information histories of all monitored devices and the exchange node 1
Failure information histories for each user using A and 1B are stored in separate databases.

The NMS consoles 3a, 3b, 3c include:
The failure information history notified to the NMS server 2 is displayed.
Here, it is assumed that the NMS console 3a displays all failure information of the managed switching nodes 1A and 1B. The NMS console 3b is connected to the switching node 1A,
This is a console for displaying a failure state of the user A using the lines 5a and 5b between the terminals 1B. Further, the NMS console 3c is a console for displaying a failure state of the user B using the line 5c between the switching nodes 1A and 1B.

Next, the configuration and operation of the failure information storage and display processing function of the NMS server 2 will be described with reference to FIG. The exchange node communication processing unit 6 in the NMS server 2 receives the failure information of the monitored node, here the exchange nodes 1A and 1B described in FIG. The content of the failure information is
It is composed of a failure occurrence location such as a device or package name, a failure occurrence date and time, and the like.

When the failure information is received by the exchange node communication processing unit 6, the failure information storage processing unit 7 is notified that the failure information has been received, and the failure information storage processing unit 7 sends the NMS server 2 The fault information is stored in the fault information storage database 8 in the inside, the fault information is passed to the fault information real-time display processing unit 9, and the fault information is displayed on the NMS console 3a in real time.

The failure information storage database 8
The failure information log accumulated in the server is displayed in the failure information log display processing unit 1.
0 indicates a GUI from the NMS console 3a. Next, the failure information storage processing unit 7 transmits the failure information to the failure information storage processing unit 11 set for each user. When notifying the fault information to the fault information storage processing unit 11 for each user, the fault information storage processing unit 7 refers to the user table for notification.

FIG. 3 is an explanatory diagram showing an example of the above-mentioned user table, in which a user name and a database name assigned to this user are stored in association with each other. It is assumed that this user table can be configured using a GUI on the NMS console 3a. Here, the accumulation process of the user A will be described.

Upon receiving the fault information, the fault information storage processor 11 of the user A refers to the fault display management table,
Only for the failure information registered in this table,
The failure information is stored in the failure information storage database 12 for the user A. FIG. 4 is an explanatory diagram showing an example of the above-mentioned fault display management table, in which IDs of devices or lines in which fault information is to be stored and messages are stored in association with each other.

In the table shown in FIG. 4, in the case of the user A, if a failure occurs in the line 5a or 5b in FIG. 2, the failure information is stored, and in the case of the user B, the failure occurs in the line 5c. In such a case, failure information is accumulated. The failure information storage processing unit 11 of the user A stores the failure information in the failure information storage database 12 for the user A with reference to the failure display management table as described above, and performs the real-time display of the failure information of the user A. The failure information is passed to the unit 13, and the failure information of the user A is displayed on the NMS console 3b in real time.

The failure information storage database 1
The trouble information log stored in the NMS 2 is transmitted from the NMS console 3b of the user A by the trouble information log display
Indicated by I. Note that the process of the user B is performed in the same manner. That is, when a failure occurs in a device such as a line used by the user B, the failure information storage processing unit 7 refers to the user table and stores the failure information in the failure information storage processing unit 11 set for the user B. Send

Upon receiving the fault information, the fault information storage processor 11 of the user B refers to the fault display management table,
Only for the failure information registered in this table,
The fault information is stored in the fault information storage database 12 for the user B, the fault information is passed to the fault information real-time display processing unit 13 of the user B, and the fault information of the user B is displayed on the NMS console 3c in real time.

The failure information log stored in the failure information storage database 12 of the user B is transmitted to the NMS console 3 of the user B by the failure information log display processing unit 14.
A GUI is displayed from c. Also, as shown in FIG. 4, in the fault display management table for each user, a message is registered for each ID of a device, a line, and the like. When notifying the failure information to the unit 13, this message is added and notified, so that the failure information and this message are displayed when the failure information is displayed on the NMS console 3 b or 3 c.

[0017] Thus, it is possible to add a message that enables an appropriate response to the failure information for each user. The failure display management table for each user shown in FIG. 4 can be configured by a GUI on the NMS console 3a. Here, the users A and B are shown, but when the number of users increases, fault information is accumulated and displayed by the same processing.

As described above, switching nodes 1A, 1
In the network management system that manages B, a database 12 that stores the history of fault information is provided for each user who uses the switching node. Therefore, when each user searches for his own fault information, Since it suffices to search the corresponding database 12, it is possible to shorten the fault display search processing time for each user.

[0019] Further, the failure information for each user is given by NM.
S makes it possible to give separate comments.
Further, the failure information storage processing unit 7 is obtained by adding a filtering process of a failure information storage processing notification for each user to the existing processing.
Is a software that adds filtering processing for obtaining and selecting fault information for each user to the existing fault information storage processing, so only software changes are required, and the existing fault information real-time display processing function and fault information log display processing It is possible to use functions.

[0020]

As described above, according to the present invention, in a server connected to a switching node, a database for storing fault information for each user using the switching node is provided, and fault information is stored for each user. I decided to accumulate them separately,
When considering the operation mode of allocating the line on the switching node for each user and managing the failure information of the switching node for each user, when searching for the failure information from the console for each user,
Since it is only necessary to access the database assigned to itself, the time for the search process can be reduced.

Further, since a comment is given to the failure information according to the content of the failure information and the user who notifies the failure information, it is possible to provide an optimal comment for each user when a failure occurs. It becomes possible.

[Brief description of the drawings]

FIG. 1 is a block diagram of an NMS server showing an example of an embodiment of the present invention.

FIG. 2 is a block diagram showing an example of the overall configuration of a network management system.

FIG. 3 is an explanatory diagram showing an example of a user table.

FIG. 4 is an explanatory diagram showing an example of a fault display management table.

[Explanation of symbols]

 11 failure information storage processing unit 12 failure information storage database

Claims (2)

[Claims] 1. A network management system for managing switching nodes, which is connected to the switching nodes in a fault information storage / display method in a network management system for displaying fault information history for each user who uses the switching nodes. A failure information storage / display method in a network management system, characterized in that a failure information storage database for each user using the switching node is provided in a server, and failure information is stored separately for each user. 2. A fault information storage / display method in a network management system according to claim 1, wherein a comment is given to the fault information according to the content of the fault information and a user who notifies the fault information. Failure information storage and network management system
Display method.