Client Disconnects from AP

Upendra
Here to help

Client Disconnects from AP

hello.

 

 

The client laptop is disconnects for sometime from the AP and need to manually reconnect back.

Its a radius authentication.

 

 

 

 

11 REPLIES 11
cta102
Building a reputation

What do the logs say?

I don't find any logs once the user gets disconnected.
cta102
Building a reputation

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.

 

 

 

 

Dear Sir,
Please look into the below log details.
at 15:06 client automatically disconnected and it'll not connect back automatically, after waiting for sometime. at 15:35 client manually disconnects and reconnected.

Time(IST) Access point SSID Client Event type Details
01-05-2009 15:35 OM-EC-1F-LW-AP-03 OMWLAN WBLL0917S0097 802.1X authentication "radio: 1, vap: 0, client_mac: 80:86:F2:DC:99:93"
01-05-2009 15:35 OM-EC-1F-LW-AP-03 OMWLAN WBLL0917S0097 802.1X EAP success "radio: 1, vap: 0, client_mac: 80:86:F2:DC:99:93"
01-05-2009 15:35 OM-EC-1F-LW-AP-03 OMWLAN WBLL0917S0097 RADIUS response "radio: 1, vap: 0, vlan: 325"
01-05-2009 15:35 OM-EC-1F-LW-AP-03 OMWLAN WBLL0917S0097 802.11 association "channel: 157, rssi: 34"
01-05-2009 15:35 OM-EC-1F-LW-AP-06 WBLL0917S0097 802.11 association rejected for load balancing "load: 22, best_ap: 172.19.65.35, best_ap_load: 12"
01-05-2009 15:35 OM-EC-1F-LW-AP-02 WBLL0917S0097 802.11 association rejected for load balancing "load: 16, best_ap: 172.19.65.35, best_ap_load: 12"
01-05-2009 15:35 OM-EC-1F-LW-AP-06 OMWLAN WBLL0917S0097 802.11 disassociation "radio: 1, vap: 0, client_mac: 80:86:F2:DC:99:93"
01-05-2009 15:06 OM-EC-1F-LW-AP-06 OMWLAN WBLL0917S0097 Multiple DHCP servers detected "vap: 0, original_server_ip: 172.19.128.1, original_server_mac: 44:03:A7:2A:FF:3F"
01-05-2009 15:06 OM-EC-1F-LW-AP-06 OMWLAN WBLL0917S0097 802.1X authentication "radio: 1, vap: 0, client_mac: 80:86:F2:DC:99:93"
01-05-2009 15:06 OM-EC-1F-LW-AP-06 OMWLAN WBLL0917S0097 802.11 association "channel: 40, rssi: 50"
01-05-2009 15:06 OM-EC-1F-LW-AP-06 OMWLAN WBLL0917S0097 OKC match "radio: 1, vap: 0, vlan: 325"
01-05-2009 15:06 OM-EC-1F-LW-AP-06 OMWLAN WBLL0917S0097 802.11 disassociation "radio: 1, vap: 0, client_mac: 80:86:F2:DC:99:93"
01-05-2009 15:06 OM-EC-1F-LW-AP-06 OMWLAN WBLL0917S0097 802.11 disassociation "radio: 1, vap: 0, client_mac: 80:86:F2:DC:99:93"

thanks
cta102
Building a reputation

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.


Only 2 to 3 users are facing the issue.

The RADIUS server allocating the IP address and VLAN.
yes VLAN is 325.

thanks.
PhilipDAth
Kind of a big deal
Kind of a big deal

If you are not running 25.11 then upgrade to that firmware release.

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:43ap-xxxx-08XXXXXXX-A11214SL802.1X deauthenticationradio: 1, vap: 0, client_mac: 4C:34:88:63:54:BB  « hide
client_ip0.0.0.0
identityXXXX\xxxxxxx
aid737848522
Jul 30 01:27:43ap-xxxx-08XXXXXXX-A11214SL802.11 associationchannel: 48, rssi: 49
Jul 30 00:42:52ap-xxxx-06XXXXXXX-A11214SL802.11 disassociationunspecified reason
Jul 30 00:42:52ap-xxxx-06XXXXXXX-A11214SL802.11 associationchannel: 153, rssi: 35
Jul 30 00:42:51ap-xxxx-06XXXXXXX-A11214SL802.11 disassociationunspecified reason
Jul 30 00:42:51ap-xxxx-06XXXXXXX-A11214SL802.11 associationchannel: 153, rssi: 34

Hi all,

 

@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!

 

Giacomo

Please keep in mind that what I post here is my personal knowledge and opinion. Don't take anything I say for the Holy Grail, but try and see!
Appreciate who helps and be respectful of every opinion and every solution offered.
Share the love, especially the Meraki one!
WitriManurung
New here

Have you any solution or suggestion for this problem?

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels