Building Disaster Recovery Serviceguard Solutions Using Continentalclusters for Linux B.01.00.00
Table 3 Monitoring definitions Parameters (continued)
Mandatory or OptionalValueParameter
Optional.The OPC level followed by the
notification message. The value of
NOTIFICATION OPC**
<level> might be 8 (normal), 16
(warning), 32 (minor), 64 (major),
128 (critical). The notification message
is provided in the next line.
Optional.The SNMP level followed by the
notification message. The value of
NOTIFICATION SNMP**
<level> might be 1 (normal), 2
(warning), 3 (minor), 4 (major), 5
(critical). The message is provided in
the next line.
Optional.The notification message is provided
in the next line.
NOTIFICATION SYSLOG**
Optional.The node name and the port number
is provided. The notification message
is provided in the next line.
NOTIFICATION TCP**
Optional.The path name to the log file is
provided. The notification message is
provided in the next line.
NOTIFICATION TEXTLOG**
Optional.The node name and the port number
is provided. The notification message
is provided in the next line.
NOTIFICATION UDP**
The following example is for the CLUSTER_EVENT parameter with unreachable value. Similarly, you can also configure
for other CLUSTER_EVENT parameter values.
CLUSTER_EVENT primary_cluster/UNREACHABLE
MONITORING_CLUSTER recovery_cluster
CLUSTER_ALERT 5 MINUTES
NOTIFICATION EMAIL admin@primary.site
"primary_cluster status unknown for 5 min. Call
recovery site."
NOTIFICATION EMAIL admin@recovery.site
"Call primary admin. (555) 555-6666."
NOTIFICATION CONSOLE
"Cluster ALERT: primary_cluster not responding."
NOTIFICATION TEXTLOG /var/adm/cmconcl/logs/logging
“primary_cluster UNREACHABLE alert”
NOTIFICATION SYSLOG
“primary_cluster UNREACHABLE alert”
NOTIFICATION UDP central_node1:6624
"primary_cluster UNREACHABLE alert"
NOTIFICATION TCP central_node1:9921
"primary_cluster UNREACHABLE alert"
NOTIFICATION OPC 64
"primary_cluster UNREACHABLE alert"
NOTIFICATION SNMP 4
"primary_cluster UNREACHABLE alert"
** These notifications can be separately configured for both CLUSTER_ALERT and
CLUSTER_ALARMS.
Mutlitple cluster events can be defined by repeating parameters.
For more information, see “Sample Continentalclusters ASCII configuration file” (page 73).
Checking and applying the Continentalclusters configuration
After editing the configuration file on any of the participating clusters in the Continentalcluster.
To apply the configuration on all the nodes in the Continentalclusters:
20 Building the Continentalclusters configuration