Client Connecting to WLAN on Cisco WLC

Posted by robd on January 22, 2019
Wireless

Hi All,

Had a issue with users connecting to a WLAN on the virtual controller i.e. my mobile phone (94:65:2d:29:00:00) wouldn’t connect to standard PSK SSID.

So I ran the following on the console:

debug client 94:65:2d:29:00:00

Then tried to connect and had the following results:

(Cisco Controller) >*apfOpenDtlSocket: Jan 22 08:52:43.645: 94:65:2d:29:00:00 Recevied management frame ASSOCIATION REQUEST on BSSID f8:0b:cb:43:15:bb destination addr f8:0b:cb:43:15:bb
*apfOpenDtlSocket: Jan 22 08:52:46.278: 94:65:2d:29:00:00 Recevied management frame ASSOCIATION REQUEST on BSSID f8:0b:cb:43:15:bb destination addr f8:0b:cb:43:15:bb
*apfMsConnTask_6: Jan 22 08:52:46.278: 94:65:2d:29:00:00 Processing assoc-req station:94:65:2d:29:00:00 AP:f8:0b:cb:43:15:b0-01 ssid : GUEST thread:a513f80
*apfMsConnTask_6: Jan 22 08:52:46.278: 94:65:2d:29:00:00 Station: 94:65:2d:29:00:00 trying to join WLAN with RSSI -50. Checking for XOR roam conditions on AP: F8:0B:CB:43:15:B0 Slot: 1
*apfMsConnTask_6: Jan 22 08:52:46.278: 94:65:2d:29:00:00 Station: 94:65:2d:29:00:00 is associating to AP F8:0B:CB:43:15:B0 which is not XOR roam capable
*apfMsConnTask_6: Jan 22 08:52:46.278: 94:65:2d:29:00:00 Association received from mobile on BSSID f8:0b:cb:43:15:ba AP ISE-TEST-AP
*apfMsConnTask_6: Jan 22 08:52:46.278: 94:65:2d:29:00:00 Station: 94:65:2d:29:00:00 trying to join WLAN with RSSI -50. Checking for XOR roam conditions on AP: F8:0B:CB:43:15:B0 Slot: 1
*apfMsConnTask_6: Jan 22 08:52:46.278: 94:65:2d:29:00:00 Station: 94:65:2d:29:00:00 is associating to AP F8:0B:CB:43:15:B0 which is not XOR roam capable
*apfMsConnTask_6: Jan 22 08:52:46.278: 94:65:2d:29:00:00 Global 200 Clients are allowed to AP radio
*apfMsConnTask_6: Jan 22 08:52:46.278: 94:65:2d:29:00:00 Max Client Trap Threshold: 0 cur: 19
*apfMsConnTask_6: Jan 22 08:52:46.278: 94:65:2d:29:00:00 Rf profile 600 Clients are allowed to AP wlan
*apfMsConnTask_6: Jan 22 08:52:46.278: 94:65:2d:29:00:00 Max client(60) reached on WLAN. Sending assoc resp failure with reason code 17(max_sta)

The bottom line looked like the issue was a client connection limit per WLAN so I had a look on the console and found:

 

Changed it to 0 and BOOM.

Tags: ,

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.