7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
CLI usage
– If a force-switchover command has been applied to a spoke SDP FEC of a dynamic multi-segment
pseudowire, 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 dependent on admin state), 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. The following are some examples:
• Configuration changes that require a shutdown and no shutdown to be done by an operator
to take operational effect also need a manual shutdown and no shutdown to be performed by
the operator to take operational effect after a rollback if the rollback changes those configuration
items. Some examples include:
• Changes to autonomous system or confederation values require a BGP shutdown and no
shutdown.
• Changes to VPRN max-routes require a shutdown and no shutdown on the VPRN service.
• Changes to an OSPF or ISIS export limit require a shutdown and no shutdown on OSPF or
ISIS.
• Configuration changes to an MSAP policy that 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, the operator will have to run the eval-msap tools
command.
• Changes to the SAP egress policy require a port shutdown and no shutdown. This is done
automatically by the software when it detects a change.
• Changes to the number of 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 and some changes were
made, but the commit command was never entered) in the following areas will be lost/cleared when
a rollback revert is initiated:
• config>router>policy-options
• config>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 the following:
– config>card>card-type
– config>card>mda
– config>card>mda>mda-type
• Although the use of the Ctrl-C key combination is not recommended during a rollback revert, it is
supported through CLI and SNMP. Interrupting a rollback revert may leave the router in a state that is
not necessarily something between the old active configuration and the rollback checkpoint since the
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
48
SPACER TEXT
To Next Page
Loading...