Navigating

Progress indicator

[ex:/configure]
A:admin@node-2# compare
...                    # progress indicator displays here as dots 

The delay interval can be configured using the delay command or the indicator can be disabled with the admin-state disable command under the environment progress-indicator context.

Customizing the progress indicator for logged sessions

[/environment progress-indicator]
A:admin@node-2# ?

 admin-state          - Administrative state of the progress indicator
 delay                - Delay before progress indicator is displayed
 type                 - Progress indicator output style

Using the environment more command

[/]
A:admin@node-2# environment more true

[/]
A:admin@node-2# show system security management

===============================================================================
Server Global
===============================================================================
Telnet:
Administrative State         : Enabled
Operational State            : Up
Telnet6:
Administrative State         : Disabled
Operational State            : Down
FTP:
Administrative State         : Disabled
Operational State            : Down
SSH:
Administrative State         : Enabled
Operational State            : Up
NETCONF:
Administrative State         : Disabled
Operational State            : Down
GRPC:
Administrative State         : Disabled
Operational State            : Down

--(more)--(39%)--(lines 1-23/55)--

The pagination setting can be overridden by using | no-more for a single command. As with pagination disabled, the output is displayed completely without any prompts to continue.

Overriding the pagination setting

[/]
A:admin@node-2# show system security management | no-more

[/environment]
A:admin@node-2# console ?

 console

 length               - Number of lines displayed on the screen
 width                - Number of columns displayed on the screen

[/environment message-severity-level]
A:admin@node-2# cli ?

 cli <keyword>
 <keyword> - (warning|info)
 Default   - info

    Message severity threshold for CLI messages

Following are examples of INFO: CLI messages that are suppressed when the setting is changed to warning.

INFO: CLI #2051: Switching to the classic CLI engine
INFO: CLI #2052: Switching to the MD-CLI engine
INFO: CLI #2054: Entering global configuration mode
INFO: CLI #2056: Exiting global configuration mode 
INFO: CLI #2055: Uncommitted changes are present in the candidate configuration
INFO: CLI #2057: Uncommitted changes are kept in the candidate configuration

In the following configuration output, the admin-state for port 1/1/2 with a default configuration is not displayed using the info command. The admin-state is displayed after the environment info-output always-display admin-state command is configured to true.

[ex:/configure port 1/1/2]
A:admin@node-2# info

[ex:/configure port 1/1/2]
A:admin@node-2# /environment info-output always-display admin-state

[ex:/configure port 1/1/2]
A:admin@node-2# info
    admin-state disable

In the following configuration output, entry 113 blocks user ‟tstuser” from modifying the global environment settings. In addition, entry 114 prevents the user from changing the per-session environment settings.

(ro)[/configure system security aaa local-profiles profile "tstuser"]
A:admin@node-2# info
    default-action permit-all
    entry 113 {
        action deny
        match "configure system management-interface cli md-cli environment"
    }
    entry 114 {
        action deny
        match "environment"
    }

[ex:/configure system management-interface cli md-cli environment]
A:tstuser@node-2# prompt timestamp
MINOR: MGMT_CORE #2020: Permission denied

[ex:configure system management-interface cli md-cli environment]
A:tstuser@node-2# /environment
MINOR: MGMT_CORE #2020: Permission denied

[ex:/configure system management-interface cli md-cli environment]
A:tstuser@node-2#

In the following help display example, the containers are eth-cfm, domain, and association. The leafs are apply-groups, apply-groups-exclude, dns, format, level, mac, md-index, and name, while level is also a mandatory element.

[ex:/configure]
A:admin@node-2# eth-cfm ?

 eth-cfm

 apply-groups          - Apply a configuration group at this level
 apply-groups-exclude  - Exclude a configuration group at this level
 default-domain        + Enter the default-domain context
 domain                + Enter the domain list instance

[ex:/configure eth-cfm]
A:admin@node-2# domain ?

 [md-admin-name] <string>
 <string> - <1..64 characters>

    Unique domain name

[ex:/configure eth-cfm]
A:admin@node-2# domain dom-name ?

 domain

 Immutable fields      - level, dns, mac, name, format, md-index

 apply-groups          - Apply a configuration group at this level
 apply-groups-exclude  - Exclude a configuration group at this level
 association           + Enter the association list instance
 level                 ^ Maintenance Domain Level (MD Level)
 md-index              - The index of the Maintenance Domain (MD)

 Mandatory choice: md-name
 dns                  :- Domain name like text string derived from a DNS name
 format               :- Maintenance domain name not to be provided
 mac                  :- Maintenance domain MAC name
 name                 :- Maintenance domain name as an ASCII string

[/]
A:admin@node-2# tree flat
admin
admin clear
admin clear security
admin clear security lockout
admin clear security lockout all
admin clear security lockout user
admin clear security password-history
admin clear security password-history all
admin clear security password-history user
admin disconnect
admin disconnect address
admin disconnect op-table-bypass
admin disconnect session-id
admin disconnect session-type
admin disconnect username
admin reboot
admin reboot [card]
admin reboot now
admin redundancy
admin redundancy force-switchover
admin redundancy force-switchover now
admin redundancy synchronize
admin redundancy synchronize boot-environment
admin redundancy synchronize certificate
admin redundancy synchronize configuration

---snip---

[/]
A:admin@node-2# tree detail
+-- admin
| +-- clear
| | +-- security
| | +-- lockout
| | | +-- all
| | | +-- user <string>
| | +-- password-history
| | +-- all
| | +-- user <string>
| +-- disconnect
| | +-- address <ipv4-address | ipv6-address>
| | +-- op-table-bypass <boolean>
| | +-- session-id <number>
| | +-- session-type <keyword>
| | +-- username <string>
| +-- reboot
| | +-- [card] <keyword>
| | +-- now
| +-- redundancy
| | +-- force-switchover
| | | +-- now
| | +-- synchronize
| | +-- boot-environment
| | +-- certificate
| | +-- configuration

---snip---

The flat and detail options can be combined in any order.

[/]
A:admin@node-2# tree flat detail
admin
admin clear
admin clear security
admin clear security lockout
admin clear security lockout all
admin clear security lockout user <string>
admin clear security password-history
admin clear security password-history all
admin clear security password-history user <string>
admin disconnect
admin disconnect address <ipv4-address | ipv6-address>
admin disconnect op-table-bypass <boolean>
admin disconnect session-id <number>
admin disconnect session-type <keyword>
admin disconnect username <string>
admin reboot
admin reboot [card] <keyword>
admin reboot now
admin redundancy
admin redundancy force-switchover
admin redundancy force-switchover now
admin redundancy synchronize
admin redundancy synchronize boot-environment
admin redundancy synchronize certificate
admin redundancy synchronize configuration

---snip---

In the following example, if either the cir or fir command is entered, the police command is not available. The pir command is available regardless of which choice command is entered.

*[ex:/configure qos sap-ingress "ing-1" queue 1 rate]
A:admin@node-2# ?

 pir                   - Administrative PIR

 Choice: rate-cir-fir-or-police
 cir                  :- Administrative CIR
 fir                   - Administrative FIR
 police               :- Drop the traffic feeding into queue above the PIR rate

*[ex:/configure qos sap-ingress "ing-1" queue 1 rate]
A:admin@node-2# cir max Press Tab

 fir     pir

 delete

Similarly, if the police command is entered, the cir and fir commands are unavailable on the same command prompt line.

*[ex:/configure qos sap-ingress "ing-1" queue 1 rate]
A:admin@node-2# police ?

 police - This element has no values

    Drop the traffic feeding into queue above the PIR rate

 pir                   - Administrative PIR

*[ex:/configure qos sap-ingress "ing-1" queue 1 rate]
A:admin@node-2# police Press Tab

 pir

 delete

In the following example, "interface-name" is the variable parameter name and "int-1" and "system" are configured names.

*[ex:/configure router "Base"]
A:admin@node-2# interface Press Tab 

 <interface-name>
 "int-1"
 "system"

*[ex:/configure router "Base"]
A:admin@node-2# interface

The following example matches on the pattern autonomous-system in the tree detail under the configure router "Base" context, and starts the display with ten lines preceding the pattern match.

[ex:/configure router "Base"]
A:admin@node-2# tree detail | match autonomous-system pre-lines 10
|   |   +-- local-preference <number>
|   |   +-- policy <reference>
|   |   +-- summary-only <boolean>
|   |   +-- tunnel-group <number>
|   +-- apply-groups <reference>
|   +-- apply-groups-exclude <reference>
+-- allow-icmp-redirect <boolean>
+-- allow-icmp6-redirect <boolean>
+-- apply-groups <reference>
+-- apply-groups-exclude <reference>
+-- autonomous-system <number>

---snip---

[ex:/configure router "Base"]
A:admin@node-2# tree flat detail | match seamless-bfd
bfd seamless-bfd
bfd seamless-bfd peer <unicast-ipv4-address | global-unicast-ipv6-address>
bfd seamless-bfd peer <unicast-ipv4-address | global-unicast-ipv6-address> apply-groups <reference>
bfd seamless-bfd peer <unicast-ipv4-address | global-unicast-ipv6-address> apply-groups-exclude <reference>
bfd seamless-bfd peer <unicast-ipv4-address | global-unicast-ipv6-address> discriminator <number>

[ex:/configure router "Base"]
A:admin@node-2# tree flat detail | match seamless-bfd | count
Count: 5 lines

[/]
A:admin@node-2# ping 10.184.216.34 | reverse-dns
PING 10.184.216.34 56 data bytes
  (10.184.216.34) www.example.com
64 bytes from 10.184.216.34: icmp_seq=1 ttl=61 time=82.4ms.
64 bytes from 10.184.216.34: icmp_seq=2 ttl=61 time=82.5ms.
64 bytes from 10.184.216.34: icmp_seq=3 ttl=61 time=82.4ms.
64 bytes from 10.184.216.34: icmp_seq=4 ttl=61 time=82.3ms.
64 bytes from 10.184.216.34: icmp_seq=5 ttl=61 time=82.2ms.

---- 10.184.216.34 PING Statistics ----
  (10.184.216.34) www.example.com
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 82.2ms, avg = 82.4ms, max = 82.5ms, stddev = 0.122ms

[ex:/configure router "Base"]
A:admin@node-2# info detail | match leak-export > ?

 [url] <string>
 <string> - <1..199 characters

    Location to save the output

[ex:/configure router "Base"]
A:admin@node-2# info detail | match leak-export > cf3:leak-export.cfg

Using no match expressions

The first output does not use any match expressions and therefore shows the entire output.

[/]
A:admin@node-2# show port

===============================================================================
Ports on Slot 1
===============================================================================
Port          Admin Link Port    Cfg  Oper LAG/ Port Port Port   C/QS/S/XFP/
Id            State      State   MTU  MTU  Bndl Mode Encp Type   MDIMDX
-------------------------------------------------------------------------------
1/1/1         Down  No   Ghost   8704 8704    - netw null xcme
1/1/2         Up    No   Ghost   1514 1514    - accs null xcme
1/1/3         Up    No   Ghost   1514 1514    - accs null xcme
1/1/4         Up    No   Ghost   1514 1514    - accs null xcme
1/1/5         Up    No   Ghost   1514 1514    - accs null xcme
1/1/6         Down  No   Ghost   8704 8704    - netw null xcme
1/1/7         Down  No   Ghost   8704 8704    - netw null xcme
1/1/8         Down  No   Ghost   8704 8704    - netw null xcme
1/1/9         Down  No   Ghost   8704 8704    - netw null xcme
1/1/10        Down  No   Ghost   8704 8704    - netw null xcme
1/1/11        Down  No   Ghost   8704 8704    - netw null xcme
1/1/12        Down  No   Ghost   8704 8704    - netw null xcme
1/2/1         Up    No   Ghost   8704 8704    - netw null xcme
1/2/2         Up    No   Ghost   1514 1514    - accs null xcme
1/2/3         Up    No   Ghost   1514 1514    - accs null xcme
1/2/4         Down  No   Ghost   8704 8704    - netw null xcme
(more)--(64%)--(lines 1-23/37)--

Using matching list expression

In this matching list expression, a match is any single character in the bracket expression, which in this case is 1, 3, or 5.

[/]
A:admin@node-2# show port | match '1/1/[135]'
1/1/1         Down  No   Ghost   8704 8704    - netw null xcme
1/1/3         Up    No   Ghost   1514 1514    - accs null xcme
1/1/5         Up    No   Ghost   1514 1514    - accs null xcme
1/1/10        Down  No   Ghost   8704 8704    - netw null xcme
1/1/11        Down  No   Ghost   8704 8704    - netw null xcme
1/1/12        Down  No   Ghost   8704 8704    - netw null xcme

Using non-matching list expression

In this non-matching list expression, a match is any single character not in the bracket expression, that is, not 1, 2, or 4.

[/]
A:admin@node-2# show port | match '1/1/[^124]'
1/1/3         Up    No   Ghost   1514 1514    - accs null xcme
1/1/5         Up    No   Ghost   1514 1514    - accs null xcme
1/1/6         Down  No   Ghost   8704 8704    - netw null xcme
1/1/7         Down  No   Ghost   8704 8704    - netw null xcme
1/1/8         Down  No   Ghost   8704 8704    - netw null xcme
1/1/9         Down  No   Ghost   8704 8704    - netw null xcme

Using the range operator

The range operator (-) can be used in a matching or non-matching list expression.

[/]
A:admin@node-2# show port | match '1/1/[3-7]'
1/1/3         Up    No   Ghost   1514 1514    - accs null xcme
1/1/4         Up    No   Ghost   1514 1514    - accs null xcme
1/1/5         Up    No   Ghost   1514 1514    - accs null xcme
1/1/6         Down  No   Ghost   8704 8704    - netw null xcme
1/1/7         Down  No   Ghost   8704 8704    - netw null xcme

[/]
A:admin@node-2# show port | match '1/1/[^3-7]'
1/1/1         Down  No   Ghost   8704 8704    - netw null xcme
1/1/2         Up    No   Ghost   1514 1514    - accs null xcme
1/1/8         Down  No   Ghost   8704 8704    - netw null xcme
1/1/9         Down  No   Ghost   8704 8704    - netw null xcme
1/1/10        Down  No   Ghost   8704 8704    - netw null xcme
1/1/11        Down  No   Ghost   8704 8704    - netw null xcme
1/1/12        Down  No   Ghost   8704 8704    - netw null xcme

Using the alternation operator

The alternation operator (|) can be used with or without a bracket expression to match against two or more alternative expressions.

[/]
A:admin@node-2# show port | match '1/1/[2-5|7-9]'
1/1/2         Up    No   Ghost   1514 1514    - accs null xcme
1/1/3         Up    No   Ghost   1514 1514    - accs null xcme
1/1/4         Up    No   Ghost   1514 1514    - accs null xcme
1/1/5         Up    No   Ghost   1514 1514    - accs null xcme
1/1/7         Down  No   Ghost   8704 8704    - netw null xcme
1/1/8         Down  No   Ghost   8704 8704    - netw null xcme
1/1/9         Down  No   Ghost   8704 8704    - netw null xcme

Using no bracket expression

Without a bracket expression, an exact match is attempted against two or more alternative expressions.

*[ex:/configure card 1]
A:admin@node-2# info | match '10g|100g'
        mda-type imm4-10gb-xp-xfp
        mda-type cx2-100g-cfp

MD-CLI REs match on the output format of an element, as is shown in the configuration. For example, if the value of an element is shown in hexadecimal in info output, a decimal RE does not match the value.

Using anchoring special characters

MD-CLI REs are not implicitly anchored. This complete configuration is used to show how the ^ or $ anchoring special characters can be used to match in the following examples.

*[ex:/configure router "Base" bgp]
A:admin@node-2# info
    group "external" {
    }
    group "internal" {
    }
    neighbor "192.168.10.1" {
        group "external"
        keepalive 30
        peer-as 100
    }
    neighbor "192.168.10.2" {
        group "external"
        peer-as 100
        family {
            ipv4 true
        }
    }

Using the anchor character preceded by four spaces

This example uses the ^ anchor character to match on "group" preceded by four spaces at the beginning of the line.

*[ex:/configure router "Base" bgp]
A:admin@node-2# info | match '^    group' pre-lines 1
    group "external" {
    }
    group "internal" {

Using the anchor character preceded by eight spaces

This example uses the ^ anchor character to match on "group" preceded by eight spaces at the beginning of the line.

*[ex:/configure router "Base" bgp]
A:admin@node-2# info | match '^        group' pre-lines 1
    neighbor "192.168.10.1" {
        group "external"
    neighbor ""192.168.10.2" {
        group "external"

Using the compare command

In the following configuration example using the compare command, the | match option filters out those commands to be deleted (configuration statements beginning with minus (-)) and those to be added (configuration statements beginning with plus (+)).

*[ex:/configure log accounting-policy 5]
A:admin@node-2# /compare
+   admin-state enable
-   collection-interval 105
+   collection-interval 75
-   include-system-info true
+   include-system-info false

*[ex:/configure log accounting-policy 5]
A:admin@node-2# /compare | match '^-'
-   collection-interval 105
-   include-system-info true

Using the backslash

The backslash (\) is used to match the literal "+" character that denotes additions to the configuration seen in the compare command.

*[ex:/configure log accounting-policy 5]
A:admin@node-2# /compare | match '^\+'
+   admin-state enable
+   collection-interval 75
+   include-system-info false

First container is log and next is log-events

All containers are marked with a "+".

[ex:/configure log]
A:admin@node-2# ?

 accounting-policy     + Enter the accounting-policy list instance
 app-route-            + Enter the app-route-notifications context
  notifications
 apply-groups          - Apply a configuration group at this level
 apply-groups-exclude  - Exclude a configuration group at this level
 event-damping         - Allow event damping algorithm to suppress QoS or
                         filter change events
 event-handling        + Enter the event-handling context
 event-trigger         + Enter the event-trigger context
 file                  + Enter the file list instance
 filter                + Enter the filter list instance
 log-events            + Enter the log-events context
 log-id                + Enter the log-id list instance
 route-preference      + Enter the route-preference context
 services-all-events   + Enter the services-all-events context
 snmp-trap-group       + Enter the snmp-trap-group list instance
 syslog                + Enter the syslog list instance
 throttle-rate         + Enter the throttle-rate context

[ex:/configure log]
A:admin@node-2# log-events

[ex:/configure log log-events]
A:admin@node-2#

Same context entered on one line

Alternatively, the same context can be entered on one line:

(ex)[/]
A:admin@node-2# configure log log-events

(ex)[/configure log log-events]
A:admin@node-2#

Container lists are marked with a "+"

Container lists are also marked with a "+" and the context is entered by specifying the key for the list.

[ex:/configure log]
A:admin@node-2# ?

 accounting-policy     + Enter the accounting-policy list instance
 app-route-            + Enter the app-route-notifications context
  notifications
 apply-groups          - Apply a configuration group at this level
 apply-groups-exclude  - Exclude a configuration group at this level
 event-damping         - Allow event damping algorithm to suppress QoS or
                         filter change events
 event-handling        + Enter the event-handling context
 event-trigger         + Enter the event-trigger context
 file                  + Enter the file list instance
 filter                + Enter the filter list instance
 log-events            + Enter the log-events context
 log-id                + Enter the log-id list instance
 route-preference      + Enter the route-preference context
 services-all-events   + Enter the services-all-events context
 snmp-trap-group       + Enter the snmp-trap-group list instance
 syslog                + Enter the syslog list instance
 throttle-rate         + Enter the throttle-rate context

[ex:/configure log]
A:admin@node-2# log-id ?

 [name] <string>
 <string> - <1..64 characters>

    Log ID

[ex:/configure log]
A:admin@node-2# log-id "99"

[ex:/configure log log-id "99"]
A:admin@node-2#

Configuring a leaf element

Configuring a leaf element maintains the present working context if there is no explicit opening brace. Entering an explicit opening brace navigates into the specified context.

*[ex:/configure card 1 mda 2]
A:admin@node-2# clock-mode mode ?

 mode <keyword>
 <keyword> - (adaptive|differential)

    Clock mode

*[ex:/configure card 1 mda 2]
A:admin@node-2# clock-mode mode adaptive

*[ex:/configure card 1 mda 2]
A:admin@node-2# clock-mode { mode adaptive

*[ex:/configure card 1 mda 2 clock-mode]
A:admin@node-2#

Configuring a container

Configuring a container navigates into the context.

[ex:/configure router "Base"]
A:admin@node-2# ?

 aggregates            + Enter the aggregates context
 allow-icmp-redirect   - Allow ICMP redirects on the management interface
 allow-icmp6-redirect  - Allow IPv6 ICMP redirects on the management interface
 apply-groups          - Apply a configuration group at this level
 apply-groups-exclude  - Exclude a configuration group at this level
 autonomous-system     - AS number advertised to peers for this router
 bfd                   + Enter the bfd context
 bgp                   + Enable the bgp context

---snip---

[ex:/configure router "Base"]
A:admin@node-2# bgp

[ex:/configure router "Base" bgp]
A:admin@node-2# ?

 add-paths             + Enable the add-paths context
 admin-state           - Administrative state of the BGP instance
 advertise-external    + Enter the advertise-external context
 advertise-inactive    - Advertise inactive BGP routes to peers

---snip---

[ex:/configure router "Base" bgp]
A:admin@node-2# add-paths

*[ex:/configure router "Base" bgp add-paths]
A:admin@node-2#

Configuring an empty container or a list where the only children are keys does not navigate into the context. These elements are displayed with aggregated braces with a space ({ }) on the same line. It is possible to enter the element name with an opening brace; however, no options are available in this context.

Configuring the list element sdp-include

For example, configuring the list element sdp-include with a key of ‟ref_group_name” does not change the existing context.

*[ex:/configure service pw-template "tt"]
A:admin@node-2# sdp-include ref_group_name

*[ex:/configure service pw-template "tt"]
A:admin@node-2# info
    sdp-include "ref_group_name" { }

*[ex:/configure service pw-template "tt"]
A:admin@node-2#

In the following example with an opening brace on the command line, the closing brace exits VPRN 1, and then enters the context of VPRN 2.

(ex)[/]
A:admin@node-2# configure service vprn 1 { interface "intf1" description "vprn-if" } vprn 2

*(ex)[/configure service vprn "2"]
A:admin@node-2#

In the following example without an opening brace on the command line, the first closing brace exits interface "int1", and the second closing brace exits VPRN 1 and enters the VPRN 2 context.

*[ex:/configure service]
A:admin@node-2# vprn 1 interface "int1" description "vprn-if" } } vprn 2

*[ex:/configure service vprn "2"]
A:admin@node-2#

Displaying configured information

The following displays configured information for configure router bgp.

*[ex:/configure router "Base" bgp]
A:admin@node-2# info
    connect-retry 90
    local-preference 250
    add-paths {
        ipv4 {
            receive true
        }
    }

The following output displays the same information in JSON IETF format.

[ex:/configure router "Base" bgp]
A:admin@node-2# info json
{
    "nokia-conf:connect-retry": 90,
    "nokia-conf:local-preference": 250,
    "nokia-conf:add-paths": {
        "ipv4": {
            "receive": true
        }
    }
}

The following output displays the same information in XML format:

[ex:/configure router "Base" bgp]
A:admin@node-2# info xml
<connect-retry xmlns="urn:nokia.com:sros:ns:yang:sr:conf" xmlns:nokia-attr="urn:nokia.com:sros:ns:yang:sr:attributes">90</connect-retry>
<local-preference xmlns="urn:nokia.com:sros:ns:yang:sr:conf" xmlns:nokia-attr="urn:nokia.com:sros:ns:yang:sr:attributes">250</local-preference>
<add-paths xmlns="urn:nokia.com:sros:ns:yang:sr:conf" xmlns:nokia-attr="urn:nokia.com:sros:ns:yang:sr:attributes">
    <ipv4>
        <receive>true</receive>
    </ipv4>
</add-paths>

The configuration output can display all elements that are configured, even if an element is set to the system default state or value. The detail option displays all data for the context, including default configurations. The double hash (##) indicates an unconfigured element or a dynamic default.

Displaying all configured elements

*[ex:/configure router "Base" bgp]
A:admin@node-2# info detail
 ## apply-groups
    admin-state enable
 ## description
    connect-retry 90
    keepalive 30
    damping false
    local-preference 250
    loop-detect ignore-loop
    loop-detect-threshold 0
    selective-label-ipv4-install false
    min-route-advertisement 30
    aggregator-id-zero false
    preference 170
    block-prefix-sid false
 ## multihop
 ## med-out
 ## authentication-key
    client-reflect true
    vpn-apply-export false
    vpn-apply-import false
    asn-4-byte true

When using the info command with both the detail and xml options, the double hash (##) elements (indicating unconfigured elements or dynamic defaults) are enclosed within XML comments.

Using the detail and xml options

*[ex:/configure router "Base" bgp] 
A:admin@node-2# info detail xml
<!-- ## apply-groups -->
<!-- ## apply-groups-exclude -->
<admin-state xmlns="urn:nokia.com:sros:ns:yang:sr:conf" xmlns:nokia-attr="urn:nokia.com:sros:ns:yang:sr:attributes">enable</admin-state>
<!-- ## description -->
<connect-retry xmlns="urn:nokia.com:sros:ns:yang:sr:conf" xmlns:nokia-attr="urn:nokia.com:sros:ns:yang:sr:attributes">90</connect-retry>
<keepalive xmlns="urn:nokia.com:sros:ns:yang:sr:conf" xmlns:nokia-attr="urn:nokia.com:sros:ns:yang:sr:attributes">30</keepalive>
<damping xmlns="urn:nokia.com:sros:ns:yang:sr:conf" xmlns:nokia-attr="urn:nokia.com:sros:ns:yang:sr:attributes">false</damping>
<local-preference xmlns="urn:nokia.com:sros:ns:yang:sr:conf" xmlns:nokia-attr="urn:nokia.com:sros:ns:yang:sr:attributes">250</local-preference>

...

When using the info command with both detail and json options, the output does not include unconfigured elements. Unconfigured elements in the MD-CLI are denoted with ## and there is no standard method of displaying comments within the JSON format.

Using the detail and json options

[ex:/configure router "Base" bgp]
A:admin@node-2# info detail json
{
    "nokia-conf:admin-state": "enable",
    "nokia-conf:connect-retry": 90,
    "nokia-conf:keepalive": 30,
    "nokia-conf:damping": false,
    "nokia-conf:local-preference": 250,
    "nokia-conf:loop-detect": "ignore-loop",
    "nokia-conf:loop-detect-threshold": 0,
    "nokia-conf:selective-label-ipv4-install": false,
    "nokia-conf:min-route-advertisement": 30,
    "nokia-conf:aggregator-id-zero": false,
    "nokia-conf:preference": 170,
    "nokia-conf:block-prefix-sid": false,
    "nokia-conf:client-reflect": true,
    "nokia-conf:vpn-apply-export": false,
    "nokia-conf:vpn-apply-import": false,
    "nokia-conf:asn-4-byte": true,
    "nokia-conf:path-mtu-discovery": false,
    "nokia-conf:enforce-first-as": false,
    "nokia-conf:initial-send-delay-zero": false,
    "nokia-conf:inter-as-vpn": false,
    "nokia-conf:purge-timer": 10,
    "nokia-conf:route-table-install": true,

...

The flat option displays the context of every element in the present working context on a single line. Braces ensure that the context stays in the present working context for copy and paste purposes.

Using the flat option

*[ex:/configure router "Base" bgp]
A:admin@node-2# info flat
connect-retry 90
    local-preference 250
    add-paths ipv4 receive true

The full-context option displays the full context of every element from the present working context on a single line.

Using the full-context option

*[ex:/configure router "Base" bgp]
A:admin@cses-V93# info full-context
    /configure router "Base" bgp connect-retry 90
    /configure router "Base" bgp local-preference 250
    /configure router "Base" bgp add-paths ipv4 receive true

When the full-context option is used in conjunction with the json or xml option, the output is modified to display the configuration back to the YANG model-aware root of the configuration tree.

Using the full-context option with the json or xml option

[ex:/configure router "Base" bgp]
A:admin@node-2# info full-context json
{
    "nokia-conf:configure": {
        "router": [
            {
                "router-name": "Base",
                "bgp": {
                    "connect-retry": 90,
                    "local-preference": 250,
                    "add-paths": {
                        "ipv4": {
                            "receive": true
                        }
                    }
                }
            }
        ]
    }
}

[ex:/configure router "Base" bgp]
A:admin@node-2# info full-context xml
<configure xmlns="urn:nokia.com:sros:ns:yang:sr:conf" xmlns:nokia-attr="urn:nokia.com:sros:ns:yang:sr:attributes">
    <router>
        <router-name>Base</router-name>
        <bgp>
            <connect-retry>90</connect-retry>
            <local-preference>250</local-preference>
            <add-paths>
                <ipv4>
                    <receive>true</receive>
                </ipv4>
            </add-paths>
        </bgp>
    </router>
</configure>

Using the depth option

[ex:/configure router "Base"]
A:admin@node-2# info depth 1
    autonomous-system 65816
    router-id 172.16.255.0
    }
    interface "system" {
    }
    bgp {
    }
    isis 0 {
    }

The following examples show the admin show configuration output of the running configuration in the default configuration region (configure). Other configuration regions can also be specified, including bof, debug, and li.

[/]
A:admin@node-2# admin show configuration
# TiMOS-B-22.2.R1 both/x86_64 Nokia 7750 SR Copyright (c) 2000-2022 Nokia.
# All rights reserved. All use subject to applicable license agreements.
# Built on Sat Feb 26 15:31:00 PST 2022 by builder in /builds/c/222B/R1/panos/main/sros
# Configuration format version 22.2 revision 0

# Generated 2022-03-07T17:08:41.4+00:00 by admin from Console

configure {
    card 1 {
        card-type iom4-e
        mda 1 {
            mda-type me10-10gb-sfp+
        }
        mda 2 {
            mda-type me10-10gb-sfp+
        }
        fp 1 {
        }
    }
    log {
        filter "1001" {
            entry 10 {
                description "Collect only events of major severity or higher"
                action forward
                match {
                    severity {
                        gte major
                    }
                }
            }
        }
        log-id "99" {
            description "Default System Log"
            source {
                main true
            }
            destination {
                memory {
                    max-entries 500
                }
            }
        }
        log-id "100" {
            description "Default Serious Errors Log"
            filter "1001"
            source {
                main true
            }
            destination {
                memory {
                    max-entries 500
                }
            }
        }
    }

...

[/]
A:admin@node-2# admin show configuration full-context
# TiMOS-B-23.10.R1 both/x86_64 Nokia 7750 SR Copyright (c) 2000-2023 Nokia.
# All rights reserved. All use subject to applicable license agreements.
# Built on Wed Aug 9 01:11:04 UTC 2023 by builder in /builds/2310B/R1/panos/main/sros
# Configuration format version 23.10 revision 0

# Generated 2023-08-09T16:38:38.0-05:00 by admin from Console

    /configure card 1 card-type iom4-e
    /configure card 1 mda 1 mda-type me10-10gb-sfp+
    /configure card 1 mda 2 mda-type me10-10gb-sfp+
    /configure log filter "1001" named-entry "10" description "Collect only events of major severity or higher"
    /configure log filter "1001" named-entry "10" action forward
    /configure log filter "1001" named-entry "10" match severity gte major
    /configure log filter "1001" named-entry "asdf" action forward
    /configure log log-id "99" description "Default System Log"
    /configure log log-id "99" source main true
    /configure log log-id "99" destination memory max-entries 500
    /configure log log-id "100" description "Default Serious Errors Log"
    /configure log log-id "100" filter "1001"
    /configure log log-id "100" source main true
    /configure log log-id "100" destination memory max-entries 500

...

[/]
A:admin@node-2# admin show configuration json
{
    "nokia-conf:configure": {
        "card": [
            {
                "slot-number": 1,
                "card-type": "iom4-e",
                "mda": [
                    {
                        "mda-slot": 1,
                        "mda-type": "me10-10gb-sfp+"
                    },
                    {
                        "mda-slot": 2,
                        "mda-type": "me10-10gb-sfp+"
                    }
                ],
        ],
        "log": {
            "filter": [
                {
                    "filter-id": "1001",
                    "entry": [
                        {
                            "entry-id": 10,
                            "description": "Collect only events of major severity or higher",
                            "action": "forward",
                            "match": {
                                "severity": {
                                    "gte": "major"
                                }
                            }
                        }
                    ]
                }
            ],
            "log-id": [
                {
                    "id": "99",
                    "description": "Default System Log",
                    "source": {
                        "main": true
                    },
                    "destination": {
                        "memory": {
                            "max-entries": 500
                        }
                    }
                },
                {
                    "id": "100",
                    "description": "Default Serious Errors Log",
                    "filter": 1001,
                    "source": {
                        "main": true
                    },
                    "destination": {
                        "memory": {
                            "max-entries": 500
                        }
                    }
                }
            ]
        },

...

[/]
A:admin@node-2# admin show configuration xml
<?xml version="1.0" encoding="UTF-8"?>
<configure xmlns="urn:nokia.com:sros:ns:yang:sr:conf" xmlns:nokia-attr="urn:nokia.com:sros:ns:yang:sr:attributes">
    <card>
        <slot-number>1</slot-number>
        <card-type>imm48-sfp+2-qsfp28</card-type>
        <mda>
            <mda-slot>1</mda-slot>
        </mda>
    </card>
    <card>
        <slot-number>2</slot-number>
        <card-type>imm36-100g-qsfp28</card-type>
        <mda>
            <mda-slot>1</mda-slot>
        </mda>
    </card>
    <log>
        <filter>
            <filter-id>1001</filter-id>
            <entry>
                <entry-id>10</entry-id>
                <description>"Collect only events of major severity or higher"
</description>
...

CLI path references a section of the MD-CLI tree under the indicated context

/configure card 1 mda 1

CLI path references a specific leaf in the tree

/state system oper-name

In the following example, the two info commands display the same information. The first command usage is an absolute path reference and the next usage is a relative path from the present working context (pwc).

[ex:/configure router "Base" bgp]
A:admin@node-2# pwc
Present Working Context:
  configure
  router "Base"
  bgp

[ex:/configure router "Base" bgp]
A:admin@node-2# info /configure router "Base" bgp group "grp1"

[ex:/configure router "Base" bgp]
A:admin@node-2# info group "grp1"