VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
Verifying subnets/VLAN settings
To view correct subnet masks, the following ESXCLI command may be used on each
ESXi host in the cluster:
esxcli network ip interface ipv4 get –i vmk2
~ # esxcli network ip interface ipv4 get -i vmk2
Name IPv4 Address IPv4 Netmask IPv4 Broadcast Address Type DHCP DNS
---- ------------ ------------- -------------- ------------ --------
vmk2 172.32.0.4 255.255.255.0 172.32.0.255 STATIC false
~ #
One thing missing from the above output is the VLAN id associated with the Virtual
SAN network. This is important as the vmknic for the Virtual SAN network on some
hosts may be tagged with the VLAN IDs and others may not be tagged. This will
again lead to network misconfiguration and cluster partitioning.
To check which VLAN ID, if any, is associated with the Virtual SAN network, the
easiest way is to use the vSphere web client, and navigate to the VMkernel adapter
on each host, select the Virtual SAN network adapter, and check its properties as
shown below. This screenshot is taken from a Virtual SAN 5.5 deployment:
In this case, the Virtual SAN network is not using VLANs that is why the VLAN type
in the lower part of the screen is set to “None”. If VLANs were being used, this
information would be populated. This would then have to be checked on all hosts in
the Virtual SAN Cluster.
V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 1 2 0