Description

This article explains how to install SPC or SPC II modules in an existing SRX5000 chassis cluster using the simultaneous reboot method.

Prerequisites:-

  • If the chassis cluster is operating in active-active mode, you must transition it to active-passive mode before using this procedure. You transition the cluster to active-passive mode by making one node primary for all redundancy groups.

>show chassis cluster status
 
root@srx5K> show chassis cluster status 
Mar 13 21:32:41
Monitor Failure codes:
    CS  Cold Sync monitoring        FL  Fabric Connection monitoring
    GR  GRES monitoring             HW  Hardware monitoring
    IF  Interface monitoring        IP  IP monitoring
    LB  Loopback monitoring         MB  Mbuf monitoring
    NH  Nexthop monitoring          NP  NPC monitoring              
    SP  SPU monitoring              SM  Schedule monitoring
    CF  Config Sync monitoring      RE  Relinquish monitoring
 
Cluster ID: 1
Node   Priority Status               Preempt Manual   Monitor-failures
 
Redundancy group: 0 , Failover count: 1
node0  100      primary              no      no       None           
node1  1        secondary            no      no       None           
 
Redundancy group: 1 , Failover count: 1
node0  100      primary              yes     no       None           
node1  1        secondary            yes     no       None           
 
Redundancy group: 2 , Failover count: 1
node0  100      secondary            yes     no       None           
node1  1        primary              yes     no       None    
 
>request chassis cluster failover redundancy group 2 node 0

  • To install first-generation SRX5K-SPC-2-10-40 SPCs, both of the services gateways in the cluster must be running Junos OS Release 11.4R2S1, 12.1R2, or later.

  • To install next-generation SRX5K-SPC-4-15-320 SPCs, both of the services gateways in the cluster must be running Junos OS Release 12.1X44-D10, or later.

  • You must install SPCs of the same type and in the same slots in both of the services gateways in the cluster. Both services gateways in the cluster must result in the same physical configuration and slot locations post upgrade.

  • If you are adding first-generation SRX5K-SPC-2-10-40 SPC in an existing cluster installed with next-generation SRX5K-SPC-4-15-320 SPC, you must install the new SPCs so that a next-generation SRX5K-SPC-4-15-320 SPC is the SPC in the original lowest-numbered slot. For example, if the chassis already has two first-generation SPCs installed in slots 2 and 3, you cannot install SRX5K-SPC-4-15-320 SPCs in slots 0 or 1. You will need to make sure that an SRX5K-SPC-4-15-320 SPC is installed in the slot providing center point (CP) functionality (in this case, slot 2). This ensures that the CP functionality is performed by an SRX5K-SPC-4-15-320 SPC.

  • If you are replacing next-generation SRX5K-SPC-4-15-320 SPCs in the services gateways, both services gateways must already be equipped with high-capacity power supplies and fan trays.

  • Console connections to both chassis cluster nodes are necessary to allow unique config adjustments and due to device power off via 'halt' method used.

Solution

  • This procedure was compiled with the assumption that node0 is the primary for control plane (RG0) and data plane (RG1+) and configured with higher priority than the secondary node. Ensure you have two separate console CLI sessions to each node before proceeding with the steps below.  Allow ~15 minutes after reboot for the respective node to come up with all its modules online in the procedure. 

  1. Disable TCP SYN check and sequence check
     
    set security flow tcp-session no-syn-check
    set security flow tcp-session no-sequence-check
     
  2. Disable preempt for all RG1+ groups
     
    deactivate chassis cluster redundancy-group 1 preempt
    deactivate chassis cluster redundancy-group 2 preempt

  3. Disable interface-monitoring, ip-monitoring and control-link recovery features if used
     
    deactivate chassis cluster redundancy-group 1 interface-monitor
    deactivate chassis cluster redundancy-group 1 ip-monitoring
    deactivate chassis cluster redundancy-group 2 interface-monitor
    deactivate chassis cluster redundancy-group 2 ip-monitoring
    deactivate chassis cluster control-link-recovery  

  4. Commit the configuration from steps 1 through 3
     
    >commit

  5. Power down both nodes, unplug the power cables and install new/updated SPC module(s) in accordance with prerequisites given above
    >request system power-off

  6. Once the modules are installed, plug the power cables back to both the nodes for it to boot up.
    After login, verify chassis bootup with all its modules online with below commands:
     
    >show version
    >show chassis fpc pic-status
    >show chassis cluster status 

  7. Post the cluster becomes stable, reconfigure any/all features added/disabled in steps 1, 2 and 3 (interface-monitoring, IP-monitoring, control-link-recovery, TCP syn/seq checks) except 'preempt'.

    delete security flow tcp-session no-syn-check
    delete security flow tcp-session no-sequence-check
    activate chassis cluster redundancy-group 1 interface-monitor
    activate chassis cluster redundancy-group 1 ip-monitoring
    activate chassis cluster redundancy-group 2 interface-monitor
    activate chassis cluster redundancy-group 2 ip-monitoring
    activate chassis cluster control-link-recovery
    commit

  8. Verify if the RG states are back online with the correct priority and that interface monitoring and ip-monitoring are working correctly

    >show chassis cluster status
    >show chassis cluster ip-monitoring status
    >show chassis cluster interfaces

  9. Enable “preempt” for RG1+ groups, if previously used. 
    Note: Enabling preempt may result in RG1+ failover depending on the RG priority configured for the data RG groups

    activate chassis cluster redundancy-group 1 preempt
    activate chassis cluster redundancy-group 2 preempt

Modification History

2024-11-22 : Article Created