Synchronizing The Routing Engine Configuration - Juniper EX9200 Features Manual

High availability feature guide ex series
Hide thumbs Also See for EX9200:
Table of Contents

Advertisement

High Availability Feature Guide for EX9200 Switches

Synchronizing the Routing Engine Configuration

54
If the routing protocol process (rpd) on the NSR master Routing Engine crashes, the
master Routing Engine simply restarts rpd (with no Routing Engine switchover), which
impacts routing protocol adjacencies and neighbors and results in traffic loss. To prevent
this negative impact on traffic flow, configure the
at the
[edit system]
hierarchy level. This configuration forces an NSR Routing Engine
switchover if rpd on the master Routing Engine crashes.
[edit system]
user@host# set switchover-on-routing-crash
To enable the routing platform to switch over to the backup Routing Engine when the
routing protocol process (rpd) fails rapidly three times in succession, include the
other-routing-engine
statement at the
level.
For more information about the
Administration Library.
When you configure nonstop active routing, you must also include the
statement at the
[edit system]
synchronized on both Routing Engines:
[edit system]
synchronize;
If you try to commit the nonstop active routing configuration without including the
statement, the commit fails.
synchronize
If you configure the
commit synchronize
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
OS 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.
CAUTION:
We recommend that you do not restart Routing Protocol Process
(rpd) on master Routing Engine after enabling nonstop active routing, as it
disrupts the protocol adjacency/peering sessions, resulting in traffic loss.
switchover-on-routing-crash
[edit system processes routing failover]
statement, see the Junos OS
other-routing-engine
hierarchy level so that configuration changes are
statement at the
Copyright © 2017, Juniper Networks, Inc.
statement
hierarchy
commit synchronize
commit
[edit system]
hierarchy level

Advertisement

Table of Contents
loading

Table of Contents