Related
Documentation
Checklist for Monitoring Redundant Routing Engines on page 591•
Displaying Redundant Routing Engine Errors
Purpose To determine the details of the redundant Routing Engine error messages in the
redundancy log messages.
Action To view redundancy log messages, use the following command:
user@host> show log mastership
Sample Output
user@host> show log mastership
[...Output truncated...]
May 13 11:18:31 RE mastership msg error: subtype 52
May 13 11:18:32 failed to receive loss of keepalives from other RE for the last
20 sec
[...Output truncated...]
Meaning The /var/log/mastership file records error messages from redundancy logging. The file
records the time of the message and a description of the message. A message is logged
after 20 seconds of keepalive loss.
Related
Documentation
Checklist for Monitoring Redundant Routing Engines on page 591•
Manually Switch from Master to Backup Routing Engine
To manually switch from master to backup Routing Engine, or to force the backup Routing
Engine to become master, use the following command:
user@host> request chassis routing-engine master release
You can also use the following command:
user@host> request chassis routing-engine master switch
For routers with multiple Routing Engines only, you can control which Routing Engine is
the master.
CAUTION: For routers that have two Routing Engines, both Routing Engines
must be running Junos OS Release 4.0 or later. Do not run Junos OS Release
3.4 on one of the Routing Engines and Release 4.0 on the other. Junos OS
Release 3.4 does not support Routing Engine redundancy. If you are using
this release of the software, only one Routing Engine can be installed in either
slot in the router.
By default, the Routing Engine in slot 0 (RE0) is the master and the Routing Engine in
slot 1 (RE1) is the backup. To change the default master Routing Engine, include the
603Copyright © 2012, Juniper Networks, Inc.
Chapter 29: Monitoring Redundant Routing Engines
To Next Page
Loading...
Need help?
General
