Allied Telesis AlliedView-UM 2.0 - Manual (Page 116)

18 Rollback
A. Rollbacks and the Audit Trail
Rollbacks are based on the contents of a device’s audit trail. A rollback of an operation can
only be performed if the device’s audit trail contains a record of an operation that can be
used as a reference to rollback to.
For instance, assume that a device definition contains the following audit trail:
# AUDIT
1 Release Upgrade 1
2 Patch Upgrade 1
3 Configuration File Update 1
4 Patch Upgrade 2
5 Release Upgrade 2
6 Release Upgrade 3
In the example above, “Release Upgrade 3” is the last operation performed on the device.
If a rollback operation is performed, AlliedView-UM will try to find the Release Upgrade
operation that was performed prior to Release Upgrade 3. In this case, it is Release
Upgrade 2. During the rollback, AlliedView-UM will re-execute the Release Upgrade 2
operation recorded in the audit trail.
Now, let’s say that a device contains the following audit trail:
# AUDIT
1 Patch Upgrade 1
2 Patch Upgrade 2
3 Configuration File Update 1
4 Patch Upgrade 3
5 Release Upgrade 1
In the example above, “Release Upgrade 1” is the last operation performed on the device.
If a rollback operation is performed, AlliedView-UM will try to find the Release Upgrade
operation that was performed prior to Release Upgrade 1. However, as indicated in the
table above, there are no Release Upgrades to rollback to. In this case, a rollback operation
cannot be performed.
AlliedView™-UM 2.0 USER’S GUIDE Page 116 of 128