Juniper SRX5K-MPC-R

Software release

• Junos OS Release 9.2 and later

Cables and connectors

CHASSIS CLUSTER CONTROL 0 and CHASSIS CLUSTER CONTROL 1–SFP ports for control links in chassis cluster configurations.

Supported SFP transceivers:

1000BASE-LH (model numbers SRX-SFP-1GE-LH, SRX-SFP-1GE-LH-ET)

1000BASE-LX (model numbers SRX-SFP-1GE-LX, SRX-SFP-1GE-LX-ET)

1000BASE-SX (model numbers SRX-SFP-1GE-SX, SRX-SFP-1GE-SX-ET)

Controls

None

Supported Slots

• SRX5600–Any slot, except the bottom slots 0 or 1 which are reserved for SCB/RE.

• SRX5800–Any slot, except the slots 0 or 1 which are reserved for SCB/RE.

Power Requirement

Maximum 351 W

Weight

Approximately 13 lb (5.9 kg)

LEDs

OK/FAIL LED, one bicolor:

• Steady green–The SPC is operating normally.

• Red–The SPC has failed and is not operating normally.

• Off–The SPC is powered down.

STATUS LED, one tricolor for each of the two SPUs SPU 0 and SPU 1:

• Green–The SPU is operating normally.

• Amber–The SPU is initializing.

• Red–The SPU has encountered an error or a failure.

• Off–The SPU is offline. If all four SPUs are offline, it is safe to remove the SPC from the chassis.

SERVICE LED, one bicolor for each of the two SPUs, SPU 0 and SPU 1:

• Green–Service is running on the SPU under acceptable load.

• Amber–Service on the SPU is overloaded.

• Off–Service is not running on the SPU.

HA LED, one tricolor:

• Green (bold)–Clustering is operating normally. All cluster members and monitored links are available, and no error conditions are detected.

• Green (blinking)–Data transfer between the nodes.

• Red–A critical alarm is present on clustering. A cluster member is missing or unreachable, or the other node is no longer part of a cluster because it has been disabled by the dual membership and detection recovery process in reaction to a control link or fabric link failure.

• Amber–All cluster members are present, but an error condition has compromised the performance and resiliency of the cluster. The reduced bandwidth could cause packets to be dropped or could result in reduced resiliency because a single point of failure might exist. The error condition might be caused by:

  • The loss of chassis cluster links which causes an interface monitoring failure.

  • An error in an SPU or NPU.

  • Failure of the spu-monitoring or cold-sync-monitoring processes.

  • A chassis cluster IP monitoring failure.

LINK/ACT LED, one for each of the two ports CHASSIS CLUSTER CONTROL 0 and CHASSIS CLUSTER CONTROL 1:

• Green (flickering)–Chassis cluster control port link is active.

• Off–No link.

ENABLE LED, one for each of the two ports CHASSIS CLUSTER CONTROL 0 and CHASSIS CLUSTER CONTROL 1:

• Green–The chassis cluster control port is enabled.

• Off–The chassis cluster control port is disabled.