I'm on a trial with the MR52 APs and they worked great with DHCP but the building I'm wanting to use these in has everything statically assigned. I changed the IP settings in the dashboard and tried to connect the APs at that location but the lights kept doing the rainbow color change like it was looking for the controller. I tried the steps listed under this article to try and access the AP locally but didn't have much luck:
I don't have an AC adapter so the APs were being powered via PoE. Tried factory resetting the APs and unplugging one but didn't see the default SSID being broadcasted. Also tried connecting to meraki-<MAC ADDRESS> with no luck there either... Anything else I could try to access this AP locally so I can see what's going on?
Solved! Go to Solution.
I have to ask: is there any possible way to put a DHCP server on a vlan there for these APs? Better practice is to use DHCP with reservations.
Is the AP accessible if you take it back to a location with DHCP?
@Nash is he able to get into the local status page without configuring the AP? I forget. He might be able to set a static there.
No, it's at a detention center and the director requires all of our equipment to have static IPs. But when the APs are used on our network at our main office they work fine. I can't tell if it's taking the IP though when I change it to static as it's not reflected in the dashboard but it does stop communicating with the cloud so I'm assuming the IP is sticking but soon as I take it over to the other building I'm not seeing it in the cloud anymore.
All gateway MR52s and MR53s (An AP with Ethernet connections to the LAN) must be assigned routable IP addresses. These IP addresses can be dynamically assigned via DHCP or statically assigned.
When using DHCP, the DHCP server should be configured to assign a static IP address for each MAC address belonging to a Meraki AP. Other features of the wireless network, such as 802.1X authentication, may rely on the property that the APs have static IP addresses.
Static IPs are assigned using the local web server on each AP. The following procedure describes how to set the static IP:
Not sure if you solved your issue but I have been successful setting the APs to static IPs. The best way to set the static is not to enter a VLAN, leave it blank, I generally use Google DNS servers which should allow the AP to reach the internet.
I see. One could have a dhcp server with reservations for each available IP, but arguing this is... difficult... when people are stuck on statics. Especially when they have confused static IPs with security measures.
Have you tried setting it with a static IP valid for the building w DHCP? To ensure that your process is correct? As @kYutobi notes, you’ll need to set it via local status.
Doing it in the working building ensures that your AP will be able to pull a config easily if you need to reset it again.