Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

synchronize

Syntax

Hierarchy Level

Description

For devices with multiple Routing Engines only. Configure the commit command to automatically perform a commit synchronize action between dual Routing Engines within the same chassis. The Routing Engine on which you execute the commit command (the requesting Routing Engine) copies and loads its candidate configuration to the other (the responding) Routing Engine. Each Routing Engine then performs a syntax check on the candidate configuration file being committed. If no errors are found, the configuration is activated and becomes the current operational configuration on both Routing Engines.

Note:

If you configure the commit synchronize statement at the [edit system] hierarchy level and issue a commit in the primary Routing Engine, the primary configuration is automatically synchronized with the backup. However, if the backup Routing Engine is down when you issue the commit, the Junos OS displays a warning and commits the candidate configuration in the primary Routing Engine. When the backup Routing Engine comes up, its configuration will automatically be synchronized with the primary. A newly inserted backup Routing Engine automatically synchronizes its configuration with the primary Routing Engine configuration.

Note:

When you configure nonstop active routing (NSR), you must configure the commit synchronize statement. Otherwise, the commit operation fails.

Note:

Starting in Junos OS Release 20.2R1, when the commit synchronize statement is configured and the backup Routing Engine synchronizes its configuration with the primary Routing Engine, for example, when it is newly inserted, brought back online, or during a change in primary role, it also synchronizes the ephemeral configuration database.

On the TX Matrix router, synchronization only occurs between the Routing Engines within the same chassis. When synchronization is complete, the new configuration is then distributed to the Routing Engines on the T640 routers. That is, the primary Routing Engine on the TX Matrix router distributes the configuration to the primary Routing Engine on each T640 router. Likewise, the backup Routing Engine on the TX Matrix router distributes the configuration to the backup Routing Engine on each T640 router.

On the TX Matrix Plus router, synchronization only occurs between the Routing Engines within the switch-fabric chassis and when synchronization is complete, the new configuration is then distributed to the Routing Engines on the line-card chassis (LCC). That is, the primary Routing Engine on the TX Matrix Plus router distributes the configuration to the primary Routing Engine on each LCC. Likewise, the backup Routing Engine on the TX Matrix Plus router distributes the configuration to the backup Routing Engine on each LCC.

In EX Series Virtual Chassis configurations:

  • On EX4200 switches in Virtual Chassis, synchronization occurs between the switch in the primary role and the switch in the backup role.

  • On EX8200 switches in a Virtual Chassis, synchronization occurs only between the primary and backup XRE200 External Routing Engines.

Options

and-quit

(Optional) Quit configuration mode if the commit synchronization succeeds.
at

(Optional) Time at which to activate configuration changes.
comment

(Optional) Write a message to the commit log.
force

(Optional) Force a commit synchronization on the other Routing Engine (ignore warnings).
scripts

(Optional) Push scripts to the other Routing Engine.

Required Privilege Level

system—To view this statement in the configuration.

system-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 7.4.

Related Documentation