ā10-15-2018 07:31 AM - edited ā07-05-2021 09:18 AM
I have a single Cisco 2500 series wireless controller and approximately 30 access points that are models AIR-CAP2702E-B-K9 and AIR-CAP2702I-A-K9. The issue that I am experiencing is that an AP will hold onto an established connection even when other APs become much closer in range. There have been times where I have to physically walk out of range of an AP before it will latch to a new AP. I have been able to trick the system into handing off to another AP quicker by forcing an increase in minimum throughput required for a connection, but the AP will still hold that connection to the point where it is still clear a moderately seamless hand-off is not taking place. I am speculating that either something is misconfigured in my Mesh settings, or Mesh has not been setup to begin with. Any advice on the proper configuration of a Mesh network would be very well received.
ā10-15-2018 07:38 AM
ā10-15-2018 07:41 AM
ā10-15-2018 11:02 PM
@AngryPanda wrote:
I have a single Cisco 2500 series wireless controller and approximately 30 access points that are models AIR-CAP2702E-B-K9 and AIR-CAP2702I-A-K9. The issue that I am experiencing is that an AP will hold onto an established connection even when other APs become much closer in range. There have been times where I have to physically walk out of range of an AP before it will latch to a new AP.
This behaviour is well known (and well documented).
The issue is caused by the wireless NIC driver. If the drivers have never been updated, then what you've describe is the "norm".
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide