Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Virtual Chassis

  • Commit process optimization (EX4100-48MP, EX4100-24P, and EX4100-24T)—Using the fast-synchronize feature, optimize the commit time on Junos OS EX Series Virtual Chassis devices. You can perform commit checks and commit activations in parallel across all Virtual Chassis members. You can validate the configuration only on the primary Virtual Chassis device where you perform the commit operation.

    [See commit (System) and Synchronizing Configurations Across Routing Engines.]

  • Synchronize Virtual Chassis configuration using SCP (EX4300-MP, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48MXP, EX4400-48XP, EX4400-48P, EX4400-48T, QFX5120-32C, QFX5120-48T, QFX5120-48T-VC, QFX5120-48Y, QFX5120-48Y-VC, and QFX5120-48YM)—You can use Secure Copy Protocol (SCP) to securely transfer configuration data in a Virtual Chassis from the Virtual Chassis member in the primary Routing Engine role to a Virtual Chassis member in the backup Routing Engine role or line-card role. Synchronization occurs when a configuration is committed on the primary Virtual Chassis member, when a line-card member reboots, or when a new line-card member is added to the Virtual Chassis. When FIPS is enabled, the system uses SCP by default to synchronize configuration data.

    You must enable the system commit config-sync-with-scp configuration to use SCP for synchronization.

    [See Configure Synchronization of Configuration Data Using SCP in a Virtual Chassis.]