Request that the NETCONF server perform one of the variants of the commit operation on the candidate configuration or open configuration database:
To commit the configuration immediately, making it the active configuration on the device, emit the empty
To commit the configuration but require an explicit confirmation for the commit to become permanent, enclose the
<confirmed/>tag in the
<confirmed/>tag is not supported when committing configuration data to the ephemeral configuration database.
If the commit is not confirmed, the configuration rolls back to the previous configuration after a short time. By default, the rollback occurs after 600 seconds (10 minutes). To set a different rollback delay, include the
<confirm-timeout>tag element, and specify the number of seconds in the range from 1 through 4,294,967,295 seconds.
To delay the rollback again (past the original rollback deadline), emit the
<confirmed/>tag (enclosed in the
<commit>tag element) before the deadline passes, and optionally include the
<confirm-timeout>element to specify a delay that is different from the default. The rollback can be delayed repeatedly in this way.
To commit the configuration immediately and permanently after emitting the
<confirmed/>tag, emit the empty
<commit/>tag before the rollback deadline passes. The device commits the candidate configuration and cancels the rollback. If the candidate configuration is still the same as the current commited configuration, the effect is the same as recommitting the current committed configuration.
<confirmed>—Request a temporary commit of the candidate configuration. If the commit is not confirmed, the device reverts to the previous active configuration after a specified time, which is 600 seconds (10 minutes) by default.
<confirm-timeout>—Specify the number of seconds before the device reverts to the previously active configuration. If this tag element is omitted, the default value is used.
Range: 1 through 4,294,967,295 seconds
Default: 600 seconds