ON THIS PAGE
<load-configuration>
Usage
<rpc>
<load-configuration configuration-revision="revision-id"/>
<load-configuration rescue="rescue"/>
<load-configuration rollback="index"/>
<load-configuration url="url"
[action="(merge | override | replace | update)"]
[format="(text | xml)"] />
<load-configuration url="url" [action="(merge | override | update)"]
format="json" />
<load-configuration url="url" action="set" format="text"/>
<load-configuration [action="(merge | override | replace | update)"]
[format="xml"]>
<configuration>
<!-- tag elements for configuration elements to load -->
</configuration>
</load-configuration>
<load-configuration [action="(merge | override | replace | update)"]
format="text">
<configuration-text>
<!-- formatted ASCII configuration statements to load -->
</configuration-text>
</load-configuration>
<load-configuration [action="(merge | override | update)"] format="json">
<configuration-json>
<!-- JSON configuration data to load -->
</configuration-json>
</load-configuration>
<load-configuration action="set" format="text">
<configuration-set>
<!-- configuration mode commands to load -->
</configuration-set>
</load-configuration>
</rpc>Description
Request that the NETCONF or Junos XML protocol server load configuration data into the candidate configuration or open configuration database.
If a client application issues the Junos XML protocol <open-configuration> operation to open a specific
configuration database before executing the <load-configuration> operation, the server loads the configuration data into the open
configuration database. Otherwise, the server loads the configuration
data into the candidate configuration.
Table 1 describes the common load configuration operations.
<load-configuration> Operation |
Description |
|---|---|
<load-configuration configuration-revision="revision-id"/> |
Load a previously committed configuration by referencing its configuration revision ID. The specified configuration completely replaces the candidate configuration. |
<load-configuration rescue="rescue"/> |
Load the rescue configuration. The rescue configuration completely replaces the candidate configuration. |
<load-configuration rollback="index"/> |
Load a previously committed configuration by referencing its numerical rollback index. The specified configuration completely replaces the candidate configuration. |
<load-configuration url="url" format="(text | xml | json)/> <load-configuration url="url" action="set" format="text"/> |
Load configuration data from the file specified in the
<load-configuration url="/tmp/add.conf" format="text"/> |
<load-configuration format="xml">
<configuration>...</configuration>
</load-configuration>
<load-configuration format="text">
<configuration-text>...</configuration-text>
</load-configuration>
<load-configuration format="json">
<configuration-json>...</configuration-json>
</load-configuration>
<load-configuration action="set" format="text">
<configuration-set>...</configuration-set>
</load-configuration>
|
Load the configuration as a data stream. Enclose the configuration data in the appropriate set of tags for the format. |
Attributes
action |
Specify how to load the configuration data, particularly when the target configuration database and the loaded configuration contain conflicting statements. The ephemeral configuration database supports all of the
|
configuration-revision |
Load a previously committed configuration by referencing its configuration revision ID. The specified configuration completely replaces the candidate configuration. |
format |
Specify the format used for the configuration data.
|
rescue |
Replace the candidate configuration with the rescue configuration.
Note:
You can also use the |
rollback |
Load a previously committed configuration by referencing its numerical rollback index. Valid values are 0 (for the most recently committed configuration) through one less than the number of stored previous configurations (maximum is 49). Note:
You can also use the |
url |
Specify the full pathname of the file that contains the configuration data to load. The value can be a local file path, an FTP location, or an HTTP URL.
In each case, the default value for the path variable is the home directory for the username. To specify an absolute path, the application starts the path with the characters %2F; for example, ftp://username:password@hostname/%2Fpath/filename. |
Release Information
This operation is a Junos XML management protocol operation. It is supported in Junos XML protocol sessions, and it is supported as a Juniper Networks proprietary extension in NETCONF sessions on Junos devices that identify the URI http://xml.juniper.net/netconf/junos/1.0 in the capabilities exchange.
action attribute value set added in Junos OS Release 11.4.
format attribute value json added in Junos OS Release 16.1.
configuration-revision attribute
added in Junos OS Release 20.4R1 and Junos OS Evolved Release 20.4R1.