Lightweight AP - Fail to create CAPWAP/LWAPP connection due to certificate expiration

[Yasir Iqbal]

Dear All,

We are facing very serious issues. We have Cisco 2505 WLAN Controller and 28 different AP are connecting in our office installed on different location. When one user connect to one AP and than move in the building he/she could not disconnect from the first AP and do not connect automatically to next AP which have strong wireless signals. We have to manually disconnect the AP and than reconnect to new AP which have strong signal. We have default configuration please help to solve the problem. 

[Sandeep Choudhary]

APs are in local mode or flexconnect mode ?

whihc software version you are running on WLC ?

[marce1000]

 - Why do you think this is due to certificate expiration ?

 M.

[Leo Laohoo]

---

@Yasir Iqbal wrote:

When one user connect to one AP and than move in the building he/she could not disconnect from the first AP and do not connect automatically to next AP which have strong wireless signals. 

---

I've seen this several times.  This is particularly so on laptops where the wireless NIC drivers were never updated.  Once the wireless NIC drivers where updated the wireless NIC roams marvelously.

[Scott Fella]

To add to Leo’s statement, it also depends on what data rates you have set at mandatory/supported/disabled along with the TX power for each radio on the AP. The device is the decision maker and typically the driver has a threshold on when the NIC should start to roam and when to roam. If the signal from the NIC is still within the threshold, the NIC will not roam or scan. So lowering the TX power and or disabling the low data rates helps with making the NIC scan and then eventually roam.