&+$37(5$&7,21$1'(9(177$%/(6
.1 and .2 are added to show two subsequent actions to be taken. When the .AUTHFAIL alarm is detected, the terminal server “phones home” and pages, sending the alarm and the comments.
NOTE: DOLIST cannot be nested (a DOLIST inside another DOLIST).
ALARM | ACTION | PARAMETER | COMMENTS |
|
.AUTHFAIL | DOLIST |
| HACKER ALERT | |
.AUTHFAIL.1 | PHONHOME |
|
|
|
.AUTHFAIL.2 | PAGE |
|
|
|
NOTE: The actions in a DOLIST are dispatched in the order shown in the Action Table, but they are not necessarily executed in that order. For example, the PHONHOME action may be rescheduled if the modem is already in use. In that case, the system will begin to execute the PAGE action without waiting for PHONHOME to complete.
Planning the Action Table
Before you start to build your Action Table, you should determine which alarm conditions to monitor and decide what action should be taken for each alarm condition.
A worksheet is provided to assist you in planning alarm/status messages monitored by the terminal server, and actions taken by the terminal server when they are received. To help guide you, we have also provided an example of a filled in worksheet at the end of this section.
NOTE: You must have at least Sysop 3 level access to add, delete or change Action Table items.
1.Determine which alarm conditions to monitor.
Examine the types of alarms to which you or your staff respond on a regular basis and then define them in the worksheet.
100
