Configuration Rollback
Page 54 7210 SAS M, T, X, R6 Basic System Configuration Guide
occurs during a rollback (or within a few seconds of a rollback completing), the operator
is advised to repeat the rollback revert operation to the same checkpoint.
• A rollback checkpoint stores the rollback-location and the local/remote-max-checkpoint
values, and as such a rollback revert operation can change those values. If an operator
changes the local/remote-max-checkpoint values it is recommended to delete all the
existing checkpoints (otherwise a subsequent rollback revert could change the max back
to a previous value).
• If a warning prompt (y/n) is displayed when a rollback revert is initiated, it is highly
suggested to respond ‘no’ to the warning prompt the first time, save a rollback checkpoint
before attempting this rollback revert, and then executing the revert again and responding
‘yes’. If the rollback encounters problems then a revert to the saved checkpoint can be
used to go back to the initial configuration state.
Limitations of CLI rollback
The following are the limitations for 7210 SAS-R6:
• Resource profile policy changes cannot be rolled back. Ie if there is a change in resource
policy/parameters between active config and checkpoint rollback will not proceed.
• For Sap ingress qos due to the slice information being available in .sdx file whenever
there is a change in ingress qos policy attached to sap or if there is any additional sap in
checkpoint we tear down and rebuild all the saps. User will be prompted before doing this.
• The saps that has a change in egress qos policy will be shut down and do a no shut after a
delay.
To Next Page
Loading...
