This capability indicates that the device can perform a distinct startup. More specifically, the device can distinguish the <running/> configuration database from the <startup/> configuration database.
The NETCONF server must independently maintain the running configuration and be able to restore the running configuration after the device restarts. The configuration data of the <running/> configuration database is not automatically synchronized to the <startup/> configuration database. You must perform the <copy-config> operation to copy the data from the <running/> configuration database to the <startup/> configuration database.
Perform the <copy-config> operation to copy the data from the <running/> configuration database to the <startup/> configuration database:
RPC request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<copy-config>
<source>
<running/>
</source>
<target>
<startup/>
</target>
</copy-config>
</rpc>
RPC reply:
<rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <ok/> </rpc-reply>