Cisco Cisco 2000 Series Wireless LAN Controller Guia De Resolução De Problemas
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Aggressive Load−Balancing
Aggressive load−balancing on the WLC allows the LAPs to load−balance wireless clients across APs in an
LWAPP system.
LWAPP system.
This feature can be used in order to load−balance clients across LAPs on a single controller.
Aggressive load−balancing works at the association phase. If enabled and the conditions to load−balance are
met, when a wireless client attempts to associate to a LAP, association response frames are sent to the client
with an 802.11 response packet that includes status code 17. This code indicates that the AP is too busy to
accept any more associations.
met, when a wireless client attempts to associate to a LAP, association response frames are sent to the client
with an 802.11 response packet that includes status code 17. This code indicates that the AP is too busy to
accept any more associations.
It is the responsibility of the client to honor, process or discard that association response frame with reason
code 17. Some clients ignore it, even though it is part of the 802.11 specification. The standard dictates that
the client driver must look for another AP to connect to since it receives a "busy" message from the first AP it
tries. Many clients do not do this and send the association request again. The client in question is allowed on
to the wireless network upon subsequent attempts to associate.
code 17. Some clients ignore it, even though it is part of the 802.11 specification. The standard dictates that
the client driver must look for another AP to connect to since it receives a "busy" message from the first AP it
tries. Many clients do not do this and send the association request again. The client in question is allowed on
to the wireless network upon subsequent attempts to associate.
In WLC versions 6.0.182.0 and earlier, the controller only sends one association response frame with reason
code 17 to the client. If the client decides to discard the reason code 17, the client can try the same AP again
and this time the AP allows the client to complete the association.
code 17 to the client. If the client decides to discard the reason code 17, the client can try the same AP again
and this time the AP allows the client to complete the association.
If the client honors the association response status code 17, the client then attempts to associate to a different
AP. For example, if load−balancing is enabled and the load−balancing window is configured as five clients,
when a sixth client tries to associate to the AP, the client receives an 802.11 Association Response frame with
status code 17, which indicates that the AP is busy.
AP. For example, if load−balancing is enabled and the load−balancing window is configured as five clients,
when a sixth client tries to associate to the AP, the client receives an 802.11 Association Response frame with
status code 17, which indicates that the AP is busy.
Configure Aggressive Load−Balancing
Aggressive load−balancing can be configured through the CLI or the GUI on the Wireless LAN Controller.
Command Line Interface
In order to enable or disable aggressive load−balancing through the CLI, complete these steps:
Issue this command:
config load−balancing status {enable | disable}
1.
Issue this command in order to configure the window size:
configure load−balancing window <size>
Note: The size of the window can be from zero to 20.
2.
Graphical User Interface
In order to configure aggressive load−balancing through the GUI, complete these steps: