Commit Configuration
Commit the configuration to set the new values in the current running configuration.
The configuration can also be committed through a confimed-commit
operation. NETCONF supports confirmed-commit RPC. This RPC requires an explicit confirmation from the user before the configuration
takes effect on the router. This feature helps in verifying that the change in the configuration works correctly and does
not cause fluctuation in the management connectivity. If the configuration change causes loss of management connectivity,
the configuration is automatically rolled back to the previous committed configuration after the default confirm-timeout
period of 600 seconds.
To commit a configuration, use </commit> RPC:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<commit/>
</rpc>
To confirm-commit a configuration:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<commit>
<confirmed/>
</commit>
</rpc>
The confirmed-commit capability supports the <cancel-commit> operation and the <confirmed>, <confirm-timeout>, <persist>, and <persist-id> parameters for the <commit> operation.
<rpc message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<commit>
<confirmed/>
<persist>IQ,d4668</persist>
<confirm-timeout>120</confirm-timeout>
</commit>
</rpc>
A confirmed-commit request will fail with Datastore Locked
error if:
-
Another operation is performed between a confirmed-commit and a confirming-commit operation
-
Another session has an active confirmed-commit request and a persist ID was not provided
-
A persist ID was provided but did not match the persist ID of the active confirmed-commit session