JP4777307B2 - Network setting restoration method and system - Google Patents

Description

  The present invention relates to a network setting restoration method and system that restores a setting of a network device such as a router or a server by switching back to the state before the change, and in particular, a network setting restoration method that enables restoration in a short time and About the system.

  A next-generation network operation server that manages network configuration files for network devices such as routers and servers (hereinafter sometimes simply referred to as configuration files) was installed on the network (NW), causing problems such as operational errors. In this case, a system that supports quick failure recovery by reading the previous setting files collectively from the next-generation NW operation server and sequentially switching back to each network device is disclosed in Non-Patent Documents 1 and 2 and Patent Documents. 1 is disclosed. The conventional switch back of the network setting file is executed by the following procedure, for example.

  Procedure 1: An operator operates (operates / sets) various network devices such as routers, switches, and servers using a client terminal. At that time, the next generation NW operation server collects operation logs. Also, the configuration files of all network devices are saved and managed at the end of the operation.

  Procedure 2: When an error or the like is included in the content of the operation, an alarm or failure occurrence is notified.

  Procedure 3: The operator operates the next generation NW operation server via the client terminal, and switches back the setting files of all the managed devices to the previous state (at any time point where they were operating normally). Thereby, it recovers from the failure.

Procedure 4: After the failure recovery, the operator analyzes the operation log stored and managed by the next generation NW operation server to identify the cause of the failure.
“Proposal of a dependable network management system that enables quick recovery from operational errors”, Takahito Yoshihara et al .: Proceedings of the IEICE General Conference 2007 Implementation of a dependable network management system that enables quick recovery from operational mistakes, Daisuke Arai et al .: Proceedings of the IEICE General Conference 2007 Japanese Patent Application No. 2006-249299

  Of the network devices that are subject to switchover of the network settings, the routers and switches that operate in accordance with their own route information and the network configuration switchback the route information to the previous settings. In some cases, the route information is flawed between the device before switch back and the device after switch back, and the connection is cut off. Therefore, it is desirable to switch back the network settings in order from a router or the like located far from the operation server so that the influence of drought can be suppressed to a minimum among network devices, particularly routers and switches.

  However, in the above prior art, even when switching back the network settings of routers and switches, the order was not taken into account at all, so many routes were cut off immediately after the start of switching back and communication was disabled. There was a technical problem.

  An object of the present invention is to provide a network setting restoration method and system capable of resolving all the above-described problems of the prior art and switching back a network setting of a router or a switch while ensuring connectivity from a server.

  In order to achieve the above-described object, the present invention operates based on its own route information, saves a setting file of a network device constituting the network in an operation server in response to a save request, and then switches back In the network setting restoration method for restoring the network settings by switching back the registered configuration file specified in the request to each network device, the operation server detects the number of hops to each network device, and the number of hops And a procedure for determining a switch back order so that the network setting is switched back preferentially from a network device having a large number of network devices.

  According to the present invention, it operates based on its own route information, and the setting file of the network device constituting the network can be switched back in order from the network device far from the operation server, so the connectivity with the server is maintained. Restoration is possible.

  DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the best embodiment of the present invention will be described in detail with reference to the drawings. FIG. 1 is a diagram showing a typical assumed environment of a network to which a network setting restoration method according to the present invention is applied.

  The network 1 to be managed accommodates various network devices A, B, C, D, etc., such as switches, routers, or servers, to be restored from the network setting file. The network 1 further obtains a network setting file from each network device in response to a storage request from the client 2 that performs network settings for each network device and the client 2, and further performs a switchback request from the client 2. In response to this, the operation server 3 is connected to restore the network setting by switching back the registered setting file to each network device.

  In FIG. 2, the configuration files of the four network devices A, B, C, and D are updated by the operation of the client 1, and the updated configuration file is associated with the two identifiers IDs and IDrs and stored in the operation server 3. FIG.

  In the present invention, the setting files of all network devices are stored in the operation server 3 in association with the first identifier (session identifier IDs) representing the storage time for each storage request. Further, in the present invention, in order to avoid waste of repeatedly acquiring an unupdated setting file for each storage request from each network device, only setting files that may be updated are acquired from each network device, Regarding the unupdated setting file, the setting file already registered in the operation server 3 is read and copied.

  Therefore, in the present invention, a second identifier (actual session identifier IDrs) representing the time when the copy source setting file is newly saved is defined, and this actual session identifier IDrs is also associated with each setting file. Accordingly, in the setting file that is acquired from the network device and newly saved, the session identifier IDs and the actual session identifier IDrs have the same value.

  In FIG. 2, the configuration files Fa, Fb, Fc, and Fd of all network devices A, B, C, and D are linked to the session identifier IDs and the actual session identifier IDrs that represent the storage timing at time t1. Registered in advance in the server 3. If the time t1 is the first storage timing, “1” representing the time t1 is registered in both the session identifier IDs and the real session identifier IDrs.

  FIGS. 3 and 4 are flowcharts showing the operation of the operation server 3. Only the setting files Fb and Fc of the two network devices B and C are updated after the time t1 in FIG. Is notified from the client 1 to the operation server 3, this is detected in step S1 of FIG. 3, and the process proceeds to step S2. In step S2, a setting file saving process is executed.

  FIG. 4 is a flowchart showing a procedure of the setting file saving process. In step S201, a session identifier IDs = 2 and a real session identifier IDrs = 2 representing the time t2 are set. In step S202, one of network (NW) devices having an operation history after the previous storage time t1 is selected. In the present embodiment, the description will be continued assuming that there is an operation history for the three network devices B, C, and D, and the network device B is selected first.

  In step S203, the setting file Fb of the network device B is acquired by the operation server 3. In step S204, the setting file Fb of the network device B is read from the registered setting file group associated with the session identifier IDs = 1 representing the immediately previous storage time t1. Then, the setting file Fb (IDs = 1) is compared with the current setting file Fb acquired at time t2, and whether or not there is an update is determined based on whether or not they match. If they do not match, it is determined that there has been an update, and the process proceeds to step S205, where the current setting file Fb acquired in step S203 includes the session identifier IDs = 2 representing the time t2 and the actual session identifier IDrs = 2. Saved by tying.

  In step S206, it is determined whether or not each process described above has been completed for all network devices having an operation history. Here, since the processes for the network devices C and D remain, the process returns to step S202 and the above-described processes are performed. The process is repeated. At this time, as with the network device B, it is determined that the setting file has been updated for the network device C. Therefore, the setting file Fc acquired from the network device C in step S203 represents the time t2. The session identifier IDs = 2 and the actual session identifier IDrs = 2 are stored in association with each other.

  On the other hand, for the network device D, for example, only an operation history referring to the file remains, so in step S204 it is determined that the setting file has not been updated, and the process proceeds to step S206.

  In step S207, one of the network devices whose configuration file has not been updated is selected. In the present embodiment, two network devices A and D are selected sequentially. In step S208, with respect to the selected network device, the configuration file of the unupdated network device is selected from the registered configuration file group associated with the session identifier IDs = 1 representing the previous storage time t1. Read together with its session identifier IDs and real session identifier IDrs. In step S209, only the session identifier IDs is rewritten to “2” representing the current storage time t2, and stored as one of the setting file groups corresponding to the session identifier IDs = 2.

  In the case of network device A, a setting file having the same contents as the already registered setting file Fa (IDs = 1, IDrs = 1) associated with the session identifier IDs = 1 and the actual session identifier IDrs = 1 The session identifier IDs = 2 representing the storage time t2 and the actual session identifier IDrs = 1 are stored in association with each other.

  In step S210, it is determined whether or not each process described above has been completed for all network devices whose configuration files have not been updated, and the process returns to step S207 until the above process is completed for all network devices. The process is repeated.

  Returning to FIG. 2, when a save request is detected at time t2 as described above, the setting files Fb and Fc of the two network devices B and C are set to the session identifier IDs = 2 representing the save time t2 and the actual session. It is associated with the identifier IDrs = 2 and stored in the operation server 3.

  On the other hand, the configuration files Fa and Fd of the remaining network devices A and D whose configuration files have not been updated have the session identifier IDs = 2 representing the current storage time t2 and the configuration files are newly stored. The real session identifier IDrs = 1 representing the time t1 is linked to the operation server 3 and registered.

  Furthermore, when only the setting file Fd of the network device D is updated after the time t2, and a new save request is detected at the time t3, the setting file Fd of the network device D is a session representing the current save time t3. The identifier IDs = 3 and the real session identifier IDrs = 3 are associated with each other and registered in the operation server 3.

  On the other hand, among the remaining configuration files Fa, Fb, and Fc of the remaining network devices A, B, and C whose configuration files have not been updated, the content of the network device A is the same as the content newly stored at time t1. Is registered in the operation server 3 in association with the session identifier IDs = 3 representing the current storage time t3 and the actual session identifier IDrs = 1 representing the time t1.

  Similarly, for the configuration files Fb and Fc of the network devices B and C whose contents of the setting file are the same as the contents newly saved at time t2, the session identifier IDs = 3 representing the current saving time t3 and the time t2 Is registered in the operation server 3 in association with the real session identifier IDrs = 2 representing the above.

  Next, a procedure for switching back the setting file of each network device to the setting contents at a desired restoration time using the setting file saved in time series as described above will be described. Here, a case will be described as an example where the setting file of each network device is updated through the process shown in FIG. 5 and the latest storage timing is time t3.

  The operator transmits a reversion request including a desired restoration time from the client 1 to the operation server 3, and when this is detected in step S3 in FIG. 3, the process proceeds to step S4, and a setting file reversion process is executed. Here, the description is continued assuming that t2 is designated as the restoration time.

  FIG. 7 is a flowchart showing a procedure of the setting file switch-back process, and FIG. 8 is a sequence flow thereof.

  In step S401, it is determined whether there is a newly operated network device after the latest storage time t3. If there is no operated network device, the process proceeds to step S403, and if there is, the process proceeds to step S402. In step S402, processing similar to the setting file saving processing described in the flowchart of FIG. 4 is executed, and the setting file is saved in the operation server 3 in the same manner as described above, with the reception time t4 of the switchback request as the saving time. Thereafter, the process proceeds to step S403.

  FIG. 6 is a diagram showing the update state of the setting file of each network device when the network setting saving process is newly executed at time t4. Here, network device B is operated after time t3. Therefore, the setting file Fb of the network device B is fetched and associated with the session identifier IDs = 4 and the actual session identifier IDrs = 4 representing the storage time t4 and newly stored in the operation server 3.

  For other network devices A, C, and D that have not been updated, the setting file associated with the session identifier IDs = 3 representing the previous storage time t3 is read, and only the session identifier IDs are The session identifier IDs = 4 representing the current storage time t4 is overwritten and stored.

  In step S403, the actual session identifier IDrs of each setting file associated with the session identifier IDs = 3 representing the latest (immediately) saved time (in the example of FIG. 5, time t3), and the restoration time t2 are represented. The session identifier IDs = 2 and the actual session identifier IDrs associated with each setting file are compared, and the network device to be reverted is specified based on the comparison result. In other words, network devices whose actual session identifiers IDrs do not match are targeted for reversion.

  Referring to FIG. 5, the actual session identifier IDrs of the configuration file Fa stored at the time t3 of the network device A and the actual session identifier IDrs of the configuration file stored at the restoration time t2 are both “1”. Since it can be seen that the setting files at the times t2 and t3 are the same, the network device A is not set as a target for reversion.

  Similarly, for the network devices B and C, the actual session identifier IDrs at the time t3 and the actual session identifier IDrs at the restoration time t2 of the setting files Fb and Fc are both “2”, and the settings at the times t2 and t3 are performed. Since the files are found to be the same, the network devices B and C are not subject to switchback.

  On the other hand, for the network device D, the actual session identifier IDrs at the restoration time t2 of the setting file Fd is “1”, whereas the actual session identifier IDrs at the latest storage time t3 is “3”. Yes, since it can be seen that the setting files at the times t2 and t3 are different, the network device D is set as the target of reversion.

  In the example shown in FIG. 6, the network devices A and C are not subject to reverting, and the network devices B and D are subject to reverting.

  Returning to the flowchart of FIG. 7, in step S404, one identified network device to be switched back is selected. In step S405, a network setting switch-back process, which will be described in detail later, is executed for this network device. In step S406, it is determined whether or not the reversion processing for all reversion targets has been completed, and the process returns to step S404 until the completion, and the above-described procedures are repeated.

  Next, the network setting switch-back method executed in step S405 will be described.

  In this embodiment, whether or not the network device is a device that is executed by copying the configuration file stored in the non-volatile storage area to the volatile storage area at startup, such as a Cisco router or switch. Depending on the device, the switchback procedure differs, and the device that copies and executes the setting file stored in the non-volatile storage area to the volatile storage area at startup executes the switchback procedure using the commands detailed below. In other devices, the same switch-back procedure as in the prior art is executed.

FIG. 9 is a diagram showing an example of a configuration file for a Cisco router. The configuration file is a set of “items” sandwiched between two “!” Marks, and each “item” includes “items”. Value "is registered. Here, the three item values “ip route 0.0.0.0 0.0.0.0 192.168.1.1”, “ip route 192.168.2.0 255.255.255.0 192.168.0.8”, “ip route 192.168.” Registered in the item “static route” 3.0 255.255.255.0 192.168.0.8 ”will be explained. In the present invention, switching back is executed by adopting one of the following two switching back methods.
[First failback method]

Cisco routers have non-volatile "startup-config" and volatile "running-config" as storage areas for configuration files, and the contents of "startup-config" are changed to "running-config" when the router starts up. After that, the router operates according to the configuration file registered in "running-config". Therefore, if the restoration time configuration file is written in “startup-config” and then the router is restarted, the configuration file is copied to “running-config”, so that the router can be restored.
[Second failback method]

  In the first switch-back method described above, it is necessary to restart the router. However, if the restoration target configuration file can be directly copied to "running-config" instead of "startup-config", it is not necessary to restart the router. However, if the copy command to "running-config" is merged (combined) as in the case of Cisco routers, the contents of the restore target configuration file and the "running-config" after switching back May occur.

  FIG. 10 is a diagram for explaining a trap that can be generated when a restoration target setting file is merged with “running-config” of a network device. The restoration target is restored from the current setting file registered in “running-config”. If the switch back to the configuration file is only the addition or change of the item value, there is no hesitation just by merging the restore target configuration file into the current configuration file. However, when the item value is deleted, the existing unnecessary item value cannot be deleted by merging, which causes a flaw.

  Therefore, in the second failback method, the current setting file and the restoration target setting file are compared in advance to find the difference between the two. When copying directly to "-config", but a crease occurs in the merge, the operation server 3 generates a command for rewriting "running-config" and sends this to the network device to rewrite "running-config" I have to.

  Hereinafter, the procedure of the second switching back method described above will be described in detail with reference to the flowchart of FIG.

  In step S61, the difference between the latest setting file and the restoration target setting file is acquired for each setting item. In step S62, it is determined whether or not merge back-up is possible based on the difference. If it is possible to switch back by merging, the process proceeds to step S63, and the restoration target configuration file is copied (merged) to the "running-config" of the router.

  On the other hand, if it is impossible to switch back by merging, the process proceeds to step S64, and one of the items is selected. In step S65, with respect to the selected item, a difference between each item value of the latest setting file and each item value of the restoration target setting file is referred to. If there is a difference, the process proceeds to step S66, and a command for switching back this difference is obtained. Is generated.

  FIG. 12 is a flowchart illustrating a procedure for generating a command. Here, a command for switching back the item “static route” will be described as an example.

  In step S71, the difference is analyzed for each item value. In step S72, based on the analysis result, it is determined whether the update content from the restoration target setting file to the current setting file is “deletion”, “addition”, or “change”.

  As shown in FIG. 13, even if the current configuration file has some item values (in this case, “ip route 192.168.3.0 255.255.255.0 192.168.0.8”) deleted from the restoration target configuration file. For example, since it is determined as “delete”, the process proceeds to step S73 to generate a command “iproute 192.168.3.0 255.255.255.0 192.168.0.8” for adding this item value to the setting file.

  Moreover, as shown in FIG. 14, the current configuration file is a content in which some item values (in this case, “ip route 0.0.0.0 0.0.0.0 192.168.1.1”) are added to the restoration target configuration file. If there is, it is determined as “added”, so the process proceeds to step S74, and a command “no iproute 0.0.0.0 0.0.0.0 192.168.1.1” for deleting this item value from the setting file is generated.

  Further, as shown in FIG. 15, the current setting file is a content in which some item values of the restoration target setting file are changed (here, “ip route 192.168.5.0 255.255.255.0 192.168.0.8” is changed). If it is changed to “ip route 192.168.3.0 255.255.255.0 192.168.0.8”), it is determined as “change”, so the process proceeds to step S75, and the changed (current) item value is deleted from the setting file. The command "no iproute 192.168.3.0 255.255.255.0 192.168.0.8" is generated. In step S76, a command “iproute 192.168.5.0 255.255.255.0 192.168.0.8” for adding the item value before the change to the setting file is generated.

  Returning to FIG. 11, in step S67, it is determined whether or not command generation has been completed for all items, and until completion, the process returns to step S64 and the above-described processes are repeated. In step S68, the command generated in step S66 is transmitted to the corresponding network device. Each network device executes the received command and switches back “running-config”. In step S69, a request to copy “running-config” to “startup-config” is transmitted to the network device. In response to this request, each network device copies the contents of “running-config” to “startup-config”.

  Next, a method for determining the switchback order of network devices (here, routers or switches) will be described with reference to the flowcharts of FIGS. 16 and 17. In this embodiment, the operation server 3 executes a traceroute for route investigation as a background process, transmits an ICMP echo request message to each router, and reaches each router based on the ICMP Time Exceeded error message that is the response. The network settings are restored in order from the router with the largest number of hops.

  FIG. 17 is a flowchart showing the procedure of the router switchback order determination method performed by the operation server 3. In step S81, one of the network devices is selected as the current device of interest. In step S82, a traceroute is executed for the current device of interest, and an ICMP echo request message destined for the device of interest is sequentially transmitted while updating the value of the TTL (Time To Live) field.

  Each router on the route that received this ICMP echo request message decrements the value of its TTL field by “1”, and if the result is other than “0”, the message is sent to the next hop based on its own route information. Forward to the destination. If the result of subtracting “1” from the TTL field is “0”, the message is discarded and an ICMP Time Exceeded error message with its own IP address registered in the source IP address field is displayed. A reply is sent to the operation server 3.

  In step S83, it is determined whether or not the traceroute for the current device of interest has been completed based on whether or not the response message from the current device of interest has been received. When the traceroute is completed, the process proceeds to step S84, and the number of hops to the current device of interest is confirmed. In step S85, a pair of the IP address of the current device of interest and the number of hops to the device of interest is stored. In step S86, it is determined whether or not the traceroute has been completed for all the networks. Until the traceroute is completed, the process returns to step S81 and the above-described processes are repeated while changing the target device.

  When the traceroute is completed for all the network devices, the process proceeds to step S87, and the data stored for each network device is sorted in descending order of the number of hops in step S85 to determine the switch back order. That is, the fast switching order is assigned in order from the network device having the largest number of hops from the operation server 3.

  FIG. 18 is a functional block showing a configuration of an embodiment of the operation server 3, and illustration of a configuration unnecessary for the description of the present invention is omitted here.

  The setting file database 301 is storage means for storing a setting file in association with a first identifier (session identifier IDs) representative of the storage timing and a second identifier (actual session identifier IDrs) representative of the new storage timing. is there. The operation history monitoring unit 302 monitors the operation history of each network device, and in step S401, selects a network device having an operation history.

  The storage request detection unit 305 detects a storage request transmitted from the client 1 in step S1. In response to the save request, the setting file acquisition unit 303 acquires a setting file from a network device having an operation history after the previous save timing.

  In step S204, the update presence / absence determination unit 304 acquires, for each network device, the acquired setting file and a registered setting file associated with the first identifier (session identifier IDs) representing the previous storage timing. To determine whether or not there is an update. In step S205, the new storage unit 312 acquires the updated setting file from the network device, and the first identifier (session identifier IDs) with the current time as the storage timing and the second identifier (with the current time as the new storage timing) ( It is associated with the actual session identifier IDrs) and stored in the setting file database 301.

  In step S209, the storage unit 311 copies the already registered setting file of the network device whose setting file has not been updated, and is associated with the first identifier representing the current storage timing and the setting file. The setting identifier is stored in the setting file database 301 in association with the second identifier. The failback request detection unit 306 detects the failback request transmitted from the client 1 in step S3. In step S403, the reversion target specifying unit 307 specifies the network device to be reverted in response to the reversion request including the restoration time. In step S405, the setting file switchback unit 308 switches back the registered setting file associated with the first identifier representing the restoration time to the network device to be switched back.

  In step S403, the reversion target specifying unit 307 determines the second identifier (actual session identifier IDrs) of the already registered setting file associated with the first identifier (session identifier IDs) representing the latest storage timing. A first reading unit 307a that reads a second identifier (actual session identifier IDrs) of a registered setting file that is associated with a first identifier (session identifier IDs) that represents the restoration time. And a comparison unit 307c that compares the read second identifiers, and identifies a network device to be reverted based on the comparison result.

  In step S61 and S62, the setting file switchback unit 308 links the registered setting file linked to the first identifier representing the latest storage timing and the first identifier representing the restoration time. It includes a change analysis unit 308e that compares the registered setting file that has been registered and analyzes change items and change contents.

  The setting file switch-back unit 308 further includes a first command generation unit 308a that generates a command for adding the deleted item to the setting file for the item whose change content is “deleted” in step S73. Regarding the item “added”, the second command generation unit 308b generates a command for deleting the added item from the setting file in step S74, and regarding the item whose change content is “change”, the item after the change is displayed. A command to be deleted from the setting file and a command to add the item before the change to the setting file are transmitted to the third command generating unit 308c that generates the command in steps S75 and S76, respectively, and the commands are transmitted to the network device in step S68. A command transmission unit 308d to be executed.

  In step S82, the message transmission / reception unit 309 sequentially executes trace route for route investigation for each network device (here, a router or a switch), and transmits / receives an ICMP echo request message and an ICMP Time Exceeded error message. In steps S84 to S86, the hop number detection unit 310 detects the hop number to each network device based on the response message returned from each network device. In step S87, the switchback order determination unit 313 determines the switchback order of network devices based on the number of hops to each network device. Based on the switch-back order, the switch-back target specifying unit 307 switches back network settings preferentially from network devices having a large number of hops from itself.

It is the figure which showed the typical assumption environment of the network to which the network setting restoration method which concerns on this invention is applied. It is the figure which expressed typically a mode that the setting file of a network device was linked | related with session identifier IDs and real session identifier IDrs = 1, and was preserve | saved. 3 is a flowchart showing the operation of the operation server 3. It is the flowchart which showed the procedure of the setting file preservation | save process. FIG. 6 is a diagram (part 1) schematically representing a state in which a network device setting file is restored based on session identifier IDs and actual session identifier IDrs = 1. FIG. 6 is a diagram (part 2) schematically representing a state in which a network device setting file is restored based on session identifier IDs and actual session identifier IDrs = 1. It is the flowchart which showed the procedure of the setting file switchback process. It is the sequence flow which showed the procedure of the setting file switchback process. It is the figure which showed an example of the setting file of the router made from Cisco. It is the figure explaining a mode that a wrinkle arises when a setting file is cut back by merge. It is the flowchart which showed the procedure of the 2nd switchback method. It is the flowchart which showed the procedure of command generation. It is the figure (the 1) explaining the content of the command. It is the figure (the 2) explaining the content of the command. FIG. 11 is a diagram (part 3) illustrating the contents of a command. It is a figure explaining the determination method of the switchback order of a router. It is the flowchart which showed the switchback order of a router. It is a functional block of the operation server.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Network, 2 ... Client, 3 ... Operation server, 301 ... Setting file database, 302 ... Operation history monitoring part, 303 ... Setting file acquisition part, 304 ... Update existence determination part, 305 ... Save request detection part, 306 ... Off Return request detection unit, 307 ... Reversion target specifying unit, 308 ... Setting file reversion unit, 309 ... Message transmission / reception unit, 310 ... Hop number detection unit, 311 ... Storage unit, 312 ... New storage unit, 313 ... Reversion order Decision part

Claims (8)

Operates based on its own route information, saves the configuration files of the network devices that make up the network to the operation server in response to the save request, and then stores the registered configuration files specified in the subsequent reversion request for each network In the network setting restoration method that restores the network settings by sequentially switching back to the device,
The operation server is
Procedure to detect the number of hops to each network device,
And a procedure for determining a switch back order so that the network settings are switched back preferentially from a network device having a large number of hops. The procedure for detecting the number of hops to each network device is as follows:
The operation server
A procedure for sequentially sending route survey messages to each network device;
A procedure for receiving a response message for each route survey message sent;
The network setting restoration method according to claim 1, further comprising: determining a hop count to each network device based on the received response message.   The network setting restoration method according to claim 1 or 2, wherein an early switchback order is assigned in order from a network device having a large number of hops from the operation server.   4. The network setting restoring method according to claim 1, wherein the network device is a router or a switch. Operates based on its own route information, saves the configuration files of the network devices that make up the network to the operation server in response to the save request, and then stores the registered configuration files specified in the subsequent reversion request for each network In a network settings restoration system that restores network settings by sequentially switching back to the device,
The operation server is
Means for detecting the number of hops to each network device;
A network setting restoration system, comprising: means for determining a switching order so that network settings are switched back preferentially from a network device having a large number of hops. Means for detecting the number of hops to each network device,
Means for sequentially sending a route investigation message to each network device;
Means for receiving a response message for each route survey message transmitted;
6. The network setting restoration system according to claim 5, further comprising means for determining the number of hops to each network device based on the received response message.   The network setting restoration system according to claim 5 or 6, wherein an early switchback order is assigned in order from a network device having a large number of hops from the operation server.   8. The network setting restoration system according to claim 5, wherein the network device is a router or a switch.

Images