JPH0442632A - System management method - Google Patents

Abstract

PURPOSE:To manage an equipment to be managed continuously even when a fault takes place in a slave management equipment by revising dynamically a range of equipments to be managed by the slave management equipment from a master management equipment. CONSTITUTION:A master management equipment 2 sets information of managed equipment group 4 managed by a slave management equipment 3 corresponding to each of the slave management equipments 3 and control parameter information for the management to a slave management equipment information table 13 of the slave management equipment 3 through the use of a management information setting interface between the main management equipment 2 and the slave management equipment 3. The slave management equipment 3 monitors the operating state of the managed equipment 4 based on the managed equipment group information and the control parameter information. Thus, even when a slave management equipment 3 is faulty and the management of the managed equipment 4 managed by the slave management equipment 3 is disabled, the managed equipment 4 is managed.

Description

Detailed Description of the Invention [Field of Industrial Application] The present invention relates to a system management method, and in particular, the operational status (normal, normal, The present invention relates to a system management method that can monitor abnormalities.

[Conventional technology] As a conventional technology related to system management methods, for example, Hitachi Hyoron Vol. 69, No. 9 (Tomaki No. 788), special feature on network system technology, page 23 "Development of packet switching system "PS400"" and page 61 Technologies described in "network management systems" and the like are known.

In this prior art, a group of managed devices to be managed by a slave management device is set and determined in advance, and a main management device manages the managed devices via the slave management device.

[Problems to be Solved by the Invention] According to the above-mentioned conventional technology, when a slave management device becomes a failure, it becomes impossible to manage the operating state of the managed device managed by the slave management device that has become the failure. There is a problem with this.

An object of the present invention is to solve the problems of the prior art described above, and even when a slave management device becomes a failure and the managed devices managed by the slave management device cannot be managed, these devices can be managed. An object of the present invention is to provide a system management method that enables management of managed devices.

[Means for Solving the Problems] According to the present invention, the above object is achieved when the slave management device becomes an obstacle;
If it becomes impossible to manage the managed device managed by that slave management device, the scope of management of another slave management device is expanded, and the managed device managed by the failed slave management device is expanded. This is achieved by having the device managed by another slave management device.

Therefore, in the present invention, between the main management device and the slave management device,
Equipped with a management information setting interface that can dynamically change the range information of the managed device group that the slave management device manages, and the control parameter information for management that changes as the scope of management increases or decreases, the main management device A master management information table is provided in the device that indicates range information of a group of managed devices managed by the slave management device for each slave management device. It is configured by providing a slave management information table for holding the passed information on the group of managed devices to be managed and the control parameters for management.

[Function] The main management device transfers information on the group of managed devices to be managed by the slave management device and control parameter information for management to the management information settings between the main management device and the slave management device. The information is set in the slave management device information table of the slave management device using the interface, and the slave management device monitors the operating state of the managed device based on the managed device group information and control parameter information.

In addition, the master management device monitors the operating status of the slave management device, and when it detects a failure in the slave management device, the master management device also checks the information in the master management information table for the managed devices managed by the slave management device that detected the failure. Extract the device group information and send it to another slave management device 7.
Using the management information setting interface for another slave management device, in addition to the managed device group information managed by
The information in the slave management information table of another slave management device is updated, and the managed device group that was being managed by the failed slave management device is managed by another slave management device.

In this case, the main management device also updates control parameter information for various types of management as the number of managed devices managed by another slave management device increases, as necessary, via the management information setting interface. can do.

[Example 1] Hereinafter, an example of the system management method according to the present invention will be explained in detail with reference to the drawings.

FIG. 1 is a block diagram showing the system configuration of an embodiment of the present invention, FIGS. 2(a) to (h) are diagrams explaining control information for system management exchanged between devices, and FIG. 3 (a)
- (d) are diagrams explaining the main management information table, slave management information table, and information setting examples of each table in the main management device and the slave management device, and Fig. 4 (a) to (f) are the main management device,
FIG. 5 is a processing flowchart explaining the operations of the slave management device and the managed device. FIG. 5 is a diagram explaining an example of a system management sequence among the main management device, the slave management device, and the managed device.

In FIG. 1, 1 is a network, 2 is a main management device,
3 is a slave management device, 4 is a managed device, 5.6 is a management line, 10 is a main management information table, 13 is a slave management information table, and 14 is a management group.

As shown in FIG. 1, a system management system according to an embodiment of the present invention includes a main management device 2, a slave management device 3 that is directly managed by the main management device 2, and a system management device 3 that is directly managed by the main management device 2. The managed device 4 to be directly managed is connected via the network 1 with management lines 5 and 6, and the main management is performed by sending and receiving the control information frame shown in FIG. 2 using the lines. The device 2 is configured to manage a slave management device 3 and a managed device 4.

In FIG. 1, the main management device 2 performs a health check 8 on the slave management device 3 based on the slave management device address registered in the main management information table 10 shown in FIG. The management device 4 has the slave management information table 1
A health check is performed on the group of managed devices 4 obtained from 3 using the patrol frame 9.

As a result, the embodiment of the present invention shown in FIG. 1 can manage the slave management device 3 and the managed device 4 as a whole.

When the main management device 2 detects a failure in the slave management device 3 as a result of a health check on the slave management device 3, the main management device 2 checks the group of managed devices 4 managed by the failed slave management device 3 from the main management information table 10. Find another slave management device 3 that can perform the management on behalf of the machine management device 3, and add the group of managed devices 4 managed by the failed slave management device 3 to the group of managed devices 4 managed by the machine management device 3. In addition, this new group of managed devices 4 is
Patrol control information 7 for instructing the slave management device 3 that can perform proxy management as a new management range is transmitted to the slave management device 3 that can perform proxy management.

The main management device 2 continues to perform a health check 8 on the failed managed device 3 even after the failure is detected, and when it detects that the failure has been recovered, the main management device 2 performs a health check 8 on the failed managed device 3. The slave management device 3 that was managing the group of managed devices 4 on behalf of the group is found from the main management information table 10 (the details of which are shown in FIG. 3), and the agent management device management device 3 Patrol control information 7 returned to the control range of group 4
By sending , the original management state can be restored.

Furthermore, as a result of transmitting the patrol frame 9 and performing a health check on the group of managed devices 4, the slave management device 3 does not receive a patrol frame and the managed devices 4
When an abnormality is detected, the main management device 2 is notified of the abnormality using the patrol abnormality notification 15.The main management device 2 performs a health check on the group of managed devices 4 managed by the slave management device 3 that has notified the abnormality. 8 to search for the failed managed device 4.

When the main management device 2 detects the failed managed device 4 through the above-described process, the main management device 2 selects the failed managed device 4 from the group of managed devices 4 of the slave management device 3 that is managing the managed device 4. Create patrol control information 7 with the excluded range as the management range, send this control information 7 to the slave management device 3 that notified the failure, and cause the device management device 3 to perform patrol processing for the group of managed devices 4. continue.

The main management device 2 records the address of the faulty managed device 4 in the faulty device information column of the main management information table 10, and similarly to the slave management device 3, the main management device 2 directly records the address of the faulty managed device 4. When the check is performed and recovery is detected, the original management state is restored by transmitting the patrol control information 7 to have the optical slave management device 3 perform the management again to the slave management device 3 that notified the failure. be able to.

The outline of one embodiment of the present invention has been explained above with reference to FIG. 1. Further, the details of one embodiment of the present invention will be explained with reference to FIGS. An example of a management sequence among a management device, a slave management device, and a managed device will be explained.

FIG. 2 explains control frames exchanged for system management between the main management device 2, slave management device 3, and managed device 4 of FIG. 1.

The health check frame 21 is a frame sent from the main management device 2 to the slave management device 3 or managed device 4 for failure and failure recovery detection. The addresses of the management device 3 and managed device 4 and information indicating that the frame is a health check frame are set.

The health check response frame 22 is a response frame indicating normality to the health check frame 21, and is transmitted from the slave management device 3 or managed device 4 that received the health check frame 21 to the main management device 2.

The information in this frame includes the address of the main management device 2 as the destination of the frame, the address of the slave management device 3 or managed device 4 as the source, and information indicating that it is a health check response frame. Ru.

The patrol control information frame 23 is transmitted by the slave management device 3.
This is a frame for transmitting information necessary for health checking a group of managed devices from the main management device 2 to the managed devices 3. The information set in this frame includes the address indicating the destination of the frame, the address group of the managed device 4 to be managed by the slave management device 3, and the device management device 3.
These are patrol order information with the last address given, and time monitoring information from when the slave management device 3 sends a patrol frame to the managed device 4 for a health check until the patrol frame returns.

Note that when the slave management device 3 receives this frame, it stores the information in the received frame in the slave management information table 13 shown in FIG. 3(d), and performs subsequent patrol processing based on this information. conduct.

The patrol frame 24 is a frame that is transmitted from the slave management device 3, relayed through the managed device 4 to be managed, returned to the slave management device 3 as the issuer, and used to perform a health check on the managed device 4.

The information set in this frame is the address of the destination managed device 4 of the frame, and this information is changed to the address of the next relay destination managed device 4 for each managed device 4. is a managed device, and is set to the address of the issuing slave management device 4.

Further, within this frame, address information of the slave management device 3 indicating the final page destination of this frame is set in address group information of the managed device 4 indicating the patrol order.

The patrol abnormality notification frame 25 is used to notify the main management device 2 of an abnormality when the slave management device 3 detects an abnormality as a result of a health check of the managed device 4 using the patrol frame 24. The address of the main management device 2 indicating the destination of the frame and the slave management device address 3 indicating the source of the abnormality notification are set in the frame for notification.

The initialization instruction frame 26 is an initialization instruction frame that the main management device issues to the device management device after the slave management device 3 recovers from a failure. The instructed and held patrol control information is set in the rear-guard subordinate management information table shown in FIG. 3, and patrol processing is performed.

Note that the correspondence between the control information shown in FIG. 1 and the control frame shown in FIG. 2 is based on the patrol control information 7 in FIG.
corresponds to the patrol control information frame 23 in FIG.
Health check 8 in FIG. 1 corresponds to health check frame 21 and health check response frame 22 in FIG. 2, patrol frame 9 in FIG. 1 corresponds to patrol frame 24 in FIG. The abnormality notification 15 corresponds to the patrol abnormality notification frame 25 in FIG. Note that the initialization instruction frame 26 in FIG.
Omitted from the figure.

FIG. 3 shows details of the main management information table 10 and the slave management information table 13 for storing information necessary for managing the main management device and the slave management device 3 shown in FIG. 1. .

In FIG. 3, the main management device table 10 includes a management table i (i=1 to m) corresponding to the slave management device, and the management table i includes device address information of the corresponding slave management device, Information on the number of managed devices managed by the machine management device, and an alternative slave management device table number indicating the management table number of the slave management device that manages the managed devices managed by the machine management device on behalf of the machine management device when the machine management device fails. information,
When another slave management device performs proxy management of a managed device to be managed by the machine management device, the proxy slave management device management table number information indicating the management table number of the delegated slave management device and the managed device A group of address information for managed devices that should be managed by the device itself, as well as records for managing managed devices that should be managed by the machine management device so that they can be directly managed by the main management device in the event of a failure of the device. A group of failed device address information for information storage is stored. This information is
Set as necessary.

Note that FIG. 3(b) shows an example of information settings in the main management information table 1.

In addition, the slave management information table 13 shows whether the slave management device is
This table stores information necessary for performing roll processing, and as shown in FIG. 3(C), the patrol time monitoring value information and patrol order information described in FIG. 2(c) are set.

Note that (d) in FIG. 3 shows an example of information settings in the slave management information table 2.

FIG. 4 shows a specific processing flowchart for each of the main management device, slave management device, and managed device.

The main management device processing flowchart shown in FIG. 4(a) is as follows:
The process in which the main management device performs a health check on the slave ring device is shown as follows: Process 101 to Process 104 → Process 105 → Process 111 → Process 112, and Process 113 → Process 111.
→ In the processing flow of process 112, failure detection and failure recovery detection of the slave ring device are performed, and process 105 → process 106
The processing flow from 110 to 110 shows that the management configuration change process for the managed device of the slave ring device and the process of the slave ring are performed after the failure of the slave management device is detected.

The slave pipe ring device processing flowchart shown in FIG. 4(d) is as follows:
Processes 401 to 403 are processes for detecting failures, and processes 404 to 407 are processes for notifying the main management device after a failure is detected when a failure is detected. This shows the processing of

The slave pipe ring device processing flowchart shown in FIG. 4(e) is as follows:
A patrol control information frame when a failure occurs in another slave ring device and the managed device of the failed slave management device is managed on behalf of the slave ring device, or a slave ring information table from the master management device for the slave management device in question. It shows the processing when an initialization instruction frame is received.

The managed device processing flowchart shown in FIG. 4(f) is as follows:
It shows the relay processing in the managed device of the patrol frame transmitted by the subordinate link device.

FIG. 5 shows the management method shown in FIGS. 1 to 4, tables necessary for management, and management for managing the main management device, slave ring devices, and managed devices using the control information frame. An example sequence is shown.

This shows that instructions are given to the device, and in steps 114 to 119, processing for restoring the management configuration after recovery of the slave ring device and return instructions to the slave ring device are performed.

The main management device processing flowchart shown in FIG. 4(b) is a processing flowchart for the main management device to detect the recovery of a slave link device whose failure state has been detected as a result of the health check of the slave link device. , and processes 201 to 2
05 and processes 205 and 2o6, recovery of the managed device is detected in processes 207 and 208, and processes 209 to 2o6 are performed.
211 and processes 209 to 214 indicate that processing is being performed to make the recovery managed device a management target of the slave ring device.

The main management device processing flowchart shown in FIG. 4(c) is as follows:
When the main management processing unit receives a patrol abnormality notification frame from a slave link device, the main management processing unit performs the process of detecting a faulty managed device, and the main processing to make the managed device where the fault has been detected become a device directly managed by the main management device. It shows management information table update processing.

Processes 301 to 314 indicate processes for detecting a failed managed device, and processes 315 to 318 and processes 319 to 320
teeth. This figure shows a process for making a failed managed device a management target of the main management device.

According to the embodiment of the present invention described above, as a result of the health check of the slave ring device by the main management device, the managed device managed by the slave ring device that has an abnormality is transferred to the managed device managed by another slave ring device. By dynamically changing the management range of the management device, it is possible to have this other slave ring device manage it.

[Effects of the Invention] As explained above, according to the present invention, the range of managed devices managed by the slave ring device can be dynamically changed from the main management device, so that the slave ring device is prevented from failing. Even if this occurs, the managed device can be continuously managed.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing the system configuration of an embodiment of the present invention, FIGS. 2(a) to (h) are diagrams explaining control information for system management exchanged between devices, and FIG. 3 (a)
- (d) are diagrams explaining the main management information table, slave ring information table, and information setting examples of each table in the main management device and the slave ring device, and Figures 4 (a) to (f) are the main management Device,
FIG. 5 is a processing flowchart explaining the operations of the slave ring device and the managed device. FIG. 5 is a diagram explaining an example of a system management sequence among the main management device, the slave ring device, and the managed device. 1...Network, 2...Main management device, 3...00. Slave management device, 4... Managed device, 5.6... Management line, 10...
-Main management information table, 13...Slave management information table, 14...Management group. (f) Patrol frame example (C) Labor management information table 16 (d) Slave management information table example Figure (a) Main management information table 10 Figure (b) Part 2 1!1 (e) Slave management device processing Flowchart 2 Figure (f) Managed device processing flowchart 1 Patrol frame relay processing

Claims (1)

[Claims] 1. A system management method comprising a main management device, a slave management device and a managed device managed by the main management device, and in which the slave management device patrols the managed devices for health checks. A system management method characterized in that the management device includes means for dynamically changing configuration information and patrol monitoring information of a managed device that is a target of patrol by the slave management device.