Juniper SRX 5800, Hardware Manual, Page: 370 / 536

SPCs installed in slots 2 and 3, then you must replace the SPC in slot 2 first. This ensures that the central
point (CP) functionality is performed by an SRX5K-SPC-4-15-320 SPC.
•
If you are adding next-generation SRX5K-SPC3 SPCs to the chassis, you must install the new SPCs so
that a next-generation SRX5K-SPC3 is the SPC in the original lowest-numbered slot. For example, if the
chassis already has two second-generation SPCs installed in slots 2 and 3, you must install SRX5K-SPC3
SPCs in slots 0 or 1. You will need to make sure that an SRX5K-SPC3 SPC is installed in the slot providing
central point (CP) functionality so that the CP functionality is performed by an SRX5K-SPC3 SPC.
NOTE: Your services gateway cannot have a mix of SRX5K-SPC-2-10-40 SPCs and
SRX5K-SPC3 SPCs, but starting with Junos OS release 18.2R2 and then 18.4R1 but not
18.3R1 you can have a mix of SRX5K-SPC-4-15-320 SPCs and SRX5K-SPC3 SPCs.
•
If you are adding the second-generation SRX5K-SPC-4-15-320 SPCs or the next-generation SRX5K-SPC3
SPCs to a services gateway, the services gateway must already be equipped with high-capacity power
supplies and fan trays, and the high-capacity air filters. See Upgrading an SRX5600 Services Gateway from
Standard-Capacity to High-Capacity Power Supplies or Upgrading an SRX5600 Services Gateway from
Standard-Capacity to High-Capacity Power Supplies for more information.
If your installation does not meet these criteria, use the procedure in Installing an SRX5400 Services Gateway
SPC, or Installing an SRX5600 Services Gateway SPC, or “Installing an SRX5800 Services Gateway SPC” on
page 363 to install SPCs in your services gateway.
NOTE: During this installation procedure, you must shut down both devices, one at a time.
During the period when one device is shut down, the remaining device operates without a backup.
If that remaining device fails for any reason, you incur network downtime until you restart at
least one of the devices.
To replace SPCs in an Services Gateway cluster without incurring downtime:
1. Use the console port on the Routing Engine to establish a CLI session with one of the devices in the
cluster.
2. Use the show chassis cluster status command to determine which services gateway is currently primary,
and which services gateway is secondary, within the cluster.
3. If the device with which you established the CLI session in Step 2 is not the secondary node in the
cluster, use the console port on the device that is the secondary node to establish a CLI session.
4. Use the show chassis fpc pic-status command to check the status of all the cards on both the nodes.
371