Fujitsu SPARC Enterprise M3000 Product Notes page 54

Hide thumbs Also See for SPARC Enterprise M3000:
Table of Contents

Advertisement

XCP Issues Fixed in Releases Earlier Than XCP 1112 (Continued)
TABLE 3-3
M4000
ID
M3000
M5000
RTIF1-
O
O
091109-004
RTIF1-
O
O
100331-001
RTIF1-
O
O
100713-001
RTIF1-
100713-002
RTIF1-
O
O
101019-001
40
SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1112 • May 2012
M8000
M9000 Description
O
When 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.
O
When 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.
O
While 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
O
Though the mainline switch is on, the
showhardconf(8) command might
wrongly display the PSU status as
"Breaker off" or "Input fail."
O
When 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.
Workaround
No workaround is available.
When you create the self CA or a CSR,
do not specify only spaces in the e-mail
operand.
No workaround is available.
When this problem occurred, turn off
the domain power and then turn on.
No workaround is available.
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.

Advertisement

Table of Contents
loading

Table of Contents