Unable to vmotion between vDS Switch in vCenter 6.0 Web Interface

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
LVL 21
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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)
compdigit44Author Commented:
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
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

compdigit44Author Commented:
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..
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
compdigit44Author Commented:
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""
compdigit44Author Commented:
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.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, it should fix all the issues, again incorrect vendor id.
compdigit44Author Commented:
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...
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
because they NO LONGER support 5.1!

and would like you to be on supported platform that they will entertain you on!
compdigit44Author Commented:
LOL... true.....

Thanks Again for all of your help
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.