We have been using DHCP Option 82 on our 1k and 2k equipment for a long time and it works great with out Mikrotik routers and Sonar for attaching IPs and customer routers to our billing system. We launched a 3000 AP (with 300 SMs) about 6 months ago and have been having Option 82 and MAC address issues in Sonar ever since. The issues appear to be directly related to the 3000AP or the 300 SMs. Is anyone out there using Sonar as a billing system and using DHCP IPs on your management interface for your SMs with a 3000AP and 300 SMs?
Cambium, any code differences in how Option 82 is handled on the 3000 series? We are running 4.3.1 firmware on all devices (been the most stable so far).
One thing you can do is take a packet capture on a 2000 AP and compare it to a 3000 AP, just to see what it's doing. It's fairly easy in mikrotik to set it up, and you can reboot a EPMP client to cause it to trigger a lease for the capture.
I am finding an issue with MAC address assignments that might be causing this. With all of our 1000/2000 sites (and Mimosa and UBNT), the MAC address in the DHCP server that is assigned an IP address for the radio is the WIRELESS MAC. For Option 82 Agent Remote ID, the WIRELESS MAC is also used.
For the 3000 site (with 300 SMs), the ETHERNET MAC address is assigned an IP address but the Agent Remote ID is the WIRELESS MAC. They are different. This is throwing off Sonar and also seems to be non-standard operation.
Also, though maybe not related, for all of our 1000/2000 SMs, the "active host name" in the DHCP server is the system name for the radio (we use customer address for the system name). For the 3000 SMs, there is no "active host name" sent from the radio.