vmware 5.5 - can't migrate VM between two hosts

I'm trying to migrate a VM from one host to another and they are connected to the same Distributed Switch. However I can't migrate, I get the error that the "The Network interface 'Network adapter 1' uses network "test-dvSwitch1-lacp', which is not accessible.".
The port groups are named the same across the hosts, so I'm not sure what it could be.
It does this no matter which network I make the VM a part of.    
At this point I can change the VM's network to "VM Network", migrate it to other host, then set it back to the desired vLAN, power on, and good to go.    
I just don't know why I can't keep it on the same vlan during the migration if it exists on both hosts...
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.

Zephyr ICTCloud ArchitectCommented:
Well, the only thing I can say is that, if you're absolutely sure everything is the same on both port-groups and the hosts are connected to the same dvSwitch then it should work ...

Maybe go over all the settings with a fine tooth comb make sure there are no differences, disable things like promiscuous mode and such ...
garryshapeAuthor Commented:
Yeah I'm not sure. So go over the settings on the hosts?
garryshapeAuthor Commented:
So I removed one of the hosts from the vSphere Distributed Switch, then went to migrate from another host on the switch to the host I just removed, and this time I don't get an error but just a warning:    
"Network interface 'Network adapter 1' uses network 'Distributed Virtual Switch (uuid: (uuid: b7 41 06 50 ee 92 a7 45-ae f6 68 12 44 67 0f 5e), which is not accessible. But the NExt button is clickable this time.    
And the "Next" button is clickable at the migrate wizard, whereas before it wasn't clickable.

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
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

garryshapeAuthor Commented:
Ok after I removed, I re-added the host to the switch choosing the host and its only available NIC. Then it let me assign port group and I did so, and also specified the 3 VM's on the host to the destination port group, now I think the error is resolved, and the VDS Status column shows "Up".
Zephyr ICTCloud ArchitectCommented:
Ok, sometimes these uuid's can have some issues I've learned, if they don't match up, maybe something somewhere got screwed up somehow...

Test a few vmotions and make sure no more errors happen ... case closed ;-)
garryshapeAuthor Commented:
Ok I think it's good, still checking though.
I can migrate between both hosts.
What I had done after my last step was migrate the Management Netowrk VM Kernel out of the Distributed switch, it was sitting in a specific port group. I migrated it back to the vSwitch0 and I think that may have fixed the final thing.
garryshapeAuthor Commented:
Only issue I have now is occassional VM won't power on getting the same network not accessible error.    
Workaround apparently on these are two change to VM Network, powe r on, then change network back to the preferred network while it's on and it picks up the new network setting. I can apparently reboot it from the console leaving that setting...so not sure why powering on from a power off state would cause that error.
Zephyr ICTCloud ArchitectCommented:
I'd have to take a look at the network setup, it's getting hard to follow :-)

You could start by leaving the vmkernels on standard vswitches for now and try to get it all working smoothly before moving them to distributed vswitches ... If feasible of course.
garryshapeAuthor Commented:
Well I think at this point a support call with VMWare should help me finish up the last lap

I think on the last issue it's a matter of removing the network card then re-adding it
Zephyr ICTCloud ArchitectCommented:
That sometimes can help yes, make sure you're (almost always) using the vmxnet3 type vnic (if you're not talking about the physical ones).
garryshapeAuthor Commented:
So vMotion kernels should be on the standard vSwitches?
Zephyr ICTCloud ArchitectCommented:
No, I was just saying that for troubleshooting purposes, sometimes it's better to start a new with a simpler setup and evolve from that.
garryshapeAuthor Commented:
Ok I'm still learning the product so trying to figure out the differences and best practices for them, what kernels are, etc.
PberSolutions ArchitectCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

-- garryshape (https:#a40898444)
-- Zephyr ICT (https:#a40898241)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

Experts-Exchange Cleanup Volunteer
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.