Synchronizing the Routing Engine Configuration
When you configure nonstop active routing, you
must also include the commit synchronize statement at the [edit system] hierarchy level so that configuration changes
are synchronized on both Routing Engines:
[edit system] commit synchronize;
If you try to commit the nonstop active routing configuration
without including the commit synchronize statement, the
commit operation fails.
If you issue the commit synchronize command at the [edit] hierarchy level on the backup Routing Engine, the Junos
system software displays a warning and commits the candidate configuration.
A newly inserted backup Routing Engine automatically synchronizes its configuration with the primary Routing Engine configuration.
When you configure nonstop active routing, you can bring the backup Routing Engine online after the primary Routing Engine is already running. There is no requirement to start the two Routing Engines simultaneously.