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 NCM: How does the device naming scheme work? Where are priorities set? Can the Fully Qualified Domain Name (FQDN) option be deleted from the device naming scheme? Is there a way we can we avoid it? (305020)

Last Updated: 5/29/2020Categories: How toTotal Views: 2432Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

What are the priorities for device naming in Smarts NCM?
Can the Fully Qualified Domain Name (FQDN) option be deleted from the device naming scheme?
Is there a way we can we avoid it?

FQDN cannot be deleted but can be avoided by using the Device Naming Scheme.

Use the Device Naming Scheme to determine how the device name is generated from one of these three names of the device. For example, if you prefer to use Alias for the device name, you select Alias as the highest priority by making sure Alias is shown in the top position of the Priority Order list (as shown in the following graphic).

When you select a device name (Alias, FQDN, or Hostname) you must determine the priority order you want Network Configuration Manager to use when naming the device. As displayed in the graphic, Alias is the first priority (default), then FQDN is the second priority, with Hostname being the last priority you want Network Configuration Manager  to use when naming the device.

For example :

If a device has the following names; Hostname (AA) and FQDN (BB), using the default priority order, you would still use the default priority. Network Configuration Manager uses the designated priority (Alias, FQDN and then Hostname) to name the device. Not finding Alias as a name for the device, Network Configuration Manager  would then go to the next priority order (FQDN) and use that as the device name. Subsequently, if neither Alias or FQDN is available as a device name, Network Configuration Manager uses Hostname as the device name.

The hostname is always available for every device in Network Configuration Manager. The device name will always be resolved, resulting in a device name for every device.

Once the order is determined, Network Configuration Manager attempts to assign the device name following the order you specified.

To Select a Device Name:
1. Go to System Admin --> Global --> Device Options --> Device Naming scheme

2. Select the naming scheme from the Priority Order list. Use the Up and Down arrows to move your naming scheme to the top of the list.

3. After making your selection, click Apply.

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 - NCM

Take Our Survey

Support Assistant