Example: Synchronizing The Configuration On Both Routing Engines; Forcing A Synchronized Commit Operation - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Junos 10.3 Junos XML Management Protocol Guide

Forcing a Synchronized Commit Operation

142

Example: Synchronizing the Configuration on Both Routing Engines

The following example shows how to commit and synchronize the candidate configuration
on both Routing Engines.
Client Application
<rpc>
<commit-configuration>
<synchronize/>
</commit-configuration>
</rpc>
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
configuration and force the synchronization.
NOTE: When you use a
force-synchronize
configuration will be lost.
To force a synchronization, enclose the empty
tags in the <commit-configuration>
<rpc>
<commit-configuration>
<synchronize/>
<force-synchronize/>
</commit-configuration>
</rpc>
Junos XML Protocol Server
<rpc-reply xmlns:junos="URL ">
<commit-results>
<routing-engine>
<name>re0</name>
<commit-check-success/>
</routing-engine>
<routing-engine>
<name>re1</name>
<commit-check-success/>
</routing-engine>
<routing-engine>
<name>re1</name>
<commit-success/>
</routing-engine>
<routing-engine>
<name>re0</name>
<commit-success/>
</routing-engine>
</commit-results>
</rpc-reply>
command to override a locked
<force-synchronize/>
command, any uncommitted changes to the
<synchronize/>
and <rpc> tag elements:
and <force-synchronize/>
Copyright © 2010, Juniper Networks, Inc.