Fujitsu M10 Product Notes page 41

Table 3-3
Problems resolved in versions prior to XCP 2043 (continued)
SPARC
RTI No. M10-1
RTIF2-121113- x
029
RTIF2-121113- x
031
RTIF2-121129- x
001
RTIF2-121129- x
002
RTIF2-121129- x
004
SPARC SPARC
M10-4 M10-4S Description
x x When the following error is
registered in the error log, the
mark (*) showing a failure state
does not appear when you
execute the showhardconf(8)
command or the showstatus(8)
command.
System backup memory
access error
x x After creating an I/O domain to
which the PCI card is assigned
with Oracle VM Server for
SPARC, turn on the power of
the I/O domain. If you then stop
it in ok prompt, the configuration
information of the PCI card may
not be displayed with the
showhardconf(8) command of
XSCF.
x x By restarting XSCF, an error log
"System backup memory access
error" may be recorded and a (*)
mark indicating a failure state
may be put to PSUBP. Once this
error occurs, you cannot start
the physical partition (PPAR) or
collect log information.
x x When you replace the CPU
memory unit (CMU) or
motherboard unit (MBU), the
XSCF user account information
may be deleted.
To recover the XSCF user
account information, you need
to use the restoreconfig(8)
command to restore the
information saved by the
dumpconfig(8) command.
x x The restoredefaults(8) cannot
initialize the following
information. The setting
information remains as it is.
Timezone for XSCF
■
Server certificate for HTTPS
■
Workaround
There is no effective workaround.
Start Oracle Solaris of the
logical domain to which the PCI
card is assigned with Oracle
VM Server for SPARC.
XSCF is restored by restarting
XSCF, although the (*) mark to
PSUBP indicating the failure
state remains. The remaining (*)
mark does not cause any
inconvenience.
To remove the (*) mark, power
off the server and then power it
on again.
After you have conducted the
replacement, use the
restoreconfig(8) command to
restore the information saved
by the dumpconfig(8)
command, or set the XSCF user
account information again.
There is no effective workaround.
Reset by the settimezone(8),
sethttps(8), and setssh(8)
commands.
Chapter 3 Information on Software 29