Configuring automatic name resolution
The TM_USEAUTONAME option in the name-resolver.conf file enables you to configure the Name Resolution
probe to automatically resolve system names by using the naming sources in the order that you specify.
- “Configuring automatic name resolution” section in Chapter 3, Discovery, in the provides more information on naming-source sequence used by the Name Resolution probe to resolve system names.
- “Configuring automatic name resolution”section in Chapter 3, Discovery, in the provides more information on AutoNameOrder naming sources.To configure automatic name resolution:
- Go to the BASEDIR/smarts/bin directory in theIP Managerinstallation area and type the following command to open the name-resolver.conf file:sm_edit conf/discovery/name-resolver.conf
- Find theNameFormatsection of the file:#NameFormat = "TM_USESEEDNAME" NameFormat = "TM_USEAUTONAME"
- Ensure that theNameFormat = “TM_USEAUTONAME”option is the only one that isnotcommented out.
- Find theAutoNameOrdersection of the file:AutoNameOrder 0 TM_USELOOPBACK AutoNameOrder 1 TM_USESYSNAME AutoNameOrder 2 TM_USENONPRIVATEIP AutoNameOrder 3 TM_USEPRIVATEIP AutoNameOrder 4 TM_USEAGENTADDRESS
- Change theAutoNameOrdernumbers (0 through 4) to the order that you prefer. The resolution process is performed in ascending order, starting withAutoNameOrder 0. AutoNameOrder naming sources describes theAutoNameOrdernaming sources.
Naming source | Description |
|---|---|
TM_USELOOPBACK | Resolve loopback IP address: If a loopback
interface IP address can be resolved to a name, that name will be used to name the system. By default, the default loopback interface type number is 24, which represents the “software loopback” interface type. For a discovered system that
has multiple loopback addresses, the Name Resolution probe tries to resolve the lowest loopback address first. If that resolution fails, the Name Resolution probe tries to resolve each of the remaining loopback addresses. |
TM_USESYSNAME | Resolve MIB-II sysName: If the sysName can be resolved to at least one IP address,
and at least one of the resolved IP addresses resolves back to the sysName, the sysName will be used to name the system. |
TM_USENONPRIVATEIP | Resolve non-private IP address: If at least one of the IP addresses is not a private IP address, the non-private IP address will be used to resolve the name. Once a name is
resolved, the name will be used to name the system. |
TM_USEPRIVATEIP | Resolve
private IP address: If at least one of the IP addresses is a private IP address, the private IP address will be used to resolve the name. Once a name is resolved, the name will be used to name the system. By default, the private IPv4 address
pattern is 10.*|192.168.*|172.<16-31>.*, which is defined as follows:
|
TM_USEAGENTADDRESS | Resolve SNMP agent address: If an SNMP agent address can be resolved to a name, that name will be used to name the system. |
- Save and close the file.The modified version of the name-resolver.conf file is saved to the BASEDIR/smarts/local/conf/discovery directory.
- Type the following command from BASEDIR/smarts/bin to implement your changes:sm_tpmgr -s<IP Managerinstance name>-b <brokerName:port>--load-conf=name-resolver.confsm_tpmgr -s INCHARGE-AM -b localhost:426 --load-conf=name-resolver.conf
- Optional: Configure exceptions to automatic name resolution by using a seed file, as described in“Configuring exceptions to automatic name resolution” on page 154.If the resolution process is unsuccessful for all naming sources that are defined in the name-resolver.conf file, a final procedure uses a public IP address, a private IP address, or the SNMP agent address for the system name.