Virtual machines are reported to be inaccessible after exiting host out of maintenance.

Products

• VMware vSAN

Issue/Introduction

Symptoms:

• Virtual machines started going into inaccessible state once the host was exited out of maintenance.
• In vCenter UI, "vSAN cluster > Monitor > Virtual objects" Virtual machine objects shows inaccessible.

• Packet drops may be observed when vmkping is performed between the hosts vSAN network.

[root@Host#:~] vmkping -I vmk2 ##:##:##:## -d -s 8972
PING ##:##:##:## (##:##:##:##): 8972 data bytes

--- ##:##:##:## ping statistics ---
3 packets transmitted, 0 packets received, 15% packet loss

• In vCenter UI, vSAN cluster > Monitor > Skyline Health may report Network latency alarms.

 

Environment

VMware vSAN (All Versions)

Cause

This issue is caused due to network latency. "Network latency check" will be triggered by any host with more then 5 ms latency on the vSAN network.

VM may go inaccessible when multiple components of the object reports to be in Absent state due to slow resync when there is an ongoing Network latency issues.

In vCenter UI, vSAN Cluster> Monitor > Skyline health

 

Resolution

Engage the network team or vendor to further investigate the network latency issue.

Additional Information

Network latency check intermittently reporting high latency between nodes