JPH06222937A - Automatic fault recovering system in network managing system - Google Patents

Abstract

PURPOSE:To save labor for fault recovery and to perform speedy fault recovery in a network managing system. CONSTITUTION:When any fault is generated at a managing object 4 in a network managing system 1, an agent 3 receives managing object information corresponding to that managing object 4 and the kind of error corresponding to the kind of the fault from the managing object 4 and retrieves a data base 5 with those data as keys. First of all, a recoverying method provided with the highest priority and a limitation for the number of times of retry are provided and by that recoverying method, the recoverying method is repeatedly tried until the fault recovery is made successful or the limitation for the number of times of retry is exceeded. When the number of times of retry for fault recovery exceeds the limitation for the number of times of retry, the retrieval of the data base 5 and the try of fault recovery based on the result are performed until the recoverying method of non-retrieval concerning the same managing object information and the error kind is eliminated.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a failure automatic recovery method in a network management system, and more particularly to a failure automatic recovery method using a database.

[0002]

Modeled by a manager and an agent, the manager issues management operations to multiple agents and receives notifications, and the agent issues management operations to multiple management targets and receives notifications. In the network management system to perform, when the management target notifies the agent of failure occurrence, and when performing failure recovery for the management target, conventionally, a person directly performs failure recovery for the management target or Failure recovery is automatically performed by a single predetermined method.

[0003]

SUMMARY OF THE INVENTION In this conventional technique,
It is premised that the failure is reliably recovered by one kind of failure recovery method. That is, it is impossible to automatically try another failure recovery method when a failure recovery method fails despite the attempt. Therefore, there is a problem that a large amount of manual intervention is required for disaster recovery, which hinders quick disaster recovery.

[0004]

SUMMARY OF THE INVENTION The present invention provides a plurality of failure recovery methods in a database for labor saving and quick failure recovery until failure is actually recovered.
Automatically repeats.

The automatic failure recovery system in network management according to the present invention uses a database according to a certain algorithm and leaves the recovery when an error occurs to an agent, thereby saving labor in failure recovery and speedy recovery. .

[0006]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be described with reference to the drawings.

FIG. 1A is an explanatory diagram showing the configuration of the network management system 1. The network management system 1 is composed of one manager 2, a plurality of agents 3, a management target 4 and a database 5.

The manager 2 issues a management operation to the subordinate agent 3 and receives the notification, and the agent 3 issues a management operation to the subordinate management target 4 and receives the notification. Also, each agent 3 can search the database 5 under it.

FIG. 1B is a diagram for explaining the means of only the main part of the present invention.

FIG. 2 is an explanatory diagram showing information held by the database 5. The database 5 stores the following information regarding failure recovery.

(1) Management target information 11 (2) Error type 12 (3) Recovery method 13 (4) Priority of the recovery method 14 (5) Retry limit of the recovery method 15 Each management target information 11 On the other hand, a plurality of error types 12 correspond, and a plurality of recovery methods 13 correspond to each error type 12, but the recovery method 13, its priority 14 and retry count limit 15 correspond to 1: 1 respectively. .

An example of the restoration algorithm is shown in FIG. The example shows a case where the agent 3 attempts recovery according to the recovery algorithm.

FIG. 4 is an explanatory diagram showing a sequence of a fault notification from the management target 4 to the agent 3 and a database search.

The operation of each means of the present invention shown in FIG. 1B will be described below with reference to the drawings.

First, when a failure occurs in the managed object 4,
The management target 4 notifies the agent 3 of failure notification means 10
1, the failure occurrence notification is performed. The failure occurrence notification includes the management target information 11 corresponding to the management target 4 and 1: 1,
The error type 12 corresponding to the type of failure is included.

The agent 3 searches the database 5 by the database searching means 102 using the management target information 11 and the error type 12 as a key (database searching operation). The agent 3 obtains the recovery method 13 having the highest priority 14 and the retry count limit 15 from the database 5 (database search result notification).

The agent 3 tries the failure recovery by the recovery method 13 to the managed object 4 by the recovery trial means 103 (failure recovery operation).

FIG. 5 is an explanatory diagram showing a sequence of trial and success of failure recovery. When the agent 3 succeeds in the failure recovery attempt on the management target 4, the management target 4 notifies the agent 3 of the success of the failure recovery result, and the failure recovery algorithm ends.

FIG. 6 is an explanatory diagram showing a sequence of trial and failure of failure recovery. If disaster recovery fails,
The management target 4 notifies the agent 3 of the failure recovery result failure. The agent 3 receiving the failure notification repeatedly attempts the same recovery method 13 on the same management target 4 until failure recovery is successful or the retry count limit 15 is exceeded.

The number of retries for failure recovery is the retry count limit 1
When the number exceeds 5, the agent 3 searches the subordinate database 5 again, and if the next highest priority 14 of the same management target information 11 and the error type 12 that has already been searched exists, the priority 14 thereof is exceeded. The recovery method 13 and the retry count limit 15 corresponding to are obtained. In that case,
The disaster recovery attempts are repeated in the same manner as above.

The search of the database 5 and the trial of the failure recovery based on the result thereof are carried out until there is no unsearched recovery method 13 for the same management target information 11 and error type 12.

If all failure recovery attempts fail,
The agent 3 notifies the manager 2 that a failure has occurred, and the failure recovery algorithm ends.

That is, when the notification of failure recovery failure is received from the managed object 4, the agent 3 follows the algorithm shown in FIG. 3 to (1) try again the failure recovery for the managed object 4, and (2) again. Search the database 5, (3) notify the manager 2 of the failure occurrence,
Either end the disaster recovery.

[0024]

As described above, the automatic failure recovery method in the network management system according to the present invention uses a plurality of failure recovery methods by utilizing a database according to a certain algorithm until the failure is actually recovered. It is possible to automatically and repeatedly perform trials, which leads to labor saving in disaster recovery and quick disaster recovery.

[Brief description of drawings]

FIG. 1 is an explanatory diagram for explaining a configuration of a network management system and a failure automatic restoration method of the present invention.

FIG. 2 is an explanatory diagram showing information possessed by a database storing failure recovery information.

FIG. 3 is a flowchart showing an example of a fault recovery algorithm.

FIG. 4 is an explanatory diagram showing a database search operation and a search result notification sequence.

FIG. 5 is an explanatory diagram showing a sequence of trial and success of failure recovery.

FIG. 6 is an explanatory diagram showing a sequence of trial and failure of failure recovery.

[Explanation of symbols]

 1 Network Management System 2 Manager 3 Agent 4 Management Target 5 Database 11 Management Target Information 12 Error Type 13 Recovery Method 14 Priority 15 Retry Count Limit 101 Fault Notification Means 102 Database Search Means 103 Recovery Trial Means

Claims (2)

[Claims] 1. A network management system having a plurality of agents, a manager for managing the agents, a plurality of management targets managed by the agents, and a database, wherein the management targets notify the agent of occurrence of a failure. Failure notifying means for performing, and a plurality of recovery methods according to the management target in the database based on the notification information by the failure notifying means,
And its priority, and a database search means for searching the data of the number of retries limit, and from the restoration method of the high priority to the restoration method of the low priority, within the limit of the number of trials, the failure An automatic failure recovery method in a network management system, which comprises: 2. The automatic failure recovery system in a network management system according to claim 1, wherein the notification information by the failure notification means includes management target information and error type data corresponding to the type of failure.