Event Monitoring Service Version A.03.10 Release Notes

18 Chapter1

Known Problems and Workarounds

<package_name>/<service_name> may be incorrectly reported. When

monitoring the service status of a package running locally and the

ServiceGuard coordinator node is not the same node, service status may

be incorrectly reported as UNKNOWN or DOWN when itis reallyUP. cmviewcl

shows the service is UP.

What is the workaround? Conﬁgure package and service status

monitoring on each node in the cluster. Then correlate the data reported

on each node. The coordinator node will report status of UNKNOWN for the

remote service. UNKNOWN state means that the service is up and running

somewhere in the cluster.

opcmsg protocol

• What is the problem? The opcmsg protocol for communicating with

IT/Operations (ITO) is supported for managed nodes running HP-UX

10.20, but it is not yet available in EMS on HP-UX 11.0.

• What is the workaround? For HP-UX 11.0 do one of the following:

— conﬁgure EMS monitoring requests to send SNMP traps to ITO

for event notiﬁcations from 11.0 managed nodes

— apply patch PHSS_20326

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