JP2004265304A - Remote network equipment management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a remote network equipment managing method capable of preventing update from being disrupted and invalidated due to an unexpected accident when the software of network equipment is updated from a remote place without changing a mechanism(configuration or the like) or a program inside the network equipment to be updated. <P>SOLUTION: When the software of network equipment is updated from a center device through a wide band network, a file for update is temporarily transmitted from the center device to a predetermined terminal. Afterwards, the file for update is transmitted from the terminal through a local network to the network equipment, and the update is executed. After the execution of update, the normal operation of the network equipment is confirmed, and the network equipment is automatically reset from the terminal when the normal operation of the network equipment is not confirmable. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a remote network device management method capable of remotely and securely updating software of various network devices.
[0002]
[Prior art]
When updating software such as firmware incorporated in a network device such as a router or a firewall, an end user actually using the network device uses an update file downloaded or sent on a flexible disk or the like. Update directly. In addition, a worker goes to a site where the network device is located, and updates the file using an update file. However, in the method of updating the end user by himself, there must be a person who has some knowledge on the end user side. Further, if the worker goes to the base, there is a disadvantage that the man-hour of the worker is increased.
[0003]
In order to solve these inconveniences, attempts have been made to update the software of the network device by transmitting an update file directly from the remote center to the network device via the Internet.
[0004]
Further, in the method described in Patent Document 1, a plurality of FLASH memories are prepared, update software is stored in the first FLASH memory, and when the storage is completed, the download completion flag is turned on. Is copied to the second FLASH memory, the copy completion flag is turned on. When the initial setting signal is generated, the download completion flag is checked. If the download completion flag is on, the copy completion flag is checked. If the copy completion flag is on, the download completion flag is stored in the second flash memory. It is determined that the update software is stored. When the download completion flag is off, the old version in the second FLASH memory is used.
[0005]
[Patent Document 1] Japanese Patent Application Laid-Open No. 2002-189609
[Problems to be solved by the invention]
In the above-described method of updating the software of a network device by transmitting an update file from the remote center to the network device via the Internet, the update is performed simultaneously on a large number of network devices from a remote location. Is possible. However, due to various conditions such as device characteristics and line characteristics, unexpected accidents such as disconnection of the Internet during the update may occur.In this case, network devices may not operate. It is conceivable that the connection from the network device to the Internet becomes completely impossible. When the network device stops operating, it is necessary to take measures such as resetting the network device.
[0007]
According to the method disclosed in Patent Document 1, it is possible to avoid such a situation that the network device does not operate at all. However, this cannot be realized without changing the mechanism (such as the configuration) or the program inside the network device, and cannot be realized on other devices.
[0008]
SUMMARY OF THE INVENTION In view of the above-described problems in the related art, the present invention is not unexpected when updating the software of a network device remotely without changing the internal mechanism (such as the configuration) or the program of the network device to be updated. It is an object of the present invention to provide a remote network device management method capable of preventing an update from being interrupted due to an accident and a loss of communication after that.
[0009]
[Means for Solving the Problems]
To achieve the above object, an invention according to claim 1 is a remote network device management method for updating software of a network device from a center device via a wide area network, wherein the method is connected to the network device via a local area network. Transmitting the update file from the center device to the predetermined terminal, and after receiving the update file at the terminal, the terminal transmits the update file to the network device via the local area network. And executing a software update in the network device.
[0010]
The invention according to claim 2 is a remote network device management method for updating software of a network device from a center device via a wide area network, wherein a predetermined terminal connected to the network device via a local area network includes: Transmitting an update file from a center device; and, after receiving the update file at the terminal, transmitting the update file from the terminal to the network device via the local area network. Executing a software update; waiting at the terminal for a predetermined waiting time after transmitting the update file; and after the waiting, confirming operation of the network device from the terminal. Further comprising the step of issuing a command to be characterized.
[0011]
The invention according to claim 3 is the remote network device management method according to claim 1 or 2, wherein when the terminal receives the update file, the terminal confirms that the received update file is normal, When the terminal is confirmed to be normal, the terminal transmits the update file to the network device.
[0012]
According to a fourth aspect of the present invention, in the remote network device management method according to the second aspect, the step of issuing a command for confirming an operation of the network device from the terminal includes the step of: A communication confirmation is transmitted via a network device and a wide area network, and the terminal confirms whether or not a response communication is returned from the center device in response to the communication confirmation.
[0013]
According to a fifth aspect of the present invention, in the remote network device management method according to the second aspect, the predetermined waiting time is determined based on a characteristic of the network device, a capacity of an update file, or an interval between the terminal and the network device. Is determined on the basis of at least one of the communication characteristics.
[0014]
According to a sixth aspect of the present invention, in the remote network device management method according to any one of the second to fifth aspects, when the normal operation of the network device cannot be confirmed by issuing the command, the terminal transmits the command to the remote device. The network device is reset.
[0015]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0016]
FIG. 1 is a configuration diagram for explaining the outline of the remote network device management method according to the present embodiment. For example, various network devices 104 such as a router and a firewall and a terminal 103 are connected to a local area network (LAN) 105 installed in a certain company or the like. The network device 104 is connected to the Internet 102. Further, a center device 101 is connected to the Internet 102.
[0017]
In the present embodiment, the firmware of the network device 104 can be automatically updated from the remote center device 101. The procedure is as follows.
[0018]
(1) A file for automatically updating the firmware of the network device 104 is transmitted from the center device 101 to a predetermined terminal 103 on the LAN 105 side (11).
[0019]
(2) In the terminal 103 on the LAN 105 side, automatic update software is installed, and when an update file is transmitted from the center apparatus 101, the automatic update software is started. The automatic update software automatically updates the firmware of the network device 104 based on the received update file (112).
[0020]
FIG. 2 shows a detailed configuration of the center device 101 and the terminal 103 of FIG. In the center device 101, a file distribution program 211, a confirmation program 212, a communication management program 213, and a result notification program 214 are operating. In the terminal 103, a file distribution / confirmation program 221, a result notification program 222, a power control program 223, a communication management program 224, and a file distribution / update program 225 are operating.
[0021]
First, a file for updating the firmware of the network device 104 is transmitted to the terminal 103 via the Internet 102 by the file distribution program 211 of the center device 101. After receiving the update file, the terminal 103 confirms the consistency of the file by the file distribution / confirmation program 221 and notifies the center apparatus 101 of the confirmation result. After confirming that the file is normal, the terminal 103 updates the network device 104 based on the update file using the file distribution / update program 225. After the update is executed, the communication control program 224 of the terminal 103 waits for a predetermined time t, and then transmits a communication confirmation to the communication management program 213 of the center apparatus 101.
[0022]
The predetermined time t is a time considered to be sufficient until the update in the network device 104 is completed. For example, the characteristic of the network device 104, the capacity of the update file transferred for the update, or the terminal 103 and the network device 104 What is necessary is just to determine based on at least one of the communication characteristics with, for example.
[0023]
Upon receiving the communication confirmation, the communication management program 213 of the center apparatus 101 transmits a response communication to the communication management program 224 of the terminal 103. When the response is received, the result notification program 222 of the terminal 103 notifies the center device 101 of the success. If there is no response communication from the communication management program 213 of the center apparatus 101 to the communication management program 224 of the terminal 103 in response to the communication confirmation, the power supply control program 223 automatically restarts the network device 104, and the result notification program At 222, a restart execution notification is sent to the center apparatus 101.
[0024]
FIG. 3 shows a sequence diagram in the case where the update of the firmware of the network device has been completed normally in the present embodiment.
[0025]
The center device transmits the update file to the terminal (301), and after confirming that the file has been normally transmitted, the terminal notifies the center device of the reception of the file (302). Thereafter, the terminal sends the file sent from the center device to the network device and executes the update (303). The terminal waits for a predetermined waiting time t until the update is completed (304), and then confirms communication with the center device (305). This waiting time t may be determined as described with reference to FIG. The center device waits until a communication confirmation is sent from the terminal, and upon receiving the communication confirmation, returns a response communication to the terminal (306). After receiving the response from the center device, the terminal transmits an update completion notification to the center device (307), and ends the process.
[0026]
FIG. 4 shows a sequence diagram when the update of the firmware of the network device has failed in the present embodiment.
[0027]
The center device transmits the update file to the terminal (401), and after confirming that the file has been normally transmitted, the terminal notifies the center device of the reception of the file (402). Thereafter, the terminal sends the file sent from the center device to the network device and executes the update (403). The terminal waits for a predetermined waiting time t until the update is completed (404), and then confirms communication with the center device (405). If there is no response from the center device (406), the terminal executes reset for the network device (407), and sends a reset execution notification to the center device (408).
[0028]
FIG. 5 is a flowchart showing a processing procedure in the center device 101 for implementing the operation of the present embodiment as described above. In step 501, the update file is transmitted to the terminal 103. In step 502, it is determined whether or not the number of retries is equal to or more than a predetermined number of times. If the number of retries is equal to or more than n times, the process is terminated assuming that the communication situation is bad. If the number of retries is not n or more, the reception notification is confirmed in step 503. If the confirmation cannot be made, the process returns to step 501 to continue the file transmission. If the reception notification has been confirmed, it is determined in step 504 whether or not the communication confirmation from the terminal 103 has been received. If the communication confirmation has been received, response communication is returned in step 505. When the reset execution notification is received instead of the response communication in step 504, step 505 is skipped and the process proceeds to step 506. In step 506, it is determined whether an update or reset execution notification has been received. If either is received, the process ends.
[0029]
FIG. 6 is a flowchart showing a processing procedure in the terminal 103 for realizing the operation of the present embodiment as described above. At step 601, an update file is received. In step 602, it is checked whether the received update file is normal. If the reception has failed, a reception failure notification is sent to the center device 101 in step 603, and the process returns to step 601. If the received file is confirmed to be normal, a reception notification is transmitted to the center apparatus 101 in step 604, and the update file is uploaded to the network device 104 in step 605. As a result, in the network device 104, the firmware is updated based on the update file. Next, at step 606, the process waits for a predetermined waiting time t. Thereafter, in step 607, a communication confirmation is transmitted to the center device 101. In step 608, it is confirmed whether or not there is a response communication from the center device. If there is, a notification indicating that the update was successful is transmitted to the center device 101 in step 609, and the process ends. If there is no response from the center device, the network device 104 is reset in step 610, and a reset execution notification is transmitted to the center device 101 in step 611, and the process ends.
[0030]
The communication between the center apparatus 101 and the terminal 103 is preferably performed by encrypted communication such as a VPN (virtual private network). In the above embodiment, the center device 101 and the network device 104 are connected via the Internet. However, the present invention is not limited to the Internet but can be applied to a wide area network using a dedicated line or a public line. Further, in the above embodiment, the communication confirmation is transmitted from the terminal and the normal operation of the network device is confirmed based on whether or not there is a response communication in response to the communication confirmation. However, the present invention is not limited to this. A method of sending the data to a device and confirming the operation may be adopted.
[0031]
【The invention's effect】
As described above, according to the present invention, when software of a network device is updated from a center device via a wide area network, an update file is temporarily transmitted from the center device to a predetermined terminal, and then the terminal device transmits the update file to the network. Since the update file is transmitted to the device via the local network and the update is executed, if the update file is not sent from the center device to the terminal due to communication conditions of the wide area network, the update is not performed. , And secure and reliable updates. In particular, by checking the normality of the update file received by the terminal, if a communication failure occurs, the network device does not have to read the damaged file.
[0032]
In addition, if the terminal instructs the network device to update and then waits for a predetermined waiting time to check the operation, the update can be executed more reliably. If an unexpected accident occurs during the update and the network device cannot operate normally, the terminal automatically resets (restarts) the network device, minimizing the time during which communication is not possible be able to. Furthermore, there is no need to change the internal mechanism (such as the configuration) or the program on the network device side.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of an embodiment of the present invention.
FIG. 2 is a schematic diagram showing a detailed configuration of a center device and a terminal.
FIG. 3 is a sequence diagram when the firmware update is completed normally.
FIG. 4 is a sequence diagram in a case where an accident has occurred in a firmware update.
FIG. 5 is a flowchart illustrating a processing procedure in the center device.
FIG. 6 is a flowchart illustrating a processing procedure in a terminal.
[Explanation of symbols]
101: Center device, 102: Internet, 103: Terminal, 104: Network device, 105: Local area network (LAN), 211: File distribution program, 212: Confirmation program, 213: Communication management program, 214: Result notification program, 221, a file distribution / confirmation program, 222, a result notification program, 223, a power control program, 224, a communication management program, 225, a file distribution / update program.

Claims (6)

A remote network device management method for updating software of network devices from a center device via a wide area network,
Transmitting a file for update from the center device to a predetermined terminal connected to the network device via a local area network;
After receiving the update file at the terminal, transmitting the update file from the terminal to the network device via the local area network, and performing a software update in the network device. A method for managing remote network devices, comprising: A remote network device management method for updating software of network devices from a center device via a wide area network,
Transmitting a file for update from the center device to a predetermined terminal connected to the network device via a local area network;
After receiving the update file at the terminal, transmitting the update file from the terminal to the network device via the local area network, and performing a software update on the network device;
At the terminal, after transmitting the update file, waiting for a predetermined waiting time;
Issuing a command for confirming the operation of the network device from the terminal after the waiting. The remote network device management method according to claim 1 or 2,
When the terminal receives the update file, the terminal confirms that the received update file is normal. A remote network device management method. The remote network device management method according to claim 2,
The step of issuing a command for confirming the operation of the network device from the terminal includes transmitting a communication confirmation from the terminal to the center device via the network device and a wide area network, and responding to the communication confirmation by the center. A remote network device management method, wherein the terminal checks whether or not a response communication is returned from the device. The remote network device management method according to claim 2,
Wherein the predetermined waiting time is determined based on at least one of a characteristic of the network device, a capacity of an update file, and a communication characteristic between the terminal and the network device. Network device management method. The remote network device management method according to any one of claims 2 to 5,
If the normal operation of the network device cannot be confirmed by issuing the command, the terminal resets the network device from the terminal.

Images