Fujitsu SPARC Enterprise M3000

Chapter 3 Information About Software 47
RTIF1-
091109-004
OOOWhen you start up a domain from a
disk connected to the 8-Gbps fibre
channel card (SE0X7F21F, SE0X7F22F),
if you fail to specify the correct device
path, an error log with no message
might be registered.
In the same way, when you start up a
domain from a disk connected to the
8-Gbps fibre channel card (SE0X7F21F,
SE0X7F22F), even if the domain
cannot be started due to reasons such
as disk failure, the error log might not
be registered.
No workaround is available.
RTIF1-
100331-001
OOOWhen you use the sethttps(8)
command to create the self CA
(Certificate Authority) or a CSR with
specifying only spaces (for example, "
") in the e-mail operand, the HTTPS
function might be disabled after XSCF
reset.
When you create the self CA or a CSR,
do not specify only spaces in the e-
mail operand.
RTIF1-
100713-001
OOOWhile the Oracle Solaris 10 OS is
running, if the occurrence of RED
State Exception or watchdog reset or
the execution of the reset xir
command lead to the domain CPU
reset, the following message might be
displayed on the console and the
domain might hang up.
Failed to complete trap
processing. mid=0xXX
No workaround is available.
When this problem occurred, turn off
the domain power and then turn on.
RTIF1-
100713-002
O Though the mainline switch is on, the
showhardconf(8) command might
wrongly display the PSU status as
"Breaker off" or "Input fail."
No workaround is available.
RTIF1-
101019-001
OOOWhen you start up a domain from a
hard disk that is connected to the
8Gbps fibre channel card (SE0X7F21F,
SE0X7F22F) and if you specified an
erroneous value after "@" of the disk
node, the message of "Fast Data
Access MMU Miss" might be
displayed on the console and an error
log of the TT=0x68 trap might be
registered.
No workaround is available.
When this event occurred, change the
environmental variable 'auto-boot?'
setting to false and use the reset-
all command to reset the domain.
Then, specify the correct value after
"@" of the disk node and execute the
boot command.
TABLE 3-3 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)
ID M3000
M4000
M5000
M8000
M9000 Description Workaround