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

Building a Continental Cluster
Building the ContinentalClusters Configuration
Chapter 5226
#### DATA_RECEIVER_PACKAGE
eastcoast/nfsreceiverpkg ####
## ##
####
# # # # R E C O V E R Y _ G R O U P _ N A M E h p g r o u p
####
#### PRIMARY_PACKAGE westcoast/hppkg
####
#### DATA_SENDER_PACKAGE westcoast/hpsenderpkg
####
#### RECOVERY_PACKAGE eastcoast/hpbackuppkg
####
#### DATA_RECEIVER_PACKAGE
eastcoast/hpreceiverpkg ####
## ##
####
RECOVERY_GROUP_NAME
PRIMARY_PACKAGE
# DATA_SENDER_PACKAGE
RECOVERY_PACKAGE
# DATA_RECEIVER_PACKAGE
Editing Section 3—Monitoring Definitions
Finally, you enter monitoring definitions, which define cluster events
and set times at which alert and alarm notifications are to be sent out.
Define notifications for all cluster events—Unreachable, Down, Up, and
Error.
Although it is impossible to make specific recommendations for every
ContinentalClusters environment, here are a few general guidelines
about notifications.
1. Specify the cluster event by using the CLUSTER_EVENT keyword
followed by the name of the cluster, a slash (“/”) and the name of the
status—Unreachable, Down, Up, or Error. Example:
CLUSTER_EVENT LAcluster/UNREACHABLE
2. Define a CLUSTER_ALERT at appropriate times following the
appearance of the event. Specify the elapsed time and include a
NOTIFICATION message that provides useful information about the
event. You can create as many alerts as needed, and you can send as
many notifications as you wish to different destinations (see the