How do I force USM to use only shortnames when doing discovery?
search cancel

How do I force USM to use only shortnames when doing discovery?


Article ID: 34611


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


It is often possible, though not always simple, to control the display of USM hostnames through a careful configuration of the robots, probes,  QoS profiles, and so forth in the environment;  however, certain probes and types of discovery will nearly always return the FQDN no matter what configuration changes are attempted.

Therefore, it is often desirable to force the discovery_server to use the shortname when populating the discovery tables, so that all systems will appear in a consistent manner in the USM portlet.

(Note that the reverse is generally not possible - we cannot "force" discovery_server to always use the FQDN.  This is because using the FQDN when one has been discovered is the default behavior; therefore, if a machine is not showing up with FQDN it generally means we were unable to discover the FQDN in the first place.)

In order to force discovery_server to truncate all FQDN's into shortnames/hostnames, you must use a LUA script which applies the desired changes to the incoming discovery information; such a script has been attached to this article.

To implement this script you will need to do the following:

1. deactivate the discovery_server
2. Place the script (called override_eval_name.lua) into the folder <Nimsoft root>\probes\service\discovery_server\scripts on your primary hub.
3. delete the rows from CM_COMPUTER_SYSTEM which correspond to machines that are currently displayed using FQDN.
4. activate discovery_server and wait for the systems to be re-discovered.   When re-discovered they will be populated into CM_COMPUTER_SYSTEM with the shortname.

NOTE: This applies to discovery 7.0 and later only.

keywords: force forcing discovery discovery_server configure short shortname long longname FQDN LUA script



Release: CNMSPP99000-7.6-Unified Infrastructure Mgmt-Server Pack-- On Prem





Additional Information

If this is as a result of migration deleting the entries in the nas "name service" will be required to resolve this issue.

Attachments get_app