Committing And Synchronizing A Configuration On Redundant Control; Planes - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Junos 10.3 Junos XML Management Protocol Guide
Committing and Synchronizing a Configuration on Redundant Control Planes
140
Client Application
<rpc>
<commit-configuration>
<confirmed/>
<confirm-timeout>20</confirm-timeout>
</commit-configuration>
</rpc>
A Routing Engine resides within a control plane. For single-chassis configurations, there
is one control plane. In redundant systems, there are two control planes, the master plane
and the backup plane. In multichassis configurations, the control plane includes all
Routing Engines with the same Routing Engine designation. For example, all master
Routing Engines reside within the master control plane, and all backup Routing Engines
reside within the backup control plane.
Committing a configuration applies a new configuration to the device Engine. In a
multichassis configuration, once a change to the configuration has been committed to
the system, this change is propagated throughout the control plane using the distribution
function.
In a redundant architecture, you can issue the
configuration to both the master and the slave control planes. When issued, this command
will save the current configuration to both device Engines and commit the new
configuration to both control planes. On a multichassis system, once the configuration
has been committed on both planes, the distribution function will distribute the new
configuration across both planes. For more information on Routing Engine redundancy,
see the Junos High Availability Configuration Guide.
NOTE: In a multichassis architecture with redundant control planes, there is a difference
between synchronizing the two planes and distributing the configuration throughout
each plane. Synchronization only occurs between the Routing Engines within the same
chassis. Once this synchronization is complete, the new configuration is distributed to
all other Routing Engines within each plane as a separate distribution function.
Because synchronization happens across two separate control planes, synchronizing
configurations is only valid on redundant Routing Engine architectures. Further,
configuration groups must be defined on each routing, swtiching, or security platform.
re1
For more information about configuration groups, see the Junos CLI User Guide.
Junos XML Protocol Server
<rpc-reply xmlns:junos="URL ">
<commit-results>
<routing-engine>
<name>re1</name>
<commit-success/>
</routing-engine>
</commit-results>
</rpc-reply>
command to commit the new
synchronize
Copyright © 2010, Juniper Networks, Inc.
and
re0