[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Unable to vmotion between vDS Switch in vCenter 6.0 Web Interface

Posted on 2016-08-24
11
Medium Priority
?
938 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 5
11 Comments
 
LVL 123
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 20

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 123

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 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
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
LVL 20

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 123
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 20

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 20

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 123
ID: 41770462
Yes, it should fix all the issues, again incorrect vendor id.
0
 
LVL 20

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 123
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 20

Author Comment

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

Thanks Again for all of your help
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

If we need to check who deleted a Virtual Machine from our vCenter. Looking this task in logs can be painful and spend lot of time, so the best way to check this is in the vCenter DB. Just connect to vCenter DB(default DB should be VCDB and using…
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 delpoy the vCenter Server Appliance and how to configure its network settings Deploy OVF: Open VM console and configure networking:
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…

649 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