JP2003092602A - Network apparatus - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a network apparatus that can match programs and automatically down load the programs or the like. SOLUTION: The network apparatus is provided with a data storage section for storing data, a version management section for managing version information of the data, a version transmission request section for requesting an adjacent network apparatus to transmit the version information of the data of the adjacent network apparatus when the own network apparatus is boosted, a version comparison section for comparing the version information of the data managed by the version management section with the version information of the data of the adjacent network apparatus sent from the adjacent network apparatus on the basis of the transmission request, a data transmission request section for requesting the adjacent network apparatus to transmit the data on the basis of the comparison result of comparison by the version comparison section, and a data reception section for receiving the data sent from the adjacent network apparatus on the basis of the request of the data transmission request section and storing the data to the data storage section.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network device, and more particularly to control of downloading and restarting an installation, a switchboard, a program in operation, and operating data, which is necessary when operating the network device.

[0002]

2. Description of the Related Art Networks such as corporate networks are composed of a plurality of network devices (nodes). A node is a router function that supports multiple low-speed LAN interfaces or a high-speed interface that forms a backbone network between nodes, such as SDH and SONE.
It has the functions of an SDH device that supports a T interface and the like. The network is operated by newly introducing a plurality of nodes and connecting the nodes. Also,
In the case of a node failure or the like, it is replaced with a new network device. Furthermore, during operation, version upgrades of programs and setting information are performed simultaneously on all nodes.

(1) At the time of introduction It is necessary to set network setting information (NW setting information) and individual setting information for the router introduction node. NW
The setting information is information that nodes must have in common, and is, for example, IP address information, node number information, VLAN setting information, or the like. The individual setting information is individual information of each node, and is, for example, LAN interface information accommodated in each port. Conventionally, this is done by an operator, setting data is stored in the apparatus, and a backup of the setting data is sucked up and stored in a medium.

It is necessary to install an SDH device monitoring program and set individual setting information. The monitoring program is a program for monitoring whether the SDH device is operating normally. Individual setting information is information that is unique to each node, for example,
The information includes time slot allocation information, QoS setting information, and the like. In the past, this was done by an operator downloading from a management terminal on the center side, and individual setting information was collected at the management terminal and backed up on a medium.

(2) When replacing a device It is necessary to do the same as when introducing a router. This was done by resetting the setting data backed up in the medium at the time of introduction by the operator.

When the version number of the program installed in the SDH device exchange node is different from the version number of the exchange device, the program operated by the operator is downloaded from the management terminal. Also, the setting data backed up at the time of installation is reset by the operator from the management terminal.

(3) Batch change At the time of collectively changing the versions of programs and setting data (versions of IP addresses) during operation, download the programs and setting data from the management terminal to all the devices, and download the data at once. After the replacement, the operator confirms from the management terminal whether or not the versions of all the devices have been replaced.

[0008]

However, in the prior art,
There were the following problems.

(1) At the time of introduction Generally, the network setting of the router is complicated, and an operator at the system engineer level is required in addition to the equipment / worker. Therefore, as the number of installed units increases, the work cost of the operator increases proportionally. It is necessary to confirm that the version numbers of the programs and NW setting information that are operated in the already installed network are the same as the version numbers of the programs and the like installed in the expansion device. The reason is that if the version numbers of the monitoring programs are different, a failure occurs that monitoring cannot be performed. Also, IP
If the version number of the address is different for each node like IPv4 and IPv6, routing becomes impossible. Therefore, if it is mistakenly incompatible or is started up with a different version number, the network may be cut off.

(2) At the time of device replacement, it is essential to confirm that the version numbers of the programs and setting data that are being operated are the same as those at the time of node addition at the time of initial introduction, or that they are compatible. Requires installation work, which complicates the work. Further, it is necessary for the operator to reset the backup data for operation. However, in the case of the router, there is a problem that knowledge on the network is required, work is usually performed by a system engineer level person, and a worker different from the apparatus installation worker is required, resulting in cost increase.

(3) At the time of exchanging the batch exchanging program during operation, in order to shorten the network interruption due to the switching of the program, the switching is performed all at once by the operator's instruction from the management terminal. At this time, the network may be disconnected if there is even one node that has failed to switch. In this case, the operator must use the management terminal to check whether the switching has been successful for each node, and to check the disconnection point, and the network is disconnected until the investigation is completed. become. In particular, when the nodes are cascaded and the management terminal is connected to one terminal node and the network is disconnected due to unsuccessful switching of the other terminal node, it takes a long time to complete the investigation. . Further, when there are a plurality of disconnection points in the network, the recovery is performed one by one, so that it takes time to recover in proportion to the disconnection points.

The present invention has been made in view of the above, and an object thereof is to provide a network device capable of automatically adjusting the operation data version numbers at the time of introduction, replacement, and batch replacement during operation.

[0013]

FIG. 1 shows the principle of the present invention. As shown in FIG. 1, nodes 2 # i (i = 1,
2) is an adjacent node. The node 2 # i includes a data storage unit 4 # i, a version number management unit 6 # i, a version number transmission request unit 8 # i,
The version comparison unit 10 # i, the data transmission request unit 12 # i, the data reception unit 14 # i, and the restart control unit 16 # i are provided. Data is stored in the data storage unit 4 # i. The data is program data, setting data, or the like. The data has a version number, and the version number management unit 6 # i manages version number information of the data stored in the data storage unit 4 # i. It is assumed that the node 2 # 2 has been started up for addition to the network, new introduction, replacement, or the like. On the other hand, it is assumed that the node 2 # 1 has already been operated on the network.

The version number transmission requesting unit 8 # 2 requests the node 2 # 1 to transmit the version number information of the data possessed by the adjacent node 2 # 1 when its own device is started up. Version comparison section 10 #
2 compares the version information of the data managed by the version management unit 6 # 2 with the version information of the data transmitted from the node # 1 based on the transmission request. Data transmission request unit 12 #
2 is the adjacent node 2 based on the comparison result of the version comparison unit.
Requests # 1 to transmit data. Data receiver 1
4 # 2 receives the data transmitted from the adjacent node 2 # 1 and stores the data in the data storage unit 4 # 2. The restart control unit 16 # 2 restarts based on the data received by the data receiving unit 14 # 2. in this way,
When the node 2 # 2 is added or replaced, the necessary data is downloaded from the adjacent node 2 # 1 when the node 2 # 2 is started up, so that the operator does not need to download the data.

[0015]

FIG. 2 is a network configuration diagram according to an embodiment of the present invention. FIG. 2A is a diagram showing a ring-connected network, and FIG. 2B is a diagram showing a cascade-connected network. Figure 2
As shown in (a) and FIG. 2 (b), the network is
Management terminal 50, a plurality of nodes 52 # i (i = 1 to 4),
Transmission path 54 and node 52 connecting between the nodes 52 # i
#I LAN cable 60 # ij (j = 1 to
n).

The management terminal 50 has the following functions.
The monitoring program, NW setting information, and individual setting information are downloaded to the relevant node 52 # i. For communication between the management terminal 50 and the node 52 # i, for example, the management terminal 50 and the node 52 # 1 are connected by a LAN, and LAN communication is performed between the management terminal 50 and the node 52 # 1. Between the management terminal 50 and the node 52 # i (i = 2, ...) For example, SDH main signal communication is performed between the node 52 # 1 and the node 52 # i. All nodes 5 to switch all at once
2 #i (i = 1, ...) Is instructed to restart.

FIG. 3 is a block diagram of the node 52 # i in FIG. As shown in FIG. 3, the node 52 # i has a router 100 # i, an SDH device 102 # i, and a plug-in control unit 104 # i. The router 100 # i has a plurality of L
It accommodates the AN interface 60 # ij (j = 1, ...) And, according to the NW setting data, the LAN interface 5
The IP packet is routed between the 2 # ij and the SDH device 102 # i. The SDH device 102 # i has the following functions. According to the time slot allocation information,
The SDH is interfaced between the main transmission line 54 and the router 100 # i. Monitor the failure with a monitoring program.

FIG. 4 shows the plug-in control unit 104 shown in FIG.
It is a block diagram of #i. As shown in FIG. 4, the plug-in control unit 104 # i includes a program storage unit 150 # i, a device NW setting information storage unit 152 # i, a device individual setting information storage unit 154 # i, and an adjacent device individual setting information. Storage unit 156
#I, version management unit 158 # i, state management unit 160 # i,
Adjacent node data management unit 162 # i, activation factor storage unit 1
64 # i, main line communication unit 166 # i, restart control unit 168 # i, communication control unit 170 # i, and adjacent communication unit 1
72 # i.

The program storage unit 150 # i is, for example, a ROM that stores the monitoring program together with its version number. The own device NW setting information storage unit 152 # i stores the NW setting information of the own device together with its version number, for example, RO
It is M. The own device individual setting information storage unit 154 #i stores the individual setting information of the own device together with its version number in the ROM.
Is. The adjacent device individual setting information storage unit 156 # i is, for example, a ROM that stores the individual setting information of the adjacent node together with its version number. The version number management unit 158 # i includes a program storage unit 150 # i and an own device NW setting information storage unit 15
2 # i and the version number of the program, NW setting information, and individual setting information stored in its own apparatus individual setting information storage unit 156 # i are managed. The state management unit 160 # i manages the state of its own device. The status is normal operation, waiting for download,
Downloading, download complete, start / restart, communication disabled, operating condition checking, operating condition error,
There are various states, FPGA loading and FPGA abnormal.

FIG. 5 is a diagram showing state transitions. Start / restart means reset button ON or power ON
When the program, the NW setting information, and the individual setting information are downloaded, the node is started / restarted when the management terminal 50 issues an external restart instruction. Checking operating conditions means checking the SDH frame between adjacent nodes and checking whether communication is possible between the adjacent nodes. The communication-disabled state means a state in which communication cannot be performed with an adjacent node.

The abnormal operating condition means that the abnormal condition is detected by checking the operating condition. The "waiting for download" means waiting for the download of a program or the like from an adjacent node. Downloading means that a program or the like is being downloaded. Download complete means that the download of the program etc. is completed. FPGA
Loading means that data is being loaded into the FPGA. In the FPGA, a part of the SDH device is configured by the FPGA, and the function of the SDH device is determined by loading FPGA data which is individual setting data. The FPGA abnormality means a state in which an abnormality in FPGA data or the like has occurred. "Normal operation" means that the local node is in operation. The above state transitions as shown in FIG.

The adjacent node data storage section 170 # i has the following functions. When the individual setting information of the adjacent node is received from the communication control unit 170 # i, it is stored in the adjacent device individual setting information storage unit 156 # i. When the communication control unit 170 # i requests reading of the individual setting information of the adjacent node, the individual setting information is read from the adjacent device individual setting information storage unit 156 # i.

The activation factor storage unit 164 # i has the following functions. Save the activation factor. The activation factor means a factor in which the own node is activated, which is activated by an instruction from the management terminal 50 (forced restart), activated at the time of introduction (introduction restart), and activated at the time of replacement ( This means either the restart (exchange restart) or the restart due to the forced restart of the adjacent node (spontaneous restart). The reason for saving the activation factor is to determine the presence / absence of the download based on the activation factor notified from the adjacent node. The operation time after entering the operation state by restarting is measured. The operation time is measured because the operation time should be adjusted according to the latest program. Communication control unit 17
The activation factor and the operation time are read according to the instruction of 0 # i.

The main line communication unit 166 # i transmits / receives data such as a restart instruction and download data from the management terminal 50 which is mapped in the SDH payload. The restart control unit 168 # i has the following functions. When the restart instruction is received from the main line communication unit 166 # i, the restart is started. When the restart instruction is received, the communication control unit 170 # i is notified of that fact,
The activation factor storage unit 164 # i is notified of the activation factor (forced restart). The restart is started according to the instruction from the communication control unit 170 # i.

The communication control section 170 # i has the following functions.

The following processing is performed at the time of introduction.

(I) Request the version number information from the adjacent node through the adjacent communication unit 172 # i. (ii) The version number information is received from the adjacent node through the adjacent communication unit 172 # i. FIG. 6 is a diagram showing the contents of version number information transmitted from an adjacent node. As shown in FIG. 6, the version number information includes its own node state, NW setting information version number, program version number, individual setting information version number, activation factor, and operating time.
It should be noted that, although the individual setting information version number, the activation factor, and the operation time are not required at the time of introduction, it is because the common format is used. (iii) The version number information of the own node is received from the version number management unit 158 # i. (iv) The version number information of the own node and the version number information of the adjacent node are compared to determine whether the download is necessary. Here, at the time of introduction, if it is necessary to download, it is necessary to satisfy the following conditions (a), (b) and (c). (a) Different version numbers, (b) Adjacent node status is normal operation, (c) If the left and right adjacent nodes are normal operation, the left and right adjacent nodes have the same version number. .

7 (a) to 7 (c) are diagrams showing conditions of download and wait at the time of introduction. Figure 7 (a)
Shows a case where the version number of its own node is V0, FIG. 7 (b)
Shows a case where the version number of its own node is V1, FIG. 7 (c)
FIG. 6 is a diagram showing a case where the version number of the own node is V2. Here, the version number refers to the program version number or the version number of the NW setting information. DL means download. The download target at the time of introduction is the program or NW setting information of the version to be compared. WAIT means a state of waiting for download. The activation means a condition for restarting without downloading.

The restart is started when the version number of the program and the version number of the NW setting information satisfy the conditions shown in the figure. In the figure, the list on the left shows the state of the left adjacent node, and the list on the top shows the state of the right adjacent node. In the figure, the list on the left extends to the right and the column on the top extends to the bottom, and the intersecting list refers to the state where the own node transits. For example, if the adjacent nodes on the left and right are in operation and the version numbers are both V1, the download (DL) is performed. Note that the download is performed from the adjacent node on the left, for example. When both the left and right adjacent nodes are in operation, but the version numbers are different, for example, if the version number of the left adjacent node is V1 and the version number of the right adjacent node is V2,
Wait. This is because the nodes in operation should have the same version number, and the difference in version numbers is not a normal state, and therefore waits until a normal state is reached.

(V) If you need to download,
The corresponding version number is passed through the adjacent communication unit 172 # i,
Make a download request to an adjacent node. FIG. 8 is a diagram showing the contents of the download request. As shown in FIG. 8, the download request is made by turning on / off the NW setting information download request flag, the individual setting information request flag, and the program download request flag. (vi) Version number management unit 158 downloads from the adjacent node
Through #i, the program is stored in the corresponding program storage unit 150 #i or the like.

At the time of node replacement, the same processing as at the time of introduction is performed. At this time, if the latest individual setting information is not set in the exchange node, the individual setting information stored in the adjacent node at the time of introduction is downloaded. The individual setting information is downloaded because the version number of the individual setting information of the own node stored in the adjacent node is different from the version number of the individual setting information stored in the own apparatus individual setting information storage unit 154 # i. This is the case (including the case where the individual setting information is not set and the individual setting information is different from the latest one).

The following processing relating to a restart instruction from the outside is performed.

(I) When the restart controller 168 # i notifies the restart controller 168 #, the inter-adjacent communication unit 172 #
Through i, the adjacent node is notified of the version number information shown in FIG. (ii) When the version number information is received from the adjacent node, it is determined whether or not the download is necessary. FIG. 9 is a diagram showing conditions for determining whether or not downloading is necessary. Figure 9
The left side in the center is the left adjacent node, the right side is the right adjacent node, and the leftmost column or the upper right side line is the state of the adjacent node or the state compared with the version number information (operating time) of the own node. The startup time new (old) means that the operation time of the adjacent node is shorter (longer) than the operation time of its own node. As shown in FIG. 9, the inter-adjacent communication unit 17 is provided when all the following conditions (a) to (d) are satisfied.
2 #i makes a download request. (a) Adjacent node is in normal operation, (b) The cause of activation of the adjacent node is an external restart instruction (forced restart) or a restart based on the forced restart of the adjacent node (voluntary restart). That is, (c) the operating time of the adjacent node is shorter than the operating time of the own node, and (d) the version number of the adjacent node and the version number of the own node are different.

(Iii) If the download condition is satisfied, the restart control unit 168 performs the download.
Through #i, a spontaneous restart is performed and the activation factor storage unit 164 #i is notified of the activation factor (spontaneous restart). Note that the left and right adjacent nodes with the shortest operation time are downloaded. (iv) When restarting after downloading, notify the adjacent node of the version number information.

When the version number information is requested from the adjacent node, the version number management unit 158 # i and the activation factor storage unit 16 # i.
The version number information shown in FIG.
2 # i to the adjacent node.

When a download request is made from an adjacent node, the corresponding program storage unit 150 # i and its own device NW will be selected for those for which the download request flag is set.
The data is read from the setting information storage unit 152 # i or the adjacent device individual setting information storage unit 156 # i and transferred to the adjacent node through the inter-adjacent communication unit 172 # i.

When the individual setting information is transferred from the adjacent node, it is stored in the adjacent device individual setting information storage unit 156 # i.

The inter-adjacent communication section 172 # i is the communication control section 1
According to the instruction of 70 # i, communication is performed between adjacent nodes by a sub signal, for example, SDH overhead.

The operation of FIG. 2 will be described below.

(1) At the time of introduction In FIG. 2A, the nodes 52 # 3 and 52 # 1
In the meantime, in FIG. 2B, the operation at the time of introduction will be described by taking as an example the case where the node 52 # 4 is added on the right side of the node 52 # 3. The maintenance person locally connects the node 52 # 4 to the transmission line 54 and turns on the power supply. When the power is turned on, node 5
2 # 4 rises and starts operation. As shown in FIG. 5, a transition is made from the start state to the operating condition checking state.
In the operation state confirming state, it is checked whether or not the communication between the left and right adjacent nodes is possible, and if the communication between the adjacent nodes is impossible, the communication becomes impossible between the adjacent nodes.

10 to 12 are flow charts of download at the time of introduction and exchange. FIG. 13 is a download sequence chart when the node 52 # 4 is added. In step S2, (1L) and (1R) in FIG.
As shown in, the version number notification request is transmitted to the adjacent nodes of both systems. The adjacent nodes 52 # 1 and 52 # 3 are indicated by (2
As shown in L) and (2R), the version number information of the NW setting information, the program, and the individual setting information is transmitted to the node 52 # 4,
The node 52 # 4 receives the version number information. In step S4, it is determined whether or not there is a response from both systems. If there is a response from both systems, the process proceeds to step S6. If there is no response from both systems, the process proceeds to step S30. In step S6, it is determined whether or not both systems are in normal operation. If both systems are in operation, the process proceeds to step S8. If both systems are not in operation, the process proceeds to step S32.

In step S8, as shown by (2) in FIG. 13, it is determined whether the NW setting information of both systems and the version numbers of the programs match. If they do not match, the process returns to step S2. If they match, the process proceeds to step S10. In step S10, it is determined whether or not the version number of the NW setting information of the own node and the version number of the NW setting information of the adjacent node match. If they match, the process proceeds to step S12. If they do not match, the process proceeds to step S14. In step S12, the NW setting information request flag is turned on.

In step S14, it is determined whether the version number of the program of the own node matches the version number of the program of the adjacent node. If they match, the process proceeds to step S18. If they do not match, the process proceeds to step S16. In step S16, the program request flag is turned on.
In step S18, it is determined whether the version number of the individual setting information of the own node and the version number of the individual setting information of the own node held by the adjacent node match. If they match, step S
Go to 50. If they do not match, the process proceeds to step S20.
In step S20, the individual setting information request flag is turned on.

In step S30, it is determined whether or not there is a response from one system. If there is a response,
It proceeds to step S32. If there is no response, the process returns to step S2. In step S32, it is determined whether one-sided normal operation is in progress. If it is in normal operation, the process proceeds to step S34. If not in normal operation, step S
Return to 2. In step S34, it is determined whether the version number of the NW setting information of the own node and the version number of the NW setting information of the adjacent node match. If they match, the process proceeds to step S38. If they do not match, the process proceeds to step S36. In step S36, the NW setting information request flag is turned on.

In step S38, it is determined whether the version number of the program of the own node and the version number of the program of the adjacent node match. If they match, the process proceeds to step S42. If they do not match, the process proceeds to step S40. In step S40, the program request flag is turned on.
In step S42, it is determined whether or not the version number of the individual setting information of the own node and the version number of the individual setting information of the own node of the adjacent node match. If they match, step S
Proceed to 60. If they do not match, the process proceeds to step S44.
In step S44, the individual setting information request flag is turned on.

In step S50 in FIG. 11, it is determined whether or not the on flag is present. If there is an ON flag, the process proceeds to step S52. If there is no ON flag, the process proceeds to step S56. In step S52, in FIG.
As shown in (4), a download request is made to the left adjacent node 52 # 1. In step S54, the process waits for download. In step S56, normal operation is performed. In step S60, it is determined whether or not the on flag is present. If there is an on-flag, step S62
Proceed to. If there is no ON flag, the process proceeds to step S66. In step S62, a download request is made to the active adjacent node. In step S64, the process waits for download. In step S66, normal operation is performed.

Upon receiving the download request, the adjacent node downloads the flag-on ones as shown in (5) and (5 ') in FIG. Node 52 # 4
Receive what was downloaded. In step S80, it is determined whether the data is OK. If the data is not OK, the process returns to step S2. Data is OK
If so, the data is saved and the process proceeds to step S82. In step S82, as shown in (6) of FIG.
Restart. In step S84, normal operation is performed, and the start factor is restart at the time of extension, and the operation time is measured.

(2) Individual setting information download FIG. 14 is a flowchart of the transfer of individual setting information.
FIG. 15 is a sequence chart of transfer of individual setting information. In step S100 in FIG. 14, the node 52
In the case of # 4, individual setting information is input from the management terminal 50 or a terminal connected to the RS-232C interface (not shown) at the time of expansion. In step S102, the node 5
As indicated by (20) in FIG. 15, 2 # 4 requests individual setting information transfer to the left and right adjacent nodes 52 # 1 and 52 # 3. Upon receiving the individual setting information transfer request, the adjacent node 52 # 1 responds as indicated by (21) in FIG. In step S104, the node 52 # 4 determines whether or not there is a response from both systems. If there is a response from both systems, the process proceeds to step S106. If there is no response from both systems, the process proceeds to step S108.

In step S106, (2
As shown in 2), the individual setting information is transferred to the adjacent node. Upon receiving the individual setting information, the adjacent node stores the individual setting information as the individual setting information of the adjacent device. Then, (2
As shown in 3), it responds to the node 52 # 4. In step S108, the node 52 # 4 determines whether or not there is a response from one system. If there is a response from one system, the process proceeds to step S110. If there is no response from one system, the process returns to step S102. Step S110
At, the individual setting information is transferred to the adjacent node. Upon receiving the individual setting information of the node 52 # 4, the adjacent nodes 52 # 1 and 52 # 3 store the individual setting information and respond to the node 52 # 4.

(3) At the time of replacement, for example, a failure occurs in the node 52 # 4 and the node 52 # 4
Suppose you exchange # 4. When the node 52 # 4 is replaced, the node 52 # 4 is started in the same manner as at the time of introduction and the same processing is performed.
At this time, even when the individual setting information is not set in the exchange node 52 # 4, the exchange node 52 # 4 has the version number of the individual setting information of the own node 52 # 4 which the adjacent node has in step S18 in FIG. And the version number of the individual setting information of the exchange node 52 # 4 is different, and when it is determined that the version number is different and the latest individual setting information is stored, the individual setting information is downloaded from the adjacent node. To do.

(4) The management terminal 50 causes all the nodes 52 # i (i = 1, 2, 1) due to a batch download program, version upgrade of NW setting information, and the like.
...) is downloaded. Each node 52 # i
(I = 1, ...) Receives the program downloaded from the main signal and the NW setting information and stores them in the ROM. When the download is completed, the management terminal 50 gives an instruction to restart using the main signal. Node 52 # i (i = 1, ...)
Upon receiving the restart instruction, starts forced restart. Then, the activation factor is forced restart, and the operation time measurement is started.

FIG. 16 is a flow chart for spontaneous restart. FIG. 17 is a sequence chart of a spontaneous restart, in which the node 52 # 3 fails the forced restart and the adjacent nodes 52 # 2 on the left and right of the node 52 # 3.
When 52 # 4 succeeds in the forced restart, the node 5
2 # 3 shows a case where a spontaneous restart is performed. Figure 1
As indicated by (51L) and (51R) in No. 7, it is downloaded from the management terminal 50 to the nodes 52 # 2 and 52 # 4. FIG. 17
As shown in (52L) and (52R), the nodes 52 # 2 and 52
# 4 is forced to restart. On the other hand, the node 52 # 3
As indicated by (53) in FIG. 17, it is assumed that the node 52 # 3 has failed in forced restart. Adjacent nodes 52 # 2, 52
# 4 transmits version number information to the node 52 # 3, as indicated by (54L) and (54R) in FIG. In step S150, version number information is received from the adjacent nodes 52 # 1 and 52 # 4. As shown by (55) in FIG. 17, the following version number comparison is performed.

In step S152, it is determined whether or not there is a response from both systems. If there is a response from both systems, the process proceeds to step S154. If there is no response from both systems, the process proceeds to step S170. Step S154
At, it is determined whether or not both systems are in operation. If both systems are in operation, the process proceeds to step S156. If neither system is in operation, the process proceeds to step S172. In step S156, it is determined whether the NW setting information matches. If they match, the process proceeds to step S158.
If they do not match, the process proceeds to step S180.

In step S158, it is determined whether or not the version number of the individual setting information of the own individual node and the version number of the individual setting information of the own node of the adjacent node match. If they match, the process proceeds to step S160. If they do not match, the process proceeds to step S180. In step S160, it is determined whether the version number of the program of the own node matches the version number of the program of the adjacent node. If they match, the process proceeds to step S184. If they do not match, step S180
Proceed to. In step S180, it is determined whether the activation factor of the adjacent node is forced restart or spontaneous restart. If neither, the process proceeds to step S184. If either, the process proceeds to step S182. In step S182, it is determined whether the activation time of the adjacent node is newer than the activation time of its own node. If new, go to step S190.

In step S170, it is determined whether or not there is a response from one system. If there is a response, the process proceeds to step S172. If there is no response,
It proceeds to step S186. In step S172,
Determine whether one-sided normal operation is in progress. If it is in normal operation, the process proceeds to step S174. If normal operation is not in progress, the process proceeds to step S276. In step S174, it is determined whether the NW setting information matches. If they match, the process proceeds to step S174. If they do not match, the process proceeds to step S180. In step S176, it is determined whether the version number of the individual setting information of the own individual node matches the version number of the individual setting information of the own node of the adjacent node. If they match, the process proceeds to step S178.
If they do not match, the process proceeds to step S180. Step S
At 178, it is determined whether the version number of the program of the own node matches the version number of the program of the adjacent node.
If they match, the process proceeds to step S188. If they do not match, the process proceeds to step S180.

In steps S184 and S186, it is assumed that the node is in operation. In step S190, the flag is turned on for different version numbers, and the adjacent node 52 # 1 having the latest start time is set to (5
6L), a download request is made, and as shown in (57L) (57′L) in FIG. 17, the adjacent node 52 # 1
When the download request flag is turned on, it is downloaded to the node 52 # 3, and when the node 52 # 3 is normally downloaded, as shown by (58) in FIG. 17, the activation factor is automatically restarted, Enter normal operation.
When the node 52 # 3 spontaneously restarts, it notifies the adjacent nodes 52 # 4 and 52 # 1 of version number information in which the activation factor is the spontaneous restart. As a result, if the forced restart fails, it is automatically downloaded from the adjacent node and restarted spontaneously.

Nodes 52 # 2, 52 # 3, 52 #
If the forced restart fails at 4 and the node 52 # 1 succeeds in forced restart, the node 52 # 1 notifies the node 52 # 2 of the version number information in the same manner as described above. Upon receiving the version number information, the node 52 # 2 makes a download request to the node 52 # 1 as described above, and when downloaded, restarts spontaneously and enters normal operation.
Then, the node 52 # 3 is notified of version number information in which the activation factor is spontaneous restart.

The node 52 # 3 issues a download request from the node 52 # 2 in the same manner as described above, and when it is downloaded, the node 52 # 3 restarts spontaneously and enters normal operation, and the node 52 # 4 voluntarily restarts the activation factor. Notify the version number information. Thus, even if three or more nodes 52 # 2, 52 # 3, 52 # 4 connected in series fail in forced restart, they are sequentially downloaded from the nodes that have succeeded in downloading.

According to the embodiment described above, at the time of initial installation of the second and subsequent units, as work at the installation site, confirmation and replacement of the program version number and consistency, setting of network setting information, setting of device individual setting information By eliminating the need for a worker, a worker who has network knowledge at the system engineer level becomes unnecessary. Therefore, if there are many introduced devices,
The labor costs associated with equipment settings will be significantly reduced.

Similarly, at the time of device replacement, there is no need to confirm or replace the consistency between the operating program version number and the replacement device version number, reset network setting information, and reset device individual setting information. , A worker with network knowledge at the system engineer level is not required, and only the person in charge of construction can go to the site, reducing labor costs. With automatic recovery when the batch replacement of programs fails, the recovery time can be minimized. Further, even if there are a plurality of failed parts, the recovery time can be minimized regardless of the number.

The present invention includes the following supplementary notes.

(Supplementary Note 1) A data storage unit for storing data, a version number management unit for managing version number information of the data,
When the self-device is started up, the version number transmission request unit for requesting the adjacent network device to transmit the version number information of the data possessed by the adjacent network device, and the version number information of the data managed by the version management unit. And a version number comparison unit that compares version number information of the data included in the adjacent network device transmitted based on the transmission request, and based on the comparison result of the version number comparison unit, data of the adjacent network device is transmitted. A data transmission requesting unit that requests transmission, a data receiving unit that receives data transmitted from an adjacent network device based on a request from the data transmission requesting unit, and stores the data in the data storage unit; A network device, comprising: a restart control unit that restarts based on data received by a receiving unit.

(Supplementary Note 2) A version number information transmission unit for transmitting version number information of data owned by the own network device to the adjacent network device based on a request for transmission of the version number information from the adjacent network device, and an adjacent network device. 2. The network device according to appendix 1, further comprising: a data transmission unit that transmits the data that the device owns based on the data transmission request.

(Supplementary Note 3) Based on a status management unit that manages the status of the device itself, a status transmission request unit that requests the adjacent network device to send the status, and a status management unit that is based on the status transmission request from the adjacent network device. Further includes a status transmission unit for transmitting the status managed by the adjacent network device to the adjacent network device, wherein the data transmission requesting unit transmits the data when the adjacent network device is in the operating state and the version number of the data is different. The network device as set forth in appendix 2, characterized in that

(Supplementary Note 4) An individual setting data transmitting section for transmitting the individual setting data set in the own apparatus to an adjacent network apparatus when the own apparatus is introduced into a network,
Based on a transmission request from the second data storage unit, the individual setting data received from the adjacent network device, and receiving the individual setting data transmitted from the adjacent network device, and storing the individual setting data in the second data storage unit. The network device according to appendix 3, further comprising: an individual setting information transmitting unit that transmits the individual setting data stored in the second data storage unit.

(Supplementary Note 5) The data is program data, network setting data common to network devices, and the individual setting data. When the data transmission requesting unit has different versions for the program data and the network setting data, Regarding the individual setting data, when the individual setting data of the own device is stored in the adjacent network device, the network device according to appendix 4 is characterized in that a transmission request is made to the adjacent network device.

(Supplementary Note 6) A second restart control unit for restarting in response to a forced restart request from the outside,
From the start factor management unit that manages the restart factor and the operation time after restart, the start factor transmission unit that sends the start factor and operation time to the adjacent network device when restarted, and from the adjacent network device A second data transmission request unit that requests the adjacent network device to transmit data when the transmitted activation factor is a forced restart request and the operating time of the adjacent network device is shorter than the operating time of its own device. A second data receiving unit that receives data based on a request from the second data transmission requesting unit transmitted from an adjacent network device and stores the data in the data storage unit; and a spontaneous restart based on the data. 6. The network device according to appendix 5, further comprising a third restart controller.

(Supplementary Note 7) The activation factor transmission unit, when the spontaneous restart is performed, transmits the activation factor to be the spontaneous restart to the adjacent network device, and the second data transmission request unit causes the activation factor to be voluntarily generated. 7. The network device according to appendix 6, wherein the network device is a restart and requests the adjacent network device to transmit data when the operation time is shorter than the operation time of the own device.

(Supplementary Note 8) The network managed by the supplementary note 3, wherein the status managed by the status management unit includes a download waiting status, which is waiting for data transfer from an adjacent network device, an operational status, and a communication disabled status. apparatus.

[0070]

According to the present invention described above, since the data is downloaded from the adjacent node at the time of introduction, no operator is required.

[Brief description of drawings]

FIG. 1 is a principle diagram of the present invention.

FIG. 2 is a network configuration diagram according to an embodiment of the present invention.

FIG. 3 is a node configuration diagram in FIG.

4 is a configuration diagram of a plug-in control unit in FIG.

FIG. 5 is a state transition diagram.

FIG. 6 is a diagram showing the contents of version number information.

FIG. 7 is a diagram showing download and wait conditions at the time of introduction.

FIG. 8 is a diagram showing download request contents.

FIG. 9 is a diagram showing a relationship between spontaneous restart and version number information.

FIG. 10 is a flowchart of download at the time of introduction and replacement.

FIG. 11 is a flowchart of download at the time of introduction and replacement.

FIG. 12 is a flowchart of download at the time of introduction and replacement.

FIG. 13 is a sequence chart at the time of introduction.

FIG. 14 is a flowchart of individual setting information transfer.

FIG. 15 is a sequence chart of individual setting information transfer.

FIG. 16 is a flowchart of a spontaneous restart.

FIG. 17 is a sequence chart up to a spontaneous restart.

[Explanation of symbols]

2 # 1, 2 # 2 nodes 4 # 2 data storage 6 # 2 Version Management Department 8 # 2 Version transmission request part 10 # 2 Version comparison section 12 # 2 Data transmission request section 14 # 2 Data receiver 16 # 2 Restart controller

   ─────────────────────────────────────────────────── ─── Continued front page    F term (reference) 5B076 AC07 BB02 BB06                 5K019 BA01 BA51 CA05 DA03                 5K030 GA12 HA08 HB14 HB20 JL10                       KA05 LD18 MA07 MC07

Claims (5)

[Claims] 1. A data storage unit that stores data, a version number management unit that manages version number information of the data, and a version number information of data that an adjacent network device has when its own device is started up. A version number transmission request unit for requesting the adjacent network device, version number information of data managed by the version number management unit, and version number information of data included in the adjacent network device transmitted based on the transmission request. And a data transmission request unit that requests the adjacent network device to transmit data based on a comparison result of the data version comparison unit, and an adjacency based on a request from the data transmission request unit. A data receiving unit that receives data transmitted from the network device and stores the data in the data storage unit; and a list based on the data received by the data receiving unit. A network device, comprising: a restart control unit for starting. 2. A state management unit that manages the state of its own device, a state transmission request unit that requests the neighboring network device to transmit the state, and a state management unit that manages the state based on a state transmission request from the neighboring network device. A status transmission unit for transmitting the status to the adjacent network device to the adjacent network device, wherein the data transmission requesting unit requests the transmission of the data when the adjacent network device is in the operating state and the version number of the data is different. The network device according to claim 1, wherein: 3. An individual setting data transmitting unit for transmitting the individual setting data set in the own device to an adjacent network device when the own device is introduced into a network, a second data storage unit, and a transmission from the adjacent network device. The individual setting data received by the received individual setting data and stored in the second data storage unit, and the individual setting data stored in the second data storage unit based on a transmission request from the adjacent network device. The network device according to claim 2, further comprising: an individual setting information transmitting unit that transmits the. 4. A second restart control unit that restarts based on a forced restart request from the outside, and a start factor management unit that manages the restart factor that has been restarted and the operation time after restarting. When a restart is performed, the activation factor and the operating time are transmitted to the adjacent network device, and the activation factor transmitted from the adjacent network device is a forced restart request, and the operating time of the adjacent network device is When it is shorter than the operating time,
A second requesting the adjacent network device to transmit data
A data transmission request unit, a second data reception unit that receives data based on a request from the second data transmission request unit transmitted from an adjacent network device, and stores the data in the data storage unit; 4. The network device according to claim 3, further comprising a third restart control unit that spontaneously restarts. 5. The activation factor transmission unit, when the spontaneous restart is performed, transmits an activation factor to be a spontaneous restart to an adjacent network device, and the second data transmission request unit causes the activation factor to be spontaneously restarted. 5. The network device according to claim 4, wherein when the operating time is shorter than the operating time of the device itself, the adjacent network device is requested to transmit data.