Herman.E.Caballero AT Lowes DOT com writes:
>
> We are using Netview 7.1.2 on AIX.  We are also running TEC 3.8.  My
> issue is that I want to reduce the amount of traps/traffic/events
> being sent to TEC, and would like to filter some of these on the
> Netview box.  For example I have certain devices that I don't want
> to manage or monitor ports for, or specific address that I don't
> care to monitor.   I was pointed by support to a Redbook "Examples
> of Using Netview on AIX version 4". 
> 
> Has anyone else encountered this? and do have a method, script, etc
> to resolve this?

First, how are all your traps getting to TEC?  Are you running a
ruleset that is activated in teh TEC adapter and is Forwarding every
event that comes in?  

Or is every defined trap checked to send a TEC event? 


The usual approach is either deciding whether to send the event to TEC
on a trap by trap basis in the trap configuration panel (we do this,
and use a Command For Automatic Action to run a script.  The script
populates some items that are specific to our TEC environment, and
ultimately calls a postemsg command to send the TEC event).

Or, you can go with using rulesets, and just don't activate a ruleset
in the TEC adapter that Forwards everthing.   

A combination of two is what is typically done.  Send events directly
from the trap configuration panel for traps that don't need
correlation, and use a ruleset for the stuff that you need to do
event-to-event correlation on.


-- 
Todd H.
http://www.toddh.net/

---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com
For additional commands, e-mail: nv-l-help AT lists.tivoli DOT com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)