Juniper M Series Monitoring And Troubleshooting Manual page 629

Meaning
Related
Documentation
Configuring the Backup Routing Engine to Assume Mastership on Failure of Keepalives
Copyright © 2012, Juniper Networks, Inc.
reason_code: 1
Jan 12 21:50:53 timestamp: Wed
Jan 12 21:50:53 2000
Jan 12 21:50:53 new state = master
Jan 12 21:51:01 failed to receive keepalives from other RE for the last 100 sec
Jan 12 21:51:06 failed to send RE info/keepalive: errno=65, total=7 in the last
20 sec
Jan 12 21:51:06 failed to send RE info/keepalive: errno=65, total=7 in the last
20 sec
Jan 12 21:51:21 failed to receive keepalives from other RE for the last 120 sec
Jan 12 21:51:26 failed to send RE info/keepalive: errno=22, total=6 in the last
20 sec
Jan 12 21:51:26 failed to send RE info/keepalive: errno=22, total=6 in the last
20 sec
The beginning of the log shows that keepalives are not being responded to and the state
of the Routing Engine changed from
routing-engine master release
is not taking over mastership because it is unreachable. Eventually a timeout (
occurs until the Routing Engine reaches the maximum number of attempts permitted
( E_MAXTRY ). The output then shows the Routing Engine state changing from
back to .
master
The output doesn't indicate why the mastership switchover did not work. However, it is
clear that the backup Routing Engine is unreachable.
Understanding Redundancy for the Routing Engine, Host Module, and Host Subsystem
on page 565
Configure the backup Routing Engine to automatically assume mastership if it detects
a loss of keepalive responses with the
hierarchy level:
[edit]
user@host# set chassis redundancy failover on-loss-of-keepalives
NOTE: By default, a backup Routing Engine does not assume mastership
when a loss of keepalive responses occurs.
[edit]
user@host# set chassis redundancy failover on-loss-of-keepalives
[edit]
user@host# set chassis redundancy keepalive-time 300
[edit]
user@host# commit
commit complete
The results of issuing this command on the backup Routing Engine are as follows:
Chapter 28: Host Redundancy Overview
master to giveup after the
command was issued. However, the other Routing Engine
set chassis routing-engine
request chassis
)
E_TMOUT
giveup
statement at the [ ]
edit
585