MC55 with AP RUCKUS 7341 problems

[julien_barbe]

Hello.
Excuse my english, i'm a french customer.
I have a big problem with my WiFi Ruckus network for my warehouse.
I've put 12 Ruckus 7341, and i have a fibre connexion with my headquarter on a ZD3000.
All my WiFi's installations have the lastest version and it's working on others devices on my 60 stores.
Today, i have 115 AP, they're working all normally, except these 12 in my warehouse
In each store, we have 10/15 Motorola MC50, and they fully work.

I know that's my PDA the problem, when it's connected with a Ruckus, but i would like to know if it's possible to repair this.

I've checked the ping connexion, and with each PDA MC55 we have the following situation:

PS C:\> ping -t 192.168.102.131

Envoi d'une requête 'Ping' 192.168.102.131 avec 32 octets de données :
Réponse de 192.168.102.131 : octets=32 temps=199 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=57 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=67 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=102 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=24 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=45 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=66 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=88 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=110 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=32 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=53 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=63 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=86 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=119 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=24 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=46 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=82 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=89 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=47 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=45 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=227 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=2140 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=2 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=53 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=73 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=83 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=17 ms TTL=128
Délai d'attente de la demande dépassé.
Délai d'attente de la demande dépassé.
Réponse de 192.168.102.131 : octets=32 temps=1575 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=7 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=33 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=95 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=16 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=23 ms TTL=128
Délai d'attente de la demande dépassé.
Délai d'attente de la demande dépassé.
Réponse de 192.168.102.131 : octets=32 temps=1892 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=3 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=103 ms TTL=128
Délai d'attente de la demande dépassé.
Délai d'attente de la demande dépassé.
Réponse de 192.168.102.131 : octets=32 temps=433 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=17 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=17 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=130 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=49 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=71 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=16 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=16 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=19 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=16 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=16 ms TTL=128
Délai d'attente de la demande dépassé.
Délai d'attente de la demande dépassé.
Réponse de 192.168.102.131 : octets=32 temps=599 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=101 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=2493 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=7 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=52 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=74 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=16 ms TTL=128
Réponse de 192.168.102.131 : octets=32 temps=116 ms TTL=128

Statistiques Ping pour 192.168.102.131:
Paquets : envoyés = 63, reçus = 55, perdus = 8 (perte 12%),
Durée approximative des boucles en millisecondes :
Minimum = 2ms, Maximum = 2493ms, Moyenne = 218ms

It's always two or three packets lost and regulary.

During the test, we haven't any roaming's tentatives or action ... they're just on their zone to work on the AP of them sector, and it's interrupting their loading transactions.

These ping have been tested localy in the headquarter with only one AP for have no roaming, and they presents same symptômes that the warehouse.
If i test the PDA MC50, i haven't the problem.

I also have in the end, this type of message in the ZD3000:
2013/12/12 08:56:57 Faible User[00:40:17:8d:b5:d2] leave WLAN[auxlogis] at AP[AP04-SQF] with Session Time[3372.40 sec] RX Bytes[21000] TX Bytes[994786]
2013/12/12 08:56:52 Faible User[00:15:70:f6:0b:db] leave WLAN[auxlogis] at AP[AP04-SQF] with Session Time[22.19 sec] RX Bytes[89] TX Bytes[20069]

During the problem, the network indicator shows a full connectivity level and don't remove or get less network level reception.

After changing the management of components MC55 PDA (battery) "Power Plus" to "CAM", the latencies are going down to 3-6ms but there are always losses.
I've seen that two PDA on the same AP are disconnected in same time and the same duration.

I would like to know if this type of problems are known, and if you've got any solutions tu resolve it?

In advance, thank you.

[keith_redfield]

Hi Julien,

These can be very difficult to troubleshoot and so if you have a support contract I recommend you open a support ticket https://support.ruckuswireless.com/co...

One thing which I see after a little digging is that these scanners apparently have some trouble with 802.11d (country code) in the beacons, so try disabling that as a test.

[julien_barbe]

Hi, thanks for your answer.
I've already disabled this option in my configuration, and don't troubleshoot this case. (my MC50 have had problems with 802.11d)
I'm customer, and i'll open a ticket in the support, i'd just want to know if someone met this type of problem and what did he do.

[massimo_mazzeo_]

Hi Julien,
in some warehouses environment it may help changing some bitrates.
You may want to try these advanced settings:

From the ZD CLI:

ruckus> enable
ruckus# config
You have all rights in this mode.

ruckus(config)# wlan xxxxx
The WLAN service 'xxxxx' has been created. To save the WLAN service, type 'end' or 'exit'.
ruckus(config-wlan)#

ruckus(config-wlan)# mgmt-tx-rate 1
ruckus(config-wlan)# bss-minrate 1

ruckus(config-wlan)# exit
The WLAN service 'xxxxx' has been updated and saved.
Your changes have been saved.
ruckus(config)#

ruckus(config)# end
Your changes have been saved.
ruckus#

ruckus# debug
You have all rights in this mode.
ruckus(debug)#i

ruckus(debug)# remote_ap_cli -A " set mrc-cck wlan0 1”

This last command has to be applied to the effective wlan# that is used by the MC55...
if you are not sure which one it is, you can check on the AP GUI.

regards

[julien_barbe]

Hi Massimo,
Thanks for your answer.
I'm trying this solution today, at lunch time.
I come back Friday for more details and tell you if it's troubleshooting the problems.

Regards.