Solved

Unable to vmotion between vDS Switch in vCenter 6.0 Web Interface

Posted on 2016-08-24
11
272 Views
Last Modified: 2016-08-28
In vCenter 6 when I try to vmotion a VM to a new host on another vDS I am getting the following errors in the compatibility check.

"Change the network and host of a virtual machine during vmotion isi not supported on the "source" host"

"Current connected network interface "network adapter 1" cannot use network XXXXXXXXX becuase the destination vDS has a different version and or vendor than the source.."

Source vDS = Version 5.1 | ESXi host version 5.1
Destination vDS = 5.1 | ESXi host version 6.0
0
Comment
Question by:compdigit44
  • 6
  • 5
11 Comments
 
LVL 119
ID: 41769336
this is because of VMware vendor strings.

 vSphere 5.0 vDS vendor label is Vmware.

vSphere 5.5 vDS vendor label is VMware Inc.

the mismatched string means the migration destination is not compatible.

(effectively VMware Quality Control failure!)

simply changed, so ALL is well.

see here

Virtual machine migration using vMotion fails with the error: The destination distributed switch has a different version or vendor than the source distributed switch (2126851)
0
 
LVL 19

Author Comment

by:compdigit44
ID: 41769357
Thank you very much!!!
 
What is the impact on other vDS switch in my VMware datacenter since I have some ranging from version 4.1 to 6
0
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 41769419
You will need to ensure they all have the same Vendor ID.

and anything older than 5.5 is no longer supported from TODAY! (24th August 2016).

HORAAH! no more 4.x, 4.1, 5.0, 5.1 ....

see here

End of General Support for vSphere 5.0 and vSphere 5.1 (2145103)

So it's about time, you did something about anything older than 5.5.

To discuss such things is a no brainer!

otherwise we will be complaining why I cannot vMotion from our Production ESX 2.5.4 to vSphere 6.5, 7.0 or 8.0!
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
LVL 19

Author Comment

by:compdigit44
ID: 41769579
I totally understand... I have to read the article you posted in more detail but can you do this "per vDS" instead of doing them all at once..
0
 
LVL 119
ID: 41769811
the change is needed to make vMotion happy without doing it you will not be able to vMotion between different hosts versions or vds versions.
0
 
LVL 19

Author Comment

by:compdigit44
ID: 41770214
Will the change you recommend also fix the other error message I am getting as well... ""Change the network and host of a virtual machine during vmotion is not supported on the "source" host""
0
 
LVL 19

Author Comment

by:compdigit44
ID: 41770247
I do not think I will be able to do the change you recommended. I do know 5.1 is out of main stream support hence why I am moving all VM's to a new cluster running 6.0 then shutting down the old host.
0
 
LVL 119
ID: 41770462
Yes, it should fix all the issues, again incorrect vendor id.
0
 
LVL 19

Author Comment

by:compdigit44
ID: 41773722
Sorry to the delay in getting back to you. I ended up called VMware support and from what they told me I will not be able to vmotion between vDS switch is the source is 5.1 and destination is 6.0. I would need to get the source host(s) to 5.5 update 3B in order for this to work...
0
 
LVL 119
ID: 41773730
because they NO LONGER support 5.1!

and would like you to be on supported platform that they will entertain you on!
0
 
LVL 19

Author Comment

by:compdigit44
ID: 41773798
LOL... true.....

Thanks Again for all of your help
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When converting a physical machine to a virtual machine using VMware vCenter Converter Standalone or vCenter Converter Enterprise, if an adapter type is not selected during the initial customization the resulting virtual machine may contain an IDE d…
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …
This Micro Tutorial walks you through using a remote console to access a server and install ESXi 5.1. This example is showing remote access and installation using a Dell server. The hypervisor is the very first component of your virtual infrastructu…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question