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

Network partition may occur when adding a vSAN 6.5 host to a vSAN 6.6 cluster with on-disk format v3 disks (54925)

Last Updated: 1/9/2021Categories: TroubleshootingTotal Views: 11377Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

vSAN cluster may become partitioned in the following situation:

vCenter Server resides on the vSAN datastore.

The vSAN cluster is configured as vSAN 6.6 with on-disk format v3 disks.

Unicast mode is enabled on the vSAN cluster.

An ESXi host with vSAN 6.5 installed (which doesn't support unicast mode) is added to the vSAN cluster.

Cause

This is expected behavior (limitation).When non-supported unicast hosts are added to vSAN cluster, unicast mode may change to multicast mode in some or all nodes in the vSAN cluster.
Under certain circumstances, this issue can occur:

Add ESXi hosts to vSAN cluster.

vCenter Server sequentially pushed changed mode to each host.

ESXi host is temporarily partitioned for mixed mode (unicast + multicast).

vCenter Server may get into an unknown state or its related vSAN objects may become inaccessible due to the cluster partition.

vCenter Server can hang/become inaccessible due to this and it cannot push multicast state to other hosts.

vSAN cluster will be partitioned for mix mode (unicast + multicast).

Impact / Risks

If this issue occurs, some vSAN objects may become inaccessible due to loss of quorum or availability of data-replicas.

Resolution

You can avoid this issue by planning following action.

Migrate the vCenter that manages the cluster to a non-vSAN datastore so that a cluster partition does not cause it to become unavailable.

Update ESXi hosts to vSAN 6.6 or later (which supports unicast) before adding them to the vSAN cluster.

Workaround

If this issue occurs, you can use esxcli vsan cluster unicastagent remove command to remove unicast entries referencing the node that was added to the cluster.

esxcli vsan cluster unicastagent remove –a <IP> -u <LOCAL NODE UUID>

You can check unicastagent list to use esxcli vsan cluster unicastagent list command.

Example:

This is 4 node vsan cluster and added another hosts  Node Uuid is 5aa12a01-eeee-eeee-eeee-00109b37ee4a

[root@esx-01:~]esxcli vsan cluster unicastagent list

NodeUuid                              IsWitness  Supports Unicast  IP Address    Port   Iface Name
--------------------------------------------------------------------------------------------------
596f1214-bbbb-bbbb-bbbb-00109b165b8e          0  true              192.168.XXX.2  12321
596f115a-cccc-cccc-cccc-00109b16566e          0  true              192.168.XXX.3  12321
596f1189-dddd-dddd-dddd-00109b165b6e          0  true              192.168.XXX.4  12321
5aa12a01-eeee-eeee-eeee-00109b37ee4a          0  false             192.168.XXX.5  12321   #### added host

[root@esx-02:~]esxcli vsan cluster unicastagent list
NodeUuid                              IsWitness  Supports Unicast  IP Address    Port   Iface Name
--------------------------------------------------------------------------------------------------
596f1189-dddd-dddd-dddd-00109b165b6e          0  true              192.168.XXX.4  12321
596f115a-cccc-cccc-cccc-00109b16566e          0  true              192.168.XXX.3  12321
591b8c87-aaaa-aaaa-aaaa-00109b165b2e          0  true              192.168.XXX.1  12321

[root@esx-03:~]esxcli vsan cluster unicastagent list
NodeUuid                              IsWitness  Supports Unicast  IP Address    Port   Iface Name
--------------------------------------------------------------------------------------------------
591b8c87-aaaa-aaaa-aaaa-00109b165b2e          0  true              192.168.XXX.1  12321
596f1214-bbbb-bbbb-bbbb-00109b165b8e          0  true              192.168.XXX.2  12321
596f1189-dddd-dddd-dddd-00109b165b6e          0  true              192.168.XXX.4  12321

[root@esx-04:~]esxcli vsan cluster unicastagent list
NodeUuid                              IsWitness  Supports Unicast  IP Address    Port   Iface Name
--------------------------------------------------------------------------------------------------
596f115a-cccc-cccc-cccc-00109b16566e          0  true              192.168.XXX.3  12321
596f1214-bbbb-bbbb-bbbb-00109b165b8e          0  true              192.168.XXX.2  12321
591b8c87-aaaa-aaaa-aaaa-00109b165b2e          0  true              192.168.XXX.1  12321

Execute following command

esxcli vsan cluster unicastagent remove –a 192.168.XXX.5 -u 5aa12a01-eeee-eeee-eeee-00109b37ee4a

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

Take Our Survey

Support Assistant