Sounds like reset-on-match might do the trick.
Is something like this what you have in mind?
>From the initial node (purple pizza) which is et to BLOCK (these two events
are the only ones you want to consider in this ruleset) you have two trap
settings nodes, one for your server trap and one for the router trap,
whatever they are. Then the server trap trap setting is input 1 to a reset
and the router trap is input 2. Then if a router trap comes in during your
reset period (which you define) and it matches a server trap you already
have, then the server trap processing stops. Otherwise is continues to the
next node in your ruleset. In the reset-on-match you have to tell it how
to match the events, by origin or by some other trap variable. Make sure
you add this comparison or it won't work right. There is no processing
on the router trap at all, unless you add that for it.
Hope this helps
James Shanks
Tivoli (NetView for UNIX) L3 Support
Jan Green <greenjan@YAHOO.COM> on 05/12/99 11:03:10 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: Ruleset Suggestions
I am running Netview 5.1.1, Framework 3.6 on AIX 4.3.1
and am trying to suppress a server notification if a
network problem exists. Specifically, If a server and
a router trap come in, throw them both out and do not
process them through the ruleset.
Does anyone have any suggestions as to what node or
combination of nodes might work?
Thanks for any suggestions
Jan
_________________________________________________________
Do You Yahoo!?
Free instant messaging and more at http://messenger.yahoo.com
|