Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[SRX] Troubleshooting Priority 0 issue on Redundancy Groups with both nodes of a Chassis Cluster

0

0

Article ID: KB19431 KB Last Updated: 24 Oct 2013Version: 3.0
Summary:
This article describes the issueof the priority for a Redundancy Group on both nodes becoming 0 on SRX Branch devices.
Symptoms:
This article is applicable to the following Junos platforms:

  • SRX100

  • SRX210

  • SRX220

  • SRX240

  • SRX550

  • SRX650

The priority for both of the nodes is set to 0 under the redundancy groups as shown below:
{primary:node0}[edit]
root@srx# run show chassis cluster status
Cluster ID: 1
Node         Priority    Status  Preempt  Manual failover

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

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

Solution:
To troubleshoot this issue, perform the following procedure:
  1. Make sure that all the interfaces are physically up.The interface configuration for this example is as follows:
    ge-0/0/3, ge-9/0/3 -> reth0
    ge-2/0/5, ge-11/0/5 -> reth1
  2. Make sure that the fabric links are configured correctly and the corresponding member physical interfaces are up. Configuring the fabric links properly could resolve this issue. If the issue still persists, then refer to the next step.

  3. Check if interface monitoring is enabled on the RG and if more than one pair of interfaces (one pair belongs to one reth) is configured under monitoring:
    chassis {
        cluster {
            redundancy-group 1 {
                node 0 priority 200;
                node 1 priority 100;
                interface-monitor {
                    ge-0/0/3 weight 255;
                    ge-9/0/3 weight 255;;
                    ge-2/0/5 weight 255;
                    ge-11/0/5 weight 255;
                }
            }
        }
    }
  4. Deactivate the interface monitor, commit, and check the cluster status. If the priority is shown properly, then the issue is with the interfaces that are being monitored:
    {primary:node0}[edit]
    root@srx# deactivate chassis cluster redundancy-group 1 interface-monitor
    
    {primary:node0}[edit]
    root@srx# commit
    
    {primary:node0}[edit]
    root@srx# run show chassis cluster status
    Cluster ID: 1 
    Node        Priority   Status    Preempt  Manual failover
    
    Redundancy group: 0 , Failover count: 1
        node0   200        primary    no       no
        node1   100        secondary  no       no
    
    Redundancy group: 1 , Failover count: 8
        node0   200        secondary  no       no
    node1   100        primary    no       no
  5. To check which monitored interface is down, re-activate interface-monitor:
    {primary:node0}[edit]
    root@srx# rollback 1
    load complete
    
    {primary:node0}[edit]
    root@srx# commit
  6. Assuming that ge-0/0/3 and ge-2/0/5 are node0 interfaces and ge-9/0/3 and ge-11/0/5 are node1 interfaces, if only one interface from each node is up, then the priority for both the nodes under that RG will be set to 0:
    root@srx# run show interfaces terse | match reth
    ge-0/0/3.0   up up   aenet --> reth0.0
    ge-2/0/5.0   up down aenet --> reth1.0
    ge-9/0/3.0   up down aenet --> reth0.0
    ge-11/0/5.0  up up   aenet --> reth1.0
    reth0        up down
    reth0.0      up down inet 2.2.2.2/24
    reth1        up up
    reth1.0      up up   inet 3.3.3.3/24
    
    {primary:node0}[edit]
    root@srx# run show chassis cluster status
    Cluster ID: 1 
    Node        Priority   Status    Preempt  Manual failover
    
    Redundancy group: 0 , Failover count: 1
        node0   200        primary    no       no
        node1   100        secondary  no       no
    
    Redundancy group: 1 , Failover count: 9
        node0    0         secondary  no       no     node1    0         primary    no       no
  7. The following output is after both the interfaces on node 1 are brought back up; but not all interfaces are on node 0:
    {primary:node0}[edit]
    root@srx# run show interfaces terse | match reth
    ge-0/0/3.0  up up   aenet --> reth0.0
    ge-2/0/5.0  up down aenet --> reth1.0
    ge-9/0/3.0  up up   aenet --> reth0.0
    ge-11/0/5.0 up up   aenet --> reth1.0
    reth0       up up
    reth0.0     up up inet 2.2.2.2/24
    reth1       up up
    reth1.0     up up inet 3.3.3.3/24
    
    {primary:node0}[edit]
    root@srx# run show chassis cluster status
    Cluster ID: 1 
    Node    Priority   Status    Preempt  Manual failove
    Redundancy group: 0 , Failover count: 1
    node0   200        primary    no       no
    node1   100        secondary  no       no
    
    Redundancy group: 1 , Failover count: 10
    node0    0        secondary  no       no
    node1    100      primary    no       no
  8. The issue should be resolved, when all the interfaces under monitoring are brought up:
    {primary:node0}[edit]
    root@srx# run show interfaces terse | match reth
    ge-0/0/3.0  up up aenet --> reth0.0
    ge-2/0/5.0  up up aenet --> reth1.0
    ge-9/0/3.0  up up aenet --> reth0.0
    ge-11/0/5.0 up up aenet --> reth1.0
    reth0       up up
    reth0.0     up up inet 2.2.2.2/24
    reth1       up up
    reth1.0     up up inet 3.3.3.3/24
    
    {primary:node0}[edit]
    root@srx# run show chassis cluster status
    Cluster ID: 1 
    Node        Priority   Status    Preempt  Manual failover
    
    Redundancy group: 0 , Failover count: 1
        node0   200        primary    no       no
        node1   100        secondary  no       no
    
    Redundancy group: 1 , Failover count: 10
        node0    200        secondary no       no
        node1    100        primary   no       no
  9. If all the interfaces are shown as up, but still the priority remains at 0 on both or either one of the nodes, then check if the failover count; if it is increasing, which means that the interface is flapping, you will have to check for the interface statistics. This could be a physical link or possibly a hardware issue.


The configuration used in this article is as follows:
{primary:node0}[edit]
root@srx# show chassis
cluster {
    control-link-recovery;
    reth-count 7;
    heartbeat-interval 2000;
    heartbeat-threshold 8;
    redundancy-group 0 {
        node 0 priority 200;
        node 1 priority 100;
    }
    redundancy-group 1 {
        node 0 priority 200;
        node 1 priority 100;
        interface-monitor {
            ge-0/0/3 weight 255;
            ge-9/0/3 weight 255;
            ge-2/0/5 weight 255;
            ge-11/0/5 weight 255;
        }
    }
}
{primary:node0}[edit]
root@srx# show interfaces
ge-0/0/3 {
    gigether-options {
    redundant-parent reth0;
    }
}
ge-2/0/5 {
    gigether-options {
        redundant-parent reth1;
    }
}
ge-9/0/3 {
    gigether-options {
        redundant-parent reth0;
    }
}
ge-11/0/5 {
    gigether-options {
        redundant-parent reth1;
    }
}
fab0 {
    fabric-options {
        member-interfaces {
            ge-0/0/2;
        }
    }
}
fab1 {
    fabric-options {
        member-interfaces {
            ge-9/0/2;
        }
    }
}
reth0 {
    redundant-ether-options {
        redundancy-group 1;
    }
    unit 0 {
        family inet {
            address 2.2.2.2/24;
        }
    }
}
reth1 {
    redundant-ether-options {
        redundancy-group 1;
    }
    unit 0 {
        family inet {
            address 3.3.3.3/24;
        }
    }
}
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search