Juniper SRX 5800, Hardware Manual

Page: 373 / 536

NOTE: We strongly recommend that you perform the ISHU during a maintenance window, or
during the lowest possible traffic as the secondary node is not available at this time.
To install SRX5K-SPC3s in a services gateway that is part of a chassis cluster using the ISHU
procedure, the following conditions have to be met:
•
Each services gateway must have at least one SRX5K-SPC3 installed. ISHU is not supported
if you want to add SRX5K-SPC3s into a node that only contains SRX5K-SPC-4-15-320s.
•
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.
•
When you are adding a new SRX5K-SPC3 to a chassis, it must be installed in the
higher-numbered slot than any other installed SPCs in the chassis.
•
Installing SRX5K-SPC3s to the chassis cluster must not change the central point (CP)
functionality mode from Combo CP mode to Full CP mode.
When there are two or less than two SRX5K-SPC3s in the chassis, the CP mode is Combo CP
mode. More than two SRX5K-SPC3s in the chassis, the CP mode is Full CP mode.
•
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.
During this installation procedure, you must shut down both devices, one at a time. During the
period when one device is shut down, the other device operates without a backup. If that other
device fails for any reason, you incur network downtime until you restart at least one of the
devices.
To add SRX5K-SPC3s 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.
374