SR OS routers can be in different management interface configuration modes, which affects the management interfaces that can be used to configure the router. The following interfaces are available for configuration on SR OS:
classic (default)
Configuration via the classic CLI and SNMP, no model-driven interfaces are supported.
model-driven
Configuration via model-driven interfaces: the MD-CLI, NETCONF, and gRPC/gNMI, read-only access via the classic CLI and SNMP.
mixed
Configuration via the classic CLI and model-driven interfaces: the MD-CLI, NETCONF, and gRPC/gNMI, read-only access via SNMP.
Mixed configuration mode is a transition mode for operators to migrate from classic management interfaces to operating in a full model-driven mode. It allows the use of previous classic CLI scripts or other OSS integration developed by users for configuration, although with some prerequisites (see Prerequisites for using model-driven management interfaces) and some limitations (see Table: Management interface configuration mode). If the Nokia Network Services Platform (NSP) is used to manage the network, use model-driven mode. Do not use mixed mode if the NSP is used.
Use the configure system management-interface configuration-mode command to enable configuration editing by model-driven interfaces.
| Configuration mode | ||||
|---|---|---|---|---|
| Classic | Mixed | Model-driven | ||
Classic Interfaces |
Classic CLI: configuration write |
✓ | ✓ |
|
Classic CLI: configuration read |
✓ | ✓ | ✓ | |
Classic CLI: non-configuration commands |
✓ | ✓ | ✓ | |
SNMP: configuration write |
✓ |
|
|
|
SNMP: non-configuration writes (such as admin reboot) |
✓ |
|
|
|
SNMP: configuration read |
✓ | ✓ | ✓ | |
SNMP: state read |
✓ | ✓ | ✓ | |
SNMP: notifications (traps) |
✓ | ✓ | ✓ | |
Model-driven Interfaces with Nokia YANG Models |
MD-CLI: configuration write and read |
✓ | ✓ | |
MD-CLI: state read |
✓ | ✓ | ✓ | |
NETCONF: configuration write and read |
|
✓ | ✓ | |
NETCONF: state read |
✓ | ✓ | ✓ | |
gNMI Set/Get: configuration write and read |
✓ | ✓ | ||
gNMI Get: state read |
✓ | ✓ | ✓ | |
gNMI Telemetry: configuration read |
|
✓ | ✓ | |
gNMI Telemetry: state read |
✓ | ✓ | ✓ | |
Saved Configuration File Format |
bof |
Classic |
Classic |
Classic |
configure |
Classic |
Classic |
MD |
|
debug |
Classic |
Classic |
MD |
|
li |
Classic |
Classic |
MD |
|
|
Features |
OpenConfig YANG models |
✓ | ||
Commit history |
✓ | |||
Configuration annotations |
✓ | |||
Configuration groups |
✓ | |||
MD-CLI rollback command |
✓ | |||
Classic CLI admin rollback revert command |
✓ | ✓ |
|
|
Explicit defaults1 |
✓ | |||
Explicit non-deletable SPC objects2 |
✓ | |||
Configuration changes accepted immediately after a CPM high-availability switchover3 |
✓ | ✓ | ||
Named route policy entries |
✓ | |||
|
gRPC MD-CLI service for the NISH client |
✓ | ✓ | ||
|
Remote management using the NISH manager |
✓ | ✓ | ||
|
MD-CLI command aliases |
✓ | |||
|
Python 3 for pyexec, EHS, CRON, and MD-CLI command aliases |
✓ | |||
|
The use of the pySROS library from any location |
✓ | |||
| Incremental saved configuration files | ✓ | |||