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
external-header-nav
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Request Multiple Configuration Elements Using the Junos XML Protocol

date_range 14-Jul-21

In a Junos XML protocol session with a device running Junos OS, a client application can request multiple configuration elements of the same type or different types within a <get-configuration> tag element. The request includes only one <configuration> tag element (the Junos XML protocol server returns an error if there is more than one).

If two requested objects have the same parent hierarchy level, the client can either include both requests within one parent tag element, or repeat the parent tag element for each request. For example, at the [edit system] hierarchy level, the client can request the list of configured services and the identifier tag element for RADIUS servers in either of the following two ways:

content_copy zoom_out_map
<!-- both requests in one parent tag element -->
<rpc>
    <get-configuration>
        <configuration>
            <system>
                <services/>
                <radius-server>
                    <name/>
                </radius-server>
            </system>
        </configuration>
    </get-configuration>
</rpc>
    
<!-- separate parent tag element for each request -->
<rpc>
    <get-configuration>
        <configuration>
            <system>
                <services/>
            </system>
            <system>
                <radius-server>
                    <name/>
                </radius-server>
            </system>
        </configuration>
    </get-configuration>
</rpc>

The client can combine requests for any of the types of information discussed in the following sections:

external-footer-nav