Client associating not Auth. 5508WLC 1100 series AP

[Stewart Roth]

This client is a handheld unit that has communicated in the past and now will not.  I can have user take handheld to a different office close by and it will communicate.  This other office is in the same AP Group as well.

7.0.116 code on the WLC..that is the oldest code that will still support the 1121 AP's i am in the waiting for $$ to phase those out.

c1100-rcvk9w8-tar.124-21a.JA2.tar is on the AP.  I admit i am not the best at reading debugs but can anyone find any issue from looking at my debug that follows?

debug from the AP:

dot1xMsgTask: Feb 20 08:44:23.673: 00:02:b3:e1:89:76 dot1x - moving mobile 00:02:b3:e1:89:76 into Force Auth state

*dot1xMsgTask: Feb 20 08:44:43.749: 00:02:b3:e1:89:76 Sent Deauthenticate to mobile on BSSID 00:12:d9:c2:22:d0 slot 0(caller 1x_ptsm.c:534)

*dot1xMsgTask: Feb 20 08:44:43.749: 00:02:b3:e1:89:76 Scheduling deletion of Mobile Station: (callerId: 57) in 10 seconds

*apfMsConnTask_3: Feb 20 08:44:44.420: 00:02:b3:e1:89:76 Association received from mobile on AP 00:12:d9:c2:22:d0

*apfMsConnTask_3: Feb 20 08:44:44.420: 00:02:b3:e1:89:76 0.0.0.0 8021X_REQD (3) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1621)

*apfMsConnTask_3: Feb 20 08:44:44.420: 00:02:b3:e1:89:76 Applying site-specific IPv6 override for station 00:02:b3:e1:89:76 - vapId 1, site 'NC_APG', interface 'nc_ap'

*apfMsConnTask_3: Feb 20 08:44:44.421: 00:02:b3:e1:89:76 Applying IPv6 Interface Policy for station 00:02:b3:e1:89:76 - vlan 382, interface id 44, interface 'nc_ap'

*apfMsConnTask_3: Feb 20 08:44:44.421: 00:02:b3:e1:89:76 Applying site-specific override for station 00:02:b3:e1:89:76 - vapId 1, site 'NC_APG', interface 'nc_ap'

*apfMsConnTask_3: Feb 20 08:44:44.421: 00:02:b3:e1:89:76 0.0.0.0 8021X_REQD (3) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1621)

*apfMsConnTask_3: Feb 20 08:44:44.421: 00:02:b3:e1:89:76 STA - rates (4): 130 132 139 150 0 0 0 0 0 0 0 0 0 0 0 0

*apfMsConnTask_3: Feb 20 08:44:44.421: 00:02:b3:e1:89:76 0.0.0.0 8021X_REQD (3) Initializing policy

*apfMsConnTask_3: Feb 20 08:44:44.421: 00:02:b3:e1:89:76 0.0.0.0 8021X_REQD (3) Change state to AUTHCHECK (2) last state 8021X_REQD (3)

*apfMsConnTask_3: Feb 20 08:44:44.421: 00:02:b3:e1:89:76 0.0.0.0 AUTHCHECK (2) Change state to 8021X_REQD (3) last state 8021X_REQD (3)

*apfMsConnTask_3: Feb 20 08:44:44.421: 00:02:b3:e1:89:76 0.0.0.0 8021X_REQD (3) DHCP Not required on AP 00:12:d9:c2:22:d0 vapId 1 apVapId 1for this client

*apfMsConnTask_3: Feb 20 08:44:44.421: 00:02:b3:e1:89:76 Not Using WMM Compliance code qosCap 00

*apfMsConnTask_3: Feb 20 08:44:44.421: 00:02:b3:e1:89:76 0.0.0.0 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 00:12:d9:c2:22:d0 vapId 1 apVapId 1

*apfMsConnTask_3: Feb 20 08:44:44.421: 00:02:b3:e1:89:76 apfPemAddUser2 (apf_policy.c:223) Changing state for mobile 00:02:b3:e1:89:76 on AP 00:12:d9:c2:22:d0 from Associated to Associated

*apfMsConnTask_3: Feb 20 08:44:44.421: 00:02:b3:e1:89:76 Scheduling deletion of Mobile Station: (callerId: 49) in 1800 seconds

*apfMsConnTask_3: Feb 20 08:44:44.421: 00:02:b3:e1:89:76 Sending Assoc Response to station on BSSID 00:12:d9:c2:22:d0 (status 0) ApVapId 1 Slot 0

*apfMsConnTask_3: Feb 20 08:44:44.421: 00:02:b3:e1:89:76 apfProcessAssocReq (apf_80211.c:5241) Changing state for mobile 00:02:b3:e1:89:76 on AP 00:12:d9:c2:22:d0 from Associated to Associated

*dot1xMsgTask: Feb 20 08:44:44.471: 00:02:b3:e1:89:76 dot1x - moving mobile 00:02:b3:e1:89:76 into Force Auth state

*dot1xMsgTask: Feb 20 08:45:04.553: 00:02:b3:e1:89:76 Sent Deauthenticate to mobile on BSSID 00:12:d9:c2:22:d0 slot 0(caller 1x_ptsm.c:534)

*dot1xMsgTask: Feb 20 08:45:04.553: 00:02:b3:e1:89:76 Scheduling deletion of Mobile Station: (callerId: 57) in 10 seconds

*osapiBsnTimer: Feb 20 08:45:14.557: 00:02:b3:e1:89:76 apfMsExpireCallback (apf_ms.c:608) Expiring Mobile!

*apfReceiveTask: Feb 20 08:45:14.557: 00:02:b3:e1:89:76 apfMsExpireMobileStation (apf_ms.c:5009) Changing state for mobile 00:02:b3:e1:89:76 on AP 00:12:d9:c2:22:d0 from Associated to Disassociated

*apfReceiveTask: Feb 20 08:45:14.557: 00:02:b3:e1:89:76 Scheduling deletion of Mobile Station: (callerId: 45) in 10 seconds

*spamApTask2: Feb 20 08:45:23.966: 00:02:b3:e1:89:76 Received Idle-Timeout from AP 00:12:d9:c2:22:d0, slot 0 for STA 00:02:b3:e1:89:76

*spamApTask2: Feb 20 08:45:23.966: 00:02:b3:e1:89:76 apfMsDeleteByMscb Scheduling mobile for deletion with deleteReason 4, reasonCode 4

[Scott Fella]

Stewart,

If it works everywhere else and not at that site, can other devices connect to the AP?  I would take a look at the debug from another site so you can compare the debugs to see what is happening. 

Thanks,

Scott

*****Help out other by using the rating system and marking answered questions as "Answered"*****

[Stewart Roth]

Yes other devices can connect fine.  Handhelds of the same model even connect.  I can't tell from the debug if the client is just not responding or not responding fast enough.  I have my timeout and handshake timeouts etc etc up a little higher because of a similiar issue with this model handheld at a large number of our 300+ locations.

[Scott Fella]

It seems like you isolated the issue to the 1100's... is the ssid open or you using some layer 2 encryption, because that might also the the cause... the hardware might not adhere to the requirements for the newer hardware or code.  If the device doesn't connect to an open ssid, I would have to say you need to replace that AP(S).  No reason to change your WLAN configuration since its working in you other 300+ locations.

Thanks,

Scott

*****Help out other by using the rating system and marking answered questions as "Answered"*****

[Stewart Roth]

I'm using WPA TKIP with a PSK.  I wish I had it isolated to the 1100's as this would push the need to upgrade..but this handheld when taken to the other location was also an 1121 AP... this is very sporadic behavior as i will hear of no issues for months..then out of nowhere it just refuses to connect.  It's been exceptionally frustrating to say the least.

Thanks!

[Scott Fella]

Could be that the AP's are going bad... They don't last forever.

Sent from Cisco Technical Support iPhone App