Implementing A Rollback - Cisco Nexus 7000 Series Configuration Manual

Implementing a Rollback

Step 2
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
Cisco Nexus 7000 Series NX-OS System Management Configuration Guide
152
Command or Action
show checkpoint cp-name [all]
Example:
switch# show checkpoint
stable
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 | best-effort |
stop-at-first-failure]
Example:
switch# rollback running-config
checkpoint stable
Purpose
(Optional) Displays the contents of the checkpoint name.
Purpose
Displays the differences between the source and
destination checkpoint selections.
Creates a rollback to the specified checkpoint name
or file. You can implement the following rollback
types:
• atomic—Implement a rollback only if no
errors occur.
• best-effort—Implement a rollback and skip
any errors.
• stop-at-first-failure—Implement a rollback
that stops if an error occurs.
The default is atomic.
This example shows how to implement a rollback
to a user checkpoint name.
Configuring Rollback