Network inside VM fails after live migration hyper-v

Hi,
I have replaced one of two cluster nodes (different hardware) and have issue with live migration.
When i live migrate machine to new host network fails and that machine cant ping other machines. If i restart that machine on new host it strarts to work, if i live migrate it to old host, it works.

Windows Server 2012 R2, old host is using Broadcom BASP for teaming, new host is using Windows teaming
New host also gaves me "MAC conflict: A port on the virtual switch has the same MAC as one of the underlying team members on Team Nic Microsoft Network Adapter Multiplexor Driver" and cant get rid of it, changed both Team and hyper adapter MAC, still have the error, so i revert it all back...
oompaloompaAsked:
Who is Participating?
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.

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Is the vSwitch on each node named the same?
0
Anand PandyaCommented:
I would request you to check the MAC address of VM in hyper V Manager by right clicking the machine and checking it properties
0
oompaloompaAuthor Commented:
- name of vSwich is the same
- MAC address of the VM after live migration is from pool of OLD host
- MAC address after reboot on new HOST is from the pool of new host
- also i'm using SCVMM 2012 for LM
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Go Premium
oompaloompaAuthor Commented:
vm on new host cant ping vm on another, both has access to other resources
0
oompaloompaAuthor Commented:
Broadcom again, after updating network drivers and using Broadcom teming instead of native MS everything looks fine.
i suppose that it was a driver issue and not MS teaming, but i haven't any more time to test it.
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
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
I suggest using Windows teaming and not BASP.

Also, disable VMQ on each Broadcom Gigabit port.

We avoid Broadcom in our solution set when possible.
0
oompaloompaAuthor Commented:
Broadcom drivers update
0
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
Hyper-V

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.