Nokia 7210 Configuration Manual page 48

CLI Usage
48
• 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.
• 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 configuration 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, it will be re-started as part of the rollback revert after the
configuration changes have been applied (just as if the operator had typed
no shutdown for the continuous SAA job). Non-continuous SAA jobs that
were modified by the rollback need to be manually restarted if they need to
be run again.
- If max-nbr-mac-addr is reduced as part of the revert but the number of
MAC addresses in the forwarding database is greater than the maximum
number of MAC addresses, 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 to proceed with the rollback.
- 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.
Use subject to Terms available at: www.nokia.com
7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System
© 2021 Nokia.
Configuration Guide
3HE 17358 AAAB TQZZA