Cisco Nexus 7000 Series Configuration Manual page 178

Guidelines and Limitations for Rollbacks
• Beginning in Cisco NX-OS Release 4.2(1), you can start a checkpoint filename with the word auto.
• Beginning in Cisco NX-OS Release 4.2(1), you can name a checkpoint file summary or any abbreviation
of the word summary.
• Only one user can perform a checkpoint, rollback, or copy the running configuration to the startup
configuration at the same time.
• After the system executes the write erase or reload command, checkpoints are deleted. You can use
the clear checkpoint database command to clear out all checkpoint files.
• A rollback fails for NetFlow if during a rollback, you try to modify a record that is programmed in the
hardware.
• Although a rollback is not supported for checkpoints across software versions, users can perform a
rollback at their own discretion and can use the best-effort mode to recover from errors.
• 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 virtual device context (VDC).
• Checkpoints created using the checkpoint and checkpoint checkpoint_name commands are present
upon a switchover.
• Checkpoints created in the default VDC are present upon reload unless a write-erase command is issued
before a reload.
• Checkpoints created in nondefault VDCs are present upon reload only if a copy running-config
startup-config command is issued in the applicable VDC and the default VDC.
• A rollback to files on bootflash is supported only on files created using the checkpoint checkpoint_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.
• Rollback is not supported in the storage VDC.
• Rollback is not supported in the Admin virtual device context (VDC) feature.
• Configure the terminal dont-ask command before executing the rollback command to a checkpoint.
In a rollback patch, the rollback process does not pause for user interaction and takes the default values
for interactive commands. Configuring the terminal dont-ask command before executing the rollback
command helps in resolving this issue.
• Rollback is not supported in the context of auto configurations. Checkpoints do not store auto
configurations. Therefore, after a rollback is performed, the corresponding auto configurations will not
be present.
• When you perform rollback, if the patch contains the reload command for the corresponding module
along with the configuration commands for that module, rollback fails. This is because the rollback
action does not wait for the module to come online; it starts executing the configuration commands on
the module even as the reload process is in progress. To resolve this issue, manually execute the
configuration commands for the module after the module is online.
Examples:
Cisco Nexus 7000 Series NX-OS System Management Configuration Guide
150
• A rollback fails when you execute the bfd hw-offload-module command or the no form of this
command. In this instance, failure is because rollback cannot execute these commands when the
Configuring Rollback