I'd really make sure that only "important" events end up over on
TEC.  Make sure the filtering takes care of all "noise".

The reason for this is simple... a single NetView system can handle
10-20 times the events per second as a TEC.  If you end up with any
kind of event-storm (and the filtering doesn't cover it)... you'll
end up crashing the TEC (or rendering it useless).

Regards,

Gary Boyles


-----Original Message-----
From: Allen Mobasseri [mailto:amobasse AT YAHOO DOT COM]
Sent: Wednesday, May 05, 1999 10:05 AM
To: NV-L AT UCSBVM.UCSB DOT EDU
Subject: NetView/Tivoli Implementation


We are planning to install NetView and I would appriciate any input you
guys can give me regarding the follwoings.


 Our focus is on
event correlation and rule sets.  We are planning to have an
application support desk recieve trouble tickets from the nms system,
where
the GUI into the NMS system is Tivoli TEC console, and act upon them.

The current plan or desire by is to access the netview 5.1
maps via HTTP.

With this all stated, what issues do you see in the following setup ?


                                ***     Netview 5.1
TEC Console ****        CiscoWorks 2000
                                ***     Tivoli Application Monitor



What issues / limitations are there in the event correlation engine of
Netview.  We would like to  these events filtered as much as
possible.  Right now we are thinking the majority of the correlation
will
occur at the TEC console. Any issues here you know about.

Thanks in advance
Allen

amobasse AT yahoo DOT com




_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com