<?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: Client load-balancing in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703685#M100240</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no feature on the AP/WLC that load-balances if the AP's CU is too high. "Load-Balancing" refers to quantity of clients and not the CU itself. As George pointed out, most clients don't honor the rejection (which is why we have to build in a mechanism to only reject a client X # of times so we can eventualy let them associate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now regarding what I think you are asking. The expectation is that the Client will have its own logic to choose not to roam to an AP/Channel if CU is too high. The QBSS Parameter in our beacon specifically advertises Client Load and Channel Utilization for a client to see. So a client has every right to decide not to use that AP if it thinks the count or utilization is too high.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume the line about "new clients" avoid loaded AP might be referencing intelligent clients that listen to our advertised QBSS value, but I honeslty have never seen such a client myself.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 23 Apr 2011 07:44:57 GMT</pubDate>
    <dc:creator>weterry</dc:creator>
    <dc:date>2011-04-23T07:44:57Z</dc:date>
    <item>
      <title>Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703676#M100231</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a short question.&lt;/P&gt;&lt;P&gt;Is there a feature in Cisco WLC like load-balancing based on bandwidth utilization?&lt;/P&gt;&lt;P&gt;What I mean is, one AP (channel6) has a channel utilization of 40%, the neighbor AP (channel 11) has a channel utilization of 10%.&lt;/P&gt;&lt;P&gt;So I would like push new clients automatically to the AP in channel 11.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;many thanks&lt;/P&gt;&lt;P&gt;Martin&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 03:07:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703676#M100231</guid>
      <dc:creator>mlieber</dc:creator>
      <dc:date>2021-07-04T03:07:00Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703677#M100232</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The feature callled Aggressive Load Balancing on the WLC does this Job.. the below link will help you out!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00809c2fc3.shtml"&gt;http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00809c2fc3.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lemme know if this answered ur question!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Surendra&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Apr 2011 12:55:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703677#M100232</guid>
      <dc:creator>Surendra BG</dc:creator>
      <dc:date>2011-04-22T12:55:29Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703678#M100233</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Surendra however it is not per chanel utilization. Aggressive load balancing is per ammount of users..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Apr 2011 15:24:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703678#M100233</guid>
      <dc:creator>dmantill</dc:creator>
      <dc:date>2011-04-22T15:24:06Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703679#M100234</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; It doesnt work worth a crap anyway ... Most clients don't adhere to code 17 so what's the point ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="content"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Aggressive load-balancing works at the association phase. If enabled &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; and the conditions to load-balance are met, when a wireless client attempts to &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; associate to a LAP, association response frames are sent to the client with an &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 802.11 response packet that includes status code 17. This code indicates that &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the AP is too busy to accept any more associations.&lt;/P&gt;&lt;SPAN class="content"&gt;&lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="content"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 14pt;"&gt;&lt;STRONG&gt;&lt;EM style="text-decoration: underline; "&gt;It is the responsibility of the client to honor, process or discard &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; that association response frame with reason code 17.&lt;/EM&gt;&lt;/STRONG&gt;&lt;/SPAN&gt; Some clients ignore it, &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; even though it is part of the 802.11 specification. The standard dictates that &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the client driver must look for another AP to connect to since it receives a &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "busy" message from the first AP it tries. Many clients do not do this and send &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the association request again. The client in question is allowed on to the &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; wireless network upon subsequent attempts to associate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Apr 2011 15:43:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703679#M100234</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2011-04-22T15:43:37Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703680#M100235</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think getting to the root problem of your channel utilization is important. Do you have 1 meg&lt;/P&gt;&lt;P&gt;frames as mandatory ? This can lead to high utilization ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your deign is solid and you still have high utilization i might suggest powering down your access point. Perhaps even shaping the coverage with a direction antenna. Its a way of using RF to enhance your clients roaming. Make sense?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Apr 2011 15:47:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703680#M100235</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2011-04-22T15:47:37Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703681#M100236</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;+5 for that...&amp;nbsp; Usually aggressive load balancing&amp;nbsp; just cause alot of problems &lt;STRONG&gt;LOL&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="http://www.popartuk.com/g/l/lgpp31157+balance-is-the-key-to-life-balancing-elephant-poster.jpg" class="jive-image" src="http://www.popartuk.com/g/l/lgpp31157+balance-is-the-key-to-life-balancing-elephant-poster.jpg" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Apr 2011 15:56:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703681#M100236</guid>
      <dc:creator>dmantill</dc:creator>
      <dc:date>2011-04-22T15:56:02Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703682#M100237</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I did extensive testing and white paper on LB and its not worth a darn ... Almost all the clients I tested ... ignored code 17 ..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Apr 2011 16:19:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703682#M100237</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2011-04-22T16:19:22Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703683#M100238</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;By any chance you have that lab report? I am interesting on&amp;nbsp; see that &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Apr 2011 16:21:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703683#M100238</guid>
      <dc:creator>dmantill</dc:creator>
      <dc:date>2011-04-22T16:21:27Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703684#M100239</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;many thanks to all.&lt;/P&gt;&lt;P&gt;I don't have a problem with this issue, one of our customers has asked me if it is possible to configure something like that.&lt;/P&gt;&lt;P&gt;And I have read in the config guide in RRM - DCA this:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Load—Load is taken into account when changing the channel structure to minimize the impact on&lt;BR /&gt;clients currently in the wireless LAN. This metric keeps track of every access point’s transmitted&lt;BR /&gt;and received packet counts to determine how busy the access points are. &lt;SPAN style="color: #333333; text-decoration: underline; "&gt;New clients avoid an&lt;BR /&gt;overloaded access point and associate to a new access point.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;But I think that this isn't the same and I didn't found any further information about this configuration parameter like client threshold.&lt;/P&gt;&lt;P&gt;In the same page there is also a description about utilization but I think it is only for monitoring.&lt;/P&gt;&lt;P&gt;Or are there any CLI hidden commands available?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Apr 2011 06:53:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703684#M100239</guid>
      <dc:creator>mlieber</dc:creator>
      <dc:date>2011-04-23T06:53:59Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703685#M100240</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no feature on the AP/WLC that load-balances if the AP's CU is too high. "Load-Balancing" refers to quantity of clients and not the CU itself. As George pointed out, most clients don't honor the rejection (which is why we have to build in a mechanism to only reject a client X # of times so we can eventualy let them associate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now regarding what I think you are asking. The expectation is that the Client will have its own logic to choose not to roam to an AP/Channel if CU is too high. The QBSS Parameter in our beacon specifically advertises Client Load and Channel Utilization for a client to see. So a client has every right to decide not to use that AP if it thinks the count or utilization is too high.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume the line about "new clients" avoid loaded AP might be referencing intelligent clients that listen to our advertised QBSS value, but I honeslty have never seen such a client myself.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Apr 2011 07:44:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703685#M100240</guid>
      <dc:creator>weterry</dc:creator>
      <dc:date>2011-04-23T07:44:57Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703686#M100241</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks for the answer &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Apr 2011 08:53:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703686#M100241</guid>
      <dc:creator>mlieber</dc:creator>
      <dc:date>2011-04-23T08:53:38Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703687#M100242</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So what happens if you limit the number of clients per AP? If the clients still see that AP as the best signal stregnth AP will they continue to try to join that AP and get rejections for ever? My scenario is two APs to handle load in a conference room and I am seeing 27 people join one AP and the other AP gets no clients or 1 client most of the time. Signal stregnth settings are set to automatic and seem to always be defaulting to full power even though the APs are 10-15 feet apart. If I set them both to say 15 clients max will this resolve this issue or will I just have clients reporting they can't connect?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Nov 2013 16:11:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703687#M100242</guid>
      <dc:creator>Andrew Vlasek</dc:creator>
      <dc:date>2013-11-07T16:11:55Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703688#M100243</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is the power level for both AP's currently and for each radio?&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Nov 2013 17:22:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703688#M100243</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2013-11-07T17:22:55Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703689#M100244</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Both power levels are auto setting to full power "1" channels are different.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Nov 2013 22:13:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703689#M100244</guid>
      <dc:creator>Andrew Vlasek</dc:creator>
      <dc:date>2013-11-07T22:13:17Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703690#M100245</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well I don't really see why clients would prefer one ap over the other in the same room. I have many installs with two or more in a room and as long as the power is not set too low like 7-8, clients have balanced themselves out.&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Nov 2013 02:40:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703690#M100245</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2013-11-08T02:40:40Z</dc:date>
    </item>
    <item>
      <title>Re: Client load-balancing</title>
      <link>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703691#M100246</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeah I don't either. I figured the clients would by mere signal level and position join somewhat evenly. I have noticed the auto power and interference avoidance don't seem to work very quickly if at all. The more I read about the load balancing it seems very reliant on the client which limits me as an administrator of the wlc but not the clients.&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Nov 2013 05:56:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-load-balancing/m-p/1703691#M100246</guid>
      <dc:creator>Andrew Vlasek</dc:creator>
      <dc:date>2013-11-08T05:56:53Z</dc:date>
    </item>
  </channel>
</rss>

