Synchronizing The Configuration On Both Routing Engines - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Synchronizing the Configuration on Both Routing Engines

Copyright © 2010, Juniper Networks, Inc.
NOTE: If you issue the synchronize
the Junos XML protocol server will commit the configuration on the one control plane.
For more information about synchronizing configurations, see the following sections:
Synchronizing the Configuration on Both Routing Engines on page 141
Forcing a Synchronized Commit Operation on page 142
Synchronizing Configurations Simultaneously with Other Operations on page 143
To synchronize a configuration on a redundant Routing Engine system, a client application
needs to enclose the empty
tag elements:
<rpc>
<commit-configuration>
<synchronize/>
</commit-configuration>
</rpc>
The Junos XML protocol server verifies the configuration's syntactic correctness on the
Routing Engine where the
Engine), copies the configuration to the remote Routing Engine and verifies its syntactic
correctness there, and then commits the configuration on both Routing Engines.
The Junos XML protocol server encloses its response in
tag elements. It emits a separate
each Routing Engine:
If the syntax check succeeds on a Routing Engine, the
encloses the <commit-check-success/>
the name of the Routing Engine on which the check succeeded (
<routing-engine>
<name>(re0 | re1)</name>
<commit-check-success/>
</routing-engine>
If the configuration is incorrect, an
the error.
If the commit operation succeeds on a Routing Engine, the
encloses the <commit-success/>
name of the Routing Engine on which the commit operation succeeded:
<routing-engine>
<name>(re0 | re1)</name>
<commit-success/>
</routing-engine>
If the commit operation fails, an
the error. The most common causes of failure are semantic or syntactic errors in the
configuration.
command on a nonredundant Routing Engine system,
<synchronize/> tag in <commit-configuration>
<synchronize/> tag is emitted (referred to as the local Routing
<routing-engine> tag element for each operation on
tag and the
<xnm:error> tag element encloses a description of
tag and the <name>
<xnm:error> tag element encloses a description of
Chapter 6: Committing a Configuration
and
and
<rpc-reply> <commit-results>
tag element
<routing-engine>
<name> tag element, which reports
or ):
re0 re1
tag element
<routing-engine>
tag element, which reports the
<rpc>
141