<?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 Best Practice Optimization by CLI for Zone Director in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Best-Practice-Optimization-by-CLI-for-Zone-Director/m-p/32264#M9057</link>
    <description>Based upon reading through the various technotes and forum posts, we've come up with the following command-line optimizations for ruckus deployments.  I'd like to hear from Ruckus if all of these are still valid/necessary with current configurations, and/or if anyone else has additional items they find helpful.
&lt;BR /&gt;&lt;BR /&gt;
These are designed for public-access scenarios with moderate density, and the changes have been particularly focused on increasing compatibility with Mac OS, Apple TV and iOS clients.
&lt;BR /&gt;&lt;BR /&gt;
1) for each wlan:
&lt;BR /&gt;
wlan "mywlan"
&lt;BR /&gt;
ofdm-only
&lt;BR /&gt;
bss-minrate 5.5
&lt;BR /&gt;
no qos directed-multicast
&lt;BR /&gt;
qos directed-threshold 0 
&lt;BR /&gt;
No qos igmp-snooping
&lt;BR /&gt;&lt;BR /&gt;
2) For each AP group:
&lt;BR /&gt;
ap-group "System Default"
&lt;BR /&gt;
no qos mld-query v1
&lt;BR /&gt;
no qos mld-query v2
&lt;BR /&gt;
no qos igmp-query v2
&lt;BR /&gt;
no qos igmp-query v3
&lt;BR /&gt;
qos query-Interval 0   directed multicast disable</description>
    <pubDate>Fri, 11 Oct 2013 19:06:31 GMT</pubDate>
    <dc:creator>jeff_roback</dc:creator>
    <dc:date>2013-10-11T19:06:31Z</dc:date>
    <item>
      <title>Best Practice Optimization by CLI for Zone Director</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Best-Practice-Optimization-by-CLI-for-Zone-Director/m-p/32264#M9057</link>
      <description>Based upon reading through the various technotes and forum posts, we've come up with the following command-line optimizations for ruckus deployments.  I'd like to hear from Ruckus if all of these are still valid/necessary with current configurations, and/or if anyone else has additional items they find helpful.
&lt;BR /&gt;&lt;BR /&gt;
These are designed for public-access scenarios with moderate density, and the changes have been particularly focused on increasing compatibility with Mac OS, Apple TV and iOS clients.
&lt;BR /&gt;&lt;BR /&gt;
1) for each wlan:
&lt;BR /&gt;
wlan "mywlan"
&lt;BR /&gt;
ofdm-only
&lt;BR /&gt;
bss-minrate 5.5
&lt;BR /&gt;
no qos directed-multicast
&lt;BR /&gt;
qos directed-threshold 0 
&lt;BR /&gt;
No qos igmp-snooping
&lt;BR /&gt;&lt;BR /&gt;
2) For each AP group:
&lt;BR /&gt;
ap-group "System Default"
&lt;BR /&gt;
no qos mld-query v1
&lt;BR /&gt;
no qos mld-query v2
&lt;BR /&gt;
no qos igmp-query v2
&lt;BR /&gt;
no qos igmp-query v3
&lt;BR /&gt;
qos query-Interval 0   directed multicast disable</description>
      <pubDate>Fri, 11 Oct 2013 19:06:31 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Best-Practice-Optimization-by-CLI-for-Zone-Director/m-p/32264#M9057</guid>
      <dc:creator>jeff_roback</dc:creator>
      <dc:date>2013-10-11T19:06:31Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice Optimization by CLI for Zone Director</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Best-Practice-Optimization-by-CLI-for-Zone-Director/m-p/32265#M9058</link>
      <description>I should add that these are in no way recommendations for you to try this in your environment &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;   Review all documentation and TEST in your environment before deploying...
&lt;BR /&gt;&lt;BR /&gt;
These are just things I've picked up from reviewing forum posts and reading tech notes. I've been particularly focused on largest common denominator settings that get virtually all clients connected and working without any IT intervention.</description>
      <pubDate>Fri, 11 Oct 2013 19:09:39 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Best-Practice-Optimization-by-CLI-for-Zone-Director/m-p/32265#M9058</guid>
      <dc:creator>jeff_roback</dc:creator>
      <dc:date>2013-10-11T19:09:39Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice Optimization by CLI for Zone Director</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Best-Practice-Optimization-by-CLI-for-Zone-Director/m-p/32266#M9059</link>
      <description>It's excellent that there are people like you willing to share their test and results.
&lt;BR /&gt;&lt;BR /&gt;
One thing I noticed though is that I don't think ofdm-only and bss-minrate 5.5 go together. when you enable ofdm-only the minimum rate is 6.</description>
      <pubDate>Mon, 14 Oct 2013 06:21:01 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Best-Practice-Optimization-by-CLI-for-Zone-Director/m-p/32266#M9059</guid>
      <dc:creator>primoz_marinsek</dc:creator>
      <dc:date>2013-10-14T06:21:01Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice Optimization by CLI for Zone Director</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Best-Practice-Optimization-by-CLI-for-Zone-Director/m-p/32267#M9060</link>
      <description>Two cents to Primoz.  Omit the 'ofdm-only' under the WLAN, and you have our
&lt;BR /&gt;
recommendation for Bonjour and non-well-known multicast protocols, that these
&lt;BR /&gt;
commands will flood to wired/wireless clients on the VLAN.  The bss-minrate 5.5
&lt;BR /&gt;
will stop using 1mb/2mb, and thus shrinks your coverage radius to tell clients to
&lt;BR /&gt;
consider roaming sooner (specifically implemented to help sticky Apple clients).
&lt;BR /&gt;
By disabling mld/igmp on the AP, you also tell the system to let clients register
&lt;BR /&gt;
and query with multicast groups, not to proxy on their behalves.</description>
      <pubDate>Mon, 02 Jun 2014 22:28:58 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Best-Practice-Optimization-by-CLI-for-Zone-Director/m-p/32267#M9060</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2014-06-02T22:28:58Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice Optimization by CLI for Zone Director</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Best-Practice-Optimization-by-CLI-for-Zone-Director/m-p/32268#M9061</link>
      <description>Thanks for the thoughts on this.  Why should we omit ofdm-only?   I've seen that in several of the best practices documents.  My understanding is that the only downsifde of this is blocking 802.11b-only clients, which I'm OK with &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;  Are there other side-effects?
&lt;BR /&gt;&lt;BR /&gt;
Jeff</description>
      <pubDate>Tue, 03 Jun 2014 07:33:39 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Best-Practice-Optimization-by-CLI-for-Zone-Director/m-p/32268#M9061</guid>
      <dc:creator>jeff_roback</dc:creator>
      <dc:date>2014-06-03T07:33:39Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice Optimization by CLI for Zone Director</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Best-Practice-Optimization-by-CLI-for-Zone-Director/m-p/32269#M9062</link>
      <description>As Michael said. Recommendation for using Bonjour is to omit ofdm-only.
&lt;BR /&gt;&lt;BR /&gt;
But by enabling it it doesn't mean 11b (and the old 802.11 only) clients will be blocked. They just won't be able to connect to a network that uses OFDM-only. They don't understand it since they only speak DSSS and HR-DSSS which is completely different modulation technique.
&lt;BR /&gt;&lt;BR /&gt;
This is a 2 edged sword mind you. On one hand you're management frames will spend less time occupying the air living more time for actual client data, but If you have many 11b STAs around they could still cause you problems with their signal energy received by your APs and clients.
&lt;BR /&gt;&lt;BR /&gt;
So by allowing 11b STAs and using a higher minimum rate of 5.5Mbps you hopefully get the better bit of both.</description>
      <pubDate>Wed, 04 Jun 2014 07:46:14 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Best-Practice-Optimization-by-CLI-for-Zone-Director/m-p/32269#M9062</guid>
      <dc:creator>primoz_marinsek</dc:creator>
      <dc:date>2014-06-04T07:46:14Z</dc:date>
    </item>
  </channel>
</rss>

