SPARC Mx-32 Servers: All Internal Disk LEDs Are Solidly On In DCU_2 And DCU

Asset ID:	1-72-2118426.1
Update Date:	2017-10-05
Keywords:

Solution Type Problem Resolution Sure

Solution 2118426.1 : SPARC Mx-32 Servers: All Internal Disk LEDs Are Solidly On In DCU_2 And DCU_3

Applies to:

SPARC M5-32 - Version All Versions and later
SPARC M6-32 - Version All Versions and later
Information in this document applies to any platform.

Symptoms

DCU_0 and DCU_1 the internal harddisks only have the Green LED on, blinking, Fault LED and Ready to Remove LED are off.
DCU_2 and DCU_3 the internal harddisks have the Green LED, Fault LED and Ready to Remove LED solidly on.

Changes

A factory build Mx-32 Server is having new hardware added, through an order of X-options to add to the machine.

Cause

The root cause of this issue is mixing Gen-1 and Gen-2 HDDPB and EMS FRUs. This is what you will find when checking the ILOM snapshot of the system:

/SYS/IOU2/HDDBP0:
  /FRU_IdentityR/FRU_Part_Number: 7058660
  /FRU_IdentityR/FRU_Revision_Level: 02
  /FRU_IdentityR/FRU_Serial_Number: 465769T+1322VU01LU

/SYS/IOU2/HDDBP1
  /FRU_IdentityR/FRU_Part_Number: 7058660
  /FRU_IdentityR/FRU_Revision_Level: 02
  /FRU_IdentityR/FRU_Serial_Number: 465769T+1322VU01LV

/SYS/IOU2/EMS1/CARD
  /FRU_IdentityR/FRU_Part_Number: 7074101
  /FRU_IdentityR/FRU_Revision_Level: 01
  /FRU_IdentityR/FRU_Serial_Number: 465769T+1527FJ042N

/SYS/IOU2/EMS2/CARD
  /FRU_IdentityR/FRU_Part_Number: 7074101
  /FRU_IdentityR/FRU_Revision_Level: 01
  /FRU_IdentityR/FRU_Serial_Number: 465769T+1552FJ04N6

/SYS/IOU2/EMS3/CARD
  /FRU_IdentityR/FRU_Part_Number: 7074101
  /FRU_IdentityR/FRU_Revision_Level: 01
  /FRU_IdentityR/FRU_Serial_Number: 465769T+1552FJ04N9

/SYS/IOU2/EMS4/CARD
  /FRU_IdentityR/FRU_Part_Number: 7074101
  /FRU_IdentityR/FRU_Revision_Level: 01
  /FRU_IdentityR/FRU_Serial_Number: 465769T+1552FJ04N4

/SYS/IOU3/HDDBP0:
  /FRU_IdentityR/FRU_Part_Number: 7058660
  /FRU_IdentityR/FRU_Revision_Level: 02
  /FRU_IdentityR/FRU_Serial_Number: 465769T+1322VU01PJ

/SYS/IOU3/HDDBP1
  /FRU_IdentityR/FRU_Part_Number: 7058660
  /FRU_IdentityR/FRU_Revision_Level: 02
  /FRU_IdentityR/FRU_Serial_Number: 465769T+1322VU01LX

/SYS/IOU3/EMS1/CARD
  /FRU_IdentityR/FRU_Part_Number: 7074101
  /FRU_IdentityR/FRU_Revision_Level: 01
  /FRU_IdentityR/FRU_Serial_Number: 465769T+1552FJ04ND

/SYS/IOU3/EMS2/CARD
  /FRU_IdentityR/FRU_Part_Number: 7074101
  /FRU_IdentityR/FRU_Revision_Level: 01
  /FRU_IdentityR/FRU_Serial_Number: 465769T+1552FJ04NH

/SYS/IOU3/EMS3/CARD
  /FRU_IdentityR/FRU_Part_Number: 7074101
  /FRU_IdentityR/FRU_Revision_Level: 01
  /FRU_IdentityR/FRU_Serial_Number: 465769T+1547FJ04M5

/SYS/IOU3/EMS4/CARD
  /FRU_IdentityR/FRU_Part_Number: 7074101
  /FRU_IdentityR/FRU_Revision_Level: 01
  /FRU_IdentityR/FRU_Serial_Number: 465769T+1552FJ04N5

When you poweron a HOST with such a mix of hardware, you will be warned:

2016-02-26 13:48:49 SP> NOTICE: Check for usable CPUs in /SYS/DCU2
2016-02-26 13:48:51 SP> NOTICE: Apply configuration rules to /SYS/DCU2
2016-02-26 13:48:52 SP> NOTICE: Warning: Invalid configuration of /SYS/DCU2. Reason: Mixing M5 and M6 HDDBP/BaseIO cards in the same DCU
2016-02-26 13:48:56 SP> NOTICE: Start Host in progress: Step 1 of 9

This message flags this known issue and should not be ignored.

The issue is described in the "SPARC M5-32 and SPARC M6-32 Servers Service Manual • December 2014", page 194 and onwards"

Please checkout the Oracle System Handbook at https://support.oracle.com/handbook_private/Systems/SPARC_M5_32/components.html#DiskBackplane:

- Drive Cage Assembly 7058660 requires Base-IO Board 7058671
- Drive Cage Assembly 7074234 requires Base-IO Board 7074101
- Disk Drive Cages cannot be mixed within a DCU / I/O column
- the disk drive cage is the HDDPBx
- the BASE-IO board is the EMSx/CARD

Solution

There is no way to fix this issue in software. Customer will need to work with the local sales team to get hold of a working combination of parts.

References

<BUG:16495219> - M*-32 HDDBP/BASEIO CANNOT MIX IN THE SAME DCU
<BUG:20483587> - HDDBP/BASE-IO CONFIGURATION RULES NOT WORKING

Attachments

This solution has no attachment