Hi All,
I am trying to replace my Meraki switch with C9300 but keep Meraki AP.
First step was to replicate settings and apply to the C9300, however Meraki AP isn't able to resolve dnslookup on tagged traffic but all is fine on untagged traffic. DHCP server resides on the switch with two number Vlan's linked to the AP with different SSID.
From the VLAN's gateway, which belongs to SSID's I am able to ping 8.8.8.8 but from the client on the same subnet only up to the uplink.
Sounds likely to be an issue with VLAN tagging somewhere along the line (double tagging, native tagging etc).
What's the VLAN config on the switchports between the AP and the gateway?
Are you tagging the management VLAN on the Meraki AP or is it untagged?
My gateway resides on the router, then via uplink onto the switch with vlan's allow all and the onto the switch port with native vlan 1, then allowed vlan's list is 1,1515 (represents SSID),2020 (and another SSID).
Management is untagged on meraki AP.
What VLAN tag is the SSID using?
Is the switch port that the AP plugs into configured as a trunk port, using a native VLAN that is not the same as the tag, and is the tag allowed on that port?
What is te default gateway for that VLAN? If it is the switch, does the MX have a static route pointing to the switch for that VLAN subnet?
I am using VLAN 1515 and VLAN 2020 for two different SSID's
The port where AP is plugged in is in trunk mode with the following VLAN's, 1,1515, 2020 along with native VLAN 1. Below is the extract from my switch config.
Default gateway is .1 address on the switch where switch provide DHCP services to the AP. In my case, I have static routes for VLAN 1515 and 2020 assigned on the Cisco NGFW device and pointing to the uplink address on the switch.
Just spotted that in my config VLAN 1 doesn't have any IP assignment, but not sure what has to be there. On my Cisco NGFW I have VLAN 1 with the subnet which is used for Meraki AP.
What happens if you give the switch a static IP address in VLAN1515 and 2020?
Thank you for your advise.
It appears that issues was with the switch, as ip routing wasn't enabled, and after enabling it routing start working as expected.