I work for a smallish organization and we have a network that is locked down that we use for managing devices, however we don't run a DHCP server on it. The MR36 unlike the MR32 and MR33 requires a network with a DHCP server for internet access and management of the access points. Trying to double up using an already established network you are using for wifi clients for example causes connectivity issues for the wifi clients.
In the past we would configure the meraki ap on a network with a DHCP server and change the VLAN and network settings on the AP to match the statically assigned ip we wanted for the device on our management network. When we did that it worked just fine as shown below on an MR32.
However not so with the MR36, setting the VLAN's for the AP's worked the same but when I switched it back to the network without DHCP server the device became unavailable along with not routing traffic properly. The AP goes offline. Shown below VLAN X is a network where devices are statically assigned, and when the meraki switch has that VLAN setup for the AP the AP cannot connect, and the dashboard times out.
Switch Settings
Dashboard
But when I change the VLAN to one with a DHCP Server (VLAN A) the dashboard becomes responsive again.
To resolve the issue what I had to do was create a Management AP network for the Meraki AP's that has a DHCP Server. So instead of using VLAN X I have it using VLAN Y for the native VLAN. When I tried to use a network for double duty such as VLAN A, your wifi clients cannot connect and their mobile devices give a connection error.
On my firewall I created a new network (VLAN Y as described above) and I put the VLAN throughout where it is required, and will use that as the native VLAN and management network for the Meraki APs.
