C H A P T E R
9
Configuration Replace and Configuration
Rollback
•
Prerequisites for Configuration Replace and Configuration Rollback, on page 181
•
Restrictions for Configuration Replace and Configuration Rollback, on page 182
•
Information About Configuration Replace and Configuration Rollback, on page 182
•
How to Use Configuration Replace and Configuration Rollback, on page 185
•
Configuration Examples for Configuration Replace and Configuration Rollback, on page 191
•
Feature History for Configuration Replace and Configuration Rollback, on page 193
Prerequisites for Configuration Replace and Configuration
Rollback
The format of the configuration files used as input by the Configuration Replace and Configuration Rollback
feature must comply with standard Cisco software configuration file indentation rules as follows:
• Start all commands on a new line with no indentation, unless the command is within a configuration
submode.
• Indent commands within a first-level configuration submode one space.
• Indent commands within a second-level configuration submode two spaces.
• Indent commands within subsequent submodes accordingly.
These indentation rules describe how the software creates configuration files for such commands as
show
running-config
or
copy running-config destination-url
. Any configuration file generated on a Cisco device
complies with these rules.
Free memory larger than the combined size of the two configuration files (the current running configuration
and the saved replacement configuration) is required.
System Management Configuration Guide, Cisco IOS XE Gibraltar 16.10.x (Catalyst 9200 Switches)
181