<?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 Wireless CAPWAP Control Traffic in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180618#M79077</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;George, Najaf,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So would it be a good idea to place the management interface in its own vlan then? It currently resides in the management vlan. Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 08 Feb 2013 18:01:27 GMT</pubDate>
    <dc:creator>Craddockc</dc:creator>
    <dc:date>2013-02-08T18:01:27Z</dc:date>
    <item>
      <title>Wireless CAPWAP Control Traffic</title>
      <link>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180613#M79072</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was wondering what the best practices were for handling the control traffic of the AP's and controller on the switched network. Is it best to set up a separate VLAN altogether for this traffic? I have a 5508 controller so the management interface is the AP Manager interface. Should I create a separate VLAN for this interface on my network, segmenting this traffic off? Currently it is riding on the management vlan. Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris.&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 06:30:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180613#M79072</guid>
      <dc:creator>Craddockc</dc:creator>
      <dc:date>2021-07-04T06:30:01Z</dc:date>
    </item>
    <item>
      <title>Wireless CAPWAP Control Traffic</title>
      <link>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180614#M79073</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Carddockc,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ideally it is better to have a seperate AP Manager interface for the communication between AP and WLC rather than using managment interface for the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A controller may have one or more AP-manager interfaces, which are used for all Layer 3 communications between the controller and lightweight access points after the access points have joined the controller. The AP-manager IP address is used as the tunnel source for CAPWAP packets from the controller to the access point and as the destination for CAPWAP packets from the access point to the controller.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also please be aware that i&lt;SPAN style="font-size: 10pt;"&gt;f the access points are on a different subnetwork than the one used on the management interface, your network infrastructure must provide multicast routing between the management interface subnet, and the AP subnetwork.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&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;Najaf&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Please rate when applicable or helpful !!!&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2013 01:55:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180614#M79073</guid>
      <dc:creator>kcnajaf</dc:creator>
      <dc:date>2013-02-08T01:55:46Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless CAPWAP Control Traffic</title>
      <link>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180615#M79074</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would tend to disagree. 5508 an wism2 no longer build ap mangers by default. You are fine riding both, especially if you are lag.&lt;BR /&gt;&lt;BR /&gt;But you can break out a ap manger.&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2013 02:02:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180615#M79074</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2013-02-08T02:02:21Z</dc:date>
    </item>
    <item>
      <title>Wireless CAPWAP Control Traffic</title>
      <link>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180616#M79075</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi George,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry my mistake. I didnt realise Chris was refering specific to WLC 5508 here &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&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;Najaf&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2013 02:14:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180616#M79075</guid>
      <dc:creator>kcnajaf</dc:creator>
      <dc:date>2013-02-08T02:14:51Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless CAPWAP Control Traffic</title>
      <link>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180617#M79076</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No worries .. There are still use cases where one might break out ap managers still .. But if you use lag it's a mute point .. Just my 2 cents&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2013 02:58:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180617#M79076</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2013-02-08T02:58:01Z</dc:date>
    </item>
    <item>
      <title>Wireless CAPWAP Control Traffic</title>
      <link>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180618#M79077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;George, Najaf,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So would it be a good idea to place the management interface in its own vlan then? It currently resides in the management vlan. Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2013 18:01:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180618#M79077</guid>
      <dc:creator>Craddockc</dc:creator>
      <dc:date>2013-02-08T18:01:27Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless CAPWAP Control Traffic</title>
      <link>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180619#M79078</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yea just use a management vlan ..&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 10 Feb 2013 03:45:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-capwap-control-traffic/m-p/2180619#M79078</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2013-02-10T03:45:18Z</dc:date>
    </item>
  </channel>
</rss>

