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

Committing and Synchronizing a Configuration on Redundant Control Planes

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 Router 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 synchronize command to commit the new configuration to both the master and the slave control planes. When issued, this command will save the current configuration to both Router 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, re0 and re1 configuration groups must be defined on each routing platform. For more information about configuration groups, see the JUNOS CLI User Guide.

Note: If you issue the synchronize command on a nonredundant Routing Engine system, the JUNOScript server will commit the configuration on the one control plane.

For more information about synchronizing configurations, see the following sections:

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