topic Re: CAPWAP and LAG in Wireless

CAPWAP and LAG

DAVIES604 — Mon, 05 Jul 2021 19:20:18 GMT

Hi,

Can someone answer whats probably a simple question please, I can't quite find an answer that I'm happy with and I've not really got much WiFi experience.

If I have an AP with a single physical connection to a switch, and the path from the switch to the WLC involves aggregated ports along the way, and the WLC is configured for LAG to it's neighbour switch, will a separate tunnel be created between the AP and WLC for each client/connection to utilise the full potential bandwidth, or will connections initiated from the AP always use the same tunnel connection?

Thanks.

Re: CAPWAP and LAG

Scott Fella — Wed, 29 Jul 2020 17:40:19 GMT

I think you need to just look at how LAG works alongside etherchannel mode on. Basically its source destination ip that will determine what port on the switch and WLC the traffic will be placed on. This has nothing to do with CAPWAP as the AP and WLC will create a tunnel again based on the etherchannel mode on. Same thing for client traffic src-dst-ip.

Re: CAPWAP and LAG

DAVIES604 — Wed, 29 Jul 2020 21:33:01 GMT

Hi Scott, thanks for the reply. I read a Cisco doc that stated all traffic including client traffic is sent down the capwap tunnel, my question really was, which I think you’ve answered, is does a new tunnel get created each time and so can make use of the load-balancing across etherchannels along the path, in other words does a single AP create multiple tunnels for all connected clients? Thanks

Re: CAPWAP and LAG

Scott Fella — Wed, 29 Jul 2020 23:25:19 GMT

No... the Capwap is a single connection from ap to controller. This is transparent to any user traffic.

Re: CAPWAP and LAG

patoberli — Thu, 30 Jul 2020 09:26:33 GMT

Also read into Flexconnect if you expect client traffic to become an issue (it rarely is).

Re: CAPWAP and LAG

Rich R — Thu, 30 Jul 2020 15:52:18 GMT

specifically flexconnect LOCAL SWITCHING 🙂