nv-l

Re: 3COM Corebuilder 3500 traps

1999-12-08 11:40:51
Subject: Re: 3COM Corebuilder 3500 traps
From: James Shanks <James_Shanks AT TIVOLI DOT COM>
To: nv-l AT lists.tivoli DOT com
Date: Wed, 8 Dec 1999 11:40:51 -0500
The first thing you need to do is use xnmtrap to modify these traps so that they
each say something different than just "a power supply has failed"  -- have them
display whatever variable makes them unique.

I am puzzled that you want to send all three traps to TEC but display only one,
but that is your choice.  You have several options.  You can build a filter or
build a ruleset to use with the display, or you could make all three traps "Log
Only" and build a ruleset to catch one or more of them, and then in action node,
use snmptrap to create your own custom trap which says just what you want, and
have that display in the event window and get sent to TEC.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Drew Van Order <dvanorder AT DTTUS DOT COM> on 12/07/99 09:35:45 PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
      <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  Re: 3COM Corebuilder 3500 traps





     Thanks James.

     3COM has been trying to convince me that this is a 'product feature',
     and of course, we know how vendors will often do anything to avoid
     blame for something poorly written. To answer your question, I do get
     3 event cards. However, the same trap type (power_supply_failed) is
     used for each one, and if I understand correctly, setting the trap
     type to log only would stop everything from going to TEC. Attached is
     what appears in trapd.log--might help explain.

     Thanks


______________________________ Reply Separator _________________________________
Subject: Re: 3COM Corebuilder 3500 traps
Author:  James_Shanks AT TIVOLI DOT COM at Internet-USA
Date:    12/7/1999 11:37 AM


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 AT DTTUS DOT COM> on 12/07/99 11:23:09 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
      <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT 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

Attachment: 3comtr~1.txt
Description: Text - character set unknown

<Prev in Thread] Current Thread [Next in Thread>