Designing a Continental Cluster
Building the Continentalclusters Configuration
Chapter 288
#### A notice of the event is written to a user- ####
#### specified log file. <pathname> must be a full ####
#### path for the user-specified file.The user ####
#### specified file must be under /var/opt/resmon/log directory. ####
#### ####
#### NOTIFICATION UDP <nodename>:<portnumber> ####
#### <message> ####
#### Message is sent to a UDP port on the ####
#### specified node. ####
#### ####
#### For the cluster event, enter a cluster name followed by ####
#### a slash ("/") and a cluster condition (UP, DOWN, UNREACHABLE, ####
#### ERROR) that may be detected by a monitor program. ####
#### ####
#### Each cluster event must be paired with a monitoring cluster. ####
#### Include the name of the cluster on which the monitoring ####
#### will take place. Events can be monitored from either the ####
#### primary cluster or the recovery cluster. ####
#### ####
#### Alerts, alarms, and notifications have the following syntax. ####
#### ####
#### CLUSTER_ALERT <min> MINUTES <sec> SECONDS ####
#### Delay before the software issues ####
#### an alert notification about the ####
#### cluster event. ####
#### ####
#### CLUSTER_ALARM <min> MINUTES <sec> SECONDS ####
#### Delay before the software issues ####
#### an alarm notification about the ####
#### cluster event and enables the cmrecovercl(1m) ####
#### command for immediate execution. ####
#### ####
#### NOTIFICATION <type> ####
#### <message> ####
#### A string value which is sent from the ####
#### monitoring cluster for a given event ####
#### to a specified destination. The <message>, ####
#### which can be no more than 170 characters, ####
#### is also appended to the ####
#### /var/opt/resmon/log/cc/eventlog ####
#### file on the monitoring node in the cluster ####
#### where the event was detected. ####
#### ####
#### Example: ####