Fujitsu M10 Product Notes page 65

Table 3-5 Problems that might occur with XCP 2240 and workarounds (continued)
SPARC M10-
RTI No. 1 4 4S
RTIF2- x
131213-022
RTIF2- x x x
140121-001
RTIF2- x x x
140212-003
Description
After firmware update, if the XCP
version is checked by the version(8)
command or the XSCF Web interface,
versions of each crossbar box (XBBOX) or
the XCP of SPARC M10-4S (BB) may not
be the same as the updated XCP version.
In the following example, although the
firmware has been updated to XCP2052
from XCP 2042, the XCP of "XCP0
(Reserve):" of BB#00 has not been updated.
XSCF> version -c xcp -v
XBBOX#80-XSCF#0 (Master)
XCP0 (Reserve): 2052
XSCF : 02.05.0002
XCP1 (Current): 2052
XSCF : 02.05.0002
XBBOX#81-XSCF#0 (Standby)
XCP0 (Current): 2052
XSCF : 02.05.0002
XCP1 (Reserve): 2052
XSCF : 02.05.0002
BB#00-XSCF#0
XCP0 (Reserve): 2042
CMU : 02.05.0002
POST : 1.43.0
OpenBoot PROM : 4.34.0+1.22.0
Hypervisor : 0.27.8
XSCF : 02.04.0000
XCP1 (Current): 2052
CMU : 02.05.0002
POST : 1.43.0
OpenBoot PROM : 4.34.0+1.22.0
Hypervisor : 0.27.8
XSCF : 02.05.0002
If the input power is turned off (AC OFF)
while the XSCF is processing large
amounts of data, only occasionally, XSCF
may not start-up when the input power
in turned on (AC ON) again.
The OID information of "scfPsbInfo" in
the definition file of XSCF extension MIB
is not updated even if the information of
the system board (PSB) is updated.
Workaround
There is no effective workaround.
[How to restore]
Specify the BB-ID of the crossbar box
(XBBOX) or of the SPARC M10-4S (BB),
which was not updated, to the
"rebootxscf -b BB-ID" command and
execute it to reset the XSCF of the
specified chassis.
There is no effective workaround.
Contact a field engineer if this problem
occurs.
Restart the snmp daemon using any of
the setsnmp(8), setsnmpusm(8) or the
setsnmpvacm(8) commands or reset
XSCF.
Chapter 3 Information on Software 51