MX-SPC3 Services Card

Software release

• Junos OS Release 19.3R2 and later

Description

Services Processing Card (SPC) with two SPUs of 256 GB memory.

• Power requirement: 650 W maximum

• Weight: Approximately 18 lb (8.3 kg)

Hardware features

• Two 10–Gigabit Ethernet small form-factor pluggable plus (SFP+) chassis cluster control ports for connecting multiple devices into a redundant chassis cluster.

• Fabric interfaces

• One Gigabit Ethernet switch that provides control connectivity to the Routing Engine.

• Two interfaces from the SCBs that enable the boards to be powered on and controlled.

• Physical SPC connectors

• Midplane connectors and power circuitry

• Each SPU includes:

  • Two 2.3-GHz CPUs

  • One Crypto Engine

  • 128 GB memory

• Two 128 GB solid state-drives (SSDs).

• LEDs on the faceplate that indicate the SPC and SPU status.

Supported Slots

• MX240–Any slot, except the bottom slot 0 () which is reserved for SCB/RE.

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

• MX960–Any slot, except slot 11 () , and slots 0 () or 1 () which are reserved for SCB/RE.

Compatibility

The MX-SPC3 services card is compatible end-to-end with the MX Series Switch Fabrics, Routing Engines and MPC line cards. See Table 1:

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 SPU SPU 0 and SPU 1:

• Off–The SPU is offline.

• Blinking Amber–The SPU is initializing.

• Green–The SPU initialization is done and it is operating normally.

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

SERVICE LED, one tricolor for each SPU SPU 0 and SPU 1:

• Off–The SPU is offline.

• Blinking Red–The SPU initialization is done.

• Blinking Amber–Service is initializing on the SPU.

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

• Solid Red–Service encountered an error or a failure.

HA LED, one tricolor:

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

• 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.

• Off–The node is not configured for clustering or it has been disabled by the dual membership and detection recovery process in reaction to a control link or fabric link failure.

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

• Green–Chassis cluster control port link is active.

• Off–No link.