Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Building a Metropolitan Cluster Using MetroCluster/CA
XP/CA Device Group Monitor
Chapter 3 121
Troubleshooting the XP/CA Device Group Monitor
The following is a guideline to help the user identify the cause of possible
problems with the XP/CA device group monitor.
Problems with email notifications
XP/CA device group monitor uses SMTP to send out email notifications.
All email notification problems are logged in the package log file.
If a warning message in the package log file indicates the monitor is
unable to determine the SMTP port. it is caused by not having the SMTP
port defined in the /etc/services file. The monitor assumes that SMTP
port is 25. If a different port number is defined, the monitor will need to
be restarted in order for it to connect to the correct port.
If an error message in the package control log file states that the SMTP
server cannot be found is caused by not having a mail server configured
on the local node, such as sendmail. A mail server needs to be configured
and run in the local node for email notification. Once the mail server is
running in the local node, the monitor will start sending email
notifications.
Problems with Unknown CA Device Status
XP/CA device group monitor relies on the Raid Manager instance to get
the CA device group state. Under circumstances where the local Raid
Manager instance fails, the monitor will not be able to determine the
status of the CA device group state. The monitor will send out a
notification to all configured destinations (i.e. email) stating that the
state has changed to an UNKNOWN status. Since the monitor will not
try to restart the Raid Manager instance, the user is required to restart
the Raid Manager instance before the monitor will be able to determine
the status of the CA device group. Make sure to start Raid Manager
instance with the same instance number that is defined in the package’s
environment file.