Recently I was working on a project where I had to configure the vSAN fileservices on a VCF VI WLD cluster.
Below is the procedure to enable the vSAN file service:
Login to vCenter
Click on the cluster on which you want to enable vSAN FS
Click on Configure
Click on Services under vSAN
Then click on File Services and then click on Enable, you will a new wizard to configure VSFS
In the File service agent page, select one of the following options to download the OVF file
In the Domain page, enter the following information and click Next
On the Networking page, enter the following information, and click Next:
In the IP Pool page, enter the following information, select a Primary IP, and then click Next.
You can use the following options to automatically fill the IP address and DNS server name text boxes:
AUTO FILL: This option is displayed after you enter the first IP address in the IP address text box. Click the AUTO FILL option to automatically fill the remaining fields with sequential IP addresses, based on the subnet mask and gateway address of the IP address that you have provided in the first row. You can edit the auto-filled IP addresses.
LOOK-UP DNS: This option is displayed after you enter the first IP address in the IP address text box. Click the LOOK UP DNS option to automatically retrieve the FQDN corresponding to the IP addresses in the IP address column.
Review the settings and click Finish.
You can refer to this VMware document for prerequisites.
During the configuring of the vSAN file services I was getting the error on different hosts each time I tried to disable and enable the vsanfs, and after some time ultimately the task fails with the below error where the vsfs (vSAN File services) VM was unable to join the domain:
Note: The IP which we specify during the vSAN fileservices configuration does not get assigned to FSVMs, instead the containers within the vsfs VMs are assigned the IP addresses.
2023-07-05T18:40:01.588Z error [fs-sched-D-4] [WaitObjects] Failed to wait objects ['fscontainer/10.200.220.11', 'fscontainer/10.200.220.12', 'fscontainer/192.168.10.11', 'fscontainer/192.168.10.11', 'fscontainer/192.168.10.12', 'fscontainer/192.168.10.12', 'fscontainer/192.168.10.13', 'fscontainer/192.168.10.13', 'fscontainer/192.168.10.14', 'fscontainer/192.168.10.14'] Traceback (most recent call last): File "/usr/lib/vmware/vsan/perfsvc/VDFSEndpointController.py",line 2562, in WaitObjects TimeoutError: Timeout to wait objects ['fscontainer/192.168.10.11', 'fscontainer/192.168.10.11', 'fscontainer/192.168.10.12', 'fscontainer/192.168.10.12', 'fscontainer/192.168.10.13', 'fscontainer/192.168.10.13', 'fscontainer/192.168.10.14', 'fscontainer/192.168.10.14', 'fscontainer/192.168.10.11', 'fscontainer/192.168.10.11']
From the error looks like the DNS server the FSVM is failing to reach the DNS server during the joining of the AD.
So I decided to try to configure the vSAN FS without AD first. Then from the running container, I can verify the network connection between the container and the AD server.
I was able to successfully configure the vSAN FS without AD, then from the container tried to ping the AD server and the AD server was not reachable.
Once the FSVM is deployed you can execute the below command to check the network connection:
docker ps
docker exec -it <container ID> bash
ping <dns server> 
So I got to know where the issue (Network connection issue between the vSAN FS vLAN and the AD server) is and what to fix (It was identified that the FSVM's vlan was not added to the TOR switch ports and needed to update the routing table).
Post correcting the network connection I tried updating the AD and this time it was enabled successfully without any issues.
Happy learning.....
Comentarios