Behavior of the SRX5400, SRX5600, and SRX5800 Services Gateways
When the SRX5K-SCBE and SRX5K-RE-1800X4 in a Chassis Cluster Fail
It is important to understand the behavior of the SRX5400, SRX5600, and SRX5800 Services Gateways
when the Switch Control Board (SRX5K-SCBE) and Routing Engine (SRX5K-RE-1800X4) in the chassis
cluster fail.
NOTE: This procedure is also applicable for SCB3 except that SCB3 redundancy is supported.
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.
NOTE: The SRX5K-SCBE and SRX5K-RE-1800X4 are not hot-swappable.
NOTE: Four fabric planes must be active at any time in a chassis cluster. If fewer than four fabric
planes are active, then the Redundancy Group (RG1+) will fail over to the secondary node.
Table 55 on page 364 shows the minimum fabric plane requirements for the SCB.
Table 55: Expected Device Behavior and Minimum SRX5K-SCBE and Fabric Plane Requirements
Expected Behavior After the SCB and
Routing Engine are Removed
Redundant
Planes
Active
Planes
Number of
SRX5K-SCBsPlatform
If the SCB in the primary node fails, the device
will fail over to the secondary node as the
primary node powers off.
0 (virtual)4 (virtual)1SRX5400
If the active SCB in the primary node fails, the
behavior of the device does not change as the
redundant SCB becomes active provided all
four fabric planes are in good condition.
If the second SCB in the primary node fails,
the device will fail over to the secondary node
as the primary node powers off.
4 (virtual)4 (virtual)2SRX5600
364