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

Replacing the Candidate Configuration with Newly Defined Data

To replace the entire candidate configuration with new configuration data, a client application can use either of two methods, as described in the following sections.

With either method, the NETCONF server confirms that it replaced the candidate configuration by returning the <ok/> tag in the <rpc-reply> tag element:




<rpc-reply xmlns="URN" xmlns:sdx=”URL">
    <ok/>
</rpc-reply>
]]>]]>

If the NETCONF server cannot replace the candidate configuration data, the <rpc-reply> tag element instead encloses an<rpc-error> tag element explaining the reason for the failure.

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