JP2882263B2 - Network monitoring method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network monitoring system for managing, storing, displaying or notifying information of a fault occurring in a monitored device constituting a network in a communication network such as a packet switching network. .

[0002]

2. Description of the Related Art FIG. 26 is a block diagram showing a method of storing a failure log file in a conventional information processing apparatus, for example, as disclosed in Japanese Patent Laid-Open No. Hei 4-3233. In the figure, 5
01 is a log collection unit, 502 is a log analysis unit, 503 is a log editing unit, 504 is a reference suspected part name information inquiry unit, 505 is an error log deletion unit, 506 is an error log registration unit, 510 is a device to be diagnosed, and 511 is a diagnosis target device. Diagnosis CP
U, 512 an input / output control device, 513 a main storage device, 5
14 is a diagnostic unit, 515 is a service processor, 5
16 is a magnetic disk drive, 517 is a console, 518
Is a printer. FIG. 27 shows, for example, Japanese Unexamined Patent Application Publication No.
FIG. 476 is a configuration diagram showing an aggregation method of fault information and status change information in a conventional network monitoring system disclosed in Japanese Patent Application Publication No. 476. In the figure, 601 is a centralized monitoring device, 602
Is an information relay device, 603 is a remote monitoring device, 604 is a transmission line, 605 is an information relay circuit, 606 is an information transmission circuit, and 6
07 is an aggregation processing circuit, 608 is a state change detection circuit, and 609 is a monitored device.

Next, the operation will be described. 26, when a failure occurs in the device under diagnosis 510, the failure information is transmitted to the service processor 5 via the diagnosis unit 514.
15 is notified. Next, the service processor 515 collects the error log data via the diagnostic unit 514 by the log collection unit 501, and
6 is stored. After that, the log analyzing means 502
The error log data is analyzed, and the error log data edited by the log editing unit 503 is displayed on the console 51.
7 or the printer 518. This is deciphered by the operator, failure analysis is performed, and recovery is performed. At this time, the reference suspected part name information inquiring means 504 manually inquires the log information referred to at the time of performing the recovery processing, and the error log deleting means 5
05, the corresponding error log data is deleted and registered as log information after recovery.

In FIG. 27, a monitored device 609 is shown.
, A state change detection circuit 608 detects the state change as a state change of the monitoring information, and notifies the aggregation processing circuit 607. The aggregation processing circuit 607 counts the notified state change information for a certain period of time, and when the number of state changes is one and changes from recovery to occurrence, the state of occurrence continues, and the number of state changes changes from occurrence to recovery once. In this case, the state is determined to be the recovery continuation state. If the number of state changes is two, the state is determined to be instantaneous. If the number of state changes is three or more, the state is determined to be the interrupted state. The aggregated state change information is sent to the information transmission circuit 606, and is centrally monitored via the transmission line 604, the information relay circuit 605, and the information relay device 602 including the information transmission circuit 606. Sent to the device 601.

[0005]

The storage method of the failure log file of the conventional information processing apparatus such as the packet switching apparatus is configured as shown in FIG.
Even if a failure occurs due to one cause, if a lot of failure information is derived, various error log data are stored in the same failure log file in a mixed manner. It takes a great deal of labor and time for the operator to isolate and analyze the cause of the failure and complete the recovery. Therefore, there is a problem that the MTTR (Mean Time To Repair: the time required from when the service is stopped due to a failure to when the service can be started after the recovery) becomes long.

[0006] Further, when a failure in the form of repeating the occurrence / recovery of the same failure in a short time occurs in a packet switch or its network, a failure log file in the magnetic disk device of FIG. 26 overflows, and as a result, There is a problem that important fault information stored before is deleted by overwriting, and important fault information generated thereafter cannot be stored because there is no free space in the magnetic disk device.

Furthermore, since the conventional packet switching network monitoring device is configured as shown in FIG. 27, it is necessary to always connect a dedicated network management device to the network.
There is a problem that a great deal of cost is required for constructing a network by packet switching, and an extra traffic load is imposed on the network by monitoring information.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems, and the invention according to claim 1 is for grasping important trouble information of an operator in a communication network and for observing a global trouble situation. It is an object of the present invention to provide a network monitoring method that facilitates understanding and enables efficient identification and analysis of the cause of a failure.

Further, according to the invention described in claim 2, when the occurrence / recovery of the same fault information is repeated continuously, the repetition is notified to the operator in an aggregated form, so that the fault is notified. The purpose is to efficiently identify and analyze the cause of the problem, and overflow the log file that stores the failure information, and as a result, the previously stored important failure information may be deleted by overwriting, It is an object of the present invention to provide a network monitoring method that prevents important fault information that occurs thereafter from being unable to be stored because there is no free space in the magnetic disk device, thereby preventing fault isolation and analysis from being impossible. .

Another object of the present invention is to provide a network monitoring system which displays fault information on a terminal used as a maintenance console as needed to prevent a load caused by extra traffic. I do.

[0011] The invention according to claim 4 is, in operation,
An object of the present invention is to provide a network monitoring method capable of automatically suppressing information on a failure that occurs regularly.

The invention according to claim 5 is characterized in that the operator can change the condition of the classification according to the importance of the fault and the schedule for switching the condition at a fixed time, and the operator can change the condition online. An object of the present invention is to provide a network monitoring method that can be easily performed.

Another object of the present invention is to provide a network monitoring system capable of immediately displaying fault information on a terminal.

Another object of the present invention is to provide a network monitoring system which enables each operator to analyze fault information from a plurality of terminals in different formats.

Further, according to the present invention, even if a terminal used as a maintenance console is not connected, when an important failure occurs among the failures, it is immediately notified to the outside. It is another object of the present invention to provide a network monitoring method capable of issuing an alarm to an operator.

Further, according to the ninth aspect of the present invention, each of the above objects is realized by a monitoring method for a network constituted by a packet switching network.

[0017]

According to the first aspect of the present invention, there is provided a network monitoring system for detecting a failure occurring in a monitored device constituting a communication network,
A failure information generation unit that generates failure information in response to the detection notification from the failure detection unit; and performs a major operation on the failure information from the failure information generation unit according to the definition of the importance according to a predefined failure information classification table. -Alarms (major fault information) and minor alarms (light fault information) are classified into summary information, and the fault information is limited to major information such as the time and location of the fault, and its faults. Fault information classification control unit that classifies the information into detailed information including all information that can be collected with respect to the alarm information, a major alarm summary log file and a minor alarm summary log that store the failure information classified by the failure information classification control unit And a detailed information log file.

According to a second aspect of the present invention, there is provided a network monitoring system, comprising: a failure information aggregation monitoring timer; when the occurrence / recovery of the same failure information is continuously repeated within a set time of the timer, the failure information is monitored; Information aggregation buffer for temporarily storing the
Equipped with a failure information aggregation monitoring unit that summarizes the series of recovery start and end times and the number of repetitions, and stores the relevant failure information in the major alarm summary log file, minor alarm summary log file, and detailed information log file. It is a thing.

In the network monitoring method according to the third aspect of the present invention, a terminal used as a maintenance console is connected, and a major stored in a major / alarm summary log file is indispensable in response to a display request from the terminal. Read the alarm, send it to the terminal and display it, and select the major alarm stored in the major alarm summary log file, the minor alarm stored in the minor alarm summary log file, or A failure log display control unit is provided for reading the failure detailed information stored in the detailed information log file and sending it to the terminal for display.

According to a fourth aspect of the present invention, there is provided a network monitoring system, wherein a plurality of fault information classification tables are provided, and a plurality of fault information classification tables are defined according to the contents of a schedule management table defined in advance.
A failure information classification table switching control unit that switches a failure information classification table to be applied at a predetermined time is provided.

According to a fifth aspect of the present invention, there is provided a network monitoring system for connecting a terminal used as a maintenance console, and registering and changing the definition contents of a fault information classification table and a schedule management table in accordance with an instruction from the terminal. , A failure information classification table maintenance unit and a schedule management table maintenance unit to be deleted.

According to the network monitoring method of the present invention, a terminal used as a maintenance console can be connected, and when the terminal is connected, this is detected, and a major alarm, A fault message display control unit is provided for receiving the fault summary information of each minor / alarm and sending it to the terminal for display.

According to a seventh aspect of the present invention, there is provided a network monitoring system including a plurality of terminals, wherein a type of fault information to be displayed is set in advance for each terminal, and the type of the fault information is set in accordance with the connection of each terminal. The failure information of a predetermined type is sent and displayed.

The network monitoring system according to the present invention is provided with an alarm output control unit for receiving a major alarm from the fault information classification control unit and reporting the occurrence of the serious fault to the outside. .

A ninth aspect of the present invention provides a network monitoring system in which each of the above-mentioned inventions is applied to a packet switching network in which a communication network is constituted by a plurality of packet switches. And process information on the fault that occurs in the monitored device.

[0026]

According to the first aspect of the present invention, the failure information classification control unit is configured to provide a major alarm (major failure information) and a minor alarm (slight failure information) according to the importance of each failure information in advance with respect to network failure information. ) Is classified according to the classification definition, and the fault information is further divided into summary information in which the main contents such as the time and location of occurrence and detailed information in which all information that can be collected regarding the fault are stored, By storing them separately in the major / alarm summary log file, minor / alarm summary log file, and detailed information log file, the cause of the failure can be efficiently identified and analyzed from the contents of these log files. Realize a network monitoring method that can.

The fault information classification control unit according to the second aspect of the present invention temporarily stores fault information received from the fault information generating unit in a fault information aggregation buffer, and stores the fault information in a time determined by a fault information aggregation monitoring timer. When the fault information aggregation monitoring unit monitors the same fault information, the time from the fault occurrence time to the recovery time is shorter than a certain monitoring time, and the time when the fault reoccurs from the recovery time. If the time until the time is shorter than a certain monitoring time, it is assumed that the same fault information is continuously generated / restored, and is aggregated into a series of start / end times of occurrence / recovery of the fault information and the number of repetitions thereof. To realize a network monitoring method.

According to the third aspect of the present invention, the fault log display control unit reads a major alarm stored in a major / alarm summary log file in accordance with a display request from the terminal and sends the read major alarm to the terminal. The details of major alarms stored in the major alarm summary log file, minor alarms stored in the minor alarm summary log file, and faults stored in the detailed information log file are displayed and selected by the terminal. A network monitoring method capable of reading information, sending the information to a terminal, and displaying the information is realized.

According to the fourth aspect of the present invention, the fault information classification table switching control unit selects a switching time and a fault information classification table to be switched from the plurality of fault information classification tables in accordance with the contents of a schedule management table registered and defined in advance. A network monitoring method capable of automatically switching to a valid failure information classification table is realized.

The fault information classification table maintenance unit and the schedule management table maintenance unit in the invention according to claim 5 are configured so that the classification condition registered in the failure information classification table is controlled in response to an instruction from a terminal connected as a maintenance console. , And registered in the schedule management table,
A network monitoring method capable of registering, changing, and deleting the switching time and the failure information classification table number of the failure information classification table while online is realized.

The fault message display control unit in the invention according to claim 6 automatically detects the state of the terminal used as the maintenance console while the terminal is used, and outputs a major / alarm / minor signal from the fault information classification control unit. -Implement a network monitoring method that receives fault summary information for each alarm, immediately sends it to the terminal, and displays it, so that the operator can be notified of the fault occurrence status in real time.

In the network monitoring method according to the present invention, a plurality of terminals to be used as a maintenance console are connected, and communication by each terminal is simultaneously realized. Inside, the state is detected, and the fault summary information and detailed information of each of the major alarm and minor alarm from the fault information classification control unit are sent to and displayed on separate terminals.

The alarm output control unit according to the eighth aspect of the present invention, upon receiving a major alarm from the fault information classification control unit, performs an electrical contact output and immediately notifies the outside of the occurrence of a serious fault. To realize a network monitoring method.

The network monitoring method according to the ninth aspect of the present invention is particularly applied to a packet switching network.
Various kinds of fault information generated in many monitored devices connected to this network are appropriately classified and processed, so that the fault information can be easily grasped, and the cause and analysis of the fault can be efficiently performed.

[0035]

[Embodiment 1] Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG.
FIG. In the figure, reference numeral 1 denotes packets exchange, 2 external storage device connected to the packet switch 1,
3 is a maintenance console connected to the packet switch 1, 4
Is an alarm device connected to the alarm contact output of the packet switch 1, 5 is a relay line connecting lines (inter-offices) of the packet switch 1, and 6 is a subscriber terminal accommodated in the packet switch 1. . In this figure, three packet switches 1 are connected by a relay line 5 to form a packet switching network.

FIG. 2 is a block diagram showing the internal configuration of the packet switch 1 of FIG. In the figure, reference numeral 11 denotes a device management processor for managing the entire device of the packet switch 1, and the external storage device 2 and the maintenance console 3 are connected to the device management processor 11. Reference numeral 12 denotes a plurality of communication control processors for performing packet exchange processing from a subscriber and communication processing for inter-station relay. Reference numeral 13 denotes a system bus for interconnecting the device management processor 11 and the plurality of communication control processors 12. Reference numeral 14 denotes a DTE (Data Terminal Equivalent) connected to the communication control processor 12 to accommodate the subscriber terminal 6.
pment) line, and the relay line 5 connecting the stations is also connected to another communication control processor 12.

Next, FIG. 3 shows the device management processor 1 of FIG.
1 is a block diagram showing the internal configuration of the external storage device 2 by attaching reference numerals after 21 to the internal configuration of the external storage device 2. In the figure, reference numeral 111 denotes a failure detection unit for detecting the occurrence and recovery of a failure in the apparatus of the packet switch 1 and in the network.
Reference numeral 12 denotes a failure information generation unit that receives the detection notification from the failure detection unit 111 and generates the failure information, and 113 classifies the failure information passed from the failure information generation unit 112 into a major alarm and a minor alarm. A failure information classification control unit 1131 for further classifying the failure information into summary information and detailed information; and 1311, a condition for the failure information classification control unit 113 to classify the failure information into a major alarm and a minor alarm. It is a failure information classification table defined in advance according to the degree.

In the external storage device 2, 21 is a major alarm summary log file storing summary information of major alarms, 22 is a minor alarm summary log file storing summary information of minor alarms, and 23.
Is a detailed information log file storing detailed information of the failure.

FIG. 4 is a diagram showing the configuration of the fault information classification table 1131 of FIG. Here, a plurality (n) of failure information classification tables 1131 are prepared, and in each table, 1131a is a table number for identifying a plurality of failure information classification tables, and 1131b is a type of a predefined failure information. Message N to do
o, 1131c stores importance classifications for classifying the fault information into three types of major alarm (major fault information), minor alarm (light fault information), and suppression (suppress fault information). Is done. Here, deterrence means
This refers to cases where it is not necessary to treat the information as failure information with very small contents.

FIG. 5 is a diagram showing the configuration of the major / alarm summary log file 21 of FIG. 211 is management information of each log file, 211a is the current number of log storage records, 211b is the latest log record pointer,
11c is the oldest log record pointer input first, 212 indicates the configuration of each log record, and 212a
Is a record No. 212b is a message No. for identifying the type of the stored failure information, 212c is a distinction of occurrence / recovery of the failure, 212d is an occurrence / recovery time,
Reference numeral 12e indicates the location where the failure has occurred. Specifically, the station number, unit number, card number, line number, etc. of the packet switch are recorded, and 212f stores a detailed information log corresponding to the detailed information log file 23. Record No. recorded is recorded. Reference numeral 222g denotes aggregate information, which will be described later (second embodiment).

FIG. 6 is a diagram showing the configuration of the minor / alarm summary log file 22 shown in FIG. 221 is management information of each log file, 221a is the current number of log storage records, 221b is the latest log record pointer,
221c is the oldest log record pointer, 222 indicates the configuration of each log record, and 222a is the record N
o, 222b are the message numbers for identifying the type of the stored fault information, 222c is the distinction of occurrence / recovery of the failure, 222d is the occurrence / recovery time, 222e is the location where the failure occurred, Specifically, a station number, a unit number, a card number, a line number, and the like of the packet switch are recorded, and a record number 222f in which the detailed information log corresponding to the detailed information log file 23 is stored is recorded.

FIG. 7 is a diagram showing the structure of the detailed information log file 23 shown in FIG. 231 is management information of a detailed information log file, 231a is the current number of log storage records, 231b is the latest log record pointer, 231c
Is the oldest log record pointer, 232 is the configuration of the detailed information log record, 232a is the record number,
232b is a message number for identifying the type of the stored fault information, 232c is a distinction between occurrence / recovery of the fault, 232d is an occurrence / recovery time, and 232e is detailed information of the fault information.

Next, the operation will be described. FIG. 8 shows a processing procedure of the fault information classification control unit 113 in FIG. First, P
In step 1, the failure information is received from the failure information generation unit 112. Here, FIG. 9 shows the configuration of the fault information. a is a message number for identifying the type of failure information, b is occurrence / recovery distinction, c is occurrence / recovery time, d is a location where the failure information is generated, and e is individual information specific to the failure information. Represent. a to d are summary information, and e plus e is detailed information.

Returning to FIG. 8, the fault information classification control unit 113
Is a plurality of fault information classification tables 1131 in P2.
Select and refer to a valid failure information classification table from
In P3, the importance classification corresponding to the message No. of the failure information received in P1 is referred from the failure information classification table, and the importance classification is determined in P4.

In the judgment at P4, if the alarm is a major alarm, the process proceeds to P51, where the detailed information log record 232 shown in FIG. 7 is created from the range of the detailed information shown in FIG. 9, and the detailed information log is created at P52. 7 management information 231
In the detailed information log file 23 of FIG. In subsequent P53, the major / alarm summary log record 212 shown in FIG. 5 is created from the summary information range shown in FIG. 9 and the record number of the detailed information log stored in P52, and the major / alarm summary log is created in P54. Is stored in the major / alarm summary log file 21 of FIG. 3 according to the management information 211 of FIG.

If it is a minor alarm in the judgment of P4 in FIG. 8, the process proceeds to P61, where the detailed information log record 232 shown in FIG. 7 is created from the range of the detailed information shown in FIG. The log is stored in the detailed information log file 23 of FIG. 3 according to the management information 231 of FIG. In the subsequent P63, the minor / alarm summary log record 222 shown in FIG. 6 is created from the range of the summary information shown in FIG. 9 and the record number of the detailed information log stored in P62, and the minor / alarm summary log is created in P64. the in accordance with the management information 2 2 1 6, stored in the minor alarm summary log file 22 in FIG. 3.

If the information is inhibition information in the determination at P4 in FIG. 8, the process is terminated without storing the information in any failure log file.

As described above, in this embodiment, the fault information is classified into a major alarm and a minor alarm according to their importance, and very small ones are also excluded from the fault information, and the summary information and the detailed information are also excluded. Since the information is classified and stored, the management of the memory becomes clear and orderly, and it can be expected that the cause and analysis of the failure can be efficiently performed. Further, as shown in FIG. 3 and the like, the device management processor 11 including the fault information classification control unit 113 and the like.
Is provided in the packet switch 1 which stores a fixed amount of data and performs data transmission processing in a packet system, so that the overall configuration of the apparatus is simplified and the above-described fault monitoring is performed without affecting the data transmission processing performance. Processing can be executed.

Embodiment 2 FIG. In the first embodiment, the fault information classification control unit 113 in FIG.
Each time the fault information shown in FIGS. 2 to 9 is received, the summary information is classified and stored in the major / alarm summary log file 21 and the minor / alarm summary log file 22. The fault information aggregation buffer 1141 for temporarily storing the fault information and a fault information aggregation monitoring timer for monitoring the time from the occurrence of the same failure information to the recovery and the time from the recovery to the next occurrence in the configuration of FIG. 1142 is added, and when the occurrence / recovery of the same fault information is continuously repeated within the range defined by the monitoring timer, a major alarm summary log file, a minor alarm summary log file, and a detailed information log file The end time of the repetition and the number of repetitions of occurrence / recovery are added to the log record of the fault information stored in the When the occurrence / recovery of the same failure information is continuously repeated by providing the failure information aggregation monitoring unit 114, a series of start time, end time, and repetition of the occurrence / recovery of the failure information are repeated. It can also be summarized in the number of times.

The phenomena targeted for the aggregation processing include, for example, a result of an abnormal operation in the switching network, within a short time of about several seconds set by the monitoring timer 1142.
It is assumed that the same information detected as fault information repeats its occurrence / recovery a plurality of times. In such a case, if the information of each occurrence and recovery is individually stored as one piece of failure information in each log file, the storage capacity becomes insufficient, and the usefulness as the failure information is low. A series of information detected under the above-mentioned conditions is collected and handled, and efficiency is improved from both hardware and software. Hereinafter, the second embodiment will be described in more detail.

FIG. 10 shows the failure information aggregation buffer 11 of FIG.
FIG. 41 is a diagram illustrating a configuration of a first embodiment. a is a buffer number, b is a valid / invalid flag for distinguishing use / non-use of the buffer, c is a message number for identifying the type of failure information, d
Is the location of occurrence of the fault, e is the first occurrence / recovery time at which the repetition of the fault has started, f is the last occurrence / recovery time of the repetition of the fault, and g is the last status of the repetition. H indicates the type of log file in which the failure information is stored and each record No. i indicates an occurrence count indicating the number of times the failure information has been repeated, j is a recovery count indicating the number of times the recovery of the fault information has been repeated.

Next, the operation will be described. FIG. 11 shows FIG.
8 shows the processing procedure of the part related to the aggregation of the failure information performed after P1 of the classification procedure shown in FIG. In Q1 of FIG. 11, the fault information received from the fault information
The same message No. and the same occurrence location are searched for from the trouble information aggregation buffer 1141 of the above, and the same trouble information is determined in Q2. When it is determined that the same failure information is present, the last occurrence / recovery time f on the failure information aggregation buffer in FIG. 10 is determined in Q3, and the final state g is determined in Q4.
In step Q5, the occurrence count i and the recovery count j are rewritten to the received failure information.
Thereafter, the process ends without storing the failure log in each log file as shown in FIG.

On the other hand, if the same failure information is not determined in all the failure information aggregation buffers in Q2 and Q2 ', the procedure proceeds to Q6, and the valid / invalid flag in the failure information aggregation buffer is An invalid, unused failure information aggregation buffer is found, and the message number of the failure information received in Q7 is changed from the message number of FIG.
10 is written from the occurrence of the failure information received in Q8 to the occurrence / recovery time of the failure information received in Q9.
When the recovery time and the last occurrence / recovery time of f are written equally, the final state of g in FIG. 10 is written from the distinction between the occurrence / recovery of the failure information received in Q10, and if the failure information received in Q11 occurs, The occurrence count of i in FIG. 10 is incremented, and in the case of recovery, the recovery count of j in FIG. 10 is incremented. Thereafter, in Q12, the detailed information log file and the major / alarm summary log file or the minor / alarm summary log file are stored. Store the error log. Further, the log write destination, file type, and record No. of h in FIG. 10 are written (Q13), and the process is ended. Note that the processing procedure in Q12 follows the procedure from P4 in FIG. 8 described in the first embodiment.

Next, the fault information temporarily stored in the fault information collecting buffer shown in FIG. 10 is collected into a major alarm summary log file 21, a minor alarm summary log file 22, and a detailed information log file shown in FIG. The failure information aggregation monitoring unit 114 of FIG.
Will be described.

FIG. 12 shows the processing procedure of the fault information aggregation monitoring unit 114. The process of FIG. 12 is periodically started. The cycle at that time takes a value sufficiently smaller than the set value of the monitoring timer.

First, at R1 in FIG. 12, the final state g of the valid / invalid flag b of the failure information aggregation buffer in FIG. 10 is checked. To determine its status in R2, the process proceeds to R31 when it was generated, to calculate the value obtained by subtracting the last occurrence time from the current time as delta _1. Comparing the monitoring timer value until recovery from generating a delta ₁ in R32, the flow proceeds to R33 when towards the delta ₁ is greater. In R33, the last occurrence / recovery time f, occurrence count i, and recovery count j in the failure information aggregation buffer in FIG. 10 are read, and in R34, the type of the log file storing the corresponding failure information and its record No. If the error log record at the storage destination is a major / alarm summary log file or a minor / alarm summary log file in R35, the log record 212 in FIG. 5 or the log record 222 in FIG. Then, for the aggregated information 212g, 222g, the occurrence count and the recovery count of the number of repetitions 212g1, 222g1, the last occurrence / recovery time 212g2,
222g2, the valid / invalid flag b is invalidated (R36), and the process ends. If towards the delta ₁ in the previous R32 is not large, the process ends.

[0057] Further, the flow advances to R41 when the final state g was recovered in the determination of R2 in FIG. 12, calculates a value obtained by subtracting the final recovery time from the current time as the delta _2. R4
2 delta ₂ and compares the monitoring timer value until occurrence from the recovery,
Proceed to the R43 in the case towards the Δ ₂ is large. Hereafter, R43,
In R44, R45, and R46, the above-described R3
3, the same processing as R34, R35 and R36 is performed. If towards the delta ₂ in the previous R42 is not large, the process ends. The above is executed for all buffers (R36 ').

Embodiment 3 FIG. In the first embodiment, the fault information classification control unit 113 in FIG.
Each time the fault information shown in FIGS. 2 to 9 is received, the summary information is classified and stored in the major / alarm summary log file 21 and the minor / alarm summary log file 22. The following elements are added to the configuration of the third device management processor 11. That is, a terminal 3 used as a maintenance console is connected to the packet switch 1 of FIG. 1, and a terminal communication control unit 115 for performing communication in a non-procedural manner, and in accordance with a display request from the terminal, a required The major alarm stored in the alarm summary log file is read and sent to the terminal 3 for display. In addition to the major alarm, the major alarm is stored in the minor alarm summary log file in response to a selection request from the terminal 3. A failure log display control unit 116 that reads out the detailed information of the minor / alarm and the failure stored in the detailed information log file and sends it to the terminal 3 for display.
Reduces the cost of constructing a packet-switched network by displaying fault information selectively from the fault log file and performing fault analysis without constantly connecting a dedicated network management device to the packet-switched network. In addition, a load caused by extra traffic other than the traffic of the user communication in the network is prevented.

Next, the operation will be described. FIG. 13 shows FIG.
When the maintenance console 3 is connected to the packet switch 1 of FIG. 3 and the contents of the major alarm summary log file 21, the minor alarm summary log file 22, and the detailed information log file 23 of FIG.
Terminal communication control unit 115 and failure log display control unit 116
Represents the processing procedure.

At 301 in FIG. 13, a terminal used as a maintenance console is connected to the packet switch. At this time, the terminal communication control unit recognizes that the maintenance console is connected by detecting the significance of the physical signal line with the terminal, for example, the ON of the RS signal in the RS-232C. The terminal communication control unit that has recognized the connection sends a connection message to the terminal at 302 and displays it. When a failure log display request is issued from the maintenance console at 303, the terminal communication control unit passes the request to the failure log display control unit, and the failure log display control unit sequentially reads the contents of the major / alarm summary log file. The summary log data is sent to the maintenance console via the terminal communication control unit and displayed. When a selection request for a major / alarm summary log display is sent from the maintenance console in 305, the terminal communication control unit passes the request to the failure log display control unit, and the failure log display control unit sequentially reads the contents of the major / alarm summary log file. In step 306, the major / alarm summary log data is sent to the maintenance console via the terminal communication control unit and displayed. When the maintenance console sends a request to select a minor / alarm summary log display from the maintenance console at 307, the terminal communication control unit passes the request to the failure log display control unit, and the failure log display control unit transmits the contents of the minor / alarm summary log file. The log data is sequentially read, and at 308, the minor / alarm summary log data is sent to the maintenance console via the terminal communication control unit and displayed. Further, when the maintenance console sends a selection request for detailed information log display from the maintenance console at 309, the terminal communication control unit passes the request to the fault log display control unit, and the fault log display control unit sequentially reads the contents of the detailed information log file. Sends the detailed information log data to the maintenance console via the terminal communication control unit for display. Finally, disconnect the terminal (31
1) The terminal communication control unit detects that the RS signal has been turned off, and recognizes that the terminal has been disconnected.

Embodiment 4 FIG. In the first embodiment, the fault information classification control unit 113 in FIG.
Each time the fault information shown in FIGS. 2 to 9 is received, the summary information is classified and stored in the major / alarm summary log file 21 and the minor / alarm summary log file 22. 11 is provided with a plurality of failure information classification tables 1131, a schedule management table 1171 in which the times at which the failure information classification tables are switched is defined in advance, and a failure information classification table switching operation for switching the failure information classification tables according to the definition. By providing the control unit 117, fault information that constantly occurs in operation in the packet switching network (for example, a host computer that has joined the packet switching network as a packet-type terminal, closes every night on a regular basis, Information on failure occurrence / recovery of subscriber line of packet switch according to start of operation Can be automatically suppressed.

FIG. 14 is a diagram showing the configuration of the schedule management table 1171 of FIG. “a” indicates a switching type for discriminating whether designation of the switching timing is daily or one-time only, “b” indicates switching (day) time, and “c” indicates a table number of the switching failure information classification table.

Next, the operation will be described. FIG. 15 shows FIG.
Represents a processing procedure of the switching operation of the failure information classification table switching control unit 117. The process of FIG. 15 is started periodically. The cycle at that time is about 1 second. First, in S1, the switching type a of the schedule management table is read. The switching type is determined in S2, and if it is a one-time designation, the process proceeds to S3 to check whether the current date and the switching date in the schedule management table are equal. If they are equal, the process proceeds to S4, and it is checked whether the current time is equal to the switching time on the schedule management table. If the switching type is daily in S2, the process skips S3 and proceeds directly to S4. If the current time is equal to the switching time in S4, the process proceeds to S5. In S5, the switching failure information classification table number c on the schedule management table is read, and is set as an effective failure information classification table number. Thereafter, the failure information classification control unit 113 of FIG. 3 performs processing based on the failure information classification table of this number. If the values are not equal in S3 and S4, the process ends.

FIG. 16 shows the switching operation of the fault information classification table switching control unit shown in FIG. 15, and as shown above, the host computer starts and ends as a subscriber terminal actually connected to the packet switch. FIG. 9 is a diagram illustrating, as an example, a case where failure information is periodically generated due to the failure information. This host computer runs every day at 08:40
Starts at 17:25 and ends at 17:25. Therefore, as for the registered contents of the schedule management table, the switching type is daily, the switching time is 17:25, the switching time is 08:40, and the failure information classification table number to be switched is #.
2 and # 1. On the other hand, regarding the registered contents of the failure information classification tables # 1 and # 2, the importance classification of the message No k indicating the failure information of the DTE line to which the host computer is connected is set to minor, Keep it as a deterrent. As a result, every day when the host computer is operating from 08:40 to 17:
For the time up to 25, the fault information is created as a minor alarm, but for the time from 17:25 when the work ends and the work starts until 08:40 the next day, no fault information is created and a useless fault log is generated. do not do.

Embodiment 5 FIG. In the first embodiment, the fault information classification control unit 113 in FIG.
2 to 9 each time the fault information is received, the summary information is classified according to the contents of the fault information classification table 1131 and stored in the major / alarm summary log file 21 and the minor / alarm summary log file 22. Further, in the fourth embodiment, the failure information classification table switching control unit 117 in FIG.
In accordance with the contents of 171, a case has been described in which a valid failure information classification table is switched from a plurality of previously prepared failure information classification tables 1131, but in the fifth embodiment, the configuration of the device management processor 11 of FIG. A failure information classification table maintenance unit 1132 that maintains the contents of the failure information classification table 1131 in response to a request from a terminal used as a maintenance console, and a schedule management table 11
By providing the schedule management table maintenance unit 1172 for maintaining the contents of the failure management information 71, the classification conditions registered in the failure information classification table and the failure information classification registered in the schedule management table are provided in response to an instruction from the maintenance console. The table switching time and the fault information classification table number can be registered, changed, or deleted while online.

Next, the operation will be described. FIG. 17 shows a processing procedure of the failure information classification table maintenance unit when maintaining the failure information classification table from the maintenance console. In FIG. 17, when a display request for the contents of the current trouble information classification table is issued from the maintenance console at 301, the request is transmitted to the trouble information classification table maintenance unit via the terminal communication control unit. The failure information classification table maintenance unit reads out the contents of the failure information classification table on the packet switch, and
2 is sent to the maintenance console via the terminal communication control unit and displayed. Next, when the maintenance console issues a registration request for the fault information classification table at 303, the request is transmitted to the fault information classification table maintenance unit via the terminal communication control unit.
The failure information classification table maintenance unit sends a response indicating whether registration of the failure information classification table is possible to the maintenance console via the terminal communication control unit at 304 and displays the response. If registration is possible, the failure information classification table created on the maintenance console is sent as registration data at 305 to the failure information classification table maintenance unit via the terminal communication control unit. The failure information classification table maintenance unit receives this, registers it as a new failure information classification table, and stores the registered table number in 306.
Is sent to the maintenance console via the terminal communication control unit for display. If additional registration is not possible due to restrictions on storage capacity or the like, a message to that effect is sent to the maintenance console for display.

Next, when a request for changing the failure information classification table is issued from the maintenance console at 307, the request is transmitted to the failure information classification table maintenance unit via the terminal communication control unit. The failure information classification table maintenance unit reads out the contents of the change target failure information classification table designated at 307, and sends it to the maintenance console via the terminal communication control unit at 308 to display.
In the maintenance console, necessary portions of the failure information classification table are changed, and then the data is sent to the failure information classification table maintenance unit via the terminal communication control unit as change table data in 309. The failure information classification table maintenance unit replaces the failure information classification table with the contents of the change table data sent in 309, and sends the response 310 to the maintenance console via the terminal communication control unit and displays it. Further, when the maintenance console issues a request for deleting the failure information classification table at 311, the request is transmitted to the failure information classification table maintenance unit via the terminal communication control unit. The fault information classification table maintenance unit deletes the deletion target fault information classification table specified in 311 and sends the response to the maintenance console via the terminal communication control unit in 312 for display.

FIG. 18 shows a processing procedure of the schedule management table maintenance unit when the schedule management table is maintained from the maintenance console. In FIG. 18, when a request for displaying the current contents of the schedule management table is issued from the maintenance console at 301, the request is transmitted to the schedule management table maintenance unit via the terminal communication control unit. The schedule management table maintenance unit reads the contents of the schedule management table on the packet switch,
The display data of 302 is sent to the maintenance console via the terminal communication control unit and displayed. Next from the maintenance console 303
When a request for changing the schedule management table is issued, the request is transmitted to the schedule management table maintenance unit via the terminal communication control unit. The schedule management table maintenance unit has 30
The contents of the schedule management table to be changed designated at 3 are read out and sent to the maintenance console via the terminal communication control unit at 304 for display. In the maintenance console, necessary portions of the schedule management table are changed, and then the data is sent as change table data to the schedule management table maintenance unit via the terminal communication control unit in 305. The schedule management table maintenance unit replaces the schedule management table with the contents of the change table data sent in 305, sends the response of 306 to the maintenance console via the terminal communication control unit, and displays it.

Embodiment 6 FIG. In the third embodiment, the terminal communication control unit 115 shown in FIG.
The terminal 3 to be used as a maintenance console is connected to the server, and communication is performed in a non-procedural manner. In response to a display request from the maintenance console, the fault log display control unit 116 in FIG. The stored major alarm is read out and sent to the terminal for display.
FIG. 3 shows a case where, in addition to the alarm, the minor alarm stored in the minor / alarm summary log file and the detailed information of the failure stored in the detailed information log file are read out and sent to the maintenance console for display.
The configuration of the device management processor 11 automatically detects the status of the connection of the maintenance console, receives the fault summary information of the major alarm and the minor alarm from the fault information classification control unit 113, and By providing the failure message display control unit 118 for sending and displaying the information to the user, it is also possible to notify the operator of the occurrence state of the failure in real time.

Next, the operation will be described. FIG. 19 shows that the failure message display control unit 118 sends the major alarm and the minor alarm notified from the failure information classification control unit 113 to the maintenance console 3 via the terminal communication control unit 115 while the maintenance console is connected. It is a figure which shows the operation | movement which carries out forward display. Initially, when the maintenance console is not connected, the RS
The signal recognition is OFF, and the failure message display control unit discards the alarm even if it receives the notification of the major alarm and the minor alarm from the failure information classification control unit. On the other hand, when the maintenance console is connected in 301, the terminal communication control unit recognizes that the RS signal is ON, and the connection message 302
To the maintenance console for display. Further, the fault message display control unit refers to the terminal communication control unit's recognition of the ON of the RS signal, and thereafter transmits the major alarm and the minor alarm notified from the fault information classification control unit to the terminal communication control unit at 303. To the maintenance console for display. Further, when the maintenance console is disconnected at 304, the terminal communication control unit recognizes that the RS signal is OFF, and the fault message display control unit refers to this, and thereafter, the fault information classification control unit issues a major alarm and a minor alarm. Discard even if notified.

Next, FIG. 20 shows the trouble message display control unit 1.
18 shows a processing procedure in FIG. First, T1
Receives a notification of a major alarm or a minor alarm from the failure information classification control unit. Then T2
Then, the terminal communication control unit checks the recognition of the RS signal, and determines whether the RS signal is ON or OFF at T3.
If the RS signal is ON, the process proceeds to T4, in which the received major alarm or minor alarm fault summary information is sent to the maintenance console via the terminal communication control unit and displayed. If the RS signal is OFF at T3, the process ends.

Embodiment 7 FIG. In the sixth embodiment, while one terminal used as a maintenance console is connected by the terminal communication control unit 115 of FIG.
18 automatically detects the connected state of the maintenance console, receives the summary information of the major alarm and the minor alarm from the failure information classification control unit 113, and sends the summary information to the maintenance console for display. Although the case has been described, the configuration of the device management processor 11 in FIG. 3 includes a terminal communication control unit 115 that performs non-procedural communication with a plurality of terminals used as a maintenance console, and a state in which the plurality of maintenance consoles are connected. The terminal type management table 1 shown in FIG. 21 is automatically detected, and the major alarm or minor alarm failure summary information or detailed information from the failure information classification control unit 113 is shown in FIG.
By providing the fault message display control unit 118 for sending and displaying the corresponding terminal number to the maintenance console in accordance with the registered contents of the terminal 181, each type of fault information individually requested by a plurality of operators relating to each terminal is provided. It can also be displayed on the terminal immediately to facilitate the trouble information analysis of each operator.

FIG. 21 shows the structure of the terminal type management table 1181. a is a terminal number for identifying each terminal when a plurality of maintenance consoles 3 are connected to the packet switch of FIG. 1, and b is a display type for registering a type of fault information displayed for each terminal number. Specifies the summary information of the major alarm, the summary information of the minor alarm, or the detailed information. In the example of FIG.
The two terminals are connected as a maintenance console. For the maintenance console of the terminal number 1, summary information of the major alarm is displayed, and for the maintenance console of the terminal number 2, summary information of the minor alarm is displayed. Is displayed, and detailed information is displayed for the maintenance console of terminal number 3. Of course, a single terminal can register a plurality of types of fault information.

Next, the operation will be described. FIG. 22 shows FIG.
Based on the registration contents of the terminal type management table 1181, the failure message display control unit 118 transmits the major alarm, minor alarm, and detailed information from the failure information classification control unit 113 via the terminal communication control unit 115, respectively. It is a figure which shows operation | movement which sends to three corresponding maintenance consoles and displays. First, in a state where all three maintenance consoles are not connected, the terminal communication control unit recognizes the RS signal for each terminal is OFF, and the failure message display control unit issues a major alarm, Discard even if minor alarms and detailed information are notified. On the other hand, at 301, terminal number 1,
When terminal number 3 is connected with terminal number 2 and 303 at 302, the terminal communication control unit recognizes that the RS signals of terminal number 1, terminal number 2 and terminal number 3 are ON, and transmits connection messages 304, 305 and 306 respectively. It is sent to terminal number 1, terminal number 2 and terminal number 3 and displayed. Further, the fault message display control unit refers to the terminal number 1, the terminal number 2, and the terminal number 3 of the terminal communication control unit and recognizes the ON state of each of the RS signals, and thereafter, refers to the terminal type management table shown in FIG. According to the contents, when a major alarm is received from the fault information classification control unit, it is sent to the maintenance console of terminal number 1 at 307 and displayed, and when a minor alarm is received, it is sent and displayed at 308 to the maintenance console of terminal number 2. When the detailed information is received, the detailed information is sent to the maintenance console of the terminal number 3 at 309 for display. Also, 310, 31
When the maintenance consoles of the terminal numbers 1, 2, and 3 are disconnected at 1, 312, respectively, the terminal communication control unit sends the OF signals of the terminal signals 1, 2, and 3 to the OF signal.
F, the failure message display control unit refers to this, and thereafter receives the major alarm, the minor alarm, and the detailed information from the failure information classification control unit, and receives the terminal number 1, the terminal number 2, These are discarded without being sent to the maintenance console of terminal number 3 for display.

Next, FIG. 23 shows the trouble message display control unit 1.
18 shows a processing procedure in FIG. First, U1
Receives fault information from the fault information classification control unit. Thereafter, it is determined whether the failure information received at U2 is a major alarm, a minor alarm, or detailed information. At U3, a major alarm, a minor alarm, and detailed information are determined. If it is a major alarm, the process proceeds to U41.
In U41, the display type b in the terminal type management table of FIG.
Is a major alarm, reference is made to the recognition of the RS signal ON / OFF state in the terminal communication control unit for that terminal number a. The state of the RS signal is determined in U42, and if the RS signal is ON, the corresponding major alarm is sent to the maintenance console of the corresponding terminal number via the terminal communication control unit and displayed in U43. If the state of the RS signal is OFF in U42, the processing is terminated as it is. The above processing is repeated for all the terminals whose display type b is registered as a major alarm (U43 ').

If the judgment at U3 is a minor alarm, the process proceeds to U51. In U51, when the display type b of the terminal type management table of FIG. 21 is a minor alarm, the terminal communication control unit recognizes the RS signal ON / OFF state corresponding to the terminal number a. The state of the RS signal is determined in U52, and if the RS signal is ON, the corresponding minor alarm is sent to the maintenance console of the corresponding terminal number via the terminal communication control unit and displayed in U53. In U52, the state of the RS signal is OF
If it is F, the process ends. The above processing is repeated for all terminals for which the display type b is registered as a minor alarm (U53 '). Furthermore, U
If the determination in 3 is detailed information, the flow proceeds to U61. In U61, when the display type b of the terminal type management table in FIG. 21 is the detailed information, the terminal communication control unit recognizes the RS signal ON / OFF state corresponding to the terminal number a. The state of the RS signal is determined in U62, and if the RS signal is ON, the corresponding detailed information is transmitted to the maintenance console of the corresponding terminal number via the terminal communication control unit and displayed in U63. In U62, the state of the RS signal is OF
If it is F, the process ends. The above processing is repeated for all the terminals for which the display type b is registered as the detailed information (U63 ').

Embodiment 8 FIG. Lastly, in the sixth embodiment and the seventh embodiment, when one or more terminals used as a maintenance console are connected by the terminal communication control unit 115 of FIG. 3 is automatically detected, and when fault information is received from the fault information classification control unit 113, it is sent to the maintenance console for display. However, the configuration of the device management processor 11 in FIG. When a major alarm is received from the failure information classification control unit 113, an alarm output control unit 119 that performs an electrical contact output is provided, so that the alarm device 4 such as a lamp or a buzzer is simply connected to the packet switch 1 in FIG. The occurrence of a critical failure can be immediately notified to the outside.

FIG. 24 shows that the alarm output control unit 119 shown in FIG.
FIG. 9 is a diagram showing a configuration of an alarm contact output flag for performing an alarm contact output in response to a major / alarm notification from a failure information classification control unit 113. From bit 0 to bit 31
For each type of fault information of the corresponding major alarm, 1 is set when the fault occurs, and reset to 0 when the fault is recovered.

Next, the operation will be described. FIG. 25 shows FIG.
It is a figure which shows the processing procedure of the alarm output control part. When a major / alarm notification is received from the fault information classification control unit in V1, the fault information is examined in V2 to determine whether a fault has occurred or has been recovered. If a fault has occurred, the process proceeds to V3, where the bit corresponding to the type of the fault information in the alarm output control unit in FIG. 24 is set to 1. If it is determined in V2 that the fault has been recovered, the process proceeds to V4, and the bit corresponding to the type of the fault information in the alarm output control unit in FIG. 24 is reset to 0. Thereafter, the program proceeds to V5, where the value of the alarm output contact flag pattern is checked. The value is determined in V6, and if it is not 0, that is, all the alarm output contact flags are set to 0
If not, the process proceeds to V7, and an alarm is issued with the alarm contact output as significant. 0
, That is, all flags of the alarm output contact flags are 0
If the state has been reset, the alarm contact output is insignificant and the alarm is released.

In the above description, the type of the major alarm is not displayed.
The type may be determined from the bit position indicated by, and the type may be displayed simultaneously with the alarm. Further, the output to the alarm device 4 is not necessarily limited to the form of the electrical contact output.

Further, in each of the above embodiments, in a packet switching network in which a communication network is constituted by a plurality of packet switches, information on a fault occurring in a monitored device connected to each packet switch is processed. Although the present invention has been described, the present invention is not limited to the packet-switched network, and can be widely applied to monitoring and processing of fault information in various communication networks using other methods, and has the same effect.

[0082]

As described above, according to the first aspect of the present invention, a fault detecting unit for detecting a fault in a network,
A failure information generation unit that generates failure information relating to the failure, a failure classification table in which conditions for classifying the failure information into a major alarm and a minor alarm are registered in advance according to the definition of the importance of the failure information, A failure information classification control unit that classifies the failure information according to the information and divides the content of the failure information into summary information and detailed information is provided, and a major alarm summary log file and a minor alarm summary log file that store respective failure information. A detailed information log file is provided to separately store network fault information. From the contents of these log files, important fault information of the network operator can be grasped and the global fault status can be monitored. Easier understanding, effective identification of failure cause, and efficient analysis A.

According to the second aspect of the present invention, a failure information aggregation buffer for temporarily storing failure information, the time from the occurrence of the same failure information to recovery, and the next generation after recovery. A failure information aggregation monitoring timer that monitors the time until the failure information is collected, and a failure information aggregation monitoring unit that performs failure information aggregation processing within the monitoring time range. By monitoring the same fault information, in a predetermined case, the same fault information is continuously generated / recovered, and the occurrence / recovery of the fault information is determined.
Since a series of recovery start and end times and the number of repetitions are stored as failure logs, the cause of the failure can be isolated and analyzed efficiently from the contents of these log files. The log file that stores the fault information overflows, and as a result, the previously stored important fault information may be deleted by overwriting, or the important fault information that has occurred later may be stored in the storage device. There is an effect of preventing failure isolation and analysis from becoming impossible due to the inability to store data because there is no free space.

According to the third aspect of the present invention, a terminal used as a maintenance console is connected, and the contents of the accumulated major alarm summary log file, minor alarm summary log file, and detailed information log file are stored. A failure log display control unit is provided for sending and displaying a major alarm stored in a major / alarm summary log file in accordance with a display request from the terminal, and sending and displaying the major alarm to the terminal. Reads the minor alarm stored in the minor alarm summary log file in addition to the major alarm and detailed information of the fault stored in the detailed information log file in response to a selection request from the terminal, and sends it to the terminal for display. As a result, there is no need to constantly connect a dedicated network management device to the network. The fault information is selectively displayed using the network, fault isolation and analysis are performed to reduce the cost of network construction and to prevent the load caused by extra traffic other than user communication traffic in the network. .

According to the fourth aspect of the present invention, there are provided a plurality of the fault information classification tables, a schedule management table in which the switching times of the fault information classification tables are defined in advance, and a fault for performing the table switching operation. An information classification table switching control unit is provided to automatically switch from a plurality of failure information classification tables to a valid failure information classification table in accordance with the contents of the schedule management table. Fault information that occurs regularly in operation (for example, when a host computer subscribing as a terminal finishes work every night and starts work every morning,
This is effective in automatically suppressing cases in which recovery failure information is generated.

According to the fifth aspect of the present invention, a failure information classification table maintenance unit that maintains the contents of the failure information classification table from a terminal used as a maintenance console, and maintains the contents of the schedule management table. A schedule management table maintenance unit is provided so that the registered contents of the fault information classification table and the registered contents of the schedule management table can be registered, changed, and deleted online while responding to an instruction from the maintenance console. With this configuration, the operator can easily change the conditions for classification according to the importance of the failure and change the schedule for switching those conditions at a fixed time online during network operation. There is.

According to the invention of claim 6, a terminal used as a maintenance console is connected, the terminal recognizes the state of being connected, and the terminal receives a major alarm from the fault information classification control unit. , A fault message display control unit that receives fault summary information for each minor alarm and sends it to the terminal for display is provided, receives fault summary information for each of the major alarm and minor alarm, and immediately sends it to the terminal. Is displayed on the display, so that the operator can be notified of the failure occurrence status in real time.

According to the seventh aspect of the present invention, a plurality of terminals used as a maintenance console are connected, each terminal recognizes a connected state, and a major alarm, A fault message display control unit that sends and displays the fault summary information and detailed information of each minor alarm is provided, and sends the fault summary information and detailed information of each major alarm and minor alarm to separate terminals. Since it is configured to be able to display, the fault information that has occurred is classified according to the importance of the fault, and the content of the fault information is divided into summary information and detailed information, and immediately displayed on separate terminals. In addition, it is possible to allow a plurality of operators to share the analysis of the fault information, and to effectively perform the cause identification and the analysis of the fault.

According to the invention of claim 8, the alarm output control unit is provided so that when a major alarm is received, the occurrence of the major failure is immediately notified to the outside. Even if the terminal used as a maintenance console is not connected to the system, if an important failure occurs, it can be notified immediately and an alarm can be issued to the operator. effective.

According to the ninth aspect of the present invention, since the above-described network monitoring method is applied particularly to a packet-switched network, various types of fault information generated in a large number of monitored devices connected to this network can be appropriately used. In particular, the effect that the trouble information can be easily grasped, and the cause of the trouble can be identified and analyzed efficiently can be greatly expected.

[Brief description of the drawings]

FIG. 1 is a configuration diagram showing an entire packet switching network applied to Embodiments 1 to 8 of the present invention.

FIG. 2 is a configuration diagram of a packet switch in the embodiment.

FIG. 3 is a configuration diagram of an apparatus management processor in the embodiment.

FIG. 4 is a configuration diagram of a failure information classification table in the embodiment.

FIG. 5 is a configuration diagram of a major / alarm summary log file in the embodiment.

FIG. 6 is a configuration diagram of a minor / alarm summary log file in the embodiment.

FIG. 7 is a configuration diagram of a detailed information log file in the embodiment.

FIG. 8 is an explanatory diagram of an operation of a fault information classification control unit according to the first embodiment of the present invention.

FIG. 9 is a configuration diagram of fault information passed from a fault information generation unit to a fault information classification control unit in the embodiment.

FIG. 10 is a configuration diagram of a failure information aggregation buffer according to a second embodiment of the present invention.

FIG. 11 is an explanatory diagram of an aggregation operation of the failure information of the failure information classification control unit in the embodiment.

FIG. 12 is an explanatory diagram of an operation of a fault information aggregation monitoring unit in the embodiment.

FIG. 13 is an explanatory diagram of a display sequence by a failure log display control unit according to the third embodiment of the present invention.

FIG. 14 is a configuration diagram of a schedule management table in Embodiment 4 of the present invention.

FIG. 15 is an explanatory diagram of an operation of a failure information classification table switching control unit in the embodiment.

FIG. 16 is a diagram showing an example of switching contents in the embodiment.

FIG. 17 is an explanatory diagram of a maintenance sequence of a failure information classification table maintenance unit according to the fifth embodiment of the present invention.

FIG. 18 is an explanatory diagram of a maintenance sequence of a schedule management table maintenance unit in the embodiment.

FIG. 19 is a diagram illustrating a display sequence of a failure message display control unit according to the sixth embodiment of the present invention.

FIG. 20 is an explanatory diagram of an operation of the failure message display control unit in the embodiment.

FIG. 21 is a configuration diagram of a terminal type management table in Embodiment 7 of the present invention.

FIG. 22 is an explanatory diagram of a display sequence of a failure message display control unit in the embodiment.

FIG. 23 is an explanatory diagram of an operation of the fault message display control unit in the embodiment.

FIG. 24 is a configuration diagram of an alarm contact output flag in Embodiment 8 of the present invention.

FIG. 25 is a diagram illustrating the operation of the alarm output control unit in the embodiment.

FIG. 26 is a configuration diagram of a conventional failure diagnosis result display method for an information processing system.

FIG. 27 is a configuration diagram of a conventional network monitoring system.

[Explanation of symbols]

1 Packet Switch 11 Packet Switch Device Management Processor 111 Packet Switch Fault Detection Unit 112 Packet Switch Fault Information Generation Unit 113 Packet Switch Fault Information Classification Control Unit 1131 Fault Information Classification Table 1132 Fault Information Classification Table Maintenance Unit 114 Packet Switch Failure information aggregation monitoring unit 1141 Failure information aggregation buffer 1142 Failure information aggregation monitoring timer 115 Terminal communication control unit of packet switch 116 Failure log display control unit of packet switch 117 Failure information classification table switching control unit of packet switch 1171 Schedule management table 1172 Schedule Management table maintenance unit 118 Fault message display control unit of packet switch 119 Alarm output control unit of packet switch 2 External storage device of packet switch 21 Measure -Alarm summary log file 22 Minor alarm summary log file 23 Detailed information log file 3 Maintenance console of packet switch 4 Alarm device connected to packet switch 5 Relay line of packet switch 6 Subscriber terminal of packet switch

──────────────────────────────────────────────────続 き Continuing on the front page (51) Int.Cl. ⁶ identification symbol FI H04Q 11/04 (58) Field surveyed (Int.Cl. ⁶ , DB name) H04L 12/24

Claims (9)

(57) [Claims] 1. A failure detection unit that detects a failure that occurs in a monitored device that constitutes a communication network, a failure information generation unit that generates failure information in response to a detection notification from the failure detection unit, and a failure information generation unit. Is classified into a major alarm (heavy failure information) and a minor alarm (light failure information) according to the definition of its importance in accordance with a predefined failure information classification table. A failure information classification control unit that classifies the content into summary information that is limited to major information such as an occurrence time and an occurrence location and detailed information including all information that can be collected regarding the failure, and the failure information Major / alarm summary log file, minor / alarm summary log file that stores fault information classified by the classification control unit,
Network monitoring method with detailed information log file. 2. A failure information aggregation monitoring timer, and a failure information aggregation buffer for temporarily storing the failure information when occurrence / recovery of the same failure information is continuously repeated within a set time of the timer. , And a summary of the start / end time and the number of repetitions of the occurrence / recovery of the fault information and storing the fault information in a major alarm summary log file, minor alarm summary log file, and detailed information log file 2. The network monitoring system according to claim 1, further comprising a failure information aggregation monitoring unit that performs the monitoring. 3. A terminal to be used as a maintenance console is connected, and in response to a display request from the terminal, a major / alarm stored in a major / alarm summary log file is required.
The alarm is read out and sent to the terminal, and the major / alarm stored in the major / alarm summary log file and the minor / alarm stored in the minor / alarm summary log file in response to a selection request from the terminal.
3. The network monitoring system according to claim 1, further comprising a failure log display control unit that reads out the detailed failure information stored in the alarm or detailed information log file and sends the read detailed information to the terminal. 4. A failure information classification table switching control unit for providing a plurality of failure information classification tables and switching a failure information classification table to be applied at a predetermined time according to the definition content of a schedule management table defined in advance. 4. The network monitoring method according to claim 1, wherein: 5. A terminal to be used as a maintenance console is connected, and definition contents of a failure information classification table and a schedule management table are registered according to an instruction from the terminal.
5. The network monitoring system according to claim 4, further comprising: a failure information classification table maintenance unit for changing and deleting, and a schedule management table maintenance unit. 6. A terminal used as a maintenance console is connectable, and when the terminal is connected, the connection is detected, and a major alarm, a minor alarm, a minor
3. The network monitoring system according to claim 1, further comprising a fault message display control unit that receives fault summary information of each of the alarms and sends it to the terminal for display. 7. A method in which a plurality of terminals are provided, a type of fault information to be displayed is set in advance for each terminal, and the predetermined type of fault information is sent and displayed according to the connection of each terminal. 7. The network monitoring method according to claim 6, wherein: 8. An alarm output control unit for receiving a major alarm from the fault information classification control unit and notifying the occurrence of the serious fault to the outside.
The network monitoring method according to any one of the above. 9. A packet switching network in which a communication network is constituted by a plurality of packet switches, wherein information on a fault occurring in a monitored device connected to each of said packet switches is processed. The network monitoring method according to any one of the above.