Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Juniper Paragon Automation User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

show device dependant configuration

date_range 18-Jun-24

Syntax

content_copy zoom_out_map
show device dependant configuration <device-name>

To save the configuration as a template in your local system:

content_copy zoom_out_map
show device dependant configuration <device-name> | save <directory-path>/<filename>.xml

Description

Displays the configuration committed on a device for provisioning a service instance, in the XML format. This device-centric information is useful for troubleshooting and debugging errors when a service order associated with the service instance fails to execute. You can save the device configuration by providing a directory and a filename.

Options

device-name

The name of the device for which you want to view configuration committed for provisioning a service instance.

directory-path

The location in the Paragon Automation cluster where you want to save the template.

filename

The name with which you are saving the template in the Paragon Automation cluster.

Sample Output

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 Paragon Automation Release 2.0.0.

footer-navigation