EasyManua.ls Logo

Nokia 7210 SAS-Mxp - Page 43

Nokia 7210 SAS-Mxp
736 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
CLI usage
Options Similar to Description
\s [ \t\n\r\f\v] blank characters
2.7.8 Redirection
SR OS supports redirection (‟>”), which allows the operator to store the output of a CLI command as a
local or remote file. Redirection of output can be used to automatically store results of commands in files
(both local and remote).
Example
‛ping <customer_ip> > cf3cf1:/ping/result.txt’
‛ping <customer_ip> > ftp://test@ftp.nokia.com/ping/result.txt’
In some cases only part of the output might be applicable. The pipe/match and redirection commands can
be combined:
Example
ping 10.0.0.1 | match expression ‟time.\d+” > cf3cf1:/ping/time.txt
This records only the RTT portion (including the word ‟time”).
2.8 Configuration rollback
Note:
This feature is only supported on 7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp.
The configuration rollback feature provides the ability to ‟undo” a configuration and return to previous
router configuration states while minimizing impacts to services.
This feature gives the operator better control and visibility over router configurations and reduces
operational risk while increasing flexibility and providing powerful recovery options.
Configuration rollback is useful in cases where configuration changes are made, but the operator later
decides not to keep the changes (for example, when experimenting or when problems are identified in the
configuration during actual network operation).
The advantages of this feature are as follows:
By not having to reboot the router, changes made to a router configuration have minimal impact on
services provided by the 7210 SAS.
There is no impact to areas of configuration that did not change, but there are some exceptions.
Configuration parameters that changed (or items that a changed configuration has dependencies on) are
first removed (return to default), and the previous values are then restored (can be briefly service impacting
in changed areas).
A history of changes is preserved using checkpoint IDs that allow rollback to different points, as well as
examination of changes made, as shown in the following figure.
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
43
SPACER TEXT

Table of Contents

Related product manuals