Mobile Computer Zebra - Disconnection - Mobility Express 18.5.131

[Welcome2008]

Hi,

I recently bought a new android terminal (Zebra MC2700) which unfortunately has disconnection problems causing the connection to be lost with an As400 client (Mocha app), my network is made up of several devices.

AIR-AP1852E-E-K9 (4ap) AIR-CAP1602I-E-K9 (2ap) AIR-CAP1602E-E-K9 (2ap)

After sending the logs to Zebra Support for analysis, I am prompted to have the APs checked and firmware updated.

I wonder if by purchasing a SmartNet support I can solve the disconnection problem or if I will only be able to get the firmware update from Cisco and not solve the actual problem!

[Scott Fella]

Smartnet allows you to open a support case with TAC and also provide access to the downloads for your devices.  With terminals like these in a warehouse environment as an example, is hard to troubleshoot without additional information.  Software is not always the fix.  Testing prior to putting the device into production would identify most issues and that is where you can also test various images.  Understanding if you have any existing issues from users also helps.  

1. Was there a site survey performed to identify ap locations, mounting, and power settings
2. Have you tested with other devices on the same SSID to see if roaming is working and if the device is not disconnecting from the SSID
3. Have you validated your WLAN configuration against what the device manufacturer recommends?
4. Have you asked users in that location if they have issue with wireless using any other device
5. You able to replicate the issue and is the issue roaming from one ap to another or a specific location

You need to provide some information on what you already did for troubleshooting as that makes it easy.  Start to eliminate variables.

[Welcome2008]

1. Yes, the Aps are installed perfectly.
2. Yes, other devices of different brands and different operating systems (Zebra Android, Datalogic Windows Ce 6) are connected in the same network, in the same SSID.
With windows ce devices never had any disconnection issues, but they also use a different client than android (telnet ce for windows ce, mocha app for android)

[Scott Fella]

If you have no other issues and user experience on wireless at that location, then I would have to assume that there is a setting or firmware on the device that is causing the issue.  The device MC2700 has the latest recommended version?  

So Zebra is recommending to update the ap's?  Have they reviewed your SSID configuration and the code you are running?  What are they seeing from the logs? 

[Welcome2008]

This is the response of Zebra Support (2 Level).
The timed out isn't a problem, probabily the mobile computer is out range (work shift finished)
Zebra support made me update to the latest android release for their device but the problem was not solved.

1. Frequent WIFI reconnection - Due to Low RSSI roam trigger -> Expected behavior -> suggestion: to keep the environment with good signal strength.
             
              Roaming sequence: LOW_RSSI Roam Trigger (Once RSSI reaches -65 dBm) -> ROAM_SCAN -> RESULTS -> Select candidate based on highest roam score.
              Other Points:
              • We cannot directly compare zebra device with other OS devices -> complete roam logic will be different.
              • Signal strength analysis of the Work area could help to ensure keeping good RSSI environment -> to avoid frequent roaming and other disturbances.
              • There is no disconnection or roaming delay happened -> even though device reconnected frequently because of bad signal strength of the APs.
              • Our device roaming threshold is -65 dBm, it need not be same on other devices, to hold the connection.
                  But our device will not disconnect after reaching roaming threshold, it will only do background scanning and try to roam to a better candidate.
             
              Note: If no APs are available during this scan and the currently connected APs signal strength goes worst, it will disconnect with reason as No AP found.
                           
2. One time Disconnection -> EAPOL M1 timed out -> needs to be debugged from AP vendor.

Below are the analysis prints from logs-16-12

12-16 09:07:57.449  1727  1943 D WifiClientModeImpl:  L2ConnectedState screen=on 2 0 "XXXX" e0:89:9d:5a:14:f0 rssi=-73

[09:07:59.150382] wlan: [1998:I:WMA] [09:07:54.508000] [ROAM_TRIGGER]: VDEV[0] Reason: "LOW RSSI" Sub-Reason: FULL SCANCur_rssi_threshold: 0 [09:07:59.150412] wlan: [1998:I:WMA] [09:07:54.508000] [ROAM_SCAN]: VDEV[0] Scan_type: FULL next_rssi_threshold: 26 dBm

[09:07:59.150445] wlan: [1998:I:WMA]      AP BSSID           TSTAMP       CH   TY  ETP  RSSI/SCR CU%/SCR TOT_SCR
[09:07:59.150483] wlan: [1998:I:WMA] e0XXX:f0 [09:07:54.508000] 2462 P_AP    0  69/0     0/0     2325
[09:07:59.150509] wlan: [1998:I:WMA] 00:XXXXe:e0 [09:07:54.516000] 2412 C_AP   56  58/0    13/0     4400
[09:07:59.150535] wlan: [1998:I:WMA] e0:XXXX:50 [09:07:54.617000] 2437 C_AP   50  74/0    21/0     1490
[09:07:59.150561] wlan: [1998:I:WMA] 34:XXa:d0 [09:07:54.689000] 2462 C_AP   30  73/0    53/0     1490
[09:07:59.150587] wlan: [1998:I:WMA] 00:XXX:e0 [09:07:54.691000] 2462 C_AP   52  79/0    20/0     1130
[09:07:59.150612] wlan: [1998:I:WMA] 00:XX5:80 [09:07:54.623000] 2437 C_AP   27  89/0     8/0      750

[09:07:59.150638] wlan: [1998:I:WMA] [09:07:59.142000] [ROAM_RESULT]: VDEV[0] FAILED Reason: EAPOL M1 timed out

[09:07:59.150668] wlan: [1998:I:WMA] [09:07:55.130000] [NEIGH_RPT_REQ] VDEV[0] [09:07:59.150686] wlan: [1998:I:WMA] NEIGH_RPT No response received from AP

[09:07:59.163998] wlan: [1998:I:HDD] Disconnect reason: 1 WLAN_REASON_UNSPECIFIED vendor: 2 QCA_DISCONNECT_REASON_EXTERNAL_ROAM_FAILURE LG: 1

12-16 09:07:59.173  2170  2170 I wpa_supplicant: wlan0: CTRL-EVENT-DISCONNECTED bssid=e0:8XXXX:f0 reason=1 locally_generated=1

This is the debug log of the Mobility express, by MAC client (Zebra mobile computer)

*apfReceiveTask: Jan 10 14:57:32.090: 78:b8:d6:a9:27:f1 Recevied management frame REASSOCIATION REQUEST on BSSID 00:3c:10:6b:d3:c0 destination addr 00:3c:10:6b:d3:c0
*apfMsConnTask_0: Feb 14 14:57:32.090: 78:b8:d6:a9:27:f1 Processing assoc-req station:78:b8:d6:a9:27:f1 AP:00:3c:10:6b:d3:c0-00 ssid : XXXXX thread:821fdd0
*apfMsConnTask_0: Feb 14 14:57:32.090: 78:b8:d6:a9:27:f1 Station: 78:B8:D6:A9:27:F1 trying to join WLAN with RSSI -107. Checking for XOR roam conditions on AP: 00:3C:10:6B:D3:C0 Slot: 0
*apfMsConnTask_0: Feb 14 14:57:32.090: 78:b8:d6:a9:27:f1 Station: 78:B8:D6:A9:27:F1 is associating to AP 00:3C:10:6B:D3:C0 which is not XOR roam capable
*apfMsConnTask_0: Feb 14 14:57:32.090: 78:b8:d6:a9:27:f1 Setting RTTS enabled to 0
*apfMsConnTask_0: Feb 14 14:57:32.090: 78:b8:d6:a9:27:f1 Reassociation received from mobile on BSSID 00:3c:10:6b:d3:c0 AP AP003C.106A.6020
*apfMsConnTask_0: Feb 14 14:57:32.090: 78:b8:d6:a9:27:f1 Station: 78:B8:D6:A9:27:F1 trying to join WLAN with RSSI -107. Checking for XOR roam conditions on AP: 00:3C:10:6B:D3:C0 Slot: 0
*apfMsConnTask_0: Feb 14 14:57:32.090: 78:b8:d6:a9:27:f1 Station: 78:B8:D6:A9:27:F1 is associating to AP 00:3C:10:6B:D3:C0 which is not XOR roam capable
*apfMsConnTask_0: Feb 14 14:57:32.090: 78:b8:d6:a9:27:f1 Global 200 Clients are allowed to AP radio

*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 Max Client Trap Threshold: 0 cur: 0

*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 Rf profile 600 Clients are allowed to AP wlan

*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 override for default ap group, marking intgrp NULL
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 apfApplyWlanPolicy: Apply WLAN Policy over PMIPv6 Client Mobility Type, Tunnel User - 0
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 In processSsidIE:6954 setting Central switched to FALSE
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 Set Clinet MSCB as Central Association Disabled
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 Applying site-specific Local Bridging override for station 78:b8:d6:a9:27:f1 - vapId 1, site 'default-group', interface 'management'
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 Applying Local Bridging Interface Policy for station 78:b8:d6:a9:27:f1 - vlan 0, interface id 0, interface 'management'
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 processSsidIE statusCode is 0 and status is 0
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 processSsidIE ssid_done_flag is 0 finish_flag is 0
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 STA - rates (8): 130 132 139 150 140 146 152 36 48 72 96 108 0 0 0 0
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 suppRates statusCode is 0 and gotSuppRatesElement is 1
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 STA - rates (12): 130 132 139 150 140 146 152 36 48 72 96 108 0 0 0 0
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 extSuppRates statusCode is 0 and gotExtSuppRatesElement is 1
*apfMsConnTask_0: Feb 14 14:57:32.091: RSNIE in Assoc. Req.: (20)

*apfMsConnTask_0: Feb 14 14:57:32.091: [0000] 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f

*apfMsConnTask_0: Feb 14 14:57:32.091: [0016] ac 02 00 00

*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 Processing RSN IE type 48, length 20 for mobile 78:b8:d6:a9:27:f1
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 Selected Unicast cipher CCMP128 for client device
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 Received 802.11i PSK key management suite, enabling Authentication
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 RSN Capabilities: 0
*apfMsConnTask_0: Feb 14 14:57:32.091: 78:b8:d6:a9:27:f1 Marking Mobile as non-11w Capable
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 Received RSN IE with 0 PMKIDs from mobile 78:b8:d6:a9:27:f1
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 pemApfDeleteMobileStation2: APF_MS_PEM_WAIT_L2_AUTH_COMPLETE = 0.
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 the value of url acl preserve flag is 1 for mobile 78:b8:d6:a9:27:f1 (caller pem_api.c:4921)
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 192.168.XX.246 RUN (20) Deleted mobile LWAPP rule on AP [00:3c:10:6b:d5:80]
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 Succesfully freed AID 1, slot 0 on AP 00:3c:10:6b:d5:80, #client on this slot 0
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 New ctxOwnerMwarIp: 192.168.XX.230 New ctxOwnerApMac: 00:3C:10:6B:D3:C0 New ctxOwnerApEthMac: 00:3C:10:6A:60:90 New ctxOwnerApSlotId: 0
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 Updated location for station old AP 00:3c:10:6b:d5:80 oldSlot 0, new AP 00:3c:10:6b:d3:c0 newSlot 0, AID 0 MsType 0 MobilityRole 1
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 Assigning flex webauth ACL ID :65535 for vlan : 1
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 Updating AID for REAP AP Client 00:3c:10:6b:d3:c0 - AID ===> 1
*spamApTask0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 Delete Mobile request on slot 0 sent to the AP 00:3c:10:6b:d5:80 IP: 192.168.XX.238:5264

*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 apfMs1xStateDec
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 192.168.XX.246 RUN (20) Change state to START (0) last state RUN (20)

*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 pemApfAddMobileStation2: APF_MS_PEM_WAIT_L2_AUTH_COMPLETE = 0.
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 the value of url acl preserve flag is 0 for mobile 78:b8:d6:a9:27:f1 (caller pem_api.c:3494)
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 192.168.XX.246 START (0) Initializing policy
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 192.168.XX.246 START (0) Change state to AUTHCHECK (2) last state START (0)

*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 apfVapSecurity=0x40004000 L2=16384 SkipWeb=0
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 AuthenticationRequired = 1
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 192.168.XX.246 AUTHCHECK (2) Change state to 8021X_REQD (3) last state AUTHCHECK (2)

*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 Encryption policy is set to 0x80000001
*apfMsConnTask_0: Feb 14 14:57:32.092: 78:b8:d6:a9:27:f1 192.168.XX.246 8021X_REQD (3) Client already has IP 192.168.XX.246, DHCP Not required on AP 00:3c:10:6b:d3:c0 vapId 1 apVapId 1
*apfMsConnTask_0: Feb 14 14:57:32.093: 78:b8:d6:a9:27:f1 Not Using WMM Compliance code qosCap 00
*apfMsConnTask_0: Feb 14 14:57:32.093: 78:b8:d6:a9:27:f1 flex webauth acl id to be sent :65535 name : client acl id : 65535
*apfMsConnTask_0: Feb 14 14:57:32.093: 78:b8:d6:a9:27:f1 Vlan while overriding the policy = -1
*apfMsConnTask_0: Feb 14 14:57:32.093: 78:b8:d6:a9:27:f1 sending to spamAddMobile vlanId -1 aclName = , flexAclId 65535

*apfMsConnTask_0: Feb 14 14:57:32.093: 78:b8:d6:a9:27:f1 192.168.XX.246 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 00:3c:10:6b:d3:c0 vapId 1 apVapId 1 flex-acl-name:
*apfMsConnTask_0: Feb 14 14:57:32.093: 78:b8:d6:a9:27:f1 apfPemAddUser2 (apf_policy.c:423) Changing state for mobile 78:b8:d6:a9:27:f1 on AP 00:3c:10:6b:d3:c0 from Associated to Associated

*apfMsConnTask_0: Feb 14 14:57:32.095: 78:b8:d6:a9:27:f1 apfPemAddUser2:session timeout forstation 78:b8:d6:a9:27:f1 - Session Tout 0, apfMsTimeOut '0' and sessionTimerRunning flag is 0
*apfMsConnTask_0: Feb 14 14:57:32.095: 78:b8:d6:a9:27:f1 Stopping deletion of Mobile Station: (callerId: 48)
*apfMsConnTask_0: Feb 14 14:57:32.095: 78:b8:d6:a9:27:f1 Func: apfPemAddUser2, Ms Timeout = 0, Session Timeout = 0

*apfMsConnTask_0: Feb 14 14:57:32.095: 78:b8:d6:a9:27:f1 Sending assoc-resp with status 0 station:78:b8:d6:a9:27:f1 AP:00:3c:10:6b:d3:c0-00 on apVapId 1
*apfMsConnTask_0: Feb 14 14:57:32.096: 78:b8:d6:a9:27:f1 Sending Assoc Response (status: '0') to station on AP AP003C.106A.6020 on BSSID 00:3c:10:6b:d3:c0 ApVapId 1 Slot 0, mobility role 1
*apfMsConnTask_0: Feb 14 14:57:32.096: 78:b8:d6:a9:27:f1 apfProcessAssocReq (apf_80211.c:11927) Changing state for mobile 78:b8:d6:a9:27:f1 on AP 00:3c:10:6b:d3:c0 from Associated to Associated

*spamApTask0: Feb 14 14:57:32.096: 78:b8:d6:a9:27:f1 Add SGT:0 to AP 00:3c:10:6b:d3:c0
*spamApTask0: Feb 14 14:57:32.096: 78:b8:d6:a9:27:f1 Add CTS mobile SGT - Encoded the capwap payload for the mobile with SGT 0
*spamApTask0: Feb 14 14:57:32.097: 78:b8:d6:a9:27:f1 Successful transmission of LWAPP Add-Mobile to AP 00:3c:10:6b:d3:c0
*spamApTask0: Feb 14 14:57:32.097: 78:b8:d6:a9:27:f1 Setting ADD_MOBILE (idx 0, seqno 0, action 1, count 674787259) ack state for STA on AP 00:3c:10:6b:d3:c0
*spamApTask0: Feb 14 14:57:32.102: 78:b8:d6:a9:27:f1 Received ADD_MOBILE ack - Initiating 1x to STA 78:b8:d6:a9:27:f1 (idx 22)
*spamApTask0: Feb 14 14:57:32.102: 78:b8:d6:a9:27:f1 APF Initiating 1x to STA 78:b8:d6:a9:27:f1
*spamApTask0: Feb 14 14:57:32.102: 78:b8:d6:a9:27:f1 Sent dot1x auth initiate message for mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.102: 78:b8:d6:a9:27:f1 dot1xProcessInitiate1XtoMobile to mobile station 78:b8:d6:a9:27:f1 (mscb 108, msg 108)
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.102: 78:b8:d6:a9:27:f1 reauth_sm state transition 0 ---> 0 for mobile 78:b8:d6:a9:27:f1 at 1x_reauth_sm.c:53
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.102: 78:b8:d6:a9:27:f1 Normal psk client, full auth
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.102: 78:b8:d6:a9:27:f1 Created PKC PMK Cache entry for station 78:b8:d6:a9:27:f1 (RSN 2)
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.102: 78:b8:d6:a9:27:f1 Resetting MSCB PMK Cache Entry @index 0 for station 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.102: 78:b8:d6:a9:27:f1 Removing BSSID 00:3c:10:6b:d5:80 from PMKID cache of station 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.102: 78:b8:d6:a9:27:f1 Setting active key cache index 0 ---> 8
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.102: 78:b8:d6:a9:27:f1 Setting active key cache index 8 ---> 0
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.102: 78:b8:d6:a9:27:f1 Created PMKID PMK Cache for BSSID 00:3c:10:6b:d3:c0 at index 0 for station 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.102: New PMKID: (16)

*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: [0000] 0a b3 9c f1 94 ab 7e e2 96 03 b7 d8 ce 6d 43 f7

*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: 78:b8:d6:a9:27:f1 Initiating RSN PSK to mobile 78:b8:d6:a9:27:f1keyMgmtType : 0
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: 78:b8:d6:a9:27:f1 unsetting PmkIdValidatedByAp
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: 78:b8:d6:a9:27:f1 EAP-PARAM Debug - eap-params for Wlan-Id :1 is disabled - applying Global eap timers and retries
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: 78:b8:d6:a9:27:f1 Disable re-auth, use PMK lifetime.
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: 78:b8:d6:a9:27:f1 dot1x - moving mobile 78:b8:d6:a9:27:f1 into Force Auth state
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: 78:b8:d6:a9:27:f1 Skipping EAP-Success to mobile 78:b8:d6:a9:27:f1 (encryptBit:0)
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: 78:b8:d6:a9:27:f1 key Desc Version FT - 0

*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: 78:b8:d6:a9:27:f1 Found an cache entry for BSSID 00:3c:10:6b:d3:c0 in PMKID cache at index 0 of station 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: 78:b8:d6:a9:27:f1 Found an cache entry for BSSID 00:3c:10:6b:d3:c0 in PMKID cache at index 0 of station 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: Including PMKID in M1 (16)

*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: [0000] 0a b3 9c f1 94 ab 7e e2 96 03 b7 d8 ce 6d 43 f7

*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: M1 - Key Data: (22)

*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: [0000] dd 14 00 0f ac 04 0a b3 9c f1 94 ab 7e e2 96 03

*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: 78:b8:d6:a9:27:f1 Starting key exchange to mobile 78:b8:d6:a9:27:f1, data packets will be dropped
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: 78:b8:d6:a9:27:f1 Sending EAPOL-Key Message to mobile 78:b8:d6:a9:27:f1
state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.103: 78:b8:d6:a9:27:f1 Allocating EAP Pkt for retransmission to mobile 78:b8:d6:a9:27:f1
*spamApTask0: Feb 14 14:57:32.107: 78:b8:d6:a9:27:f1 apfUpdateDeleteAckInMscb (apf_api.c:54068) Expiring Mobile!
*CAPWAP DATA: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 validating eapol pkt: key version = 2
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 Received EAPOL-Key from mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 Ignoring invalid EAPOL version (1) in EAPOL-key message from mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 key Desc Version FT - 0

*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 Received EAPOL-key in PTK_START state (message 2) from mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 Encryption Policy: 4, PTK Key Length: 48
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 Received valid MIC in EAPOL Key Message M2!!!!!
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 Compare RSN IE in association and EAPOL-M2 frame(Skip pmkIdLen:0,and grpMgmtCipherLen:0)
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 Dumping RSNIE received in Association request:
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 00000000: 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 0...............
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 00000010: 00 0f ac 02 00 00 ......
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 Dumping RSNIE received in EAPOL M2 :
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 00000000: 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ................
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 00000010: ac 02 00 00 ....
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 Stopping retransmission timer for mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 key Desc Version FT - 0

*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 key Desc Version FT - 0

*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 Sending EAPOL-Key Message to mobile 78:b8:d6:a9:27:f1
state PTKINITNEGOTIATING (message 3), replay counter 00.00.00.00.00.00.00.01
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.114: 78:b8:d6:a9:27:f1 Reusing allocated memory for EAP Pkt for retransmission to mobile 78:b8:d6:a9:27:f1
*CAPWAP DATA: Feb 14 14:57:32.123: 78:b8:d6:a9:27:f1 validating eapol pkt: key version = 2
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.123: 78:b8:d6:a9:27:f1 Received EAPOL-Key from mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.123: 78:b8:d6:a9:27:f1 Ignoring invalid EAPOL version (1) in EAPOL-key message from mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.123: 78:b8:d6:a9:27:f1 key Desc Version FT - 0

*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.123: 78:b8:d6:a9:27:f1 Received EAPOL-key in PTKINITNEGOTIATING state (message 4) from mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.123: 78:b8:d6:a9:27:f1 Stopping retransmission timer for mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.123: 78:b8:d6:a9:27:f1 Freeing EAP Retransmit Bufer for mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.123: 78:b8:d6:a9:27:f1 apfMs1xStateInc
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.123: 78:b8:d6:a9:27:f1 192.168.XX.246 8021X_REQD (3) Change state to L2AUTHCOMPLETE (4) last state 8021X_REQD (3)

*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.124: 78:b8:d6:a9:27:f1 192.168.XX.246 L2AUTHCOMPLETE (4) Client already has IP 192.168.XX.246, DHCP Not required on AP 00:3c:10:6b:d3:c0 vapId 1 apVapId 1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.124: 78:b8:d6:a9:27:f1 Not Using WMM Compliance code qosCap 00
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.124: 78:b8:d6:a9:27:f1 flex webauth acl id to be sent :65535 name : client acl id : 65535
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.124: 78:b8:d6:a9:27:f1 Vlan while overriding the policy = -1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.124: 78:b8:d6:a9:27:f1 sending to spamAddMobile vlanId -1 aclName = , flexAclId 65535

*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.124: 78:b8:d6:a9:27:f1 192.168.XX.246 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP 00:3c:10:6b:d3:c0 vapId 1 apVapId 1 flex-acl-name:
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.124: 78:b8:d6:a9:27:f1 apfMsRunStateInc
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.124: 78:b8:d6:a9:27:f1 192.168.XX.246 L2AUTHCOMPLETE (4) Change state to RUN (20) last state L2AUTHCOMPLETE (4)

*spamApTask0: Feb 14 14:57:32.124: 78:b8:d6:a9:27:f1 Add SGT:0 to AP 00:3c:10:6b:d3:c0
*spamApTask0: Feb 14 14:57:32.124: 78:b8:d6:a9:27:f1 Add CTS mobile SGT - Encoded the capwap payload for the mobile with SGT 0
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.124: 78:b8:d6:a9:27:f1 192.168.XX.246 RUN (20) Reached PLUMBFASTPATH: from line 7154, null
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.125: 78:b8:d6:a9:27:f1 192.168.XX.246 RUN (20) No 11v BTM
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.125: 78:b8:d6:a9:27:f1 192.168.XX.246 RUN (20) NO release MSCB
*Dot1x_NW_MsgTask_0: Feb 14 14:57:32.125: 78:b8:d6:a9:27:f1 Successfully Plumbed PTK session Keysfor mobile 78:b8:d6:a9:27:f1
*spamApTask0: Feb 14 14:57:32.125: 78:b8:d6:a9:27:f1 Successful transmission of LWAPP Add-Mobile to AP 00:3c:10:6b:d3:c0
*apfReceiveTask: Feb 14 14:57:32.171: 78:b8:d6:a9:27:f1 WcdbClientUpdate: IP Binding from WCDB ip_learn_type 2, add_or_delete 1
*apfReceiveTask: Feb 14 14:57:32.171: 78:b8:d6:a9:27:f1 IPv4 Addr: 192:168:98:246

*apfReceiveTask: Feb 14 14:57:32.171: 78:b8:d6:a9:27:f1 Static IP client associated to interface management which can support client subnet.
*apfReceiveTask: Feb 14 14:57:36.657: 78:b8:d6:a9:27:f1 Recevied management frame ASSOCIATION REQUEST on BSSID 00:3c:10:6b:d5:80 destination addr 00:3c:10:6b:d5:80
*apfMsConnTask_0: Feb 14 14:57:36.658: 78:b8:d6:a9:27:f1 Processing assoc-req station:78:b8:d6:a9:27:f1 AP:00:3c:10:6b:d5:80-00 ssid : XXXX thread:821fdd0
*apfMsConnTask_0: Feb 14 14:57:36.658: 78:b8:d6:a9:27:f1 Station: 78:B8:D6:A9:27:F1 trying to join WLAN with RSSI -107. Checking for XOR roam conditions on AP: 00:3C:10:6B:D5:80 Slot: 0
*apfMsConnTask_0: Feb 14 14:57:36.658: 78:b8:d6:a9:27:f1 Station: 78:B8:D6:A9:27:F1 is associating to AP 00:3C:10:6B:D5:80 which is not XOR roam capable
*apfMsConnTask_0: Feb 14 14:57:36.658: 78:b8:d6:a9:27:f1 Setting RTTS enabled to 0
*apfMsConnTask_0: Feb 14 14:57:36.658: 78:b8:d6:a9:27:f1 Association received from mobile on BSSID 00:3c:10:6b:d5:80 AP AP003C.106A.6090
*apfMsConnTask_0: Feb 14 14:57:36.658: 78:b8:d6:a9:27:f1 Station: 78:B8:D6:A9:27:F1 trying to join WLAN with RSSI -107. Checking for XOR roam conditions on AP: 00:3C:10:6B:D5:80 Slot: 0
*apfMsConnTask_0: Feb 14 14:57:36.658: 78:b8:d6:a9:27:f1 Station: 78:B8:D6:A9:27:F1 is associating to AP 00:3C:10:6B:D5:80 which is not XOR roam capable
*apfMsConnTask_0: Feb 14 14:57:36.658: 78:b8:d6:a9:27:f1 Global 200 Clients are allowed to AP radio

*apfMsConnTask_0: Feb 14 14:57:36.658: 78:b8:d6:a9:27:f1 Max Client Trap Threshold: 0 cur: 0

*apfMsConnTask_0: Feb 14 14:57:36.658: 78:b8:d6:a9:27:f1 Rf profile 600 Clients are allowed to AP wlan

*apfMsConnTask_0: Feb 14 14:57:36.658: 78:b8:d6:a9:27:f1 override for default ap group, marking intgrp NULL
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 apfApplyWlanPolicy: Apply WLAN Policy over PMIPv6 Client Mobility Type, Tunnel User - 0
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 In processSsidIE:6954 setting Central switched to FALSE
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 Set Clinet MSCB as Central Association Disabled
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 Applying site-specific Local Bridging override for station 78:b8:d6:a9:27:f1 - vapId 1, site 'default-group', interface 'management'
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 Applying Local Bridging Interface Policy for station 78:b8:d6:a9:27:f1 - vlan 0, interface id 0, interface 'management'
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 processSsidIE statusCode is 0 and status is 0
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 processSsidIE ssid_done_flag is 0 finish_flag is 0
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 STA - rates (8): 130 132 139 150 140 146 152 36 48 72 96 108 0 0 0 0
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 suppRates statusCode is 0 and gotSuppRatesElement is 1
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 STA - rates (12): 130 132 139 150 140 146 152 36 48 72 96 108 0 0 0 0
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 extSuppRates statusCode is 0 and gotExtSuppRatesElement is 1
*apfMsConnTask_0: Feb 14 14:57:36.659: RSNIE in Assoc. Req.: (20)

*apfMsConnTask_0: Feb 14 14:57:36.659: [0000] 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f

*apfMsConnTask_0: Feb 14 14:57:36.659: [0016] ac 02 00 00

*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 Processing RSN IE type 48, length 20 for mobile 78:b8:d6:a9:27:f1
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 Selected Unicast cipher CCMP128 for client device
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 Received 802.11i PSK key management suite, enabling Authentication
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 RSN Capabilities: 0
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 Marking Mobile as non-11w Capable
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 Received RSN IE with 0 PMKIDs from mobile 78:b8:d6:a9:27:f1
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 pemApfDeleteMobileStation2: APF_MS_PEM_WAIT_L2_AUTH_COMPLETE = 0.
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 the value of url acl preserve flag is 1 for mobile 78:b8:d6:a9:27:f1 (caller pem_api.c:4921)
*apfMsConnTask_0: Feb 14 14:57:36.659: 78:b8:d6:a9:27:f1 192.168.XX.246 RUN (20) Deleted mobile LWAPP rule on AP [00:3c:10:6b:d3:c0]
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 Succesfully freed AID 1, slot 0 on AP 00:3c:10:6b:d3:c0, #client on this slot 0
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 New ctxOwnerMwarIp: 192.168.XX.230 New ctxOwnerApMac: 00:3C:10:6B:D5:80 New ctxOwnerApEthMac: 00:3C:10:6A:60:20 New ctxOwnerApSlotId: 0
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 Updated location for station old AP 00:3c:10:6b:d3:c0 oldSlot 0, new AP 00:3c:10:6b:d5:80 newSlot 0, AID 0 MsType 0 MobilityRole 1
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 Assigning flex webauth ACL ID :65535 for vlan : 1
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 Updating AID for REAP AP Client 00:3c:10:6b:d5:80 - AID ===> 1
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 apfMsRunStateDec
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 apfMs1xStateDec
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 192.168.XX.246 RUN (20) Change state to START (0) last state RUN (20)

*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 pemApfAddMobileStation2: APF_MS_PEM_WAIT_L2_AUTH_COMPLETE = 0.
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 the value of url acl preserve flag is 0 for mobile 78:b8:d6:a9:27:f1 (caller pem_api.c:3494)
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 192.168.XX.246 START (0) Initializing policy
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 192.168.XX.246 START (0) Change state to AUTHCHECK (2) last state START (0)

*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 apfVapSecurity=0x40004000 L2=16384 SkipWeb=0
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 AuthenticationRequired = 1
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 192.168.XX.246 AUTHCHECK (2) Change state to 8021X_REQD (3) last state AUTHCHECK (2)

*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 Encryption policy is set to 0x80000001
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 192.168.XX.246 8021X_REQD (3) Client already has IP 192.168.XX.246, DHCP Not required on AP 00:3c:10:6b:d5:80 vapId 1 apVapId 1
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 Not Using WMM Compliance code qosCap 00
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 flex webauth acl id to be sent :65535 name : client acl id : 65535
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 Vlan while overriding the policy = -1
*apfMsConnTask_0: Feb 14 14:57:36.660: 78:b8:d6:a9:27:f1 sending to spamAddMobile vlanId -1 aclName = , flexAclId 65535

*spamApTask0: Feb 14 14:57:36.661: 78:b8:d6:a9:27:f1 Setting DEL_MOBILE (seqno 0, action 6) ack state for STA on AP 00:3c:10:6b:d3:c0
*apfMsConnTask_0: Feb 14 14:57:36.661: 78:b8:d6:a9:27:f1 192.168.XX.246 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 00:3c:10:6b:d5:80 vapId 1 apVapId 1 flex-acl-name:
*spamApTask0: Feb 14 14:57:36.661: 78:b8:d6:a9:27:f1 Delete Mobile request on slot 0 sent to the AP 00:3c:10:6b:d3:c0 IP: 192.168.XX.235:5264

*apfMsConnTask_0: Feb 14 14:57:36.661: 78:b8:d6:a9:27:f1 apfPemAddUser2 (apf_policy.c:423) Changing state for mobile 78:b8:d6:a9:27:f1 on AP 00:3c:10:6b:d5:80 from Associated to Associated

*apfMsConnTask_0: Feb 14 14:57:36.661: 78:b8:d6:a9:27:f1 apfPemAddUser2:session timeout forstation 78:b8:d6:a9:27:f1 - Session Tout 0, apfMsTimeOut '0' and sessionTimerRunning flag is 0
*apfMsConnTask_0: Feb 14 14:57:36.661: 78:b8:d6:a9:27:f1 Stopping deletion of Mobile Station: (callerId: 48)
*apfMsConnTask_0: Feb 14 14:57:36.661: 78:b8:d6:a9:27:f1 Sending assoc-resp with status 0 station:78:b8:d6:a9:27:f1 AP:00:3c:10:6b:d5:80-00 on apVapId 1
*apfMsConnTask_0: Feb 14 14:57:36.661: 78:b8:d6:a9:27:f1 Sending Assoc Response (status: '0') to station on AP AP003C.106A.6090 on BSSID 00:3c:10:6b:d5:80 ApVapId 1 Slot 0, mobility role 1
*apfMsConnTask_0: Feb 14 14:57:36.661: 78:b8:d6:a9:27:f1 apfProcessAssocReq (apf_80211.c:11927) Changing state for mobile 78:b8:d6:a9:27:f1 on AP 00:3c:10:6b:d5:80 from Associated to Associated

*spamApTask0: Feb 14 14:57:36.661: 78:b8:d6:a9:27:f1 Add SGT:0 to AP 00:3c:10:6b:d5:80
*spamApTask0: Feb 14 14:57:36.661: 78:b8:d6:a9:27:f1 Add CTS mobile SGT - Encoded the capwap payload for the mobile with SGT 0
*spamApTask0: Feb 14 14:57:36.662: 78:b8:d6:a9:27:f1 Successful transmission of LWAPP Add-Mobile to AP 00:3c:10:6b:d5:80
*spamApTask0: Feb 14 14:57:36.662: 78:b8:d6:a9:27:f1 Setting ADD_MOBILE (idx 0, seqno 0, action 1, count 674787261) ack state for STA on AP 00:3c:10:6b:d5:80
*spamApTask0: Feb 14 14:57:36.668: 78:b8:d6:a9:27:f1 apfUpdateDeleteAckInMscb (apf_api.c:54068) Expiring Mobile!
*spamApTask0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 Received ADD_MOBILE ack - Initiating 1x to STA 78:b8:d6:a9:27:f1 (idx 38)
*spamApTask0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 APF Initiating 1x to STA 78:b8:d6:a9:27:f1
*spamApTask0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 Sent dot1x auth initiate message for mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 dot1xProcessInitiate1XtoMobile to mobile station 78:b8:d6:a9:27:f1 (mscb 109, msg 109)
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 reauth_sm state transition 0 ---> 0 for mobile 78:b8:d6:a9:27:f1 at 1x_reauth_sm.c:53
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 Normal psk client, full auth
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 Created PKC PMK Cache entry for station 78:b8:d6:a9:27:f1 (RSN 2)
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 Resetting MSCB PMK Cache Entry @index 0 for station 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 Removing BSSID 00:3c:10:6b:d3:c0 from PMKID cache of station 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 Setting active key cache index 0 ---> 8
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 Setting active key cache index 8 ---> 0
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 Created PMKID PMK Cache for BSSID 00:3c:10:6b:d5:80 at index 0 for station 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: New PMKID: (16)

*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: [0000] 11 43 cb 6c 05 fa 5b 2f 82 eb e0 e5 4c 14 10 ae

*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 Initiating RSN PSK to mobile 78:b8:d6:a9:27:f1keyMgmtType : 0
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 unsetting PmkIdValidatedByAp
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 EAP-PARAM Debug - eap-params for Wlan-Id :1 is disabled - applying Global eap timers and retries
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 Disable re-auth, use PMK lifetime.
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 dot1x - moving mobile 78:b8:d6:a9:27:f1 into Force Auth state
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 Skipping EAP-Success to mobile 78:b8:d6:a9:27:f1 (encryptBit:0)
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 key Desc Version FT - 0

*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.669: 78:b8:d6:a9:27:f1 Found an cache entry for BSSID 00:3c:10:6b:d5:80 in PMKID cache at index 0 of station 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.670: 78:b8:d6:a9:27:f1 Found an cache entry for BSSID 00:3c:10:6b:d5:80 in PMKID cache at index 0 of station 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.670: Including PMKID in M1 (16)

*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.670: [0000] 11 43 cb 6c 05 fa 5b 2f 82 eb e0 e5 4c 14 10 ae

*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.670: M1 - Key Data: (22)

*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.670: [0000] dd 14 00 0f ac 04 11 43 cb 6c 05 fa 5b 2f 82 eb

*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.670: [0016] e0 e5 4c 14 10 ae

*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.670: 78:b8:d6:a9:27:f1 Starting key exchange to mobile 78:b8:d6:a9:27:f1, data packets will be dropped
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.670: 78:b8:d6:a9:27:f1 Sending EAPOL-Key Message to mobile 78:b8:d6:a9:27:f1
state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.670: 78:b8:d6:a9:27:f1 Allocating EAP Pkt for retransmission to mobile 78:b8:d6:a9:27:f1
*CAPWAP DATA: Feb 14 14:57:36.680: 78:b8:d6:a9:27:f1 validating eapol pkt: key version = 2
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.680: 78:b8:d6:a9:27:f1 Received EAPOL-Key from mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.680: 78:b8:d6:a9:27:f1 Ignoring invalid EAPOL version (1) in EAPOL-key message from mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.680: 78:b8:d6:a9:27:f1 key Desc Version FT - 0

*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.680: 78:b8:d6:a9:27:f1 Received EAPOL-key in PTK_START state (message 2) from mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.680: 78:b8:d6:a9:27:f1 Encryption Policy: 4, PTK Key Length: 48
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.680: 78:b8:d6:a9:27:f1 Successfully computed PTK from PMK!!!
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.680: 78:b8:d6:a9:27:f1 Received valid MIC in EAPOL Key Message M2!!!!!
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.680: 78:b8:d6:a9:27:f1 Compare RSN IE in association and EAPOL-M2 frame(Skip pmkIdLen:0,and grpMgmtCipherLen:0)
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.680: 78:b8:d6:a9:27:f1 Dumping RSNIE received in Association request:
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.680: 00000000: 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 0...............
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.680: 00000010: 00 0f ac 02 00 00 ......
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.680: 78:b8:d6:a9:27:f1 Dumping RSNIE received in EAPOL M2 :
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.681: 00000000: 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ................
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.681: 00000010: ac 02 00 00 ....
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.681: 78:b8:d6:a9:27:f1 Stopping retransmission timer for mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.681: 78:b8:d6:a9:27:f1 key Desc Version FT - 0

*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.681: 78:b8:d6:a9:27:f1 key Desc Version FT - 0

*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.681: 78:b8:d6:a9:27:f1 Sending EAPOL-Key Message to mobile 78:b8:d6:a9:27:f1
state PTKINITNEGOTIATING (message 3), replay counter 00.00.00.00.00.00.00.01
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.681: 78:b8:d6:a9:27:f1 Reusing allocated memory for EAP Pkt for retransmission to mobile 78:b8:d6:a9:27:f1
*CAPWAP DATA: Feb 14 14:57:36.688: 78:b8:d6:a9:27:f1 validating eapol pkt: key version = 2
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.688: 78:b8:d6:a9:27:f1 Received EAPOL-Key from mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.688: 78:b8:d6:a9:27:f1 Ignoring invalid EAPOL version (1) in EAPOL-key message from mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.688: 78:b8:d6:a9:27:f1 key Desc Version FT - 0

*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.688: 78:b8:d6:a9:27:f1 Received EAPOL-key in PTKINITNEGOTIATING state (message 4) from mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.689: 78:b8:d6:a9:27:f1 Stopping retransmission timer for mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.689: 78:b8:d6:a9:27:f1 Freeing EAP Retransmit Bufer for mobile 78:b8:d6:a9:27:f1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.689: 78:b8:d6:a9:27:f1 apfMs1xStateInc
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.689: 78:b8:d6:a9:27:f1 192.168.XX.246 8021X_REQD (3) Change state to L2AUTHCOMPLETE (4) last state 8021X_REQD (3)

*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.689: 78:b8:d6:a9:27:f1 192.168.XX.246 L2AUTHCOMPLETE (4) Client already has IP 192.168.XX.246, DHCP Not required on AP 00:3c:10:6b:d5:80 vapId 1 apVapId 1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.689: 78:b8:d6:a9:27:f1 Not Using WMM Compliance code qosCap 00
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.689: 78:b8:d6:a9:27:f1 flex webauth acl id to be sent :65535 name : client acl id : 65535
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.689: 78:b8:d6:a9:27:f1 Vlan while overriding the policy = -1
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.689: 78:b8:d6:a9:27:f1 sending to spamAddMobile vlanId -1 aclName = , flexAclId 65535

*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.689: 78:b8:d6:a9:27:f1 192.168.XX.246 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP 00:3c:10:6b:d5:80 vapId 1 apVapId 1 flex-acl-name:
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.689: 78:b8:d6:a9:27:f1 apfMsRunStateInc
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.689: 78:b8:d6:a9:27:f1 192.168.XX.246 L2AUTHCOMPLETE (4) Change state to RUN (20) last state L2AUTHCOMPLETE (4)

*spamApTask0: Feb 14 14:57:36.689: 78:b8:d6:a9:27:f1 Add SGT:0 to AP 00:3c:10:6b:d5:80
*spamApTask0: Feb 14 14:57:36.689: 78:b8:d6:a9:27:f1 Add CTS mobile SGT - Encoded the capwap payload for the mobile with SGT 0
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.690: 78:b8:d6:a9:27:f1 192.168.XX.246 RUN (20) Reached PLUMBFASTPATH: from line 7154, null
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.690: 78:b8:d6:a9:27:f1 192.168.XX.246 RUN (20) No 11v BTM
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.690: 78:b8:d6:a9:27:f1 192.168.XX.246 RUN (20) NO release MSCB
*Dot1x_NW_MsgTask_0: Feb 14 14:57:36.690: 78:b8:d6:a9:27:f1 Successfully Plumbed PTK session Keysfor mobile 78:b8:d6:a9:27:f1
*spamApTask0: Feb 14 14:57:36.690: 78:b8:d6:a9:27:f1 Successful transmission of LWAPP Add-Mobile to AP 00:3c:10:6b:d5:80
*apfReceiveTask: Feb 14 14:57:36.825: 78:b8:d6:a9:27:f1 WcdbClientUpdate: IP Binding from WCDB ip_learn_type 2, add_or_delete 1
*apfReceiveTask: Feb 14 14:57:36.825: 78:b8:d6:a9:27:f1 IPv4 Addr: 192:168:98:246

*apfReceiveTask: Feb 14 14:57:36.826: 78:b8:d6:a9:27:f1 Static IP client associated to interface management which can support client subnet.

[Scott Fella]

Thanks for the additional info.  If including large amount of text, like from a debug, attach that to a file as it helps prevent post from being so long.... that way folks read it:)

From what they mentioned, -65 is a requirement for roaming and decision of neighbors.  So to me, it means that from any given location on the floor, a device should see another ap @ -65.  Have you had a site survey performed and does that show overlapping of -65dbm?  It also seems like these devices are 2.4GHz?  Do they also connect to 5ghz?  If so, you would need to make sure 5GHz meets the manufactures recommendations too.  

Now since this is a warehouse environment???? Take a look at the TX power level of your access points.  If you see them being assigned to a low TX power level, 8 being the lowest and 1 being the highest, it might be due to your access point location/mounting/antennas.  Basically if ap's are line of site in the ceiling, they will reduce the TX power level, they don't know of the power level on the floor.  So this is where yo need to make adjustments to your wireless and either increase your TX power and also look at the data rates to make sure you are achieving good signal, low noise, good data rates, etc. 

If you have Ekahau or AirMagnet site survey tools, you might want to analyze your site yourself, so you can determine if you do have coverage gaps that the new device will encounter.  Just because older or other devices work, you are now introducing a new device with different requirements in which you need to meet in order to have a successful deployment of those new devices.

If you can't achieve that with making adjustments, you might have to add or move access points around at your site.  Again, its best to have a site survey performed unless you have the tools in which you can do that work.

[Scott Fella]

What you can provide also is a floor plan of your site in question also how high are the access points mounted?  It seems like you have a mix of 8 access points with some having external antennas.  Know what antennas you have and the direction they are facing if directional also helps.  Is this a warehouse?  Is there a lot of products that can attenuate the signal?

[Welcome2008]

it 's a warehouse of food and beverage.
the access point are 8/10 meters from the floor.
The area of warehouse is 3.5 square meters.  in the shape of a rectangle
yes, i have 8 AP:
AIR-AP1852E-E-K9 (4ap)
AIR-CAP1602I-E-K9 (2ap)
AIR-CAP1602E-E-K9 (2ap)

[Welcome2008]

Antennas 2.4 GHZ 2 DBI/5 GHZ 4 DBI W RP-TNC
The antennas are perpendicular to the floor.

The Ap without external antennas, they are at 3 meters from the floor, (i added them later)

[Scott Fella]

So a few things to note.  Internal antenna access points are recommended to be mounted in typical office area ceiling heights.  Now its okay to increase that, but not more than 6-7 meters.  Its just the way the antenna is designed to send/receive signal.  External antennas that are direction is fine as long as the angle is adjusted properly to provide the best coverage and coverage for roaming.

So my question is, do you have a site survey documentation to shows you have -65dbm from at least two access points in all areas?  That is what the vendor is pointing to, saying you don't have -65 coverage from an adjacent access point to meet their roaming requirements.

What does the two commands show as far as TX power levels:
wlc show advanced 802.11a summary
wlc show advanced 802.11b summary

Take a look at this command also to see how the ap's hear one another:
show ap auto-rf {802.11a|802.11b}

That way you can go onsite and compare the signal from below the ap's and between the ap's and how the ap's hear each other.  In the end, I think you need to make adjustments based on what you see as far as signal/noise in areas where you really need these devices to work.

[Scott Fella]

Also go through this analyzer to also show you the health:
https://developer.cisco.com/docs/wireless-troubleshooting-tools/#!wireless-config-analyzer/wireless-lan-config-analyzer

[Welcome2008]

The vendor not pointing to have -65 coverage, 

It says :
But our device will not disconnect after reaching roaming threshold, it will only do background scanning and try to roam to a better candidate.
             
              Note: If no APs are available during this scan and the currently connected APs signal strength goes worst, it will disconnect with reason as No AP found.

[Scott Fella]

I know what you mentioned, but if you read it again, at -65 then will scan for a better ap. So what is the signal you have for overlap, -70, -75, -80? 

If no ap's are available, it will not disconnect.  This is typical for all devices, however, it doesn't mean it will won't drop due to poor signal or no signal.  What you tend to see is stickiness to a given ap due to poor roaming.

Provide a site survey to the vendor so that at least they have an idea of the environment and can help you.  The main thing when folks complain about coverage or disconnection issues, everyone wants to know if there was a site survey performed or not.  Because at least, there is documentation to present that can help with areas where you might be experiencing issue.

If you want something quick, listen to the vendor and upgrade to the latest software.  If that doesn't fix it, then at least you eliminated one variable.

[Welcome2008]

AP003C.106A.3AE8
Nearby APs
AP 00:3c:10:6b:d3:c0 slot 0.................. -38 dBm on 11 20MHz (192.168.98.230) AP003C.106A.6020
AP 00:3c:10:6b:d3:e0 slot 0.................. -41 dBm on 1 20MHz (192.168.98.230) AP003C.106A.6028
AP 00:3c:10:6b:d5:80 slot 0.................. -42 dBm on 6 20MHz (192.168.98.230) AP003C.106A.6090
AP 34:a8:4e:bb:7c:e0 slot 0.................. -54 dBm on 11 20MHz (192.168.98.230) AP6c20.560e.31d6
AP e0:89:9d:5a:14:f0 slot 0.................. -47 dBm on 11 20MHz (192.168.98.230) APa0ec.f931.a24c
AP e0:d1:73:1b:92:50 slot 0.................. -52 dBm on 6 20MHz (192.168.98.230) AP881d.fc4b.0119

This is ok ? -54 is best of -65 ?

AP6c20.560e.35b5
Nearby APs
AP 00:3c:10:6b:3e:e0 slot 0.................. -72 dBm on 1 20MHz (192.168.98.230) AP003C.106A.3AE8
AP 00:3c:10:6b:d3:c0 slot 0.................. -72 dBm on 11 20MHz (192.168.98.230) AP003C.106A.6020
AP 00:3c:10:6b:d3:e0 slot 0.................. -71 dBm on 1 20MHz (192.168.98.230) AP003C.106A.6028
AP 00:3c:10:6b:d5:80 slot 0.................. -64 dBm on 6 20MHz (192.168.98.230) AP003C.106A.6090
AP 34:a8:4e:bb:7c:e0 slot 0.................. -93 dBm on 11 20MHz (192.168.98.230) AP6c20.560e.31d6
AP e0:89:9d:5a:14:f0 slot 0.................. -87 dBm on 11 20MHz (192.168.98.230) APa0ec.f931.a24c
AP e0:d1:73:1b:92:50 slot 0.................. -76 dBm on 6 20MHz (192.168.98.230) AP881d.fc4b.0119

This is another Ap. It's ok ? The best value is -64 ..

[Welcome2008]

With the command:
show ap auto-rf 802.11a AP003C.106A.3AE8
only for this Ap.
I do not see the nearby Ap:

RSSI -100 dbm................................ 0 clients
RSSI -92 dbm................................ 0 clients
RSSI -84 dbm................................ 0 clients
RSSI -76 dbm................................ 0 clients
RSSI -68 dbm................................ 0 clients
RSSI -60 dbm................................ 0 clients
RSSI -52 dbm................................ 0 clients
Client Signal To Noise Ratios
SNR 0 dB.................................. 0 clients
SNR 5 dB.................................. 0 clients
SNR 10 dB.................................. 0 clients
SNR 15 dB.................................. 0 clients
SNR 20 dB.................................. 0 clients
SNR 25 dB.................................. 0 clients
SNR 30 dB.................................. 0 clients
SNR 35 dB.................................. 0 clients
SNR 40 dB.................................. 0 clients
SNR 45 dB.................................. 0 clients
Nearby APs
Radar Information
Channel Assignment Information
Current Channel Average Energy............... unknown
Previous Channel Average Energy.............. unknown
Channel Change Count......................... 0
Last Channel Change Time..................... Wed Feb 22 17:46:56 2023
Recommended Best Channel..................... 40
RF Parameter Recommendations
Power Level.................................. 7
RTS/CTS Threshold............................ 2347
Fragmentation Threshold...................... 2346
Antenna Pattern.............................. 0