The following sample RPC shows that the NETCONF server confirms that the candidate configuration is committed temporarily: xmlns="URN" xmlns:nc="URL"> If the NETCONF server cannot commit the candidate configuration, the element will enclose an element explaining the reason for the failure. The most common causes are semantic or syntactic errors in the candidate configuration. To delay the rollback to a time later than the current rollback timer, the client application sends a tag inside a tag element again before the deadline passes. Optionally, it includes the element to specify how long to delay the next rollback.
The client application can delay the rollback indefinitely by sending the tag repeatedly. To commit the configuration permanently, the client application sends the tag enclosed in an tag element before the rollback deadline passes. The rollback is canceled and the candidate configuration is committed immediately. If the candidate configuration is the same as the temporarily committed configuration, the temporarily committed configuration is recommitted.
If another application uses the tag element to terminate this application’s session while a confirmed commit is pending (this application has committed changes but not yet confirmed them), the NETCONF server that is using this session restores the configuration to its state before the confirmed commit instruction was issued. The candidate datastore is disabled by using the no netconf-yang feature candidate-datastore command. Because the candidate datastore confirmed commit is enabled when the candidate datastore is enabled, the confirmed commit is disabled when the candidate datastore is disabled. All sessions in progress are terminated, and the confd program is restarted.
Candidate Support Configuration The candidate datastore functionality can be enabled by using the netconf-yang feature candidate-datastore command. When the datastore state changes from running to candidate or back, a warning message is displayed, notifying the user that a restart of NETCONF or RESTCONF will occur in order for the change to take effect. If the selection of the candidate or running datastore is specified in the configuration when a NETCONF-YANG or RESTCONF confd process starts, a warning message appears as shown below:
Device(config)# netconf-yang feature candidate-datastore netconf-yang initialization in progress - datastore transition not allowed, please try again after 30 seconds If the selection of the candidate or running datastore is made after the NETCONF-YANG or RESTCONF confd process starts, the following apply: • If the netconf-yang feature candidate-datastore command is configured, the command enables the candidate datastore and prints the following warning: “netconf-yang and/or restconf is transitioning from running to candidate netconf-yang and/or restconf will now be restarted, and any sessions in progress will be terminated”.
Model-Driven Programmability Candidate Support Configuration Programmability Configuration Guide, Cisco IOS XE 17.16.x 179