How to configure Control-link-recovery on Chassis Cluster and what does Control-link-recovery

Enable control link recovery to be done automatically by the system.

If the control link fails, the secondary node enters to ineligible and then to disabled state. If the control link recovers with in three consecutive responses, the device auto reboots irrespective of the state (ineligible or disable) of the node. You can reboot automatically using the control-link-recovery configuration option.

After the control link recovers, the system checks whether it receives at least three consecutive heartbeats on the control link. This is to ensure that the control link is not flapping and is perfectly healthy. Once this criterion is met, the system issues an automatic reboot on the node that was disabled when the control link failed. When the disabled node reboots, the node rejoins the cluster. There is no need for any manual intervention.

Configuration:

{primary:node0}

root@SRX4600_1> show chassis cluster status 

Monitor Failure codes:

  CS Cold Sync monitoring    FL Fabric Connection monitoring

  GR GRES monitoring       HW Hardware monitoring

  IF Interface monitoring    IP IP monitoring

  LB Loopback monitoring     MB Mbuf monitoring

  NH Nexthop monitoring     NP NPC monitoring        

  SP SPU monitoring       SM Schedule monitoring

  CF Config Sync monitoring   RE Relinquish monitoring

  IS IRQ storm

Cluster ID: 10

Node  Priority Status        Preempt Manual  Monitor-failures

Redundancy group: 0 , Failover count: 1

node0 255   primary       no   yes   None      

node1 200   secondary      no   yes   None   

{primary:node0}[edit]

root@SRX4600_1# set chassis cluster control-  

                      ^

'control-' is ambiguous.

Possible completions:

> control-interface  Disable/enable HA control-link interface

 control-link-recovery Enable automatic control link recovery. <<<<<<<<<<

{primary:node0}[edit]

root@SRX4600_1# set chassis cluster control-link-recovery ?

Possible completions:

 <[Enter]>      Execute this command

+ apply-groups     Groups from which to inherit configuration data

+ apply-groups-except Don't inherit configuration data from these groups

> configuration-synchronize Cluster configuration action

> control-interface  Disable/enable HA control-link interface

 heartbeat-interval  Interval between successive heartbeats (1000..2000 milliseconds)

 heartbeat-threshold Number of consecutive missed heartbeats to indicate device failure (3..8)

> network-management  Define parameters for network management

> redundancy-group   Set redundancy-group parameters

 reth-count      Number of redundant ethernet interfaces (1..128)

> traceoptions     Set chassis cluster traceoptions

 use-active-child-mac-on-reth Copy Child's physical MAC on RETH parent's current MAC

 use-actual-mac-on-physical-interfaces Use Hypervisor provided MAC for physical interfaces on virtual platforms

 |          Pipe through a command

{primary:node0}[edit]

root@SRX4600_1# set chassis cluster control-link-recovery   

{primary:node0}[edit]

root@SRX4600_1# show | compare 

[edit chassis cluster]

+  control-link-recovery;

{primary:node0}[edit]

root@SRX4600_1# commit 

node0: 

configuration check succeeds

node1: 

commit complete

node0: 

commit complete

Statement introduced in Junos OS Release 9.5.