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

Placing vSAN Witness in a cluster results in non-functional witness (59483)

Last Updated: 8/18/2023Categories: Best PracticesTotal Views: 3728Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

If a vSAN Witness Host is moved into a vSphere cluster within vCenter, this prevents it from functioning correctly as a witness for a vSAN cluster.

See witness3.demo.local in the image below:

Purpose

To clarify a common misunderstanding about vSAN Witness hosts (either physical or appliance)

Cause

Moving a witness appliance into a Cluster prevents it from properly acting as a vSAN Witness Host.  It is not supported to allow a vSAN Witness appliance to participate in a vSphere Cluster other than the vSAN cluster it is a part of for providing witness components.

Impact / Risks

Placing the witness host in this unsupported configuration (vSphere cluster membership) prevents it from functioning as a vSAN witness.  This could result in data unavailability or loss in the event that a physical node suffers a failure before the condition is corrected.

Resolution

To correct this situation, follow the action plan outlined below:

Deploy a new vSAN Witness Host with appropriate network configuration at a Datacenter level in vSphere.

Select Change Witness Host from the Fault Domains & Stretched Cluster menu under the vSAN Cluster's Config menu/tab

Add the new vSAN Witness Host as normal

If the vSAN Witness Host is added before the CLOMRepairDelay timer has expired, choose Repair Objects under the vSAN Health Check to rebuild the vSAN Witness Components.

Related Information

Understanding the vSAN Witness Host
Details and setup of the vSAN Witness Appliance

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

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:

VMware vSAN

Related Versions:

Take Our Survey

Support Assistant