User's Guide

in the Site Controller Package directory and the same file path must be passed to the Device Group
Monitor service.
The Site Controller Package can be halted in the DETACH mode for maintenance in the Site
Controller Package configuration. The Site Controller Package can also fail in the cluster. In these
conditions, the Device Group Monitoring service is not available for the workloads. The service
resumes once the Site Controller Package is restarted. For more information on the Site Controller
Package and the DETACH mode halt, see “Site Controller Package” (page 341) and “Maintaining
Site Controller Package” (page 396).
Troubleshooting the Metrocluster with Continuous Access for P9000 and XP Device Group Monitor
The following is a guideline to help identify the cause of potential problems with the Metrocluster
with Continuous Access for P9000 and XP device group monitor.
• Problems with email notifications:
Metrocluster with Continuous Access for P9000 and XP 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 Continuous Access Device Status:
Metrocluster with Continuous Access for P9000 and XP 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 will not be able to
determine the status of the Continuous Access device group state. The monitor will send out
a notification to all configured destinations, via 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 Continuous Access device group. Make sure to start Raid Manager
instance with the same instance number that is defined in the package’s environment file.
Completing and Running a Continentalclusters Solution with Continuous
Access P9000 or XP
The following section describes how to configure Continentalclusters solution using Continuous
Access P9000 or XP, which requires the Metrocluster with Continuous Access for P9000 and XP
product.
Setting up a Primary Package on the Source Disk Site
Use the procedures in this section to configure a primary package on the source disk site. Consult
the Serviceguard documentation for more detailed instructions on setting up Serviceguard with
packages, and for instructions on how to start, halt, and move packages and their services between
nodes in a cluster.
200 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP