vSAN Cluster partition due to VLAN misconfiguration
search cancel

vSAN Cluster partition due to VLAN misconfiguration

book

Article ID: 391883

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

Symptoms:

  • vSAN Cluster partition
  • vSAN: Basic (unicast) connectivity check alert
  • vmkping between the physical hosts/witness are unsuccessful
  • VM performance may be slow and sluggish
  • Object Resynchronization may be slow and sometimes stuck

Validations:

1. Skyline health reported with vSAN Cluster partition with vSAN: Basic (unicast) connectivity check under vSAN cluster>Monitor>Skyline health

 

 

2. Physical Host/Witness partitioned.
 
esxcli vsan cluster get
 
[root@Host1:~] esxcli vsan cluster get
   Sub-Cluster Membership Entry Revision: 0
   Sub-Cluster Member Count: 1
 
3. Unsuccessful vmkping over the vSAN VMK 
 
vmkping -I VMKX (WERE x IS THE VSAN VMK) ip 
 
 
[root@Host1:~] vmkping -I vmkX ***.**.**.3
PING ###.###.###.### (###.###.###.###): 56 data bytes
 
--- ***.**.**.3 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss

Environment

VMware vSAN (All versions)

Cause

Issue is caused due to the mis-configured VLAN tagging on the port of the physical port used by the vmk for vSAN/Witness traffic.

For example, If a host does not have the correct VLAN tagged on the physical switch when compared to the other hosts in the vSAN cluster for vSAN/Witness network, that host will will not be able to communicate with the other hosts on the vSAN network. 

Resolution

Engage your internal network team/vendor to further investigate the misconfiguration on your physical network, paying attention to VLAN tagging / trunk ports. 

Additional Information

Powered by Wolken Software