<?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 My primary requirement is to in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/multiple-ap-manager-interfaces-for-the-large-network-comprising/m-p/2928010#M56003</link>
    <description>&lt;PRE class="prettyprint"&gt;&lt;SPAN&gt;My primary requirement is to have atleast 4 subnets for these large number of APs rather than having a single /23 subnet.&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN&gt;This does not require to create multiple AP manager interfaces on WLC. AP management can be in any number of vlans/subnets. You simply require to have AP to WLC IP connectivity and APs &amp;nbsp;learn about WLC to go &amp;amp; register.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;In summary, just enable LAG &amp;amp; make WLC management interface as AP manager interface.&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;*** Pls rate all useful responses ***&lt;/P&gt;</description>
    <pubDate>Sat, 16 Jul 2016 21:30:06 GMT</pubDate>
    <dc:creator>Rasika Nayanajith</dc:creator>
    <dc:date>2016-07-16T21:30:06Z</dc:date>
    <item>
      <title>Multiple ap manager interfaces for the large network comprising of 1000+ APs</title>
      <link>https://community.cisco.com/t5/wireless/multiple-ap-manager-interfaces-for-the-large-network-comprising/m-p/2928009#M56002</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I have a large site coming over with 1000+ APs.&lt;/P&gt;
&lt;P&gt;Per the design requirement I need to have LAG configured and at the same time having multiple AP manager interfaces. However these two requirement are not supported simultaneously by Cisco Code:&lt;/P&gt;
&lt;P&gt;Per documentation:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;EM&gt;&lt;SPAN style="font-size: 8.0pt;"&gt; If link aggregation (LAG) is enabled, there can be only one AP-manager interface. But when LAG is&lt;/SPAN&gt;&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;EM&gt;&lt;SPAN style="font-size: 8.0pt;"&gt;disabled, one or more AP-manager interfaces can be created, generally one per physical port.&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P style="text-indent: .5in;"&gt;&lt;EM&gt;&lt;SPAN style="font-size: 8.0pt; color: red;"&gt;◦When LAG is enabled—Supports only one AP Manager, which can either be on the management or dynamic interface with AP management.&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P style="text-indent: .5in;"&gt;&lt;EM&gt;&lt;SPAN style="font-size: 8.0pt;"&gt;◦When LAG is disabled—Supports one AP Manager per port. The Dynamic Interface tied to a VLAN can act as an AP Manager (when enabled).&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;SPAN style="font-size: 8.0pt;"&gt;When you enable LAG, all the ports would lose their AP Manager status and the AP management reverts back onto the Management interface.&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;SPAN style="font-size: 8.0pt;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;Generally as per recommended practices, it better not to have all large number of APs as part of a single vlan. But the code limitation limits me to proceed with the recommended practices.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Could someone please suggest how would I be able to achieve the client requirement of having multiple ap manager interfaces while at the same time having the LAG configured? My primary requirement is to have atleast 4 subnets for these large number of APs rather than having a single /23 subnet.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Adnan&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 12:26:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/multiple-ap-manager-interfaces-for-the-large-network-comprising/m-p/2928009#M56002</guid>
      <dc:creator>Muhammed Adnan</dc:creator>
      <dc:date>2021-07-05T12:26:19Z</dc:date>
    </item>
    <item>
      <title>My primary requirement is to</title>
      <link>https://community.cisco.com/t5/wireless/multiple-ap-manager-interfaces-for-the-large-network-comprising/m-p/2928010#M56003</link>
      <description>&lt;PRE class="prettyprint"&gt;&lt;SPAN&gt;My primary requirement is to have atleast 4 subnets for these large number of APs rather than having a single /23 subnet.&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN&gt;This does not require to create multiple AP manager interfaces on WLC. AP management can be in any number of vlans/subnets. You simply require to have AP to WLC IP connectivity and APs &amp;nbsp;learn about WLC to go &amp;amp; register.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;In summary, just enable LAG &amp;amp; make WLC management interface as AP manager interface.&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;*** Pls rate all useful responses ***&lt;/P&gt;</description>
      <pubDate>Sat, 16 Jul 2016 21:30:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/multiple-ap-manager-interfaces-for-the-large-network-comprising/m-p/2928010#M56003</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2016-07-16T21:30:06Z</dc:date>
    </item>
    <item>
      <title>Years ago there would be</title>
      <link>https://community.cisco.com/t5/wireless/multiple-ap-manager-interfaces-for-the-large-network-comprising/m-p/2928011#M56004</link>
      <description>&lt;P&gt;Years ago there would be multiple ap managers but today one is only needed.&lt;/P&gt;</description>
      <pubDate>Sun, 17 Jul 2016 01:40:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/multiple-ap-manager-interfaces-for-the-large-network-comprising/m-p/2928011#M56004</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2016-07-17T01:40:16Z</dc:date>
    </item>
  </channel>
</rss>

