10-10-2019 02:19 PM
I'm really confused about this. When I set Native VLAN on the upstream port to VLAN 1, the APs get a 192 address (default for that vlan on the meraki dhcp server). If I set the Native VLAN to 20, they get a 172.20 address. All of this is entirely expected and predictable.
However, when the VLAN is set to 20, while the AP gets a proper management IP address, the SSIDs stop loading.
And if that's not confusing enough, AP-FRONT has a static IP on the DHCP server in VLAN 20 which works fine and can be pinged. AP-OFFICE however is fully dynamic and gets thrown into VLAN 1, while both devices have the same configuration all the way from the SVI to the firewall port.
Screenshots below
List of APs from the perspective of my Meraki MX65 (also DHCP server for all VLANs)
AP-OFFICE configuration (device level)
AP-FRONT configuration (device level)
Trunk VLAN assignments on the upstream MX65 (APs are plugged into 11 and 12)
Solved! Go to Solution.
10-10-2019 03:29 PM
RIGHT, so I don't know why this is working now, but I changed the MGT VLAN to 1, did a full config update, set it back to 20, did a full config update.
10-10-2019 02:28 PM
And just for fun, here is some output from the other AP
DHCP Tests performed for VLANs 20-20
Passed VLANs:
20 172.20.0.0/23
Status: complete
10-10-2019 02:26 PM
Yeah, there's a whole /23 for that VLAN, and barely 40 hosts on it.
Output:
DHCP Tests performed for VLANs 20-20
Passed VLANs:
20 172.20.0.0/23
Status: complete
10-10-2019 02:22 PM
Does the DHCP pool for VLAN 20 have an available address for AP-OFFICE? If it does, could you SSH in to AP-OFFICE and run a VLAN probe on the CLI of the AP for VLAN 20? That command will be: int mgt0 dhcp-probe vlan-range 20