Cluster virtual MAC addresses. When a cluster is operating, the FGCP assigns virtual MAC addresses to each primary unit interface. HA uses virtual MAC addresses so that if a failover occurs, the new primary unit interfaces will have the same virtual MAC addresses and IP addresses as the failed primary unit. Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Microsoft Failover Cluster Virtual Adapter Change Mac Address On Roku Devices
Its not a secret that my Linux experience is pretty limited, please keep this in mind as I frame this issue.
I've setup a VM webserver using CentOS, and generally speaking it's going ok. There's one major problem I'm having, every time I move the VM to another node, the process appears to generate a new MAC address from the Virtual Switch Manager's MAC Address Range...I had never really paid any attention to this in the past as it was happening in the background without any noticeable effect on a Windows based OS that had a statically assigned address... However, with CentOS, each time a new MAC is assigned to the VM, it creates another interface (eg: eth1, then eth2, etc.), and requires reconfiguring the adapter with the new MAC address. Move the VM again to another NODE and voila, same issue.
I'd like to have the MAC address follow the VM after its been assigned when the Network Adapter is created for the VM in Hyper-V. I can also see how the need for these MAC ranges is necessary so you don't end up with 2 NIC's that have the same MAC address.
Can anyone suggest how to best approach this?