JP4437416B2 - Network maintenance system - Google Patents

Description

  The present invention relates to a network failure determination apparatus that automatically determines the cause of a failure in a network composed of information communication devices.

  In order to determine the main cause from a network failure, a method disclosed in, for example, Japanese Patent Laid-Open No. 10-200257 “Network service failure diagnosis method and apparatus” has been devised.

  FIG. 15 is a block diagram of a conventional network failure determination device, in which 61 is an input device, 71 is an equipment information database, 72 is a design information database, 62 is a storage device, 63 is a display device, and 81 is a display device. An equipment model generation means, 82 a communication sequence generation means, 83 a failure service component estimation means, and 64 a management device.

  Next, the operation of the background art will be described. The equipment model generation means 81 searches the equipment information database 71 based on the user name and service name of the user who has reported the failure, and when the user uses the corresponding service, between the terminal and the information source. A facility model composed of a plurality of communication devices to be arranged is generated. In addition, a user name and a use service name using a communication device estimated to be out of order are searched from the facility information database 21, and other use services or use services of other users who have reported the failure are included. When the user uses the corresponding service, an equipment model including a plurality of communication devices arranged between the terminal and the information source is generated.

  The communication sequence generation unit 82 searches the design information database 22 and generates a communication sequence when each communication device has failed together with a communication sequence when all communication devices constituting the equipment model are normal.

The failure communication device estimation means 83 compares the generated plurality of communication sequences with the observation information at the time of the failure report, estimates which communication sequence is occurring, and estimates the communication device that has failed. In addition, if the event of the user terminal estimated in the other usage service of the user who has reported the failure or the usage service of the other user matches the event at the time of the failure notification of the corresponding user, it is due to the failure of the same communication device. Estimated.
Japanese Patent Laid-Open No. 10-200527

  Since the conventional network failure determination apparatus is configured as described above, it has the following problems.

  (Problem 1) Since the trigger for determining the cause of failure is a failure report from the user to the management center, the cause of the failure cannot be accurately determined without a report from the user.

  (Problem 2) An end-to-end communication path is generated as a communication model, an end-to-end normal communication sequence and a fault communication sequence are generated, and the observation information reported by the user is generated. By comparing the communication sequences, the failed communication device is estimated. In the conventional example, it is assumed that a unique communication path is determined when a terminal communication device is specified. However, in the case of a dynamically determined communication path or a dual transmission network, in the conventional example, the cause of failure is determined. It can not be identified.

  (Problem 3) Since there is no processing when a large number of alarms are generated due to a network failure, when the management device receives a large number of alarms, it takes a lot of time to identify the main cause alarm from them. .

  (Problem 4) When the information communication device is stopped for maintenance and inspection, the network failure determination device cannot automatically determine how much the line is stopped in advance.

  (Problem 5) A large number of alarms may be generated when maintenance and inspection of information and communication equipment is stopped. However, since alarms generated by maintenance and alarms are handled in the same way, It takes time to determine the alarm generated by.

The network failure determination apparatus according to the present invention is
A network failure determination apparatus that determines a failure of a network to which a plurality of information communication devices are connected, and includes the following elements: (1) a self-generated information communication device that is a sender side Alarm generation pattern table (corresponding to the alarm generation pattern consisting of the alarm type of the side alarm and the alarm type of the other party alarm generated by the other party information communication device on the receiving side) 2) Facility information table that stores the physical connection relationship of the information communication device and the logical line that accommodates the information communication device in association with each other. (3) For the information communication device, stores the latest state as to whether the information communication device is healthy. Equipment status table (4) Alarm collection unit that communicates with the plurality of information communication devices and collects alarms (5) Collected alarms and the alarm generation patterns in the alarm generation pattern table The main cause determination unit that determines the cause of the alarm corresponding to the corresponding alarm occurrence pattern as the main cause (6) specifies the connection relation of the information communication device that is the main cause from the facility information table, and Based on the connection relationship, the information communication device having a predetermined relationship with the information communication device that has caused the main cause is determined to be incapable of communication, the logical line that accommodates the information communication device incapable of communication is extracted, and the extracted logical line The latest state of the information communication device on the route of the communication line is acquired from the equipment state table, and when the latest state is not healthy, the communication line state determination unit (7) determines that the logical line is incapable of communication. A fault reporting unit that reports alarms that have become unusable and logical lines that cannot communicate.

  As described above, according to the present invention, it is possible to specify the cause of a network failure using only the alarm generated by the information communication device without using the user report information.

  Moreover, the cause of the failure can be identified at high speed by rearranging the alarms generated by the information communication device according to the transmission speed of the information communication facility.

  Further, in a network in which an end-to-end communication path is fixed, it is possible to specify a logical line that stops due to the cause of the failure.

  Further, the end-to-end communication path is not fixed, and the network failure cause can be accurately specified in a network in which a plurality of communication paths are set.

  In addition, a logical line that cannot be communicated by maintenance work can be predicted before the maintenance work.

Embodiment 1 FIG.
FIG. 1 is a configuration diagram according to the first embodiment. In the figure, 1 is an information communication device such as a personal computer or a router, 2 is a storage device, 3 is a display device, and 4 is a management device.

  21 is an alarm definition database for storing types and formats of alarms generated by information communication devices, 22 is an alarm priority database, 23 is an alarm generation pattern database, 24 is an equipment information database, and 25 is a route information database. 41 is an alarm collection unit, 42 is an alarm alignment unit, 43 is a main cause determination unit, 44 is a communication line state determination unit, 45 is a failure notification unit, 46 is an alarm log, and 47 is an equipment state. Represents a database.

  FIG. 2 is an alarm definition table, which is table information in which information communication device types 201, alarm types 202 generated by them, and alarm importance 203 are associated with each other. It is stored in the alarm priority database 22 of the storage device 2.

  Here, the information communication device type 201 represents the type and model name of the information communication device. The alarm type 202 represents the type of alarm that the information communication device can transmit to the management device. The alarm importance is a parameter for determining whether or not the management apparatus is a failure to be used for failure determination, and can take a value of Major (large) or Minor (small). However, the alarm importance need not be limited to two values, and may be three or more.

  FIG. 3 is an alarm alignment rule table, which is an alarm alignment rule referred to by the management device 4 for rearranging alarms received from the information communication device 1. It is stored in the alarm priority database 22 of the storage device 2. In the figure, the device priority 301 indicates the level of priority. The lower the device priority number, the higher the priority. The alarm generating device type 302 represents the type of the information communication device that is the source of the alarm. The transmission rate 303 represents the transmission rate of the information communication device that is the source of the alarm.

  FIG. 4 is an alarm generation determination pattern table for collating with the alarm generation pattern received from the information communication device 1 by the management device 4. The alarm generation pattern database 23 of the storage device 2 is stored in advance. In the figure, a pattern number 401 represents an identifier of an alarm generation pattern, an own side alarm 402 represents an alarm type generated on the own side, and an opponent side alarm 403 represents an alarm type generated on the other side. The cause 403 represents the type of alarm that causes the alarm when it matches the pattern and the information communication device (local side or partner side) that is the source of the alarm.

  FIG. 5 is a facility information table that stores physical connection relationships between information communication devices. The information is stored in advance in the facility information database 24 of the storage device 2. In the figure, an information communication device name 501 is a name for identifying an information communication device. The host device name list 502 is a name list of information communication devices connected to the information communication device. The lower connection device name list 503 is a name list of information communication devices connected to the information communication device. An information communication device having a transmission speed higher than that of the information communication device is stored in the upper connection apparatus name list 502, and an information communication apparatus having a lower transmission speed is stored in the lower connection apparatus name list 503. Information communication devices having the same transmission rate are stored in the upper connection device name list 502 or the lower connection device name list 503. The logical line name list 504 is a list of logical lines having the information communication device as a start / end.

  FIG. 6 is a communication path information table representing a logical communication path between two information communication devices, and is stored in advance in the path information database 25 of the storage device 2.

  The logical line name 601 is a name for identifying a logical line. The local information communication device name 602 represents a name for identifying the local (communication side) information communication device, and the counterpart information communication device name 603 represents a name for identifying the counterpart (reception side) information communication device. Communication path 1 is a name list of information communication apparatuses existing on the communication path between the local information communication apparatus name 602 and the counterpart information communication apparatus name 603. Communication path 2 (604b) and communication path n (n = 3, 4,...) (604c) are the same as communication path 1 (604a).

  Next, the operation of the failure determination apparatus of the present invention for extracting the main cause of network failure will be described. The operation will be described with reference to FIGS. FIG. 7 shows a physical connection configuration of the network. In the figure, when a failure occurs in the information communication apparatus 1d, various alarms are transmitted from the information communication apparatuses 1a, 1b, 1c, 1d, 1g, 1h, 1j, and 1k to the management apparatus 4. FIG. 8 is a diagram illustrating an example of a received alarm.

  In this example, it is assumed that the management device 4 has received an alarm as shown in FIG. In the figure, the alarm reception time 801 represents the date and time when the management apparatus 4 received the alarm, and the alarm generation device name 802 represents a name for identifying the information communication device that is the alarm generation source. The alarm generation device type 803 indicates the type of the information communication device that is the alarm generation source, and the alarm type 804 indicates the type of alarm.

  FIG. 9 shows an operation flow of the failure determination apparatus. The management device 4 continues to wait for an alarm from the information communication device (S1).

  When a failure is detected in the information communication device a, an alarm is transmitted to the management device 4 (S2).

  The alarm collection unit 41 of the management device 4 receives an alarm from the information communication device 1a (S3).

  The alarm collection unit 41 compares the alarm type of the received alarm with the alarm definition table (FIG. 2) in the alarm definition database 21 (S4).

  If the received alarm is Minor (small), the management device stores the alarm as a log and returns to the alarm reception waiting state (S5).

  When the received alarm is Major (large), the alarm collection unit 41 operates a timer for a predetermined alarm collection time (for example, 10 seconds) and continues to wait for other alarms for the alarm collection time (S6). If the information communication device 1b detects a failure during the alarm collection time, the information communication device 1b transmits an alarm to the management device 4.

  The alarm alignment unit 42 of the management device 4 rearranges the collected alarms while referring to the alarm alignment rule table (FIG. 3) of the alarm priority database 22. The criteria for rearrangement are that the alarm with the highest transmission rate of the information communication device that is the source of the alarm is the first, and the alarm with the lowest transmission rate is the last (S7).

  The main cause determination unit 43 of the management device 4 checks the first alarm generation source in S7, and generates an alarm generation pattern database (FIG. 4) corresponding to the information communication device of the generation source as an alarm generation pattern database ( 23). The generated alarm is compared with the alarm generation pattern (S8).

  If there is a matched pattern, the alarm corresponding to the main cause alarm described in the alarm generation pattern file is determined as the main cause (S10).

  If the comparison does not match the alarm generation pattern file, all extracted alarms are determined as the main cause (S11).

  The communication line state determination unit 44 of the management device 4 searches the facility information table (FIG. 5) for the name of the alarm source determined to be the main cause in S10 or S11, and displays the physical connection configuration diagram of the information communication device. create. In the connection configuration diagram, an information communication device that is connected to a lower level of the information communication device that is the main cause, and an information communication device that is connected to the information communication device that is in an end-to-end relationship with the information communication device that is the main cause It is determined that the information communication device cannot communicate. Then, a list of logical lines registered in each information communication device that cannot communicate is extracted. FIG. 10 is a diagram showing an equipment state table.

  Next, the communication line state determination unit 44 refers to the path information database 25 and checks whether there are a plurality of communication paths for the logical lines extracted above. Referring to the equipment state table (FIG. 10) stored in the equipment state database 47, the state of the information communication device on each route is checked. If there is even one healthy communication path, the logical line is Is determined to be sound, and if all communication paths are incapable of communication, it is determined that the logical line is incapable of communication (S12).

  The failure notification unit 45 of the management device 4 displays the alarm as the main cause and the logical line that cannot be communicated due to the alarm on the display device 3, and returns to the alarm waiting state S1.

  As described above, the management device 4 has the alarm definition database 21, the alarm priority database 22, the alarm generation pattern database, the facility information database 24, and the route information database 25, and the alarm alignment unit 42 while referring to these databases. The main cause determination unit 43 and the communication line state determination unit 44 can automatically determine the main cause of the network failure by analyzing the alarm of the information communication device.

Embodiment 2. FIG.
In the first embodiment, the storage device 2 stores an alarm definition database 21, an alarm priority database 22, an alarm generation pattern database 23, an equipment information database 24, and a route information database 25. Although configured, the alarm definition database 21, the alarm priority database 22, the alarm generation pattern database 23, the facility information database 24, and the route information database 25 are included in the management device 4 instead of the storage device. Even if it is configured to store, the same effect can be obtained. FIG. 11 is a configuration diagram according to the second embodiment.

Embodiment 3 FIG.
FIG. 12 is a configuration diagram according to the third embodiment. In the figure, 1 to 47 are the same as those in the first embodiment. 50 represents a maintenance terminal device, 51 represents a maintenance terminal interface unit, and 52 represents a pseudo alarm generation unit. Further, the maintenance terminal device 50 includes a pseudo alarm transmission unit 53, a communication impossible line notification receiving unit 54, and a communication impossible line display unit 55.

  FIG. 13 is an operation flow for explaining the operation of the third embodiment. The operation will be described with reference to FIG.

  The maintenance terminal device 50 pseudo-generates an alarm of the information communication device that stops due to maintenance work, and transmits the pseudo-alarm to the management device 4 (S101).

  The maintenance terminal interface unit 51 of the management device 4 receives the pseudo alarm (S2), processes the alarm in the same manner as in the first embodiment, and determines a logical line that cannot communicate (S2 to S12). Via the maintenance terminal interface 51 of the management device 4, the maintenance terminal device 50 is notified of the logical line that cannot communicate.

  The maintenance terminal device 50 displays on the maintenance terminal a logical line that is expected to be unable to communicate due to maintenance (S102).

  As described above, since the maintenance terminal device 50 is provided, and the management device 4 includes the maintenance terminal interface unit and the pseudo alarm generation unit, a logical line that cannot be communicated when the information communication device is stopped by the maintenance work is provided in advance. Can be predicted.

  FIG. 14 is a diagram illustrating a hardware configuration example of the network failure determination apparatus. An arithmetic device 1401, a data storage device 1402, a memory 1403, and a communication interface 1404 are connected to the bus. The data storage device 1402 is, for example, a ROM (Read Only Memory) or a hard disk. The memory 1403 is a normal RAM (Random Access Memory).

  The program is normally stored in the data storage device 1402, and is loaded in the memory 1403 and sequentially read into the arithmetic device 1401 for processing.

1 is a configuration diagram according to Embodiment 1. FIG. It is a figure which shows an alarm definition table. It is a figure which shows an alarm alignment rule table. It is a figure which shows an alarm generation determination pattern table. It is a figure which shows an equipment information table. It is a figure which shows a communication path information table. It is a figure which shows the physical connection structure of a network. It is a figure which shows the example of the received alarm. It is a figure which shows the operation | movement flow of a failure determination apparatus. It is a figure which shows an equipment state table. 6 is a configuration diagram according to Embodiment 2. FIG. FIG. 6 is a configuration diagram according to a third embodiment. 10 is an operation flow for explaining the operation of the third embodiment. It is a figure which shows the hardware structural example of a network failure determination apparatus. It is a block diagram of the conventional network failure determination apparatus.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 Information communication apparatus, 2 Storage device, 3 Display apparatus, 4 Management apparatus, 21 Alarm definition database, 22 Alarm priority database, 23 Alarm generation pattern database, 24 Equipment information database, 25 Path information database, 41 Alarm collection part, 42 Alarm alignment unit, 43 Main cause determination unit, 44 Communication line state determination unit, 45 Fault notification unit, 46 Alarm log, 47 Equipment status database.

Claims (1)

In a network maintenance system having a network failure determination device for determining a failure of a network to which a plurality of information communication devices are connected,
Network failure judgment device
(1) An alarm generation pattern comprising an alarm type of the local alarm generated by the local information communication device that is the transmission side and an alarm type of the remote side alarm generated by the counterpart information communication device that is the reception side; , An alarm generation pattern table (2) for storing the cause of these alarms in association with each other, and a facility information table (3) for storing the physical connection relationship of the information communication equipment and the logical line accommodating the information communication equipment in association with each other ) Equipment status table for storing the latest state of information communication equipment, whether healthy or not (4) Alarm type, and information indicating the importance level of the alarm corresponding to the alarm type, high importance and low importance (5) Log storage unit for storing alarms as a log (6) Communicating with the plurality of information communication devices, collecting alarms having alarm types, and having collected alarms The information indicating the importance of the alarm corresponding to the alarm type included in the alarm collected by comparing the alarm type stored in the alarm definition table with the alarm type stored in the alarm definition table is acquired from the alarm definition table, and the importance of the acquired alarm When the information indicating the degree of importance is low, the collected alarm is stored as a log in the log storage unit, and when the information indicating the degree of importance of the acquired alarm is high in importance, the collected alarm is output. The alarm collecting unit (7) compares the alarm output from the alarm collecting unit with the alarm generation pattern in the alarm generation pattern table, and determines the cause of the alarm corresponding to the corresponding alarm generation pattern as the main cause. Cause determination unit (8) The connection relationship of the information communication device that is the main cause is identified from the equipment information table, and information that has a predetermined relationship with the information communication device that is the main cause is identified based on the connection relationship. The communication device is determined to be incapable of communication, the logical line accommodating the information communication device that is incapable of communication is extracted, and the latest state of the information communication device on the route of the extracted logical line is acquired from the equipment state table. When the latest state is not healthy, a communication line state determination unit that determines that the logical line is not communicable (9) A failure notification unit that reports an alarm that is the main cause and a logical line that is not communicable ,
The network maintenance system further includes a maintenance terminal that artificially generates an alarm of the information communication device,
The alarm collection unit of the network failure determination device collects alarms generated by the maintenance terminal in a pseudo manner as alarms collected by communication with the plurality of information communication devices,
The network failure determination device includes a maintenance terminal interface unit that notifies the maintenance terminal of information specifying the incommunicable logical line,
A network maintenance system , wherein the maintenance terminal receives information specifying a logical line that cannot communicate and displays the logical line .

Images