user@host# commit
To view the Routing Engine mastership/backup status, use the following CLI command
in operational mode:
user@host> show chassis routing-engine
user@host> show chassis routing-engine
Routing Engine status:
Slot 0:
Current state Backup
Election priority Backup (default)
Temperature 26 degrees C / 78 degrees F
DRAM 2048 MB
Memory utilization 12 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 1 percent
Interrupt 0 percent
Idle 99 percent
Serial ID 210929000142
Start time 2004-05-12 13:14:30 PDT
Uptime 5 days, 22 hours, 7 minutes, 9 seconds
Load averages: 1 minute 5 minute 15 minute
0.07 0.02 0.00
Routing Engine status:
Slot 1:
Current state Master
Election priority Master (default)
Temperature 27 degrees C / 80 degrees F
DRAM 2048 MB
Memory utilization 13 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 0 percent
Interrupt 0 percent
Idle 100 percent
Serial ID 210929000143
Start time 2004-04-05 17:08:41 PDT
Uptime 42 days, 18 hours, 12 minutes, 45 seconds
Each Routing Engine only checks its own configuration. Therefore, you must configure
the redundancy settings on both Routing Engines correctly for the system to operate
properly.
If both Routing Engines are configured as master, whichever Routing Engine comes up
first will be the master. When the second Routing Engine comes up, it will try to assume
mastership. However, the current master Routing Engine will reject this request, and the
second Routing Engine will become the backup.
If both Routing Engines are configured as backup and come up after bootup, neither
Routing Engine becomes master. The only way for either to become master is if one of
the host module components (such as the Routing Engine) is physically removed, or if
a Routing Engine has failover on-loss-of-keepalives configured and the connection
between Routing Engines is interrupted for a period of time. The resulting timeout due
to a loss of keepalives will force one of the Routing Engines to become the master.
Copyright © 2012, Juniper Networks, Inc.580
M Series and T Series Routers Monitoring and Troubleshooting Guide