For instance, one of my VM's is a web server, I need its IP to not change. I use DHCP address reservations to control my server's IP addresses.
During normal operation, the IP address doesn't change because the MAC address doesn't change. If however, that VM fails and I have to bring a replica online, it will have a different MAC address (because vCenter "helps" by changing the MAC address to something else when a duplicate is detected). DHCP will not provide this new MAC address the same reserved IP as before, which breaks my requirement of the IP not changing.
Is it simply a matter of bad practice to use DHCP reservations in this manner? If so, even with static IP addresses, if the replica VM re-enumerates the NICs, finds a "new" one (new MAC), won't it orphan the first NIC AND the associated static IP address?
MAC addresses WILL change, so DHCP reservation for IP assignment seems out. NICs might? get re-enumerated, so static IP assignment seems out...
Is there a best practice for ensuring that a replica, in a disaster situation, will have the same IP as it's originating VM?