Pertaining to DHCP on Cisco Devices:
Currently IPAM creates DHCP scope reservations and always creates these using "client-identifier 01" to identify the target MAC address. However there are several devices, most notably printers, that will not talk to a DHCP reservation using "client-identifier 01". These DHCP scope reservations have to be changed to "hardware-address 0000.0000.0000" in order for those devices to get their IP addresses. Without this support IPAM can not be used to manage reservations for Cisco DHCP servers with these types of devices on the network.
Here is an example from a Cisco DHCP server of both examples:
ip dhcp pool Res-VL123-HRPrinter
host 10.10.10.11 255.255.255.0
client-identifier 0100.0011.1122.22
client-name HRPrinter
!
ip dhcp pool Res-VL123-R&DPrinter
host 10.10.10.12 255.255.255.0
hardware-address 0000.aaaa.bbbb
client-name R&DPrinter
I believe this is being caused by network card manufacturers who do not properly format their DHCP requests. Specifically, they do not include option 61 client-identifier in their DHCP request packets. Here is a capture of a laptop performing DHCP with option 61 and a printer performing DHCP without option 61. The printer requires "hardware-address" in the DHCP setup in order to get a DHCP reservation, which has to be done on the DHCP server itself because this currently isn't an option in IPAM. I think this feature should be added.
I freely admit I may be entirely wrong and have missed something obvious, if you think I have please point it out. I have 150+ of these stubborn devices and this is a problem for us.
b-
