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

Failure to promote CMMDs version resulting in vSAN cluster to become partitioned during upgrade (76841)

Last Updated: 10/14/2021Categories: TroubleshootingTotal Views: 9754Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

During an upgrade of a vSAN cluster one or more nodes become partitioned from the rest of the cluster, forming one or more new cluster partitions.

No indication of network communication issues (e.g. vmkping between nodes on the vSAN network succeeds).

In vmkernel.log for the host of the new cluster partition(s) messages similar to the following are observed:

WARNING: CMMDS: CMMDSPromoteFormatVersion:423: Failed to promote the node to a format version X beyond its software version Y
Where X is the version promoting to and Y is the version promoting from

This issue can be observed when upgrading a vSAN cluster to any version higher than the version upgrading from where the on-disk format version would require an upgrade as well. For example:
6.5U3 to 6.7U2
6.7U2 to 7.0U2
6.5U3 to 7.0U1

Cause

Recreating or adding Disk-Groups to the cluster which are using an on-disk format version higher than the rest of the cluster causes CMMDS version on these nodes to be updated, these are then non-compatible with the nodes that have not been upgraded yet (as they are unable to use later versions of CMMDS). This can occur when recreation of a higher on-disk format Disk-Group fails.

Removing the higher version Disk-Groups will not resolve the issue as this will not revert the CMMDS version in use.

Setting virsto version to legacy format will not resolve the issue as this will not revert the CMMDS version in use.

Resolution

There is no resolution for this issue and thus this issue should be avoided or workarounds implemented.

This issue can be avoided by not adding/creating/re-creating Disk-Groups of a higher format until all hosts have been upgraded to the same ESXi build - if Disk-Groups need to be recreated mid-upgrade then temporarily setting virsto to use the highest version that all hosts are compatible with is a valid option, these changes should be reverted once all hosts have been upgraded:

How to format vSAN Disk Groups with a legacy format version (2146221)
Understanding vSAN on-disk format versions and compatibility (2145267)

Workaround

If you've already encountered this issue, you have two options to work around it:

Either move forward and update the remaining nodes in the cluster - note that this may cause further data inaccessibility as depending on how the cluster partitioned, the updated nodes may be joining the cluster partition that does not have the majority of the data accessible and following update it will no longer be able to communicate with the lower version nodes that it was clustered with prior to updating.

OR

Roll-back/re-install the previous version of ESXi on the nodes with higher version of CMMDS - before considering rollback option, validate that there is actually the lower build version available by checking the contents of /altbootbank/boot.cfg .

If this option is chosen then the Disk-Group created on a higher version will need to be removed prior to rollback/re-install so as to not cause possible further issues.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vSphere 6.5 およびその互換性のある VMware 製品の更新手順 (2147289)

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

VMware vSAN 7.0.x

VMware vSAN 6.7.x

Take Our Survey

Support Assistant