topic The iOS devices having this in Wireless

WLC 5508 - iOS devices dropping WiFi after upgrade to 8.0.140.0

sean Riley — Mon, 05 Jul 2021 13:26:50 GMT

We upgraded our WLC 5508 this past weekend from v 8.0.121.0 to v 8.0.140.0. Since we have noticed that iOS devices (iPad, iPhones) are dissociating from the WLC after they are idle/sleeping for a given period of time. As soon as you unlock an iOS device it reconnects to the WLAN without issue. This seems to be happening with both certificate and 802.1x authenticated devices. We are using ACS for authentication. We did not have this issue before the upgrade. Windows laptops connecting to the same WLAN seem to be OK.

WLC is in HA mode and primary controller has control.

AP's are Aironet 3702i's in local mode.

Any suggestions on how to start debugging?

Thanks.

are dissociating from the WLC

Leo Laohoo — Thu, 26 Jan 2017 21:32:50 GMT

are dissociating from the WLC after they are idle/sleeping for a given period of time.

I believe this has something to do with Sleeping Clients.

This ensures the wireless client's will maximize their battery life.

The iOS devices having this

sean Riley — Fri, 27 Jan 2017 14:13:03 GMT

The iOS devices having this issue are not using webauth, but instead 802.1x, so I do not believe "Sleeping Clients" is valid. Correct?

I tried adjusting the global "User Idle Timeout (seconds)" to 4 hours, but the devices still seem to be disconnecting before this timeout.

I did see the WLAN being used has "Enable Session Timeout" set to 30 minutes. Does this setting take priority over the global "User Idle Timeout (seconds)"?

Still seems strange that we these problems did not crop up until after the last upgrade. I verified the timeout settings are the same as they were in prior 8.0.121.0 version.

Since you are not using

Scott Fella — Fri, 27 Jan 2017 14:22:12 GMT

Since you are not using webauth, sleeping clients doesn't matter and you shouldn't be able to set that. I would just disable the session timer and leave idle timer at 300 seconds which is default globally. Make sure you are only using either WPA/TKIP or WPA2/AES, the later is preferred. Also make sure you don't have client load balancing enabled.

-Scott

*** Please rate helpful posts ***

Can you put one IOS client to

rafael.alves — Mon, 30 Jan 2017 17:02:47 GMT

Can you put one IOS client to debug:

(Cisco Controller) >debug client <XX:XX:XX:XX:XX:XX>

And get the logs it shows. You'll be able to determine the issue analyzing the log itself.

Disabling the session timeout

sean Riley — Mon, 30 Jan 2017 19:08:24 GMT

Disabling the session timeout for the WLAN seems to have resolved our problems. Just not sure why this behavior did not crop up until after the last upgrade, since the behavior we experienced was in-line with our configuration. Thanks.

If you "disable" the session

Freerk Terpstra — Thu, 02 Feb 2017 19:35:59 GMT

If you "disable" the session timeout on a 802.1x enabled WLAN the default value of 86400 will be used. You had it configured for 30 minutes before which means that the session will be terminated every 30 minutes no matter what. The idle time-out is a "early clean-up feature" which will remove the client before the session timeout expired based on inactivity.

Please rate useful posts... 🙂