How to find the cause of the secondary node in disabled state in a Chassis Cluster.

Secondary node is in disabled state, how to find the reason why the secondary node went to Disabled state.

1. Run the "show chassis cluster information detail no-forwarding" command to help find the reason for the secondary node in a Disabled state. 

2. In the example below the Control link failed, which caused the secondary Node to go into the "ineligible" state and then if the timer expires, it goes to Disabled. 

3. In the below example the  " Ineligible timer expired " and still the control link is down. So went to the ineligible state. 

   root@lab-srx> show chassis cluster information detail no-forwarding
   
   Redundancy mode:
       Configured mode: active-active
       Operational mode: active-active
   Cluster configuration:
       Heartbeat interval: 1000 ms
       Heartbeat threshold: 3
       Control link recovery: Disabled
       Fabric link down timeout: 66 sec
   Node health information:
       Local node health: Not healthy
       Remote node health: Not healthy
   Redundancy group: 0, Threshold: 255, Monitoring failures: none
       Events:
           Apr 29 02:19:23.205 : secondary->ineligible, reason: Control link failure
           Apr 29 02:22:23.231 : ineligible->disabled, reason: Ineligible timer expired
   
   Redundancy group: 1, Threshold: 0, Monitoring failures: interface-monitoring
       Events:
           Apr 29 02:19:23.205 : secondary->ineligible, reason: Control link failure
           Apr 29 02:22:23.231 : ineligible->disabled, reason: Ineligible timer expired
   
   Redundancy group: 2, Threshold: 0, Monitoring failures: interface-monitoring
       Events:
           Apr 29 02:19:23.205 : secondary->ineligible, reason: Control link failure

    

4. To find the root cause of the Control link failure , check the JSRPD log under /var/log on both node0 and node1 in the Chassis Cluster: 

   root@lab-srx> show log jsrpd