Alcatel-Lucent 7210 SAS M Configuration Manual page 51

•
7210 SAS M, T, X, R6 Basic System Configuration Guide
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.
−
Changes to SAP egress policy requires port shutdown and no shutdown. This is
done automatically by the software when it detects a change.
−
Changes to num-qos-resources in the SAP ingress policy, results in deletion and
creation of all the SAPs. This is done to ensure that the configuration can be
successfully recreated using the sdx file.
−
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>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
revert command. Some examples of card and mda commands that may cause a prompt
are:
−
configure>card>card-type
−
configure>card>mda
−
configure>card>mda>mda-type
CLI Usage
Page 51