Event Monitoring Service Version A.03.10 Release Notes

Chapter 1 17
Event Monitoring Service Version A.03.10 Release Notes
Known Problems and Workarounds
nslookup $(hostname)
Using /etc/hosts on: mynode
Name: mynode
Address: 192.1.2.3
If you are using DNS, typically the canonical [official] host name can be a
fully-qualified domain name. For example, myhost.hp.com, even if you
use only the first component, myhost, for the system hostname. See the
search directive in the resolver(4) man page.
JAGab04559: Adding availMb requests on busy system
fails due to SNMPGet failure
What is the problem? Various EMS MIB Monitor resources are not
available for configuration from the EMS GUI. The error reported from
GUI is unable to register monitor request. The error reported in
/etc/opt/resmon/log/api.log is:
-------------------Start Event--------------------
User event occurred at Fri Sep 11 17:29:27 1998
Process ID: 11275 (/etc/opt/resmon/lbin/fsmond)
Log Level: Error
SNMPGet of /system/filesystem/availMb/diskfs_dsk-c7t15d3 failed: No
Such Variable Binding name, see returned error index
-------------------End Event----------------------
What is the workaround? Two command line options for the MIB
monitors are available to increase the time-out for SNMPGet and
configure additional retries. These are:
-t <sec>: timeout option, default is 5 seconds, max is 60 seconds;
-r <count>: retry option, default is 1, max is 15.
To do this, add the options in the dictionary file,
/etc/opt/resmon/dictionary/mibmond.dict, and restart the monitor.
For example:
# The filesystem free space, derived from the HP-UNIX MIB
RESOURCE_NAME: /system/filesystem/availMb
MONITOR: /etc/opt/resmon/lbin/fsmond -t 10 -r 2
JAGab77759: ServiceGuard package service status is
reported incorrectly
What is the problem? /cluster/package/service_status/