Nokia 7210 Configuration Manual page 49

7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System
Configuration Guide
3HE 17358 AAAB TQZZA
• 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 control-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 rollback
processing may have been in the middle of tearing things down or rebuilding
configurations. A strong warning is issued in this case to indicate that the
operator must examine the configuration and potentially issue another rollback
revert to return to a known (and coherent) configuration.
• A high availability CPM switchover during a rollback revert will cause the
rollback operation to abort. The newly active CPM will have an indeterminate
configuration. When an HA switchover occurs during a rollback (or within a few
seconds of a rollback completing), the operator is advised to repeat the rollback
revert operation to the same checkpoint.
Use subject to Terms available at: www.nokia.com
© 2021 Nokia.
CLI Usage
49