STM Release Notes for HP-UX 11i v3 September 2011 Release

Known Problems and Workaround
• Symptom: Re-installation of OnlineDiag alone causes core-hw events not to be logged into
/var/opt/resmon/log/event.log in SFM mode.
Problem: When OnlineDiag is removed, it will remove the complete monitor directory. This
causes the removal of the reverse wrapper which consumes SFM events and log into EMS
event.log. Hence when you install OnlineDiag again, the reverse wrapper for SFM providers
does not come up. The reverse wrapper is required to log the events from SFM providers to
EMS event.log in SFM mode. But the events are still logged into SFM event.log and in evweb.
Workaround: Replace the reverse wrapper to monitor and dict file to the correct directory
using the following steps:
1. etc/opt/resmon/lbin/toggle_switch stop
2. cp /var/opt/sfm/data/WbemWrapperMonitor.dict
/etc/opt/resmon/dictionary/
3. cp /var/opt/sfm/data/WbemWrapperMonitor
/usr/sbin/stm/uut/bin/tools/monitor/
4. /etc/opt/resmon/lbin/toggle_switch restart
• Symptom: A warning message is logged by diag2 to syslog.log file.
Problem: A DIAGNOSTIC SYSTEM WARNING message is logged by diag2 which mentions
the STM and diaglogd processes names on HP integrity and NGIS systems even though
OnlineDiag is not supported.
Diagnostic System Warning:
The diagnostic logging facility has started receiving excessive errors from the I/O subsystem. I/O error
entries will be lost until the cause of the excessive I/O logging is corrected. If the diaglogd daemon
is not active, use the Daemon Startup command in stm to start it. If the diaglogd daemon is active, use
the log tool utility in stm to determine which I/O subsystem is logging excessive errors.
Workaround: None
Resolution: Ignore the terms stm or diaglogd. The diaglogd will be changed to oserlogd
and the support of log tool utility will not be available from STM. If oserlogd daemon is not
started, then use this command /sbin/init.d/oserlogd start to start the daemon.
• Symptom: OnlineDiag does not work properly when the length of the system name exceeds
8 characters.
Problem: When the length of the hostname for a system name exceeds 8 characters,
OnlineDiag cannot retrieve the hostname. So, OnlineDiag cannot function as expected.
Workaround: Change the default values of the expanded_node_host_names and
uname_eoverflow kernel parameters by completing the following steps:
1. kctune expanded_node_host_names=1
2. kctune uname_eoverflow=0
Release Notes for STM B.11.31.17.04 on HP-UX 11i v3 (September 2011) 3