Meraki AP guest ssid not taking DHCP from correct DHCP server

[CameronR]

We have recently installed some new Meraki APs at one of our locations. We are running two SSID one internal and one guest. The internal SSID is leasing as expected from our 2016 DHCP server. The guest SSID however is no longer leasing IPs from the DHCP server on our 9300 core switch, but from the internal scope on our 2016 server.

Trunking the ports on the LAN has not had any effect and assigning VLAN tagging has resulted in users losing access. Either for the internal or guest SSIDs.

We were initially using an HA pair of Cisco 3504 WLCs for wireless but migrated to Meraki. I've reviewed the WLCs and the AP config for the previously deployed solution and not noticed anything overly different that should be causing this issue. 

Wireless isn't my specialty and I was hoping for some suggestions on how best to resolve this issue.

Thanks in advance!

[Mloraditch]

Presuming you are handing the ssids onto separate vlans, the most likely reason for something like this is vlans being crossed somewhere. A Guest Vlan port is connected over to an internal vlan port and it has not been detected as a loop.  The other thing I've seen is when Windows DHCP servers are not on access mode ports with only a data vlan assigned sometimes they will essentially leak DHCP onto other VLANs so make sure the server port is not a trunk.

[rwiesmann]

Are you using Vlan 1 for the guest SSID?

[CameronR]

I believe so I reviewed the template used and seen it was set to a single VLAN and on 1 default.

I added both of my VLANs and tagged guest to the appropriate VLAN ID. Validating the change now.

[rwiesmann]

well, and I guess ssid guest is on vlan 1 and you tagged it on the ssid config to the vlan 1, correct?

If so, change it ones to default with vlan 0

I had lately some test installation, where used vlan 1 just to be simple...and realized that if I use vlan 1, which ist also the native vlan, I do not have to give along the vlan.

or the other way arround, if I tag here with the 1...DHCP did not work.

I think it's worth a try...and I am intrested in your feedback.

[CameronR]

I've configured the VLANs and  DHCP to relay to the Cisco 9300 providing DHCP for the guest network. I've also configured a vlan for our corporate network but haven't applied vlan tagging as it's caused issues in the past. Validating now.

[CameronR]

Addresses are still leasing from the production VLAN. For context let's say guest is in 169.254.x.x and our production vlan is in 10.193.x.x range.

The guest vlan is still leasing from the incorrect dhcp scope for production and not leasing from the dhcp scope for guest (169.254.x.x). 

Our switch ports are access and not trunk. I've tested this and it nor VLAN tagging seems to have any effect beyond disrupting our users access to the internet or internal resources.