nv-l
[Top] [All Lists]

Re: Paging on unacknowledged alarms

To: nv-l@lists.tivoli.com
Subject: Re: Paging on unacknowledged alarms
From: Arthur Heinrichs <arthur_heinrichs@TRANSCANADA.COM>
Date: Thu, 9 Dec 1999 13:31:59 -0700
This is what I tried but the problem is there is no event generated for an
operator acknowledgment.  I do not think there are any traps or events
generated from any acknowledgment or unacknowledgment so I cannot correlate
them.  If you get acknowledgment events, what did you set to get them?

Steve Francis wrote:

> Sounds like a good case for a rule:
> something like: for all interface down events, go to a reset on match for
> 10 minutes node.
> INput 2 to reset on match is the acknowledge event, and make sure the
> right variable correlate (not just the node, but also the interface.)
> If the reset on match does not trigger (i.e. the 10 minutes expires before
> an ack event) then fire off the pager...
>
> Arthur Heinrichs wrote:
>
> > We have the Netview (version 5.1.2 for AIX) console monitored 7x24 but
> > every once in awhile, an alarm goes unacknowledged for extended
> > periods.  I would like to make a ruleset that if the operator does not
> > acknowledge an alarm, perhaps after 10 minutes, then have Netview
> > automatically send out a page and escalate the issue.  The problem I
> > have is that I do not know how to test whether or not a "RED" symbol
> > caused by a trap has been acknowledged.  Is there a way to do this?
> >
> > Thanks,
> > Art Heinrichs
> > TransCanada Pipelines


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

Archive operated by Skills 1st Ltd

See also: The NetView Web