Using the info command

The info command shows configuration or state information from the present context. The command can only be executed in a configuration mode for a configuration region or for the state branch. By default, all configured parameters in the candidate configuration datastore are displayed for a configuration region. For a state region, all elements that have a value are displayed.

Use the following syntax to configure the info command.

[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
Table: Displaying configuration from configuration groups and third party models with info options
Usage Info option Datastore Nokia configuration Configuration groups Third party model configuration
Display third party configuration converted to Nokia configuration converted Running Nokia and converted third party configuration with origin comments groups and unexpanded apply-groups statements —
Display the configuration with configuration groups inheritance inheritance Any ✓ groups and expanded apply-groups statements with origin comments Native format
Display third party configuration converted to Nokia configuration with configuration groups inheritance converted inheritance Running Nokia and converted third party configuration with origin comments groups and expanded apply-groups statements with origin comments —
Display the expanded configuration applied by the router intended Intended ✓ Expanded configuration without groups or apply-groups statements or origin comments Native format
Note: The converted and model options are only available when configure system management-interface yang-modules openconfig-modules is set to true.
Note: The output of info flat and info full-context display braces relative to the context from which the command is executed so that the session remains in the context if the output is pasted.

Execute the command from the configuration root to stay at the root context without navigating.

Note: As indicated in the choice statement, the flat, json, and xml options are mutually exclusive options. Other unsupported combinations include:

The order of the configuration output is as follows:

Example: 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.

Example: 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.

Example: 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>

---snip---

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.

Example: 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,

---snip---

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.

Example: Using the flat option

*[ex:/configure router "Base" bgp]
A:admin@node-2# info flat detail
 ## apply-groups
    admin-state enable
 ## description
    connect-retry 90
    keepalive 30
    damping false
    local-preference 250
 
---snip---

 ## route-target-list
 ## outbound-route-filtering
 ## monitor
    rib-management { }
    rib-management { ipv4 }
    rib-management { ipv4 route-table-import }
 ## rib-management ipv4 route-table-import apply-groups
 ## rib-management ipv4 route-table-import policy-name
 
---snip---

    rib-management { label-ipv4 }
    rib-management { label-ipv4 route-table-import }
 ## rib-management label-ipv4 route-table-import apply-groups
 ## rib-management label-ipv4 route-table-import policy-name
 
---snip---

 segment-routing { }
 ## segment-routing apply-groups
    segment-routing { admin-state disable }
 ## segment-routing prefix-sid-range
 
---snip---

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

Example: Using the full-context option

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

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

---snip---

    /configure router "Base" bgp add-paths { }
    /configure router "Base" bgp add-paths { ipv4 }
 ## /configure router "Base" bgp add-paths ipv4 send
    /configure router "Base" bgp add-paths { ipv4 receive true }
    /configure router "Base" bgp add-paths { ipv6 }

---snip---

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.

Example: 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>
Parent topic: Displaying information in the MD-CLI

Displaying lists

The info command always displays all keys of the list on the same line. The first key of a list is unnamed in the MD-CLI, however, there are exceptions where the key is named and must be entered. (See the online help for the correct syntax of the command, or the 7450 ESS, 7750 SR, 7950 XRS, and VSR MD-CLI Command Reference Guide). All other keys are named.

Example

For example, the collector list has two keys, ip-address and port. The name of the first key, ip-address, does not appear in the info display. The name of the second key and any subsequent keys are always displayed.

*[ex:/configure cflowd]
A:admin@node-2# info
    collector 10.10.20.30 port 7 {
    }
    collector 10.10.30.40 port 8 {
    }