nv-l
[Top] [All Lists]

Re: Event Correlation

To: nv-l@lists.tivoli.com
Subject: Re: Event Correlation
From: James_Shanks@tivoli.com
Date: Tue, 4 Jul 2000 14:38:05 -0400

I sense that you don't quite understand what event correlation is.  You don't so
much turn it on as design for yourself what should happen in your particular
system and code that into a ruleset.

Event Correlation is user-programmable.  You decide what should happen and you
program that.  But the example you have given is not specific enough.  When you
say, for example, that event correlation should ignore alarms (you mean traps I
take it) from B, C, D, you can do this in a ruleset and suppress these from the
event display (using the Block or Resolve Function) and in that same ruleset you
can "take action on alarms  from router A".  But what action do you want to have
happen? You would set up an Action node to fire off a script or program of your
own choosing  ( or perhaps your won making)  to take this action, whatever it
is.   Do you see how it is all up to you to decide what  should happen when
these traps arrive?  Otherwise the default action is just to display them in the
event window or log them in trapd.log.

Does this help?

James Shanks
Team Leader, Level 3 Support
 Tivoli NetView for UNIX and NT



Salinas Sangines Guillermo <gsalinas@scanda.com.mx> on 07/04/2000 11:21:21 AM

Please respond to IBM NetView Discussion <nv-l@tkg.com>

To:   "'NetView'" <NV-L@UCSBVM.ucsb.edu>
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  [NV-L] Event Correlation




Hi, I'm configuring the event correlation feature on NetView 6.0 for Unix
(AIX).
As I understand, one of the primary function of an event correlator, is to
filter multiple alarms.
An example is: if nodes B, C and D, are switches connected to a router A,
and router A goes down. The event correlation functionality would filter
alarms from nodes B, C and D, and only take actions on the alarm from node
A.

Well, does someone knows how to configure this on NetView 6.0 ?
I've seen the RuleSet Editor, with the default rulesets (NodeDown/NodeUp,
InterfaceDown/InterfaceUp).
But it doesn't looks like this rules resolve the example I've posted.

Regards

Guillermo Salinas Sangin
és
Omniscope - México DF
tel. 5422-2700 ext.6033
mailto:gsalinas@scanda.com.mx

_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l






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

Archive operated by Skills 1st Ltd

See also: The NetView Web