Sun Ultra 20 Workstation
 
Sun Fire V20z Server
 
Sun Java Workstation W1100z
 
Sun Fire X4200 Server
 
Sun Ultra 40 Workstation
 
Sun Fire X4200 M2 Server
 
Sun Fire X4600 M2 Server
 
Sun Fire V40z Server
 
Sun Fire X4100 M2 Server
 
Sun Fire X4100 Server
 
Sun Fire X4600 Server
 
Sun Fire X4500 Server
 
Sun Java Workstation W2100z
 
Sun Fire X2100 Server
 

GCS>Sun Microsystems>Servers>x64 Servers
 

Applies to:

Symptoms

Solaris[TM] Operating System for x64 Platforms FMA (Fault Management Architecture) or PSH (Predictive Self Healing) messaging calls out faulted Memory Modules as dimm=0, dimm=1, etc. Not all Sun AMD systems physically label or silkscreen Memory Modules starting with dimm0. Please reference your specific system/platform, found in the resolution section, to show it's Memory Module layouts.

Changes

Cause

FMA events are reported as Logical Devices, so in some platforms the reported dimm name does not match the label marked on the motherboard.

Solution

If your platform is not on the list as this was required only for older systems, later systems, the dimm label is more likely to match FMA labelling.

Changes to FMA reporting which includes dimm serial numbers being reporting in the dimm output, greatly enchance the likely hood of confirming the dimms location. Using this serial number it is possible that this number can be used as a cross check to ensure the correct dimm location. The dimm serial numbers can be gained by looking at the output of either the output from ipmitool fru output or the Service Processor CLI or BUI.


Resolution
The following systems labeling/silkscreening of DIMM locations coincide with Solaris FMA Fault Messaging.

Sun Fire[TM] V20z

Sun Fire[TM] V40z

Sun Fire[TM] X4100 and M2

Sun Fire[TM] X4200 and M2

Sun Fire[TM] X4500

Sun Fire[TM] X4600 and M2

Where Solaris x64 FMA Memory Module messages match 1:1, dimm=x maps to DIMMx:

dimm=0 maps to the physical location; DIMM0 dimm=1 maps to the physical location; DIMM1 dimm=2 maps to the physical location; DIMM2 dimm=3 maps to the physical location; DIMM3

Sun Fire V20z/V40z label dimms starting with dimm0 closest to processor, moving outward, labeling reads dimm0, dimm1, dimm2, dimm3.

Sun Fire X4100/X4200/X4500/X4600/x4600 plus M2 variants label dimms starting with dimm3 closest to processor, moving outward, labeling reads dimm3, dimm1, dimm2, dimm0.

The following systems labeling/silkscreening of DIMM locations do NOT coincide with Solaris FMA Fault Messaging.

Sun Fire[TM] X2100

Sun Java[TM] Workstation W1100z

Sun Ultra[TM] 20 Workstation

Where Solaris x64 FMA Memory Module messages does not match 1:1 then:

dimm=0 maps to the physical location; DIMM1 dimm=1 maps to the physical location; DIMM2 dimm=2 maps to the physical location; DIMM3 dimm=3 maps to the physical location; DIMM4

Sun Fire X2100 label dimms starting with dimm1 closest to processor, moving outward labeling reads dimm1, dimm2, dimm3, dimm4.

Sun Java Workstation W1100z label dimms starting with dimm4 closest to processor, moving outward labeling reads dimm4, dimm3, dimm2, dimm1.

Sun Ultra 20 Workstation label dimms starting with dimm1 closest to processor, moving outward labeling reads dimm1, dimm2, dimm3, dimm4.

The following system labeling/silkscreening of DIMM locations do NOT coincide with Solaris FMA Fault Messaging.

Sun Java[TM] Workstation W2100z

Where Solaris x64 FMA Memory Module messages does not match 1:1 then:

CPU0

dimm=0 maps to the physical location; DIMM1 dimm=1 maps to the physical location; DIMM2 dimm=2 maps to the physical location; DIMM3 dimm=3 maps to the physical location; DIMM4

CPU1

dimm=0 maps to the physical location; DIMM5 dimm=1 maps to the physical location; DIMM6 dimm=2 maps to the physical location; DIMM7 dimm=3 maps to the physical location; DIMM8

Sun Java Workstation W2100z label dimms starting with dimm4 closest to processor 0, moving outward labeling reads dimm4, dimm3, dimm2, dimm1.

Labeling for second processor  starts with dimm8 closest to processor 1, moving outward labeling reads dimm8, dimm7, dimm6, dimm5.

The following system labeling/silkscreening of Dimm locations do NOT coincide with Solaris FMA Fault Messaging.

Sun Ultra[TM] 40 Workstation

Where Solaris x64 FMA Memory Module messages does not match 1:1 then:

CPU0

dimm=0 maps to the physical location; DIMM0 dimm=1 maps to the physical location; DIMM1 dimm=2 maps to the physical location; DIMM2 dimm=3 maps to the physical location; DIMM3

CPU1

dimm=0 maps to the physical location; DIMM4 dimm=1 maps to the physical location; DIMM5 dimm=2 maps to the physical location; DIMM6 dimm=3 maps to the physical location; DIMM7

Sun Ultra 40 Workstation label dimms starting with dimm0 closest to processor 0, moving outward, labeling reads dimm0, dimm1, dimm2, dimm3.

Labeling for second processor  starts with dimm4 closest to processor 1, moving outward labeling reads dimm4, dimm5, dimm6, dimm7.

This solution has no attachment