Using The Redundant Routing Engine Configuration - Juniper M Series Monitoring And Troubleshooting Manual

Hide thumbs Also See for M Series:
Table of Contents

Advertisement

Related
Documentation

Using the Redundant Routing Engine Configuration

Purpose
Action
Copyright © 2012, Juniper Networks, Inc.
After 2 seconds of keepalive loss, a message is logged.
1.
After 2 seconds of keepalive loss, the backup Routing Engine attempts to assume
2.
mastership. An alarm is generated whenever the backup Routing Engine is active, and
the display is updated with the current status.
Once the backup Routing Engine assumes mastership, it continues to function as
3.
master even after the originally configured master Routing Engine has successfully
resumed operation. You must manually restore it to its previous backup status.
However, if at any time one of the Routing Engines is not present, the other Routing
Engine becomes master automatically, regardless of how redundancy is configured.
Checklist for Monitoring Redundant Routing Engines on page 591
For routers with redundant Routing Engines, you can configure a master and backup
Routing Engine. By default, the Routing Engine in slot
Engine in slot
is the backup. Once configured, you can specify the Routing Engine to
RE1
assume mastership automatically if it detects loss of the keepalive signal from the master.
You can configure Routing Engine redundancy in the configuration mode at the
chassis redundancy]
hierarchy level.
NOTE:
We recommend that both Routing Engines have the same
configuration. When changing the configuration on a Routing Engine, commit
it to both Routing Engines using the
[
edit
] hierarchy level.
You can configure redundant Routing Engine automatic failover for the backup Routing
Engine with a specified failover time. By default, automatic failover is disabled. To enable
it, include the
failover on-loss-of-keepalives
hierarchy level. By default, failover will occur after 300 seconds (5 minutes) unless a
different time is specified. The failover time is indicated by the
statement at the
[edit chassis redundancy]
time is from 2 to 10,000 seconds.
To display the current Routing Engine redundancy configuration:
Enter configuration mode using the following command:
1.
user@host# configure
From the
[edit chassis redundancy]
2.
following command:
user@host# show
To display the current Routing Engine configuration, you can also use the following
command:
Chapter 29: Monitoring Redundant Routing Engines
RE0
is the master, and the Routing
commit synchronize
statement at the
[edit chassis redundancy]
keepalive-timeseconds
hierarchy level. The range for the keepalive
hierarchy level, show the configuration using the
[edit
statement at the
599

Advertisement

Table of Contents
loading

This manual is also suitable for:

T series

Table of Contents