vMotion fails for VMs on NSX-prepared DVS regular port groups
search cancel

vMotion fails for VMs on NSX-prepared DVS regular port groups

book

Article ID: 445795

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Attempting to vMotion fails with the following error:
    "Current connected network interface" 'Network adapter #' uses network '<PortGroup_Name> (<DVS_Name>)', which is not accessible.

  • Running the net-dvs -l command on the destination ESXi host for the target DVS yields the following result:
    [root@<Destination_ESXi>:~] net-dvs -l
    switch ## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## (vswitch)
    ...
    	host properties:
    		com.vmware.common.host.volatile.overlay.status = red nsxa down, 	propType = RUNTIME
    ...

Environment

VMware NSX

Cause

  • This issue can occur if there is a connectivity problem between the target ESXi host and the NSX Manager. A connectivity issue between the ESXi host and the NSX Manager does not trigger this problem immediately. However, if the target ESXi host or the nsx-opsagent is restarted while the connectivity issue persists, the status changes to com.vmware.common.host.volatile.overlay.status = red nsxa down, at which point the issue manifests.
  • Even if NSX has been uninstalled, this issue may still occur if com.vmware.common.host.volatile.overlay.status remains on the target DVS due to an issue similar to the one described in KB#416818. If this is the case, perform the steps outlined in the Resolution section of KB#416818.

Resolution

Resolve the connectivity issue between the target ESXi host and the NSX Manager.