Troubleshooting migration compatibility error: Currently connected network interface uses network, which is a virtual intranet
Article ID: 302355
Updated On:
Products
Issue/Introduction
- 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
Resolution
- vCenter Server 5.0 Update 2. To download vCenter Server 5.0 Update 2, see the VMware Download Center.
- vCenter Server 5.1 Update 1 . To download vCenter Server 5.1 Update 1, see the VMware Download Center.
- 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).
Additional Information
Feedback
