In this blog post I’m going to show you how can enable vSAN 7.0 File Service. This article doesn’t cover of vCenter, vSphere ESXi and vSAN upgrade process, just show you how can configure one of new capability of vSAN 7.0 I don’t want to rob your time let’s jump in.
Open vCenter server and select your vSAN cluster where you want to enable File Service.
Configure vSAN file service
When you selected your vSAN cluster jump to Configure / vSAN / Services menu and push Enable button in line of File Service.
Configuration wizard will popup. You need to have the following information to File Service wothout Kerberos authentication:
- Static IP address
- Subnet mask and Gateway
- DNS server (valid)
- Reverse DNS lookup
In my lab environment I use a Microsoft Active Directory integrated DNS server, where I had created DNS names.
I don’t have internet connection in my lab subnet, so I had to download and install File service agent by manual approach.
You can download vSAN File Service Appliance from my.vmware.com site. You need all files below.
Select all files (6 pieces) and click Open. The files will be uploaded to vCenter server appliance.
Click Next after the files uploaded to vCenter server appliance. You can check it here:
In the next section you can configure Domain settings:
File service domain: vsan-fs
DNS servers: 172.24.0.177 (this is my AD integrated DNS server)
DNS suffixes: mydomain.loc (i use my AD domain name)
At the IP Pool section just write your first IP address of vSAN File Service Agent appliance and hit AUTOFILL option. The wizard will fill the IPs in order. Good checking options when you use LOOKUP DNS. Just push the link and wizzard will resolve your DNS names. If it matches your IPs you configugured DNS well. Crosschek! 🙂
Before you hit the Finish button I recommend to disable or set DRS to parity automated! Check your review and finish the process.
The wizzard are going to create vSAN file service agent appliances (VMs) from OVF template. Every host will running one copy of appliances. You can see the VMs under “ESX Agents” resource pool. End of the deployment process the appliances state change to powerOn and vCenter enable vSAN file service on hosts.
Just go back vSAN cluster / Configure / vSAN / Services menu and notice that the File service state changed from Disabled to Enabled. This is not the end of story. Until this you just configured vSAN file services and now you are able to create NFS shares.
Create NFS share on vSAN
vSAN Cluster / Configure / vSAN / File Shares and click Add icon.
Just type your share name. As you can see NFS 4.1 and NFS 3 are supported. You can create warning and hard quota and labels. Labels similar as tags. Create a key like Applications and add an value like Demo. It is case sensitive. Now you can filter by labels. It helps to you in search.
Set up access control. In my lab I decided to use customize access. I type my lab’s subnet and provided to RW access. Click Next see review and then click Finish to create share.
Now you can see your share under File Shares. For deatails just click name of share or the little icon next name of share.
I would like to check my NFS share so I moint it to my W10 Client. In case of W10 don’t forget enable NFS Cliens feature on Windows. When you select your share in vCenter and click to “COPY PATH” button, the GUI will show you the path of your share.
In W10 I used this command:
moint -o anon \\vsan-fs01.mydomain.loc\NameOfShare Z:
(where “Z:” is the drive letter where I want to mount NFS share) Now I able to copy files and create folders on my vSAN File Share 😀