Juniper JUNOS - NETWORK OPERATION GUIDE REV1 Network Operation Manual page 521

Jan 12 21:50:43 event = E_TMOUT, state = giveup, param = 0x0
Jan 12 21:50:43 send "you are the master" request
Jan 12 21:50:43 Failed to send RE mastership cmd. err = 65
Jan 12 21:50:43 Currentstate: giveup
Jan 12 21:50:43 new state = giveup
Jan 12 21:50:46 failed to send RE info/keepalive: errno=35, total=7 in the last
20 sec
Jan 12 21:50:46 failed to send RE info/keepalive: errno=35, total=7 in the last
20 sec
Jan 12 21:50:46 event = E_TMOUT, state = giveup, param = 0x0
Jan 12 21:50:46 send "you are the master" request
Jan 12 21:50:46 Failed to send RE mastership cmd. err = 65
Jan 12 21:50:46 Currentstate: giveup
Jan 12 21:50:46 new state = giveup
Jan 12 21:50:48 event = E_TMOUT, state = giveup, param = 0x0
Jan 12 21:50:48 send "you are the master" request
Jan 12 21:50:48 Failed to send RE mastership cmd. err = 65
Jan 12 21:50:48 Currentstate: giveup
Jan 12 21:50:48 new state = giveup
Jan 12 21:50:50 event = E_TMOUT, state = giveup, param = 0x0
Jan 12 21:50:50 send "you are the master" request
Jan 12 21:50:50 Failed to send RE mastership cmd. err = 65
Jan 12 21:50:50 Currentstate: giveup
Jan 12 21:50:50 new state = giveup
Jan 12 21:50:53 event = E_MAXTRY, state = giveup, param = 0x0
Jan 12 21:50:53 Currentstate: giveup
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
What It Means
state of the Routing Engine changed from master to giveup after the request chassis
routing-engine master release
Engine is not taking over mastership because it is unreachable. Eventually a timeout
( E_TMOUT ) occurs until the Routing Engine reaches the maximum number of
attempts permitted ( E_MAXTRY ). The output then shows the Routing Engine state
changing from giveup 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.
NextState:giveup
reason_code: 1
NextState:giveup
reason_code: 1
NextState:giveup
reason_code: 1
NextState:giveup
reason_code: 1
NextState:master
reason_code: 1
command was issued. However, the other Routing
Chapter 36: Host Redundancy Overview
Determining Why Mastership Switched
!
485