Rolling back configuration
To avoid a rollback failure, follow these guidelines:
Make sure the replacement configuration file is created by using the configuration archive feature or the save command on the local device.
If the configuration file is not created on the local device, make sure the command lines in the configuration file are fully compatible with the local device.
The replacement configuration file is not encrypted.
To perform a configuration rollback:
Step | Command | Remarks |
---|---|---|
1. Enter system view. | system-view | N/A |
2. Roll the running configuration back to the configuration defined by a configuration file. | configuration replace file filename | The specified configuration file must not be encrypted. |
The configuration rollback feature might fail to reconfigure some commands in the running configuration for one of the following reasons:
A command cannot be undone because prefixing the undo keyword to the command does not result in a valid undo command. For example, if the undo form designed for the A [B] C command is undo A C, the configuration rollback feature cannot undo the A B C command. This is because the system does not recognize the undo A B C command.
A command (for example, a hardware-dependent command) cannot be deleted, overwritten, or undone due to system restrictions.
The commands in different views are dependent on each other.
Commands or command settings that the device does not support cannot be added to the running configuration.