Solaris OS Issues and Workarounds for All Supported Releases (2 of 3)
TABLE 3-2
CR ID
Description
6660168
If a ubc.piowbeue-cpu error occurs on a
domain, the Solaris Fault Management
cpumem-diagnosis module might fail, causing
an interruption in FMA service. If this
happens, you will see output similar to the
following sample in the console log:
SUNW-MSG-ID: FMD-8000-2K, TYPE:
Defect, VER: 1, SEVERITY: Minor
EVENT-TIME: Fri Apr
2008
PLATFORM: SUNW,SPARC-Enterprise, CSN:
2020642002, HOSTNAME: <hostname>
SOURCE: fmd-self-diagnosis, REV: 1.0
EVENT-ID: 6b2e15d7-aa65-6bcc-bcb1-
cb03a7dd77e3
DESC: A Solaris Fault Manager
component has experienced an error
that required the module to be
disabled.
http://sun.com/msg/FMD-8000-2K for
more information.
AUTO-RESPONSE: The module has been
disabled.
module will be saved for manual
diagnosis.
IMPACT: Automated diagnosis and
response for subsequent events
associated with this module will not
occur.
REC-ACTION: Use fmdump -v -u <EVENT-
ID> to locate the module.
reset
<module> to reset the module
6668237
After DIMMs are replaced the corresponding
DIMM faults are not cleared on the domain.
18
Sun SPARC Enterprise M3000 Server Product Notes for XCP 1090 • August 2009
4 21:41:57 PDT
Refer to
Events destined for the
Use fmadm
Workaround
If fmd service fails, issue the following
command on the domain to recover:
# svcadm clear fmd
Then restart cpumem-diagnosis:
# fmadm restart cpumem-diagnosis
Use the following commands:
# fmadm repair fmri|uuid
# fmadm rotate
Need help?
Do you have a question about the SPARC Enterprise M3000 and is the answer not in the manual?