Question:
Who reads the trapd.conf file for formatting traps? Which app writes to
trapd.log?
These may sound like funny questions, but we are trying to diagnose a
problem with unformatted traps. I wrote a sniffer application (NV API) to
register with trapd and receive traps. I display the PDUs which contain
'variables' to be used by trapd.conf, $1 $2 $3, etc. As we know, trapd.conf
specifies what nvevents will display using $e, "Text $1, Text $2, etc".
At what point are the PDUs parsed and formatted to be displayed using the
rules in trapd.conf for nvevents?
We have a COTS application that is having some problems when trapd.conf does
not have an absolute OID defined for formatting. Netview works fine, but
the COTS app calls it unformmatted. This COTS application is designed and
sold to work with Netview. An example of what I am trying to explain is:
trapd.conf has:
Hello-World .1.3.6.1.4.1.5 -> "Hello World"
-- Trap comes in with oid .1.3.6.1.4.1.5.180
Netview -> "Hello World"
COTS -> "Unformatted trap"
-- If we change trapd.conf to look like this:
Hello-World .1.3.6.1.4.1.5 -> "Hello World"
180-Hello-World .1.3.6.1.4.1.5.180 -> "180 - Hello World"
-- Trap comes in with oid .1.3.6.1.4.1.5.180
Netview -> "180 - Hello World"
COTS -> "180 - Hello World"
Now, as a side-note, when this same COTS application talks to another type
of NMS (non-Netview), it works.
The other NMS's trapd.conf does look like this though:
Hello-World .1.3.6.1.4.1.5.* -> "Hello World"
-- Trap comes in with oid .1.3.6.1.4.1.5.180
Other NMS -> "Hello World"
COTS -> "Hello World"
Thanks,
Jason Allison
Principal Engineer
ARINC Incorporated
Office: (410) 266-2006
FAX: (410) 573-3026
|