Restoration of archived configurations for a network device

• US 7,523,097 B1
• Filed: 01/13/2004
• Issued: 04/21/2009
• Est. Priority Date: 01/13/2004
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Wilson, Reid E., Shafer, Philip A.
• Primary Examiner(s): Cottingham; John R.
• Assistant Examiner(s): Badawi; Sherief
• Application Number:
  US10/756,960
• Time in Patent Office: 1,925 Days
• Field of Search: 707/8, 707/3, 707/10, 707/100, 370/351, 709/220, 709/213, 714/726
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/0863 by rolling back to previous configuration versions
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database

Abstract

Techniques are described for reliable restoration of archived configuration. For example, a device, such as a router, comprises a first memory to store operational configuration data and a second memory to store candidate configuration data. The candidate configuration data represents a working copy of the operational configuration data. The device further includes a control unit to lock the candidate configuration data, load archived configuration data to replace the locked candidate configuration data and commit the candidate configuration data to restore the archived configuration data as the operational configuration data of the device. In locking the candidate configuration, the device ensures reliable restoration of the candidate configuration by helping prevent the device from becoming both unreachable and inoperable.

Claims

1. A method comprising:

establishing, with a network device, a communication session with a client;

receiving, with the network device, a lock command from the client via the communication session;

locking candidate configuration data in response to the lock command from the client to grant an archive system exclusive access to the candidate configuration data of the network device and lock the candidate configuration data so that no other clients can edit the candidate configuration data, wherein the candidate configuration data represents an editable working copy of current operational configuration data of the network device;

after locking the candidate configuration data, receiving a load command from the client and, in response to the load command, loading, from the archive system, archived configuration, data that represents previous operational configuration data of the network device to replace the locked candidate configuration data;

in response to a first commit command from the client, temporarily committing the candidate configuration data to temporarily restore the archived configuration data as the operational configuration data of the network device;

upon temporarily committing the candidate configuration data, enabling a timer within the network device;

in response to receiving a second commit command from the client prior to the timer exceeding a pre-set time limit, permanently committing the candidate configuration data to restore the archived configuration data as the operational configuration data of the network device;

upon expiration of the timer without receiving the second commit command with the network device, executing a first rollback to undo any changes to the operational data from the archived configuration data as loaded into the candidate configuration data; and

upon failure of the communication session prior to receiving the second commit command, executing a second rollback to undo any changes made to the candidate configuration data by the archived configuration data to ensure the candidate configuration is synchronous with the operational configuration of the network device.

2. The method of claim 1, wherein the load command comprises an override attribute;

and wherein loading the archived configuration data in response to receiving the load, command includes discarding the entire candidate configuration and replacing the discarded, candidate configuration data with the archived configuration data in response to the override attribute of the load command.

3. The method of claim 1, further comprising alter successfully permanently committing the candidate configuration data in response to receiving the second commit command prior to the timer exceeding the pre-set limit, unlocking the candidate configuration data.

4. The method of claim 3, wherein unlocking the candidate configuration data occurs in response to receiving an unlock command after receiving the second commit command.

5. The method of claim 4, wherein locking candidate configuration data permits only a single client to edit the candidate configuration data and unlocking the candidate configuration data allows one or more clients to simultaneously edit the candidate configuration data.

6. The method of claim 1, wherein committing the candidate configuration comprises:

generating a configuration patch that lists any differences between the candidate configuration data and the operational configuration data; and

applying the configuration patch to the operational configuration data to update the operational configuration data in accordance with the differences.

7. The method of claim 6, wherein generating a configuration patch comprises:

creating a temporary copy of the candidate configuration data;

merging the operational configuration data into the temporary copy to generate a list of updated configuration objects; and

generating the configuration patch to list the updated configuration objects.

8. A device comprising:

memory to store current operational configuration data and candidate configuration data, wherein the candidate configuration data represents an editable working copy of the current operational configuration data;

a timer;

a control unit;

a control unit configured to establish a communication session with a client and present a user interface to the client for modifying the operational configuration data via the communication session, the user interface configured to support a first commit command that requires explicit confirmation by a second commit command from the client within a time; and

wherein, upon receiving a lock command from the client, the control unit is configured to lock the candidate configuration data and grant an archive system exclusive access to the, candidate configuration data, wherein the candidate configuration data represents an editable working copy of current operational configuration data;

wherein, upon receiving a load command from the client, the control unit is configured to load from the archive system archived configuration data that represents previous operational configuration data to replace the locked candidate configuration data;

wherein, in response to the first commit command from the client, the control unit is configured to temporarily commit the candidate configuration data to temporarily restore the archived configuration data as the operational configuration data and, upon temporarily committing the candidate configuration data, enables the timer;

wherein, in response to receiving the second commit command from the client prior to the timer exceeding a pre-set time limit, the control unit is configured to permanently commit the candidate configuration data to restore the archived configuration data as the operational configuration data;

wherein, upon expiration of the timer without receiving the second commit command from the client, the control unit is configured to execute a first rollback to undo any changes to the operational data from the archived configuration data as loaded into the candidate configuration data; and

wherein, upon failure of the communication session prior to receiving the second commit command, is configured to execute a second rollback to undo any changes made to the candidate configuration data by the archived configuration data to ensure the candidate configuration is synchronous with the operational configuration of the network device.

9. The device of claim 8, wherein the load command comprises an override attribute;

and wherein the control unit discards the entire candidate configuration and replace the discarded candidate configuration data with the archived configuration data when the override attribute is enabled.

10. The device of claim 8, further comprising the control unit, configured to unlock the candidate configuration data after successfully permanently committing the candidate configuration data in response to receiving the second commit command prior to the timer exceeding the pre-set limit.

11. The device of claim 10, wherein the control unit unlocks the candidate configuration data occurs in response to receiving an unlock command after receiving the second commit command.

12. The device of claim 10, wherein locking candidate configuration data permits only a single client to edit the candidate configuration data and unlocking the candidate configuration data allows one or more clients to simultaneously edit the candidate configuration data.

13. The device of claim 8, wherein committing the candidate configuration comprises the control unit to generate a configuration patch that lists any differences between the candidate configuration data and the operational configuration data, and apply the configuration patch to the operational configuration data to update the operational configuration data in accordance with the differences.

14. The device of claim 13, wherein generating a configuration patch comprises the control unit to create a temporary copy of the candidate configuration data, merge the operational configuration data into the temporary copy to generate a list of updated, configuration objects, and generate the configuration patch to list the updated configuration objects.

15. An archive system comprising:

a memory to store archived configuration data that represents previous operational configuration data of a network device; and

a computing device configured to establish a communication session from the archive system to a network device to be configured, wherein the computing device of the archive system is configured to issue a lock command from the archive system to the network device via the communication session to request exclusive access to the candidate configuration data of the network device and lock the candidate configuration so that no other clients can edit the candidate configuration data, wherein the candidate configuration data represents an editable working copy of current operational configuration data of the network device;

wherein the computing device is configured to issue a load command to the network device to load the archived configuration data that represents previous operational configuration data of the network device to replace the locked candidate configuration data; and

wherein the computing device is configured to issue a first commit command to the network device to commit the candidate configuration data to temporarily restore the archived configuration data as the operational configuration data of the network device for only a pre-set time limit;

wherein the computing device is configured to, after issuing the first commit command and before expiration of the pre-set time limit, integrity testing the network device with the client to determine whether the network device is rendered inoperable by the restored archived configuration; and

wherein the computing device is configured to, when the network device is operable, issue a second commit command within the pre-set time limit to permanently commit the candidate configuration data as the operational configuration data of the network device.

16. The archive system of claim 15, wherein the computing device of the archive system, is configured to perform integrity tests on the network device after issuing the first commit command to assess a state of one or more devices, and selectively issue the second commit command commit command based on the assessed state of the one or more devices.