Chapter 9 Wireless
Table 42 Configuration > Wireless > Load Balancing (continued)
LABEL | DESCRIPTION |
Disassociate | Select this option to “kick” wireless clients connected to the AP when |
station when | it becomes overloaded. If you do not enable this option, then the AP |
overloaded | simply delays the connection until it can afford the bandwidth it |
| |
| requires, or it shunts the connection to another AP within its |
| broadcast radius. |
| The kick priority is determined automatically by the |
| series AP and is as follows: |
| • Idle Timeout - Devices that have been idle the longest will be |
| kicked first. If none of the connected devices are idle, then the |
| priority shifts to Signal Strength. |
| • Signal Strength - Devices with the weakest signal strength will |
| be kicked first. |
| Note: If you enable this function, you should ensure that there are |
| multiple APs within the broadcast radius that can accept |
| any rejected or kicked wireless clients; otherwise, a |
| wireless client attempting to connect to an overloaded AP |
| will be kicked continuously and never be allowed to |
| connect. |
|
|
Apply | Click Apply to save your changes back to the |
|
|
Reset | Click Reset to return the screen to its |
|
|
9.5.1 Disassociating and Delaying Connections
When your AP becomes overloaded, there are two basic responses it can take. The first one is to “delay” a client connection. This means that the AP withholds the connection until the data transfer throughput is lowered or the client connection is picked up by another AP. If the client is picked up by another AP then the original AP cannot resume the connection.
For example, here the AP has a balanced bandwidth allotment of 6 Mbps. If laptop R connects and it pushes the AP over its allotment, say to 7 Mbps, then the AP
120 |
| |
| ||
|
|
|