ON THIS PAGE
<edit-config>
Usage
<rpc> <edit-config> <target> <candidate/> </target> <!-- EITHER --> <config> <configuration> <!-- tag elements representing the data to incorporate --> </configuration> </config> <!-- OR --> <config-text> <configuration-text> <!-- configuration data in text format --> </configuration-text> </config-text> <!-- OR --> <url format="(xml | text)"> <!-- location specifier for file containing data --> </url> <default-operation>(merge | none | replace)</default-operation> <error-option>(ignore-error | stop-on-error)</error-option> <test-option>(set | test-then-set)</test-option> </edit-config> </rpc> ]]>]]>
Description
Request that the NETCONF server incorporate configuration data into the candidate configuration or open configuration database. Provide the data in one of three ways:
Data stream of Junos XML elements—Include the
<config>
tag element to provide a data stream of Junos XML configuration tag elements to incorporate. The tag elements are enclosed in the<configuration>
tag element.Data stream of configuration data in text format—Include the
<config-text>
tag element to provide a data stream of CLI configuration statements to incorporate. The configuration statements are enclosed in the<configuration-text>
tag element.File containing configuration data—Include the
<url>
tag element to specify the location of a file that contains the Junos OS configuration to incorporate. The format of the configuration data can be Junos XML elements or CLI configuration statements.
If a client application issues the Junos XML protocol <open-configuration>
operation to open a specific
configuration database before executing the <edit-config>
operation on the target <candidate/>
, Junos OS performs the <edit-config>
operation on the open configuration database. Otherwise, the operation
is performed on the candidate configuration.
Contents
<config> |
Enclose the |
<configuration> |
Enclose configuration data in Junos XML format. This configuration data is provided as a data stream and is incorporated into the candidate configuration or open configuration database. For information about the syntax for representing the elements to create, delete, or modify, see Map Configuration Statements to Junos XML Tag Elements. |
<config-text> |
Enclose the |
<configuration-text> |
Enclose configuration data formatted as CLI configuration statements. This configuration data is provided as a data stream and is incorporated into the candidate configuration or open configuration database. |
<default-operation> |
(Optional) Specify how to incorporate the new configuration data into the candidate configuration or open configuration database, particularly when there are conflicting statements.
|
<error-option> |
(Optional) Specify how the NETCONF server handles errors encountered while it incorporates the configuration data.
|
<test-option> |
(Optional) Specify whether the NETCONF server validates the configuration data before incorporating it into the candidate configuration.
Regardless of the value provided, the NETCONF server performs a basic syntax check on the Junos
OS configuration data in the Note:
The ephemeral configuration database does not support using the
|
<url> |
Specify the full pathname of the file that contains the configuration data to load. When the configuration data is formatted as Junos XML tag elements, set
the |
The <target>
tag element and its
contents are explained separately.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.
<default-operation>
to
replace
, the device uses a load update
operation instead of a load override
operation to replace the
configuration. In load update operations, the device notifies only the Junos
processes that correspond to changed statements, thus minimizing possible
disruptions to the network.