Virtual Machine vMotion task fails during pre-check stage with "Network Not Accessible" when the VM is connected to a vSphere Distributed Switch (vDS) port group.

Products

• VMware vSphere ESXi

Issue/Introduction

• Migration Wizard Failure: Attempting to migrate a VM to specific host fails at the network pre-check stage.

Compatibility
"Currently connected network interface" 'Network adapter 1' uses network 'xxxxx', which is not accessible.

Environment

VMware ESXi 8.x
VMware vCenter 8.x

Cause

• Review of the vCenter vpxd.log ( /var/log/vmware/vpxd) at the specified timestamp indicates the following compatibility check result:

 info vpxd[] [Originator@6sub=VmCheck opID=] CompatCheck results: (vim.vm.check.Result) [
-->    (vim.vm.check.Result) {
-->       vm = 'vim.VirtualMachine::vm-',
-->       host = 'vim.HostSystem:host-',
-->       error = (vmodl.MethodFault) [
-->          (vim.fault.CannotAccessNetwork) {                      <-----------------------
-->             device = "Network adapter 1",
-->             backing = "DVSwitch: ",
-->             connected = true,
-->             msg = "",
-->          },
-->          (vim.fault.FeatureRequirementsNotMet) {                <-----------------------
-->             host = 'vim::host-',
-->             msg = "",
-->          }
-->       ],
-->    }
--> ]

• Further analysis of the net-dvs-l data on the affected ESXi host indicates the following error for the host LACP LAG:

  host properties:
                com.vmware.common.host.volatile.status = yellow Set host status property for a LAG is failed to form,   propType = RUNTIME
                com.vmware.common.host.volatile.dvsID =  ,       propType = RUNTIME
                com.vmware.common.host.portset = DvsPortset ,         propType = CONFIG
                com.vmware.common.host.volatile.overlay.status = green ,        propType = RUNTIME
                com.vmware.common.portset.opaque = false ,      propType = RUNTIME
                com.vmware.net.feature.cap.supportVmotionFromOpaqueNetwork = 1 ,        propType = CONFIG
                com.vmware.common.host.lacp.extraconfig:
                        lag name:                       lag
                        lag timeout:                    slow

• Further review of the LACP status (esxcli network vswitch dvs vmware lacp status get) on this host indicates that the partner is not in the bundled state.

   DVSwitch: DVS_Name
   Flags: S - Device is sending Slow LACPDUs, F - Device is sending fast LACPDUs, A - Device is in active mode, P - Device is in passive mode
   LAG ID: 
   Mode: Passive
   Nic List:
            Local Information:
                  Admin Key: 15
                  Flags: SP
                  Oper Key: 15
                  Port Number: 2
                  Port Priority: 255
                  Port State: AGG,SYN,
            Nic: vmnicx
            Partner Information:
                  Age: 00:00:00
                  Device ID:
                  Flags:
                  Oper Key: 0
                  Port Number: 0
                  Port Priority: 0
                  Port State:
            State: Independent    <----------------------------

            Local Information:
                  Admin Key: 15
                  Flags: SP
                  Oper Key: 15
                  Port Number: 1
                  Port Priority: 255
                  Port State: AGG,SYN,
            Nic: vmnicy
            Partner Information:
                  Age: 00:00:00
                  Device ID:
                  Flags:
                  Oper Key: 0
                  Port Number: 0
                  Port Priority: 0
                  Port State:
            State: Independent    <---------------------------------

 

Resolution

• The Distributed Virtual Switch (DVS) status is currently degraded (indicated by a yellow state) due to the identified LACP configuration issues.
• To resolve this, the recommended action is to configure the LACP group consistently on both the physical switch and the ESXi host.
• Expected Outcome: Successfully configuring the LACP group is projected to restore the DVS status to a normal, operational state, thereby enabling successful vMotion operations.