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

How to configure a witness appliance for use with a direct connect 2-node vSAN cluster (74827)

Last Updated: 7/29/2023Categories: How toTotal Views: 4294Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Direct connect 2-node vSAN cluster

Although all the hosts can ping the witness appliance and both hosts have correct unicast table entries, the witness will not join the cluster.

Purpose

The vSAN network is isolated between the host vSAN nodes. As a result, separate interfaces need to be tagged as witness traffic.

Cause

No interfaces are tagged for witness traffic.

Resolution

Before starting, verify the two vSAN nodes and witness are all on the same ESXi build version.

1. Decide whether you want to use the witnessPG or the management interface for vSAN traffic on the witness. Use an interface that can ping the management interfaces on both of the hosts.

2. Tag the interface for vSAN traffic only and do not tag it for anything else such as witness, vMotion, or management.

esxcli vsan network ip set -i vmkx -T=vsan

3. Tag the management interfaces on the hosts for witness traffic.

esxcli vsan network ip add -i vmkx -T=witness

4. Double-check the unicast table entries on both hosts.

esxcli vsan cluster unicastagent list

NOTE: you should only see two entries for the other two nodes. You will not see the local node entry.

If all of this is done correctly, the witness should join the cluster successfully.

Related Information

2 Node Direct Connect

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 ファイル サービスの構成を更新できない (78769)

KB
•
将延伸集群 vSAN 上的 vCenter Server 升级到版本 6.6 或更高版本后，vSAN 集群进行了分区 (79068)

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.x

Take Our Survey

Support Assistant