Fujitsu M10 Product Notes page 30

Table 3-1
Problems that might occur with XCP 2043 and workarounds (continued)
SPARC
RTI No.
M10-1
RTIF2-
130219-007
RTIF2-130228- x
001
RTIF2-130305- x
001
RTIF2-130305- x
002
Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2043 ･ October 2013
18
SPARC SPARC
M10-4 M10-4S Description
x When you turn on the input
power supply to a crossbar box
or SPARC M10-4S after
disconnecting it in a system
with building block configuration,
"Board control error (MBC link
error)" may be registered in the
error log. In addition, an
non-existing crossbar box or
SPARC M10-4S may be
displayed as a faulty unit.
x x If a physical partition (PPAR) is
powered on again after the
PPAR is forcefully powered off
with the poweroff -f command
while starting up Oracle Solaris,
"Unable to connect to Domain
Service providers" is output to
the OS console and Oracle
Solaris may not be started.
x x " The limit of power has
been exceeded " is
registered on the event log if
you execute the following.
Execute the setpowercapping(8)
command to set the power
consumption limit function to
"Enable", the power consumption
upper limit value to "Specify to
100 percent (default)", and an
extension of time when
exceeding the upper limit of
power consumption to "none."
And then turn on the input
power supply or turn off the
power of a physical partition.
x x If an error in the CPU or
memory is detected and if the
XSCF is switched while the
XSCF is notifying the error
information to the control
domain, the error information
may not be notified again to the
control domain. Because of this,
the error information displayed
with the showlogs error
command is not displayed in
the Fault Report output by the
fmdump command.
Workaround
This error log is registered
when you disconnect the input
power supply. Ignore this error
log.
Power on the PPAR again with
the poweron(8) command after
disconnecting the power of the
PPAR with the poweroff(8)
command. If Oracle Solaris does
not start up even after that, reset
the XSCF after disconnecting
the power of the PPAR and then
power on the PPAR again.
There is no effective workaround.
Ignore this event log.
There is no effective workaround.
Maintain according to the FRU
displayed by the showlogs error
command.