James, idea is to only suppress certain
traps (not all) coming from the router. We rather suppress them at the source,
but that may require some work for over 2000 routers.
I am having trouble finding and loading
Cisco DLSW trap definitions (OID: 1.3.6.1.4.1.9.9.74.2). BTW, if someone has a
working trap definition shell script (via mib2trap) for CISCO-DLSW-EXT-MIB.my -
please drop me a copy. For now, I have added this OID via xnmtrap with a
generic 6 and specific 2 (that's what we were seeing come in tons) with
the log-only option.
-----Original Message-----
From: owner-nv-l@lists.us.ibm.com
[mailto:owner-nv-l@lists.us.ibm.com] On
Behalf Of James Shanks
Sent: Tuesday, March 23, 2004
11:44 AM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] unknown format
suppression
Well, I think that's a bad idea, but it can be done.
Just
edit trapd.conf with xnmtrap, find the Enterprises (1.3.6.1.4.1) entry which
has that message as its log message, and change the status to "Log
Only"
But
why configure a box to send traps to NetView if you care so little about them
that (a) you don't care what they look like and (b) you don't want the operator
to see them? That's just a waste of bandwidth, isn't it? Besides
you will get marginally better throughput from trapd if you define your traps,
though that may be hard to measure depending on how many time this occurs.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
"Qureshi, Fawad"
<Fawad.Qureshi@ssa.gov>
Sent
by: owner-nv-l@lists.us.ibm.com
03/23/2004 11:09 AM
|
To
|
"'nv-l@lists.us.ibm.com'"
<nv-l@lists.us.ibm.com>
|
cc
|
|
Subject
|
[nv-l] unknown format suppression
|
|
NV 7.1.3
Anyway
to suppress "trap found with no known format in trapd.conf" traps
from being displayed in events window without having to load the trap
definitions into Netview?
Cheers
Fawad
Qureshi