JP2004260729A - Operation system, and recovery processing method for communication device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To avoid the execution of the same recovery process to the same device based on the fault message which is caused by one fault and transmitted from the communication device in various timings. <P>SOLUTION: In an automatic process execution operation system 1 for executing the automatic recovery process when receiving a fault message, a history of processes which are executed to the communication device is recorded in an operation history DB. Even when the fault message caused by one fault is transmitted in various timings, by referring to the operation history DB 13, another overlapping processes to the same communication device can be avoided. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to an operation system and a recovery method for a communication device, and more particularly to an operation system and a recovery method for a communication device, which are suitable for executing a recovery process for a failure message from a communication device constituting a communication network. About the method.
[0002]
[Prior art]
When a failure occurs in a communication device constituting the communication network, a failure message is notified from the communication device to each operation system that manages the communication device for each device type and system such as switching, transmission, and wireless.
By analyzing the failure message sent to the operation system, it is possible to execute a recovery measure based on the analysis result. However, it is difficult to identify the failure from many failure messages generated due to one device failure. Conventionally, this operation is performed by a maintenance person, and each operation system that manages the communication device is used. It was necessary to take failure recovery measures by maintenance personnel through the service.
[0003]
On the other hand, in recent years, an automatic action execution operation system that automatically executes a recovery action upon notification of a failure message has been studied (see Non-Patent Document 1).
[0004]
[Non-patent document 1]
CD-ROM "Transactions of the Society of Electronics, Information and Communication Engineers 2002 Society Conference", The Institute of Electronics, Information and Communication Engineers, August 20, 2002, Lecture Number: B-6-76. Examination "
[0005]
[Problems to be solved by the invention]
However, in realizing an operation system that implements the above-described automatic recovery measure method, there is a problem based on the following failure message occurrence phenomenon.
That is, when the recovery measures are automatically performed, during the recovery process of the device, or when the device remains unrecovered, the device notifies the failure message again. For example, when a failure occurs, a failure message of "failure occurred", and in the recovery process, a failure message indicating "not implemented" due to a part of the device being reset due to execution of measures, Until the recovery, the communication device sends a failure message.
[0006]
For this reason, in an operation system that implements the automatic recovery measure method, it is meaningless to analyze and execute a failure message generated by the failure recovery measure or a failure message notified after the measure in the same way as a normal message, and to execute the measure. Endlessly it becomes a load of the system. Further, this causes a problem that it is difficult to quickly recover not only the device concerned but also another failed communication device.
An object of the present invention is to solve the above-mentioned problems and to provide an operation system capable of avoiding execution of duplicate measures and a recovery measure method for a communication device.
[0007]
[Means for Solving the Problems]
An operation system according to claim 1 of the present invention is an operation system that manages a device by executing a process for the device based on a message notified from a device connected via a communication medium,
Processing recording means for recording the executed processing;
Processing determining means for determining processing to be performed on the device based on notification of a new message by referring to processing already performed on the same device based on notification of the message, which is recorded in the processing recording means; , Is characterized by having.
[0008]
With this configuration, it is possible to cope with processing based on the message notified at each timing, and it is possible to efficiently manage the apparatus.
Here, the operation system is a terminal, device, or other management system having the above functions.
The operation system according to claim 2 of the present invention is characterized in that, in claim 1, the message is a failure message for notifying a failure in a communication device constituting a communication network.
[0009]
The operation system having the configuration of claim 1 is particularly effective when performing processing based on a failure message transmitted from a communication device forming a communication network.
That is, since the communication devices are connected to each other by the communication network, a failure message is transmitted from each of the plurality of devices at each timing due to the failure of one device, or the content is different even in a recovery process of the failed device. The transmission timing and the content of the failure message due to one failure such as the transmission of the failure message are various. Even if these cannot be related to all due to one failure, and even if the transmission timings are different, not only the failure message to be notified but also the measures for the communication device are focused on, so that an accurate communication device can be obtained. Can be controlled.
[0010]
Here, the notification of the new message described in claim 1 means a time lag, and does not mean a failure message caused by a new failure.
In an operation system according to a third aspect of the present invention, in the second aspect, when the same processing has already been executed for the same apparatus based on the notification of the message, the processing determining means performs the processing again. Is determined not to be performed.
[0011]
This avoids the execution of duplicate processing for the same device. For example, in the case of performing recovery measures for a failure message, the communication apparatus that has been in the recovery process due to recovery measures such as initialization of software is used. It is possible to avoid a delay in recovery due to initialization or the like, a load on the operation system due to repeated meaningless measures, and a delay in measures for other failures based on the load.
[0012]
The operation system according to claim 4 of the present invention, according to claim 2 or 3, further comprises an action table in which recovery actions for the failure message are defined in stages.
The processing determining means refers to the measure table to determine the execution of a recovery measure having a higher measure than the measure already performed for the unrecovered communication device.
[0013]
By dynamically updating and executing a measure with reference to the measure history in this way, more efficient recovery measures can be taken.
An operation system according to a fifth aspect of the present invention is the operation system according to any one of the second to fourth aspects, further comprising: a failure identification unit that identifies a failure that caused the failure message based on the notification of the failure message. In addition,
The process determining unit refers to a process that has already been executed based on a notification of a failure message caused by the same failure specified by the failure specifying unit, and determines a process based on notification of a new message. Features.
[0014]
A recovery method for a communication device according to claim 6 of the present invention is a recovery method for executing a recovery measure for the communication device based on a failure message notified from the communication device,
On the basis of a record of recovery measures already performed on the same communication device, recovery measures for the communication device based on notification of a new failure message are determined and executed.
[0015]
According to a sixth aspect of the present invention, in the method for recovering a communication device according to the seventh aspect, when the same process has already been performed on the same device based on the notification of the message, the process is performed again. It is characterized by not having.
The method for recovering a communication device according to claim 8 of the present invention is characterized in that, in claim 6 or 7, a recovery measure having a higher-level measure than the measure already performed for an unrecovered communication device is executed. And
[0016]
BEST MODE FOR CARRYING OUT THE INVENTION
Next, an embodiment of the present invention will be described with reference to the drawings. In each of the drawings referred to in the following description, parts equivalent to those in other drawings are indicated by the same reference numerals.
FIG. 1 shows a configuration of a network managed by the automatic action execution operation system 1 according to the present embodiment. The network shown in FIG. 1 includes various network elements 9 (hereinafter, referred to as “NE”) for a switching system, a transmission system, and a wireless system. The automatic action execution operation system 1 according to the present embodiment receives a failure message from the NE 9 via an NE-OPS 8 (NE Operation System) that manages various kinds of NEs 9, analyzes the failure message, and analyzes the failure message. To automatically execute the measures. The automatic measure execution operation system 1 is constituted by, for example, a general-purpose computer.
[0017]
FIG. 2 shows a configuration of the automatic action execution operation system 1 of the present embodiment, and FIG. 3 shows a flowchart for explaining an example of the operation of the automatic action execution operation system. Hereinafter, the configuration and operation of the automatic action execution operation system 1 will be described with reference to FIGS.
A failure message notified via the NE-OPS in FIG. 2 when a failure occurs in the NE is received by the alarm analysis unit 11 (S201).
[0018]
The alarm analysis unit 11 selects and stores the recovery measure scenario 12 corresponding to the received failure message from the recovery measure scenarios 12 set for each failure message. This recovery action scenario shows a recovery action execution procedure in response to a notification of a failure message, and is executed by an estimation rule section 15 for estimating a main cause and an action rule section 16 for executing recovery action. Performs recovery measures.
[0019]
The estimation rule unit 15 performs main factor estimation of the occurrence of a failure message according to the defined operation rule. Then, a measure target device and a measure content corresponding to the main cause estimated by the main cause estimation are determined (S202).
The measure rule unit 16 executes the determined measure content. At this time, in the present invention, it is determined with reference to the operation history DB 13 whether or not there is a history of the same action as the determined action content (S203), thereby determining whether or not to execute the action. I do.
[0020]
If there is a history of the measures ("history exists" in FIG. 3), it is recognized that the same measure has been executed, and the process ends without executing the decided measure. This makes it possible to avoid the execution of the duplicated measures for the target device in the recovery process by the previously executed restoration measures.
If there is no history of the measure ("no history" in FIG. 3), the status of the target device is confirmed (S204). The status confirmation is performed, for example, by inputting a command for acquiring the status information (failure, recovery, etc.) to the target device via the NE-OPS.
[0021]
As a result of the status check, if the target device is “recovered”, a process of deleting the measure history from the operation history DB is performed (S205). This makes it possible to execute measures when a new failure occurs.
As a result of the status check, if the target device is “unrecovered”, it is checked whether or not a higher-order measure exists by referring to the measure table 14 (S206).
[0022]
If there is a higher-level measure ("Yes" in FIG. 3), the higher-level measure is recorded in the operation history DB (S207), and the higher-level measure is executed (S208). This is repeated until the recovery of the device is confirmed.
FIG. 4 shows a configuration example of the operation history DB 13. In the drawing, “failure NE” for specifying the NE where the measure has been taken, “message No.” for specifying the notified failure message, “measure content” for specifying the executed measure, and “state of execution of the measure” It consists of items of "measure flag" and "measure level". This makes it possible to determine the content of the measure based on the notification of the new message with reference to the measure executed in the target device and the level of the measure.
[0023]
FIG. 5 shows a configuration example of the measure table. In the figure, a measure and a measure level are associated with the “message No.” of the failure message. In the present embodiment, the “message No.” is a number uniquely assigned to the failure message, and it is possible to specify which function of which NE has failed by this.
[0024]
FIG. 6 is a diagram for explaining a physical stage of the escalation measure, and FIG. 7 is a diagram for explaining a logical stage of the escalation. As described above, if the device remains unrecovered despite the action, a higher level action is taken. As shown in FIG. 6, in the physical escalation, at the level 1, first, the card L11 which performs a part of a function such as a T-PA (transmission power amplifier) is reset. If the function block L12 constituted by L11 is reset and still does not recover, a measure for resetting the entire communication device L13 at level 3 is executed. As shown in FIG. 7, in the logical escalation, the level of the software is higher, the level of the software is initialized L21, the level of the hardware is initialized L22, the level of the hardware is initialized, and the program L23 for loading the program from the outside is the higher level.
[0025]
8 to 12 show an example of a processing sequence in the automatic action execution operation system that performs the above-described configuration and operation.
FIG. 8 shows a sequence when the operation history DB has a measure record. After the reference result confirms that the measure history is present (S82), it is further confirmed by referring to the measure table whether a higher-order measure exists (S83). If there is no higher-level measure than the measure of the already executed level, the process is terminated without executing the measure (S85).
[0026]
In FIG. 9, there is a measure candidate higher in level than the recovery measure executed with reference to the measure table (S91). In this case, the content of the measure determined by the measure rule is updated (S92) and escalated.
FIG. 10 shows a sequence when the measure content is updated or when there is no measure history in the operation history DB (S102). The state of the measure target device is confirmed (S103). (S104).
[0027]
In the sequence of FIG. 11, if there is no action history in the operation history DB (S111), and if the device to be actioned is in an unrecovered state (S113), the action rule is to record the action to be executed in the operation history DB ( (S114), and requests the NE-OPS to execute measures for the NE (S115). If the device does not recover as a result of the measure, the status of the device is recorded in the operation record DB and the operation is terminated (S117).
[0028]
In the sequence of FIG. 12, when the NE is recovered (S122) as a result of the measure execution (S121), the record is deleted from the operation history DB upon the recovery message (S123), and the process ends.
In this way, by referring to the operation history and confirming the status of the target device, it is possible to avoid the same measure for the same device irrespective of the timing of occurrence of a failure message due to the recovery measure. That is, not only can the system load be reduced by avoiding meaningless duplication measures, but also efficient recovery measures can be executed by updating the measure contents based on reference to a measure history such as escalation.
[0029]
【The invention's effect】
As described in detail above, by referring to the record of the measures performed on the communication device and determining the measure, even if a failure occurs in the communication device in the communication network having a complicated configuration, Recovery measures can be automatically executed without reducing the processing performance of the system by avoiding the same measures for the same device, and the maintenance work can be made more efficient.
[0030]
Further, by escalating the contents of the measure from the minimum unit, it is possible to execute an appropriate measure for minimizing the influence on the service and recovering the failed device early.
[Brief description of the drawings]
FIG. 1 is a diagram showing a configuration of a network managed by an automatic action execution operation system 1 according to an embodiment.
FIG. 2 is a diagram showing a configuration of an automatic action execution operation system 1 of the present embodiment.
FIG. 3 is a flowchart illustrating an example of an operation of the automatic action execution operation system.
FIG. 4 is a diagram illustrating a configuration example of an operation history DB;
FIG. 5 is a diagram showing a configuration example of a measure table.
FIG. 6 is a diagram illustrating a physical stage of an escalation measure.
FIG. 7 is a diagram illustrating a logical stage of escalation.
FIG. 8 is a processing sequence diagram when there is a record in the operation history DB.
FIG. 9 is a processing sequence diagram when the content of the measure is changed.
FIG. 10 is a processing sequence diagram in a case where the communication device has recovered before executing the measure.
FIG. 11 is a processing sequence diagram in a case where recovery is not performed even after execution of a measure.
FIG. 12 is a processing sequence diagram in a case where recovery is performed after execution of a measure.
[Explanation of symbols]
1 Automatic action execution operation system 11 Alarm analysis unit 12 Recovery action scenario 13 Operation history DB
14 Measure table 15 Estimation rule section 16 Measure rule section 9 Network element

Claims (8)

An operation system that manages the device by executing a process on the device based on a message notified from the device connected via the communication medium,
Processing recording means for recording the executed processing;
A process determining unit that refers to a process that has already been executed for the same device based on a notification of a message, which is recorded in the process recording unit, and determines a process for the device based on a notification of a new message; An operation system comprising: The operation system according to claim 1, wherein the message is a failure message for notifying a failure in a communication device forming a communication network. The method according to claim 2, wherein the processing determination unit determines not to perform the processing again when the same processing is already executed for the same apparatus based on the notification of the message. Operation system. The apparatus further comprises an action table in which recovery actions for the failure message are defined in stages,
3. The processing determination unit according to claim 2, wherein the processing determination unit refers to the processing table to determine execution of a recovery processing of a higher-level processing content than a processing content already performed on an unrecovered communication device. 4. 3. The operation system according to 3. Based on the notification of the failure message, further includes a failure identification unit that identifies a failure that has caused the failure message,
The process determining unit refers to a process that has already been executed based on a notification of a failure message caused by the same failure identified by the failure identification unit, and determines a process based on notification of a new message. The operation system according to any one of claims 2 to 4, wherein A recovery measure method for performing a recovery measure for the communication device based on a failure message notified from the communication device,
Recovering a communication device based on a notification of a new failure message based on a record of recovery actions already performed on the same communication device; . 7. The recovery method for a communication device according to claim 6, wherein if the same process has already been performed on the same device based on the notification of the message, the process is not performed again. 8. The recovery method for a communication device according to claim 6, wherein a recovery measure of a measure content higher than the measure content already executed for the unrecovered communication device is executed.

Images