Thanks :-)

It's Intermec terminals on the rolling equipment. Only WPA is supported.

We are using WPA-PSK right now.

I will collect more info tomorrow

PerB

Like Greg mentioned, wpa does not support fast roaming which causes you to loose connection for a while. Caching support in WPA2 allows you to reconnect to an access point that you've recently connected to without the need to re-authenticate again. Without PMK (as in WPA2) you can expect re-authentication to take around one second, which can cause your application to break.

Just tested yesterday with a normal laptop.

Configured a wireles SSID on the a radios, WPA2-PSK. When driving around in the warehouse, the pc was loosing lots of packets.

Sometimes it was roaming withiut loosing a ping, but in other cases loosing op to 5 pings. The warehouse is empty and signal is fine.

You have 2 WLC's, is your mobility setup correctly? As far as LAP's go, are they all on one wlc or did you split them up?

Same mobility group on both WLC's.

It's 2 x 4402-12 and all AP's are on the same controller. I will end up with 16-18 AP's but at this time only 10 of them are installed.

/PerB

I don't know why you would loose that many pings during a roam. If you feel comfortable, can you post your show run-config so I can look at if the configuration need something changed.

Here it is.

The setup is going in production monday, and i am not happy with this behavior.

/PerB

I hear you. Can you post the show run-configuration. You posted the show running-configuration.

Try disabling Aggressive Load Balancing and WMM unless your scanner supports that. I will wait to see the run-configuration.

Sorry, but here is run-config.

You only have 7 ap's on this controller but you said you had a total of 10. If you have 10 and a user roams from an ap on this controller to an ap on the other controller, you will have timeouts. This because you also don't have both controllers configured in the mobility group setting. Also you need to configure the service port with an ip address that is not routable in your network. Just configure the port but don't attach that to the network. After you makes these changes and you still have issues, disable aggressive load balancing and WMM and see if that helps.