<?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 Re: 802.11n client distribution across 2.4 and 5.0 radios? in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/802-11n-client-distribution-across-2-4-and-5-0-radios/m-p/1590638#M81535</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On the WGB configuration I know the WGB uses "Load" as part of its decision on whether or not to associate with a certain AP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am guessing the client has the same ability as well.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;James&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Mar 2011 07:49:40 GMT</pubDate>
    <dc:creator>jfraasch</dc:creator>
    <dc:date>2011-03-16T07:49:40Z</dc:date>
    <item>
      <title>802.11n client distribution across 2.4 and 5.0 radios?</title>
      <link>https://community.cisco.com/t5/wireless/802-11n-client-distribution-across-2-4-and-5-0-radios/m-p/1590636#M81533</link>
      <description>&lt;P&gt;What is the recommended way to ensure 802.11n clients are evenly split between 2.4Ghz and 5.0Ghz frequencies?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We're using 4404 controllers with WCS and Cisco 3502i AP's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 02:57:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/802-11n-client-distribution-across-2-4-and-5-0-radios/m-p/1590636#M81533</guid>
      <dc:creator>rcoote5902_2</dc:creator>
      <dc:date>2021-07-04T02:57:09Z</dc:date>
    </item>
    <item>
      <title>Re: 802.11n client distribution across 2.4 and 5.0 radios?</title>
      <link>https://community.cisco.com/t5/wireless/802-11n-client-distribution-across-2-4-and-5-0-radios/m-p/1590637#M81534</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;/PRE&gt;&lt;/P&gt;&lt;P&gt;What is the recommended way to ensure 802.11n clients are evenly split between 2.4Ghz and 5.0Ghz frequencies?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The "best" way is to configure the clients to associate to the correct radio of your choice.&amp;nbsp; Doing this will cause issues in the near future.&amp;nbsp; For example, you have configured a client to associate to the "a" radio.&amp;nbsp; However, if the client goes beyond the "a" radio range ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The "easiest" way is to let the client/wireless NIC make the decision themselves.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Mar 2011 20:45:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/802-11n-client-distribution-across-2-4-and-5-0-radios/m-p/1590637#M81534</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2011-03-14T20:45:20Z</dc:date>
    </item>
    <item>
      <title>Re: 802.11n client distribution across 2.4 and 5.0 radios?</title>
      <link>https://community.cisco.com/t5/wireless/802-11n-client-distribution-across-2-4-and-5-0-radios/m-p/1590638#M81535</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On the WGB configuration I know the WGB uses "Load" as part of its decision on whether or not to associate with a certain AP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am guessing the client has the same ability as well.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;James&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Mar 2011 07:49:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/802-11n-client-distribution-across-2-4-and-5-0-radios/m-p/1590638#M81535</guid>
      <dc:creator>jfraasch</dc:creator>
      <dc:date>2011-03-16T07:49:40Z</dc:date>
    </item>
  </channel>
</rss>

