CLI Usage
7450 ESS OS Basic System Configuration Guide Page 57
• Rollback is supported even after an admin reboot is performed (or changes the primary
config in the bof is changed and an admin reboot is performed). Admin reboot does not
“break the chain” for rollback.
• The Configuration Rollback feature is incompatible with the use of Time Of Day (ToD)
policies and functionality. Rollback save and rollback revert operations are blocked if any
ToD policies are active (for example, assigned to objects such as a SAP).
• Lawful Intercept configuration under the config>li branch is not affected by a rollback or
rescue. LI configuration is not saved in the rollback checkpoint or rescue file, and a
rollback revert does not touch any config under the config>li branch.
• Any configuration or state change performed under the debug branch of CLI is not saved
in the rollback checkpoint file nor impacted by a rollback.
• Rollbacks to a checkpoint created in a more recent release is not supported (for example,
node running in 9.0r5 can not rollback to a checkpoint created in 9.0r7).
• The following list captures some side effects and specific behaviors of a Rollback revert.
Some of these side effects are not related purely to configuration (that is, in the CLI config
branch) and may have interactions with tools commands, RADIUS, etc.
SAA jobs that are running when a rollback revert is initiated, and need configuration
changes due to the rollback, will be stopped. If the SAA job is a continuous type then
it will be re-started as part of the rollback revert after the config changes have been
applied (just as if the operator had typed “no shutdown” for the continuos SAA job).
Non-continuous SAA jobs that were modified by the rollback would need to be
manually restarted if they need to be run again.
If max-nbr-mac-addr is reduced as part of the revert and the number of mac
addresses in the forwarding database is greater than the max-nbr-mac-addr, then the
rollback is aborted (before any actions are taken) and an informative error message is
provided. The operator must take actions to remove the mac addresses if they wish to
proceed with the rollback.
If active subscribers and/or subscriber hosts and/or DHCP lease state are present in the
system then some associated configuration changes may be blocked (just as those
same changes would be blocked if an operator tried to make them via CLI – e.g. trying
to delete an sla-profile being used by active subscriber hosts, or trying to change a nat-
policy in a sub-profile). If certain configuration changes associated with the hosts or
lease states are required as part of the rollback but those changes are blocked, then for
each blocked configuration item a warning will be printed, that particular
configuration item will not be changed and the rollback will continue.
If a force-switchover command (for example, tools perform service id 1 endpoint "x"
force-switchover spoke-sdp-fec 1) has been applied to a spoke-sdp-fec of a dynamic
multi-segment pseudo wire, and a rollback revert needs to change the admin state of
the spoke-sdp-fec (for example, to modify spoke-sdp-fec parameters that may be
To Next Page
Loading...
