<commit>

Usage

Description

Request that the NETCONF server perform one of the variants of the commit operation on the candidate configuration:

• To commit the configuration immediately, making it the active configuration on the device, emit the empty <commit/> tag.
• To commit the candidate configuration but require an explicit confirmation for the commit to become permanent, enclose the <confirmed/> tag in the <commit> tag element.

  By default, the NETCONF server rolls back to the previous running configuration after 10 minutes; to set a different rollback delay, also emit the optional <confirm-timeout> tag element. To delay the rollback again (past the original rollback deadline), emit the <confirmed/> tag (enclosed in the <commit> tag element) again before the deadline passes. Include the <confirm-timeout> tag element to specify how long to delay the next rollback, or omit that tag element to use the default of 10 minutes. 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 NETCONF server commits the candidate configuration and cancels the rollback. If the candidate configuration is still the same as the running configuration, the effect is the same as recommitting the current running configuration.

<confirmed>—Requests a temporary commit of the candidate configuration. The device reverts to the previous active configuration after a specified time.

<confirm-timeout>—Specifies the number of minutes before the device reverts to the previously active configuration. If this tag element is omitted, the default is 10 minutes.

Usage Guidelines

See Committing a Configuration.

Related Topics

• ]]>]]>
• <rpc>