<?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 Capwap high bandwidth utilization in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/capwap-high-bandwidth-utilization/m-p/1678091#M95209</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to know if this traffic is correct... (wan link - remote APs)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;minute:&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/8/8/4/47488-untitled.bmp" alt="untitled.bmp" class="jive-image-thumbnail jive-image" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;15 minutes:&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/7/6/5/47567-untitled2.bmp" alt="untitled2.bmp" class="jive-image-thumbnail jive-image" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think that something is wrong... there is a high bandwidth utilization.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All APs are configured with h-reap and local switching.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All traffic wan link - 15 minutes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/8/6/5/47568-untitled3.bmp" alt="untitled3.bmp" class="jive-image-thumbnail jive-image" onclick="" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks.&lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 03:08:39 GMT</pubDate>
    <dc:creator>mscottini</dc:creator>
    <dc:date>2021-07-04T03:08:39Z</dc:date>
    <item>
      <title>Capwap high bandwidth utilization</title>
      <link>https://community.cisco.com/t5/wireless/capwap-high-bandwidth-utilization/m-p/1678091#M95209</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to know if this traffic is correct... (wan link - remote APs)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;minute:&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/8/8/4/47488-untitled.bmp" alt="untitled.bmp" class="jive-image-thumbnail jive-image" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;15 minutes:&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/7/6/5/47567-untitled2.bmp" alt="untitled2.bmp" class="jive-image-thumbnail jive-image" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think that something is wrong... there is a high bandwidth utilization.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All APs are configured with h-reap and local switching.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All traffic wan link - 15 minutes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/8/6/5/47568-untitled3.bmp" alt="untitled3.bmp" class="jive-image-thumbnail jive-image" onclick="" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks.&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 03:08:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-high-bandwidth-utilization/m-p/1678091#M95209</guid>
      <dc:creator>mscottini</dc:creator>
      <dc:date>2021-07-04T03:08:39Z</dc:date>
    </item>
    <item>
      <title>Re: Capwap high bandwidth utilization</title>
      <link>https://community.cisco.com/t5/wireless/capwap-high-bandwidth-utilization/m-p/1678092#M95210</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Maybe this answer my question?&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;SPAN class="content"&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;H3&gt;
&lt;A name="ongo"&gt;Ongoing Exchanges&lt;/A&gt;
&lt;/H3&gt; 
&lt;H4&gt;
&lt;A name="hb"&gt;Heartbeat&lt;/A&gt;
&lt;/H4&gt; 
&amp;nbsp; &lt;P&gt;The LWAPP architecture provides for a heartbeat timer that is
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; accomplished by a series of &lt;STRONG&gt;Echo Requests&lt;/STRONG&gt; and &lt;STRONG&gt;Echo
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Responses&lt;/STRONG&gt;. An AP periodically sends Echo Requests in order to
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; determine the state of the connection between the AP and the WLC. In response,
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the WLC sends the Echo Response in order to acknowledge the receipt of the Echo
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Request. The AP, then, resets the heartbeat timer to the
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;EchoInterval&lt;/STRONG&gt;. The LWAPP protocol specification draft contains
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; a detailed description of these timers. The system heartbeat, coupled with
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; fallback mechanism, is 4 packets every 30 seconds and is comprised of these
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; packets:&lt;/P&gt; 
&amp;nbsp; &lt;BLOCKQUOTE class="jive-quote"&gt;
&lt;PRE&gt;LWAPP ECHO_REQUEST from AP (78 bytes)&lt;BR /&gt;LWAPP Echo-Response to AP (64 bytes)&lt;BR /&gt;LWAPP PRIMARY_DISCOVERY_REQ from AP (93 bytes)&lt;BR /&gt;LWAPP Primary Discovery-Response to AP (97 bytes)&lt;/PRE&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;This exchange generates 33 bytes of traffic every 30 seconds.&lt;/P&gt;
&lt;H4&gt;&lt;A name="measure"&gt;RRM Measurements&lt;/A&gt;&lt;/H4&gt;
&lt;P&gt;There are two ongoing RRM exchanges. The first one, at every 60-second &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; interval, is the load and signal measurement and consists of 4 packets. This &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; exchange always adds up to 396 bytes:&lt;/P&gt;
&lt;BLOCKQUOTE class="jive-quote"&gt;
&lt;PRE&gt;LWAPP RRM_DATA_REQ from AP (107 bytes)&lt;BR /&gt;LWAPP Airewave-Director-Data Response to AP (64 bytes)&lt;BR /&gt;LWAPP RRM_DATA_REQ from AP (161 bytes)&lt;BR /&gt;LWAPP Airewave-Director-Data Response to AP (64 bytes)&lt;/PRE&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;The second sequence of packets is the noise measurement that includes a &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; statistics information request and response sequence. It is done every 180 &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; seconds. This short exchange of packets averages approximately 2,660 bytes and &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; typically lasts 0.01 seconds. It consists of these packets:&lt;/P&gt;
&lt;BLOCKQUOTE class="jive-quote"&gt;
&lt;PRE&gt;LWAPP RRM_DATA_REQ from AP&lt;BR /&gt;LWAPP Airewave-Director-Data Response to AP &lt;BR /&gt;LWAPP RRM_DATA_REQ from AP &lt;BR /&gt;LWAPP Airewave-Director-Data Response to AP &lt;BR /&gt;LWAPP RRM_DATA_REQ from AP&lt;BR /&gt;LWAPP Airewave-Director-Data Response to AP &lt;BR /&gt;LWAPP RRM_DATA_REQ from AP&lt;BR /&gt;LWAPP Airewave-Director-Data Response to AP&lt;BR /&gt;&lt;BR /&gt;LWAPP STATISTICS_INFO from AP&lt;BR /&gt;LWAPP Statistics-Info Response to AP&lt;BR /&gt;&lt;BR /&gt;LWAPP RRM_DATA_REQ from AP&lt;BR /&gt;LWAPP Airewave-Director-Data Response to AP&lt;BR /&gt;LWAPP RRM_DATA_REQ from AP&lt;BR /&gt;LWAPP Airewave-Director-Data Response to AP&lt;BR /&gt;LWAPP RRM_DATA_REQ from AP 00:14:1b:59:41:80&lt;BR /&gt;LWAPP Airewave-Director-Data Response to AP&lt;BR /&gt;LWAPP RRM_DATA_REQ from AP&lt;BR /&gt;LWAPP Airewave-Director-Data Response to AP&lt;BR /&gt;&lt;BR /&gt;LWAPP STATISTICS_INFO from AP &lt;BR /&gt;LWAPP Statistics-Info Response to AP&lt;/PRE&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&lt;/P&gt;
&lt;/PRE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 May 2011 14:03:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-high-bandwidth-utilization/m-p/1678092#M95210</guid>
      <dc:creator>mscottini</dc:creator>
      <dc:date>2011-05-02T14:03:53Z</dc:date>
    </item>
  </channel>
</rss>

