vSAN FS docker Conatiner and DNS conflict in subnet 172.17.x.x

Products

• VMware vSAN

Issue/Introduction

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

 

In the UI you will see that the skyline health is showing the vSAN File Service connectivity in a degraded state with the message:

One or more DNS server is not reachable

 

Environment

8.x

Resolution

Validate in the File Service section in vSAN Services if you are using a DNS subnet in the range of 172.17.x.x.

In order to fix the issue you have to change the DNS to a different subnet. This is also mentioned in the limitation section of the Administering VMware vSAN guide:

https://docs.vmware.com/en/VMware-vSphere/8.0/vsan-administration/GUID-97223BF9-B8D4-4B3D-985D-739F6AC4F152.html