<?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 AP-Manager Interface on WiSM2 in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ap-manager-interface-on-wism2/m-p/1775970#M15406</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Thanks for the input.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Oct 2011 18:11:42 GMT</pubDate>
    <dc:creator>thomas03usmcsf</dc:creator>
    <dc:date>2011-10-12T18:11:42Z</dc:date>
    <item>
      <title>AP-Manager Interface on WiSM2</title>
      <link>https://community.cisco.com/t5/wireless/ap-manager-interface-on-wism2/m-p/1775968#M15404</link>
      <description>&lt;P&gt;I know the WiSM 2 is like the 5500 WLC regarding the fact that you do not need to configure an ap-manager interface for CAPWAP packets because by default the managment interface acts like an ap-manager interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is best practices?&amp;nbsp; Any major advantages or disadvantages by letting the default action occur? &lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 03:54:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-manager-interface-on-wism2/m-p/1775968#M15404</guid>
      <dc:creator>thomas03usmcsf</dc:creator>
      <dc:date>2021-07-04T03:54:54Z</dc:date>
    </item>
    <item>
      <title>AP-Manager Interface on WiSM2</title>
      <link>https://community.cisco.com/t5/wireless/ap-manager-interface-on-wism2/m-p/1775969#M15405</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thomas,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Basically, the need for the ap-manager was not really needed even back in the Airespace days.&amp;nbsp; With the gen2 hardware, 5508/WiSM2 etc, this was relaxed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now on the 5508, if you don't use LAG you would still need to define multiple AP-Managers, 1 per port, if you have more than 48 AP.&amp;nbsp; If you use LAG you only need the one.&amp;nbsp; As the WiSM only does LAG, you only need the management interface, which by default acts as an ap-manager as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMO, if you don't need to burn that IP, then don't.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;P&gt;----------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Please remember to rate helpful posts or to mark the question as answered so that it can be found later.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Oct 2011 14:12:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-manager-interface-on-wism2/m-p/1775969#M15405</guid>
      <dc:creator>Stephen Rodriguez</dc:creator>
      <dc:date>2011-10-12T14:12:55Z</dc:date>
    </item>
    <item>
      <title>AP-Manager Interface on WiSM2</title>
      <link>https://community.cisco.com/t5/wireless/ap-manager-interface-on-wism2/m-p/1775970#M15406</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Thanks for the input.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Oct 2011 18:11:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-manager-interface-on-wism2/m-p/1775970#M15406</guid>
      <dc:creator>thomas03usmcsf</dc:creator>
      <dc:date>2011-10-12T18:11:42Z</dc:date>
    </item>
  </channel>
</rss>

