Consider the following when configuring vSAN File Service:

  • With vSAN 7.0 U3, File Service VMs are powered off and but no longer deleted when the vSAN cluster enters maintenance mode.
  • vSAN 7.0 Update 3 supports two-node configurations and stretched clusters.
  • vSAN 7.0 Update 3 supports 64 file servers in a 64 host setup.
  • vSAN 7.0 Update 3 supports 100 file shares.
  • vSAN File Services does not support the following:
    • Read-Only Domain Controllers (RODC) for joining domains because the RODC cannot create machine accounts. As a security best practice, a dedicated org unit should be pre-created in the Active Directory and the user name mentioned here should be controlling this organization.
    • Disjoint namespace.
    • Spaces in organizational units (OUs) names.
    • Multi domain and Single Active Directory Forest environments.
  • In releases prior to vSAN 7.0 Update 3, when a host enters maintenance mode, the Protocol Stack container moves to another FSVM. The FSVM on the host that entered maintenance mode is deleted. After the host exits maintenance mode, a new FSVM is provisioned.

  • vSAN File Services VM (FSVM) docker internal network may overlap with the customer network without warning or reconfiguration.

    There is known conflict issue if the specified file service network overlaps with the docker internal network (172.17.0.0/16). This causes routing problem for the traffic to the correct endpoint.

    As a workaround, specify a different file service network so that it does not overlap with the docker internal network (172.17.0.0/16).