Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts IP: What is the order that we resolve names in Smarts IP? How do we update this order? (332348)

Last Updated: 12/17/2018Categories: TroubleshootingTotal Views: 4588Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

This KB article explains the order in which we find a name for a device.

Resolution

Smarts IP can attempt to resolve names with the following methods:

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:

Any IP address with the value of 10 in the first octet (10.*.*.*).

Any IP address with a value of 172 in the first octet and a value between 16 and 31 in the second octet (172.<16-31>.*.*).

Any IP address with a value of 192 in the first octet and a value of 168 in the second octet (192.168.*.*).

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.

The file called: name-resolver.conf located at : <BASEDIR>/smarts/conf/discovery/ contains the order in which we try these methods.

The default order is as follows:

1: First we try a loopback  to resolve to a name.
2: Then we move to the SNMP based  sysname.
3: Then we move to non privipaddress.
4: Then we move to private ip address.
5: Then we use the IP address.

Here's a example of a default list in the name-resolver.conf file:

AutoNameOrder 0 TM_USELOOPBACK
AutoNameOrder 1 TM_USESYSNAME
AutoNameOrder 2 TM_USENONPRIVATEIP
AutoNameOrder 3 TM_USEPRIVATEIP
AutoNameOrder 4 TM_USEAGENTADDRESS

To change the order use sm_edit:

1.) ./sm_edit conf/discovery/name-resolver.conf
2.) Change the AutoNameOrder numbers (0 through 4) to the order that you prefer.
3.) Save and close the file. The modified version of the name-resolver.conf file is saved to the BASEDIR/smarts/local/conf/discovery directory.
4.) Reload the file using the following command:
./sm_tpmgr -s <IP Manager instance name> -b <brokerName:port> --load-conf=name-resolver.conf
5.) During the next discovery or autodiscovery, name resolution will be updated.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant