How to configure two WLCs to load balance the Lightweight Access Point
Information on the current AP load, which is defined as the number of APs that are joined to the WLC at the time
The AP capacity
The number of wireless clients that are connected to the WLC
The AP then attempts to join the least-loaded WLC, which is the WLC with the greatest available AP capacity. After an AP joins a WLC, the AP learns the IP addresses of the other WLCs in the mobility group from its joined WLC.
Subsequently, the AP sends LWAPP primary discovery requests to each of the WLCs in the mobility group. The WLCs respond with a primary discovery response to the AP. The primary discovery response includes information about the WLC type, total capacity, and current AP load. As long as the WLC has the AP Fallback parameter enabled, the AP can decide to change over to a less-loaded WLC.
Once an AP joins a controller, it only leaves the currently joined controller for a limited number of reasons. For that reason, this load balancing algorithm is only an approximate load balancing algorithm unless you manually define a primary controller for each AP.
Note: Once an access point joins a controller you can assign Primary , Secondary , Tertiary controller . Though it is a manual process it is the best way to Load balance Access Points.
From the GUI, click the Wireless tab in the menu at the top of the window, select the AP from the list of AP's that are registered to the WLC, and click Detail beside the AP.
The All AP's > Details window appears.
In this window, define the primary, secondary, and tertiary controllers.
Note: Define only system names under the primary, secondary, and tertiary controller name fields. Do not enter the IP address or the MAC address of the controller in these fields.
Note: This example does not add a tertiary controller name because there are only two controllers.
Configure the Fallback Feature on WLC
The last step is to configure the Fallback feature on the controller. This feature ensures that the AP switches return to the first WLC when the WLC that comes back on line. Complete these steps:
From the GUI, choose Controller > General.A list of options appears on the General screen.
For the AP Fallback option, choose Enabled from the drop-down menu.
Click Apply.Note: It is sufficient to enable the Fallback feature on the secondary controller alone. But it is recommended to configure it on the primary WLC as well because it can be configured as a secondary controller for other access points.
After you complete these steps, the setup is configured for WLC failover. When the primary controller (WLC-1, in this case) goes down, the APs automatically get registered with the secondary controller (WLC-2). The APs register back to the primary controller when the primary controller comes back on line. AP switching between the primary and secondary controllers also affects the wireless clients associated with these APs.
In controller software release 220.127.116.11, you can configure the wireless network so that the backup controller recognizes a join request from a higher-priority access point and, if necessary, disassociates a lower-priority access point as a means to provide an available port. In order to configure this feature, failover priority must be enabled on the network and assign priorities to the individual access points. By default, all access points are set to priority level 1, which is the lowest priority level.
Note: Be aware that Failover priority takes effect only if there are more association requests after a controller failure than there are available backup controller ports.
Hello friends. I have several AIR-AP1852I-E-K9 and AIR-AP1562E-E-K9 administered centrally in a controller which is configured in one of the AIR-AP1852I-E-K9. Specifically the AIR-AP1562E-E-K9 are attached with two AIR-ANT2547VG-N antennas connected...
Good day.We have Cisco WLC 2504 with fw ver. 18.104.22.168 that already works with few access points.We purchase new AP 1815i but it has 22.214.171.124 fw ver ( newer than WLC ) All other APs, that we connect to WLC earler, was automaticly updated t...
- AP1 Model : WAP581-A-K9 V01 Serial Number: DNI2141A05W Firmware Version (Active Image): V126.96.36.199- AP2 Model : WAP581-A-K9 V01 Serial Number: DNI2141A04Z Firmware Version (Active Image): V188.8.131.52- AP3 Model : WAP581-A-K9 V01 Serial Number: DNI214...
Hi All,Need help in understanding RRM for 80 MHZ. We have channel width 80 MHz and because of this , we found channel overlapping. We set channel interval time with 10 minutes (default) and DCA set as automatic. But we are not seeing channel change h...
Greetings,I have outdated AIR-BR1310 with broken configuration. This is not about fixing it, but mostly about understanding why it works like it works. BR1310 is connected via trunk interface. Native VLAN have nothing, VLAN 26 is for wireless and VLA...