Troubleshooting the migration compatibility error: Currently connected network interface uses network, which is not accessible
search cancel

Troubleshooting the migration compatibility error: Currently connected network interface uses network, which is not accessible

book

Article ID: 318738

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • When performing a vMotion migration, you see one or more of these compatibility errors:
     
    • Unable to migrate from source_server to destination_server: Currently connected network interface 'device' uses network 'network', which is not accessible
    • Currently connected network interface 'device' uses network 'network', which is not accessible.
       
  • The Network Label on the effected virtual machine settings is blank when the network portgroup label is renamed.


Environment

VMware vCenter Server 
VMware vSphere ESXi

Cause

This issue occurs for one of these reasons:

Resolution

To work around this issue, ensure that the virtual machine network port groups are named the same across all of the ESX hosts that participate in the vMotion operation.

After checking, verify and/or change the network label of virtual machine:
  1. Right-click the virtual machine, click Edit.
  2. Change the Network Label to the newly named port group.


Additional Information

In most cases, this is an error only seen with standard vSwitches.
This same message can also be presented using a distributed vSwitch (vDs) with LACP configured.

If you see this for a vDs run the following command in the ESXi command line for the destination host.

  • esxcli network vswitch dvs vmware lacp status get

The expected output should show that the LACP teaming on the physical switch side is not "bundled" and instead showing "independent" or "standalone".
If this shows anything other than "bundled" the physical network team needs to resolve the misconfiguration with the LACP in the physical switch.