[Contents] [Prev] [Next] [Index] [Report an Error]

Synchronizing Configurations but Requiring Confirmation

To commit the candidate configuration on both Routing Engines but require confirmation for the commit to become permanent, the application encloses the <synchronize/>, <confirmed/>, and (optionally) <confirm-timeout> tag elements in <commit-configuration> and <rpc> tag elements:



<rpc>
    <commit-configuration>
        
<synchronize/> 

        
<confirmed/> 

            [<confirm-timeout>minutes</confirm-timeout>] 
    </commit-configuration>
</rpc>

The same rollback deadline applies to both Routing Engines and can be extended on both at once by again emitting the <synchronize/>, <confirmed/>, and (optionally) <confirm-timeout> tag elements on the Routing Engine where the tag elements were emitted the first time.

The <force-synchronize/> tag cannot be combined with the <confirmed/> and <confirm-timeout> tag elements.

For more information about confirmed commit operations, see Committing the Candidate Configuration Only After Confirmation.

[Contents] [Prev] [Next] [Index] [Report an Error]