Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access XP P9000 for Linux B.12.00.00

Troubleshooting the Metrocluster with Continuous Access XP P9000 for Linux device
group monitor
The following is a guideline to help identify the cause of potential problems with the Metrocluster
with Continuous Access XP P9000 for Linux device group monitor.
• Problems with email notifications:
Metrocluster with Continuous Access XP P9000 for Linux 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 and connects to port number 25 using localhost as host
name. If a different port number is defined, the mail server must be restarted in order for it to
connect to the correct port. The mail server must be configured to listen on localhost address.
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 such as sendmail configured on the local node or mail
server is not configured to listen on localhost. A mail server needs to be configured to listen
on localhost 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 Continuous Access Device Status:
Metrocluster with Continuous Access XP P9000 for Linux device group monitor relies on the
Raid Manager instance to get the Continuous Access device group state. Under the
circumstances when the local Raid Manager instance fails, the monitor is unable to determine
the status of the Continuous Access device group state. The monitor sends a notification to all
configured destinations, via email, stating that the state has changed to an UNKNOWN
status. Since the monitor does not try to restart the Raid Manager instance, you must restart
the Raid Manager instance before the monitor is able to determine the status of the Continuous
Access device group. Ensure to start Raid Manager instance with the same instance number
that is defined in the package’s configuration file.
Troubleshooting Metrocluster 51