Installing and Using Monitors
Adding a Monitoring Request
Table | Monitoring Requests Configuration Settings (Continued) | |
|
|
|
Setting | Description |
|
|
|
|
Notification | The following notification methods are available. |
|
Method | EMAIL* - sends notification to the specified email address |
|
|
| |
| TEXTLOG* - sends notification to specified file |
|
| SNMP - sends notification using SNMP traps |
|
| CONSOLE - sends notification to the system console |
|
| TCP - sends notification to the specified target host and port |
|
| UDP - sends notification to the specified target host and port |
|
| OPC - sends notification to OpenView ITO applications (available |
|
| only on systems with OpenView installed). |
|
| SYSLOG - sends notification to the system log |
|
| Only one notification method can be selected for each monitor |
|
| request, consequently you will need to create multiple requests to |
|
| direct event notification to different targets. * These are the only |
|
| methods that deliver the entire content of the event message. The |
|
| remaining methods alert you to the occurrence of an event, but |
|
| require you to retrieve the complete message content using resdata |
|
| explained later in this chapter. |
|
|
|
|
Table | Event Severity Levels |
|
|
|
|
Event |
|
|
Severity |
| MC/ServiceGuard |
Level | Description | Response |
|
|
|
Critical | An event that will or has already | If MC/ServiceGuard is |
| caused data loss, system down time, | installed and this is a |
| or other loss of service. System | critical component, a |
| operation will be impacted and | package |
| normal use of the hardware should | occur. |
| not continue until the problem is |
|
| corrected. Immediate action is |
|
| required to correct the problem. |
|
|
|
|
Serious | An event that may cause data loss, | If MC/ServiceGuard is |
| system down time, or other loss of | installed and this is a |
| service if left uncorrected. System | critical component, a |
| operation and normal use of the | package |
| hardware may be impacted. The | occur. |
| problem should be repaired as soon as |
|
| possible. |
|
|
|
|
Major | An event that could escalate to a | If MC/ServiceGuard is |
Warning | Serious condition if not corrected. | installed and this is a |
| System operation should not be | critical component, a |
| impacted and normal use of the | package |
| hardware can continue. The problem | NOT occur. |
| should be repaired at a convenient |
|
| time. |
|
|
|
|
48 | Chapter 2 |