<?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: AVC and WLC Load. in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/avc-and-wlc-load/m-p/3751747#M206754</link>
    <description>&lt;P&gt;I would think it is AP count. (not 100% sure)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With AVC, if you trying do control part (re-mark, drop,etc) I think that would be more resource intensive &amp;amp; leading to WLC crashes/meltdown in large environment. Below bug may be one of reference that got many cases attached in&amp;nbsp;7.6/8.0 versions&lt;/P&gt;
&lt;P&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuq97965/" target="_self"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuq97965/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As long as you use it to get visibility (simple netflow export), I do not see a major issue of enabling that feature.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;Rasika&lt;/P&gt;
&lt;P&gt;*** Pls rate all useful responses ***&lt;/P&gt;</description>
    <pubDate>Fri, 23 Nov 2018 05:14:30 GMT</pubDate>
    <dc:creator>Rasika Nayanajith</dc:creator>
    <dc:date>2018-11-23T05:14:30Z</dc:date>
    <item>
      <title>AVC and WLC Load.</title>
      <link>https://community.cisco.com/t5/wireless/avc-and-wlc-load/m-p/3751554#M206753</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;When considering this message from the WLCCA...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD&gt;30070,General: AVC is recommended. Ensure you are using 8.0 or higher, and current load on WLC does not exceed 50%. WLAN: abcd&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;...does the 50% refer to cpu or memory usage?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 16:29:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/avc-and-wlc-load/m-p/3751554#M206753</guid>
      <dc:creator>clearcall</dc:creator>
      <dc:date>2021-07-05T16:29:30Z</dc:date>
    </item>
    <item>
      <title>Re: AVC and WLC Load.</title>
      <link>https://community.cisco.com/t5/wireless/avc-and-wlc-load/m-p/3751747#M206754</link>
      <description>&lt;P&gt;I would think it is AP count. (not 100% sure)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With AVC, if you trying do control part (re-mark, drop,etc) I think that would be more resource intensive &amp;amp; leading to WLC crashes/meltdown in large environment. Below bug may be one of reference that got many cases attached in&amp;nbsp;7.6/8.0 versions&lt;/P&gt;
&lt;P&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuq97965/" target="_self"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuq97965/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As long as you use it to get visibility (simple netflow export), I do not see a major issue of enabling that feature.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;Rasika&lt;/P&gt;
&lt;P&gt;*** Pls rate all useful responses ***&lt;/P&gt;</description>
      <pubDate>Fri, 23 Nov 2018 05:14:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/avc-and-wlc-load/m-p/3751747#M206754</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2018-11-23T05:14:30Z</dc:date>
    </item>
  </channel>
</rss>

