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

Specifying the merge Data Mode

By default, the NETCONF server merges new configuration data into the candidate configuration. Thus, if no edit-configuration mode is specified, the routers will merge the new configuration elements into the existing candidate configuration. Merging configurations is performed according to the following rules:

A configuration element (hierarchy level or configuration object) that exists in the candidate configuration but not in the new configuration remains unchanged.
A configuration element that exists in the new configuration but not in the candidate configuration is added to the candidate configuration.
If a configuration element exists in both configurations, the following results occur:
- If a child statement of the configuration element (represented by a child tag element) exists in the candidate configuration but not in the new configuration, it remains unchanged.
- If a child statement exists in the new configuration but not in the candidate, it is added to the candidate configuration.
- If a child statement exists in both configurations, the value in the new data replaces the value in the candidate configuration.

To explicitly specify that data be merged, the application can include the <default-operation> tag element with the value merge in the <edit-config> tag element:



<rpc>
    <edit-config>
        <default-operation>merge</default-operation> 

        <!- - other child tag elements of the <edit-config> tag element - ->
    </edit-config>
</rpc>
]]>]]>

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