Guillermo,

The functionality you describe is implemented in Netview 6.0
as:
    1) event suppression or 
    2) RFI (router fault isolation)or 
    3) root cause analysis

I think all these terms refer to the same thing - not generating the alarms
and relaxing polling interval for the devices which are in "unreachable"
part of 
the network.

This feauture is not enabled in 6.0 by default, will be available in 6.0a
(by default)
and there is a script (contact your Tivoli rep.) to enable in NV6.0

Could someone explain the differences between 1 and 2 and 3 or 
are they the same thing (just a different name)?

Hope this helps,


Jack

-------------------------------------------------------------------
Jack Szewczyk                    |  email: jszewczyk AT westpac.com DOT au 
Network Systems Administrator    |     
Westpac Banking Corporation      +---------------------------------
Level 2, 72 Christie Street      |   phone: +61 2 9902 6497
St Leonards NSW 2065/AUSTRALIA   |   fax:   +61 2 9902 5111
-------------------------------------------------------------------


-----Original Message-----
From: Salinas Sangines Guillermo [mailto:gsalinas AT SCANDA.COM DOT MX]
Sent: Wednesday, 5 July 2000 5:11
To: 'NetView'
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 AT scanda.com DOT mx