Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Usage Meter doesn't detect vSAN (76567)

Last Updated: 1/24/2021Categories: TroubleshootingTotal Views: 3474Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

vSAN is not detected as enabled and its usage is not included in the VMware vCloud Usage Meter monthly report.

Cause

The cause of this issue is the difference in cluster name in the vCenter Inventory and the Licensing Service.
For example: In the vCenter Server inventory, the cluster name is "Your New Cluster" but in the Licensing Service the cluster name is "domain-c1". Usage Meter does not correctly recognize the vSAN enabled clusters. As a result, vSAN is not detected as enabled and Usage Meter does not collect any usage data. The vSAN usage is not included in the Monthly report.
This behavior is observed when vSAN is programmatically added in the vCenter Server inventory, where it is registered in the licensing service with the default name. This default name for the cluster is moref("domain-c1"). This behavior is unique to scripted vSAN enabled installations. For example: VxRAIL.

Resolution

No resolution is available at this time. See the Workaround section.

Workaround

To work around this issue, you need to rename the cluster, remove, re-add, and re-synchronize the vCenter Server to the Usage Meter inventory.
To apply the workaround:

Login to the vSphere Web Client

Locate the affected vSAN cluster from the object inventory and rename it

Log in to the Usage Meter web-portal

Delete the vCenter Server which is managing the renamed cluster

Tick the "Show Inactive" box beside the vCenter product list

Activate the vCenter Server again

Synchronize the vCenter Server inventory

Trigger a data collection

Generate a Cluster History report

Confirm that vSAN cluster information is now recorded

Result: The vSAN is listed in the Monthly Report, as well as the Cluster Report.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

VMware vCloud Usage Meter

Related Versions:

VMware vCloud Usage Meter 3.6.x

Take Our Survey

Support Assistant