This capability indicates that the device supports the <candidate/> configuration database storing configuration data that is about to be committed on the device.
The <candidate/> configuration database holds a complete set of configuration data that can be manipulated without impacting the device's current configuration. The <candidate/> configuration database serves as a work place for creating and manipulating configuration data.
Additions, deletions, and changes can be made to the data in the <candidate/> configuration database to construct the desired configuration data. The following operations can be performed at any time:
<commit>: converts all configuration data in the <candidate/> configuration database into running configuration data.
If the device is unable to commit all of the changes in the <candidate/> configuration database, the running configuration data remains unchanged.
<discard-changes>: discards configuration data that has not been committed from the <candidate/> configuration database. After this operation is performed, the configuration data in the <candidate/> configuration database remains the same as that in the <running/> configuration database.
A device establishes an independent <candidate/> configuration database for each NETCONF session.
RPC request:
<?xml version="1.0" encoding="utf-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<candidate/>
</target>
<config>
<ifm xmlns="urn:huawei:yang:huawei-ifm">
<interfaces>
<interface>
<name>GigabitEthernet1/0/0</name>
<mtu>1500</mtu>
</interface>
</interfaces>
</ifm>
</config>
</edit-config>
</rpc>
RPC reply:
<?xml version="1.0" encoding="utf-8"?>
<rpc-reply xmlns:nc-ext="urn:huawei:yang:huawei-ietf-netconf-ext"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
message-id="101"
nc-ext:flow-id="27">
<ok/>
</rpc-reply>