After an ISSU reboot or reboot upgrade is performed, you can roll back the running software images
only to the status before any activate or deactivate operations were performed.
After a commit operation is performed, you cannot perform a rollback.
For a rollback to take effect after a reboot, you must perform a commit operation to update the main
startup software image list.
The device supports a maximum of 50 rollback points. The earliest rollback point is deleted if this
limit has been reached when a rollback point is created.
Patch images do not support rollback.
Examples
# Roll back the software to rollback point 1.
<Sysname>install rollback to 1
This operation might take several minutes, please wait...Done.
# Roll back the software to the original software versions and observe the change made by the
rollback.
<Sysname> display install active
Active packages on slot 1:
flash:/boot-a0201.bin
flash:/system-a0201.bin
flash:/ssh-feature-a0201.bin
<Sysname> display install rollback
Install rollback information 1 on slot 1:
Updating from no package
to flash:/ssh-feature-a0201.bin.
The output shows that currently three image files are active but only two of them are confirmed. The
image file flash:/ssh-feature-a0201.bin is not confirmed yet.
<Sysname> install rollback to original
This operation might take several minutes, please wait...Done.
<Sysname> display install active
Active packages on slot 1:
flash:/boot-a0201.bin
flash:/system-a0201.bin
<Sysname> display install committed
Committed packages on slot 1:
flash:/boot-a0201.bin
flash:/system-a0201.bin
The output shows the SSH feature has been rolled back to the original software version. The image
file flash:/ssh-feature-a0201.bin has been removed.
Related commands
display install rollback
install verify
Use install verify to verify the software change commit status, image integrity, and image
consistency.
Syntax
install verify
249