ā11-05-2016 01:30 AM - edited ā07-05-2021 06:05 AM
I'm trying to Deploy new 2802i Access points. Supposedly they are LAG capable when plugging in both POE and AUX ports and can detect LACP etherchannels. They are connected to a 3650 POE+ switch.
For some reason they won't come up if I configure Etherchannels on my switch. When I make the etherchannel LACP, I get the error that it's not LACP capable and suspends the ports. If I do static etherchannels, the switch won't complain but the APs never join the controller because for some reason they don't seem to get an IP.
The only way for them to come up is to only have the POE port plugged in and no port channel configurations what so ever. I'm hoping to leverage both ports.
Any help is appreciated. Thanks
ā11-07-2016 04:06 PM
Are you setting this up as a standalone or lightweight AP on a WLC? If on a WLC you may need the command config ap lag-mode support enable
Cisco also recommends that the switch ports are setup in active mode as you already have and use src-dst-port algorithm.
From the WLC you can verify the AP LAG mode with show ap lag-mode
Cheers,
Ric
ā11-07-2016 05:06 PM
Thanks for your reply. I have already tried all these configurations yes. The Access points still refuse to form a LAG if I etherchannel the ports.
At this point they are working off of the POE port only. Thanks
ā11-09-2016 09:53 PM
Finally got on with TAC. Apparently LAG had to manually enabled on the access points using the command "capwap ap lag enable".
The AP will reboot and then be able to join a port channel on both POE and AUC ports. LACP came up fine.
Thanks
ā11-09-2016 09:56 PM
Thanks for coming back and posting the fix, it really helps!
ā07-06-2017 06:12 AM
Don't we need to use command on the controller "config ap lag-mode support enable <ap name>" to manually enable on the access point?
ā07-06-2017 06:41 AM
As per hesham's reply try capwap ap lag enable as well if the first command doesn't work.
ā07-06-2017 06:46 AM
So this command has to be entered on the access point by enabling ssh?
ā07-06-2017 06:49 AM
I think so, ssh or telnet. You may need to use the command debug capwap console enable to permit that command (not sure as haven't tried it).
Cheers,
Ric
ā07-06-2017 04:59 PM
We need both commands. config ap lag-mode support on the WLC, and also need to ssh into the AP and enter capwap ap lag enable.
So we'll need to enable ssh or telnet on the AP as well in order to enter those commands
On the switchport side the ports can will be in LACP port channel and the load balancing will be set to src-dst port
Thanks!
ā07-07-2017 08:39 AM
Thank you for the reply.
1. Does entering "config ap lag-mode support enable" on the WLC affects or reboots other WAPs that does not support lag?
ā02-03-2017 09:37 AM
Do not forget to set this on the connect cisco switch also:
For load balancing on the LAG ports to the AP and the controller, the switch should support load balancing on the layer 4 (L4) source and destination ports. Run the following command from the switch config mode.
port-channel load-balance src-dst-port
If one doesn't configure L4 port load balancing (for example when using a switch model which does not support this feature) then the port channel will still come up but all the traffic will go through the same port. One will not have 2 gigabits of speed but there will be redundancy.
ā12-11-2018 03:45 PM
after entering capwap ap lag enable... how does one SAVE the product so that when the AP is moved to the proper interface pair.. (power down) it remember when powered back up?
ā12-12-2018 03:16 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide