I'm not certain that I understand what you are saying. I also don't
understand this term "edgeserver" that you are using. Is this another
NetView that you have forwarding traps to a central one, or what?
The origin name in an SNMP V1 trap is sent as an IP address, not as a
resolved octetstring. So if the "edgeserver" is one NetView forwarding
traps to the other, then name resolution at the "edgeserver" has nothing
to do with how the trap is displayed at the central sever. Each trapd is
going to have to do the very same reverse address lookup using
gethostbyaddr to resolve the name. So if your traps look fine in one but
not in the other, then they aren't using the same name resolution
methodology. Different name servers, perhaps? Or perhaps one also has
a host file that is overriding DNS?
Perhaps this information will help you clarify the problem.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group
cfrantse@csc.com
11/18/2002 05:59 AM
To: nv-l@lists.tivoli.com
cc:
Subject: [nv-l] [Update] DNS in a distributed environment
It seems that I had some DNS trouble at one of my edgeservers, which it's
fixed now.
So now I get some nice DNS names in the central event browser, but not for
all events.
All internal traps such as Node/Interface Down gets resolved at the
edgeserver before getting sent to the central server
but traps like cisco link traps, authentication failure does not get
resolved before getting sent to the central server.
Is it supposed to be like this?
Christian Frantsen
GIS/NES
CSC, Computer Sciences Corporation
Jonkoping, Sweden
---------------------------------------------------------------------
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)
|