We were answering at same time :)
The 8-series resolves each IP of a discovered device and accociate the DNS name of the IP to the IP. Since a NetworkDevice can have several IPs (and several DNS entries), using the DNS name as “Name” for the device will simply be wrong.
Laura -> I’m not agree at all. ADDM discovers by IP, and search the best way/route to access this IP (for example, if a server have 2 network interfaces, and try to access the 2 IPs, ADDM shows an error at one of them and says that the device is accessed by another IP).
Local FQDN contains the local “hostname” output plus the domain. This search is local, as far as I know, ADDM is not asking the configured DNS.
If the DNS resolution does not work, have you verified fw are opened between ADDM and the DNS? Are the IPs registered in DNS?
Laura -> all is open and ADDM server resolves by command line too. We have configured /etc/resolv.conf too.
I think that ADDM DNS function is not in use, because if I see the discovery scripts for servers, I can see that “name” is being mapped with the result of the command “hostname” $options.
The SysName is a more accurate attribute to use in this case.
Laura -> The customer has set his switches with an internal name like “example”, but the correct name is at DNS.
Is the customer facing the problem in ADDM or in CMDB?
Laura -> At ADDM. We are not integrating ADDM with CMDB by now, but we will do it in a month (they have 7.x integrated with CMDB).