My name is John Marlin and I am with the High Availability and Storage Team. With newer versions of Windows Server and Azure Stack HCI on the horizon, it’s time to head to the archives and dust off ...
Updated Sep 24, 2020
Version 2.0
Blog Post
John Marlin EriqStern really helpful summary thanks for this article. As it mentions DHCP I have encountered the following obstacles.
Every Hyper-V has a unique MAC address range used for its virtual switches.
Assume: We have 2 or 2+ Hyper-V cluster. A VM uses DHCP MAC address reservation to obtain it's IP config.
When live migrating the VM within a cluster from node A to node B there is no change.
The VM will keep its MAC address and a DHCP MAC reservation will still work as intended.
When I restart VM on B it gets a new MAC address from the MAC pool of B causing the DHCP MAC reservation to fail.
As a workaround I tend to configure the same MAC Address pool on all Hyper-V a cluster. This might solve the problem for the VM but I wonder how this would work correctly on the Layer 2 with or without SET or LFBO. What's your stance how to deal with it?