<?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 WLC Load Profile Failure in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-load-profile-failure/m-p/2613240#M115837</link>
    <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;Any ideas on the&amp;nbsp;issue below would be much appreciated:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;5508 WLC v7.6 code, with 4x 3702i AP's attached,&amp;nbsp;10&amp;gt;15 Wireless clients average&amp;nbsp;on&amp;nbsp;x2 of the&amp;nbsp;AP's (the Cisco stats say these AP's should handle 128 clients if pushed to their max), the other 2x AP's&amp;nbsp;have 5x clients average, aggressive load balancing is not enabled. All other setting on this controller are what I would expect, as it is a newish install.&lt;/P&gt;&lt;P&gt;The issue, "Load Profile Failure" being reported by the WLC and Prime for the 2x AP's with the&amp;nbsp;highest load&amp;nbsp;(10&amp;gt;15), and wireless clients randomly having issues connecting. The AP's in question&amp;nbsp;are also&amp;nbsp;currently displaying as yellow in Prime, because of a minor warning due to the Load Profile Issue. I could understand this warning/behaviour if Aggressive LB was enabled, but strangely it is not.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jul 2021 09:34:02 GMT</pubDate>
    <dc:creator>Fuzzy Logic</dc:creator>
    <dc:date>2021-07-05T09:34:02Z</dc:date>
    <item>
      <title>WLC Load Profile Failure</title>
      <link>https://community.cisco.com/t5/wireless/wlc-load-profile-failure/m-p/2613240#M115837</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;Any ideas on the&amp;nbsp;issue below would be much appreciated:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;5508 WLC v7.6 code, with 4x 3702i AP's attached,&amp;nbsp;10&amp;gt;15 Wireless clients average&amp;nbsp;on&amp;nbsp;x2 of the&amp;nbsp;AP's (the Cisco stats say these AP's should handle 128 clients if pushed to their max), the other 2x AP's&amp;nbsp;have 5x clients average, aggressive load balancing is not enabled. All other setting on this controller are what I would expect, as it is a newish install.&lt;/P&gt;&lt;P&gt;The issue, "Load Profile Failure" being reported by the WLC and Prime for the 2x AP's with the&amp;nbsp;highest load&amp;nbsp;(10&amp;gt;15), and wireless clients randomly having issues connecting. The AP's in question&amp;nbsp;are also&amp;nbsp;currently displaying as yellow in Prime, because of a minor warning due to the Load Profile Issue. I could understand this warning/behaviour if Aggressive LB was enabled, but strangely it is not.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 09:34:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-load-profile-failure/m-p/2613240#M115837</guid>
      <dc:creator>Fuzzy Logic</dc:creator>
      <dc:date>2021-07-05T09:34:02Z</dc:date>
    </item>
    <item>
      <title>That load message is being</title>
      <link>https://community.cisco.com/t5/wireless/wlc-load-profile-failure/m-p/2613241#M115838</link>
      <description>&lt;P&gt;That load message is being generated by the WLC based on the settings found under "Wireless -&amp;gt; 802.11a/n/ac &amp;gt; RRM &amp;gt; General" and "Wireless -&amp;gt; 802.11b/g/n &amp;gt; RRM &amp;gt; General". The default setting for the client load is 12 clients per access-point radio which is quite low. If you higher those values the messages and the yellow icons in Prime will disappear.&lt;BR /&gt;&lt;BR /&gt;You say that all the other settings are kind of "default", but I hope that you did tune the data rates and the other "basic" settings? Also make sure that you run 7.6.130 and the latest FUS.&lt;/P&gt;</description>
      <pubDate>Sat, 21 Feb 2015 22:10:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-load-profile-failure/m-p/2613241#M115838</guid>
      <dc:creator>Freerk Terpstra</dc:creator>
      <dc:date>2015-02-21T22:10:52Z</dc:date>
    </item>
    <item>
      <title>Thanks for you help with this</title>
      <link>https://community.cisco.com/t5/wireless/wlc-load-profile-failure/m-p/2613242#M115839</link>
      <description>&lt;P&gt;Thanks for you help with&amp;nbsp;this Freerk, it all makes sense now, that said the&amp;nbsp;clients having issues connecting must lie elsewhere.&amp;nbsp;Further investigation required I think.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regarding defaults, I have basically inherited this WLC and it was installed another company, so by default I should of&amp;nbsp;noted it looks to be setup&amp;nbsp;the same as&amp;nbsp;other WLC I have worked on. I will though,&amp;nbsp;as you mentioned check the data rates, OS and&amp;nbsp;FUS.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 22 Feb 2015 12:10:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-load-profile-failure/m-p/2613242#M115839</guid>
      <dc:creator>Fuzzy Logic</dc:creator>
      <dc:date>2015-02-22T12:10:36Z</dc:date>
    </item>
    <item>
      <title>Re: Thanks for you help with this</title>
      <link>https://community.cisco.com/t5/wireless/wlc-load-profile-failure/m-p/3720790#M115840</link>
      <description>&lt;P&gt;I have the same issue, were you able to resolve the itermitent connectivty issue?&lt;/P&gt;
&lt;P&gt;we also face latency and packet drops as well.... avg clinets are below 30 per AP.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Oct 2018 06:50:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-load-profile-failure/m-p/3720790#M115840</guid>
      <dc:creator>a4ter</dc:creator>
      <dc:date>2018-10-08T06:50:48Z</dc:date>
    </item>
  </channel>
</rss>

