When attempting a vMotion of a VM from one host to another, receive error "Currently connected network interface" '####' uses network '####-####', which is a 'virtual intranet'."

Products

• VMware vSphere ESXi

Issue/Introduction

When attempting a vMotion of a VM from one host to another, you may receive the error "Currently connected network interface" '####' uses network '####-####(#######-#######)', which is a 'virtual intranet'." as a "Compatibility Issue".

Where:

• '####" in the message is the name of the virtual NIC that you can see by choosing "Edit Settings" on the VM and looking at the Network Adapter section
• '####-####' in the message is the name of the distributed virtual port group on the vDS named '#######-#######'

The error refers to a problem on the target host.  The target host name will be shown under the error message.  See screen shot example below:

Cause

You will find that on the target host, the copy of the vDS is not as required to allow the migration. 

Possible causes include:

• The vDS copy on the target host has no uplinks assigned
• The vDS copy has one or more uplinks, but they are not in a "Up" state.

Resolution

1. Determine which vmnic(s) you wish to have assigned to which uplink(s) on the target host for the vDS in question.
2. Using the vSphere client to vCenter, select the Networking icon, then navigate to the vDS, Choose the "Add / Manage Hosts" action --> Manage Hosts and select the target host
3. Proceed through the wizard to Physical Adapters and then assign the appropriate Uplink(s) to the appropriate vmnic(s) according to your choices from step 1. 
4. Continue through the wizard through the Finish step.  

 

If this does not resolve the issue, or if you then encounter a different issue, please open a case with Broadcom Networking support, using the instructions at Creating and managing Broadcom support cases