vSAN: Basic (unicast) connectivity check.vSAN : MTU check (ping with large packets) Vsan object healthvSAN: Basic (unicast) connectivity check".
PING xx.xx.xxx.xx ( xx.xx.xxx.xx): 1472 data bytes--- xx.xx.xxx.xx ping statistics ---3 packets transmitted, 0 packets received, 100% packet loss
PING xx.xx.xxx.xx ( xx.xx.xxx.xx): 8972 data bytes--- xx.xx.xxx.xx ping statistics ---3 packets transmitted, 0 packets received, 100% packet loss
Either of the above tests failing confirms there is an issue preventing network connectivity between vSAN vmkernels on different ESXi hosts. The hosts are unable to communicate with each other over vSAN traffic due to an NIC issues
esxtop > press 'n' key TEAM-PNIC column across from the vmkernel for the vSAN service is the active vmnic serving vSAN traffic. esxcli network nic down -n vmnicX (where vmnicX is the vmnic being used by the vSAN vmkernel)ESXTOP data by confirming there is a different vmnic under the TEAM-PNIC column after administratively downing the active vmnic. vmkping -I vmkX -d -s 1472 <ip address>"vmkping -I vmkX -d -s 8972 <ip address>"