How to change the naming methods used by eHealth discovery.

Document ID : KB000047619
Last Modified Date : 14/02/2018
Show Technical Document Details


By default, eHealth discovery will use sysname to name elements during discovery.

Here are the steps to change that.

You have 3 options.

sysname = this is the default behavior and is taken from the MIB.

DNS = use standard name resolution on the eHealth poller that is running the discovery

file = use a flat file defined and populated by the user.


Note : to see the parameter symbols, hit show at the top of the policy section.





There is a discovery policy parameter called NH_USE_NAME_SRVC that controls how eHealth discovery for that policy will name elements during discovery.

The default value is no which = use sysname as returned from the mib.

Description of the variable from the policy itself:

Use DNS, a custom value from a file, or sysName when naming elements. Values are "DNS", "sysName", "file_name", or "No". When you set this value to DNS or sysname, you can specify a regular expression in NH_NAME_SRVC_PAT to truncate part of an element name exceeds the max name length.

(note: “file_name” is a typo, use “file” as shown in the steps below)


EHealth 6.x



1.    If you leave this as default (no), discovery will use sysname to name elements.

2.    If you change it to DNS, discovery will use standard name resolution on the eHealth server to name elements.

          Standard name resolution = local cache, hosts file, wins, dns

3.    If you change it to file, discovery will use the values in the flat file to name elements.

Please note: you have to edit a second parameter, NH_HOST_FILE to point to a flat file on the local system. The format of the flat file is the same as a host file, e.g. address name

4.    Be aware that if you put a value that is not recognized, it will be seen as a Boolean yes, and the behavior will revert to DNS.


Additional Information:

Please see the eHealth administration guide:

please see the parameters section of a discovery policy in the OneClick console.