Dear all,
we have a strange issue in our virtualization environment. Our non-clustered HyperV hosts suddenly appear with MAC conflicts. One day one host does have that issue, we resolve it, and the other day it's another HyperV host having MAC conflicts.
This is what it looks like:
Get-NetAdapter | sort-object MacAddress | ft name,MacAddress -autosize
Output:
name MacAddress
---- ----------
NIC1 14-18-77-45-76-02
CORE 14-18-77-45-76-02
vEthernet (VMNet) 14-18-77-45-76-03
NIC2 14-18-77-45-76-03
NIC3 14-18-77-45-76-04
NIC4 14-18-77-45-76-05
SLOT 2 Port 1 A0-36-9F-88-FA-FC
SLOT 2 Port 2 A0-36-9F-88-FA-FD
SLOT 2 Port 3 A0-36-9F-88-FA-FE
SLOT 2 Port 4 A0-36-9F-88-FA-FF
After changing MAC addresses for adapters NIC1 and NIC2 and a reboot, the VMs will be available again and services are back to normal.
This is really strange behavior. Those HyperV hosts are not newly installed. They're running for couple of weeks already, operational. And I wonder why in hell MAC addresses change suddenly.
It really does happen suddenly as users working on terminal servers are being kicked due to unavailability of VMs because of that.
Any ideas?