PDF(3.8 KB) View with Adobe Reader on a variety of devices
ePub(67.3 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(67.3 KB) View on Kindle device or Kindle app on multiple devices
Updated:March 22, 2016
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
For Cisco Prime Infrastructure to process client host name values successfully, DNS queries need to be returned in less than 2 seconds. Under some circumstances, even with faster DNS responses, the Prime Infrastructure server may flag the DNS server as down and will not query it for 30 minutes, causing a "no client hostname" value to be reported on some wired and wireless clients.
Fixing the Missing Client Hostnames
Users experiencing this problem can work around it using either of the following methods:
1. Increase the Prime Infrastructure default setting for DNS timeouts. You can do this by changing the value (the unit must be in seconds) for the attribute HostName.Threshold in the Prime Infrastructure properties file /opt/CSCOlumos/conf/rfm/classes/com/cisco/server/resources/ClientParameters.properties. Once you have made this change, you will need to restart the Prime Infrastructure server in order for the change to be applied (for details, see Restarting Prime Infrastructure).
2. Configure Prime Infrastructure to enable DNS hostname lookup and specifying a DNS server that has a very fast response time. For more details, see Enabling DNS Hostname Lookup.