Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Uploading Configuration Data as a Data Stream Using the Junos XML Protocol

 

In a Junos XML protocol session with a device running Junos OS, to upload configuration data as a data stream, a client application encloses the <load-configuration> tag element in an <rpc> tag element.

To define the configuration elements to change as Junos XML tag elements, the application emits the tag elements representing all levels of the configuration hierarchy from the root (represented by the <configuration> tag element) down to each element to change.

To define the configuration data to change as formatted ASCII text, the application encloses the statements in a <configuration-text> tag element and includes the format="text" attribute in the opening <load-configuration> tag.

To define the configuration data to change as Junos OS configuration mode set commands, the application encloses the commands in a <configuration-set> tag element and includes the action="set" and format="text" attributes in the opening <load-configuration> tag.

Starting in Junos OS Release 16.1, you can load configuration data formatted using JavaScript Object Notation (JSON) on devices running Junos OS. To define the configuration data to change as JSON format, the application encloses the data in a <configuration-json> tag element and includes the format="json" attribute in the opening <load-configuration> tag.

For information about the syntax for Junos XML tag elements, formatted ASCII text, configuration mode commands, and JSON format, see Defining the Format of Configuration Data to Upload in a Junos XML Protocol Session.

Related Documentation

Release History Table
Release
Description
16.1
Starting in Junos OS Release 16.1, you can load configuration data formatted using JavaScript Object Notation (JSON) on devices running Junos OS.