User guide

Reordering the Trap Parser List Configuring Event Parsers
9-9
AlliedView NMS Administration Guide (Setting Up Fault Management)
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 NMS Home>/conf
directory will be loaded automatically when the server is restarted and then displayed in
the Configured Event Parsers List.
Note: Event parsers are important to alarm correlation and should only be changed under the supervision of
Allied Telesis Technical Support personnel. If you delete any of those you made degrade or destroy
existing NMS functionality.
To configure the Event parser, select Edit -> Configure -> Event Parsers from the main menu of the Network Events Panel.
The Event Parser Configuration form appears, as shown in the following figure.