vmkernel ports for VSAN don't get DHCP addresses

[huchord]

Creating a VSAN cluster with two hosts.

All looks good, the wizard seems to complete fine.

However, the vsan pings don't seem to work, almost certainly because the DHCP didn't work for some reason.

I also tried static addresses in the 192.168.1 subnet.  Still didn't work - even tried vmkpings on the hosts.

Looking for some ideas.

[TheBobkin]

Hello sreeve3939​.

Those are APIPA addresses that are assigned - these won't work for vSAN traffic.

"I also tried static addresses in the 192.168.1 subnet."

Did you disable vSAN traffic on the original vmk (untick the box in the network adpaters page) before enabling on the new vmk?

If you didn't then do that and also validate that vCenter has pushed the new IPs to the unicast agent lists via the Health UI 'vCenter is Authoritative' check:

VMware Knowledge Base

"However, the vsan pings don't seem to work"

"Still didn't work - even tried vmkpings on the hosts."

Can you clarify what you were testing with vmkping that did/didn't work?

Bob

[huchord]

The other vmkernel ports all have no vsan config on them.

I checked them all - no mention of vsan.

The "vCenter is Authoritative" check is Green.

I tried 192.168.2 addresses on both vmkernel ports - that didn't work either:

I tried a vmkping from the esxcli shell of each host:

192.168.1.2.100 couldn't vmkping 192.168.2.101

192.168.2.101 couldn't vmkping 192.168.2.100

[huchord]

Another screen shot.

[huchord · Accepted solution]

Problem solved.

When creating the vsan, there was a checkbox for VLAN.

It was checked with a value of 0.  I thought this meant "no 802.1q".

Turns out that I needed to uncheck the checkbox to remove 802.1q.

Then I obtained my DHCP addresses no problem.