<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Warehouses best prcatices - roaming issue in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Warehouses-best-prcatices-roaming-issue/m-p/12645#M2979</link>
    <description>Hi all, I have a new deployment in a warehouse environment. I wonder if there are configuration best practices for a correct deployment.
&lt;BR /&gt;
The customer holds Motorola handheld devices and complains about low WiFi coverage and high response time from his application (telnet based).
&lt;BR /&gt;
I investigated and discovered that client devices (Motorola barcode scanner) usually does not roam between APs: they stay associated to an AP without- or little - roaming to other APs.
&lt;BR /&gt;
Are there specific configuration to make WiFi clients more "inclined" to roam? For example working on power, basic datarates, etc....
&lt;BR /&gt;
Other suggestions?
&lt;BR /&gt;
Thanks in advance
&lt;BR /&gt;
f.</description>
    <pubDate>Wed, 13 Nov 2013 14:18:57 GMT</pubDate>
    <dc:creator>itcore_network</dc:creator>
    <dc:date>2013-11-13T14:18:57Z</dc:date>
    <item>
      <title>Warehouses best prcatices - roaming issue</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Warehouses-best-prcatices-roaming-issue/m-p/12645#M2979</link>
      <description>Hi all, I have a new deployment in a warehouse environment. I wonder if there are configuration best practices for a correct deployment.
&lt;BR /&gt;
The customer holds Motorola handheld devices and complains about low WiFi coverage and high response time from his application (telnet based).
&lt;BR /&gt;
I investigated and discovered that client devices (Motorola barcode scanner) usually does not roam between APs: they stay associated to an AP without- or little - roaming to other APs.
&lt;BR /&gt;
Are there specific configuration to make WiFi clients more "inclined" to roam? For example working on power, basic datarates, etc....
&lt;BR /&gt;
Other suggestions?
&lt;BR /&gt;
Thanks in advance
&lt;BR /&gt;
f.</description>
      <pubDate>Wed, 13 Nov 2013 14:18:57 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Warehouses-best-prcatices-roaming-issue/m-p/12645#M2979</guid>
      <dc:creator>itcore_network</dc:creator>
      <dc:date>2013-11-13T14:18:57Z</dc:date>
    </item>
    <item>
      <title>Re: Warehouses best prcatices - roaming issue</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Warehouses-best-prcatices-roaming-issue/m-p/12646#M2980</link>
      <description>On a similar configuration I tried to:
&lt;BR /&gt;
- update the FW to 9.6.2
&lt;BR /&gt;
- set manualy the channels 
&lt;BR /&gt;
- use the tunnel mode 
&lt;BR /&gt;
- and certainly the most usefull action was to work on the client itself by disabling the power saving (otherwise the telnet session will always close) and the unused band on a dual band client (seems to accelerate the scan during roaming).
&lt;BR /&gt;&lt;BR /&gt;
Regarding the coverage it depends on the antenna heights and orientation. Prefer an horizontal installation and the highest location to maximize the opportunity of a direct path to the client.
&lt;BR /&gt;&lt;BR /&gt;
The service is almost good for us.. we observe only a 1-1.5s freeze during the roaming process but no application downtime.</description>
      <pubDate>Wed, 08 Jan 2014 17:26:11 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Warehouses-best-prcatices-roaming-issue/m-p/12646#M2980</guid>
      <dc:creator>gregoire_leroy</dc:creator>
      <dc:date>2014-01-08T17:26:11Z</dc:date>
    </item>
  </channel>
</rss>

