topic Cisco WLC based AP Mobility Problem in Wireless

Cisco WLC based AP Mobility Problem

adm.mehedi — Mon, 05 Jul 2021 13:29:27 GMT

Dear All,

Have fun with Cisco,

I'm facing some problem in mobility. Here is my scenario, I have four AP in a floor which is cover hole floor. But when I am moving from one AP to another AP, users couldn't shift in nearest which AP. But when I disconnect and reconnect then it can shift users in new AP.
What can I do at this time.

Regards
-MEHEDI-

Hi Mehedi,

Sandeep Choudhary — Thu, 02 Feb 2017 08:34:48 GMT

Hi Mehedi,

How roaming works:

The decision to roam from a connected access point to a new access point is generally the responsibility of the wireless client device. The roaming algorithms used by wireless client devices vary from vendor to vendor, but almost always involve the evaluation of the received signal strength indicator (RSSI). As a user moves away from the connected AP, the signal degrades. The client compares the received signal strength to a pre-defined threshold and determines if a roam is required. Once the signal drops below this threshold, the wireless client performs an off-channel scan, scanning all available channels for a candidate AP, selects one with acceptable signal strength, and completes the roaming process by connecting or associating to the new AP. Some more sophisticated clients utilize additional parameters such as AP neighbor lists or capacity load on an AP to help optimize the roaming process.

Now...

did you do the site survey properly ?
Check the Power level of each AP on radios !!
Check the client driver, if needed upgrade it.
If you are using 802.11b/g radio, disable the low data rates such as 1, 2, 5.5, 6, 9 and 11. Make 12 as Mandatory and the rest supported.

Regards

Dont forget to rate helpful posts

Thanks Sandeep,

adm.mehedi — Thu, 02 Feb 2017 12:24:19 GMT

Thanks Sandeep,

Here for your information, Where I have configured my WLC in the same site. Also another vedor controller in the same site. It is working fine.
Like One network goes to WLC network and another is in other vendor controller.

So this is very much tough for me identify what problem is exactly.