Implementing A Rollback; Verifying The Rollback Configuration - Cisco Nexus 3548 Configuration Manual

Configuring Rollback

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
Step 1
Step 2
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:
Command
show checkpoint name [ all]
show checkpoint all [user | system]
Command or Action
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}
Example:
switch# show diff rollback-patch checkpoint
stable
running-config
rollback running-config {checkpoint cp-name | file
cp-file} atomic
Example:
switch# rollback running-config checkpoint stable
Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 6.x
Purpose
Displays the differences between the
source and destination checkpoint
selections.
Creates an atomic rollback to the
specified checkpoint name or file if no
errors occur.
Purpose
Displays the contents of the checkpoint name.
Displays the contents of all checkpoints in the current
switch. You can limit the displayed checkpoints to user
or system-generated checkpoints.
Implementing a Rollback
111