"Failed to connect to owner host xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx". Failed to create object error observed during the creation of virtual machine in vSAN cluster .

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• The following error appears in vCenter when attempting to create a virtual machine within a vSAN cluster.Cannot complete file creation operation. Failed to connect to owner host xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Failed to create object. Reserving folder on host.

                  

• vSAN Proactive Health tests fail with connectivity errors.
• esxcli vsan health cluster list shows "Red" for Network misconfiguration.
• Network tests show 100% packet loss between specific hosts or the witness node

    [root@esx-#### :~ ] vmkping -I vmk# ####.####.####.####
    PING ####.####.####.#### (####.####.####.####) : 56 data bytes
    --- ####.####.####.#### ping statistics ---
    3 packets transmitted, 0 packets received, 100% packet loss

Environment

VMware vSAN 7.x

VMware vSAN 8.x

Cause

Hosts in the vSAN cluster experience 100% packet loss over the vSAN network due to incorrect or unsupported jumbo frame (MTU 9000) configuration in the network path.

Resolution

1. Verify the MTU settings on all vSAN VMkernel interfaces.
   
   
2. Coordinate with the Physical Network Team to ensure the MTU is set to 9000 across the entire physical network path, including switch ports and routers.
   
   
3. If Jumbo Frames cannot be supported globally, change the MTU setting to 1500 on all vSAN VMkernel ports to allow successful host communication.
   
   
4. Perform a vmkping test between hosts to verify 0% packet loss.
   
   
5. Rerun the vSAN Proactive Network Performance test and Skyline Health check to confirm all green statuses.

Additional Information

To speak with a customer representative or a Support Engineer Contact Support