On my SW, I have a scope of 192.168.2.50-253 and would like to add a static IP address to the Merkai AP's from 192.168.2.10-49. I add a static arp entry of IP address and the MAC but the Meraki will not change from DHCP to this enrty.
@pendek244 in that case I would crank up a Packet Monitor and look for UDP on Port 67 and 68. With Wireshark you can check in great detail what is going on. E.g. what DHCP options the Meraki is asking for and what the DHCP is offering. Maybe the Meraki is asking for the same address over and over again and the SNWL is delivering it?
Maybe you have a typo in the MAC address?
Packet Monitor will shed some light on this.
--Michael@BWC (frequent advocate for the Packet Monitor)
Did you really mean static ARP entry rather than static DHCP?
I have seen this with Unifi APs before, and the cause was that some other device had the IP defined in the static DHCP entry - I think the Sonicwall pinged it first and because it replied, it didn't assign the IP.
Answers
@pendek244 in that case I would crank up a Packet Monitor and look for UDP on Port 67 and 68. With Wireshark you can check in great detail what is going on. E.g. what DHCP options the Meraki is asking for and what the DHCP is offering. Maybe the Meraki is asking for the same address over and over again and the SNWL is delivering it?
Maybe you have a typo in the MAC address?
Packet Monitor will shed some light on this.
--Michael@BWC (frequent advocate for the Packet Monitor)
Did you really mean static ARP entry rather than static DHCP?
I have seen this with Unifi APs before, and the cause was that some other device had the IP defined in the static DHCP entry - I think the Sonicwall pinged it first and because it replied, it didn't assign the IP.
Static ARP is definitely not the way to go as Arkwright says Static DHCP + DHCP persistence