XP/CA Device Group Monitor

In the MetroCluster/CA environment where the device group state is not actively monitored and the end user may not be aware when the application data is not remotely protected for an extended period of time. Under these circumstances, the XP/CA device group monitor provides the capability to monitor the status of the XP/CA device group that is used in a package. The XP/CA device group monitor, based on a pre-configured environment variable, also provides the ability to perform automatic resynchonization of the XP/CA device group upon link recovery.




	NOTE: If the monitor is configured to automatically resynchronize the data from PVOL to SVOL upon link recovery, a Business Copy (BC) volume of the SVOL should be configured as another mirror. In the case of a rolling disaster and the data in the SVOL becomes corrupt due to an incomplete resychronization, the data in the BC volume can be restored to the SVOL. This will result non-current, bust usable data in the BC volumes

The monitor, as a package service, periodically checks the status of the XP/CA device group that is configured for the package, and sends notification to the user via email, syslog, and console if there is a change in the status of the package's device group.

XP/CA Device Group Monitor Operation Overview

The XP/CA device group monitor runs as a package service. The user can configure the monitor's setting through the package's environment file. Once the package has started the XP/CA device group monitor, the monitor will periodically check the status of the XP/CA device group. If there is a change in the status or the monitor is configured to notify after an interval of no status change, the monitor will send a notification that states the reason for the notification, a timestamp, and the status of the XP/CA device group.

Configuring the Monitor

Use the following steps to configure a monitor for a package's device group:

Configure the monitor's variables in the package environment file.
Configure the monitor as a service of the package.

Configure the Monitor's Variables in the Package Environment File.

Edit the following variables of the monitor's section in the environment file <pkgname>_xpca.env as follows:




	NOTE: See Appendix A for an explanation of these variables.

Uncomment the MON_POLL_INTERVAL variable and set it to the desired value in minutes. If this variable is not set, it will default to a value of 10 minutes.
Uncomment the MON_NOTIFICATION_FREQUENCY variable and set it to the desired value. This value is used to control the frequency of notification message when the state of the device group remains the same after the first check of the device group's state. If the value is zero, the monitor will only send notification when the state of the device group has changed. If the variable is not set, the default will be 0.
If you want to receive notification messages over email, uncomment the MON_NOTIFICATION_EMAIL variable and set it to a fully qualified email address. Multiple email addresses can be configured using comma as separator between the addresses.
If you want notification messages to be logged in the syslog file, uncomment the MON_NOTIFICATION_SYSLOG variable and set it to 1.
If you want notification messages to be logged on the system's console, uncomment the MON_NOTIFICATION_CONSOLE variable and set it to 1.
If you want an automatic resynchronization upon link recovery, uncomment the AUTO_RESYNC variable and set it to either 0, 1 or 2.
If AUTO_RESYNC is set to 0 (DEFAULT), the monitor will not try to do the resynchronization from PVOL to SVOL. This setting will only send notifications.
If AUTO_RESYNC is set to 1, the monitor will split the remote BC if one is configured from the mirror group before trying to do the resynchronization from PVOL to SVOL.
If AUTO_RESYNC is set to 2, the monitor will only do the resynchronization from PVOL to SVOL when it finds the MON_RESYNC file in the package directory on the node that the package is running. The monitor will not manage the remote BC prior to and after the resynchronization. This setting is used if the user wants to manage the BC themselves.
To enable the CA resynchronization for AUTO_RESYNC=2, it is necessary to create a file using the HP-UX command touch. For example:
# touch /etc/cmcluster/packageA/MON_RESYNC
(where /etc/cmcluster/packageA is the package directory)
After the monitor detects the MON_RESYNC file, it is automatically removed.
The following is an example of the XP/CA device group monitor definition section in the environment file (<packagename>_xpca.env>) where the monitor will perform the following:

poll every 15 minutes.
send a notification on every third polling, if the state of the device group remains the same.
send the notifications to sysadmin1@hp.com and sysadmin2@hp.com.
log notifications to system log file, syslog.
display notifications to system console.
perform automatic resynchronization with BC management when detecting the device group local state change to PVOL-PSUE or PVOL-PDUB.

MON_POLL_INTERVAL=15MON_NOTIFICATION_FREQUENCY=3MON_NOTIFICATION_EMAIL=sysadmin1@hp.com,sysadmin2@hp.comMON_NOTIFICATION_SYSLOG=1MON_NOTIFICATION_CONSOLE=1AUTO_RESYNC=1

Configure XP/CA Device Group Monitor as a Service of the Package

Add the monitor as a service in the package's configuration file and control script file as follows:

In the package's configuration file, add the following lines:

SERVICE_NAME pkgXdevgrpmon.srv

SERVICE_FAIL_FAST_ENABLED NOSERVICE_HALT_TIMEOUT 5




	NOTE: The SERVICE_HALT_TIMEOUT value of 5 is a recommended value. If the value is set to lower than 5 seconds as the service halt timeout, then it may not allow enough time for the monitor to properly clean itself up.

In the package's control script file, add the following lines on the "SERVICE NAMES AND COMMANDS" section:

SERVICE_NAME[0]="pkgXdevgrpmon.srv"SERVICE_CMD[0]="/usr/sbin/DRMonitorXPCADevGrp <full path name of the package environment file>"SERVICE_RESTART[0]="-r 10"




	WARNING! If the CA links are still down while the monitor is trying to do the resynchronization and another failure occurs that causes a remote failover to the secondary site, the SVOL's BC volumes will remain split from its mirror group. This will only occur if the monitor is configured to perform automatic resynchronization using AUTO_RESYNC=1.

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.

XP/CA Device Group Monitor

Technical documentation

» Table of Contents

» Glossary

» Index

XP/CA Device Group Monitor Operation Overview

Configuring the Monitor

Configure the Monitor's Variables in the Package Environment File.

Configure XP/CA Device Group Monitor as a Service of the Package

Troubleshooting the XP/CA Device Group Monitor