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

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 fails.

If you configure the commit synchronize statement at the [edit system] hierarchy level and issue a commit in the master Routing Engine, the master configuration is automatically synchronized with the backup.

However, if the backup Routing Engine is down when you issue the commit, the JUNOS system software displays a warning and commits the candidate configuration in the master Routing Engine. When the backup Routing Engine comes up, its configuration will automatically be synchronized with the master.

Note: A newly inserted backup Routing Engine automatically synchronizes its configuration with the master Routing Engine configuration.

When you configure nonstop active routing, you can bring the backup Routing Engine online after the master Routing Engine is already running. There is no requirement to start the two Routing Engines simultaneously.


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