Server went into orphan state and cannot open the VM folder on datastore to reregister it.
search cancel

Server went into orphan state and cannot open the VM folder on datastore to reregister it.

book

Article ID: 391050

calendar_today

Updated On:

Products

VMware vSAN 8.x

Issue/Introduction

VSAN cluster has issue where a VM went into an orphan state. When trying to navigate to the datastore to reregister the VM, could not find the home folder for the VM.

vSAN health service is reporting:

[root@Host3:~] esxcli vsan health cluster get -t siteconnectivity
Site latency health        yellow

Checks the worst network latency between any two hosts in data sites and the witness. NOTE: This check will skip the pair of hosts failing in vSAN basic connectivity (small ping) test.
Ask VMware: vSAN Health Service - Stretched cluster - Site latency

Site Latency
Fault Domain     Fault Domain     Observed Latency (ms)     Threshold (ms)     Latency Result
--------------------------------------------------------------------------------------------------
Preferred        Secondary        13.97                     5                  yellow
Preferred        Witness Host     20.64                     500                green
Secondary        Witness Host     20.59                     500                green

Environment

VMware vSAN (All Versions)

Cause

Datacenter had an issue where one of the NICs was running at 100mb, this is well below vSAN supportability, see Networking Requirements for vSAN

 

 

Resolution

Engage networking team to vet the Network health.