Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.
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...
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...
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
I would request you to check the MAC address of VM in hyper V Manager by right clicking the machine and checking it properties
- 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
- 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
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.
i suppose that it was a driver issue and not MS teaming, but i haven't any more time to test it.
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.
Also, disable VMQ on each Broadcom Gigabit port.
We avoid Broadcom in our solution set when possible.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial