<?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: Opening CAPWAP on differentes interfaces in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/opening-capwap-on-differentes-interfaces/m-p/1902277#M95170</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;AP discovery and join is handled by mgt interface. Any other interface you create is purely for WLAN traffic and that is if you don't want the mgmt interface to handle WLAN client traffic&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 10 May 2012 16:41:25 GMT</pubDate>
    <dc:creator>grabonlee</dc:creator>
    <dc:date>2012-05-10T16:41:25Z</dc:date>
    <item>
      <title>Opening CAPWAP on differentes interfaces</title>
      <link>https://community.cisco.com/t5/wireless/opening-capwap-on-differentes-interfaces/m-p/1902276#M95169</link>
      <description>&lt;P&gt;Please, I am trying to configure two AP-management interfaces to accept CAPWAP on different ports using the option "Enable Dynamic AP Management". One of them uses public ip address. However, I getting the message "Ignoring discovery request received on non-management interface ..." on this. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The controller is 5508.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cleber&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 05:09:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/opening-capwap-on-differentes-interfaces/m-p/1902276#M95169</guid>
      <dc:creator>cweissheimer</dc:creator>
      <dc:date>2021-07-04T05:09:01Z</dc:date>
    </item>
    <item>
      <title>Re: Opening CAPWAP on differentes interfaces</title>
      <link>https://community.cisco.com/t5/wireless/opening-capwap-on-differentes-interfaces/m-p/1902277#M95170</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;AP discovery and join is handled by mgt interface. Any other interface you create is purely for WLAN traffic and that is if you don't want the mgmt interface to handle WLAN client traffic&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 May 2012 16:41:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/opening-capwap-on-differentes-interfaces/m-p/1902277#M95170</guid>
      <dc:creator>grabonlee</dc:creator>
      <dc:date>2012-05-10T16:41:25Z</dc:date>
    </item>
    <item>
      <title>Re: Opening CAPWAP on differentes interfaces</title>
      <link>https://community.cisco.com/t5/wireless/opening-capwap-on-differentes-interfaces/m-p/1902278#M95171</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for answering. I think that join is handled by AP management interface and mgmt interface usually is used. But, as the manual says, it´s possible to have more than one interface working as AP management (there is a option in interface configuration that is called "Enable Dynamic AP Management" for it). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the controller would accept joins through different interfaces (and different ports).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cleber&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 May 2012 19:07:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/opening-capwap-on-differentes-interfaces/m-p/1902278#M95171</guid>
      <dc:creator>cweissheimer</dc:creator>
      <dc:date>2012-05-10T19:07:07Z</dc:date>
    </item>
    <item>
      <title>Re: Opening CAPWAP on differentes interfaces</title>
      <link>https://community.cisco.com/t5/wireless/opening-capwap-on-differentes-interfaces/m-p/1902279#M95172</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Cleber&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For the 5500, the Management interface acts as AP manager interface by default in conjuction with handling Inter-controller communication and communication with Enterprise services such as AAA. If you want enable other dynamic interfaces as AP manager, which I guess is what you want, then you must disable Dynamic AP Management on the Management interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 May 2012 20:07:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/opening-capwap-on-differentes-interfaces/m-p/1902279#M95172</guid>
      <dc:creator>grabonlee</dc:creator>
      <dc:date>2012-05-10T20:07:55Z</dc:date>
    </item>
    <item>
      <title>Re: Opening CAPWAP on differentes interfaces</title>
      <link>https://community.cisco.com/t5/wireless/opening-capwap-on-differentes-interfaces/m-p/1902280#M95173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Cleber,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me give a bit of background on the AP join process, it may help explain this scenario. There are 4 steps in the initial connection setup:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Discovery Request sent by AP to WLC&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - This discovery request must be sent to the *management* interface on the WLC. Only the management interface currently listens for discovery requests.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Discovery Response sent by WLC to AP&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - This response indicates the IP addresses of the available AP managers on the WLC. This will likely include the management IP address itself, and also any other interfaces you have set the Dynamic AP Management on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. Join Request sent by AP to WLC&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - This request is sent to the desired ap management interface, which can be either management or a dynamic AP management interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. Join Response sent by WLC to AP&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Confirmation of initial setup, DTLS tunnel is then created between AP and indicated interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, you can still use multiple AP managers to load balance the capwap&amp;nbsp; traffic between interfaces/ports. However, the initial discovery request must be received by the management interface, and you need to tell your APs to send the discovery request to the management IP address, through DHCP option 43, DNS, or broadcast forwarding.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hopefully this clears up some of the confusion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Pat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 May 2012 20:34:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/opening-capwap-on-differentes-interfaces/m-p/1902280#M95173</guid>
      <dc:creator>pcroak</dc:creator>
      <dc:date>2012-05-10T20:34:44Z</dc:date>
    </item>
  </channel>
</rss>

