100
SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010
■
PCIEX-8000-HS
The following example from the ALOM CMT compatibility CLI illustrates the
problem. In this example, the faulty FRU displayed is the motherboard (
/SYS/MB
)
when the actual faulty component is a memory DIMM.
In addition, there is a problem with the output displayed by the
show
/SYS/faultmgmt
command (ILOM CLI). The
fault_state
property of
components, and the faulted components listed under the Fault Management tab in
the ILOM BI are incorrect for the PSH Message-IDs listed above. Also, the FB-DIMM
fault indicator will not operate, and the FRUID for the motherboard will have a fault
recorded.
Workaround: Use the Fault Management utilities on the host to find the location of
the faulty DIMM(s) or PCIe adapters. Instructions for using these utilities for these
faults can be found in the Predictive Self-Healing Knowledge Articles located at:
http://www.sun.com/msg/
MSGID
where
MSGID
is one of the PSH Message IDs listed in the bulleted list in this section
and displayed by the ALOM
showfaults
command.
For faulty DIMMs, refer to the DIMM label on the air duct or system cover to verify
the DIMM location.
Once the faulty DIMM is replaced and the PSH fault has been cleared, the entry in
showfaults
will be deleted, and the fault recorded in the motherboard FRUID will
be cleared.
The
uadmin
2
0
and
reboot
Commands Read
Old Bootmode Settings (CR 6585340)
This issue is resolved by updating the system firmware to 7.1.6.d or later.
You can change LDoms variables in the control domain in one of three ways, with
the OpenBoot
setenv
command in the control domain, with the Solaris
eeprom
command in the control domain, or using ILOM
bootmode bootscript
option.
sc>
showfaults -v
Last POST Run: Jul. 13 18:32:11 2007
Post Status: Passed all devices
ID Time FRU Class Fault
0 Jul 13 19:31:34 /SYS/MB Host detected fault, MSGID:
SUN4V-8000-DX UUID: 7b471945-ceef-eea0-c3ad-85ca140be5b2
