Cisco Cisco 2000 Series Wireless LAN Controller Guia De Resolução De Problemas

If you debug on a specific client MAC address, this appears:

*May 19 13:14:13.432: 00:40:96:b4:8b:ff 

If the client does not honor the status code 17, and tries again on the original AP, this appears:

*May 19 13:14:14.042: 00:40:96:b4:8b:ff 

You can issue this command in order to verify the load−balancing configuration:

(Cisco Controller) >show load−balancing

Aggressive Load Balancing........................ Disabled

Aggressive Load Balancing Window................. 10 clients

Note: When you use Cisco 7921 and 7920 wireless IP phones with controllers, make sure that aggressive
load−balancing is disabled for each controller. Otherwise, the initial roam attempt by the phone can fail,
which causes a disruption in the audio path.

Here are a few additional things to consider:

A client that has already been authenticated and associated is never removed from the system as a
result of aggressive load−balancing. Load−balancing only happens at the association phase.

• 

This feature is implemented on a per−controller basis. This means that APs in the same geographic
area must all logically connect back to the same WLC if Aggressive load−balancing is desired.

• 

Load−balancing will not take place if:

The threshold load−balancing window is not exceeded. That is, if the AP requested by the client is a
valid candidate AP (current user count <= window + min users).

• 

The client sends a reassociation request to an AP which it was associated to previously.

• 

• 

• 

Contacts & Feedback | Help | Site Map
© 2014 − 2015 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of
Cisco Systems, Inc.

Updated: Aug 01, 2011

Document ID: 107457