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 Host Maintenance Mode is in sync with vSAN Node Decommission State (51464)

Last Updated: 11/8/2023Categories: InformationalTotal Views: 16181Language:
Chinese (Simplified)JapaneseEnglish

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Purpose

This article explains the health check- whether the host's maintenance mode is in sync with vSAN node decommission state.

Resolution

What does the check - Host Maintenance Mode is in sync with vSAN Node Decommission State do?

Once the vSAN host is in vSAN decommission state, it doesn't accept any new object creation, and all components on the host will be absent until it is back. When the host in the vSAN cluster is in maintenance mode, it is expected that this host is in vSAN decommission state. When the host exits maintenance mode, the host should not be in vSAN decommission state. This health check verifies the 2 states are in sync.

What does it mean when it is in an error state?

If a host is in maintenance mode using any of the vSAN options but is not in vSAN decommission state, or a host exits maintenance mode but is still in vSAN decommission state, the check triggers a warning message.

What action can be performed to resolve this?

If a host is decommissioned but the host is not in maintenance mode, do the following:

Identify the relevant host as per the Skyline Health alarm. Make sure to use the host where "vSAN Node in Decommission State" is "Yes".

Place the same host into maintenance mode with No Action by doing the following:
Right-click the host > select Maintenance Mode > No Action

Then exit the maintenance mode right after.

This will reset the vSAN decommission status and make it consistent with the vSphere maintenance mode.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

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)

Results 1-2 of 2

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

Take Our Survey

Support Assistant