User guide

Setting Up Fault Management Configuring Event Parsers
918
AlliedView NMS Administration Guide
9.3.2 Loading from a MIB
To load a MIB with defined traps that can then be translated to trap parsers, click Add Trap Parser, and then click Load from
MIB. A dialog box prompts for the filename of the MIB.
The filename path should be relative to the <Web NMS Home>/servlets directory. If the MIB depends on (imports) other
MIB files, they should be listed in order, separated by spaces.
For example, if A-MIB imports B-MIB imports C-MIB (all files in the <Web NMS Home>/mis directory, then enter the
following:
Input: ../mibs/C-MIB ../mibs/B-MIB ../mibs/A-MIB
The trap parsers are created only from the last MIB file. Clicking Create Parsers will load the MIBs and create trap parsers
from the last file. You can then set the event object fields for the created parsers. If no severities are specified, the default
Info will be used.
9.3.3 Loading from a File
To load a set of trap parsers previously saved by the Save to File button and add them to the list of Trap Parsers, click Load
From File, and in the dialog box, enter the filename on the server that contains the trap parsers. The trap parsers are usually
stored in
<Web NMS Home>/conf/trap.parsers. Clicking Load will load the trap parsers from the file. Parsers with the same
matching criteria are replaced. If the Trap Parser name is the same, there is confirmation prompt to replace the existing one.
Once loaded, the Apply to Server button makes the changes permanent. The trap parsers in the
trap.parsers file will load the
next time the AlliedView NMS server starts.
9.3.4 Reordering the Trap Parser List
The list for Trap Parsers is in the order the AlliedView NMS tries to find a match. To reorder the list, select a Trap Parser
and drag it up or down the list.
9.4 Configuring Event Parsers
9.4.1 Overview
When an event arrives into the AlliedView NMS, the event parsers list is checked to see whether the incoming event satisfies
the match criteria of the event parser. If the event parser matches, the event is passed through the corresponding event
parser. The outgoing event from the parser is then matched with the remaining set of parsers (if any, in sequence). If there
are any matches, then the event will be passed through those parsers. This process will continue till there are no parsers left
to be scanned.
In the Configured Event Parsers List, the user can view the list of currently configured event parsers. On clicking any of them,
the corresponding details will be listed. By default, the event parsers that are saved in the file event.parsers under
<AlliedView
$IF-
SourceMO
This tag is similar to $SourceMO, except that the properties of the interface managed object
corresponding to the source address of the received trap could be accessed using this tag.
Usage:- $IF-SourceMO(PropertyName)
$IF-Source This is similar to $Source, except that it results in the interface object name corresponding to the
source address of the trap received.
Usage:- $IF-Source
TABLE 9-3 Tokens to Access the Properties of the Trap PDU (Continued)
Token Description