Table
3-5
Problems
that
might
occur
with
XCP
2240
and
workarounds
(continued)
SPARC
M10-
RTI
No.
1
4
4S
Description
Workaround
RTIF2-
131001-002
x
While
a
physical
partition
(PPAR)
is
operating
or
when
a
PPAR
is
turned
off,
master/standby
XSCF
switching
may
occur.
If
master/standby
switching
occurs,
the
following
message
is
displayed
on
the
console
of
the
master
XSCF.
Kernel
panic
-
not
syncing:
MBC
Dual
ifcut
interrupt.
There
is
no
effective
workaround.
As
a
result
of
this
defect,
master/standby
switching
occurs,
but
this
does
not
affect
the
system,
and
the
system
can
be
operated
continuously.
RTIF2-
131112-001
x
x
x
If
data
is
transmitted
via
SSH
by
the
snapshot(8)
-t
command,
this
transmission
may
be
delayed
by
about
10
to
30
minutes
in
comparison
with
transfer
using
USB
devices
and
XSCF
Web.
There
is
no
effective
workaround.
Even
if
transfer
is
delayed,
there
is
no
problem
with
the
collected
data.
RTIF2-
131112-013
x
Suppose
that
multiple
physical
partitions
(PPARs)
are
simultaneously
started
by
the
poweron
-a
command.
The
error
message
"Error
storing
configuration
variable.
LDC
is
not
up
Configuration
variable
setting
will
not
persist
after
a
reset
or
power
cycle"
may
be
output
to
the
OS
console
after
the
message
"Unable
to
connect
to
Domain
Service
providers."
Oracle
Solaris
may
be
started
without
applying
the
OpenBoot
PROM
environment
variable
specified
with
the
setpparparam(8)
command.
There
is
no
effective
workaround.
Restart
the
control
domain
for
the
physical
partition
(PPAR)
for
which
the
error
message
was
output.
RTIF2-
131126-003
x
x
x
Update
of
the
PCI
expansion
unit
firmware
may
fail.
If
it
fails,
"LINKCARD
update
is
failed"
appears
in
the
event
log.
[Example]
SCF:LINKCARD
update
is
failed
(LINKCARD=1,
bank=0,
PCIBOX
version=1130:
last
version=1120)
There
is
no
effective
workaround.
Execute
the
ioxadm
-c
update
command
to
update
the
PCI
expansion
unit
firmware
again.
RTIF2-
131213-001
x
In
a
configuration
with
3
or
more
BBs,
or
with
crossbar
boxes,
when
the
XSCF
master/standby
switchover
is
executed
due
to
some
abnormality
on
the
master
XSCF,
the
master
XSCF
may
fail
to
switch
over
to
the
standby
XSCF
and
start
up
as
another
master
XSCF.
Due
to
this,
the
system
seems
to
contain
two
master
XSCFs.
Normal
behavior
of
a
system
is
not
guaranteed
when
there
are
two
master
XSCFs
in
the
system.
This
state
can
be
confirmed
by
a
lighted
MASTER
LED
at
the
rear
panel
of
two
chassis.
There
is
no
effective
workaround.
[How
to
restore]
The
system
can
be
operated
normally
when
the
number
of
master
XSCFs
automatically
returns
to
one
after
a
few
minutes.
If
the
number
of
master
XSCFs
does
not
return
to
one
even
after
15
minutes,
press
the
RESET
switch
at
the
rear
panel
of
all
existing
SPARC
M10
systems
and
crossbar
boxes.
The
system
can
be
operated
normally
after
that.
Fujitsu
M10/SPARC
M10
Systems
Product
Notes
for
XCP
Version
2240
・
March
2015
46
Summary of Contents for M10 Series
Page 8: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 viii ...
Page 14: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 xiv ...
Page 24: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 10 ...
Page 192: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 178 ...
Page 200: ...Fujitsu M10 SPARC M10 Systems Product Notes for XCP Version 2240 March 2015 186 ...