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

Forcing a Synchronized Commit Operation

The synchronize operation fails if the second Routing Engine's configuration is locked. If a synchronization failure occurs, it is best to determine the cause of the failure, take corrective action, and then synchronize the two Routing Engines again. However, when necessary, you can use the <force-synchronize/> command to override a locked configuration and force the synchronization.

Note: When you use a force-synchronize command, any uncommitted changes to the configuration will be lost.

To force a synchronization, enclose the empty <synchronize/> and <force-synchronize/> tags in the <commit-configuration> and <rpc> tag elements:



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

        
<force-synchronize/>

    </commit-configuration>
</rpc>

Note: In a multichassis environment, synchronization occurs between Routing Engines on the same chassis. Once the synchronization occurs, the configuration changes are propagated across each control plane using the distribution function. If one or more Routing Engines are locked during the distribution of the configuration, the distribution and thus the synchronization will fail. You will need to clear the error in the remote chassis and run the synchronize command again.

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