<?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 Channel Fly Causing Dropouts in To Be Moved</title>
    <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42872#M2338</link>
    <description>Hi.&lt;BR /&gt;&lt;BR /&gt;We have experienced an issue with Channel Fly. It seems that when it tries to change the channel, all users on the Wifi gets kicked out for a good 30 seconds. We have 2 networks setup, one that is open and one that is hidden. The one that is hidden has around 10 people on it, and the one that is hidden would have 100+ Devices on it. ( Phones, Tablets, Personal Laptops etc ).&lt;BR /&gt;&lt;BR /&gt;We have tried fixing the channel but that doesn't work very well once all the users are connected. E.G Slow.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We've also tried restarted the WAP's. but this does not help either.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We only use 2.4Ghz.&amp;nbsp;&lt;BR /&gt;Wireless Mode: 2.4GHz (802.11 b/g/n)&lt;BR /&gt;Channel: SmartSelect&lt;BR /&gt;Channel Width: 20MHz&lt;BR /&gt;Country Code: United Kingdom&lt;BR /&gt;&lt;BR /&gt;Please let me know how I can resolve this &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;thanks,&amp;nbsp;</description>
    <pubDate>Wed, 08 Mar 2017 13:33:15 GMT</pubDate>
    <dc:creator>kieran_james_cg</dc:creator>
    <dc:date>2017-03-08T13:33:15Z</dc:date>
    <item>
      <title>Channel Fly Causing Dropouts</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42872#M2338</link>
      <description>Hi.&lt;BR /&gt;&lt;BR /&gt;We have experienced an issue with Channel Fly. It seems that when it tries to change the channel, all users on the Wifi gets kicked out for a good 30 seconds. We have 2 networks setup, one that is open and one that is hidden. The one that is hidden has around 10 people on it, and the one that is hidden would have 100+ Devices on it. ( Phones, Tablets, Personal Laptops etc ).&lt;BR /&gt;&lt;BR /&gt;We have tried fixing the channel but that doesn't work very well once all the users are connected. E.G Slow.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We've also tried restarted the WAP's. but this does not help either.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We only use 2.4Ghz.&amp;nbsp;&lt;BR /&gt;Wireless Mode: 2.4GHz (802.11 b/g/n)&lt;BR /&gt;Channel: SmartSelect&lt;BR /&gt;Channel Width: 20MHz&lt;BR /&gt;Country Code: United Kingdom&lt;BR /&gt;&lt;BR /&gt;Please let me know how I can resolve this &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;thanks,&amp;nbsp;</description>
      <pubDate>Wed, 08 Mar 2017 13:33:15 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42872#M2338</guid>
      <dc:creator>kieran_james_cg</dc:creator>
      <dc:date>2017-03-08T13:33:15Z</dc:date>
    </item>
    <item>
      <title>Re: Channel Fly Causing Dropouts</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42873#M2339</link>
      <description>Channel Fly should help determine best channels in your environment, based on individual AP measurements of the RF around them.&lt;BR /&gt;They should settle down on some desired channels after a few days, when many customers will fix the channels.&amp;nbsp; That should help to&lt;BR /&gt;optimize your coverage on both bands.&lt;BR /&gt;&lt;BR /&gt;Then, if you see sub-optimal performance, you need to analyse the client devices performance, affected by their distance from the AP&lt;BR /&gt;and interference local to them.&amp;nbsp; You see connected client RF stats in the AP support info file.&amp;nbsp; A "good" connection will have PER &amp;lt; 10,&lt;BR /&gt;and RSSI - PER &amp;gt;= 25.&amp;nbsp; The RSSI is relative to client distance from the AP, and packet error rate indicates RF interference near the client.&lt;BR /&gt;&lt;BR /&gt;example: client (STA) has RSSI = 24, PER = 7, fairly good signal strength, only 7% packet loss, getting 54mbps data rate.&lt;BR /&gt;&lt;BR /&gt;STA: c4:10:8a:df:b7:c7&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; rx_data_frm 946619 rx_mgt_frm 2541 rx_bytes 338562247 rx_dup 702&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; tx_data_frm 1923183 tx_mgmt_frm 2541 tx_bytes 183424615&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; good_tx_frms 1925724 good_rx_frms 949160 tx_retries 597084&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; tx_rate 54000 tx_kbps 5234 rx_crc_errs 49292&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; tx_per 7 ack_rssi 24 rx_rssi 24&lt;BR /&gt;&lt;BR /&gt;If you identify a few clients that show high PER, try to find where they are sitting/standing as there may be some source of interference.&lt;BR /&gt;If you identify a few clients that have low RSSI, try to find where they are sitting/standing and if there are any walls/barriers between them&lt;BR /&gt;and the nearest AP(s)?&amp;nbsp; The type of WLAN (hidden/visible) doesn't matter.</description>
      <pubDate>Wed, 08 Mar 2017 17:41:08 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42873#M2339</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2017-03-08T17:41:08Z</dc:date>
    </item>
    <item>
      <title>Re: Channel Fly Causing Dropouts</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42874#M2340</link>
      <description>Hello Michael,&lt;BR /&gt;i use normally channelfly, but you &amp;nbsp;say that "They should settle down on some desired channels after a few days" few days?? it take so much time to get perfect? so if it's a temporary event of 1 or 2 days for example? It's better not to use at all?</description>
      <pubDate>Wed, 08 Mar 2017 18:15:49 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42874#M2340</guid>
      <dc:creator>nuno_pimentel</dc:creator>
      <dc:date>2017-03-08T18:15:49Z</dc:date>
    </item>
    <item>
      <title>Re: Channel Fly Causing Dropouts</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42875#M2341</link>
      <description>Another thing.. where u see that Per and RSSI per client? in support info file of the AP? i don't see that info in any section.&amp;nbsp;</description>
      <pubDate>Wed, 08 Mar 2017 18:36:16 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42875#M2341</guid>
      <dc:creator>nuno_pimentel</dc:creator>
      <dc:date>2017-03-08T18:36:16Z</dc:date>
    </item>
    <item>
      <title>Re: Channel Fly Causing Dropouts</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42876#M2342</link>
      <description>If you only have infrequent events, you might opt for Background Scanning, with default settings.&lt;BR /&gt;If using ZD, under Monitor/Access Points, click the first icon (blue/green) to the right of the AP to&lt;BR /&gt;see System Info (support text) for connected client details and rolling 2 minute RF athstats samples.&lt;BR /&gt;If using SZ, Monitor/Access Points, click the AP MAC to look into, click Download -&amp;gt; Download Support log.&lt;BR /&gt;If using Solo AP, Maintenance::Support Info page, Save to Local Computer -&amp;gt; supportinfo.txt.</description>
      <pubDate>Thu, 09 Mar 2017 18:22:35 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42876#M2342</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2017-03-09T18:22:35Z</dc:date>
    </item>
    <item>
      <title>Re: Channel Fly Causing Dropouts</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42877#M2343</link>
      <description>In support file..&lt;BR /&gt;and you see PER and RSSI in "STA Stats". Just make a search for keyword : STA Stats and slowly scroll down. you wiil see these stats..</description>
      <pubDate>Thu, 09 Mar 2017 18:22:36 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42877#M2343</guid>
      <dc:creator>monnat_systems</dc:creator>
      <dc:date>2017-03-09T18:22:36Z</dc:date>
    </item>
    <item>
      <title>Re: Channel Fly Causing Dropouts</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42878#M2344</link>
      <description>DSE, &lt;BR /&gt;time to settle down depends on your local RF conditions..</description>
      <pubDate>Thu, 09 Mar 2017 18:24:14 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42878#M2344</guid>
      <dc:creator>monnat_systems</dc:creator>
      <dc:date>2017-03-09T18:24:14Z</dc:date>
    </item>
    <item>
      <title>Re: Channel Fly Causing Dropouts</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42879#M2345</link>
      <description>I've never had success with ChannelFly on 2.4Ghz networks. It seems basically none of the manufacturers support the required notification for it to work seamlessly. Even those Wireless cards that also support 5Ghz don't seem to behave when they are on 2.4Ghz. &lt;BR /&gt;&lt;BR /&gt;Based on conversations I had at the time that was pretty much agreed to be normal and that ChannelFly only really works on 5Ghz networks without client interuption.</description>
      <pubDate>Thu, 09 Mar 2017 20:25:48 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Channel-Fly-Causing-Dropouts/m-p/42879#M2345</guid>
      <dc:creator>dave_watkins_74</dc:creator>
      <dc:date>2017-03-09T20:25:48Z</dc:date>
    </item>
  </channel>
</rss>

