Comprar o Renovar
Comprar o Renovar
cancelar
Activar sugerencias
La sugerencia automática le ayuda a obtener, de forma rápida, resultados precisos de su búsqueda al sugerirle posibles coincidencias mientras escribe.
Mostrando los resultados de 
Buscar en lugar de 
Quiere decir: 
cancel
Iniciar una conversación
1062
Visitas
0
ÚTIL
1
Respuestas

Client got no connection to WLAN over WLC 2504

Ir a solución
holgerseiler
Level 1
Level 1

el ‎09-12-2012 05:50 AM

Hi,

I got a new WLAN implementation and Clients could not connect to the WLAN.

OS is Windows XP, DHCP Proxy is enabled, DHCP Server is reachable, Controller firmware is 7.0.116.

MAC of the client is: 00:21:5d:18:e7:9c

I took the debug dhcp and debug client below

(Cisco Controller) >*apfReceiveTask: Sep 12 14:04:04.022: 00:21:5d:18:e7:9c Deleting mobile on AP 0c:85:25:32:cf:00(0)

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c Adding mobile on LWAPP AP 0c:85:25:32:cf:00(0)

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c Association received from mobile on AP 0c:85:25:32:cf:00

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c 0.0.0.0 START (0) Changing ACL 'none' (ACL ID 0) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1621)

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c Applying site-specific IPv6 override for station 00:21:5d:18:e7:9c - vapId 2, site 'default-group', interface 'wlan_inet'

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c Applying IPv6 Interface Policy for station 00:21:5d:18:e7:9c - vlan 7, interface id 11, interface 'wlan_inet'

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c STA - rates (7): 150 24 36 48 72 96 108 0 0 0 0 0 0 0 0 0

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c Processing WPA IE type 221, length 24 for mobile 00:21:5d:18:e7:9c

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c 0.0.0.0 START (0) Initializing policy

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c 0.0.0.0 START (0) Change state to AUTHCHECK (2) last state AUTHCHECK (2)

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c 0.0.0.0 AUTHCHECK (2) Change state to 8021X_REQD (3) last state 8021X_REQD (3)

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c 0.0.0.0 8021X_REQD (3) DHCP Not required on AP 0c:85:25:32:cf:00 vapId 2 apVapId 2for this client

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c Not Using WMM Compliance code qosCap 00

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c 0.0.0.0 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 0c:85:25:32:cf:00 vapId 2 apVapId 2

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c apfMsAssoStateInc

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c apfPemAddUser2 (apf_policy.c:223) Changing state for mobile 00:21:5d:18:e7:9c on AP 0c:85:25:32:cf:00 from Idle to Associated

*apfMsConnTask_1: Sep 12 14:11:38.045: 00:21:5d:18:e7:9c Scheduling deletion of Mobile Station:  (callerId: 49) in 1800 seconds

*apfMsConnTask_1: Sep 12 14:11:38.046: 00:21:5d:18:e7:9c Sending Assoc Response to station on BSSID 0c:85:25:32:cf:00 (status 0) ApVapId 2 Slot 0

*apfMsConnTask_1: Sep 12 14:11:38.046: 00:21:5d:18:e7:9c apfProcessAssocReq (apf_80211.c:5241) Changing state for mobile 00:21:5d:18:e7:9c on AP 0c:85:25:32:cf:00 from Associated to Associated

*dot1xMsgTask: Sep 12 14:11:38.049: 00:21:5d:18:e7:9c Creating a PKC PMKID Cache entry for station 00:21:5d:18:e7:9c (RSN 0)

*dot1xMsgTask: Sep 12 14:11:38.049: 00:21:5d:18:e7:9c Initiating WPA PSK to mobile 00:21:5d:18:e7:9c

*dot1xMsgTask: Sep 12 14:11:38.049: 00:21:5d:18:e7:9c dot1x - moving mobile 00:21:5d:18:e7:9c into Force Auth state

*dot1xMsgTask: Sep 12 14:11:38.049: 00:21:5d:18:e7:9c Skipping EAP-Success to mobile 00:21:5d:18:e7:9c

*dot1xMsgTask: Sep 12 14:11:38.049: 00:21:5d:18:e7:9c Starting key exchange to mobile 00:21:5d:18:e7:9c, data packets will be dropped

*dot1xMsgTask: Sep 12 14:11:38.049: 00:21:5d:18:e7:9c Sending EAPOL-Key Message to mobile 00:21:5d:18:e7:9c

                                                                                                              state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00

*osapiBsnTimer: Sep 12 14:11:39.109: 00:21:5d:18:e7:9c 802.1x 'timeoutEvt' Timer expired for station 00:21:5d:18:e7:9c and for message = M2

*dot1xMsgTask: Sep 12 14:11:39.109: 00:21:5d:18:e7:9c Retransmit 1 of EAPOL-Key M1 (length 99) for mobile 00:21:5d:18:e7:9c

*osapiBsnTimer: Sep 12 14:11:40.109: 00:21:5d:18:e7:9c 802.1x 'timeoutEvt' Timer expired for station 00:21:5d:18:e7:9c and for message = M2

*dot1xMsgTask: Sep 12 14:11:40.109: 00:21:5d:18:e7:9c Retransmit 2 of EAPOL-Key M1 (length 99) for mobile 00:21:5d:18:e7:9c

*osapiBsnTimer: Sep 12 14:11:41.109: 00:21:5d:18:e7:9c 802.1x 'timeoutEvt' Timer expired for station 00:21:5d:18:e7:9c and for message = M2

*dot1xMsgTask: Sep 12 14:11:41.109: 00:21:5d:18:e7:9c Retransmit failure for EAPOL-Key M1 to mobile 00:21:5d:18:e7:9c, retransmit count 3, mscb deauth count 0

*dot1xMsgTask: Sep 12 14:11:41.109: 00:21:5d:18:e7:9c Sent Deauthenticate to mobile on BSSID 0c:85:25:32:cf:00 slot 0(caller 1x_ptsm.c:534)

*dot1xMsgTask: Sep 12 14:11:41.109: 00:21:5d:18:e7:9c Scheduling deletion of Mobile Station:  (callerId: 57) in 10 seconds

*osapiBsnTimer: Sep 12 14:11:51.109: 00:21:5d:18:e7:9c apfMsExpireCallback (apf_ms.c:608) Expiring Mobile!

*apfReceiveTask: Sep 12 14:11:51.110: 00:21:5d:18:e7:9c apfMsExpireMobileStation (apf_ms.c:5009) Changing state for mobile 00:21:5d:18:e7:9c on AP 0c:85:25:32:cf:00 from Associated to Disassociated

*apfReceiveTask: Sep 12 14:11:51.110: 00:21:5d:18:e7:9c Scheduling deletion of Mobile Station:  (callerId: 45) in 10 seconds

*osapiBsnTimer: Sep 12 14:12:01.121: 00:21:5d:18:e7:9c apfMsExpireCallback (apf_ms.c:608) Expiring Mobile!

*apfReceiveTask: Sep 12 14:12:01.121: 00:21:5d:18:e7:9c apfMsAssoStateDec

*apfReceiveTask: Sep 12 14:12:01.121: 00:21:5d:18:e7:9c apfMsExpireMobileStation (apf_ms.c:5132) Changing state for mobile 00:21:5d:18:e7:9c on AP 0c:85:25:32:cf:00 from Disassociated to Idle

*apfReceiveTask: Sep 12 14:12:01.121: 00:21:5d:18:e7:9c 0.0.0.0 8021X_REQD (3) Deleted mobile LWAPP rule on AP [0c:85:25:32:cf:00]

Etiquetas:
0 Útil
1 SOLUCIÓN ACEPTADA

Soluciones aceptadas

Ir a solución
iilyinas
Level 3
Level 3

el ‎09-12-2012 06:09 AM

Hi, Holger,

As you see:

--

*dot1xMsgTask: Sep 12 14:11:38.049: 00:21:5d:18:e7:9c Sending EAPOL-Key Message to mobile 00:21:5d:18:e7:9c

                                                                                                               state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00

*osapiBsnTimer:  Sep 12 14:11:39.109: 00:21:5d:18:e7:9c 802.1x 'timeoutEvt' Timer  expired for station 00:21:5d:18:e7:9c and for message = M2

*dot1xMsgTask: Sep 12 14:11:39.109: 00:21:5d:18:e7:9c Retransmit 1 of EAPOL-Key M1 (length 99) for mobile 00:21:5d:18:e7:9c

*osapiBsnTimer:  Sep 12 14:11:40.109: 00:21:5d:18:e7:9c 802.1x 'timeoutEvt' Timer  expired for station 00:21:5d:18:e7:9c and for message = M2

*dot1xMsgTask: Sep 12 14:11:40.109: 00:21:5d:18:e7:9c Retransmit 2 of EAPOL-Key M1 (length 99) for mobile 00:21:5d:18:e7:9c

*osapiBsnTimer:  Sep 12 14:11:41.109: 00:21:5d:18:e7:9c 802.1x 'timeoutEvt' Timer  expired for station 00:21:5d:18:e7:9c and for message = M2

*dot1xMsgTask:  Sep 12 14:11:41.109: 00:21:5d:18:e7:9c Retransmit failure for EAPOL-Key  M1 to mobile 00:21:5d:18:e7:9c, retransmit count 3, mscb deauth count 0

--

It's your client not responding.

It could be due to old drivers, for example, or a supplicant issue, or a certificate issue.

If you check all these things and they are correct, it could be, the supplicant is not fast enough to answer.

In this case you can increase timers:

config advanced eap identity-request-timeout 60
config advanced eap identity-request-retries 10
config advanced eap request-timeout 60
config advanced eap request-retries 10

Cheers, Irina

Ver la solución en mensaje original publicado

0 Útil
1 RESPUESTA 1

Ir a solución
iilyinas
Level 3
Level 3

el ‎09-12-2012 06:09 AM

Hi, Holger,

As you see:

--

*dot1xMsgTask: Sep 12 14:11:38.049: 00:21:5d:18:e7:9c Sending EAPOL-Key Message to mobile 00:21:5d:18:e7:9c

                                                                                                               state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00

*osapiBsnTimer:  Sep 12 14:11:39.109: 00:21:5d:18:e7:9c 802.1x 'timeoutEvt' Timer  expired for station 00:21:5d:18:e7:9c and for message = M2

*dot1xMsgTask: Sep 12 14:11:39.109: 00:21:5d:18:e7:9c Retransmit 1 of EAPOL-Key M1 (length 99) for mobile 00:21:5d:18:e7:9c

*osapiBsnTimer:  Sep 12 14:11:40.109: 00:21:5d:18:e7:9c 802.1x 'timeoutEvt' Timer  expired for station 00:21:5d:18:e7:9c and for message = M2

*dot1xMsgTask: Sep 12 14:11:40.109: 00:21:5d:18:e7:9c Retransmit 2 of EAPOL-Key M1 (length 99) for mobile 00:21:5d:18:e7:9c

*osapiBsnTimer:  Sep 12 14:11:41.109: 00:21:5d:18:e7:9c 802.1x 'timeoutEvt' Timer  expired for station 00:21:5d:18:e7:9c and for message = M2

*dot1xMsgTask:  Sep 12 14:11:41.109: 00:21:5d:18:e7:9c Retransmit failure for EAPOL-Key  M1 to mobile 00:21:5d:18:e7:9c, retransmit count 3, mscb deauth count 0

--

It's your client not responding.

It could be due to old drivers, for example, or a supplicant issue, or a certificate issue.

If you check all these things and they are correct, it could be, the supplicant is not fast enough to answer.

In this case you can increase timers:

config advanced eap identity-request-timeout 60
config advanced eap identity-request-retries 10
config advanced eap request-timeout 60
config advanced eap request-retries 10

Cheers, Irina
0 Útil

Navegue y encuentre contenido personalizado de la comunidad

Discusiones Wireless Discusiones Mobile Más de Wireless & Mobile
Customers Also Viewed These Support Documents