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

vSAN Health Service - Hyperconverged cluster configuration compliance - vDS compliance check for hyperconverged cluster configuration (58897)

Last Updated: 2/9/2024Categories: InformationalTotal Views: 13365Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Details

This article explains the vDS compliance check for hyperconverged cluster configuration check in the vSAN Health Service and provides details on why it might report an error.

When configuring a vSAN cluster via Quickstart all changes need to go through Quickstart, otherwise, if any manual changes are made to the cluster outside of Quickstart the hyperconverged warnings will be triggered in vSAN Skyline Health.

The hyperconverged warnings are mainly cosmetic and the cluster will still function with these warnings triggered.

testID: com.vmware.vsan.health.test.dvshciconfig

Solution

Q: What does it mean when it is in an error state, and how to address it?

A: This health check will validate the state of the configured distributed virtual switch and the distributed port groups in cluster setup via QuickStart.

Is VDS alive - if it shows 'Not compliant', it means the vDS is no longer valid per Quickstart as manual changes have been made to the vDS outside of Quickstart or the vDS has been removed. In the health check recommendation, you will find more information about the invalid vDS, such as the vDS name. Navigate to the 'Network' configuration view, and check the vDS status. Recover the vDS to the settings as configured with Quickstart if possible, otherwise, the user has to recreate the cluster with Quickstart in order for the warning to clear.

Distributed port groups - The port groups configured for the vSAN network are not valid or missing from the vDS. Navigate to the 'Network' configuration view and check the distributed port groups under the configured vDS. If the distributed port groups have been removed or changed in any way, the user has to reconfigure the cluster network settings back to what they were when configured with Quickstart.

Alternatively, you can use the Manual method for creating your vSAN cluster as this will provide more control over the configuration of your vSAN cluster.

Related Information

Use Quickstart to Configure a vSAN Cluster
Using Quickstart to Configure and Expand a vSAN Cluster

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)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
vSAN -- vSAN Healthcheck -- Host compliance check for hyperconverged Cluster configuration (58896) (58896)

KB
•
Downloading and Installing the standalone VMware Remote Console (VMRC) in vSphere (2091284)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 6.7.x

Take Our Survey

Support Assistant