Problems Resolved In Xcp 2091 - Fujitsu M10 Product Notes

Table 3-13 Problems resolved in XCP 2092
SPARC M10-
RTI No. 1 4 4S
RTIF2- x
131213-015
RTIF2- x
140110-001
RTIF2- x x x
140110-002
RTIF2- x x x
140115-001

Problems resolved in XCP 2091

The following table lists the problems resolved in XCP 2091.
Description
In case, all of the three conditions below
are met on a physical partition, the
crossbar unit (XBU) error "Msg: XB-XB
interface fatal error" is detected.
[Condition 1] The physical partition is
configured by several SPARC M10-4S.
[Condition 2] The XSCF BB control cables
that are connected to the SPARC M10-4S
chassis are either defective or have been
disconnected.
In such a case, the "Msg: BB control cable
detected unexpected" error log is
registered.
[Condition 3] The physical partition was
rebooted due to a hardware failure, the
poweron(8) or reset(8) command was
executed.
Moreover, XSCF had either rebooted the
physical partition due to a hardware
failure or had performed retrial of the
poweron(8) or the reset(8) command
when this symptom occurred previously.
In a SPARC M10-4S (with crossbar box)
configuration, the following event log,
which notifies power off, is not registered.
BB#xx was stopped by power failure.
Power failure date is yyyy/mm/dd
hh:mm:ss
When the flashupdate(8) command is
executed, only occasionally, XSCF may
not start-up.
If a failure occurs in the PCI Expansion
Unit, all the domains that are situated in
the physical partition (PPAR) that is
connected to the PCI Expansion Unit, are
shut down.
Workaround
There is no effective workaround.
Do not execute the poweron(8) or the
reset(8) command while the XSCF BB
control cable is disconnected.
[How to restore]
If hardware failure had occurred, execute
power off and on, on the physical
partition.
If XSCF is performing retrial operations,
execute the "poweroff -f -p ppar-id"
command to forcibly power off the
physical partition. After that power it on.
There is no effective workaround.
There is no effective workaround.
Contact a field engineer if this problem
occurs.
There is no effective workaround.
Chapter 3 Information on Software 115