In warehouse or manufacturing environments where there are a loarge number of clients and a large number of APs (350s in our case), the 350 seems to wait until the quality of its association is really lousy before it tries to roam to another AP. With latency sensitive applications like telnet or 5250, this causes problems with session lockups and excessive battery use on the client because of too many retries.
How can we get these clients to roam more quickly when their sesion _begins_ to degrade?
The old Aironet/Telxon 2.4GHz networks were able to set ELH and other thresholds to cause more proactive roaming.
We have tried limiting cell size by power levels and/or restricting data rates, but it doesn't seem to improve.
Re: Need the clients to roam between APs more quickly
You're right, RTS & Data (I'm not looking at a console).
The retries control how many times a client and/or AP will attempt to re-transmit, and therefor how soon it will give up on the AP that it is moving away from.
The sooner it gives up on one, the sooner it will look for another, and when it looks for a new AP it will take the strongest signal.
The inverse is true as well. I've had trouble with clients roaming too quickly in a noisy environment - essentially jumping back and forth between APs so fast that both APs give up on them - where setting the retries higher solved the problem.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...