Navigating in the MD-CLI

A short help description is displayed immediately when the question mark (?) is entered (without needing to press Enter). The following displays help from the operational root level.

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

 admin                 + Enter the administrative context for system operations
 bof                   + Enter the bof context
 clear                 + Clear statistics or reset operational state
 configure             + Enter the configuration context
 environment           + Enter the environment configuration context
 file                  + Perform file operations
 li                    + Enter the lawful intercept context
 password              - Change the local user password
 show                  + Show operational information
 state                 + Show state information
 tools                 + Enter the tools context for troubleshooting and
                         debugging

 Global commands:
 back                  - Move back one or more levels
 delete                - Delete an element
 edit-config           - Enter a candidate configuration mode
 enable                - Enable administrative mode
 exec                  - Execute commands from a file
 exit                  - Return to the previous context or to operational root
 history               - Show the command history
 logout                - Exit the CLI session
 oam                   - Perform OAM tests
 ping                  - Ping an IP address or DNS name
 pwc                   - Show the present working context
 ssh                   - SSH to an IP address or DNS name
 telnet                - Telnet to an IP address or DNS name
 top                   - Move to the top level of the context
 traceroute            - Show the route taken to an IP address or DNS name
 tree                  - Show the command tree under the present working context

 Configuration commands:
 info                  - Show the information under the present working context

The ? help is context-sensitive. The following ? help output lists additional commands available in exclusive configuration mode.

(ex)[/]
A:admin@node-2# ?

 admin                 + Enter the administrative context for system operations
 clear                 + Clear statistics or reset operational state
 configure             + Enter the configuration context
 environment           + Enter the environment configuration context
 file                  + Perform file operations
 password              - Change the local user password
 show                  + Show operational information
 state                 + Show state information
 tools                 + Enter the tools context for troubleshooting and
                         debugging

 Global commands:
 back                  - Move back one or more levels
 delete                - Delete an element
 edit-config           - Enter a candidate configuration mode
 enable                - Enable administrative mode
 exec                  - Execute commands from a file
 exit                  - Return to the previous context or to operational root
 history               - Show the command history
 insert                - Insert an element into a user-ordered list
 logout                - Exit the CLI session
 oam                   - Perform OAM tests
 ping                  - Ping an IP address or DNS name
 pwc                   - Show the present working context
 quit-config           - Exit the candidate configuration mode
 ssh                   - SSH to an IP address or DNS name
 telnet                - Telnet to an IP address or DNS name
 top                   - Move to the top level of the context
 traceroute            - Show the route taken to an IP address or DNS name
 tree                  - Show the command tree under the present working context

 Configuration commands:
 commit                - Commit the candidate configuration
 compare               - Compare changes between datastores
 copy                  - Copy a configuration element to another
 discard               - Discard changes in the candidate datastore
 info                  - Show the information under the present working context
 rename                - Rename a list element
 update                - Update the candidate baseline
 validate              - Validate changes in the candidate datastore

The help results may depend on the cursor position. The following example shows the router command syntax, followed by available commands after entering the router context.

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

 router [[router-name] <string>]

 [router-name]         - Administrative router name

 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
 bier                  + Enable the bier context
 class-forwarding      - Allow class-based forwarding over IGP shortcuts
 confederation         + Enter the confederation context
 description           - Text description
 dhcp-server           + Enter the dhcp-server context
 dns                   + Enter the dns context
 ecmp                  - Maximum equal-cost routes for routing table instance
 
---snip---

In the following ? output, similar information is shown, with more details provided for configuring the router command, including the allowable string length and default value for the command.

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

 router [[router-name] <string>]

 [[router-name] <string>]
 <string>  - <1..64 characters>
 Default   - "Base"

    Administrative router name

 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
 bier                  + Enable the bier context
 class-forwarding      - Allow class-based forwarding over IGP shortcuts
 confederation         + Enter the confederation context
 description           - Text description
 dhcp-server           + Enter the dhcp-server context
 dns                   + Enter the dns context
 ecmp                  - Maximum equal-cost routes for routing table instance
 
 ---snip---

The global commands are available from various levels of the MD-CLI hierarchy.

Configuration commands are availabe within a configuration mode. However, some commands are not visible within specific configuration modes, For example, the commit command is not available in read-only configuration mode.

The following commands can be used to navigate the MD-CLI hierarchy (context) levels:

• pwc

  The pwc command displays the present working context with all keyword and variable parameters. The syntax is as follows:

  pwc [[path-type] {model-path | xpath| cli-path}] [previous]
  

  (ex)[/]
  A:admin@node-2# configure
  
  (ex)[/configure]
  A:admin@node-2# card 1
  
  (ex)[/configure card 1]
  A:admin@node-2# mda 2
  
  *(ex)[/configure card 1 mda 2]
  A:admin@node-2# network
  
  *(ex)[/configure card 1 mda 2 network]
  A:admin@node-2# pwc
  Present Working Context:
    configure
    card 1
    mda 2
    network
  

  • pwc previous

    The pwc previous command displays the previous working context.

    *(ex)[/configure card 1 mda 2 network]
    A:admin@node-2# pwc previous
    Previous Working Context:
      configure
      card 1
      mda 2
    

  • pwc path-type

    • model-path: a YANG-modeled path format that can be used with RESTCONF-based management systems

    • xpath: a format that can be used with streaming telemetry

    • cli-path: a single-line version of the MD-CLI command line interface path format; useful for cutting and pasting the path into an MD-CLI command which supports the CLI path as an unnamed parameter input.

    *(ex)[/configure card 1 mda 2 network]
    A:admin@node-2# pwc model-path
    Present Working Context:
    /nokia-conf:configure/card=1/mda=2/network
    
    *(ex)[/configure card 1 mda 2 network]
    A:admin@node-2# pwc xpath
    Present Working Context:
    /configure/card[slot-number=1]/mda[mda-slot=2]/network
    
    [ex:/configure router "Base" bgp group "mesh"]
    A:admin@node-2# pwc cli-path
    Present Working Context:
    /configure router "Base" bgp group "mesh"
    

• back

  The back command can be used to go back one or more levels. If no parameter value is specified for the number of levels to go back, the default is one level. Using back at the top of the current command tree moves the context to the operational root level. If the number of levels specified is greater than the current depth, the context moves to the operational root. A closing brace (}) can also be used to go back one level.

  *(ex)[/configure card 1 mda 2 network]
  A:admin@node-2# back
  
  *(ex)[/configure card 1 mda 2]
  A:admin@node-2# back 2
  
  *(ex)[/configure]
  A:admin@node-2# back 5
  
  *(ex)[/]
  A:admin@node-2#
  

• top

  The top command moves the context to the top of the current command tree without exiting the mode. Use the top command instead of issuing the back command multiple times to move the context to the top of the command tree.

  *(ex)[/]
  A:admin@node-2# configure
  
  *(ex)[/configure]
  A:admin@node-2# card 1
  
  *(ex)[/configure card 1]
  A:admin@node-2# mda 2
  
  *(ex)[/configure card 1 mda 2]
  A:admin@node-2# network
  
  *(ex)[/configure card 1 mda 2 network]
  A:admin@node-2# top
  
  *(ex)[/configure]
  A:admin@node-2#
  

• exit

  The exit command moves the context to the previous context in the current command tree. If the previous context was up one level, the exit command functions similarly to the back command. Using exit all moves the context to the operational root. A slash (/) or Ctrl-z can also be used instead of exit all. Using exit at the operational root has no effect. To log out of the system, the logout command must be used.

  *(ex)[/]
  A:admin@node-2#
  
  *(ex)[/]
  A:admin@node-2# configure card 1 mda 2
  
  *(ex)[/configure card 1 mda 2]
  A:admin@node-2# atm
  
  *(ex)[/configure card 1 mda 2 network]
  A:admin@node-2# exit all
  
  *(ex)[/]
  A:admin@node-2# configure card 1 mda 2 network
  
  *(ex)[/configure card 1 mda 2 network]
  A:admin@node-2# /
  
  *(ex)[/]
  A:admin@node-2#
  

The tree command displays the command tree under the present working context, excluding the present working context element. Hierarchy is indicated with a pipe (|), and a "+-- " separator precedes each element. The tree output is in alphabetical order of elements.

[ex:/configure system security aaa remote-servers]
A:admin@node-2# tree
+-- apply-groups
+-- apply-groups-exclude
+-- ldap
|   +-- admin-state
|   +-- apply-groups
|   +-- apply-groups-exclude
|   +-- public-key-authentication
|   +-- server
|   |   +-- address
|   |   |   +-- apply-groups
|   |   |   +-- apply-groups-exclude
|   |   |   +-- port
|   |   +-- admin-state
|   |   +-- apply-groups
|   |   +-- apply-groups-exclude
|   |   +-- bind-authentication
|   |   |   +-- password
|   |   |   +-- root-dn
|   |   +-- search
|   |   |   +-- base-dn
|   |   +-- server-name
|   |   +-- tls-profile
|   +-- server-retry
|   +-- server-timeout
|   +-- use-default-template
+-- radius
|   +-- access-algorithm
|   +-- accounting
|   +-- accounting-port
|   +-- admin-state
|   +-- apply-groups
|   +-- apply-groups-exclude
|   +-- authorization
|   +-- interactive-authentication
|   +-- port
|   +-- server
|   |   +-- address
|   |   +-- apply-groups
|   |   +-- apply-groups-exclude
|   |   +-- secret
|   +-- server-retry
|   +-- server-timeout
|   +-- use-default-template
+-- tacplus
    +-- accounting
    |   +-- record-type
    +-- admin-control
    |   +-- tacplus-map-to-priv-lvl
    +-- admin-state
    +-- apply-groups
    +-- apply-groups-exclude
    +-- authorization
    |   +-- use-priv-lvl
    +-- interactive-authentication
    +-- priv-lvl-map
    |   +-- apply-groups
    |   +-- apply-groups-exclude
    |   +-- priv-lvl
    |       +-- apply-groups
    |       +-- apply-groups-exclude
    |       +-- user-profile-name
    +-- server
    |   +-- address
    |   +-- apply-groups
    |   +-- apply-groups-exclude
    |   +-- port
    |   +-- secret
    +-- server-timeout
    +-- use-default-template

[/]
A:admin@node-2# tree
+-- admin
|   +-- clear
|   |   +-- security
|   |       +-- lockout
|   |       |   +-- all
|   |       |   +-- user
|   |       +-- password-history
|   |           +-- all
|   |           +-- user
|   +-- disconnect
|   |   +-- address
|   |   +-- session-id
|   |   +-- session-type
|   |   +-- username
|   +-- nat
|   |   +-- save-deterministic-script
|   +-- reboot
|   |   +-- now
|   +-- redundancy
|   |   +-- force-switchover
|   |   |   +-- now
|   |   +-- synchronize
|   |       +-- boot-environment
|   |       +-- configuration
|   +-- save
|   |   +-- bof
|   |   +-- configure
|   |   +-- li
|   +-- set

---snip---

Variables, keywords, global commands, and configuration commands and units are separated by a blank line in the output, in the following order:

• values or units (mutually exclusive)

• keywords

• global commands

• configuration commands

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

 accounting-policy        app-route-notifications  apply-groups
 apply-groups-exclude     event-damping            event-handling
 event-trigger            file                     filter
 log-events               log-id                   route-preference
 services-all-events      snmp-trap-group          syslog
 throttle-rate

 back                     delete                   dev-examples
 edit-config              enable                   exec
 exit                     history                  insert
 logout                   oam                      ping
 pwc                      ssh                      telnet
 top                      traceroute               tree

 commit                   compare                  copy
 discard                  info                     rename
 update                   validate

[ex:/configure log]
A:admin@node-2# event-damping Press Tab
 
 <event-damping>
 false
 true

 accounting-policy        app-route-notifications  apply-groups
 apply-groups-exclude     event-handling           event-trigger
 file                     filter                   log-events
 log-id                   route-preference         services-all-events
 snmp-trap-group          syslog                   throttle-rate

 delete                   insert

The ? help displays similar information but only displays global or configuration commands at the operational root or at the root of a command context. For example, the global and configuration commands are displayed at the environment root context.

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

 command-completion    + Enter the command-completion context
 console               + Enter the console context
 message-severity-     + Enter the message-severity-level context
  level
 more                  - Prompt to continue or stop when output text fills page
 progress-indicator    + Enter the progress-indicator context
 prompt                + Enter the prompt context
 time-display          - Time zone displayed before the prompt
 time-format           - Time format to display date and time

 Global commands:
 back                  - Move back one or more levels
 delete                - Delete an element
 dev-examples          - Enter the dev-examples context for operations
 edit-config           - Enter a candidate configuration mode
 enable                - Enable administrative mode
 exec                  - Execute commands from a file
 exit                  - Return to the previous context or to operational root
 history               - Show the command history
 logout                - Exit the CLI session
 oam                   - Perform OAM tests
 ping                  - Ping an IP address or DNS name
 pwc                   - Show the present working context
 ssh                   - SSH to an IP address or DNS name
 telnet                - Telnet to an IP address or DNS name
 top                   - Move to the top level of the context
 traceroute            - Show the route taken to an IP address or DNS name
 tree                  - Show the command tree under the present working context

 Configuration commands:
 info                  - Show the information under the present working context

The global and configuration commands are not displayed in the environment prompt context, for example, although these commands are still available in the context:

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

 context               - Show the current command context in the prompt
 newline               - Add a new line before every prompt line
 timestamp             - Show the timestamp before the first prompt line
 uncommitted-changes-  - Show an asterisk (*) when uncommitted changes exist
  indicator

[/environment prompt]
A:admin@node-2# info detail
    context true
    newline true
    timestamp false
    uncommitted-changes-indicator true

The MD-CLI supports both command abbreviation and command completion. When typing a command, TAB, Spacebar, or ENTER invokes auto-completion. If the text entered is enough to match a specific command, auto-completion completes the command. If the text entered is not sufficient to identify a specific command, pressing Tab or Spacebar displays options in alphabetical order matching the text entered.

The environment command-completion command controls what keystrokes can trigger command completion. Each keystroke is independently controlled with its own Boolean value.

(ex)[/environment command-completion]
A:admin@node-2# info detail
    enter true
    space true
    tab true

A single idle timeout applies to all CLI engines in a CLI session (classic and MD-CLI). The idle timeout can be modified to a value between 1 and 1440 minutes.

The following points apply.

• The idle timeout only affects new CLI sessions. Existing and current sessions retain the previous idle timeout.

• The idle timeout can be disabled by setting the value to none.

• The "Idle time" column in the show users display is reset after an action in either CLI engine.

  [/]
  A:admin@node-2# show users
  ===============================================================================
  User                             Type      Login time           Idle time
    Session ID   (Router instance)
                 From
  ===============================================================================
                                   Console         --             0d 21:44:02 --
    6            (--)
                 --
  admin                            SSHv2     16FEB2021 20:42:15   0d 00:00:04 --
    12           (management)
                 192.168.144.97
  admin                            SSHv2     16FEB2021 19:49:45   0d 00:00:00 --
   #11           (management)
                 192.168.144.97
  -------------------------------------------------------------------------------
  Number of users: 2
  '#' indicates the current active session
  ===============================================================================

A warning message is displayed when a session reaches one-half the value of the idle timeout, and another message is displayed when the idle timeout expires and the user is logged out.

Output modifiers provide support for post-processing of CLI output. Output modifiers are specified using a vertical bar (|) character. The following points apply when using output modifiers.

• Output modifiers can be appended to any CLI command in any command context.

• Output modifiers work across soft line breaks (visual lines) that are wrapped because of the terminal width; for example, using match or count. They do not work across hard line breaks (logical lines).

• Modifiers can be combined in any order. No hard limit exists for the number of combinations. Output is processed linearly and there is little impact on the system performance except to the operator session that entered the modifier combination.

The exec command executes commands from a file as if the user typed or pasted the input into the MD-CLI. The syntax can be seen as follows:

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

 [url] <string>
 <string>  - <0..255 characters>

    Location of the file to be executed

[ex:/configure]
A:admin@node-2# exec my-url-fn ?

 exec

 echo                  - Display the commands as they are being executed

The exec command:

• errors if it detects an interactive input

• terminates in the CLI engine in which it completes execution as follows:

  • if there are no commands that switch CLI engines, the CLI engine is always the one in which exec started

  • if there are commands that switch CLI engines, exec ends in the last CLI engine that was entered

  • //exec returns to the engine in which it was started

• terminates execution and displays an error message if an error occurs, leaving the session in the same context as when the error occurred

The system executes the file as follows:

• disables pagination while the command is running

• disables command completion while the command is running

• suppresses the commands in the file from the command history

As described in Section Navigating the MD-CLI Hierarchy Levels, the pwc command displays the present working context. Navigating around the MD-CLI hierarchy changes the present working context. The MD-CLI path format, also known as cli-path, is displayed in the MD-CLI user prompt; for example:

[ex:/configure card 1 mda 1]
A:admin@node-2# pwc
Present Working Context:
  configure
  card 1
  mda 1

For the following commands, an absolute or relative MD-CLI path can be specified to provide path qualified attributes:

• admin show configuration (see Displaying Configuration with admin Commands)

• compare (see Using the compare Outputs to Copy and Paste)

• copy (see Using the copy Command)

• discard (see Discarding Configuration Changes)

• info (see Using the info Command)

• rename (see Using the rename Command)

• tree (see Using the tree Command)

Absolute Path

An absolute CLI path is specified using the forward slash (/) as the MD-CLI tree structure from the root.

The following absolute CLI path references a section of the MD-CLI tree under the indicated context:

/configure card 1 mda 1

The following CLI path references a specific leaf in the tree:

/state system oper-name

Relative Path

A relative CLI path specifies the MD-CLI tree structure from the present working context. 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"

The CLI path is accepted as an unnamed last parameter of the command. The information is displayed for the specified path.

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

 info [[from] <keyword>] [[cli-path] <path>]

 [[from] <keyword>]
 <keyword>  - (candidate|running|baseline|intended)

    Source datastore

 [cli-path] <path>
 <path>  - <absolute or relative from pwc>

    Absolute or relative path from present working context

 converted             - Include converted third party model configuration from
                         the running datastore
 detail                - Include default and unconfigured values
 full-context          - Show the full context on each line
 inheritance           - Include configuration inherited from configuration
                         groups
 model                 - Model for which to limit converted output to values
 units                 - Include unit types for applicable elements

 Choice: output-format
 flat                 :- Show the context from the pwc on each line
 json                 :- Show the output in indented JSON format
 xml                  :- Show the output in indented XML format

[ex:/configure]
A:admin@node-2# info candidate detail units /configure system
 ## apply-groups
 ## apply-groups-exclude
 ## contact
    name "node-2"
 ## location
    icmp-vse false
    selective-fib false
 ## coordinates
 ## clli-code
    ospf-dynamic-hostnames false

---snip---

A configuration lock from either implicit or explicit configuration mode is required to display paths for a configuration region.

The state branch does not have a lock and can always be specified.

[ex:/configure]
A:admin@node-2# info detail /state system
    oper-name "node-2"
    base-mac-address aa:bb:cc:00:00:00
    platform "7750 SR-12"
    chassis-topology standalone
    crypto-module-version "SRCM 3.1"
 ## fabric-speed
    temperature-status ok
    fp-generation-fp2 false
    fp-generation-fp3 false
    fp-generation-fp4 false
    system-profile none
    active-cpm-slot "A"

The following example shows the use of the info command with a state path from operational mode.

[/]
A:admin@node-2# info /state system
    oper-name "node-2"
    base-mac-address aa:bb:cc:00:00:00
    platform "7750 SR-12"
    chassis-topology standalone
    crypto-module-version "SRCM 3.1"
    temperature-status ok
    fp-generation-fp2 false
    fp-generation-fp3 false
    fp-generation-fp4 false
    system-profile none
    active-cpm-slot "A"

In the next example, to use the info command from a state path to a configuration region, a configuration lock must be established.

[/state system]
A:admin@node-2# info /configure system
                      ^^^^^^^^^
MINOR: MGMT_CORE #2203: Invalid element - currently not allowed

[/state system]
A:admin@node-2# edit-config read-only
INFO: CLI #2066: Entering read-only configuration mode

(ro)[/state system]
A:admin@node-2# info /configure system
    name "node-2"
    management-interface {
        configuration-mode mixed
        snmp {
            admin-state disable
        }

---snip---

The following are examples of the supported commands with a CLI path parameter.

(ex)[/state router "Base" bgp]
A:admin@node-2# info /state router bgp statistics routes-per-family ipv4
    remote-routes 45
    remote-active-routes 6
    backup-routes 0

*(ex)[/state router "Base" bgp]
A:admin@node-2# compare /configure system
-   name "test1"
+   name "test"

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

(ex)[/configure router "Base"]
A:admin@node-2# tree bgp group "mesh" add-paths ipv4
+-- receive
+-- send

[/]
A:admin@node-2# admin show configuration /configure router isis interface "system"
    passive true

(ex)[/configure policy-options]
A:admin@node-2# copy policy-statement "mytest" to /configure policy-options policy-statement "my_new_policy"

(ex)[/configure router "Base" bgp]
A:admin@node-2# rename /configure policy-options policy-statement "mytest" to "another_new_policy" 

The admin show commands are available in the operational mode of the MD-CLI, or they can be executed with /admin from a command context. These commands show the same configuration about as the info command but are not subject to command authorization and do not require configuration access.

See the 7450 ESS, 7750 SR, and 7950 XRS MD-CLI Command Reference Guide for information about the admin commands in the MD-CLI.

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 and li.

[/]
A:admin@node-2# admin show configuration
# TiMOS-B-20.7.B1-24 both/x86_64 Nokia 7750 SR Copyright (c) 2000-2020 Nokia.
# All rights reserved. All use subject to applicable license agreements.
# Built on Fri Aug 28 18:12:17 PDT 2020 by builder in /builds/c/207B/B1-24/panos/main/sros
# Configuration format version 20.7 revision 0

# Generated TUE SEP 15 19:17:31 2020 UTC

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
                }
            }
        }
    }
    port 1/1/1 {
        admin-state enable

---snip---

[/]
A:admin@node-2# admin show configuration full-context
# TiMOS-B-20.7.B1-24 both/x86_64 Nokia 7750 SR Copyright (c) 2000-2020 Nokia.
# All rights reserved. All use subject to applicable license agreements.
# Built on Fri Aug 28 18:12:17 PDT 2020 by builder in /builds/c/207B/B1-24/panos/main/sros
# Configuration format version 20.7 revision 0

# Generated TUE SEP 15 19:20:50 2020 UTC

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

---snip---

[/]
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+"
                    }
                ],
                "fp": [
                    {
                        "fp-number": 1
                    }
                ]
            }
        ],
        "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
                        }
                    }
                }
            ]
        },
        "port": [
            {
                "port-id": "1/1/1",
                "admin-state": "enable"
            },

---snip---

[/]
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">
    <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>

---snip---