JPH11205318A - Network supervisory and controlling method and system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To eliminate the need for an effect development information table and to reduce the loads of an operator in changing network configuration by judging a main cause in cooperation between respective sub network management systems. SOLUTION: When a main cause judgement part 23 receives an alarm from the inside of a sub network through an alarm reception part 24, whether or not it is a main cause alarm generated inside the present network as the main cause of a device fault or the like is decided in a received alarm classifying part 1. When it is inside the present management, the alarm is reported to a host system and an under-generation main cause alarm list 3 is updated. Upon receiving the alarm incapable of being immediately judged, the present management part and an influence judgement part 21 inside the opposite sub network management system of a fault device are inquired and a response by an effect judgement inquiry part 2 is waited for by timer monitoring. The effect judgement part 21 develops effect from the information of the under- generation main cause alarm list 3 and a configuration management data base 5 and updates the held under-generation main cause alarm list 6 in the case of being within the present management sub network.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a method and system for monitoring and controlling a network in a network operation system for a backbone transmission facility.

[0002]

2. Description of the Related Art FIG. 4 is a diagram showing an example of a conventional network monitoring and control system.

In an integrated network management system composed of a plurality of sub-network management systems (hereinafter, referred to as SB-NMS) and a network management system (hereinafter, referred to as NMS) for integrating them, a notification is transmitted from a transmission apparatus to be monitored. Since the main cause alarms and their effect alarms are notified in a concentrated manner at one time, it is required to quickly perform a main cause determination process for identifying only the main cause alarms among them. For example, it is not possible to determine whether the communication failure alarm has been received and whether the main cause is a failure of the device itself or a transmission line failure of a communication cable or the like by the content of the alarm notification alone. In order to make the determination, it is necessary to make a determination based on a correlation with another alarm notification occurring in the own network and an alarm notification occurring in another network.

[0004] In the conventional system, these correlations are summarized in advance in a form in which each network is summarized as an occurrence report and a list of influence warnings which are expected to occur.
The impact deployment information table 101 is registered at 00-0, and the main impact alert is determined based on the impact deployment information table 101 with respect to the contents of the replacement notification from the lower SB-NMSs 201-0 and 202-0. .

[0005]

[Problems to be Solved by the Invention] New establishment of a network,
When the configuration is changed, the operator needs to input the update of the NMS impact deployment information table at the same time as the update of the SB-NMS database. I have.

An object of the present invention is to provide a host system (NMS)
It is an object of the present invention to provide a network monitoring control method and system for performing an impact deployment process without having an impact deployment information table of the conventional method and reducing the load on an operator when changing the network configuration.

[0007]

A network monitoring and control method according to the present invention is provided for each sub-network management system in an integrated network management system comprising a plurality of sub-network management systems and a network management system integrating them. Receiving an alarm due to a failure that has occurred in a device in the sub-network, notifying the host system as a failure alarm that clearly indicates the main cause of the failure including the device failure, and simultaneously holding the alarm as a occurring main cause alarm; Recording an impact deployment for selecting a device which becomes in a failure state under the influence of the occurring main cause alarm from the middle main cause alarm, and holding the same as an impact alert list.

Further, for each sub-network management system, for an alarm which cannot be immediately determined as a main cause at the time of receiving an alarm, an inquiry is made as to whether or not the occurring main cause alarm is held in another network having a connection relationship. With steps. On the other hand, if there is an inquiry from another network as to whether the occurring fault is held as the main cause failure of the device in the own network, the description that the occurring main cause alarm is held in the self-management system is described. Only when there is, a step of returning a response to the inquiry source system, and after performing the above inquiry to the other sub-network management system, waits for a response from the other sub-network management system, only when there is no response, Determining the main cause alarm, transferring the same to the host system, and holding the same as the occurring main cause alarm in the own sub-network management system.

[0009] The network monitoring and control system of the present invention proposes a method of determining a main cause in cooperation between sub-network management systems. In the sub-network management system, a function to notify an upper-level system of an alarm that is obvious as a main cause of a device failure or the like at the time of receiving an alarm, and at the same time hold the same as an occurring main cause alarm, and to store its own configuration management information database from the occurring main cause alarm. A function that deploys the impact on the basis and stores it as a list of impact alerts, and an alert that cannot be immediately judged as the main cause when an alert is received, an impact judgment function in its own management unit, and an impact judgment function of other subnetwork management systems In the impact determination process, the function to return an impact alarm response to the inquiring system when an inquiry is made regarding an alarm in the impact alarm list, and the main cause determination function A function to wait for a response and, if there is no response, determine that it is the main cause alarm and transfer it to the host system Realizing the main cause determinable network monitoring control system integration by providing each sub-network management system.

As described above, in the method of the present invention, the influence development information table in the upper system (NMS) becomes unnecessary.

[0011]

Embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram of an embodiment of a network monitoring and control system according to the present invention, showing an operation system of a main cause determining function.

A network management system (hereinafter, referred to as NMS) 100 accommodates a plurality of sub-network management systems (hereinafter, referred to as SB-NMSs) 201, 202. In each of the sub-network management systems, a network monitoring control system capable of integrated main cause determination is realized by having a configuration having the main cause determination unit 23 and the influence determination unit 21.

The network A has devices 31 to 34 under the control of the SB-NMS 201, and the SB-NMS 20
In the network B under the management of No. 2, devices 35 to 37 are provided.

When a failure occurs in the device 32 of the network A, the SB-NMS 201 receives an alarm receiving unit 24, and the main cause determining unit 23 determines this. Then, the alarm is reported to the alarm receiving unit 14 of the NMS 100, and at the same time, the occurring main cause alarm is transferred to the influence determining unit 21. The influence determination unit 21 records the generated main cause alarm list 3 by the transfer and records it in the configuration management database 5, and further selects an influence alarm device that is in a failure state due to the effect of the occurring type cause alarm. It has an impact deployment unit 4 that creates an impact deployment table 6 that develops and records those devices, and an impact determination / response unit 7 that handles transmission and reception of the impact determination unit.

The main cause judging section 23 receives the main cause alarm from the alarm receiving section 24.
It comprises a reception alarm classifying unit 1 for transferring to the influence judging unit 21 and an effect judging inquiry unit 2 for managing a waiting time when introducing to the shelf-unknown SB-NMS.

The main cause determination unit 23 and the influence determination unit 21
The details of the operation of the above are described in the influence development unit 4 in the SB-NMS.
2 and FIGS. 3 (a) and 3 (b).

First, when the main cause determination unit 23 in the subnetwork management system receives an alarm from a device in the jurisdiction subnetwork via the alarm reception unit 24, the reception alarm classification unit 1 (FIG. 2) It is determined whether or not the main cause of the failure is a main cause alarm in the own network (step 51). At the same time, the upper-level notification unit 22 notifies the higher-level system 100 of a clear alarm as the main cause alarm in the own jurisdiction, and simultaneously records the alarm in the occurring main-cause alarm list 3 held in the influence determination unit 21 and records this. Update (step 52). When the main cause determination unit 23 receives an alarm that cannot be immediately determined as the main cause (step 51), the main cause determination unit 23 inquires the self-management unit and the influence determination unit 21 in the sub-network management system of the partner of the faulty device. (Step 53), and enters a state of waiting for a response from the influence determination inquiry unit 2 by timer monitoring (Step 54). The influence determination unit 21 performs the effect development from the occurring main cause alarm list 3 and the information in the configuration management database 5, and updates the stored occurring effect development alarm list 6 that is stored in the own management subnetwork ( Step 55).

Further, another SB-NWS main cause determination unit 2
3 (step 61), the generated effect development alarm list 6 is checked for the alarm (step 62), and if the alarm is present in the occurring effect development list 6, the main cause determination unit 23 of the inquiry source is checked. The effect judgment / response unit 7 notifies the result of the judgment that the alarm belongs to the self-management system as a result of the judgment (step 64). If the alarm is not present in the list, no response is returned to the main cause judgment unit 23 (step 65). ).

When a timeout of the influence determination inquiry unit 2 is detected in the response waiting state of the main cause determination unit 23 (step 56), the alarm is transferred to the higher-level notification unit 22 as a main cause alarm belonging to the own management unit. The occurrence main cause alarm list 3 held in the influence determination unit 21 is updated (steps 52 and 53). If the determination result that is the influence alarm is received without time-out, the alarm is regarded as not the failure alarm belonging to the own management unit, the corresponding alarm is discarded, and the transfer to the higher-level notification function is not performed (step 57).

In the method of the present invention, the main cause determination is realized by the cooperation of the respective sub-network management systems, so that the influence development information table in the upper system becomes unnecessary.

[0022]

As described above, according to the present invention, the main cause and effect determination of the fault alarm is performed at the sub-network management unit stage, and the effect development of the fault is recorded and updated, and then the network management unit 5 performs the determination. Since this is reported, the network management unit eliminates the need for the main cause determination and the impact determination, and has the effect of speeding up the processing.

[Brief description of the drawings]

FIG. 1 is a block diagram of an embodiment of a system to which a network monitoring control method of the present invention is applied.

FIG. 2 is a diagram illustrating an influence determining unit 22 and a main cause determining unit 23 illustrated in FIG. 1;
It is a detailed block diagram of.

3A is a flowchart of an influence determination unit 21 of an inquiry sub-network management system, and FIG. 3B is a flowchart of an influence determination unit 21 of another sub-network management system that has received an inquiry.

FIG. 4 is a block diagram of an example of a conventional network monitoring and control system.

[Explanation of symbols]

 DESCRIPTION OF REFERENCE NUMERALS 1 Received alarm classification unit 2 Impact determination inquiry unit 3 Influence deployment alarm list during occurrence 4 Impact deployment unit 5 Configuration management database 6 Impact alert list 7 Impact determination / response unit 21 Impact determination unit 22 Upper notification unit 23 Main cause determination Unit 24 alarm receiving unit 25 configuration management database 32 to 37 device 100 NMS 201, 202 BS-NMS

──────────────────────────────────────────────────の Continued on the front page (51) Int.Cl. ⁶ Identification code FI H04M 3/00

Claims (6)

[Claims] 1. A network monitoring and control method in an integrated network management system including a plurality of sub-network management systems and a network management system that integrates the plurality of sub-network management systems. Receiving an alarm, notifying the host system as an alarm of a failure whose main cause of the failure including the device failure is obvious, and simultaneously holding the alarm as an occurring main cause alarm; and A step of recording the effect development for selecting a device that becomes a faulty state due to the influence of the cause alarm and maintaining it as a list of the effect alarms. Querying the network management system; If the network management system inquires whether the fault that is occurring is held as the main cause fault of the device in the own network, only when the self-management system holds the fault as the main cause alarm, Returning a response to the inquiring system, and waiting for a response from the impact determination function of another network management system.If there is no response, it is determined to be the main cause alarm and transferred to the higher-level system. Holding the alarm as a main cause alarm during occurrence. 2. The network monitoring and control method according to claim 1, wherein the response waiting state from the influence determination function of said another sub-network management system is time-managed by a timer so as to limit a preset time. 3. The method according to claim 1, wherein the step of querying the other sub-network management system includes querying another sub-network management system having a device closest to the corresponding device in the own network in the impact alert list. Network monitoring control method. 4. A network monitoring and control system in an integrated network management system comprising a plurality of sub-network management systems and a network management system that integrates the plurality of sub-network management systems. Means for notifying the upper-level system of the obvious alarm as well as holding it as an occurring main cause alarm in the occurring main cause alarm list, and the main cause based on the configuration management information database of the own device from the occurring main cause alarm Select a device that will be in a faulted state due to the effect of the fault.Deploy the affected device and maintain it as a list of affected alarms.For alarms that cannot be immediately determined as the main cause when receiving an alarm, determine the impact of the own device. The means and means of determining the impact of other subnetwork management systems From the other sub-network management system, if there is an inquiry as to whether or not the occurring fault is in the list of the effect alarms of its own device as the main cause failure of the device in its own sub-network, A means to return a response to the inquiring system only when it is listed in the impact alarm list, and a response from the impact determination function of another network management system. Means for transferring the information to a system and holding the alarm as a main cause alarm during the occurrence of the own apparatus. 5. The network monitoring and control system according to claim 4, wherein a response waiting state from the influence determination function of said another sub-network management system is time-managed by a timer so as to limit a preset time. 6. The apparatus according to claim 1, wherein the means for inquiring of the other subnetwork management system includes inquiring of another subnetwork management system having a device closest to a corresponding device in the self-management network of the impact alarm list. 3. The network monitoring and control system according to 2.