Alcatel-Lucent 7950 XRS Series, Configuration Manual

Page: 53 / 502

CLI Usage
7950 SR OS Basic System Configuration Guide Page 53
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 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 dependant on admin state), then the rollback revert will automatically remove the
force-switchover and the node will revert to whatever is the best spoke-sdp in the
redundant set.

Rollback impacts the configuration state of the router, and as with normal operator
CLI or SNMP configuration changes, additional actions or steps may need to occur
before certain configuration changes take operational effect. Some examples include:

Configuration changes that require a shutdown and then no-shutdown to be done
by an operator in order to take operational effect also need this manual shut/no-
shut to be performed by the operator in order to take operational effect after a
rollback if the rollback changes those configuration items. Some examples
include:

Changes to Autonomous System or Confederation value require a BGP shut/no-
shut.

Changes to VPRN Max-routes requires a shut/no-shut on the VPRN service.

Changes to OSPF/ISIS export-limit require a shut/no-shut on OSPF/ISIS.

Configuration changes to an msap-policy that normally requires a tools perform
subscriber-mgmt eval-msap command to take operational effect on subscribers
that are already active. Rollback will change the msap-policy configuration, but if
it is required to have the configuration changes applied to the active subscribers
then the operator will have to run the eval-msap tools command.

Any uncommitted changes (that is, the begin command was entered, some changes
made, but the commit command was never entered) in the following areas will be
lost/cleared when a rollback revert is initiated:

configure>application-assurance>group policy

configure>router>policy-options

configure>system>sync-if-timing
• Some card and mda commands require a reboot, remove or rebuild of an entire card or
XMA/MDA. When these commands need to be executed as part of a rollback, the
impacted cards/mdas will be listed in a warning and the operator will be prompted with a
single y/n prompt to decide whether to proceed or not. This prompting will not occur for a
rollback initiated via SNMP, nor if the operator uses the
now keyword with the rollback