Search the VMware Knowledge Base (KB)
View by Article ID

Troubleshooting migration compatibility error: Currently connected network interface uses network, which is a virtual intranet (1003832)

  • 14 Ratings

Symptoms

  • A vMotion migration fails
  • When performing a vMotion migration, you see the compatibility error:

    Unable to migrate from source_server to destination_server: Currently connected network interface 'device' uses network 'network', which is a 'virtual intranet' .

Cause

This error indicates that the virtual machine is connected to a network that is internal only, which means that the virtual switch has no outbound adapters attached.  

Resolution

This issue is resolved in:
 
To workaround this issue when you do not want to upgrade, use one of these options:
  • Attach an outbound network adapter to the virtual switch.
  • Power down or suspend the virtual machine and perform a cold migration to the new host.

    Note: You may see a similar message during the cold migration if there is no internal only network with the same name on the destination server. This message is only a warning and can be ignored if you plan to create a proper switch on the destination server at a later time.

  • From a vSphere Client connected to the vCenter Server, navigate to Administration > vCenter Server Settings > Advanced Settings and add config.migrate.test.CompatibleNetworks.VMOnVirtualIntranet with the value set to false.

    Note: Making this change from vSphere Client does not require a restart of the Virtual Center Server service. To restore the usual checks, change the setting to "true".

    This setting can also be changed by adding these lines to the
    <config>flag in the VirtualCenter vpxd.cfg configuration file:


    <config>

       <migrate>
        <test>
          <CompatibleNetworks>
           <VMOnVirtualIntranet>false</VMOnVirtualIntranet>
          </CompatibleNetworks>
        </test>
       </migrate>
    </config>

    Note:
    For related information, see Enabling vMotion on internal vswitch behind bridged-mode firewalls and other network appliances (1006701).

See Also

Update History

02/25/2013 - Added fixed in vcenter Server 5.0 Update 2 07/15/2013 - Added fixed in vCenter Server 5.1 Update 1

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 14 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 14 Ratings
Actions
KB: