[Contents] [Prev] [Next] [Index] [Report an Error]

## <edit-config>

#### Usage

`

    <rpc>
    <edit-config>
            <target>
                <candidate/>
            </target>

        <!- - EITHER - ->
            <config>
                <configuration>
                    <!- - tag elements representing the data to incorporate - ->
                </configuration>
            </config>

        <!- - OR - ->
            <url>
                <!- - location specifier for file containing data - ->
            </url>

            <default-operation>(merge | none | replace)</default-operation>
    <edit-config>
    </rpc>
    ]]>]]>

`

#### Description

Request that the NETCONF server incorporate configuration data into the candidate configuration. Provide the data in one of two ways:

- Include the <url> tag element to specify the location of a file that contains the XML configuration tag elements to incorporate.
- Include the <config> tag element to provide a data stream of XML configuration tag elements to incorporate. The tag elements are enclosed in the <configuration> tag element.

<config>—Encloses the <configuration> tag element.

<configuration>—Encloses the tag elements to incorporate into the candidate configuration, provided as a data stream. For information about the syntax for representing the elements to create, delete, or modify, see Mapping Configuration Statements to SRC XML Tag Elements and Changing Individual Configuration Elements.

<default-operation>—(Optional) Specifies how to incorporate the new configuration data into the candidate configuration, particularly when there are conflicting statements. The following are acceptable values:

- merge—Combines the new configuration data with the candidate configuration according to the rules defined in Setting the Default Mode for Incorporating New Configuration Data. This is the default mode if the<default-operation> tag element is omitted. It 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. (For information about the operation attribute, see Changing Individual Configuration Elements.)

- none—Retains each configuration element in the existing candidate 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. For more information, see Deleting Configuration Elements.

- replace—Discards the existing candidate configuration and replaces it with the new data. For more information, see Setting Replace Mode as the Default Mode.

<url>—Specifies the full pathname of the file that contains the configuration data to load. The file must reside on the local disk. For more information, see Providing Configuration Data in a File.

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

#### Usage Guidelines

See Changing Configuration Information.

#### Related Topics

]]>]]>, <rpc>, <target>

[Contents] [Prev] [Next] [Index] [Report an Error]