Because you said "snmptrap" and not "nvsnmptrap" I assume you have a
NetView for UNIX environment.
trapd on UNIX resolves hostname using the OS routines gethostbyaddr(),
which means that it is up to the OS to tell him the name.
You didn't mention whether both NetViews use DNS, but I would try nslookup
on the IP address, not the name, since that is how it gets resolved, by the
"reverse" of the hostname. There is also an executable in /usr/OV/bin,
nvgethost, which uses the same gethostbyname() and gethostbyname() routines
that trapd (and the other NetView daemons use) which can be used for the
same purpose, to check name resolution. You should get the same result
as you do with
nvgethost <IP address>
If you don't, then you have a badly configured DNS or /etc/hosts file
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
Sent by: firstname.lastname@example.org
[nv-l] snmptrap --> in NV different
12/14/2005 08:33 hostnames
Please respond to
We have parallel environments.
In one environment, when receiving a trap, generated by snmptrap in that
environment, the fully qualif. hostname is shown in the trap info. In the
other environment we see the short hostname. As I want to standardise both
environments, I wonder where the diff. is coming from.
I already checked the hosts file and the "hostname" command on the sending
servers is giving in both cases the short hostname.
Somebody an idea ?
Vriendelijke Groeten, Cordialement, Kind Regards,