1. MD-CLI Overview

This guide provides a comparison of the Nokia SR OS Model-Driven Command Line Interface (MD-CLI) to those used by Junos OS and IOS XR.

For more information about the MD-CLI, see the following resources:

  1. SR OS Release Notes for your current release
  2. MD-CLI User Guide
  3. MD-CLI Command Reference Guide

Table 1 describes command syntax symbols used in this guide.

Table 1:  Command Syntax Symbols  

Symbol

Description

|

A vertical bar represents an OR, indicating that only one of the parameters in the brackets or parentheses can be selected.

( )

Parentheses indicate that one of the parameters must be selected.

[ ]

Brackets indicate optional parameters.

Bold

Commands in bold indicate commands and keywords.

Italic

Commands in italics indicate that you must enter text based on the parameter.

In the following examples, location and graceful-shutdown are command names. For the location command, keyword must be one of the keywords cf1, cf2, or cf3. For the graceful-shutdown command, boolean must be one of the keywords true or false, although explicitly using the keyword true is optional.

location keyword

keyword - (cf1 | cf2 | cf3)

graceful-shutdown boolean

boolean - ([true] | false)

1.1. Enabling the SR OS MD-CLI

Perform the following procedure to enable the MD-CLI from the classic CLI.

  1. Back up your configuration. Any existing configuration will be converted to the MD-CLI format.
  2. Enable the MD-CLI and model-driven mode, using these commands in this order:
    CLI Syntax:
    configure system management-interface cli md-cli auto-config-save
    configure system management-interface configuration-mode model-driven
  3. Log out of the CLI.
  4. Log back in to the CLI. The MD-CLI engine is now active.

1.2. Disabling the SR OS MD-CLI

Perform the following procedure to return to classic CLI mode while preserving the current router configuration.

  1. Disable the MD-CLI and model-driven mode in the MD-CLI, using these commands in this order:
    CLI Syntax:
    configure exclusive
    system management-interface configuration-mode classic
    commit
  2. Log out of the CLI.
  3. Log back in to the CLI. The classic CLI engine is now active.