Description

"show chassis cluster status" shows priority of redundancy-group 1 as 0, but the priorities are defined in the configuration

Symptoms

The SRX has priorities configured for redundancy-group 1:

{primary:node0}[edit]
root@DHCP-server# show chassis cluster
reth-count 2;
redundancy-group 1 {
    node 0 priority 100;
    node 1 priority 1;
}
redundancy-group 0 {
    node 0 priority 90;
    node 1 priority 10;
}

However, when you do a "show chassis cluster status", the priorities show up as 0: 

{primary:node0}[edit]
root@DHCP-server# run show chassis cluster status 
Cluster ID: 1 
Node name                  Priority     Status    Preempt  Manual failover

Redundancy group: 0 , Failover count: 1
    node0                   90          primary   no       no  
    node1                   10          secondary no       no  

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

Solution

If the fab link is down, then you could see a scenario where the priority in the show chassis cluster status command will show 0.  To verify this, issue the show interface terse  command to verify if your fab link is up or down.

Example:
With fab0 link set as ge-0/0/11, the interface status is as follows. The output indicates the fab0 link is set to ge-0/0/11, but as you can see, this link is down. 

{primary:node0}[edit]
root@DHCP-server# run show interfaces terse 
Interface               Admin Link Proto    Local                 Remote
ge-0/0/0                up    down
ge-0/0/1                up    down
ge-0/0/2                up    up  
ge-0/0/2.0              up    up   aenet    --> reth0.0
ge-0/0/3                up    down
ge-0/0/4                up    down
ge-0/0/5                up    down
ge-0/0/6                up    down
ge-0/0/7                up    down
ge-0/0/8                up    up  
ge-0/0/9                up    down
ge-0/0/10               up    down
ge-0/0/11               up    down
ge-0/0/11.0             up    down aenet    --> fab0.0

 

 

Once a solid link is provided for the fab interface, you should see priorities reflect the proper status.  The output of the interface status shows the fab0 link is up. 

{primary:node0}[edit]
root@DHCP-server# run show interfaces terse 
Interface               Admin Link Proto    Local                 Remote
ge-0/0/0                up    down
ge-0/0/1                up    down
ge-0/0/2                up    up  
ge-0/0/2.0              up    up   aenet    --> reth0.0
ge-0/0/3                up    down
ge-0/0/4                up    down
ge-0/0/5                up    down
ge-0/0/6                up    down
ge-0/0/7                up    down
ge-0/0/8                up    up  
ge-0/0/8.0              up    up   aenet    --> fab0.0


Now that the fab0 link is up, check the cluster status.  The priorities are as-expected: 

{primary:node0}[edit]
root@DHCP-server# run show chassis cluster status 
Cluster ID: 1 
Node name                  Priority     Status    Preempt  Manual failover

Redundancy group: 0 , Failover count: 1
    node0                   90          primary   no       no  
    node1                   10          secondary no       no  

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