Siemens SPARC ENTERPRISE M8000 - Manual (Page 19)

Information about Software 11
RTIF1-
080512-001 When you specify "localhost" to the
hostname of the sethostname(8) command
and reset XSCF by using the
applynetwork
(8) and the rebootxscf(8)
commands, a process goes down in XSCF.
Do not specify "localhost" to the hostname of
the sethostname(8) command.
RTIF1-
080526-001 When the system is stressed with many faults,
the fmd process on the service processor might
hang. Once this happens, fma commands on
the service processor can fail or hang. Reboot the service processor using the XSCF
command rebootxscf(8).
RTIF1-
080725-001 In setsnmp addv3traphost, when the
authentication failed due to the reasons such
as the trap host not working, or the wrong
user name or password, the subsequent SNMP
traps will not be notified. There is no workaround.
Confirm that the SNMP trap host is working
and re-execute the setsnmp(8) command
using the correct user name.
RTIF1-
080725-002 When the SNMPv3 trap has been set, after the
watchdog timeout occurred in XSCF and XSCF
reset, the subsequent SNMP traps will not be
notified. There is no workaround.
RTIF1-
080725-003 The initial value that set with the
setdomparam
set-defaults option differs
from the initial value of OpenBoot PROM.
parameters current value expected value
diag-level none(0x00) min(0x20)
auto-boot? false(0x00) true(0xff)
In the OpenBoot PROM prompt (ok>), execute
the set-defaults command to restore the
OpenBootPROM environmental variables to
the initial value.
RTIF1-
080725-004 After set the Daylight Saving Time by using
the XSCF shell, XSCF Web does not show the
correct time in the Logs menu. There is no workaround.
Use the showlogs(8) command of the XSCF
shell.
RTIF1-
080808-001 On the cluster system using the
PRIMECLUSTER software, when there are 10
or more RCI units, the RCI busy status may be
temporarily unreleased and output the
following syslog message:
SA_pprcir.so to test host host_name
failed
Refer to the manual of the PRIMECLUSTER
software to check the cluster status. If no
problem found on the status, this message can
be safely ignored. If any problem, follow the
instructions on the manual to solve the
problem.
TABLE 3 XCP Issues and Workarounds (Continued)
ID Description Workaround