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

   
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.