Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

<commit>

Usage

Description

Request that the NETCONF server perform one of the variants of the commit operation on the candidate configuration or open configuration database. Table 1 describes the commit operations.

Note:

The <confirmed/> tag is not supported when committing configuration data to the ephemeral configuration database.

Table 1: Commit Operations
<commit> Operation     Description
<commit/>

Commit the configuration immediately, making it the active configuration on the device.

<commit>
    <confirmed/>
</commit>
    
<commit>
    <confirmed/>
    <confirm-timeout>rollback-delay</confirm-timeout>
</commit>
    

Commit the configuration but require an explicit confirmation for the commit to become permanent. If the commit is not confirmed, the configuration rolls back to the previous configuration after the specified time.

Optionally, include the <confirm-timeout> element to specify the rollback delay in the range from 1 through 4,294,967,295 seconds. By default, the rollback occurs after 600 seconds.

To delay the rollback again (past the original rollback deadline), emit the <commit><confirmed/></commit> tags before the deadline passes, and optionally include the <confirm-timeout> element. The rollback can be delayed repeatedly in this way.

To confirm the commit, emit the empty <commit/> tag before the rollback deadline passes. The device commits the candidate configuration and cancels the rollback.

Contents

<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 you omit this element, the server uses the default value.

  • Range: 1 through 4,294,967,295 seconds

  • Default: 600 seconds