Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Confirmed Commit
The confirmed commit capability indicates that the device allows the <commit> operation to carry the <confirmed> and <confirm-timeout> parameters.
- <confirmed>: commits configuration data in the <candidate/> configuration database and converts the data into running configuration data, namely configuration data in the <running/> configuration database.
- <confirm-timeout>: specifies a timeout period for confirming the <commit> operation, in seconds. The default value is 600s. After the <commit> operation is performed, if the confirmation operation is not performed within the confirmation timeout period, the configuration data in the <running> configuration database is rolled back to the state before the <commit> operation, and the edited data in the <candidate> configuration database is discarded.
This capability is only available when the candidate configuration capability is supported. It applies mainly to service trial run and verification scenarios.
Capability ID
<capability>urn:ietf:params:netconf:capability:confirmed-commit:1.0</capability>
Submit the current configuration and set the timeout period for confirming the <commit> operation to 120s:
RPC request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <commit> <confirmed/> <confirm-timeout>120</confirm-timeout> </commit> </rpc>RPC reply:
<rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <ok/> </rpc-reply>
Previous
