MD-CLI Overview

This guide provides information about the Model-Driven Command Line Interface (MD-CLI).

This guide is organized into functional sections and provides concepts and descriptions of the MD-CLI environment, the configuration workflow, and the syntax and command usage within the MD-CLI. It also describes how the MD-CLI interacts with the classic CLI to perform non-configuration operations.

For a list of unsupported features by platform and chassis, see the SR OS R21.x.Rx Software Release Notes, part number 3HE 17177 000x TQZZA.

Command outputs shown in this guide are examples only; actual outputs may differ depending on supported functionality and user configuration.

Note: This guide generically covers Release 21.x.Rx content and may contain some content that will be released in later maintenance loads. See the SR OS R21.x.Rx Software Release Notes, part number 3HE 17177 000x TQZZA, for information about features supported in each load of the Release 21.x.Rx software.

Note: Command outputs shown in this guide are examples only; actual outputs may differ depending on supported functionality and user configuration.

Using the MD-CLI

All references to the term ‛CLI’ in the SR OS user documentation generally refer to the classic CLI. The classic CLI is the CLI that has been supported in SR OS from the initial introduction of SR OS.

The MD-CLI is a management interface that can be used to manage Nokia SR OS routers. Some of the benefits of the MD-CLI include:

follows the model-driven networking strategy, based on the same YANG models for a structured configuration and state. Consistency is maintained between the MD-CLI, NETCONF, and the gRPC model-driven interfaces.
uses the transactional configuration method which uses a candidate configuration to hold the current configuration changes before they are applied to the running configuration, and avoids configuration ordering requirements
provides multiuser candidate configuration modes (global, exclusive, private, and read-only) that control access to the configuration, allowing a user exclusive access to the configuration such that no other configuration changes can be made
allows the use of configuration groups with flexible templates that simplify the configuration process by applying the template instead of repeating the same configuration
provides MD-CLI commands to simplify integration with automation, such as displaying configuration and state in a structured format (JSON or XML) and displaying contexts in an XPath format

For more information about NETCONF and gRPC, see the 7450 ESS, 7750 SR, 7950 XRS, and VSR System Management Guide.

Table 1. Command Syntax Symbols Used in this Guide
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)