Enabling vSAN file services
From Notes_Wiki
<yambe:breadcrumb self="Enabling vSAN file services">VMWare VSAN|VMWare VSAN</yambe:breadcrumb>
Enabling vSAN file services
To enable vSAN file services use following steps
- Login into vCenter
- Ideally distributed switch; a dedicated distributed port-group and optional VMkernel IPs on this distributed port-group are already configured for ESXi hosts
- Go to cluster -> Configure -> services. Click "Enable" or "edit" against vSAN file services.
- In the dialog box of vSAN file services enter following
- Approach
- Go with automatic approach with automatic download of required images
- File service domain
- Name via which file services can be accessed such as vfiles.example.com
- DNS servers
- Local DNS servers (possibly AD)
- DNS suffixes
- Various domain names used locally which should be able to access file services. (Example vfiles.example.com, example.com). Here we must add vfiles.example.com to DNS suffixes list for configuration to get accepted.
- Directory service
- If there is local AD and we enable this then only machines / users who are part of domain can access the created SMB shares. For this the service account should have administrative privileges to add required computer to AD computer list.
- Network parameters
- Mention distributed port-group to use along with netmask and gateway information
- Host IPs
- Choose as many IPs as esxi hosts. So if you have 5 hosts, ideally choose 5 IPs. For each IP we can map a DNS FQDN such as esxi01.vfiles.example.com in DNS server
- Create DNS entry of selected file service domain - vfiles.example.com pointing to file services IP chosen for hosts in previous step (All IPs of all hosts). Note that this is for file services IPs and not related to any VMkernel IPs that might have been assigned on that particular distributed port group.
- Ensure that forward DNS resolution for vfiles.example.com (To any of file services IP), esxi01.vfiles.example.com (To corresponding file services IP for esxi01, etc. works as expected.
- Wait for some time (eg 5 minutes) for file services VM to be created and configured at back-end
- Create a test share with desired name, protocol SMB (esp. if AD is configured) or NFS, desired quota settings
- Access the test share from appropriate client machine (Domain machine in case AD was configured), NFS client in case of NFS share.
- Note that in case AD is configured only AD users can connect to shares. For read-write permissions using Windows file permissions for read-write etc. control from windows explorer might work.
Refer:
- https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan.doc/GUID-CA9CF043-9434-454E-86E7-DCA9AD9B0C09.html
- https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan.doc/GUID-C97A317A-2701-4EFE-B7D9-D036FE1D1F8F.html
- https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan.doc/GUID-82565B82-C911-42F7-85B1-E9EF973EE90C.html
<yambe:breadcrumb self="Enabling vSAN file services">VMWare VSAN|VMWare VSAN</yambe:breadcrumb>
