vSAN file service is disabled on vCenter UI after moving hosts part of existing vSAN cluster to new vSAN cluster with error "Unable to extract requested data. Check vSphere Client logs for details"

Products

• VMware vSAN

Issue/Introduction

Symptoms:

• vSAN file service is disabled on vCenter UI>vSAN cluster>Configure>vSAN>Services.

"Unable to extract requested data. Check vSphere Client logs for details".

• vSAN Cluster>Monitor>Skyline Health may report below Infrastructure and file server health alarms. 

"Infrastructure Health" and "File server Health"

• These alarms may trigger after moving the hosts from existing VSAN cluster to new vSAN cluster.

 

Environment

VMware vSAN 8.x

vSAN File Services 8.x

Cause

The issue is caused due to incomplete and stale vSAN file service configurations being retained or carried over when hosts are moved from an existing cluster to a new vSAN cluster.

Stale file service configurations blocks the re enablement of file services on the vCenter UI.

## /var/run/log/vsan-mgmt logs reports "'vSAN file service not enabled'"

2025-12-17T09:12:26.185Z INFO vsan-mgmt[07366] [VsanClusterFileServiceSystemImpl::_queryFileServiceConfigsFromSingleHost opID=vsan-PC-#######] Calling host ##.com for query file service config: ['version']
2025-12-17T09:12:26.192Z ERROR vsan-mgmt[07366] [VsanClusterFileServiceSystemImpl::_queryFileServiceConfigsFromSingleHost opID=vsan-PC-#######] Query file service config failed on host.##.com
Traceback (most recent call last):
  File "bora/vsan/fileservice/vpxd/VsanClusterFileServiceSystemImpl.py", line 2152, in _queryFileServiceConfigsFromSingleHost
  File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 618, in <lambda>  File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 391, in _InvokeMethod
PyCppVmomi.vmodl.fault.SystemError: (vmodl.fault.SystemError) {
  msg = "Received SOAP response fault from [<<io_obj p:0x#######, h:59, <UNIX ''>, <UNIX '/var/run/envoy-hgw/hgw-pipe'>>, /hgw/host-##/vsan>]: queryFileServiceConfigs\nMethod vim.vsan.VsanFileServiceSystem.queryFileServiceConfigs threw undeclared fault of type vim.fault.InvalidState",
  faultCause = (vim.fault.InvalidState) {
    msg = '',
    faultMessage = (vmodl.LocalizableMessage) [
      (vmodl.LocalizableMessage) {
        key = 'com.vmware.vsan.fileservice.fault.notenabled',
        message = 'vSAN file service not enabled'
  reason = 'Undeclared fault'

## var/log/vmware/vsan-health/vmware-vsan-health-summary-result.log shows that there are no file server configured which leads to  blocking in vSAN File service in vCenter UI.

2025-12-17T09:13:08.440Z INFO vsan-mgmt[80332] [VsanHealthSummaryLogUtil::PrintHealthResult opID=####] Cluster ##  Overall Health : red
   Group fileservice health : red
      Test host health : red
         InfrastructureHealth: Host  VsanFileServiceNode  VdfsDaemon  RootFileSystem  WorkloadBalance  Description
                               (Host-##, Red, Red, Red, Skipped, FileServiceIsNotEnabled.), (Host-##, Red, Red, Red, Skipped, FileServiceIsNotEnabled.),
(Host-##, Red, Red, Red, Skipped, FileServiceIsNotEnabled.),
      Test fileserver health : yellow
         FileServerHealth: IssueInformation
(NoFileServerConfigured.PleaseCheckTheFileServiceDomainConfiguration.),

 

## /var/run/log/vsan-mgmt logs reports shows that there are issue in accessing the rootfs and monitoring stale config fails.

[VDFSEndpointLibrary::RetryRootVolumeAccess] Got exception when accessing root volume: _GetCo
nfigVersions: [Errno 111] Connection refused: '/vmfs/volumes/vdfsDatastore/####/volumes/default/config.json'
2025-12-16T11:01:07.307Z Er(11) vsanfs.mgmt[2136543]: [2137398] [VDFSEndpointConfig::_MonitorStaleConfig] Failed to monitor stale config
2025-12-16T11:01:07.307Z Er(11)[+] vsanfs.mgmt[2136543]: Traceback (most recent call last):
2025-12-16T11:01:07.307Z Er(11)[+] vsanfs.mgmt[2136543]:   File "/usr/lib/vmware/vsan/perfsvc/VDFSEndpointConfig.py", line 180, in _MonitorStaleConfig
2025-12-16T11:01:07.307Z Er(11)[+] vsanfs.mgmt[2136543]:   File "/usr/lib/vmware/vsan/perfsvc/VDFSEndpointConfig.py", line 746, in GetDomainConfigFile
2025-12-16T11:01:07.307Z Er(11)[+] vsanfs.mgmt[2136543]:   File "/usr/lib/vmware/vsan/perfsvc/VDFSStubImpl.py", line 635, in VdfsIoPathWrapper
2025-12-16T11:01:07.307Z Er(11)[+] vsanfs.mgmt[2136543]:   File "/usr/lib/vmware/vsan/perfsvc/VDFSStubImpl.py", line 596, in funcWrapper
2025-12-16T11:01:07.307Z Er(11)[+] vsanfs.mgmt[2136543]: ConnectionRefusedError: [Errno 111] Connection refused: '/vmfs/volumes/vdfsDatastore/#######/volumes/default/config.json'

Resolution

File service configuration cleanup or erasure needs to performed to get back the "Fileservice" enable option on VC UI.

Please contact Broadcom Support to run the script for completely removing the vSAN File Service configuration upon thorough investigation. 

Re-enable vSAN File Services following the network best practices.

Networking Considerations for vSAN File Service

Note: Running this script will wipe out the file shares resulting in the data on these shares being wiped as well so it's critical to have backups of the data.