Transitioning between modes

Verify that the system configuration only contains commands that are supported in model-driven interfaces. For more information, see section ‟Unsupported Configuration in MD Interfaces” in the SR OS R22.x.Rx Software Release Notes, part number 3HE 18412 000 x TQZZA.

Update the system configuration to meet the prerequisites described in Prerequisites for using model-driven management interfaces.

Perform a mode change configuration check as follows.

Use the tools perform system management-interface configuration-mode check command to check if the configuration meets the preceding prerequisite reference requirements to change the management interface configuration mode. Incompatible configuration commands are displayed with an error reason if the prerequisite is not met.

Note: The command does not check if the configuration contains commands that are unsupported in model-driven interfaces. For more information, see section ‟Unsupported Configuration in MD Interfaces” in the SR OS R22.x.Rx Software Release Notes, part number 3HE 18412 000 x TQZZA.

Example The following example shows several incompatible configuration commands.

A:node-2# tools perform system management-interface configuration-mode model-
driven check

===============================================================================
Mode Switch Validation Check
===============================================================================
Current Mode       : classic            Desired Mode       : model-driven
Configure          : Errors Detected    LI                 : No Errors
-------------------------------------------------------------------------------
Configuration Validation Errors
-------------------------------------------------------------------------------
1  : MINOR: MGMT_CORE #2004 Incompatible configuration - dynsvc-password
     configured in system security password
2  : MINOR: MGMT_CORE #2004 Incompatible configuration - 'eth-cfm association
     bridge-identifier' reference to service-id exists
3  : MINOR: MGMT_CORE #2004 Incompatible configuration - ca-profile cmpv2 url
     service-id references exist
4  : MINOR: MGMT_CORE #224 Entry does not exist (MD-CLI: configure policy-
     options policy-statement "PEERING_ROUTER_OUT" entry 50 from prefix-list)
-------------------------------------------------------------------------------
Action required: configuration requires updating before mode switch
===============================================================================

Save and back up your configuration. Existing configuration is converted to the MD-CLI format if the mode is changed to model-driven and the saved configuration file is in MD-CLI format.

Change the configuration mode to mixed or model-driven as follows.

Note:

Depending on the size of the system configuration, transitioning from classic mode may take several seconds to several minutes while the model-driven database is populated and synchronized to the current configuration. During the transition period, configuration changes are not allowed and service is not affected.
Transitioning to classic mode is immediate with no impact to services on the router.

If using mixed mode, set the configuration mode to mixed by issuing the following commands:
```
configure system management-interface cli md-cli auto-config-save
configure system management-interface configuration-mode mixed
```
Log out and start a new CLI session to access the MD-CLI engine.
If using model-driven mode, set the configuration mode to model-driven by issuing the following commands:
```
configure system management-interface cli md-cli auto-config-save
configure system management-interface configuration-mode model-driven
```
Log out and start a new CLI session to access the MD-CLI engine. When a new user session begins, the MD-CLI engine is available and the MD-CLI prompt is displayed.

Save the configuration manually.

In mixed mode, issue admin save from the classic CLI.
In model-driven mode, issue admin save from the MD-CLI.

Transitioning between modes

About this task

Procedure