<?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: CAPWAP teardown? in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/capwap-teardown/m-p/2315217#M161031</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is the preferred load balancing method you should use. This will help AP&amp;lt;-----&amp;gt; WLC traffic always goes through the same physical link of your ether channel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To confirm what happen to ap registration, you have to do a test like I mentioned earlier &amp;amp; get the AP console output while your are doing this test. It will prove whether AP disassociate when a physical interface goes down in a etherchannel which carry the CAPWAP traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Rasika&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;**** Pls rate all useful responses ****&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Oct 2013 03:56:41 GMT</pubDate>
    <dc:creator>Rasika Nayanajith</dc:creator>
    <dc:date>2013-10-16T03:56:41Z</dc:date>
    <item>
      <title>CAPWAP teardown?</title>
      <link>https://community.cisco.com/t5/wireless/capwap-teardown/m-p/2315213#M161027</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Need help to understand how the CAPWAP tunnel work when one in the bundled (group of 4) port from portchannel group was shutdown.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's the logical diagram&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;APs &lt;/STRONG&gt;&amp;lt;-&amp;gt; &lt;STRONG&gt;Access Switch&lt;/STRONG&gt; &amp;lt;-&lt;SPAN style="color: #ff0000;"&gt;portchannel&lt;/SPAN&gt;-&amp;gt; &lt;STRONG&gt;Distri Switch&lt;/STRONG&gt; &amp;lt;-portchannel-&amp;gt; &lt;STRONG&gt;Core Switch&lt;/STRONG&gt; &amp;lt;-portchannel-&amp;gt; &lt;STRONG&gt;WLC&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;1 of 4 bundled uplink ports in portchannel shown in &lt;SPAN style="color: #ff0000;"&gt;RED text &lt;SPAN style="color: #000000;"&gt;was shutdown &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt; color: #333333;"&gt;deliberately &lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10pt;"&gt;during this time the Prime Infra 1.3 reports that APs was disassociated from the controller and 1 minute later Prime Infra reports that the APs was now associated to the controller without touching any devices.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 10pt;"&gt;Is this a normal behaviour of a CAPWAP? If not then, what should I do?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 10pt; "&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 10pt; "&gt;Dave&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 10pt; "&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 08:04:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-teardown/m-p/2315213#M161027</guid>
      <dc:creator>Dave Anthony David</dc:creator>
      <dc:date>2021-07-04T08:04:02Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP teardown?</title>
      <link>https://community.cisco.com/t5/wireless/capwap-teardown/m-p/2315214#M161028</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is the load-balancing mechanism of your switch etherchannels ? "&lt;STRONG style="font-size: 10pt;"&gt;show etherchannel load-balance&lt;/STRONG&gt;&lt;SPAN style="font-size: 10pt;"&gt;" should tells you this.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;If AP to WLC capwap traffic went through the interface you shutdown, then there is possibility your AP lost connectivity to WLC momentarily. But should not take that long to revert traffic to any other interfaces.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;You can do a test like this. Enable Telnet for one your AP (via WLC GUI : Wireless -&amp;gt; select your AP -&amp;gt; Advanced -&amp;gt; tick Telnet checkbox). Then telnet to AP &amp;amp; ping your WLC IP from there. Then shutdown one of your (out of 4)&amp;nbsp; your switch etherchannel interface &amp;amp; see whether you will see ping drops for short period of time). If packet drops see how many drops before getting the connectivity back.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;HTH&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Rasika&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;**** Pls rate all useful responses ****&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Oct 2013 22:40:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-teardown/m-p/2315214#M161028</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2013-10-15T22:40:52Z</dc:date>
    </item>
    <item>
      <title>CAPWAP teardown?</title>
      <link>https://community.cisco.com/t5/wireless/capwap-teardown/m-p/2315215#M161029</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Considering the scenario provided that is due to the ether-channel configuration&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Oct 2013 23:34:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-teardown/m-p/2315215#M161029</guid>
      <dc:creator>kaaftab</dc:creator>
      <dc:date>2013-10-15T23:34:06Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP teardown?</title>
      <link>https://community.cisco.com/t5/wireless/capwap-teardown/m-p/2315216#M161030</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;DS1#sh etherchannel load-balance&lt;/P&gt;&lt;P&gt;EtherChannel Load-Balancing Configuration:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; src-dst-ip&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EtherChannel Load-Balancing Addresses Used Per-Protocol:&lt;/P&gt;&lt;P&gt;Non-IP: Source XOR Destination MAC address&lt;/P&gt;&lt;P&gt;&amp;nbsp; IPv4: Source XOR Destination IP address&lt;/P&gt;&lt;P&gt;&amp;nbsp; IPv6: Source XOR Destination IP address&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AS1#sh etherchannel load-balance&lt;/P&gt;&lt;P&gt;EtherChannel Load-Balancing Configuration:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; src-dst-ip&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With this, can you confirm if this is the default behaviour of CAPWAP when traversing etherchannel ports?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Oct 2013 02:36:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-teardown/m-p/2315216#M161030</guid>
      <dc:creator>Dave Anthony David</dc:creator>
      <dc:date>2013-10-16T02:36:25Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP teardown?</title>
      <link>https://community.cisco.com/t5/wireless/capwap-teardown/m-p/2315217#M161031</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is the preferred load balancing method you should use. This will help AP&amp;lt;-----&amp;gt; WLC traffic always goes through the same physical link of your ether channel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To confirm what happen to ap registration, you have to do a test like I mentioned earlier &amp;amp; get the AP console output while your are doing this test. It will prove whether AP disassociate when a physical interface goes down in a etherchannel which carry the CAPWAP traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Rasika&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;**** Pls rate all useful responses ****&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Oct 2013 03:56:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-teardown/m-p/2315217#M161031</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2013-10-16T03:56:41Z</dc:date>
    </item>
  </channel>
</rss>

