Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Troubleshooting an SRX Chassis Cluster with One Node in the Primary State and the Other Node in the Disabled State

Problem

Description

The nodes of the SRX chassis cluster are in primary and disabled states.

Environment

SRX chassis cluster

Symptoms

One node of the cluster is in the primary state and the other node is in the disabled state. Run the show chassis cluster status command on each node to view the status of the node. Here is a sample output:

Diagnosis

  1. Run the show chassis cluster interfaces command to verify the status of the control and fabric links. Are any of the links down?

    Here are sample outputs for a branch SRX Series device and a high-end SRX Series device.

  1. Reboot the disabled node. Does the node come up in the disabled state after the reboot?

    • Yes: There might be hardware issues. Proceed to Step 3.

    • No: The issue is resolved.

  1. Check the node for any hardware issues. Run the show chassis fpc pic-status command on both nodes, and ensure that the FPCs are online. Do you see the status of any FPC listed as Present, OK, or Offline?

    Here is a sample output.

    • Yes: Reseat the cards and reboot the node. If this does not resolve the issue, open a case with your technical support representative for further troubleshooting. See Data Collection for Customer Support.

    • No: Proceed to Step 4.

  1. Run the show chassis cluster statistics on both nodes, and analyze the output.

    Does the Heartbeat packets received field show a non-increasing value or zero (0), or does the Heartbeat packet errors field show a non-zero value?

  1. Configure set chassis cluster no-fabric-monitoring (hidden option) and commit the configuration to temporarily disable fabric monitoring during the troubleshooting process. Reboot the disabled node. After the node reboots, run the show chassis cluster statistics command. Are the probes still lost?

    • Yes: Open a case with your technical support representative for further troubleshooting. See Data Collection for Customer Support

    • No: Delete the set chassis cluster no-fabric-monitoring configuration, and verify that everything is operational. If you notice any issue, open a case with your technical support representative for further troubleshooting. See Data Collection for Customer Support