I am not certain that I can answer all of your questions, but I will try.
But whether COTS works the way you want, is not something I can guarantee.
I have never heard of it before.
trapd is the only app that writes to trapd.log. As you know, he formats
the trap according to what is in trapd.conf. The trap formatting
routines, which are in libems.a, search for the best match on the incoming
OID. In other words, if the OID is .1.3.6.1.4.1.5.180 and trapd has only
.1.3.6.1.4.1.5, he will make the best guess he can, and format the trap if the
specific
id matches what is available under that OID. He uses "No FMT Found" only
when the specific id isn't available, or the closest match he can make on
the incoming OID is just .1.3.6.1.4.1. nvevents uses the same formatting
routines in the same shared library, so
his formatting always matches. Other processes in NetView , such as
nvserverd and nvcorrd, also read trapd.conf, using the same facilities.
What's your other NMS? I cannot answer for them but NetView does not
accept a format of .1.3.6.1.4.1.5.*, because in effect, it is already implied.
Some NetView traps come in as
.1.3.6.1.4.1.2.6.3 and others as .1.3.6.1.4.1.2.6.3.1 and trapd and nvevents
recognize both of these as NetView traps. There is
no need in NetView to define down to the last element, unless you want to
ditinguish those traps from others (the way Cisco does, for example). I
cannot answer for COTS. But NetView has worked this same way since I have
been involved, which goes all the way back to Version 3 at least.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group
"Allison, Jason (JALLISON)" <JALLISON@arinc.com>
07/10/2002 09:49 AM
To: "'nv-l'" <nv-l@lists.tivoli.com>
cc: "Allison, Jason (JALLISON)" <JALLISON@arinc.com>
Subject: [nv-l] trapd vs nvevents
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
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|