Table
3-5
Problems
that
might
occur
with
XCP
2240
and
workarounds
(continued)
SPARC
M10-
RTI
No.
1
4
4S
Description
Workaround
RTIF2-
130305-001
x
x
x
"The
limit
of
power
has
been
exceeded"
is
registered
in
the
event
log
if
you
perform
the
following.
Execute
the
setpowercapping(8)
command
to
set
the
power
consumption
limiting
function
to
"Enable",
the
power
consumption
maximum
allowable
value
to
"Specify
100
percent
(default)",
and
the
time
extension
when
exceeding
the
maximum
allowable
power
consumption
to
"none."
Then,
turn
on
the
input
power
supply
or
turn
off
the
power
to
the
physical
partition
(PPAR).
There
is
no
effective
workaround.
Ignore
this
event
log.
RTIF2-
130305-002
x
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.
There
is
no
effective
workaround.
Maintain
according
to
the
FRU
displayed
by
the
showlogs
error
command.
RTIF2-
130305-007
x
x
x
FRU
registered
in
the
error
log
is
displayed
as
"PPAR#30"
if
the
configuration
error
of
the
system
board
(PSB)
is
detected
when
executing
the
testsb(8)
command
or
diagxbu(8)
command.
There
is
no
effective
workaround.
Maintain
the
applicable
PSB
of
SPARC
M10
system
chassis.
RTIF2-
130305-013
x
x
x
While
XSCF
is
starting,
process
down,
panic
or
watchdog
timeout
occurs,
which
may
cause
XSCF
to
be
reset.
Confirm
that
XSCF
is
successfully
started.
If
it
is
not
started,
turn
off
the
power
of
the
physical
partition
(PPAR),
and
then
disconnect
the
input
power
supply
to
the
system
and
back
on
again
(AC
OFF/ON).
When
recycling
the
power
supply
to
the
system,
wait
for
30
seconds
or
more
to
turn
on
the
input
power
supply
after
disconnecting.
In
case
XSCF
is
not
started
even
if
recycling
the
input
power
supply
to
the
system,
replace
the
CPU
memory
unit
lower
(CMUL)
or
the
motherboard
unit
(MBU).
RTIF2-
130305-020
x
If
an
XSCF
panic
or
hang-up
occurs,
an
error
log
showing
that
"XSCF
hang-up
is
detected"
may
be
posted
many
times.
There
is
no
effective
workaround.
Ignore
the
logs
with
the
same
contents
that
were
notified
at
the
same
period
of
time
considering
that
they
are
caused
by
the
same
reason.
Fujitsu
M10/SPARC
M10
Systems
Product
Notes
for
XCP
Version
2240
･
March
2015
42
Summary of Contents for M10 Series
Page 8: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 viii ...
Page 14: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 xiv ...
Page 24: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 10 ...
Page 192: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 178 ...
Page 200: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 186 ...
