show device dependent configuration

date_range 14-Nov-24

arrow_backward

arrow_forward

Syntax

content_copy zoom_out_map
show device dependent configuration device-name

content_copy zoom_out_map
show device dependent configuration device-name | save directory-path/filename.xml

Description

Displays the device-centric configurations for provisioning services, in the XML format. This device-centric information is useful for troubleshooting and debugging errors when a service order associated with a service instance fails to execute.

You can save the device configurations file to the service orchestration cMGD pod file system. To troubleshoot errors on devices or nodes, you must copy the configurations file from the service orchestration cMGD pod to the controller node. To copy the configurations file to the controller node, log in to the controller node and execute the following command:

content_copy zoom_out_map
kubectl cp foghorn/cmgd-pod-name:directory-path/filename.xml filename.xml

Options

`device-name`	Name of the device for which you want to view the configurations for provisioning a service.
save	This option allows you to save the device configurations to the service orchestration cMGD pod file system.
`directory-path`	The location in the service orchestration cMGD pod file system where you want to save the device configurations file. For example, /var/tmp.
`filename`.xml	File name you assign to the device configurations file (in XML format) when you are saving the file in the service orchestration cMGD pod file system.

Sample Output

show device dependent configuration device-name

content_copy zoom_out_map
<?xml version="1.0" ?>
<devices>
  <device>
    <name>00000000-0000-0000-1000-d4996c4c2ac0</name>
    <configuration>
      <groups replace="replace">
        <name>paragon-service-orchestration</name>
        <chassis>
          <network-services>enhanced-ip</network-services>
        </chassis>
        <firewall>
          <policer>
            <name>ebd5a8bf-e2bf-11ee-a392-f6e61c3d4879-VPN-1-BNG-access-input</name>
            <logical-interface-policer/>
            <if-exceeding>
              <bandwidth-limit>1000000</bandwidth-limit>
              <burst-size-limit>75000</burst-size-limit>
            </if-exceeding>
            <then>
              <discard/>
            </then>
          </policer>
          <policer>
            <name>ebd5a8bf-e2bf-11ee-a392-f6e61c3d4879-VPN-1-BNG-access-output</name>
            <logical-interface-policer/>
            <if-exceeding>
              <bandwidth-limit>1000000</bandwidth-limit>
              <burst-size-limit>75000</burst-size-limit>
            </if-exceeding>
            <then>
              <discard/>
            </then>
          </policer>
        </firewall>
        <interfaces>
          <interface>
            <name>xe-1/0/3</name>
            <mtu>1514</mtu>
            <unit>
              <name>0</name>
              <description>Network access to VPN VPN-1 for customer ebd5a8bf-e2bf-11ee-a392-f6e61c3d4879</description>
              <family>
                <inet>
                  <policer>
                    <input>ebd5a8bf-e2bf-11ee-a392-f6e61c3d4879-VPN-1-BNG-access-input</input>
                    <output>ebd5a8bf-e2bf-11ee-a392-f6e61c3d4879-VPN-1-BNG-access-output</output>
                  </policer>
                  <address>
                    <name>40.1.1.1/30</name>
                  </address>
                </inet>
              </family>
            </unit>
          </interface>
        </interfaces>

Release Information

Command introduced in Juniper Paragon Automation Release 2.0.0.

arrow_backward PREVIOUS show service designs

NEXT arrow_forward show insights configuration

Juniper Paragon Automation User Guide

ON THIS PAGE