Clients need to move further from AP to connect successfully.

Stewart Roth · ‎10-29-2012

I have clients using a hand held device that can not connect to a LAP1121G unless they move away from the LWAP. If they attempt to use it in the office they get no connection. If i have the user take the device out into the parking lot they connect and all is well. Problem is they go through a process nightly while the devices are in the office and that process is not completing because of no connectivity. Using WPA-PSK with TKIP Suggestions??

grabonlee · ‎10-29-2012

Most legacy handheld devices and scanners prefer lower data rates and the farther away you are from the AP, the AP rate shifts to lower rates. Since you would want to use the devices in the office, could you manually reduce the power of the AP by more than half and test. From the WLC, choose level 3 under TX power for the AP.

Stewart Roth · ‎10-29-2012

I will do this. Current Tx power was at a 2. Thanks!

Saravanan Lakshmanan · ‎10-29-2012

you can try enabling lower datarate starting from 5.5 until 1 and see what works for that device.

Srin_G · ‎10-29-2012

What antenna you use? Omni or directional? The handheld is g radio or b? we got plenty of handhelds in many warehouses and use patch antennas and found the same issue as well. It could be because of high channel utilization.

Disabling the 1M and 2M helped us a lot and also try disabling the power save mode in the handheld.

Stewart Roth · ‎10-31-2012

Omni. Handheld is using a b radio. I have disabled the 1M and 2M data rates with no change. TX power is at a 6 now. I can get the handhelds to communicate for just a little bit then for no reason they just drop off. I moved the access point to a different WLC with no AP but it currently on it so i can mess with data rates etc without effecting the rest of the network. I have had one of the handhelds sent back for testing but never was able to duplicate the issue.

The WLC it was on have 200+ ap's. I have changed a few settings from searching the internet for similiar issue. I have turned off Aironet IE's, MFP,short preambles. Re-entered teh PSK on the WLC, Changed eapol settings. This is where i am running into issues as shown by the client debug.

Saravanan Lakshmanan · ‎10-31-2012

*spamApTask1: Oct 31 10:02:43.605: 00:02:b3:e1:ee:20 Received Idle-Timeout from AP 00:13:19:40:c7:00, slot 0 for STA 00:02:b3:e1:ee:20

Either wireless client going idle(in this case increase the user idle timeout from WLC's controller tab) or if theywere not idle then you're using an code that has a bug on it. what's the WLC code that sees an issue Vs not seeing this issue.

Saravanan Lakshmanan · ‎10-31-2012

ignore my previous post.

*apfReceiveTask: Oct 31 10:00:04.334: 00:02:b3:e1:ee:20 0.0.0.0 DHCP_REQD (7) Successfully plumbed mobile rule (ACL ID 255)

*pemReceiveTask: Oct 31 10:00:04.334: 00:02:b3:e1:ee:20 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0

#see above, client initially stuck on getting dhcp ip. however, it got an ip and moved the client to run state - see below.

*DHCP Socket Task: Oct 31 10:00:04.608: 00:02:b3:e1:ee:20 DHCP successfully bridged packet to STA

*pemReceiveTask: Oct 31 10:00:04.608: 00:02:b3:e1:ee:20 172.17.3.27 Added NPU entry of type 1, dtlFlags 0x0

#well, why it moved to dot1x from RUN state and removing the client from wlc.

*apfMsConnTask_5: Oct 31 10:01:51.257: 00:02:b3:e1:ee:20 172.17.3.27 AUTHCHECK (2) Change state to 8021X_REQD (3) last state RUN (20)

*pemReceiveTask: Oct 31 10:01:51.258: 00:02:b3:e1:ee:20 172.17.3.27 Removed NPU entry.

#client is not holding on to M1 key from AP. this is the reason why its taking longtime to connect back to the network. you've two issues this one and client getting dhcp ip as well. however, M1 key issue is holding the client from connecting to AP.

*dot1xMsgTask: Oct 31 10:01:51.331: 00:02:b3:e1:ee:20 Sending EAPOL-Key Message to mobile 00:02:b3:e1:ee:20

state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00

*osapiBsnTimer: Oct 31 10:01:54.514: 00:02:b3:e1:ee:20 802.1x 'timeoutEvt' Timer expired for station 00:02:b3:e1:ee:20 and for message = M2

*dot1xMsgTask: Oct 31 10:01:54.515: 00:02:b3:e1:ee:20 Retransmit 1 of EAPOL-Key M1 (length 99) for mobile 00:02:b3:e1:ee:20

*osapiBsnTimer: Oct 31 10:01:57.514: 00:02:b3:e1:ee:20 802.1x 'timeoutEvt' Timer expired for station 00:02:b3:e1:ee:20 and for message = M2

*dot1xMsgTask: Oct 31 10:01:57.514: 00:02:b3:e1:ee:20 Retransmit 2 of EAPOL-Key M1 (length 99) for mobile 00:02:b3:e1:ee:20

*osapiBsnTimer: Oct 31 10:02:00.514: 00:02:b3:e1:ee:20 802.1x 'timeoutEvt' Timer expired for station 00:02:b3:e1:ee:20 and for message = M2

*dot1xMsgTask: Oct 31 10:02:00.514: 00:02:b3:e1:ee:20 Retransmit 3 of EAPOL-Key M1 (length 99) for mobile 00:02:b3:e1:ee:20

*osapiBsnTimer: Oct 31 10:02:03.514: 00:02:b3:e1:ee:20 802.1x 'timeoutEvt' Timer expired for station 00:02:b3:e1:ee:20 and for message = M2

*dot1xMsgTask: Oct 31 10:02:03.514: 00:02:b3:e1:ee:20 Retransmit 4 of EAPOL-Key M1 (length 99) for mobile 00:02:b3:e1:ee:20

*osapiBsnTimer: Oct 31 10:02:06.514: 00:02:b3:e1:ee:20 802.1x 'timeoutEvt' Timer expired for station 00:02:b3:e1:ee:20 and for message = M2

*dot1xMsgTask: Oct 31 10:02:06.515: 00:02:b3:e1:ee:20 Retransmit failure for EAPOL-Key M1 to mobile 00:02:b3:e1:ee:20, retransmit count 5, mscb deauth count 0

*dot1xMsgTask: Oct 31 10:02:06.515: 00:02:b3:e1:ee:20 Sent Deauthenticate to mobile on BSSID 00:13:19:40:c7:00 slot 0(caller 1x_ptsm.c:534)

Try - WPA2-AES instead.

Stewart Roth · ‎10-31-2012

OLD handhelds they do not even support WPA2. When i had the handhelds sent back to me i was able to associate with no issue to a different AP on the same WLC. 5508 running 7.0.116.0

Saravanan Lakshmanan · ‎10-31-2012

could you try toggling wmm on the connecting ssid. disable if enabled or enable if disabled and test.

how about driver update or using wep.

what was the working and not working AP model.

Stewart Roth · ‎10-31-2012

I will try toggling the WMM. WEP is nogo as i need to stay PCI compliant.

Stewart Roth · ‎11-01-2012

No luck either. AP currently in use where i am having the issueis an 1121G. Ap i have in the office where i attempted to duplicate issue was same AP model and it was on same controller. I'm getting more reports of clients with issues. Most are not getting past 802x_reqd state and bounce back and orthe betwwen that and authcheck state. I would think i wouldn't need 802.1x since i am using PSK not 802.1x for key management?

Srin_G · ‎11-01-2012

Mate, did you do a coverage check with a low gain radio adapter? I assume you are using this in a warehouse environment. If it is b radio client i think probably you need to re-enable 2M as you know b radio clients associated to any AP bring down its abilities in a wlc environment. Do you have WCS? what is the channel utilization of the AP's in the heatmap?

Also what antenna you are using? what is the height of the AP from the floor and do you have any tilt?

would be nice to see your floor plan.

good luck

Stewart Roth · ‎11-02-2012

No this is in a small building (typical ranch sized 2 BR home) using 1 AP. I have 800+ sites all setup similiar to this. 1 AP small buildings, no warehouses. Using NCS, no maps at this time. i have 2M data rate back in there now.

Srin_G · ‎11-05-2012

are you using the 2.2db rubber duct antenna? you need to check for interference we had a site like this near residential areas and trust me we had the same issue with handhelds. Since its 1 AP roaming is not an issue, it should be interference. Do a coverage test ( we use airmagnet spectrum analyzer and survey) and it will point out the issue. Also check the AP channel utilization.

good luck