Description

How to do troubleshoot a Chassis Cluster in the Primary/Disabled state. 

This article is part of KB20641 - [SRX] Troubleshooting steps when the Chassis Cluster does not come up [juniper.net] and the  Resolution Guide -- SRX Chassis Cluster (High Availability) .

Symptoms

Verify Chassis Cluster (JSRP) and bring it up in a healthy state.

Solution

Before proceeding, run the following command to check the status of the control or fabric link.

{primary:node1}[edit]
root@SRX> show chassis cluster interfaces

Sample Output:

 

For a Branch series SRX services gateway device:

root@SRX> show chassis cluster interfaces
Control link 0 name: fxp1
Control link status: Up

Fabric interfaces:
Name Child-interface Status
fab0 ge-0/0/2 up
fab0 ge-2/0/6 up
fab1 ge-9/0/2 up
fab1 ge-11/0/6 up
Fabric link status: Up
 

For a High-End series SRX services gateway device:

{primary:node0}
root@SRX> show chassis cluster interfaces
Control link 0 name: em0
Control link 1 name: em1
Control link status: Up

Fabric interfaces:
Name Child-interface Status
fab0 ge-2/0/0 down
fab0
fab1
fab1
Fabric link status: Up
 

step1 Which link do you see as down when running the above command on your device:


step2   Reboot the disabled node to get out of that state. After reboot, is the node still going to "disabled" state ?


step3   Check the node for any hardware issues. Follow the output as shown below.

  Run the following command on both nodes and make sure that the FPC's are online. (FPC details may differ from output shown below)
 
{primary:node1}
root@SRX> show chassis fpc pic-status
node0:
--------------------------------------------------------------------------
Slot 0  Online  FPC
  PIC 0 Online  4x GE Base PIC
Slot 2  Online  FPC
  PIC 0 Online  24x GE gPIM
Slot 6  Online  FPC
  PIC 0 Online  2x 10G gPIM

node1:
--------------------------------------------------------------------------
Slot 0  Online  FPC
  PIC 0 Online  4x GE Base PIC
Slot 2  Online  FPC
  PIC 0 Online  24x GE gPIM
Slot 6  Online  FPC
  PIC 0 Online  2x 10G gPIM

Do you find any related FPC as Present, OK or Offline?

  • Yes - Try reseating the card(s) and rebooting the node. If this does not resolve the issue please continue with Step 6
  • No - Proceed with Step 4
 


step4   Run the command ‘show chassis cluster statistics’ on both the nodes and observe the output:

{primary:node0}
root@SRX> show chassis cluster statistics
Control link statistics:
    Control link 0:
        Heartbeat packets sent: 418410
        Heartbeat packets received: 418406
        Heartbeat packet errors: 0
Fabric link statistics:
    Probes sent: 418407
    Probes received: 414896
    Probe errors: 0

If received heartbeat packet is not incrementing or zero or the heartbeat packet error counter is having a non-zero value then go to Step 6.
Also if received probe packet is zero or the probe packet error counter is having a non-zero value then go to Step 5 .


step5   Configure 'set chassis cluster no-fabric-monitoring' (hidden option) and commit to temporarily disable fabric monitoring (for troubleshooting purposes). Then reboot the disabled node. After reboot, run command ‘show chassis cluster statistics’. Are the probes still lost?

  • Yes - Proceed to Step 6 .
  • No - Delete the command and confirm all is okay. If not then open a case with your technical support representative for further troubleshooting. Proceed to Step 6 .


step6   Capture the output of the following commands:

show chassis alarms
show chassis environment
show system alarms
show chassis cluster information
request support information

Collect these outputs on both nodes and proceed to open a case with your technical support representative as per KB21781 - [SRX] Data Collection Checklist - Logs/data to collect for troubleshooting [juniper.net] .

 

Modification History

2020-06-29: Removed J-Series references.