JPH09146885A - Management system for slave device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To alter the management contents of the slave device without any hindrance to system operation. SOLUTION: A host device 20 is equipped with execution processing subprograms 1-1...1-n which are constituted in process units for events generated on the slave device 100. A sequence data table 2 is a table showing the correspondence relation between the events and execution processing subprograms 1-1...1-n. When processes corresponding to the events generated on the slave device 100 are changed or added, sequence change data are sent out of a terminal device 300 to the host device 200. A table data setting part 3 of the host device 200 changes or adds the contents of the sequence table 2 according to the sequence change data. Consequently, the management contents of the slave device 100 can be changed without stopping the host device 200.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a slave device management system in which a host device manages processing executed by a plurality of slave devices.

[0002]

2. Description of the Related Art A transmission system is known which comprises a plurality of slave devices and a host device which manages these slave devices. In such a transmission system, the slave device actually controls the transmission, and the host device manages the transmission control. Then, the higher-level device manages, for example, recovery processing when a failure occurs in the slave device. In such a case, the restoration process to the slave device performed by the host device needs to be performed according to the condition based on the failure information from the slave device and the device configuration. Specifically, the recovery processing application program of the upper-level device is configured to execute one recovery process fixedly based on the combination of the failure information from the slave device and the device type.

Therefore, when the failure information or the device configuration is changed due to the addition of a function of the subordinate device or the like, it is necessary to change the restoration processing application program of the upper device.

[0004]

As described above, in the conventional system, when the function of the subordinate device is added or the restoration process is changed due to the request of the maintenance person, the function of the host device is stopped and the restoration is performed. It was necessary to replace the processing application program. Therefore, while the program for such a recovery process is replaced, the higher-level device is stopped, so that it is not possible to manage another slave device that continues to operate.

However, in transmission systems it is generally not desirable to stop its transmission control, and
In the system (upper device-slave device) that has once started to operate, it is difficult to change the restoration process due to the request of the maintenance person who operates the upper device.

From this point of view, it has been desired to realize a slave device management system capable of changing the management contents of the slave device without any hindrance to the operation of the system.

[0007]

The present invention employs the following structure to solve the above-mentioned problems. <Structure of Claim 1> In a management system for a slave device, wherein a process executed by a slave device is managed by a host device, the host device stores an execution processing subprogram configured in a processing unit for an event that occurs in the slave device. The sub-program storage unit, the sequence data table showing the correspondence between the events that occur in the subordinate device and the execution processing subprograms, and when the execution processing instruction to the subordinate device is received, the sequence data table is referred to and the corresponding When a change instruction to the sequence data table is received from the management process execution unit that executes the process to the subordinate device using the execution process subprogram and the terminal device connected to the host device, based on the change instruction, A table data setting unit for changing table data is provided.

<Explanation of Claim 1> The slave device is a device having a function such as transmission control. In addition, the host device is
It has the function of managing and maintaining each slave device. The terminal device is a device that gives an instruction to a host device. When performing management / maintenance of a subordinate device, in the host device, the management processing execution unit first refers to the sequence data table based on the information of the event received from the subordinate device, and executes the execution processing subprogram corresponding to the event. Extract. And
The extracted execution processing subprogram is used to execute processing corresponding to the occurrence event of the slave device.

On the other hand, the management contents of the slave device can be changed,
When processing corresponding to a new event is performed, the sequence change data is created from the terminal device and transmitted to the host device. The host device changes the contents of the sequence data table based on the received sequence change data. Therefore, even if a new event occurs in the slave device or the processing for a specific event is changed, the contents of the sequence data table can be added without stopping the operation.
It can be dealt with only by changing it.

[0010]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described in detail below with reference to the drawings. FIG. 1 is a configuration diagram showing a specific example of a management system for a slave device according to the present invention. The device shown is
The slave device 100, the host device 200, and the terminal device 300. The slave device 100 includes a plurality of slave devices 100-1,
100-2, 100-3, ..., Here, an example of three slave devices 100-1, 100-2, 100-3 is shown. Each of these slave devices 100 is an information processing device that performs transmission processing such as communication control in a digital leased line. Subordinate device 100 and host device 200
Are connected via a communication path such as a LAN (local area network), and the communication path is configured to report failure information of the slave device 100 to the higher-level device 200.

The host device 200 is a device for monitoring / maintaining the slave device 100, and includes a subprogram storage unit 1, a sequence data table 2, a table data setting unit 3, and a management processing execution unit 4. In the subprogram storage unit 1, execution processing subprograms 1-1, ..., 1-n configured in units of execution processing for the slave device 100.
Is stored. These execution processing subprograms 1
-1, ..., 1-n are constituted by, for example, a minimum unit of recovery processing when a failure occurs in the slave device 100, and this is a processing unit such as device initialization, device switching, and data recovery. ing. Here, for example, the initial setting of the device is an initial setting at the time of restart of the slave device 100, and the switching of the device is a redundant system in which each slave device 100 is an active system and a standby system. It refers to the process of switching from the active system to the standby system when it is present.

The sequence data table 2 is a table showing the relationship between the execution processing in the subordinate device 100 and the execution processing subprograms 1-1, ..., 1-n in the subprogram storage unit 1.

FIG. 2 is an explanatory diagram of the sequence data table. Here, the relationship between the failure information 21 indicating the operating state of the slave device 100 and the recovery processing subprogram number 22 (number of execution processing subprograms 1-1, ..., 1-n) when performing the recovery processing is shown. Shows. For example, when the failure information A (operation system software failure) occurs, the recovery processing 1-1 (device switching) is executed. In this way, the failure information and the recovery processing subprogram number are different information depending on the system.

The table data setting unit 3 includes a terminal device 30.
When the instruction to change the table data in the sequence data table 2 is received from 0, it has a function of changing the contents of the sequence data table 2 based on the instruction to change.

The management process execution unit 4 includes an execution process main program 4a and has a function of executing the management process of the slave device 100. That is, when a process execution request is received, the execution process main program is activated to execute the corresponding execution process subprograms 1-1, ..., 1-n based on the table data of the sequence data table 2. It is what

The terminal device 300 is provided with a display, a keyboard and the like, and is for operating the host device 200. The terminal device 300 has a function of creating information (sequence change data) for changing the sequence data table 2.

Next, the operation of the slave device management system having the above configuration will be described. Normally, the higher-level device 200 monitors the operation of the slave device 100, and, for example, the slave device 100-
When the fault information A is transmitted from No. 1, the management process executing unit 4 of the higher-level device 200 executes the execution process main program 4a, and first, referring to the sequence data table 2, the fault information A is dealt with. The recovery processing subprogram number 22 is obtained. If this number is 1-1, the execution processing subprogram 1-1 stored in the subprogram storage unit 1 is executed.

When the sequence data table 2 is changed, it is performed as follows. Here, as an example of the operation, when the fault information of the slave device 100-1 is newly added (this fault information is [E: active transmission line fault]
Will be described). Further, when failure information [E] is generated by the judgment of the maintenance person who operates the terminal device 300, the execution processing subprogram 1-3 (transmission path switching & cell processing unit switching) is executed in the host device 200. Assume that they are related as they are done.

FIG. 3 is an operation flowchart of the terminal device 300. As described above, when newly adding failure information, first, a maintenance person who operates the terminal device 300
The following two pieces of information are command-input to the terminal device 300 (step S1). One is the slave device 100-
It is new fault information (fault information E) sent from 1.
The other is the recovery processing subprogram number (execution processing subprogram 1-1, ..., 1-n corresponding to the failure information E.
Identification number). Thereby, the terminal device 300
Creates sequence change data based on the input information (step S2).

FIG. 4 is a structural diagram of sequence change data. As illustrated, the sequence change data includes a command identifier 31, failure information 32, and a recovery processing number 33. Here, the command identifier 31 is an identifier indicating that the data is sequence change data, and the failure information 3
2 and the recovery processing number 33 are data corresponding to the failure information and the recovery processing subprogram number in the sequence data table 2.

When the terminal device 300 creates the sequence change data in step S2, the terminal device 300 transmits the sequence change data to the upper device 200 (step S3), and then waits for a response from the upper device 200 (step S3). Step S4). When the response is received from the host device 200 (step S5), the response result is output on the display (step S6), and the process ends.

Next, the operation of the higher-level device 200 when changing the sequence data will be described. FIG. 5 is an operation flowchart of the higher-level device 200. When the host device 200 receives data from the terminal device 300 (step S11),
The command identifier 31 is analyzed (step S12),
When the sequence change request is recognized, the information of the sequence change data (fault information 32, recovery processing number 3
3) is extracted (step S13). Next, the slave device 1
It is determined whether the recovery process of 00 is in progress (step S14), and if it is being executed, the sequence change request from the terminal device 300 is rejected (step S15). On the other hand, step S14
In the case where the recovery process is not being executed, the table data setting unit 3 sets the sequence change data in the sequence data table 2 (step S16). If the data is not the sequence change data in step S12, another process is performed.

FIG. 6 is an explanatory diagram of the sequence data table 2 after setting. As shown in the figure, the information of the failure information [E] is added as new failure information.

FIG. 7 is a flowchart showing a data setting procedure for the sequence data table 2. The table data setting unit 3 first performs a matching process between the failure information 32 indicated in the sequence change data and the failure information 21 set in the sequence data table 2 (steps S21 and S22). Here, if the matching results match,
Recovery processing subprogram number 2 corresponding to the failure information
2, the recovery process number 3 shown in the sequence change data
3 is written (step S23). On the other hand, if no matching failure information is found, failure information 32 and recovery processing number 33 are added to the end of the sequence data table 2 (step S24). In this case, since new information is added, writing to the sequence data table 2 is a route for performing step S24.

Returning to FIG. 5, the sequence data table 2
When the setting to (1) is completed, the terminal device 300 is notified that the sequence change is completed (step S1).
7). This is the end of the process of changing the sequence data table 2.

After that, in the host device 200, the slave device 1
When the failure information E is received from 00, the execution processing subprogram 1-3 is executed by referring to the sequence data table 2. As described above, in the above-described specific example, the restoration process can be changed / added without stopping the function of the higher-level device 200.

As described above, according to the above-described specific example, even if the restoration process in the sequence data table 2 is changed, the table data setting unit 3 instructs the sequence data table 3 by instructing this from the terminal device 300. Since the contents of 2 are changed, the optimum subprogram selection can be executed without stopping the system.

In the above specific example, the case where the content of the sequence data table 2 is the restoration process for the failure information has been described, but the present invention is not limited to this, and the slave device 1 is not limited thereto.
If a subprogram corresponding to the event that occurs at 00 is prepared in advance and can be processed by it, it is possible to handle any event.

[0029]

As described above, according to the slave device management system of the present invention, the system is not stopped even when the occurrence event of the slave device is added or the execution process for the occurrence event is changed. The sequence data table can be easily maintained.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a management system for a slave device according to the present invention.

FIG. 2 is an explanatory diagram of a sequence data table in the slave device management system of the present invention.

FIG. 3 is an operation flowchart of the terminal device in the slave device management system of the present invention.

FIG. 4 is a configuration diagram of sequence change data in the management system of the slave according to the present invention.

FIG. 5 is an operation flowchart of a host device in the slave device management system of the present invention.

FIG. 6 is an explanatory diagram of a sequence data table after data setting in the slave device management system of the present invention.

FIG. 7 is a flow chart of a sequence data table setting procedure in the slave device management system of the present invention.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Subprogram storage unit 1-1 to 1-n Execution processing subprogram 2 Sequence data table 3 Table data setting unit 4 Management processing execution unit 4a Execution processing main program 100 Slave device 200 Upper device 300 Terminal device

Front page continued (72) Inventor Noboru Yamamichi 1-7-12 Toranomon, Minato-ku, Tokyo Oki Electric Industry Co., Ltd.

Claims (1)

[Claims] 1. A management system for a slave device, wherein a higher-level device manages processing executed by the slave device, wherein the higher-level device stores an execution processing subprogram configured in processing units for events that occur in the slave device. A sub-program storage unit, a sequence data table indicating a correspondence relationship between an event that occurs in the slave and the execution processing sub-program, and when the execution processing instruction to the slave is received, refer to the sequence data table. If a change instruction to the sequence data table is received from the management process execution unit that executes the process to the slave device using the corresponding execution process subprogram and the terminal device connected to the host device, A subordinate characterized by having a table data setting unit for changing table data based on the change instruction. Location management system of.