MicrosoftMicrosoftvaibhavkale thank you for the interesting article.
Would like to bring some questions and other examples from customers.
I understand the problem when using DHCP and reservations, to prevent static addresses where possible, in a Failover Cluster. Is this a possible problem or does the dynamic MAC remain the same?
And when it doesn't? Believe this is when VMs are stopped and started on another Hyper-V node.
But what about the defaults?
Every Hyper-V host has a unique MAC Address Pool by default. What's are reasons to change things and not using dynamic Mac addr.?
There are customers that tend to change this Address Pool and make it the same on each node. This could be sufficient on the number of unique MAC addr., still using dynamic MAC addr. but ever wondered if this is a good idea and possible down side.
Couldn't recommend that.
Another customer doesn't use dynamic MAC addr. at all but try to mimic the VMs IPv4 in the Mac address.
So like
00-00-10-01-00-15
10.1.0.15
Or
00-00-AC-10-00-FD
172.16.0.253
To gain more confidence about duplicates, which cause catastrophic results, especially when switched, the first two could still match the Microsoft MAC vendor ID.
Thank you for time and replies.
