JP2748832B2 - Network fault management 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 fault management method and, more particularly, to a network fault management method for managing a fault alarm generated during maintenance work on a device in a network.

[0002]

2. Description of the Related Art Conventionally, a network management system for managing a plurality of devices connected to a network is shown in FIG.
The configuration was as shown in FIG. FIG. 4 is a configuration diagram showing a conventional network management system, and particularly shows a network management system for managing an in-company network connecting a remote office and a head office.

In FIG. 1, reference numeral 1 denotes a telephone terminal accommodated in a private branch exchange 2 installed at a head office, and 3 denotes a private branch exchange 2
A multiplexing device at the head office for multiplexing a line to a remote office among the lines accommodated in the network, and a line termination connecting the multiplexing device 3 to a dedicated line 5 connecting the head office and the office. Device.

[0004] Reference numeral 6 denotes a line terminating device for connecting the dedicated line 5 to the multiplexer 7 installed in the business establishment. Reference numeral 8 denotes a business establishment that accommodates the line from the multiplexer 7 and the telephone terminal 9. The private branch exchange 8 on the side.

[0005] A management terminal 10 manages each device connected to the network via a management line.
A failure alarm notified from the multiplexing device 7 at the business office to the management terminal 10, 52 is a failure alarm notified from the private branch exchange 8 at the business office to the management terminal 10, and 53 is a multiplexing device 3 at the head office. Is a failure log information indicating a failure alarm notified from each device to the management terminal 10, and 11 is a failure log information storage device for storing the failure log information 54. is there.

Now, when a maintenance work is performed on the multiplexing device 7 at the business office based on a predetermined work plan in this network, the multiplexing device 7 that is the work target of the maintenance work performs the maintenance work. The management terminal 10 is notified of a failure alarm 51 relating to the place where the operation has stopped.

The management terminal 10 determines, based on the work date and time and the work target device, of the work information input as the work plan, that the fault alarm 51 is caused by the maintenance work currently being performed. Unlike the normal failure alarm processing, the notification to the administrator by screen display or the like is suppressed, and the failure alarm 51 is not recorded as the failure log information 55.

[0008]

Therefore, in such a conventional network fault management method, a notification is given during maintenance work based on the work date and time and the work target device in the work information input as a work plan. The problem is that the alarm that occurs when the maintenance work is carried out from one device to another device is processed as a normal failure alarm. Was.

[0009] That is, in FIG. 4, a failure occurs from the private branch exchange 8 on the business office side or the multiplexing apparatus 3 on the head office side within the influence range of the maintenance work on the multiplexing apparatus 7 on the business office side to be worked. The alarm 52 or 53 is the management terminal 10
Is notified and processed as a normal fault alarm. Even if this is an invalid spread alarm, a number of spread alarms are notified to the administrator by screen display and the like, and the fault log information 54 is displayed as fault log information 54. Storage device 1
1 is recorded.

The present invention is intended to solve such a problem, and it is possible to accurately suppress an invalid spillover alarm that is spilled over due to a maintenance operation, and to eliminate unnecessary management work by a manager due to the spillover alarm. It is another object of the present invention to provide a network fault management method that can perform the above-described process and can avoid useless recording of fault log information.

[0011]

In order to achieve the above object, a network fault management method according to the present invention comprises:
Work target devices and work target locations related to maintenance work to be performed
The ripple alarm that occurs in response to
Including a spread information storage means for previously storing a ripple information includes a device for generating the control terminal of the actual maintenance work
Date and time of work related to this maintenance work,
Based on work information including work target devices and work target locations
And retrieves the work information
Acquisition of the transmission information corresponding to the work information and the acquired transmission information
The information is stored in the work management table in association with the
Referring to this task management table when receiving the over arm to determine its <br/> failure alarm or spread alarm, when a wave及alarm is obtained so as to suppress the notification.

[0012]

[0013]

Therefore, in response to the notification of the fault alarm during the execution of the maintenance work, the work information read out from the spread information storage means based on the work information indicating the contents of the maintenance work is not checked .
By referring to the corresponding spread information, it is determined whether or not the fault alarm is a spread alarm. If the fault alarm is a spread alarm, notification of occurrence of a fault to the administrator is suppressed.

[0014]

Next, the present invention will be described with reference to the drawings. FIG. 1 is a configuration diagram showing a network management system according to one embodiment of the present invention. In FIG. 1, the same reference numerals are given to the same or equivalent parts as described above (FIG. 4).

In FIG. 1, reference numeral 12 denotes a spread information storage device for storing a spread alarm generated based on maintenance work for an arbitrary work target device and a work site and a spread information of a device for generating the alarm, and 55 denotes a spread information storage device. This is ripple information retrieved and output from the ripple information storage device 12 according to the work target device and the work location.

FIG. 2 is an explanatory diagram showing the structures of the spread information table and the work management table. In the figure, 1
Reference numeral 20 denotes a spread information table indexed by the work target, that is, the device name 121 and the work location 122. As the spread information 55, all information notified to the management terminal 10 when the maintenance work is performed on each work target. Of the alarm 124 and the information indicating the generator 123 thereof are stored.

Reference numeral 100 denotes a work management table developed in the management terminal 10 at the time of maintenance work, and based on a work plan input in advance, a work date and time 101, a worker 102, a work target device 103, and a work Target location 104
Work information such as the work target device 1
The spread information 55 retrieved and output from the spread information storage device 12 based on the information 03 and the work target location 104 is registered.

FIG. 3 is a flowchart showing a spread information registration process performed by the management terminal 10 prior to the maintenance work.

Next, the operation of the present invention will be described with reference to FIG. First, the worker has a work schedule of the maintenance work to be performed, the work date and time 101, the worker 102, the work target device 1
The work information such as the information 03 and the work target location 104 is input to the management terminal 10 (step 31), and the work information is registered in the work management table 100 in the management terminal 10.

The management terminal 10 has a work management table 100
Of the work information registered in the transmission information storage device 12 based on the work target device 103 and the work target location 104 of the work information registered in the
(Step 32).

That is, the ripple information table 120 having the device name 121 and the work location 122 equal to the work target device 103 and the work target location 104 registered in the work management table 100 is searched from the ripple information storage device 12.

Here, based on the search result, it is determined whether or not the spread information 55 corresponding to the work target device 103 and the work target location 104 exists (step 33). If the spread information 55 exists, the spread information 55 is determined. That is, the spreading device 123 to which the alarm spreads due to the maintenance work and the spreading alarm 124 notified from this device are read out, registered in the work management table 100 of the management terminal 10 (step 34), and all the corresponding spreading information 55. Is repeated until is registered.

Work target device 103 and work target location 1
When the registration of all the transmission information 55 corresponding to 04 in the work management table 100 ends, the transmission information registration processing ends.

Therefore, as shown in FIG. 1, the multiplexing device 7 at the business office is registered in the work management table 100 as the work target device 103, and the head office is registered as the work target location 104.
When a location related to the dedicated line 5 connecting the offices is registered, the transmission device 123 is executed by the transmission information registration process described above.
The private branch exchange 8 at the business office and the multiplexing device 3 at the head office are registered, and an alarm of the content related to the dedicated line 5 is registered as the spread alarm 124.

Next, the management terminal 10 carries out a maintenance work on the portion related to the dedicated line 5 of the multiplexing device 7 at the business office based on the work information registered in the work management table 100.

As a result, the multiplexing device 7 is forced to stop the operation of the portion related to the dedicated line 5, and detects this, and detects a failure alarm 51 related to the dedicated line 5.
To the management terminal 10.

The private branch exchange 8 at the business office connected to the multiplexing device 7 detects the operation stop of the multiplexing device 7 and notifies the management terminal 10 of a failure alarm 52, that is, a spread alarm to that effect. I do.

Further, the multiplexing device 3 at the head office, which is connected to the multiplexing device 7 via the dedicated line 5, is connected to the private branch exchange 8
In the same manner as the above, the operation stop of the multiplexing device 7 is detected, and the failure alarm 53, that is, the spread alarm to that effect, is transmitted to the management terminal 10.
Notify.

The management terminal 10 refers to the spread information 55 registered in the work management table 100 for each of the notified fault alarms, and thereby spreads the maintenance work currently performed by the fault alarm. Judge whether the alarm has occurred.

Here, if the notification source device and the alarm content of the notified fault alarm do not match any of the spread information 55 registered in the work management table 100, the fault alarm is not a spread alarm. Instead, the management terminal 10 determines that the alarm is based on a fault that has actually occurred, notifies the manager of the fault occurrence by screen display or the like, and records the fault log information 54 in the storage device 11.

When the notification source device and the alarm content of the notified fault alarm match any of the spread information 55 registered in the work management table 100, the fault alarm is a spread alarm. Accordingly, the management terminal 10 suppresses the notification of the occurrence of the failure to the administrator by displaying the screen or the like, and does not perform the recording process on the storage device 11 as the failure log information 54.

Therefore, the administrator can manage the fault alarms 51, 52, 53 notified during the maintenance work by using the management terminal 10
, No useless tracking response processing for these alarms is performed.

[0033]

As described above, according to the present invention, spillover information indicating a spillover alarm which is generated corresponding to a work object is registered in advance, and a spillover alarm is detected based on the spillover information during maintenance work. The notification to the administrator is suppressed.

Therefore, in the network fault management method, an invalid ripple alarm that is caused by the maintenance work can be accurately suppressed, and unnecessary countermeasures by the administrator due to the ripple alarm can be completely eliminated. This has a special effect that unnecessary recording of trouble log information can be avoided.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a network fault management system according to an embodiment of the present invention.

FIG. 2 is a configuration diagram of a failure information table and a work management table.

FIG. 3 is a flowchart showing a transmission information registration process.

FIG. 4 is a configuration diagram of a conventional network fault management system.

[Description of Signs] 1,9 Telephone terminal 2,8 Private branch exchange 3,7 Multiplexer 4,6 Line termination device 5 Dedicated line 10 Management terminal 11 Fault log information storage device 12 Spread information storage device 51-53 Fault alarm 54 Fault log information 55 Spread information 100 Work management table 120 Spread information table

Claims (1)

(57) [Claims] 1. From individual devices constituting a network
It receives the output Ru failure alarms, the failure alarm
In the network failure management method having a management terminal for processing and reporting, a work target device and a work target location related to a maintenance work to be performed.
The ripple alarm that occurs in response to
A transmission information storage unit that stores in advance the transmission information including a device to be generated , wherein the management terminal is involved in the maintenance work input before the maintenance work is performed;
The work date and time, the work
Searching the transmission information storage means based on business information
Acquiring the spread information corresponding to the work information, and associating the work information with the acquired spread information
Store in the management table and refer to the work management table when a failure alarm is received
The fault alarm is determined whether spillover alarms,
Network fault management method comprising the Turkey to suppress notification when a wave及alarm.