To: | nv-l@lists.tivoli.com |
---|---|
Subject: | Ruleset question |
From: | "jcbrown.net" <jcbrown@JCBROWN.NET> |
Date: | Mon, 2 Nov 1998 17:19:57 -0800 |
In-reply-to: | <862566B0.0068F007.00@MTA-Austin2.tivoli.com> |
Reply-to: | jcbrown@pobox.com |
Sender: | Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU> |
There are umpteen million traps a Bay router will send the NMS. We can control what severity of event it sends on the router side... That limits the traps we want to see to about 1500 that shouldn't occur that often. I have a ruleset that blocks traps by default and then only allows specified traps through. This cuts down on the number of useless traps going to our event window. Is there a way that I can punch a hole in my ruleset by enterprise and ignore the specific ID. I know that I could turn around a query the device when a trap comes in and say if it is a router pass the event, but that is way too much overhead everytime a trap comes in. Any suggestions? Thanks, Cindy Brown |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: mib2trap and SNMPV2 (was Re: Problem with nvaddtrapdconf), James_Shanks |
---|---|
Next by Date: | Re: Cleaning up after seed file revisions - warning, Leslie Clark |
Previous by Thread: | Re: mib2trap and SNMPV2 (was Re: Problem with nvaddtrapdconf), James_Shanks |
Next by Thread: | Re: Ruleset question, James_Shanks |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web