Meraki MR33 Bridge Mode Not Working

[thi4go_p]

Hello,

I'm facing issues for activate my meraki MR33 as bridge mode. I've followed meraki site instructions but still don't working. Client don't get any IP address.

Below is the Switch configuration. I've utilized the same config from my Aironet APs (that works very well).

Don't know if need a special config or a missing something. 

Regards,

[Adam]

You have DHCP running on VLAN 10?  You may want to do a capture on the switch port to verify if you see the DHCP requests etc.  Also what are you trying to accomplish with those port-security settings?  Just trying to limit the number of people that can connect?

[thi4go_p]

Hi Adam,

Thanks for your reply. Yes, I've DHCP running on VLAN 10 (and also on VLAN 20). I've other two APs (Aironet not Meraki) connected utilizing the same configuration, and DHCP works normally, but on Meraki not.

About the port-security. Yes, the intention is limit the maximum users at the same time. I've tried without the port-security, but no luck too.

Checking on Meraki, I can see that is really occuring an issue with the DHCP.

I'll try capture the packets, as you suggested. Also, try enable the DHCP server directly on switch to see what happen.

Thanks.

[Adam]

One other option may be to set up a different port to connect to the AP as a test.  Keeping it as simple as possible.  Something like this although I don't know what your native VLAN is.

interface fa1/0/6
switchport mode trunk
switchport trunk encapsulation dot1q
switchport trunk native vlan ?
switchport trunk allowed vlan 1,10,20

[Pdriver]

Hello
You could also try initiate a packet capture to monitor the DORA's between the AP and the host and from the switch.

Switch:
access-list 100 permit ip host 0.0.0.0 host 255.255.255.255
debug ip dhcp server packet
debug ip udp
debug ip packet detail 100

(NOTE: - This is my very first post on this community - coming over to the dark side from CSC)

res
Paul

[thi4go_p]

Hi All,

The issue was solved. I've changed to a different VLAN (11,21 instead 10,20) and worked perfectly.

Regards,

Thiago

[Adam]

Strange that makes me wonder if there isn't something upstream causing the VLAN 10,20 issues.