Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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 - File Server Health (77165)

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

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

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

Solution

Q: What does File Service - File Server Health check do?

It checks if the file server is in a good state.
The column NFS Daemon checks if the NFS daemon process is running or not.
The column Network checks if the file server IP address is assigned or not.
The column Root File System Accessibility checks if the root file system is accessible to the file server.
The column SMB Connections shows the number of  active SMB client connections to the file server.
The column SMB Daemon checks if SMB daemon  process is running or not, and checks if the number of SMB client connections exceeds the limit.
The column DNS Lookup checks whether File server DNS configuration and connectivity is correct or not.
The column Active Directory checks whether File server AD join configuration and connectivity is correct or not.

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

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

Check Item

Error Message Type

Network

File server IP address is not present

File Server

File server not found

NFS Daemon

NFS daemon is not running

Root File System Accessibility

Root file system is not responsive to the file server

SMB Daemon

SMB daemon is not running

Current SMB connections ({count}) to the file server exceed the limit ({200}).

DNS Lookup

One or more DNS server is not reachable or File server IP and FQDN not matching with DNS entries.

Active Directory

File service is not configured with Active Directory. <Should be ignored>

One or more domain controllers are not reachable from file server.

Note: There will be an error for 60 seconds when host enters maintenance mode or reboots.

Note: If the description shows 'File server not found', then items 'NFS Daemon', 'Network' and 'Root File System Accessibility' will all be marked red.

Q: How does one troubleshoot and fix the error state?

For file server health, the health status of its managing host and the corresponding file service VM needs to be confirmed. If there are enough healthy hosts with healthy file service VM, file server will be failed over automatically to another healthy host once it detects that the file server has some issues. The file server will not be marked GREEN until the failover process is completed.

For the error "SMB daemon is not running", Click Remediate File Service to start auto-remediation by force. In most cases, issues can be remediated automatically.

For the error "SMB connections exceed the limit":
The performance of shares running on the file server with the warning message cannot be guaranteed. It is suggested to:

Close Idle SMB connections through MMC (Microsoft Management Console)

run "fsmgmt.msc /computer:\\<fileServerFQDN>" on Windows client to open MMC

click "Sessions" in the left pane, live SMB connections will be display in the right pane. close idle connections.

For DNS Lookup related error it is suggested to check following items:

Check if file service network can reach DNS servers.

Check if all of provided DNS servers are reachable. In case one or more DNS servers are changed, please update the File Service Domain configuration.

Check if both forward and reverse lookup entries are there for file server FQDN with DNS server.
Quick way to check is using nslookup utility and query FQDN and IP from DNS server.

For Active Directory related error it is suggested to check following items:

Check if AD is reachable from file service network.

Check if AD domain is responding well to other machines within the domain.

Check if the latency to authenticate with AD domain is too high.

Check if password provided at the time of configuration has been changed recently.

Check if there is any recent change in user permissions or related computer accounts for file servers,

Check if some domain controller in Active Directory domain is down.

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
•
プリエンプティブ フェイルバックで、新しいスタンバイ T0 ルータの BGP ピアリングがアクティブのまま停止する (77023)

KB
•
快照 LUN 的重新签名操作失败，并出现错误：VmfsAlreadyMounted (76989)

Results 1-3 of 3

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

Take Our Survey

Support Assistant