Issues with client looses connection with 6.0.196.0

Question

Hi,
We recently upgraded our Wisms to version 6.0.196.0 and after the upgrade we have seen the clients sometimes looses connectivity and has problems to connect. We use an network with 802.1x  and PeapMschapv2 with dynamic WEP.
We have disabled aggresive load-balancing but still see the issues.
Any ideas anyone?
Regards,
Martin

Answer 1

Hi,
Any news for these problems? Did the version 7.x fix these CAPWAP UP/DOWN problems with HREAP APs? It seems that I'm having these same problems now. Local APs seems to be fine, but HREAP APs goes UP/DOWN with versions 6.0.196.0 and 6.0.199.4.
There are three 4404 WLCs, where are different sites' office and warehouse APs connected to. The environment is configured as N + N + 1
like following:
WLC1 is for officeAPs. APs are 1131 and they're configured as H-REAP
WLC2 is for warehouseAPs. APs are 1242 and they're configured as Local
WLC3 is for backup and I used this for testing.
After I updated all the WLCs at summer to version 6.0.196.0, there have been issues where the clients looses randomly WLAN-connections. But the complaints just came from the two largest offices. And these didn't happend immeaditly after the update, but after few months. It can be that the summer holidays was reason for it. After some investigations, I updated the WLC3 for version 6.0.199.4, which just got released at the time, and moved these two largest offices' APs to there. Complaints stopped but after a month the second largest office informed that the clients' disconnections started to raise again and the WLAN-network has become unstable again. First there was just couple of issues but it have been raised as the time goes by.
When I made some more investigation to this site, I noticed that the APs' CAPWAP goes DOWN and UP randomly for a second:
*Nov 12 07:39:29.537: %CAPWAP-5-CHANGED: CAPWAP changed state to DOWN
*Nov 12 07:39:29.590: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Nov 12 07:39:29.590: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Nov 12 07:39:29.759: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
*Nov 12 07:39:29.811: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Nov 12 07:39:29.812: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Nov 12 07:39:29.849: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Nov 12 07:39:29.850: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Nov 12 07:39:29.889: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
Then I investigated some more and noticed that this happens on all of the H-REAP APs and almost in the same time:
*Nov 12 07:39:29.537: %CAPWAP-5-CHANGED: CAPWAP changed state to DOWN - WLC3, second largest site's AP (6.0.199.4)
*Nov 12 07:40:17.439: %CAPWAP-5-CHANGED: CAPWAP changed state to DOWN - WLC3, second largest site's other AP (6.0.199.4)
*Nov 12 07:41:20.297: %CAPWAP-5-CHANGED: CAPWAP changed state to DOWN - WLC3, largest site's AP (6.0.199.4)
*Nov 12 07:42:31.928: %CAPWAP-5-CHANGED: CAPWAP changed state to DOWN - WLC1, random site's AP (6.0.196.0)
When I checked the warehouseAPs, which are configured as local in the WLC2 (6.0.196.0), there was nothing like this in the logs. Logs are clean.
But when H-REAP is configured for these APs, the clients should not be disconnected when the CAPWAP goes down? And this whole "process"  seems to last just for a second. Not sure if this is the real reason for these client disconnections, but at least this is not normal. I haven't heard complaints from smaller sites, even when APs at them also does the same.
I don't feel great to update the WLCs for the version 7.x, because it just seems to be new feature release, but if it fixes these, then I should think about it. Has someone, who had these same problems, got this fixed with version 7? Or has TAC provide some other patches for this?
Thanks,
Joni