You may want to take a good look at Michael Siebold's response on how to avoid
your problem all together, but meanwhile I will answer your questions about
rulesets and TEC.
The RESOLVE mechanism is unique to NetView. The way it works is that a special
flag is added to the event which nvevents (the event window process) reads when
the event arrives. Then nvevents removes all matching events from the event
display. TEC has no such code, so a RESOLVE will not remove an event from the
TEC console. You must code TEC rules in TEC to do that. The only decision you
can make in NetView with regard to TEC is to send or not to send the event, and
that is t. And you can alter the variable content using the facilities in
trapd.conf, of course. But you cannot make TEC drop an event from his console
unless you make modifications to TEC.
You could reverse the logic in sampcorrIuId.rs and use Reset-on-Match and
Forward rather than Pass-on-Match and Resolve to acomplish the same thing. The
Reset would send along only those events which did not get a matching Interface
Up in the time allowed.
An no, you cannot "cascade" rulesets. You have to combine them into one large
ruleset when it comes to TEC. One technique that you could do however, is to
intercept traps from NetView or other sources wit one ruleset, and kick off a
script to send a new trap, using snmptrap, which contains just what you want to
go to TEC, and then have your TEC ruleset forward just your special trap and
ignore the others.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
Foss Ray-xrf001 <Ray.Foss@motorola.com> on 08/31/2000 08:03:05 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: "'IBM NetView Discussion'" <nv-l@tkg.com>
cc: (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] Ruleset using RESOLVE and FORWARD
Forgive me if this is a FAQ, my ears are still wet when it comes to NV6K.
I'm running NetView 6.0 and forwarding OV_IF_Down and OV_IF_Up events to a
3.6.2 TEC based on a NetView ruleset. My question is:
Can I use the RESOLVE template, as in the sample (sampcorrIuId.rs) ruleset,
to suppress quick down/up indications that are not real outages? Here is
the pseudo-code for my desired results:
if you get a OV_IF_Down
Hold it for a while (3 minutes)
if you get a OV_IF_Up
if you have a OV_IF_Down in hold from the same IP
resolve this event
if the Hold timeout expires
forward the OV_IF_Down event
I also don't know if I can cascade rule sets. Any help if greatly
appreciated. Thanks.
--
~~~~~~~~
Ray Foss
_________________________________________
mailto:Ray.Foss@motorola.com
Office: 480-441-1093 Mobile: 602-721-4792
Pager: 800-759-8352 PIN: 1244994
FAX: 480-441-5455
Motorola, Inc.
Global Computing & Telecommunications
8111 East McDowell Road - AZ33-H1780
Scottsdale, Arizona 85257 USA
_________________________________________
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|