My environment consists of a Sophos UTM Firewall, two ESXi Hosts, about 12 Windows Servers running as VMs, some physical switches, physical wifi controller and APs, network printers, and client PCs.
On my Windows DHCP server, I have the scope defined as 10.20.0.1 thru 10.20.0.254. I have an IP exclusion range from 10.20.0.1 thru 10.20.0.100. I currently assign static IP addresses to my Firewall, WiFi controller, Switches and all Servers (running as VMs). All of these devices and servers are assigned IPs within the 10.20.0.1 thru 10.20.0.100 IP range. In addition to assigning the devices and servers static IPs, I also create reservations for them within my DHCP server.
I also create DHCP reservations for my network printers but I leave the printer itself configured to acquire the IP address from the DHCP server. All of my client PCs, BYOD devices, etc. simply receive an IP address from the DHCP server.
Is there any problem in creating reservations for my servers and hardware despite the fact that the IP range they fall within is excluded from the scope AND the IP address is physically assigned to the device or server? I was creating the reservation so that I had quick visibility within the DHCP server as to what server / device had a given IP address. However, I am not sure if creating these reservations could cause a potential conflict or not. The one "flaw" that I could see is that if a VM is moved or restored then the virtual NIC would be assigned a different MAC address then it had originally. Therefore, the reservation for the server would not be applied to that server since the MAC address on the DHCP reservation no longer matches the MAC address of the virtual NIC. However, the IP was assigned statically to the server so the IP would remain the same and everything would function as normal on a moved or restored VM.
Do any of you see a problem with how I am handling IPs within my network? Do you have any other recommendations of pointers?