Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

vMotion fails with the error: Destination Host Not on Same Networks as Virtual Machine You Are Trying to Migrate (1723)

Last Updated: 3/24/2017Categories: Total Views: 13375Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

I'm attempting to use VMotion to migrate a virtual machine from one ESX Server system to another. In VirtualCenter, the Networks section is blank for the source server on the host summary page. Why do I receive the following error message?

Error: The destination host is not on the same set of networks as the virtual machine you are trying to migrate. Please make sure that all of the NICs on the destination host are connected to the same networks as the virtual machine.

Solution

VirtualCenter checks the names of the virtual switches that the virtual machine to be migrated is using. It expects to find identically named virtual switches on the destination ESX Server system. For example, if you have a virtual machine connected to a virtual switch called Network1, then a virtual switch called Network1 must exist on the destination ESX Server system.
Note: Although it verifies matching virtual switch names, VirtualCenter does not verify that the virtual switches are connected to the same physical network. Confirm the following:

The name of each virtual switch (network connection) used by the virtual machine you intend to migrate matches the name of an existing virtual switch on the target ESX Server system and both virtual switches access the same network.

The service consoles for both ESX Server systems access the same network.

The network adapters that are used to migrate the virtual machine access the same network.

In addition, verify that your environment meets the general VMotion requirements in the VirtualCenter 1.x documentation. To satisfy the items above, follow these steps to verify and set the virtual network adapter configuration.

In the Management Interface of the source ESX Server system, click the name of the virtual machine you plan to migrate. A new window opens.

Click hardware.

In the Network Adapter section, Click Edit.

Look at the available Network Connection entries.

If you find a Network Connection entry that satisfies the following two conditions, choose it and try migrating the running virtual machine again. Skip to the migration step, below. Prerequisites to choosing a Network Connection entry for migrating a running virtual machine include the following:

The Network Connection entry name must exactly match the name of the virtual switch that this virtual machine will use on the target ESX Server system.

The Network Connection entry must use the same physical network as the virtual switch on the target ESX Server system.

If a qualifying entry is not listed in the Network Connection dropdown menu, add a new entry by creating a new virtual switch as follows:

In the Management Interface of the source ESX Server system, click the Options tab.

Click Network Connections.

In the Overview section, click Add.

Enter the desired network connection name in the Network Label box.

Click Create Switch. By default, it is not connected to any outbound (physical) adapters, but you can connect it to any available outbound adapter.

If the new virtual switch satisfies both prerequisites above for using an entry in the Network Connection dropdown menu, choose it and retry the migration. Skip to the migration step, below.

If you cannot connect the new virtual switch to the network currently used by the virtual machine, you can either:

Connect the virtual machine to the new virtual switch anyway, which disconnects it from the network. Then skip to the migration step, below. After migration, the network connection should be restored.

Or, follow the steps below to prepare the virtual machine for migration without disrupting its network connection.

To prepare the virtual machine for migration without connecting it to the new virtual switch (which would disconnect the virtual machine from the network):

Connect to the source ESX Server system's service console.

Find the virtual machine configuration files on the ESX Server host system. Their paths are listed in /etc/vmware/vm-list.

Using a text editor, carefully edit one of the virtual machine configuration files--one that is for a currently running virtual machine--as a test subject.

Find a line that looks something like:

Ethernet0.networkName = "Adapter0 Network"

Change it to look like this:

Ethernet0.networkName = "MyNetwork"

Save the file.

Notes:

Replace the part in the quotation marks, MyNetwork, with the name of the network connection (virtual switch) you created above.

Ethernet0.networkName (or Ethernet1.networkName, etc.) is not case-sensitive.

If the line does not exist in the file at all, add it.

You can confirm that you have chosen a valid network name by viewing /etc/vmware/netmap.conf on the destination ESX Server system and looking for the name of the network connection you created on the source ESX Server system.

The running virtual machine continues to use the network to which it was connected when it started. If you reboot the virtual machine, however, the newly created network connection is used.

If the virtual machine must not be powered off, you need to temporarily bypass VirtualCenter's check for network connectivity while it performs a hot migration:

Edit config.ini in the VMware VirtualCenter folder on the system that is running the VirtualCenter management service. By default, the path to this folder is:

Windows Server 2000, 2003 and Windows XP:

C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter

Windows Server 2008, 2012, Windows Vista, 7 and 8:

C:\ProgramData\VMware\VMware VirtualCenter

Note: If the config.ini file does not exist, create it.

Add the following line to config.ini to disable the check that prevents the virtual machine from migrating.

migrate.check.nicCompat="FALSE"

Restart the VirtualCenter service for the change to take effect.

Perform a migration of the virtual machine in VirtualCenter. If you reconfigured the virtual machine to use a different network connection, you might observe that it hasn't changed in VirtualCenter. Depending on your version of VirtualCenter, the updated network connection name might not be shown after migration. You can use the management interface on the destination ESX Server system to check the network connection setting. You should also ping or otherwise confirm network connectivity to the migrated virtual machine.

If you disabled the VirtualCenter network check above, re-enable this important integrity check.

Edit the VirtualCenter config.ini file.

Change the value to "TRUE". For example:

migrate.check.nicCompat="TRUE"

Restart the VirtualCenter service.

If you created a virtual switch as described above, but the virtual switch is not connected to the desired network, you might want to delete the virtual switch after the migration is complete.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware ESX Server

Related Versions:

VMware VirtualCenter 1.2.x

VMware VirtualCenter 1.1.x

VMware VirtualCenter 1.0.x

VMware ESX Server 2.5.x

VMware ESX Server 2.1.x

VMware ESX Server 2.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant