Fujitsu M10 Product Notes page 138

Table 3-15 Problems resolved in XCP 2090 (continued)
SPARC M10-
RTI No. 1 4 4S
RTIF2- x x x
131216-001
RTIF2- x x x
140303-001
RTIF2- x x x
140410-004
RTIF2- x x x
140410-006
Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240 ･ March 2015
124
Description
The "XCP update is started." message is
mistakenly displayed when the
"flashupdate -c check" command is
executed.
Response may become slow when using
XSCF Web.
If a CPU error occurs while powering on
a physical partition (PPAR), an erroneous
error log may be registered. This
symptom can be confirmed by using the
showlogs error -v command.
If the result of the showlogs error -v
command is "Msg: SP InternalError
Occurred", and the first 4 bytes of the 5th
line of the [Diagnostic Code] is
"01920212", it corresponds to this
symptom.
[Example]
XSCF> showlogs error -v
Date: Nov 11 18:29:04 JST 2013
Code: 40000000-00fcff0000ff0000ff-
0186ffff0000000000000000
Status: Warning Occurred: Nov 11
18:29:04.871 JST 2013
FRU: /FIRMWARE
Msg: SP Internal Error Occurred
Diagnostic Code:
00000000 00000000 0000
00000000 00000000 0000
00000000 00000000 0000
0007000b 02040002 00000000 00000000
01920212 00620000 0000
If you execute the reset xir command
immediately after starting Oracle Solaris
or the ldmd service, "LDC Protocol info
fromPPAR (PPAR ID 0 : Domain Service
Data Send Failed)" may be registered in
the event log and the XSCF process down
and reset may occur.
Workaround
There is no effective workaround.
Please ignore this message.
There is no effective workaround.
There is no effective workaround.
[How to restore]
Execute the showstatus(8) command to
check whether a part has failed. A CPU
whose [Status] is "Deconfigured" has
failed. Follow the maintenance procedure
to replace the FRU mounted on the CPU.
[Example] When a "Deconfigured" CPU
exists
XSCF> showstatus
BB#11 Status:Normal;
CMUU Status:Normal;
* CPU#0 Status:Deconfigured;
There is no effective workaround.
After XSCF is reset, execute the showlogs
event command to confirm the event
logs. Or, execute the showpparstaus(8)
command to confirm that the physical
partition (PPAR) was reset. If the
physical partition has not been reset,
execute the reset xir command again.