#### #### | NOTIFICATION CONSOLE | #### | ||
#### #### | <message> |
|
| #### |
#### #### | Message written to the console. | #### | ||
#### #### |
|
|
| #### |
#### #### | NOTIFICATION EMAIL | <address> | #### | |
#### #### | <message> |
|
| #### |
#### #### | Message emailed to a fully qualified email | #### | ||
#### #### | address. |
|
| #### |
#### #### |
|
|
| ##### |
#### #### | NOTIFICATION OPC |
| <level> | #### |
#### #### | <message> |
|
| #### |
#### #### | The <message> is sent to OpenView IT/Operations)#### | |||
#### #### | The value of <level> may be 8 (normal), | #### | ||
#### #### | 16 (warning), 64 (minor), 128 (major),32 | #### | ||
#### #### | (critical). |
|
| #### |
#### #### | NOTIFICATION SNMP |
| <level> | #### |
#### #### | <message> |
|
| #### |
#### #### | The <message> is sent as an SNMP trap. | #### | ||
#### #### | The value of <level> may be 1 (normal), | #### | ||
#### #### | 2 (warning), 3 (minor), 4 (major),5 (critical). #### | |||
#### #### | NOTIFICATION SYSLOG |
| #### | |
#### #### | <message> |
|
| #### |
#### #### | A notice of the event is appended to the syslog | #### | ||
#### #### | file. |
|
| #### |
#### #### |
|
|
| #### |
#### #### | NOTIFICATION TCP | <nodename>:<portnumber> | ##### | |
#### #### | <message> |
|
| #### |
#### #### Message is sent to a TCP port on the specified | #### | |||
#### #### node. |
|
| #### | |
#### #### |
|
|
| #### |
#### #### | NOTIFICATION TEXTLOG | <pathname> | #### | |
#### #### | <message> |
|
| #### |
#### #### A notice of the event is written to a user- | #### | |||
#### #### specified log file.<pathname> must be a full | #### | |||
#### #### path for the | #### | |||
#### #### 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> | #### |
84 Designing Continentalclusters