SNMP trap configuration

Description of the configuration file that is used by the SNMP Data Provider to render trap information in a more easily readable form. The file is also used to assign categories, severities, status, and source IDs to traps.

Also contains instructions for modifying the default file or substituting your own configuration file.

SNMP trap configuration file, trapcnfg

At startup, the SNMP Data Provider reads a configuration file named trapcnfg. One purpose of this file is to translate SNMP trap information into a more readable form. Another is to assign categories, severities, status, and source IDs to specific traps, since these categories are not defined by SNMP.

You can modify the trapcnfg file to suit your site-specific needs by adding new trap or enterprise definitions or changing the existing ones. You can also use your own configuration file.

Use the HP OpenView trapd.conf file

The trapcnfg file is similar in format, but not identical, to the HP OpenView Network Node Manager trap configuration file trapd.conf. You can copy the OpenView file and reuse many of the definition statements if necessary.

Types of records

trapcnfg contains three types of records or record blocks:
comments
Comment records begin with a number sign (#).
enterprise definitions
Enterprise definitions consist of two blank-delimited tokens, where the first token is a name and the second is an object identifier (OID) surrounded by curly brackets ({ }).
trap definitions
Trap definitions consist of eight blank-delimited tokens. Trap definitions are block records because each definition might consist of multiple records.

The first type is self-explanatory. (Figure 1) shows examples of the second and third types.

The first example in Figure 1 shows an enterprise definition record which defines enterprise OID 1.3.6.1.4.1.311.1.1.3.1.1 as being Microsoft Windows NT.

The second example shows a trap definition record that defines trapName MSNTCOLD as being associated with enterprise OID 1.3.6.1.4.1.311.1.1.3.1.1, generic trap number 0, and specific trap number 0. Notice that the severity is in decimal form whereas the category is in textual form. Severities are translated into their textual form before they are displayed. The next record in the type 3 record block is the short description, which the Agent Builder does not use. The Agent Builder uses the long description that is enclosed within the delimiters SDESC and EDESC.

Figure 1. Examples of configuration record types 2 and 3
Record types

Defaults for the trapcnfg file

Tables that list the defaults that are supported by the SNMP Data Provider.

Supported categories

(Table 1) shows the categories that are supported by the Agent Builder.
Table 1. Categories supported by the SNMP Data Provider
Category Textual representation
0 Threshold Events
1 Network Topology Events
2 Error Events
3 Status Events
4 Node Configuration Events
5 Application Alert Events
6 All Category Events
7 Log Only Events
8 Map Events
9 Ignore Events
(Table 2) lists the severities that are supported by the Agent Builder.
Table 2. Severities supported by the SNMP Data Provider
Severity Textual representation
0 Clear
1 Indeterminate
2 Warning
3 Minor Error
4 Critical
5 Major Error

Supported statuses

(Table 3) shows the statuses that are defined in the Agent Builder configuration file.
Table 3. Statuses supported by the SNMP Data Provider
Status Textual representation
0 Unchanged
1 Unknown
2 Up
3 Marginal
4 Down
5 Unmanaged
6 Acknowledge
7 User1
8 User2

Supported source IDs

(Table 4) lists the source IDs supported by trapcnfg.
Table 4. Source IDs supported by the SNMP Data Provider
Source ID Description
a Application
A Agent
C Xnmcollect
d Demo
D Data Collector
E Nvevents
I Ipmap
L LoadMIB
m Shpmon
M IP topology
n netmon related
N netmon-generated traps
O OSI SA
P Non-IP traps
r Tralertd
s Spappld
S Security Agent
t Xnmtrap
T Trapd
V Vendor related
? Unknown