You get to choose between doing that work at Netview, or doing that work at
TEC. TEC is perfectly capable of it, but your implementation of it has
overly-simplified route of doing dup detect on hostname alone. To do this
Netview, you would have one background rule (in ESE) intercepting the
event and generating a custom event with the fields that your TEC rules
and having your to-tec ruleset pass those events on through.
Or you could tell your tec guys to do the dup detect on host name plus the
first word in the 4th varibiable binding of the trap, for interface events.
need to map a slot for that. It contains the ip address of the interface in
To see what this looks like, you can add that ($4) to the display of the
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
<Treptow.Craig@prin To: "NetView List (E-mail)"
03/18/02 04:09 PM Subject: [nv-l] Unique
hostnames for sending
events to TEC
Hi. We are running Netview 6.0.2 on AIX 4.3.3 and send events to TEC to
Currently, the TEC is setup with a "duplicate detector", so multiple events
from the same host only page on the first event, and just increment a
counter for the others. This causes us issues because routers, for
instance, can send a lot of events about differently things (different
interfaces, Frame-Relay DLCI status changes for different sites, etc.).
So, I raised this as an issue with our internal TEC support team, and they
would like me to pursue concatenating onto the hostname, some other string
to make the hostname in TEC unique".
We would send:
It appears to me that "$A", in Netview is fixed and I cannot modify it in
Can anybody confirm this, or otherwise help me?
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
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)