Creating MD-CLI configuration from the classic CLI procedure

Procedure

Ensure mixed management interface configuration mode is enabled and persistent (from the classic CLI engine) and log out of the current session.
Example
```
*A:node-2# /configure system management-interface configuration-mode mixed

Applying Changes to Model-Driven Database ... OK
*A:node-2# logout
```
Log in to a new CLI session.
Example
```
Login: admin
Password:
```
(Optional) Save the configuration in the classic CLI format. The saved configuration can be used to return to a known baseline configuration.
Example
```
*A:node-2# admin save
Writing configuration to cf3:config.cfg
Saving configuration ... OK
Completed.
```
Switch to the MD-CLI engine and capture the configuration in the MD-CLI format to a file that can be used for later comparison. Because the admin save command is not supported in mixed configuration mode, use the admin show configuration command and redirect the output to the file.
Example
```
*A:node-2# //
INFO: CLI #2052: Switching to the MD-CLI engine

[]
A:admin@node-2# admin show configuration > cf3:md-config.cfg
```

Return to the classic CLI engine and enter the configuration to be converted.

Example

[]
A:admin@node-2# //
INFO: CLI #2051: Switching to the classic CLI engine
A:node-2# configure system name new-node-7

Switch to the MD-CLI engine. Compare the running configuration to the saved configuration file to display the additional configuration in the MD-CLI format.

Example

*A:new-node-7# //
INFO: CLI #2052: Switching to the MD-CLI engine

[]
A:admin@new-node-7# configure global
INFO: CLI #2054: Entering global configuration mode

[gl:configure]
A:admin@new-node-7# compare from url cf3:md-config.cfg
    system {
-       name "node-2"
+       name "new-node-7"
    }

Copy and paste the differences in the MD-CLI engine on the target router or redirect to a file for later use. See Copying configuration elements and Using the file redirect option for more information.