Well, I don't have this hardware, but the only way you can stop three traps
coming to NetView is ask 3Com how to configure their device so that it only
sends one.
mib2trap has nothing to do with correlation -- he just creates a script with
addtrap commands which will add these traps, in some default format, to those
already defined in trapd.conf. Thus when the three traps arrive they will have
some message associated with them rather than "NO FMT FOUND". But you will
still get all three traps. That won't change.
By three tickets, do you mean three event cards? You will still get those too,
unless the Event Category for two of the traps is changed to "Log Only". Then
all three will get written to the trapd.log, but only one will display in the
window. Obviously, the "real" solution is have 3Com not send but one trap in
the first place. But if you cannot do that, then you can suppress the other
two.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Drew Van Order <dvanorder@DTTUS.COM> on 12/07/99 11:23:09 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: 3COM Corebuilder 3500 traps
All,
I'm working with 3COM regarding traps sent to NetView from a CB 3500
layer 3 switch. The issue is the power_supply_failed trap. When you
pull one of the redundant supplies, you get 3 separate traps, each of
which is power_supply_failed, but with a unique OID that states 5
volts, 12 volts, and A/C failed.
If 3COM chose to create 3 traps instead of one, this would not be an
issue, but I must now somehow customize/correlate within NetView so I
don't get 3 tickets ( I'm using mib2trap). I'm fairly new to
customizing traps--is this common in the SNMP world, or do some
vendors just supply substandard MIBs? Can others who have CB3500's
provide any advice?
Thanks,
DVO
|