A client application can completely replace the current candidate configuration, either with new data or by rolling back to a previous configuration.
![]() |
Note: To comply with the NETCONF specification, the NETCONF server accepts the <delete-config> tag element, which deletes the entire candidate configuration. However, a commit operation fails if the candidate configuration does not exist or is completely empty, so the application must use the <edit-config> or <copy-config> tag element to add data to the candidate configuration before committing it. See <delete-config>. |
For information about completely replacing the candidate configuration, see the following sections: