Description

How to do troubleshoot to a Chassis Cluster showing as Primary/Secondary but still not acting as a healthy cluster.

This article is part of the Resolution Guide -- SRX Chassis Cluster (High Availability) .
 

Symptoms

The goal of this article is to verify that a Chassis Cluster in a Primary/Secondary state has the proper priority. 

Solution

step1   Run the command show chassis cluster status on either node to verify the Chassis Cluster status:

{primary:node0}
root@J-SRX> show chassis cluster status 
Cluster ID: 1 
Node                  Priority          Status    Preempt  Manual failover

Redundancy group: 0 , Failover count: 1
    node0                   100         secondary      no       no  
    node1                   150         primary        no       no  

Redundancy group: 1 , Failover count: 1
    node0                   100         secondary      no       no  
    node1                   150         primary        no       no  
Do you see one node with the status of primary and one node with the status of secondary ?
step2   What is the priority of each node?
step3   If the priority for both nodes is between 1 and 254, it means that the Chassis Cluster is in a healthy state.

Each Redundancy Group (other than Redundancy Group 0) contains one or more redundant Ethernet interfaces. A redundant Ethernet interface is a pseudo interface that contains a pair of physical Gigabit Ethernet interfaces or a pair of Fast Ethernet interfaces. If a Redundancy Group is active on node 0, then the child links of all the associated redundant Ethernet interfaces on node 0 are active. If the redundancy group fails over to node 1, then the child links of all redundant Ethernet interfaces on node 1 become active.

Now that you have verified that the Chassis Cluster is in a healthy state, refer to the Understanding Failover section of the Technical Documentation and KB15911 - Troubleshoot High Availability [juniper.net] .

For troubleshooting help, refer to Resolution Guide -- SRX Chassis Cluster (High Availability) .
 

Modification History

2023-10-18: Minor modification in the solution section and updated categories.