Cisco WLC3502 with Meraki setup

Solved
Tarmahmood1
Getting noticed

Cisco WLC3502 with Meraki setup

Hi,

We are inprocess of planning to setup Branch A office to meraki from Cisco. we have Cisco wlc 3502 in Branch A office and APs in Branch B are connected to it.

 

my question is will Cisco WLC3502 connected to MS120 will work same as it is working now(as shown in figure) or should i connect to Cisco 2960 switch and then 2960 switch is connected to MX appliance directly or to any other Meraki switch. My intention is that even if i want to change to Meraki setup the APs in Branch B still connects to WLC in branch A and works as it is?

 

Otherwise i have to make one of Air-AP WLC and connect all APs to it in Brach B office itself?

 

Thankyou.

 

Tariqmahmood_0-1674739075338.jpeg

 

1 Accepted Solution
rhbirkelund
Kind of a big deal
Kind of a big deal

As long as you configure the ports on your MS120, in the same way as your 2690 switch (i.e. trunk/access port type, vlan, etc) I see no reason as to why it should'nt work. Assuming that all Layer 3 functionality is on the branch MX, the MS120 will only act in Layer 2.

 

Remember that Meraki is Cloud based, so all configuration of the MS120 switch will be done on the Meraki Dashboard, contrary to your Catalyst 2960 switch.

 

In regards to the CAPWAP tunnel from Branch A to Branch B, you might need to look into Forwarding ports udp/5246 and udp/5247 to the WLC, assuming you are routing the CAPWAP tunnel over the internet (which I wouldn't recommend). If you have a VPN tunnel between MX at Branch A and ISR4400 at Branch B, you should be ok.

 

LinkedIn ::: https://blog.rhbirkelund.dk/

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

All code examples are provided as is. Responsibility for Code execution lies solely your own.

View solution in original post

6 Replies 6
rhbirkelund
Kind of a big deal
Kind of a big deal

As long as you configure the ports on your MS120, in the same way as your 2690 switch (i.e. trunk/access port type, vlan, etc) I see no reason as to why it should'nt work. Assuming that all Layer 3 functionality is on the branch MX, the MS120 will only act in Layer 2.

 

Remember that Meraki is Cloud based, so all configuration of the MS120 switch will be done on the Meraki Dashboard, contrary to your Catalyst 2960 switch.

 

In regards to the CAPWAP tunnel from Branch A to Branch B, you might need to look into Forwarding ports udp/5246 and udp/5247 to the WLC, assuming you are routing the CAPWAP tunnel over the internet (which I wouldn't recommend). If you have a VPN tunnel between MX at Branch A and ISR4400 at Branch B, you should be ok.

 

LinkedIn ::: https://blog.rhbirkelund.dk/

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

All code examples are provided as is. Responsibility for Code execution lies solely your own.
alemabrahao
Kind of a big deal
Kind of a big deal

Yes WLC, does not support LACP, but you can use a backup port configuration. 😁

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Tarmahmood1
Getting noticed

@alemabrahao @GIdenJoe @KarstenI @rhbirkelund Thank you for your response. I will get back with outcome once it is implemented. hopefully end of feb-2023

alemabrahao
Kind of a big deal
Kind of a big deal

You can connect directly on MS120, It will work as expected. 

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
KarstenI
Kind of a big deal
Kind of a big deal

There is one thing that will not work:

If you now have a LAG between the 3504 and the 2960, this must be removed and configured for individual interfaces as the LAG implementation on the WLC and the MS switches is not compatible.

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.
GIdenJoe
Kind of a big deal
Kind of a big deal

Or you could simply connect 1 interface so you don't hit the lag thing.

Then you don't have to touch the configuration on the WLC 😉

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels