If the vendor does not identify them for
you in the MIB or documentation, you will just have to look at your trapd.log and pick them out and define them.
Some vendors are very unhelpful L .....I have had
to go through a month of trapd.log history and just grep out the "no known format" messages.
Then, try to figure out what they mean and
what severity they represent.
Here is the method of adding the
definitions, once you figure out what they are. You probably already know this
Options à Event Configuration à Trap Customization
The top half of the screen is for adding
new enterprises.Press [Add] fill
in the blanks Netegrity_widgits and the OID WITHOUT a
After you get your Enterprises(s) defined,
then click the newly added Enterprise and go to the bottom half of the screen and click [Add].
This will pop a new window where you define
all of your generic/specific traps for that specific Enterprise.
You could also do the same thing with
mib2trap, but you would have to massage the appropriate field values before you
run the script it creates.
Hope this helps,
-----Original Message----- From: Edwards, JT - ESM
[mailto:JEdwards3 AT wm DOT com] Sent:Wednesday, September 22, 2004 To: 'nv-l AT lists.us.ibm DOT com' Subject: RE: [nv-l]
Ok I have to define each
and every variation? How do I identify those?
-----Original Message----- From: owner-nv-l AT lists.us.ibm DOT com
[mailto:owner-nv-l AT lists.us.ibm DOT com]On Behalf
Of Davis, Donald Sent: Wednesday, September 22,
2004 1:47 PM To: 'nv-l AT lists.us.ibm DOT com';
'Edwards, JT - ESM' Subject: RE: [nv-l] Mib2trap
Nothing is broken. Trapd has always worked this way.
If the vendor defines n.n.n.n extensions to their (vendor) Enterprise id, then you must define each as a separate enterprise.
Look at your Cisco definitions....
There is more there than just 184.108.40.206.4.1.9
You must define an
enterprise ID for every variation the vendor has used.
Specific: 4 ----- means
the smpolicysrv is melting down
-----Original Message----- From: James Shanks
[mailto:jshanks AT us.ibm DOT com] Sent: Wednesday, September 22,
2004 2:08 PM To: nv-l AT lists.us.ibm DOT com Subject: RE: [nv-l]
Well, JT, I don't know what to tell you exactly. When
you sent the FMTCHG event you should have seen an entry in trapd.log
that it was received. I've forgotten the exact text but it is something
like "format file changed." If the reload was successful, then you
would not see an indication of that, but if there's anything wrong with the
updated file, then you'd see an error message trap, sent by trapd
himself, about how it could not be loaded because of such-and-such error
on line so-and-so. It's very specific. But
assuming that it loaded OK, it comes down to this: trapd
doesn't think that the incoming traps are defined, and you think they are.
can suggest is that you gather some data and call Support. If trapd is running with the -x option already, then toggle
the trapd.trace on from the command line ("trapd -T") and after you have traced a couple examples
of the failure, pass that data to Support : your trapd.conf
file, trapd.log, and trapd.trace,
and let them see what sense they can make of it. Also include the addtrap script you created from the MIB just for good
measure, and the MIB too. Might as well be thorough.
If trapd is not running with -x (and "ps -ef | greptrapd" will tell you)
then you can set that in serversetup with hex dump
all packets option. This gives us a hex version of the trap when we
trace, so we can follow through the formatting of it.
If Level 2 cannot figure this out, and they think trapd
is somehow broken, you can be sure they'll notify me and I'll be looking too.
If the code is broken, well, then eventually it will be my job to fix it
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
This electronic mail and any files transmitted with it are confidential and are
intended solely for the use of individual or entity to whom they are addressed.
If you are not the intended recipient or the person responsible for delivering
the electronic mail to the intended recipient, be advised that you have
received this electronic mail in error and that any use, dissemination,
forwarding, printing, or copying of this electronic mail is strictly
prohibited. If you have received this electronic mail in error, please
immediately notify the sender by return mail.