I have 4 motorola handheld guns roaming between 6 overlapping 7363 access points with Zone Director 1100. The guns are running a simple wavelink telnet application. They are sitting on a separate open WLAN with no authenticaion but with an MAC ACL. Intermittently, the guns are having problems re-establishing a link to the access point(bars that indicate signal strength go from full to none, and the handheld indicates that it lost connection with the server), even though they are within the range of them. It doesn't happen often but its annoying enough. It usually takes 10 - 20 seconds to re establish a link. What settings should I check? Thank you!
I
I
Posted 6 years ago
Primož Marinšek, AlphaDog
Eddie Felmer, Employee
Michael Brado, Official Rep
Eddie Felmer, Employee
I have another customer reporting similar issue with Windows CE Mobile 6.5 / Motorola MC9190. It seems when roaming between AP’s as they frequently do it upsets a Telnet connection to a server located externally through the internet. I have to renew their IP to get them communicating again although the ZD thinks they are still connected with excellent signal strength.
They are running latest 9.7 LCS and were already tunnelling with ofdm-only enabled. I have asked them to set bss-min rate to 12 to see if that helps and they were also going to test smart roam.
They are running latest 9.7 LCS and were already tunnelling with ofdm-only enabled. I have asked them to set bss-min rate to 12 to see if that helps and they were also going to test smart roam.
Eddie,
What was your resolution to this issue? I am currently experiencing the same.
I have another customer reporting similar issue with Windows CE Mobile 6.5 / Motorola MC9190. It seems when roaming between AP’s as they frequently do it upsets a Telnet connection to a server located externally through the internet. I have to renew their IP to get them communicating again although the ZD thinks they are still connected with excellent signal strength.
They are running latest 9.7 LCS and were already tunnelling with ofdm-only enabled. I have asked them to set bss-min rate to 12 to see if that helps and they were also going to test smart roam.
What was your resolution to this issue? I am currently experiencing the same.
I have another customer reporting similar issue with Windows CE Mobile 6.5 / Motorola MC9190. It seems when roaming between AP’s as they frequently do it upsets a Telnet connection to a server located externally through the internet. I have to renew their IP to get them communicating again although the ZD thinks they are still connected with excellent signal strength.
They are running latest 9.7 LCS and were already tunnelling with ofdm-only enabled. I have asked them to set bss-min rate to 12 to see if that helps and they were also going to test smart roam.
joe statter, Employee
Michael Brado, Official Rep
Eddie Felmer, Employee
The things to try are:
- Enable OFDM only and set BSS Min Rate = 12 on the device WLAN
- Upgrade to one of the version Michael mentions with some loop fixes
- Try setting a higher DTIM value on the APs for the device WLAN (seems 5 is recommended for Moto devices). This is currently a bit painful as you can't do it via the ZD WebUI so have to CLI to every AP and check you are applying it to the correct WLAN (if you only have 1 WLAN then its designator will be the same on every AP so you could do it with the ZD CLI remote_ap_cli command)
- Enable RTS-CTS protection on the WLAN
- Enable OFDM only and set BSS Min Rate = 12 on the device WLAN
- Upgrade to one of the version Michael mentions with some loop fixes
- Try setting a higher DTIM value on the APs for the device WLAN (seems 5 is recommended for Moto devices). This is currently a bit painful as you can't do it via the ZD WebUI so have to CLI to every AP and check you are applying it to the correct WLAN (if you only have 1 WLAN then its designator will be the same on every AP so you could do it with the ZD CLI remote_ap_cli command)
- Enable RTS-CTS protection on the WLAN
Thanks Eddie, I will give this ago. I just need some info how to setup the following:
-Enable ODFM
-Enable RTS-CTS
I'm assuming that I would be able to use the following command to set the DTIM on the ZD CLI: remote_ap_cli –A “set dtim-period wlan2 1”
Where wlan2 is my wlan that all handhelds are connect on and the number 1 represents the DTIM setting I want which in my case would be 5?
Thanks,
Julius
-Enable ODFM
-Enable RTS-CTS
I'm assuming that I would be able to use the following command to set the DTIM on the ZD CLI: remote_ap_cli –A “set dtim-period wlan2 1”
Where wlan2 is my wlan that all handhelds are connect on and the number 1 represents the DTIM setting I want which in my case would be 5?
Thanks,
Julius
Primož Marinšek, AlphaDog
Enable OFDM-only (per WLAN)
set ofdm-only : set ofdm-only {enable|disable}
-- Enable/Disable OFDM-only mode (exclude 11b CCK rates)
Sure hope RW will make it a global feature, not just per WLAN
About enabling RTS-CTS, I'm not too shure, but I think it's this
set rts-thr : set rts-thr {disable|}
-- Modify Request to Send threshold
You need to set a threshold. I would set it at size just below what your handhelds are sending data at so it will kick in.
set ofdm-only : set ofdm-only {enable|disable}
-- Enable/Disable OFDM-only mode (exclude 11b CCK rates)
Sure hope RW will make it a global feature, not just per WLAN
About enabling RTS-CTS, I'm not too shure, but I think it's this
set rts-thr : set rts-thr {disable|}
-- Modify Request to Send threshold
You need to set a threshold. I would set it at size just below what your handhelds are sending data at so it will kick in.
Eddie Felmer, Employee
You can enable OFDM only and configure the bss min rate in the ZD CLI per WLAN, rather than having to do it on the AP using set commands:
Login to ZD CLI - "en"able mode - "config" mode - "wlan xxx" (wlan name is case sensitive)
"ofdm-only"
"bss-minrate 12"
"end"
"show wlan" to show the configuration is set.
In relation to remote_ap_cli –A “set dtim-period wlan2 1” that looks correct (with a 5 in your case). The only issue is that depending on how the APs are provisioned with WLANs (maybe different WLAN on different AP, provisioning order) they won't all necessarily be called wlan2. Note this is not the wlan name you give the wlan, but an internal wlan identifier - 2.4Ghz start at wlan0 and 5Ghz start at wlan32 (on later code releases). You can get get the wlan name-SSID mapping using "get ssid wlanx" i.e.
rkscli: get ssid wlan0
wlan0 SSID: Test
This way you will find what wlan name to use for each AP (if you are lucky it might be the same for all APs!).
In relation to RTS-CTS as Primož says its "set rts-thr {disable|}". Again you will need to know the correct wlan identifier. Generally the advice is to set the threshold to a size larger than max single frame size as you probably don't want RTS-CTS for all packets, just the larger ones that will use more airtime. In 11g the recommendation was 2346, but since 11n aggregation it supports up to 65535. I would change the other settings first, monitor and if still having issues then try RTS-CTS at 2340.
Login to ZD CLI - "en"able mode - "config" mode - "wlan xxx" (wlan name is case sensitive)
"ofdm-only"
"bss-minrate 12"
"end"
"show wlan" to show the configuration is set.
In relation to remote_ap_cli –A “set dtim-period wlan2 1” that looks correct (with a 5 in your case). The only issue is that depending on how the APs are provisioned with WLANs (maybe different WLAN on different AP, provisioning order) they won't all necessarily be called wlan2. Note this is not the wlan name you give the wlan, but an internal wlan identifier - 2.4Ghz start at wlan0 and 5Ghz start at wlan32 (on later code releases). You can get get the wlan name-SSID mapping using "get ssid wlanx" i.e.
rkscli: get ssid wlan0
wlan0 SSID: Test
This way you will find what wlan name to use for each AP (if you are lucky it might be the same for all APs!).
In relation to RTS-CTS as Primož says its "set rts-thr {disable|}". Again you will need to know the correct wlan identifier. Generally the advice is to set the threshold to a size larger than max single frame size as you probably don't want RTS-CTS for all packets, just the larger ones that will use more airtime. In 11g the recommendation was 2346, but since 11n aggregation it supports up to 65535. I would change the other settings first, monitor and if still having issues then try RTS-CTS at 2340.
Thanks very much Eddie and Primoz, will try these setting in the next few days, hopefully even over the weekend.
It looks like "get ssid" is not a command.
Eddie Felmer, Employee
Are you doing this on the AP CLI, not ZD CLI as mentioned above?
Format is "get ssid [wlanid]" i.e.
rkscli: get ssid wlan1
wlan1 SSID: motoscanner
What you need to do is to use this command to find the wlanid for the SSID that your scanners use and then use that wlan id in the command "set dtim-period wlan1 5". The wlanid may vary per AP for the same SSID, hence why you need to do it separately on each AP.
You can also use the command "get wlanlist" to list all the wlans active on that AP - this will help you know which wlanid you need to check in the 2.4/5Ghz bands.
Format is "get ssid [wlanid]" i.e.
rkscli: get ssid wlan1
wlan1 SSID: motoscanner
What you need to do is to use this command to find the wlanid for the SSID that your scanners use and then use that wlan id in the command "set dtim-period wlan1 5". The wlanid may vary per AP for the same SSID, hence why you need to do it separately on each AP.
You can also use the command "get wlanlist" to list all the wlans active on that AP - this will help you know which wlanid you need to check in the 2.4/5Ghz bands.
Welcome to the Ruckus Wireless ZoneDirector 1100 Command Line
Interface
ruckus> enable
ruckus# debug
ruckus(debug)# rksap_cli -A "set dtim-period wlan0 2”
ruckus(debug)# rksap_cli -A "set dtim-period wlan1 2”
...
ruckus(debug)# rksap_cli -A "set dtim-period wlan14 2”
ruckus(debug)# rksap_cli -A "set dtim-period wlan15 2”
ruckus(debug)# quit
Interface
ruckus> enable
ruckus# debug
ruckus(debug)# rksap_cli -A "set dtim-period wlan0 2”
ruckus(debug)# rksap_cli -A "set dtim-period wlan1 2”
...
ruckus(debug)# rksap_cli -A "set dtim-period wlan14 2”
ruckus(debug)# rksap_cli -A "set dtim-period wlan15 2”
ruckus(debug)# quit
Primož Marinšek, AlphaDog
Eddie Felmer, Employee
You can't currently set DTIM (or RTS) via ZD, apart from remote_ap_cli which is not practical unless you know which wlan ID is on which AP as per my previous notes
You will need to find the right wlan ID to SSID mapping on each AP (get ssid wlanx) and set it via AP CLI when you find it. Remember you need to do it for both bands on dual band AP.
You will need to find the right wlan ID to SSID mapping on each AP (get ssid wlanx) and set it via AP CLI when you find it. Remember you need to do it for both bands on dual band AP.
It looks like "get ssid" is not a command.
Eddie Felmer, Employee
Are you doing this on the AP CLI, not ZD CLI as mentioned above?
Format is "get ssid [wlanid]" i.e.
rkscli: get ssid wlan1
wlan1 SSID: motoscanner
What you need to do is to use this command to find the wlanid for the SSID that your scanners use and then use that wlan id in the command "set dtim-period wlan1 5". The wlanid may vary per AP for the same SSID, hence why you need to do it separately on each AP.
You can also use the command "get wlanlist" to list all the wlans active on that AP - this will help you know which wlanid you need to check in the 2.4/5Ghz bands.
Format is "get ssid [wlanid]" i.e.
rkscli: get ssid wlan1
wlan1 SSID: motoscanner
What you need to do is to use this command to find the wlanid for the SSID that your scanners use and then use that wlan id in the command "set dtim-period wlan1 5". The wlanid may vary per AP for the same SSID, hence why you need to do it separately on each AP.
You can also use the command "get wlanlist" to list all the wlans active on that AP - this will help you know which wlanid you need to check in the 2.4/5Ghz bands.
as stated in the first comment above it's the ZoneDirector CLI.
Eddie Felmer, Employee
Its AP CLI command. You can't currently do it from the ZD CLI (apart from remote_ap_cli which is no use because the wlanid may vary by AP).
Eddie Felmer, Employee
Thanks Eddie,
I am going to try next week to enable OFDM-only and see what that does but I will be keeping BSS min rate off. But I think that the hand held units will not like OFDM-only.
We have 8 AP's in our ware house they are about 15-20 meters apart mounted on the roof, the roof is about 10 meters high. Is that too far apart? Should we get more?
I am going to try next week to enable OFDM-only and see what that does but I will be keeping BSS min rate off. But I think that the hand held units will not like OFDM-only.
We have 8 AP's in our ware house they are about 15-20 meters apart mounted on the roof, the roof is about 10 meters high. Is that too far apart? Should we get more?
Primož Marinšek, AlphaDog
"We have 8 AP's in our ware house they are about 15-20 meters apart mounted on the roof, the roof is about 10 meters high. Is that too far apart? Should we get more?"
I think that's your problem right there. Unplug 4 of your APs and I things should get better straight away.
I think that's your problem right there. Unplug 4 of your APs and I things should get better straight away.
Primož Marinšek, AlphaDog
Funny story that, our site was "professionally surveyed" and my apologies for some confusion we are not even using Motorola's we are actually using Touchstar Boston 8500 of Belgarvium fame, I am not sure if anyone is familiar with the company?
But the hardware is new but the OS is Windows CE 5.0 and network cards prefer to run in B only even though they are capable of G, we have had to use a registry setting to make them go to G.
I think that the network cards and OFDM disagree, I will give it a try but I don't think the technologies are compatible.
But the hardware is new but the OS is Windows CE 5.0 and network cards prefer to run in B only even though they are capable of G, we have had to use a registry setting to make them go to G.
I think that the network cards and OFDM disagree, I will give it a try but I don't think the technologies are compatible.
Primož Marinšek, AlphaDog
11g is OFDM (ERP-OFDM to be exact). The problem is most likely in the drivers that implement that, which is nothing new especially with handhelds and/or Win CE.
Define "professionally surveyed". I've seen a 100 professionals that survey with eyes and at most an InSSIDer.
Define "professionally surveyed". I've seen a 100 professionals that survey with eyes and at most an InSSIDer.
;) Perhaps slightly more sophisticated than eyes only. They came in with an access point that they set up in various places and something that looked like an over sized tricorder from star trek, then they told us we will need 8 evenly distributed through our warehouse. No map, no readings, so here we are today.
