Event Monitoring Service Version A.03.20.01 Release Notes for HP-UX 11i

Chapter 1 15

Known Problems and Workarounds

Name services requirement

What is the problem? EMS may not function if you are running name

services that do not use /etc/services, such as NIS, DNS, or X.500.

The port number for the EMS registrar is listed in /etc/services. If

you are running a different name lookup service, for example NIS, and it

is not conﬁgured to use /etc/services as part of the name lookup

process, then EMS monitors will not be able to ﬁnd the registrar

program and will not function.

What is the workaround? You can do either of the following:

• On the name server, add the registrar services line to the appropriate

services ﬁle for the name lookup service you are running. The line

should have the same port number as the line in /etc/services, for

example:

registrar 1712/tcp # resource monitor service

If inetd is not listening on port 1712, be sure the following entry is in

/etc/inetd.conf:

registrar stream tcp nowait root \

/etc/opt/resmon/lbin/registrar \

Table 1-4

monitor name

listed in output

command to re-register the monitor’s

active persistent requests

clustermond resls /cluster/localNode/status

diskmond resls /vg

fsmond resls /system/ﬁlesystem/availMb

lanmond resls /net/interfaces/lan/status

mibmond resls /system/numUsers

pkgmond resls /cluster/package/package_status

rdbmsmond resls /rdbms

svcmond resls /cluster/package/service_status