The Rollback feature allows you to take a snapshot, or user checkpoint, of the Cisco NX-OS configuration and then reapply that configuration to your switch at any point without having to reload the switch. A rollback allows any authorized administrator to apply this checkpoint configuration without requiring expert knowledge of the features configured in the checkpoint.
You can create a checkpoint copy of the current running configuration at any time. Cisco NX-OS saves this checkpoint as an ASCII file which you can use to roll back the running configuration to the checkpoint configuration at a future time. You can create multiple checkpoints to save different versions of your running configuration.
When you roll back the running configuration, you can trigger an atomic rollback. An atomic rollback implements a rollback only if no errors occur.
Guidelines and Limitations for Rollback
Rollback has the following configuration guidelines and limitations:
You can create up to ten checkpoint copies.
You cannot apply the checkpoint file of one switch into another switch.
Your checkpoint file names must be 75 characters or less.
You cannot start a checkpoint filename with the word system.
You can start a checkpoint filename with the word auto.
You can name a checkpoint file summary or any abbreviation of the word summary.
When FCoE is enabled, the checkpoint and configuration rollback functionality are disabled.
Only one user can perform a checkpoint, rollback, or copy the running configuration to the startup configuration at the same time.
After you enter the write erase and reload command, checkpoints are deleted. You can use the clear checkpoint database command to clear out all checkpoint files.
When checkpoints are created on bootflash, differences with the running-system configuration cannot be performed before performing the rollback, and the system reports “No Changes.”
Checkpoints are local to a switch.
Checkpoints that are created using the checkpoint and checkpointcheckpoint_name commands are present upon a switchover for all switches.
A rollback to files on bootflash is supported only on files that are created using the checkpointcheckpoint_name command and not on any other type of ASCII file.
Checkpoint names must be unique. You cannot overwrite previously saved checkpoints with the same name.
The Cisco NX-OS commands may differ from the Cisco IOS commands.
Creating a Checkpoint
You can create up to ten checkpoints of your configuration per switch.
Creates a checkpoint of the running configuration to either a user checkpoint name or a file. The checkpoint name can be any alphanumeric string up to 80 characters but cannot contain spaces. If you do not provide a name, Cisco NX-OS sets the checkpoint name to user-checkpoint-<number> where number is from 1 to 10.
The description can contain up to 80 alphanumeric characters, including spaces.
switch# no checkpointcp-name
switch# no checkpoint stable
You can use the no form of the checkpoint command to remove a checkpoint name.
Use the delete command to remove a checkpoint file.
switch# show checkpointcp-name [ all ]
switch# show checkpoint stable
(Optional) Displays the contents of the checkpoint name.
Implementing a Rollback
You can implement a rollback to a checkpoint name or file. Before you implement a rollback, you can view the differences between source and destination checkpoints that reference current or saved configurations.
If you make a configuration change during an atomic rollback, the rollback will fail.