Chapter 36: Host Redundancy Overview
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 NextState:giveup
reason_code: 1
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 NextState:giveup
reason_code: 1
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 NextState:giveup
reason_code: 1
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 NextState:giveup
reason_code: 1
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 NextState:master
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
What It Means The beginning of the log shows that keepalives are not being responded to and the state of the Routing Engine changed from master to giveup after the request chassis routing-engine master release command was issued. However, the other Routing
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.
Determining Why Mastership Switched !
485
JUNOS Internet Software Network Operations Guide: Hardware
Configuring the Backup Routing Engine to Assume Mastership on Failure of
Keepalives
Action Configure the backup Routing Engine to automatically assume mastership if it detects a loss of keepalive responses with the set chassis routing-engine statement at the [ edit ] hierarchy level:
[edit] user@host# set chassis redundancy failover on-loss-of-keepalives
By d
NOTE: By default, a backup Routing Engine does not assume mastership when a loss of keepalive responses occurs.
Sample Output [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
What it Means The results of issuing this command on the backup Routing Engine are as follows:
!
Every 20 seconds of keepalive loss, a message is added to the
/var/log/mastership file.
!
After keepalive-time passes, the backup Routing Engine attempts to claim mastership.
!
When the backup Routing Engine claims mastership, it continues to be master even after the other Routing Engine configured as master has successfully resumed operation. Therefore, if the backup Routing Engine claims mastership, you must manually switch mastership.
!
The default time before failover will occur is set to 300 seconds (5 minutes).
You can change the default keepalive time period with the set chassis redundancy keepalive-time time-in-seconds command (the range for keepalive-time is from 2 to 10,000 seconds).
!
Keepalive messages are sent every second.
486 !
Configuring the Backup Routing Engine to Assume Mastership on Failure of Keepalives
