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 Health Service - File Service - Infrastructure health (76677)

Last Updated: 2/24/2023Categories: InformationalTotal Views: 11069Language:
Chinese (Simplified)JapaneseEnglish

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Details

This article explains the File Service - Infrastructure health in the vSAN Health Service and provides details on why it might report an error.

Solution

What does  File Service - Infrastructure health check do?

It checks the file service infrastructure health state per ESXi host in the vSAN cluster.

The column 'vSAN File Service Node' checks if the vSAN file service node VM is in a powered on state.

The column 'VDFS Daemon' checks if VDFS daemon process is running or not.

The column 'Root File System Health' checks if the file service root file system is valid and is mounted correctly on the host.

The column "Workload Balance Health" checks whether file servers are well balanced in the cluster.

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

The column 'Description' will provide the detailed error message which can be referred to the following table.

Check Item

Error Message Type

vSAN File Service Node

Host in maintenance mode

File service VM not found on this host

File service VM not powered on this host

VDFS Daemon

VDFS daemon and sockrelay are not running

Sockrelay is not running

VDFS daemon is not running

Root File System Health

Root filesystem not present through CMMDS

Root filesystem not responsive

Workload Balance

File service is comparatively overloaded on this host.
Cannot fetch file service balance status
Load balance health check is not supported.

When the vSAN File Service is enabled, stateless containers are deployed to a max of eight ESXi hosts in vSAN 7.0. If there are nine hosts, only eight vSAN File Service nodes are deployed.

When a host is placed in maintenance mode, the vSAN File Service node is powered off. This can cause the Infrastructure Health check to trigger an error

Once the host enters maintenance mode, an informational message will be shown.

After a period of time, assuming the ESXi host isn't rebooted or shutdown, the powered off vSAN File Service node will be deleted. If another host is available, a new vSAN File Service node will be deployed.

How does one troubleshoot and fix the error state?

Click Remediate File Service to start auto-remediation by force. In most cases, issues can be remediated automatically. If it keeps failing to deploy file service VM OVF, it's suggested to check the host and vSAN status for the file service VM deployment. VDFS Daemon health and Root File System Health are monitored and remediated periodically.

For the error "File service is comparatively overloaded on this host." Click "Remediate Imbalance" to start file server rebalance by force. In NFS share only cluster environment, the issue can be remediated automatically. If the host keeps in overloaded state, it's suggested to check other file service infrastructure issues at first. Note that, file server rebalance by force will lead to the movement of parts of file servers, which will cause SMB clients to be disconnected from SMB shares running on those file servers. So, please schedule a maintenance window for file server rebalance by force.

For the error "Cannot fetch file service balance status", it is usually caused by other file service infrastructure issues, please check them at first.

For the error "Load balance health check is not supported", please fully upgrade file service cluster to 7.0 u1 by referring to the vSAN file service upgrade admin guide.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
许可证升级后，vRA Code Stream 服务在 UI 中不可见 (76642)

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

Take Our Survey

Support Assistant