Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

<edit-config>

Usage

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> tag element.
<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> tag element.
<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.

  • Default: merge

  • Values:

    • merge—Combine the new configuration data with the existing configuration according to the rules defined in Set the Edit Configuration Mode in a NETCONF Session. This mode applies to all elements in the new data that do not have the operation attribute in their opening container tag to specify a different mode.

    • none—Retain each configuration element in the existing configuration unless the new data includes a corresponding element that has the operation attribute in its opening container tag to specify an incorporation mode. This mode prevents the NETCONF server from creating parent hierarchy levels for an element that is being deleted. See Set the Edit Configuration Mode in a NETCONF Session.

    • replace—Discard the existing configuration data in the candidate configuration or open configuration database and replace it with the new data. See Replace the Candidate Configuration Using NETCONF.
<error-option>

(Optional) Specify how the NETCONF server handles errors encountered while it incorporates the configuration data.

  • Default: stop-on-error

  • Values:

    • ignore-error—Instruct the NETCONF server to continue incorporating the new configuration data even if it encounters an error.

    • stop-on-error—Instruct the NETCONF server to stop incorporating the new configuration data when it encounters an error.

<test-option>

(Optional) Specify whether the NETCONF server validates the configuration data before incorporating it into the candidate configuration.

  • Default: test-then-set

  • Values:

    • set—Do not perform validation

    • test-then-set—Perform validation and do not incorporate the data if the validation fails

Regardless of the value provided, the NETCONF server performs a basic syntax check on the Junos OS configuration data in the <edit-config> tag element. It performs a complete syntactic and semantic validation on the candidate configuration in response to the <validate> and <commit> tag elements, but not for the <edit-config> tag element.

Note:

The ephemeral configuration database does not support using the <test-option> element when loading configuration data into the database.
<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 <url> format attribute to "xml" or omit the attribute. When the configuration data is formatted as CLI configuration statements, set the <url> format attribute to "text". For more information, see Upload and Format Configuration Data in a NETCONF Session.

The <target> tag element and its contents are explained separately.

Related Documentation

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.

Release
Description
21.1R1 and 21.1R1-EVO
Starting in Junos OS Release 21.1R1 and Junos OS Evolved Release 21.1R1,when you set <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.