I would expect that, however what is the disassociation or deauthentication listed in the log?
Anything along the lines of "Client authentication expired", "Unknown Reason" , "client was deauthenticated" ?
Is it a single device, if so does it occur in a particular location?
There's some smart people around here but they need an reasonable information to work with.
Does this occur for all devices or only this client?
Assuming you have roaming configured (and working) what is providing the IP address for the client device, is it a regular DHCP service then or is the RADIUS server allocating the IP address and VLAN?
The log appears to say that the client is associated with AP06 until the disassociation at 15:35.
Does the client have an IP address belonging to vlan 325 at this point?
I always worry when I see log entries mentioning multiple DHCP servers especially when the device then stops communicating immediately afterwards. Perhaps you need to investigate this log entry.
I'm having this issue currently with an MR32 model.
802.11 association rejected for load balancing
It happens where a user cannot connect when there are too many people in the room near the AP, but once everyone leaves, the wireless works for them. This is the same results for others, for the past year and I haven't been able to figure it out.
We got similar issue. Laptops could not connect to Wifi. I don't see any record on the ISE (radius) server. And the laptop got issue would automatically connect to Wifi after 30 to 60 minutes.
|Jul 30 01:27:43||ap-xxxx-08||XXXX||XXX-A11214SL||802.1X deauthentication||radio: 1, vap: 0, client_mac: 4C:34:88:63:54:BB « hide |
|Jul 30 01:27:43||ap-xxxx-08||XXXX||XXX-A11214SL||802.11 association||channel: 48, rssi: 49|
|Jul 30 00:42:52||ap-xxxx-06||XXXX||XXX-A11214SL||802.11 disassociation||unspecified reason|
|Jul 30 00:42:52||ap-xxxx-06||XXXX||XXX-A11214SL||802.11 association||channel: 153, rssi: 35|
|Jul 30 00:42:51||ap-xxxx-06||XXXX||XXX-A11214SL||802.11 disassociation||unspecified reason|
|Jul 30 00:42:51||ap-xxxx-06||XXXX||XXX-A11214SL||802.11 association||channel: 153, rssi: 34|
@Albert1 , please ensure you remove hyperlinks when you copy over the logs, so you can avoid security issues. 😉
Regarding the problem, I always recommend to try and modify the RF profile from the Wireless > Radio Settings page.
The default profile does not always work well with all the environments and if you have a particularly dense one there's a few things you can do to improve, like increasing the bitrate and modify the transmit power range, enable client balancing and band steering, to ensure that all the clients get directed the best way possible.
Hope this helps!