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

Merging Configuration Elements

To merge configuration elements (hierarchy levels or configuration objects) into the candidate configuration, a client application emits the basic tag elements described in Changing Individual Configuration Elements.

To represent each element to merge in (either within the <config> tag element or in the file named by the <url> tag element), the application includes the tag elements representing its parent hierarchy levels and its container tag element, as described in Changing Individual Configuration Elements. Within the container tag, the application includes each of the element’s identifier tag elements (if it has them) and the tag element for each child to add or for which to set a different value. In the following, the identifier tag element is called <name>:



<configuration>
    <!- - opening tags for each parent of the element - ->
        <element> 

            <name>identifier</name>

            <!- - - child tag elements to add or change - ->
        </element> 

    <!- - closing tags for each parent of the element - ->
</configuration>

The NETCONF server merges in the new configuration element according to the rules specified in Setting the Edit Configuration Mode. As described in that section, the application can explicitly specify merge mode by including the <default-operation> tag element with the value merge in the <edit-config> tag element.

The following example shows how to merge information for a new interface called so-3/0/0 into the [edit interfaces] hierarchy level in the candidate configuration:

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