Fujitsu M10 Product Notes page 66

Table 3-5 Problems that might occur with XCP 2240 and workarounds (continued)
SPARC M10-
RTI No. 1 4 4S
RTIF2- x x x
140212-005
RTIF2- x x x
140212-007
RTIF2- x x x
140212-008
RTIF2- x
140212-011
RTIF2- x
140212-012
Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240 ･ March 2015
52
Description
In the OID information of
"scfComponentStatusEvent" in the
definition file of XSCF extended MIB,
the path information of the suspected
components may be denoted as
"unspecified" in the trap notification.
This symptom occurs when the OID
"FaultEventCode" information is any of
the following:
05018113
05018123
05018133
05018211
05018221
05018231
When an attempt is made to register a
password containing 256 or more
characters, in the password input prompt
of either the setsnmp(8) or the
setsnmpusm(8) command, only 255
characters are registered.
When powering on, or rebooting a
physical partition (PPAR), even if the
process is stopped due to the failure of a
component, the POWER LED of the
operation panel keeps blinking.
If the XSCF master/standby switchover
occurs when the physical partition
(PPAR) is running, in some very rare
cases, XSCF process down may occur and
the XSCF may be reset.
In a system configuration with 3 or more
BBs or with a crossbar box, if the XSCF
master/standby switchover occurs for 60
or more times, a process down may occur
on the slave XSCF and the slave XSCF is
reset.
Workaround
There is no effective workaround.
When setting up a password equal to or
longer than 256 letters, use the password
option of either the setsnmp(8) or the
setsnmpusm(8) command, instead of
using the password input prompt.
[How to restore]
If a password equal to or longer than 256
characters has been registered using the
password input prompt, remove the
target user data with either the "setsnmp
remv3traphost" or the "setsnmpusm
delete" command and then register the
user again.
There is no effective workaround.
There is no effective workaround. The
system can be operated continuously as it
will be restored after being reset.
There is no effective workaround. The
slave XSCF will be restored by the reset
and the system can be used continuously
after that.