We have a variety of devices in our site that show a really long hex value in the UniqueID field in the dhcp console. When IPAM discovers the nodes via SNMP it retrieves the correct MAC Address but then when it does the dhcp server scan, it cannot identify the correct MAC so all it does is truncates the last 12 characters of the hex value and sets that as the device's MAC Address. This results in a false positive IP conflict in the IPAM console. I submitted a case with Solarwinds support but they couldnt figure it out and just said to hide the conflict. That's a fine workaround if you only have a couple devices but recently, I started noticing some VMware VMs exhibiting this same behavior as well. Seems like a bug in the software. Maybe IPAM should be scanning the dhcp logs and trying to grab the MAC that way instead of relying solely on the uniqueID field in the dhcp console to report false information.
