nv-l
[Top] [All Lists]

Re: Sending Interface Down & Interface up pages and correlation

To: nv-l@lists.tivoli.com
Subject: Re: Sending Interface Down & Interface up pages and correlation
From: Steve Francis <steve.francis@COMMSERV.UCSB.EDU>
Date: Mon, 17 Jan 2000 09:41:09 -0800
Patrick McNeil wrote:

> The part I don't have working is the opposite, sending the Interface Up
> messages only when an Interface down message has been sent.
> Case 1 works fine, but Case 2 does not if I don't send an Interface down
> page, I don't want to send an Interface up page.  What I believe is going on
> is that the Rest on Match (B) does not start looking for an Interface down
> until after the Interface up is received (i.e. it does not hold the
> interface down in Slot 2 until Slot 1 is active).

Your rule logic is slightly skewed.
Change the reset on match (B) to a pass on match (same attributes.)
Make Slot 1 input of the pass on match be the output of the reset on match (A),
and slot 2 be the I-Up trap. Make the Pass on match hold time be 999 hours, or
something really big.

This will do what you want: in (kind of) English:
If there is an interface down trap, that has not been reset by an interface up,
then start waiting for the corresponding interface up, and when that arrives,
send the page.


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

Archive operated by Skills 1st Ltd

See also: The NetView Web