Hi all,
We have quite 40 Touchstar Boston 8500 (http://www.touchstar.co.uk/product_mo...) Hand Held Barcode scanners that connect via ZoneFlex 7352 controlled by a Smart Standby Zondirector 1100 to our network.
We have just started testing and what we have found is that the hand held units seem to "disconnect" from the network at random intervals (5-60 minutes) all sleep and power setting are either off or on max. The hand held still has an IP address but the device can no longer access the LAN or can be pinged from any machine within our network. To reconnect we need to put the device in standby mode and then switch it back on, this effectively restarts the network card.
The WLAN card that the handheld has is a Summit, I have found a setting that I thing may be responsible for the drop off's as it may interfere with what the ZoneDirector is trying to do: http://www.summitdata.com/Documents/G...
Agressive Scan is a feature in Summit WLAN cards that actively looks for better Ap's and try's to connect to them, from my understanding the ZoneDirector will transfer the device between Ap's? Would this be culprit?
Any help appreciated.
Thanks,
Julius
We have quite 40 Touchstar Boston 8500 (http://www.touchstar.co.uk/product_mo...) Hand Held Barcode scanners that connect via ZoneFlex 7352 controlled by a Smart Standby Zondirector 1100 to our network.
We have just started testing and what we have found is that the hand held units seem to "disconnect" from the network at random intervals (5-60 minutes) all sleep and power setting are either off or on max. The hand held still has an IP address but the device can no longer access the LAN or can be pinged from any machine within our network. To reconnect we need to put the device in standby mode and then switch it back on, this effectively restarts the network card.
The WLAN card that the handheld has is a Summit, I have found a setting that I thing may be responsible for the drop off's as it may interfere with what the ZoneDirector is trying to do: http://www.summitdata.com/Documents/G...
Agressive Scan is a feature in Summit WLAN cards that actively looks for better Ap's and try's to connect to them, from my understanding the ZoneDirector will transfer the device between Ap's? Would this be culprit?
Any help appreciated.
Thanks,
Julius
Posted 7 years ago
Primož Marinšek, AlphaDog
Primož Marinšek, AlphaDog
Hi Primoz, it's all of them. We had also once thought it was one or two AP's but this has happened to many oof them
All I have is Wifi Analyzer app on my android phone.
We are still on FW 9.5.
All I have is Wifi Analyzer app on my android phone.
We are still on FW 9.5.
Primož Marinšek, AlphaDog
9.5.2 or still 9.5.0?
9.5.1.0 build 50
Primož Marinšek, AlphaDog
OK. Recommend you go 9.6 then 9.6.1
Primož Marinšek, AlphaDog
Primož Marinšek, AlphaDog
Please copy and paste from the RF info of a few APs all lines under the below 2 subjects
------------ PHY Error Stats ------------
and
------------ Airtime Stats ------------
------------ PHY Error Stats ------------
and
------------ Airtime Stats ------------
WASP005
------------ PHY Error Stats ------------
6896450 PHY errors since clearing all stats (rx_phyerr)
1 phy cck restart
5577245 phy ofdm group
1319204 phy cck group
0 PHY errors since clearing delta stats (1 sec)
Histogram of PHY errors per second (pcttime in each range)
0 1-500 ..1K ..2K ..5K ..10K ..20K ..50K .100K more
20 76 3 1 0 0 0 0 0 0
------------ Airtime Stats ------------
Airtime utilized (percent) since clearing delta stats (1 sec)
Busy: 0 RX: 11 TX: 3 Total: 14
Histograms of airtime (pcttime in each range) since clearing all stats
0 0-10 ..20 ..30 ..40 ..50 ..60 ..70 ..80 ..90 ..100
busy: 92 7 0 0 0 0 0 0 0 0 0
rx: 0 94 5 0 0 0 0 0 0 0 0
tx: 5 95 0 0 0 0 0 0 0 0 0
tot: 0 89 9 1 0 0 0 0 0 0 0
WASP009
------------ PHY Error Stats ------------
8089188 PHY errors since clearing all stats (rx_phyerr)
5445398 phy ofdm group
2643790 phy cck group
0 PHY errors since clearing delta stats (1 sec)
Histogram of PHY errors per second (pcttime in each range)
0 1-500 ..1K ..2K ..5K ..10K ..20K ..50K .100K more
15 81 2 2 1 0 0 0 0 0
------------ Airtime Stats ------------
Airtime utilized (percent) since clearing delta stats (1 sec)
Busy: 0 RX: 8 TX: 1 Total: 9
Histograms of airtime (pcttime in each range) since clearing all stats
0 0-10 ..20 ..30 ..40 ..50 ..60 ..70 ..80 ..90 ..100
busy: 91 8 1 0 0 0 0 0 0 0 0
rx: 0 90 9 1 0 0 0 0 0 0 0
tx: 5 94 1 0 0 0 0 0 0 0 0
tot: 0 78 17 3 1 0 0 0 0 0 0
WASP012
------------ PHY Error Stats ------------
83606678 PHY errors since clearing all stats (rx_phyerr)
6 phy cck restart
60633540 phy ofdm group
22973132 phy cck group
6 PHY errors since clearing delta stats (1 sec)
6 phy cck restart
Histogram of PHY errors per second (pcttime in each range)
0 1-500 ..1K ..2K ..5K ..10K ..20K ..50K .100K more
16 80 1 1 1 0 0 0 0 0
------------ Airtime Stats ------------
Airtime utilized (percent) since clearing delta stats (1 sec)
Busy: 0 RX: 7 TX: 2 Total: 9
Histograms of airtime (pcttime in each range) since clearing all stats
0 0-10 ..20 ..30 ..40 ..50 ..60 ..70 ..80 ..90 ..100
busy: 94 5 0 0 0 0 0 0 0 0 0
rx: 0 85 13 2 0 0 0 0 0 0 0
tx: 7 93 0 0 0 0 0 0 0 0 0
tot: 0 75 21 3 1 0 0 0 0 0 0
------------ PHY Error Stats ------------
6896450 PHY errors since clearing all stats (rx_phyerr)
1 phy cck restart
5577245 phy ofdm group
1319204 phy cck group
0 PHY errors since clearing delta stats (1 sec)
Histogram of PHY errors per second (pcttime in each range)
0 1-500 ..1K ..2K ..5K ..10K ..20K ..50K .100K more
20 76 3 1 0 0 0 0 0 0
------------ Airtime Stats ------------
Airtime utilized (percent) since clearing delta stats (1 sec)
Busy: 0 RX: 11 TX: 3 Total: 14
Histograms of airtime (pcttime in each range) since clearing all stats
0 0-10 ..20 ..30 ..40 ..50 ..60 ..70 ..80 ..90 ..100
busy: 92 7 0 0 0 0 0 0 0 0 0
rx: 0 94 5 0 0 0 0 0 0 0 0
tx: 5 95 0 0 0 0 0 0 0 0 0
tot: 0 89 9 1 0 0 0 0 0 0 0
WASP009
------------ PHY Error Stats ------------
8089188 PHY errors since clearing all stats (rx_phyerr)
5445398 phy ofdm group
2643790 phy cck group
0 PHY errors since clearing delta stats (1 sec)
Histogram of PHY errors per second (pcttime in each range)
0 1-500 ..1K ..2K ..5K ..10K ..20K ..50K .100K more
15 81 2 2 1 0 0 0 0 0
------------ Airtime Stats ------------
Airtime utilized (percent) since clearing delta stats (1 sec)
Busy: 0 RX: 8 TX: 1 Total: 9
Histograms of airtime (pcttime in each range) since clearing all stats
0 0-10 ..20 ..30 ..40 ..50 ..60 ..70 ..80 ..90 ..100
busy: 91 8 1 0 0 0 0 0 0 0 0
rx: 0 90 9 1 0 0 0 0 0 0 0
tx: 5 94 1 0 0 0 0 0 0 0 0
tot: 0 78 17 3 1 0 0 0 0 0 0
WASP012
------------ PHY Error Stats ------------
83606678 PHY errors since clearing all stats (rx_phyerr)
6 phy cck restart
60633540 phy ofdm group
22973132 phy cck group
6 PHY errors since clearing delta stats (1 sec)
6 phy cck restart
Histogram of PHY errors per second (pcttime in each range)
0 1-500 ..1K ..2K ..5K ..10K ..20K ..50K .100K more
16 80 1 1 1 0 0 0 0 0
------------ Airtime Stats ------------
Airtime utilized (percent) since clearing delta stats (1 sec)
Busy: 0 RX: 7 TX: 2 Total: 9
Histograms of airtime (pcttime in each range) since clearing all stats
0 0-10 ..20 ..30 ..40 ..50 ..60 ..70 ..80 ..90 ..100
busy: 94 5 0 0 0 0 0 0 0 0 0
rx: 0 85 13 2 0 0 0 0 0 0 0
tx: 7 93 0 0 0 0 0 0 0 0 0
tot: 0 75 21 3 1 0 0 0 0 0 0
Primož Marinšek, AlphaDog
Well. It' probably not interference. It looks pretty clean.
Is tunneling helping?
Is tunneling helping?
Unfortunately not really, we are going to upgrade to 9.6 now. Thanks for looking at our logs.
Primož Marinšek, AlphaDog
Run an AP-ZD SpeedTest for every AP. Is there any packet loss?
Morning Primoz, we ran ping testing over night from the ZD to AP's and to all of our core switches, 40 000 packets sent 0% packet loss. We have upgraded to 9.6.1 and the initial results seem promising. Will keep you updated.
Primož Marinšek, AlphaDog
Any change?
Not so much solved but manageable, after a lot of tweeking and fiddling. This should not happen on a wireless network with handheld scanners, which are in fact glorified mobile phones with scanners.
Thanks for all your help and suggestions :)
Thanks for all your help and suggestions :)
Ha ha! Yes, very true! Bring on Android!
I can confirm that I have seen same problem with Summit card on Psion handhelds with same versions of firmware. Psion handhelds have been tested and confirmed unusable using 3 different (Ruckus, Cisco and Aruba) WLAN setups.
Roaming was not working properly at all, and finally, after Psion rep spending 3 days trying to fix them, all 100 devices have been replaced by Motorola 9000, which resolved problem 100%. So be informed and avoid Summit WLAN card.
Hi Eizens,
Glad you got your issue resolved, can you share the actual model number of your Motorola 9000 range, we are looking at replacing our handhelds, the issue has never been 100% resolved and the performance has always been flaky at best even after we made all the changes to Ruckus.
Thanks,
Julius
Glad you got your issue resolved, can you share the actual model number of your Motorola 9000 range, we are looking at replacing our handhelds, the issue has never been 100% resolved and the performance has always been flaky at best even after we made all the changes to Ruckus.
Thanks,
Julius
We have good experience with mutiple Motorola models (9000 and later) and Casio DTX-7, DTX-8 handhelds. Casio devices have smaller screens, are a bit cheaper, more compact and much more lightweight. Both work without problems and are reliable.
By the way, Psion brand is also owned by Motorola, but it is different device (similar in style so). It has nothing bad actually, except absolutely offull WLAN adapter (or more probably, the adapter driver is flowed). But as there is no way to fix this driver, this Psion Workabout Pro devices are useless as Wi-Fi scanners.
At least it was so during 2013 year, when we had to make different tests with them and troubleshoot customer systems.
May be newer devices have different Wi-Fi adapters and are free of this bug, but it was so scary experience, that I would not recommend use of any of them having any choice, and would not change my opinion without extensive (and trusted) testing proving that the problem is really fixed.
By the way, Psion brand is also owned by Motorola, but it is different device (similar in style so). It has nothing bad actually, except absolutely offull WLAN adapter (or more probably, the adapter driver is flowed). But as there is no way to fix this driver, this Psion Workabout Pro devices are useless as Wi-Fi scanners.
At least it was so during 2013 year, when we had to make different tests with them and troubleshoot customer systems.
May be newer devices have different Wi-Fi adapters and are free of this bug, but it was so scary experience, that I would not recommend use of any of them having any choice, and would not change my opinion without extensive (and trusted) testing proving that the problem is really fixed.
(Edited)
Julius Kisielius
Julius Kisielius
Dominic Simpson
Primož Marinšek, AlphaDog
Julius Kisielius