User guide

Setting Up Fault Management Configuring Trap Parsers
914
AlliedView NMS Administration Guide
Select a Trap Parser from the list to see how the fields are configured for that Trap parser. The following table describes
these fields at a general level, as well as the option buttons. Many of the fields will have a variable name, discussed after this
table.
TABLE 9-2 Trap Parser Configuration Form
Option Description
Trap Port Port that receives the trap. You must provide at least one, or the traps will not be received. More
than one port can be entered, separated by commas.
Name Name of the trap. The name should match the event.
Nodes Specific nodes for this trap parser. Since most trap parsers are for general conditions or device
types, this field is usually not used.
Groups Grouping of nodes.
TrapOID A TrapOID uniquely identifies an SNMP v2c or SNMPv3 trap and comes along with the Trap PDU.
The TrapOID can be a match criteria.
When the TrapOID has a value that starts with the Object Identifier the match criteria is met.
Wildcard (*) can be used. When the Trap Object Identifier of the incoming trap must match exactly
the TrapOID, put the value in brackets (<>).
Enterprise
Used to specify the enterprise OID of the SNMP v1 trap. If this field is specified, then the
parser will be applied only if the trap enterprise field starts with the value you have
specified. For example, when an enterprise OID is specified as .1.3.6.1.2.1.11, then all the
OID's under this tree will be matched for traps. To avoid this kind of matching, the
enterprise OID value should be given in angular brackets like <.1.3.6.1.2.1.11>. In this case,
only the trap with this OID will be matched. If the value is given as *, then all the OID's will
be matched.
The enterprise field should not be left empty.
Generic Type
Each SNMP v1 trap has a Generic type number. This number can used for specifying the
match criteria. You can specify the Generic Type (GT) number in this field, so that the
trap parsers will be applied if the incoming trap has a GT value equal to the one specified
in this field.
Specific Type
Each SNMP v1 trap has a Specific Type number as well. You can also use this as a match
criteria for the incoming trap. When the incoming trap matches this criteria, then the trap
parsers will be applied.
Severity Severity of the resulting alarm, ranging from info to Critical.
Message Click on the click to Edit Message button to type in what will appear in the text field of the alarm.
Failure
Object
The most important field, it must reflect the actual problem.
Domain The domain name for the Event.
Category The category for a set of events or alerts.
Network Network name associated with the event.
Node Node value for the event.
Source Source name for the event. If the status of the Managed Object is to be updated with the severity of
the event, the Source should match the Managed Object name.
Group Name The group name if alarms or events are to be grouped.
Help URL The help file, which is this document.
More After selecting this button you can include additional properties for the Event. This is explained in
more detail below.