vSAN File Service Agent: VMs fail to obtain IPv4 address on eth0

Products

• VMware vSAN

Issue/Introduction

When activating vSAN File Services, the agent VMs (one per ESXi host) are successfully deployed, but they do not receive a working IPv4 address on their network interface (eth0).

Additional symptoms include:

• Inspection of the /etc/systemd/network/ directory on the vSAN File Service Agent VM reveals conflicting network configuration files. One file specifies DHCP=no for static addressing, while a second file specifies DHCP=yes.

• nslookup tests for the File Service FQDN or IP addresses may fail or return inconsistent results.

 

Environment

VMware vSAN 8.x

Cause

The behavior is by design. Static IP configurations do not bind to the base Linux OS (eth0) of the Agent VM. Instead, they are assigned directly to the storage protocol stack containers running inside the VM namespaces.

Resolution

No issue. Product functioning as expected.