Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Wifi phone 7925 packet dropped when roaming between APs

                   Hi there,  redcently we have deployed a Two APs in branch office warehouse and  I have one wifi phone 7925 used over there. the problem is every time when phone roaming from one AP to another, 2 or 3 packets dropped,  following is result of the 'debug client ',  any suggestion:

--More or (q)uit current module or <ctrl-z> to abort*apfMsConnTask_7: Jun 27 09:52:25.496: 88:43:e1:4f:ab:39 Association received from mobile on AP a0:cf:5b:c3:a8:90
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 10.107.38.121 RUN (20) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1621)
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 Applying site-specific IPv6 override for station 88:43:e1:4f:ab:39 - vapId 14, site 'AKL-AP-GP', interface 'management'
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 Applying IPv6 Interface Policy for station 88:43:e1:4f:ab:39 - vlan 38, interface id 0, interface 'management'
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 Applying site-specific override for station 88:43:e1:4f:ab:39 - vapId 14, site 'AKL-AP-GP', interface 'management'
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 10.107.38.121 RUN (20) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1621)
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 STA - rates (6): 152 36 48 72 96 108 96 108 0 0 0 0 0 0 0 0
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 Processing RSN IE type 48, length 22 for mobile 88:43:e1:4f:ab:39
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 CCKM: Mobile is using CCKM
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 Received RSN IE with 0 PMKIDs from mobile 88:43:e1:4f:ab:39
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 10.107.38.121 RUN (20) Deleted mobile LWAPP rule on AP [a0:cf:5b:c2:29:60]
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 Updated location for station old AP a0:cf:5b:c2:29:60-1, new AP a0:cf:5b:c3:a8:90-1
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 apfMsRunStateDec
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 apfMs1xStateDec
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 10.107.38.121 RUN (20) Change state to START (0) last state RUN (20)

*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 10.107.38.121 START (0) Initializing policy
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 10.107.38.121 START (0) Change state to AUTHCHECK (2) last state RUN (20)

*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 10.107.38.121 AUTHCHECK (2) Change state to 8021X_REQD (3) last state RUN (20)

*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 10.107.38.121 8021X_REQD (3) DHCP required on AP a0:cf:5b:c3:a8:90 vapId 14 apVapId 3for this client
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 Not Using WMM Compliance code qosCap 0f
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 10.107.38.121 8021X_REQD (3) Plumbed mobile LWAPP rule on AP a0:cf:5b:c3:a8:90 vapId 14 apVapId 3
*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 apfPemAddUser2 (apf_policy.c:223) Changing state for mobile 88:43:e1:4f:ab:39 on AP a0:cf:5b:c3:a8:90 from Associated to Associated

*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 Stopping deletion of Mobile Station: (callerId: 48)
*apfMsConnTask_7: Jun 27 09:52:25.498: 88:43:e1:4f:ab:39 Sending Assoc Response to station on BSSID a0:cf:5b:c3:a8:90 (status 0) ApVapId 3 Slot 1
*apfMsConnTask_7: Jun 27 09:52:25.498: 88:43:e1:4f:ab:39 apfProcessAssocReq (apf_80211.c:5241) Changing state for mobile 88:43:e1:4f:ab:39 on AP a0:cf:5b:c3:a8:90 from Associated to Associated

*apfMsConnTask_7: Jun 27 09:52:25.554: 88:43:e1:4f:ab:39 Updating AID for REAP AP Client a0:cf:5b:c3:a8:90 - AID ===> 1
*dot1xMsgTask: Jun 27 09:52:25.554: 88:43:e1:4f:ab:39 Disable re-auth, use PMK lifetime.
*dot1xMsgTask: Jun 27 09:52:25.554: 88:43:e1:4f:ab:39 dot1x - moving mobile 88:43:e1:4f:ab:39 into Connecting state
*dot1xMsgTask: Jun 27 09:52:25.554: 88:43:e1:4f:ab:39 Sending EAP-Request/Identity to mobile 88:43:e1:4f:ab:39 (EAP Id 1)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.629: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.629: 88:43:e1:4f:ab:39 Received Identity Response (count=1) from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.629: 88:43:e1:4f:ab:39 EAP State update from Connecting to Authenticating for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.629: 88:43:e1:4f:ab:39 dot1x - moving mobile 88:43:e1:4f:ab:39 into Authenticating state
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.629: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.630: 88:43:e1:4f:ab:39 Processing Access-Challenge for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.630: 88:43:e1:4f:ab:39 Entering Backend Auth Req state (id=157) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.630: 88:43:e1:4f:ab:39 WARNING: updated EAP-Identifier 1 ===> 157 for STA 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.630: 88:43:e1:4f:ab:39 Sending EAP Request from AAA to mobile 88:43:e1:4f:ab:39 (EAP Id 157)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.739: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.739: 88:43:e1:4f:ab:39 Received EAP Response from mobile 88:43:e1:4f:ab:39 (EAP Id 157, EAP Type 13)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.739: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.741: 88:43:e1:4f:ab:39 Processing Access-Challenge for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.741: 88:43:e1:4f:ab:39 Entering Backend Auth Req state (id=158) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.741: 88:43:e1:4f:ab:39 Sending EAP Request from AAA to mobile 88:43:e1:4f:ab:39 (EAP Id 158)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.846: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.846: 88:43:e1:4f:ab:39 Received EAP Response from mobile 88:43:e1:4f:ab:39 (EAP Id 158, EAP Type 13)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.846: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.847: 88:43:e1:4f:ab:39 Processing Access-Challenge for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.847: 88:43:e1:4f:ab:39 Entering Backend Auth Req state (id=159) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.847: 88:43:e1:4f:ab:39 Sending EAP Request from AAA to mobile 88:43:e1:4f:ab:39 (EAP Id 159)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.897: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.897: 88:43:e1:4f:ab:39 Received EAP Response from mobile 88:43:e1:4f:ab:39 (EAP Id 159, EAP Type 13)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.897: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.898: 88:43:e1:4f:ab:39 Processing Access-Challenge for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.898: 88:43:e1:4f:ab:39 Entering Backend Auth Req state (id=160) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.898: 88:43:e1:4f:ab:39 Sending EAP Request from AAA to mobile 88:43:e1:4f:ab:39 (EAP Id 160)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.950: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.950: 88:43:e1:4f:ab:39 Received EAP Response from mobile 88:43:e1:4f:ab:39 (EAP Id 160, EAP Type 13)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.950: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.951: 88:43:e1:4f:ab:39 Processing Access-Challenge for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.951: 88:43:e1:4f:ab:39 Entering Backend Auth Req state (id=161) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:25.951: 88:43:e1:4f:ab:39 Sending EAP Request from AAA to mobile 88:43:e1:4f:ab:39 (EAP Id 161)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.002: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.002: 88:43:e1:4f:ab:39 Received EAP Response from mobile 88:43:e1:4f:ab:39 (EAP Id 161, EAP Type 13)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.002: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.004: 88:43:e1:4f:ab:39 Processing Access-Challenge for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.004: 88:43:e1:4f:ab:39 Entering Backend Auth Req state (id=162) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.004: 88:43:e1:4f:ab:39 Sending EAP Request from AAA to mobile 88:43:e1:4f:ab:39 (EAP Id 162)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.063: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.063: 88:43:e1:4f:ab:39 Received EAP Response from mobile 88:43:e1:4f:ab:39 (EAP Id 162, EAP Type 13)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.063: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.064: 88:43:e1:4f:ab:39 Processing Access-Challenge for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.065: 88:43:e1:4f:ab:39 Entering Backend Auth Req state (id=163) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.065: 88:43:e1:4f:ab:39 Sending EAP Request from AAA to mobile 88:43:e1:4f:ab:39 (EAP Id 163)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.115: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.115: 88:43:e1:4f:ab:39 Received EAP Response from mobile 88:43:e1:4f:ab:39 (EAP Id 163, EAP Type 13)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.115: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.116: 88:43:e1:4f:ab:39 Processing Access-Challenge for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.116: 88:43:e1:4f:ab:39 Entering Backend Auth Req state (id=164) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.116: 88:43:e1:4f:ab:39 Sending EAP Request from AAA to mobile 88:43:e1:4f:ab:39 (EAP Id 164)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.550: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.550: 88:43:e1:4f:ab:39 Received EAP Response from mobile 88:43:e1:4f:ab:39 (EAP Id 164, EAP Type 13)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.550: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.551: 88:43:e1:4f:ab:39 Processing Access-Challenge for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.551: 88:43:e1:4f:ab:39 Entering Backend Auth Req state (id=165) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.551: 88:43:e1:4f:ab:39 Sending EAP Request from AAA to mobile 88:43:e1:4f:ab:39 (EAP Id 165)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.648: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.648: 88:43:e1:4f:ab:39 Received EAP Response from mobile 88:43:e1:4f:ab:39 (EAP Id 165, EAP Type 13)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.648: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.649: 88:43:e1:4f:ab:39 Processing Access-Challenge for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.649: 88:43:e1:4f:ab:39 Entering Backend Auth Req state (id=166) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.649: 88:43:e1:4f:ab:39 Sending EAP Request from AAA to mobile 88:43:e1:4f:ab:39 (EAP Id 166)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.697: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.697: 88:43:e1:4f:ab:39 Received EAP Response from mobile 88:43:e1:4f:ab:39 (EAP Id 166, EAP Type 13)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.697: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.698: 88:43:e1:4f:ab:39 Processing Access-Challenge for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.698: 88:43:e1:4f:ab:39 Entering Backend Auth Req state (id=167) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.698: 88:43:e1:4f:ab:39 Sending EAP Request from AAA to mobile 88:43:e1:4f:ab:39 (EAP Id 167)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.758: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.758: 88:43:e1:4f:ab:39 Received EAP Response from mobile 88:43:e1:4f:ab:39 (EAP Id 167, EAP Type 13)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.758: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.759: 88:43:e1:4f:ab:39 Processing Access-Challenge for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.760: 88:43:e1:4f:ab:39 Entering Backend Auth Req state (id=168) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.760: 88:43:e1:4f:ab:39 Sending EAP Request from AAA to mobile 88:43:e1:4f:ab:39 (EAP Id 168)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.809: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.809: 88:43:e1:4f:ab:39 Received EAP Response from mobile 88:43:e1:4f:ab:39 (EAP Id 168, EAP Type 13)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.809: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.810: 88:43:e1:4f:ab:39 Processing Access-Challenge for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.810: 88:43:e1:4f:ab:39 Entering Backend Auth Req state (id=169) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.810: 88:43:e1:4f:ab:39 Sending EAP Request from AAA to mobile 88:43:e1:4f:ab:39 (EAP Id 169)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.853: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.853: 88:43:e1:4f:ab:39 Received EAP Response from mobile 88:43:e1:4f:ab:39 (EAP Id 169, EAP Type 13)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.853: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.916: 88:43:e1:4f:ab:39 Processing Access-Challenge for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.916: 88:43:e1:4f:ab:39 Entering Backend Auth Req state (id=170) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.916: 88:43:e1:4f:ab:39 Sending EAP Request from AAA to mobile 88:43:e1:4f:ab:39 (EAP Id 170)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.960: 88:43:e1:4f:ab:39 Received EAPOL EAPPKT from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.960: 88:43:e1:4f:ab:39 Received EAP Response from mobile 88:43:e1:4f:ab:39 (EAP Id 170, EAP Type 13)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.960: 88:43:e1:4f:ab:39 Entering Backend Auth Response state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962: 88:43:e1:4f:ab:39 Processing Access-Accept for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962: 88:43:e1:4f:ab:39 Resetting web acl from 255 to 255

*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962: 88:43:e1:4f:ab:39 Setting re-auth timeout to 0 seconds, got from WLAN config.
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962: 88:43:e1:4f:ab:39 Station 88:43:e1:4f:ab:39 setting dot1x reauth timeout = 0
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962: 88:43:e1:4f:ab:39 Stopping reauth timeout for 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962: 88:43:e1:4f:ab:39 Creating a PKC PMKID Cache entry for station 88:43:e1:4f:ab:39 (RSN 2)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962: 88:43:e1:4f:ab:39 Adding BSSID a0:cf:5b:c3:a8:9d to PMKID cache for station 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962: New PMKID: (16)

*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962:      [0000] 6b 25 86 3f 3a e7 f8 ac d8 69 b6 03 39 9c 19 a9

*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962: 88:43:e1:4f:ab:39 Disabling re-auth since PMK lifetime can take care of same.
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962: 88:43:e1:4f:ab:39 CCKM: Create a global PMK cache entry
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962: 88:43:e1:4f:ab:39 Sending EAP-Success to mobile 88:43:e1:4f:ab:39 (EAP Id 170)
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.963: Including PMKID in M1  (16)

*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.963:      [0000] 6b 25 86 3f 3a e7 f8 ac d8 69 b6 03 39 9c 19 a9

*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.963: 88:43:e1:4f:ab:39 Starting key exchange to mobile 88:43:e1:4f:ab:39, data packets will be dropped
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.963: 88:43:e1:4f:ab:39 Sending EAPOL-Key Message to mobile 88:43:e1:4f:ab:39
                                                                                                                    state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.963: 88:43:e1:4f:ab:39 Entering Backend Auth Success state (id=170) for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.963: 88:43:e1:4f:ab:39 Received Auth Success while in Authenticating state for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.963: 88:43:e1:4f:ab:39 dot1x - moving mobile 88:43:e1:4f:ab:39 into Authenticated state
*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.013: 88:43:e1:4f:ab:39 Received EAPOL-Key from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.013: 88:43:e1:4f:ab:39 Received EAPOL-key in PTK_START state (message 2) from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.013: 88:43:e1:4f:ab:39 CCKM: Sending cache add
*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.013: 88:43:e1:4f:ab:39 Stopping retransmission timer for mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.014: 88:43:e1:4f:ab:39 Sending EAPOL-Key Message to mobile 88:43:e1:4f:ab:39
                                                                                                                    state PTKINITNEGOTIATING (message 3), replay counter 00.00.00.00.00.00.00.01
*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.061: 88:43:e1:4f:ab:39 Received EAPOL-Key from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.061: 88:43:e1:4f:ab:39 Received EAPOL-key in PTKINITNEGOTIATING state (message 4) from mobile 88:43:e1:4f:ab:39
*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.061: 88:43:e1:4f:ab:39 apfMs1xStateInc
*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.061: 88:43:e1:4f:ab:39 10.107.38.121 8021X_REQD (3) Change state to L2AUTHCOMPLETE (4) last state RUN (20)

*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.061: 88:43:e1:4f:ab:39 10.107.38.121 L2AUTHCOMPLETE (4) DHCP required on AP a0:cf:5b:c3:a8:90 vapId 14 apVapId 3for this client
*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.061: 88:43:e1:4f:ab:39 Not Using WMM Compliance code qosCap 0f
*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.061: 88:43:e1:4f:ab:39 10.107.38.121 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP a0:cf:5b:c3:a8:90 vapId 14 apVapId 3
*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.061: 88:43:e1:4f:ab:39 apfMsRunStateInc
*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.061: 88:43:e1:4f:ab:39 10.107.38.121 L2AUTHCOMPLETE (4) Change state to RUN (20) last state RUN (20)

*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.062: 88:43:e1:4f:ab:39 10.107.38.121 RUN (20) Reached PLUMBFASTPATH: from line 4864
*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.062: 88:43:e1:4f:ab:39 Stopping retransmission timer for mobile 88:43:e1:4f:ab:39

6 REPLIES
Cisco Employee

Re: Wifi phone 7925 packet dropped when roaming between APs

could you post the complete couple of roam between AP1 - AP2 and vice-versa.

phone code ?

WLC code ?

is it central auth?

HREAP local switching

WPA2-802.1x+cckm

#Disable dhcp addr. required on wlan's advanced tab, if not already.

#CCKM require to have hreap APs on hreap group, configure if not already.

not caching the pmkid. it could be false positive also.

*apfMsConnTask_7: Jun 27 09:52:25.497: 88:43:e1:4f:ab:39 Received RSN IE with 0 PMKIDs from mobile 88:43:e1:4f:ab:39

wlc>show pmk-cache all

shouldn't it 'reassociation received'. it looks like fresh assocation or smooth roaming didn't happen.

*apfMsConnTask_7: Jun 27 09:52:25.496: 88:43:e1:4f:ab:39 Association received from mobile on AP a0:cf:5b:c3:a8:90

*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962: 88:43:e1:4f:ab:39 Creating a  PKC PMKID Cache entry for station 88:43:e1:4f:ab:39 (RSN 2)

*Dot1x_NW_MsgTask_1:  Jun 27 09:52:26.962: 88:43:e1:4f:ab:39 Adding BSSID a0:cf:5b:c3:a8:9d  to PMKID cache for station 88:43:e1:4f:ab:39

*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962: New PMKID: (16)

*Dot1x_NW_MsgTask_1: Jun 27 09:52:26.962:      [0000] 6b 25 86 3f 3a e7 f8 ac d8 69 b6 03 39 9c 19 a9

Time taken between 'eap request' and 'run' is 1.5 sec. it should be in msec.

*dot1xMsgTask: Jun 27 09:52:25.554: 88:43:e1:4f:ab:39 Sending EAP-Request/Identity to mobile 88:43:e1:4f:ab:39 (EAP Id 1)

*Dot1x_NW_MsgTask_1: Jun 27 09:52:27.061: 88:43:e1:4f:ab:39 10.107.38.121 L2AUTHCOMPLETE (4) Change state to RUN (20) last state RUN (20)

Wifi phone 7925 packet dropped when roaming between APs

Roy,

Besides Saravanan hints about (using HREAP groups and CCKM), I want to ask if your two APs are joining same WLC or different WLCs?

Have you made a site survey to decide cell overlapping and minimum edge RSSI that is needed for the cisco phone to work properly?

Thanks.

Amjad

Rating useful replies is more useful than saying "Thank you"
New Member

Wifi phone 7925 packet dropped when roaming between APs

Hi Amjad,  thanks for the reply. 

I have to admit that I did not do much site survey, since this is samll brach office and the distance between APs  is around than 15 meters.   But I can confirm that we did using H-REAP and CCKM is enalbed, and both APs are registered with same WLC. any other suggestion,  I am using 7921 in My office. we don't have any issue, those deployed in branch office is 7925.  do you guys had any issue with 7925 phone? 

Thanks

Roy

Wifi phone 7925 packet dropped when roaming between APs

Hi Roy,

same firmware version on both phone models? or different version?

Rating useful replies is more useful than saying "Thank you"

Rating useful replies is more useful than saying "Thank you"
Hall of Fame Super Gold

Wifi phone 7925 packet dropped when roaming between APs

792XG should at least be running 1.4(3)SR1.  The roaming improves dramatically starting with code.

New Member

Wifi phone 7925 packet dropped when roaming between APs

Hi all,   I am runing CP7925G-1.4.2.LOADS on wifi phone , will try to  update and see how it goes... thanks

1181
Views
5
Helpful
6
Replies