Vyatta NOS documentation

Learn how to install, configure, and operate Vyatta Network Operating System (Vyatta NOS), which helps to drive our virtual networking and physical platforms portfolio.

Test a new configuration with the confirmed commit facility

An example of how to use the <confirmed/> element in the initial <commit> RPC, to test a new configuration.

Note: You must explicitly confirm the new configuration before the end of the timeout period — otherwise, the system will automatically revert to the previous configuration.

This is particularly useful when you wish to make configuration changes that risk loss of connectivity to Vyatta NOS.

The default timeout period is 600 seconds, but you may use the <confirm-timeout> option to change this.

If you specify a persist ID, then the confirming commit may be from another session but must include the ID in the <persist-id> tag.

Note: A confirming commit is simply a <commit> RPC without a <confirmed> tag.

In this example, we use the confirmed commit facility with a timeout period and a persist ID.

  1. Use the <confirmed> RPC.
    <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
      <commit>
        <confirmed/>
        <confirm-timeout>120</confirm-timeout>
        <persist>123456ABC</persist>
      </commit>
    </rpc>
    ]]>]]>
  2. Confirm the commit, or cancel it.
    To confirm:
    <rpc message-id="102" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
      <commit>
        <persist-id>123456ABC</persist-id>
      </commit>
    </rpc>
    ]]>]]>
    To cancel:
    <rpc message-id="103" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
      <cancel-commit>
        <persist-id>123456ABC</persist-id>
      </cancel-commit>
    </rpc>
    ]]>]]