Designing and Managing Behavior Models - Using Trap Masks - Documenting a Trap Mask -
Previous: Examples of Trigger Functions Next: Enabling a Trap Mask

Documenting a Trap Mask

This section explains how to add documentation (notes) to a trap mask and what should be covered in that documentation.

How to Create Notes for a Trap Mask

You can add notes to a trap mask by following the procedure outlined in this subsection.

To add notes to a trap mask:

From the client's Admin menu, choose Mask List.
NerveCenter displays the Mask List window.
Mask List Window

Click the thumbnail above to view full-sized image.
Select the Open button.
The Mask Definition window appears.
Mask Definition Window

Click the thumbnail above to view full-sized image.
Make sure that your mask is not enabled.
In the Mask Definition window, select the Notes button.
The Mask Notes window is displayed.
Mask Notes Window

Click the thumbnail above to view full-sized image.
Enter your documentation for the trap mask by typing in this window. See the section What to Include in Notes for a Trap Mask for information on what type of information you should enter here.
Select the OK button at the bottom of the Mask Notes window.
The Mask Notes window is dismissed.
Select the Save button in the Mask Definition window.
Your notes are saved to the NerveCenter database. They can now be read by anyone who opens the definition for your mask and selects the Notes button.

What to Include in Notes for a Trap Mask

We recommend that you include the following information in the notes for your trap mask:

Purpose of the mask
Associated alarms
Vendor-specific information (if appropriate)
Description of the trigger function (if appropriate)

For example, let's consider the trap mask shown in the figures below.

Basic Definition

Trigger Function

The notes for this trap mask should look something like this:

Purpose: Detects a trap indicating that a Frame Relay virtual 
circuit has changed states.

Related alarms: IF-ifFramePVCStatus. This alarm tracks whether the 
Frame Relay Permanent Virtual Circuit interface is active or 
inactive.

Vendor information: The trap of interest has an Enterprise of 
1.3.6.1.2.1.10.32 (the Frame Relay group) and a Specific trap 
number of 1. The second variable binding contains the value of 
frCircuitState, which indicates whether a virtual circuit is 
invalid (1), active (2), or inactive (3).

Trigger function: If frCircuitState equals 2, the function fires 
the trigger If-FramePVCUp, and if frCircuitState equals 3, it 
fires If-FramePVCDown.

Previous: Examples of Trigger Functions	Next: Enabling a Trap Mask
Please send comments or corrections to Information Development	This file was last updated on 10 October 2000