vSANFS fails to enable when hosts are configured with an isolated witness network for stretch clusters
Article ID: 326545
Updated On:
Products
VMware vSAN
Issue/Introduction
Symptoms:
vSAN Stretch cluster
Isolated witness network
vSANFS fails to get enabled with the following error message:
'Root filesystem not responsive. Cannot fetch file service balance status.'
vSAN Stretch cluster
Isolated witness network
vSANFS fails to get enabled with the following error message:
'Root filesystem not responsive. Cannot fetch file service balance status.'
Cause
Currently, whenever vSANFS starts getting enabled, "vdfsd" will query CMMDS for the "NET_INTERFACE" entries on every node and picks the first healthy IP address.
This means that vSANFS doesn't always pick the IP address of the "vsan" enabled vmk. If the user has configured an isolated witness network for vSAN (which means the host can communicate with witness node via witness network, but hosts can't communicate with each other via the witness network), then the communication between hosts for vSANFS won't be established.
This means that vSANFS doesn't always pick the IP address of the "vsan" enabled vmk. If the user has configured an isolated witness network for vSAN (which means the host can communicate with witness node via witness network, but hosts can't communicate with each other via the witness network), then the communication between hosts for vSANFS won't be established.
Resolution
Upgrade vCenter/ESXi to either version 7.0u3i and higher or 8.0u1 and higher
Additional Information
Impact/Risks:
- vSAN File Services fails to get enabled
- vSANFS shares may go inaccessible
Feedback
Yes
No
Powered by
