Juniper M Series Monitoring And Troubleshooting Manual page 624

M Series and T Series Routers Monitoring and Troubleshooting Guide
580
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
Election priority
Temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Serial ID
Start time
Uptime
Load averages:
Routing Engine status:
Slot 1:
Current state
Election priority
Temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Serial ID
Start time
Uptime
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
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.
Backup
Backup (default)
26 degrees C / 78 degrees F
2048 MB
12 percent
0 percent
0 percent
1 percent
0 percent
99 percent
210929000142
2004-05-12 13:14:30 PDT
5 days, 22 hours, 7 minutes, 9 seconds
1 minute 5 minute
0.07 0.02
Master
Master (default)
27 degrees C / 80 degrees F
2048 MB
13 percent
0 percent
0 percent
0 percent
0 percent
100 percent
210929000143
2004-04-05 17:08:41 PDT
42 days, 18 hours, 12 minutes, 45 seconds
configured and the connection
Copyright © 2012, Juniper Networks, Inc.
15 minute
0.00