Fujitsu M10 Product Notes page 125

Table 3-12 Problems resolved in XCP 2210 (continued)
SPARC M10-
RTI No. 1 4 4S
RTIF2- x x x
140212-020
RTIF2- x x
140212-023
RTIF2- x x x
140212-024
Description
When hot-swapping a fan, if the fan is
installed right after removing it,
hot-swapping may fail.
If CPU failures like the following, occur
on a SPARC M10-4/M10-4S to which a
CPU memory unit lower (CMUL) and a
CPU memory unit upper (CMUU) is
mounted, when starting a physical
partition (PPAR) the "Hypervisor Abort"
error is produced and the PPAR may not
be used anymore.
- In case of SPARC M10-4, if all the CPUs
mounted on the CMUL are degraded.
- In case of SPARC M10-4S, if all the
CPUs mounted on the CMUL on all the
chassis that configures the PPAR, are
degraded.
After executing the "ldm add-spconfig"
or the "ldm set-spconfig" command on
Oracle Solaris, if the "auto-boot?"
environment variable of OpenBoot
PROM is changed, the set value does not
show up when the XSCF showpparpara
m(8) command is executed. The value
that existed before executing the "ldm
add-spconfig" or "ldm set-spconfig"
command, is displayed. This symptom
occurs when the following procedures
are conducted in the following sequence.
1. Start the physical partition (PPAR).
2. Execute the "ldm add-spconfig"
command from the control domain of
the started PPAR to save the
configuration information of the
logical domain.
Or, execute the "ldm set-spconfig"
command from the control domain of
the started PPAR to specify the name
(config-name) of the configuration
information of the logical domain that
is to be used at the time of the next
starting of the PPAR.
3. From Oracle Solaris on the control
domain, execute "eeprom auto-
boot?=xxxx" to change the environment
variable of the OpenBoot PROM or,
change the OpenBoot PROM
environment variable from the
OpenBoot PROM itself.
Workaround
When replacing a fan, after removing it,
wait for at least 10 seconds before
reinstalling it.
There is no effective workaround.
Replace the CMUL on which the failed
CPUs are mounted.
There is no effective workaround.
However, the value itself has been
enabled. Check the value of the
OpenBoot PROM environment variable
"auto-boot?", which will be used at the
next starting of the PPAR, not from the
XSCF, but from Oracle Solaris on the
control domain or from the OpenBoot
PROM.
Chapter 3 Information on Software 111