Cisco WLC 5508 – Understanding HA Licensing

I don't have anything on 7.2 still so I can't give you a definitive answer on your question. However, what I can say is that if you take the letter of the documentation as law and presume that you cannot combine FlexConnect and Local ACLs on a single WLAN, and you really don't want to create multiple WLANs, what I know you can do is use central switching on FlexConnect APs to apply local ACLs.

We actually do this for our Web Authenticated guest network. Yes, traffic on this network must transit back to the location of the WLC, but it was the best solution for us at the time of implementation.

Yes, the 2504 supports LAG in v7.4. Your first guide refers to v7.0.116.0 and the second guide written in 5/2013 implies v7.4. Enabling LAG requires a reboot of the WLC and has limitations similar to the 5500.

When LAG is enabled on a WLC, the WLC forwards data frames on the same port on which they were received. The WLC relies on the neighbor switch to load-balance traffic across the EtherChannel. The WLC does not perform any EtherChannel load-balancing on its own.

Limitations/Restrictions, same as 5500 but note 5508 doesn't have ap-manager inf's:

• LAG requires the EtherChannel to be configured for 'mode on' on both the controller and the Catalyst switch.
• The load-balancing method configured on the Catalyst switch must be a load-balancing method that terminates all IP datagram fragments on a single controller port. Not following this recommendation may result in problems with access point association.
• The recommended load-balancing method for Catalyst switches is src-dst-ip (enter the port-channel load-balance src-dst-ip command).
• With LAG, all of the controller ports need to connect to the same neighbor switch. If the neighbor switch goes down, the controller loses connectivity. With multiple AP-manager interfaces, you can connect your ports to different neighbor devices. If one of the neighbor switches goes down, the controller still has connectivity. However, using multiple AP-manager interfaces presents certain challenges when port redundancy is a concern.
• Port mirroring is not supported when link aggregation (LAG) is enabled on the controller.