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 Witness appliance partitioned from stretch cluster (76828)

Last Updated: 4/11/2022Categories: TroubleshootingTotal Views: 8705Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Witness appliance experiences some type of failure or network partition and then will not re-join the cluster, even when disabling/re-enabling the cluster

Purpose

The purpose of this KB is to provide some proven troubleshooting steps during this scenario that do not involve re-deploying the entire witness appliance.

Impact / Risks

Before disabling the stretched cluster, always confirm that all other fault domains are up and accessible.

Resolution

To resolve this issue, verify that there are no actual communication issues between the data nodes and the witness appliance before proceeding. (See Testing VMkernel network connectivity with the vmkping command (1003728)  for more details on using vmkping)

To verify connectivity perform vmkping tests between the vsan vmks.

To test 1500 MTU, run the command: vmkping -I vmkX x.x.x.x -d -s 1472
To test 9000 MTU, run the command: vmkping -I vmkX x.x.x.x -d -s 8972

In addition, check the connectivity between the witness appliance and the data nodes via port 12321.

On the witness: tcpdump-uw -i vmkX (vmkx is the vmk port that is used for witness traffic)

If there is connectivity you will see incoming requests and responses over port 12321

Example:

On the data node: tcpdump-uw -i vmkX | grep <witness IP> (vmkX is the vmk for witness traffic)

If working correctly, you will see it reaching out over port 12321 and also the response.

Example:

If there is no connectivity over port 12321, get this resolved first. If there is connectivity proceed.

Once this is verified follow these steps:

1. Put the witness appliance in maintenance mode with Ensure Accessibility

2. Disable the stretched cluster in the GUI. Configure > VSAN > Fault Domains and Stretched Clusters

3. SSH Into the witness appliance and manually dismantle the disk group. (See How to manually remove and recreate a vSAN disk group using esxcli (2150567)  for details on this process)

esxcli vsan storage remove -u <VSAN Disk Group UUID>

4. Re-enable the stretched cluster and follow the Wizard and have it create new disks to house the witness components.

This should re-form the cluster successfully and allow the witness components to re-build on the newly created virtual disks. If this fails then you may need to re-deploy the witness appliance.

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

Related Versions:

VMware vSAN 7.0.x

VMware vSAN 6.7.x

VMware vSAN 6.6.x

VMware vSAN 6.5.x

Take Our Survey

Support Assistant