CM Usertracking: Shortname instead of FQDN in End Hosts Table

Unanswered Question
Mar 5th, 2009
User Badges:

Hi


I'm using LMS 2.6, CM 4.0.12 with CS 3.06.


Although the acquisition settings are set to use DNS to resolve hostnames, I've a lot of endhosts (mostly UNIX) with shortnames in the end hosts table. I don't really understand how the UT Acquisition resolves these hostnames so it's quiet difficult to troubleshoot :(


thanks for your help, greets chris


PS: please let me now if you need more information



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Thu, 03/05/2009 - 13:59
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

It uses Java and the server's system resolver to resolve the IP address to a hostname. The best way to check this mapping is to use the NMSROOT/bin/resolver.pl utility. Take one of the end host IP addresses, and run:


NMSROOT/bin/perl NMSROOT/bin/resolver.pl IP


That will tell you what the system resolver thinks of that IP. It could be that you need to fix your DNS server to return the FQDN (or fix entries in the server's local hosts file).


For example, on a Solaris system, the typical hosts resolution order is files,dns. So, if there is an entry in the /etc/hosts file, then that will be used by UT. If that entry only has the hostname, then only the hostname will be used.

ch.jauslin Thu, 03/19/2009 - 01:21
User Badges:

The dns resolver gave me the shortname, although there was no entry in the servers's local host file.


The problem was, that NIS replied to these requests with shortnames. To solve my problem I had to change the squence of resolving hostnames in /etc/nsswitch.conf as follows


hosts: files dns nis


Thanks a lot


greets


chris

Actions

This Discussion