High Availability Monitors Version A.03.00 Release Notes

Chapter 1 7
Required Patches and Known Problems
Name services
• 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, such as NIS, and
it is not configured to use /etc/services as part of the name lookup
process, then EMS monitors will not be able to find the registrar
program and will not function.
• What is the workaround? You can do one of the following:
• On the name server, add the registrar services line to the
appropriate services file for the name lookup service you are
running. The line should have the same port number as the line in
/etc/services:
registrar 1712/ tcp # resource monitor service
• Add the /etc/services file to the lookup path your name lookup
service uses. For example, modify the nsswitch.conf file to refer
to /etc/services if you are running NIS.
Auto-start of disk monitor may fail
• What is the problem? At the end of the swinstall process, the disk
monitor is automatically started up with the resls /vg command.
This command may fail if your system is not ready, for example, if the
Internet Services daemon inetd is not already running when the
command is issued.
• What is the workaround? If the automatic command fails, enter the
resls /vg command yourself. (First, verify that inetd is running.)