Re: [nv-l] default NetView TEC rules
I'm currently working with a big customer
and we are trying to use the default ruleset right out of the box and do
ticketing from it. They do ticketing on anything from Netview (other than
the default class tec_its_base) that is still there after x minutes. They
have RFI enabled. They were generally pleased with the results. There was
one issue and that was with the Interface Unreachable event. For some reason,
in TEC 3.9, this event is an exception to the rule that the Node event
eats the Interface events. I did not understand that. Rather than modify
the rule, however, they just changed the filtering rule on Netview to not
send Interface Unreachable events to the TEC.
Because of a shortage of TEC programmer
resources, the only way this customer could get this implemented on schedule
was if the default rule did the job, and I am happy to report that it is
doing a decent job.
Leslie A. Clark
IBM Global Services On Demand - Network Mgmt
|James Shanks/Raleigh/[email protected]
Sent by: owner-nv-l AT lists.us.ibm DOT com
09/26/2005 05:41 PM
|nv-l AT lists.us.ibm DOT com
|[nv-l] default NetView TEC
I've been asked whether anyone has any comments he or she would luike to
make on the default NetView TEC rules in 7.1.4.
Are they useful or not? If you wrote your own did you use them as
sample? Or did they just get in the way?
Anyone care to comment?
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group