CHAPTER 11
Configuration Replace and Configuration
Rollback
• Prerequisites for Configuration Replace and Configuration Rollback, on page 325
• Restrictions for Configuration Replace and Configuration Rollback, on page 326
• Information About Configuration Replace and Configuration Rollback, on page 326
• How to Use Configuration Replace and Configuration Rollback, on page 329
• Configuration Examples for Configuration Replace and Configuration Rollback, on page 335
• Additional References for Configuration Replace and Configuration Rollback, on page 337
• Feature History for Configuration Replace and Configuration Rollback, on page 338
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 Bengaluru 17.4.x (Catalyst 9400 Switches)
325