Fujitsu M10 Product Notes page 135

Table 3-15 Problems resolved in XCP 2090 (continued)
SPARC M10-
RTI No. 1 4 4S
RTIF2- x
131126-002
RTIF2- x x x
131126-004
Description
If one of BB#0/BB#01/XBBOX#80/
XBBOX#81 is installed or replaced, the
synchronous processing of the CPU core
activation key in the master/standby
XSCF will fail. Subsequently, if the
master and standby are switched, the
CPU core activation key may be lost. This
generates the following phenomena.
[If the PPAR power is on]
The PPAR power is powered off because
of a CPU core activation violation.
[If the PPAR power is off]
PPAR power-on fails because there is an
insufficient number of CPU core
activations.
When the firmware update of the PCI
expansion unit and link card is complete,
the firmware version of the PCI
expansion unit is erroneously displayed.
Specifically, "PCIBOX version" of the
event log displays the pre-update
version, while "last version" displays the
post-update version.
[Example] Version displayed after an
update from 1120 to 1130
- Incorrect:
LINKCARD=1, bank=1, PCIBOX
version=1120: last version=1130
- Correct:
LINKCARD=1, bank=1, PCIBOX
version=1130: last version=1120
Workaround
After installation/replacement, the
synchronous processing of the CPU core
activation keys is performed when the
following is executed.
- If the master/standby XSCF is not
switched
Execute the rebootxscf -a or
addcodactivation(8) command from
the master XSCF that requested
installation/replacement.
- If the master/standby XSCF has been
switched
Execute the switchscf(8) command to
return the master XSCF to the
pre-installation/replacement state.
After that, execute the rebootxscf -a or
addcodactivation(8) command.
Note - Do not perform the following
operations before restoring the master
XSCF to its original state by executing
the switchscf(8) command. If these
operations are performed, it may be
necessary to register the CPU core
activation key again.
- rebootxscf -a
- addcodactivation(8)
- deletecodactivation(8)
- Input power off/on
There is no effective workaround.
Replace the version number.
Moreover, update the XCP firmware to
XCP 2090 or later.
Chapter 3 Information on Software 121