Reboot the WLC. Cisco WLC Link Aggregation is not a change that fully takes effect merely by re-enabling interfaces or clearing MAC tables. After LAG is enabled, disabled, or reconfigured, the controller must be rebooted for the new aggregation behavior to become active. Reassociating access points is not the required task; the controller platform itself needs the restart. Cisco CCNA 200-301 v1.1 Network Access expects candidates to recognize WLC operational requirements because controller changes can affect all AP and client traffic. The corrected answer is reboot the WLC. This is why LAG changes on a production controller should be planned as a maintenance-window activity rather than treated as a nondisruptive switchport-only change.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit