I have to pursue the Netview solution of modifying the hostname first, because
of political reasons. I agree that a better solution would be to modify the
"dup detect" to key on more things that I could populate with what I want.
That said, my first experiment of adding an interface name to the host name
resulted in:
snmptrap: Invalid agent-addr "rbglasvegas1nv-eth0-Serial1.net.principal.com".
I think this is because Netview knows this device as
"rbglasvegas1nv-eth0.net.principal.com". I've seen this in the past when I've
tried to alter the hostname.
What I actually execute looks like:
/usr/OV/bin/snmptrap nmsrvr.principal.com .1.3.6.1.4.1.0 \
rbglasvegas1nv-eth0-Serial1.net.principal.com 6 1007 1 \
.1.3.6.1.4.1.2.6.3.1.1.2.0 OctetString \
rbglasvegas1nv-eth0.net.principal.com \
.1.3.6.1.4.1.2.6.3.1.1.3.0 OctetString Serial1 \
.1.3.6.1.4.1.2.6.3.1.1.4.0 OctetString "Interface down [down]."
This works just fine if the hostname is left as
"rbglasvegas1nv-eth0.net.principal.com".
I don't see how I can generate my own trap when it behaves this way, so I'd
appreciate somebody telling me what I'm missing.
Thanks.
Craig
-----Original Message-----
From: Leslie Clark [mailto:lclark@us.ibm.com]
Sent: Monday, March 18, 2002 4:24 PM
To: nv-l@lists.tivoli.com
Subject: Re: [nv-l] Unique hostnames for sending events to TEC
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
taken the
overly-simplified route of doing dup detect on hostname alone. To do this
in
Netview, you would have one background rule (in ESE) intercepting the
event and generating a custom event with the fields that your TEC rules
like,
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.
You will
need to map a slot for that. It contains the ip address of the interface in
question.
To see what this looks like, you can add that ($4) to the display of the
event
in trapd.conf.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Treptow, Craig"
<Treptow.Craig@prin To: "NetView List (E-mail)"
cipal.com> <nv-l@lists.tivoli.com>
cc:
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
page.
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".
For example:
Instead of:
hostname=[router1] interface=[eth0]
hostname=[router1] interface=[eth1]
We would send:
hostname=[router1-eth0] interface=[eth0]
hostname=[router1-eth1] interface=[eth1]
It appears to me that "$A", in Netview is fixed and I cannot modify it in
this way.
Can anybody confirm this, or otherwise help me?
Thanks.
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.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)
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.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)
|