When the LAG configuration is updated on a Cisco WLC, which additional task must be performed when changes are complete?

Cisco WLCs are architected such that significant network interface configuration changes, particularly those involving LAG, necessitate a full system reboot to properly initialize the new port bundling and forwarding logic.

Flushing MAC addresses from the WLC is not the specific action required to apply a LAG configuration change; a reboot is needed for the underlying network interface re-initialization.

Simply re-enabling WLC interfaces is insufficient for applying LAG configuration changes; the system requires a full reboot to properly re-initialize the aggregated link.

Re-associating the WLC with access points is a consequence of a WLC reboot or network interruption, but it is not the direct action needed to apply a LAG configuration change.