Cisco Nexus 3548 series - Implementing a Rollback; Verifying the Rollback Configuration

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.
Note
Procedure
PurposeCommand or Action
Displays the differences between the source and
destination checkpoint selections.
show diff rollback-patch {checkpoint
src-cp-name | running-config | startup-config
| file source-file} {checkpoint dest-cp-name |
running-config | startup-config | file dest-file}
Step 1
Example:
switch# show diff rollback-patch
checkpoint stable
running-config
Creates an atomic rollback to the specified
checkpoint name or file if no errors occur.
rollback running-config {checkpoint cp-name
| file cp-file} atomic
Example:
Step 2
switch# rollback running-config
checkpoint stable
Example
The following example shows how to create a checkpoint file and then implement an atomic rollback
to a user checkpoint name:
switch# checkpoint stable
switch# rollback running-config checkpoint stable atomic
Verifying the Rollback Configuration
Use the following commands to verify the rollback configuration:
PurposeCommand
Displays the contents of the checkpoint name.
show checkpoint name [ all]
Displays the contents of all checkpoints in the current
switch. You can limit the displayed checkpoints to user
or system-generated checkpoints.
show checkpoint all [user | system]
Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x
199
Configuring Rollback
Implementing a Rollback