vMotion fails with the error "A general system error occurred: vDS host error: see faultCause Cannot create DVPort <Port ID> of VDS <DVS Name> on the host <Hostname>"

Products

• VMware vSphere ESXi

Issue/Introduction

• ESXi host has been upgraded to 8.0.3
• ESXi host is part of a direct connect vSAN 2-node stretched cluster
• NIC teaming and failover setting on the vSAN portgroup has all the uplinks set as active
• vmkping between the vSAN vmkernels fails and one of the host is isolated from the cluster
• Hosts need a datastore to write in it .dvsdata and configurations from DVS.
• In hostd.log you see the following (names and timestamps may differ):

YYYY-MM-DDT:HH:MM:SS.XXXX info hostd[2328338] [Originator@6876 sub=Solo.Vmomi opID=1b3c072c-fed1 user=vpxuser] Result:
--> (vim.fault.DvsApplyOperationFault) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    objectFault = (vim.fault.DvsApplyOperationFault.FaultOnObject) [
-->       (vim.fault.DvsApplyOperationFault.FaultOnObject) {
-->          objectId = "xxxx",
-->          type = "vim.dvs.DistributedVirtualPort",
-->          fault = (vim.fault.PlatformConfigFault) {
-->             faultCause = (vmodl.MethodFault) null,
-->             faultMessage = <unset>,
-->             text = "Failed to update port persistence location"

YYYY-MM-DDTHH:MM:SS.XXXX warning hostd[2328338] [Originator@6876 sub=Hostsvc.NetworkProvider opID=1b3c072c-fed1 user=vpxuser] Skip saving dvport <DVS_NAME>-####  to /vmfs/volumes/vsan:###############-###########/########-####-####-####-#############/.dvsData/## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##/####: failed to create dir

 

Environment

ESXi 8.0.3
VMware vSAN

Cause

If NIC teaming and failover settings have multiple uplinks set to active, it's possible for a host to use as active a vmnic that does not match the active one on the other host.
This can cause loss of connectivity between the two hosts over the vSAN network.

Resolution

Resolve the vSAN connectivity issue by changing NIC teaming and failover settings to Active/Standby so both hosts use the same vmnic as Active, and a same alternate vmnic as standby: Direct connect vSAN 2-node stretched cluster is network partitioned and has basic unicast connectivity error in skyline health

Additional Information

How to configure NIC teaming in ESXi and ESX