User guide

Configuring Trap Parsers Using Trap Values in the PDU
AlliedView NMS Administration Guide (Setting Up Fault Management)
9-6
9.3.1 Using Trap Values in the PDU
To help define the values for the event output, tokens are available in the incoming trap PDU. These can be used when defining
the output values for the trap parser. These are listed in the following table.
Load from
MIB
Loads the trap file from the mibs directory so the traps can translated to a trap parser. This is explained
in more detail below.
Load from
File
Loads the trap file from the conf directory. This is explained in more detail below.
Save to File Brings up the Save <type of information> to File form. Save the trap parsers as a file. The default
path is to the conf directory. This allows the configured trap parser to be used again and as a backup.
Note: When saving these files, the AlliedView NMS sets as the default directory
the
<AlliedView NMS Home>/state directory, so for example the file
path:
../conf/trap.parsers
is being saved in the
conf directory by going up one level from the state directory
(..) and then down to the
conf directory. If the user enters in the form only a file
name, that file is being saved in the default
state directory.
Cancel Cancels the update.
Help Brings up this section of this document.
Close Closes the form. If no changes were applied to the server, they are lost. If changes have been made,
there is a prompt on whether to apply the changes.
TABLE 9-3 Tokens to Access the Properties of the Trap PDU
Token Description
$Agent SNMP V1 Traps: If the device corresponding to the agent address returned by the trap has already
been discovered by Web NMS, then this token will fetch the name of the parent Managed Object, corre-
sponding to the interface object matching the agent address of the trap received. If the device corre-
sponding to the agent address of the trap has not been discovered, then this token will return the
corresponding IP address of the agent address from which the trap has been received.
For example, if a trap is received from an agent and if the corresponding device has already
been discovered by AlliedView NMS, then the interface object will be IF-web server and the
name of the parent managed object will be web server. In this scenario, $Agentwill return
webserver. In case the device is not yet discovered, then $Agent will return the IP address
(192.168.1.30.).
SNMP V2c & v3 Traps: If the device corresponding to the source address contained by the
trap received has already being discovered by AlliedView NMS, then this token will fetch
the name of the parent Managed Object, corresponding to the interface object matching the
source address of the received trap. If the device corresponding to the source address of the
trap has not yet been discovered, then this token will return the IPaddress of the Source of the
Trap.
$Community This token will be replaced by the community string of the received trap.
$Enterprise This token will be replaced by the enterprise id of the received trap. Applicable only in the case of
SNMP traps, or else replaced with a blank.
$GenericType This token will be replaced by the generic type of the received trap. Applicable only in the case of
SNMP v1 traps, or else replaced with a blank.
TABLE 9-2 Trap Parser Configuration Form
Option Description