Automatic Private IP Addressing (APIPA) 169.254/16 prefix IPs configured for vSAN results in cluster partition.
Article ID: 374225
Updated On:
Products
Issue/Introduction
If vSAN nodes are configured with their vsan and/or witness-tagged vmkernel adapter in the APIPA address range 169.254.0.1 to 169.254.255.254, the cluster will not form as the nodes will remain network partitioned from one another.
Tests using vmkping between the nodes vsan-tagged IPs may not indicate any issue.
This can occur either if the addresses were assigned due to DHCP being configured and DHCP server being unavailable or if Static IP addresses are assigned and in this IP range.
Environment
VMware vSAN 6.x
VMware vSAN 7.x
VMware vSAN 8.x
Cause
vSAN requires routable addresses e.g. valid IPv4 addresses outside the 169.254/16 prefix for communication and intentionally prohibits use of APIPA range IPs.
Resolution
Ensure all nodes vsan and/or witness-tagged vmkernel adapters are assigned valid IP addresses outside of the 169.254/16 prefix (169.254.0.1 to 169.254.255.254).
Feedback
