cisco IOS XE 17.16.x — Confirmed Candidate Configuration Commit

Figure 4: Modifying Candidate Datastore Steps 1. Lock the running datastore. 2. Lock the candidate datastore. 3. Make modifications to the candidate configuration through edit-config RPCs with the target candidate. 4. Commit the candidate configuration to the running configuration. 5. Unlock the candidate and running datastores. Confirmed Candidate Configuration Commit The candidate configuration supports the confirmed commit capability. This implementation is as specified in RFC 6241 for the confirmed commit capability which, when issued, sets the running configuration to the current contents of the candidate configuration and starts a confirmed commit timer.

The confirmed commit operation will be rolled back if the commit is not issued within the timeout period. The default timeout period is 600 seconds or 10 minutes. When you commit the candidate configuration, you can require an explicit confirmation for the commit to become permanent. The confirmed commit operation is useful for verifying that a configuration change works correctly and does not prevent management access to the device. If the change prevents access or causes other errors, the automatic rollback to the previous configuration restores access after the rollback deadline passes.

If the commit is not confirmed within the specified amount of time,by default, the device automatically retrieves and commits (rolls back to) the previously committed configuration. RESTCONF does not support confirmed commit. Note In a NETCONF session, to commit the candidate configuration and to explicitly confirm the commit to become permanent, a client application encloses the empty tag in the and tag elements: The following sample RPC shows how to change the default rollback timer: nnn !nnn is the rollback-delay in seconds. Model-Driven Programmability Confirmed Candidate Configuration Commit Programmability Configuration Guide, Cisco IOS XE 17.16.x 178