User`s guide

Sun SPARC Enterprise M8000/M9000 Servers Product Notes 11
6625734 Systems with large number of processors in a
single domain environment might have
suboptimal performance with certain
workloads.
Use processor sets to bind application processes
or LWPs to groups of processors. Refer to the
psrset(1M) man page for more information.
6632549 fmd service on domain might fail to
maintenance mode after DR operations.
If fmd service fails, issue the following
commands on the domain to recover:
# svcadm clear fmdt
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:
• Manually restart fmd using the command:
svcadm clear fmd
• Or, restart the cpumem-diagnosis:
fmadm restart cpumem-diagnosis
SUNW-MSG-ID: FMD-8000-2K, TYPE: Defect, VER: 1, SEVERITY: Minor
EVENT-TIME: Fri Apr 4 21:41:57 PDT 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. Refer to http://sun.com/msg/FMD-8000-2K for more
information.
AUTO-RESPONSE: The module has been disabled. Events destined for the 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. Use fmadm reset
<module> to reset the module.
6660197 DR might cause the domain to hang if either of
the following conditions exist:
• A domain contains 256 or more CPUs.
• More than 256 memory errors are detected.
Follow these steps:
1. Set the following parameter in the system
specification file (/etc/system):
set drmach:drmach_disable_mcopy=1
2. Reboot the domain.
6663570 DR operations involving the lowest number
CPU might cause the domain to panic.
Do not use DR to remove the system board that
hosts the CPU with the lowest CPU ID. Use the
Solaris prtdiag command to identify the CPU
with the lowest CPU ID.
6668237 After DIMMs are replaced, the corresponding
DIMM faults are not cleared on the domain.
Use the command fmadm repair fmri|uuid
to record the repair. Then you can use the
command fmadm rotate to clear out any
leftover events.
TABLE 5 Solaris OS Issues and Workarounds for All Supported Releases (4 of 4)
CR ID Description Workaround