<?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: Can WiNG AP-6521 adopt with WiNG AP 7522? in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/can-wing-ap-6521-adopt-with-wing-ap-7522/m-p/92098#M8803</link>
    <description>The following AP models can be deployed in a heterogenous AP VC scenario:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;AP 8533 
&lt;/LI&gt;&lt;LI&gt;AP 8432 
&lt;/LI&gt;&lt;LI&gt;AP 7632/AP 7662/AP 7612 
&lt;/LI&gt;&lt;LI&gt;AP 7622/AP7602 
&lt;/LI&gt;&lt;LI&gt;AP 7532/AP 7522/AP 7562 
&lt;/LI&gt;&lt;/UL&gt;Following are the supported adoption hierarchies:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;AP 7662/7632 can adopt AP 7662/7632/7612 
&lt;/LI&gt;&lt;LI&gt;AP 8533/8432 can adopt AP 8533/8432/7562/7532/7522/7662/7632/7622/7612/7602 
&lt;/LI&gt;&lt;LI&gt;AP 7532/7562 can adopt AP7532/AP7562/AP7522 
&lt;/LI&gt;&lt;LI&gt;AP 7532/7562/7522 can be managed by AP8533/AP8432 but not by AP7632/AP7662 
&lt;/LI&gt;&lt;/UL&gt;&lt;OL&gt; 
&lt;LI&gt;In WiNG &lt;B&gt;5.9.2.x&lt;/B&gt;, Express APs are converted to Enterprise APs and as such can be included in the above same family adoption hierarchy; however, it is important to note that an upgraded &lt;U&gt;Express&lt;/U&gt;Virtual Controller will &lt;B&gt;NOT&lt;/B&gt; be able to adopt Non-Express APs. So an Express AP 7522&lt;B&gt;E&lt;/B&gt; Virtual Controller on 5.9.2.x will not be able to adopt and manage Non-Express AP7522 APs, but on the contrary, a Non-Express AP 7522 Virtual Controller will be able to adopt and manage upgraded Express AP 7522E APs. 
&lt;/LI&gt;&lt;/OL&gt;&lt;B&gt;Example&lt;/B&gt;:&lt;BR /&gt;
AP 7522i VC can adopt AP 7522E APs&lt;BR /&gt;
AP 7522E VC cannot adopt AP 7522i APs. &lt;BR /&gt;
&lt;OL&gt; 
&lt;LI&gt;Starting in WiNG &lt;B&gt;5.9.3.0&lt;/B&gt; an Express AP virtual controller will be able to adopt Non-Express Enterprise APs, of course following the supported adoption hierarchies listed above.  
&lt;/LI&gt;&lt;/OL&gt;&lt;B&gt;Example:&lt;/B&gt;&lt;BR /&gt;
AP 7522i VC can adopt AP 7522E APs&lt;BR /&gt;
AP 7522E VC can adopt AP 7522i APs &lt;BR /&gt;
&lt;BR /&gt;
Related article:  &lt;A href="https://gtacknowledge.extremenetworks.com/articles/Solution/WiNG-Express-virtual-controller-not-adopting-non-express-APs" target="_blank" rel="nofollow noreferrer noopener"&gt;WiNG Express virtual controller not adopting non-express APs&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Note:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;Image upload capability will only be enabled on the AP that is elected as VC 
&lt;/LI&gt;&lt;LI&gt;VC can manage up to 64 APs 
&lt;/LI&gt;&lt;LI&gt;AP65xx APs do not support heterogeneous AP adoption and management.  
&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Wed, 22 May 2019 19:57:12 GMT</pubDate>
    <dc:creator>RobertZ</dc:creator>
    <dc:date>2019-05-22T19:57:12Z</dc:date>
    <item>
      <title>Can WiNG AP-6521 adopt with WiNG AP 7522?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/can-wing-ap-6521-adopt-with-wing-ap-7522/m-p/92096#M8801</link>
      <description>We have four no' of WiNG AP-6521 among these AP one of them is acting as a Virtual controller. Now, we are going to add up two more WiNG AP 7522 with WiNG AP-6521 &lt;BR /&gt;
&lt;BR /&gt;
WiNG AP 7522 can adopt with WiNG AP 6521&lt;BR /&gt;
&lt;BR /&gt;
Kindly let us know</description>
      <pubDate>Wed, 22 May 2019 15:59:24 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/can-wing-ap-6521-adopt-with-wing-ap-7522/m-p/92096#M8801</guid>
      <dc:creator>Prabhu_Dhinesh</dc:creator>
      <dc:date>2019-05-22T15:59:24Z</dc:date>
    </item>
    <item>
      <title>Re: Can WiNG AP-6521 adopt with WiNG AP 7522?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/can-wing-ap-6521-adopt-with-wing-ap-7522/m-p/92097#M8802</link>
      <description>Hi Prabhu,&lt;BR /&gt;
&lt;BR /&gt;
AFAIR WiNG version 5.9.1 introduced heterogenous AP management for VC, but only certain models have been enumerated: AP8533, AP8432, AP7632, AP7662, AP7612, AP7622, AP7602, AP7532, AP7522, AP7562. There is some hierarchy of their ability to manage different models (it's not the way that any could manage any).&lt;BR /&gt;
I couldn't find confirmation that 6521s can participate in heterogenous VC deployment at all up to date. I think Extreme might give some info if they are willing to introduce that feature to other models supported in 5.9.x release train.&lt;BR /&gt;
&lt;BR /&gt;
Hope that helps,&lt;BR /&gt;
Tomasz</description>
      <pubDate>Wed, 22 May 2019 18:08:51 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/can-wing-ap-6521-adopt-with-wing-ap-7522/m-p/92097#M8802</guid>
      <dc:creator>Tomasz</dc:creator>
      <dc:date>2019-05-22T18:08:51Z</dc:date>
    </item>
    <item>
      <title>Re: Can WiNG AP-6521 adopt with WiNG AP 7522?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/can-wing-ap-6521-adopt-with-wing-ap-7522/m-p/92098#M8803</link>
      <description>The following AP models can be deployed in a heterogenous AP VC scenario:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;AP 8533 
&lt;/LI&gt;&lt;LI&gt;AP 8432 
&lt;/LI&gt;&lt;LI&gt;AP 7632/AP 7662/AP 7612 
&lt;/LI&gt;&lt;LI&gt;AP 7622/AP7602 
&lt;/LI&gt;&lt;LI&gt;AP 7532/AP 7522/AP 7562 
&lt;/LI&gt;&lt;/UL&gt;Following are the supported adoption hierarchies:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;AP 7662/7632 can adopt AP 7662/7632/7612 
&lt;/LI&gt;&lt;LI&gt;AP 8533/8432 can adopt AP 8533/8432/7562/7532/7522/7662/7632/7622/7612/7602 
&lt;/LI&gt;&lt;LI&gt;AP 7532/7562 can adopt AP7532/AP7562/AP7522 
&lt;/LI&gt;&lt;LI&gt;AP 7532/7562/7522 can be managed by AP8533/AP8432 but not by AP7632/AP7662 
&lt;/LI&gt;&lt;/UL&gt;&lt;OL&gt; 
&lt;LI&gt;In WiNG &lt;B&gt;5.9.2.x&lt;/B&gt;, Express APs are converted to Enterprise APs and as such can be included in the above same family adoption hierarchy; however, it is important to note that an upgraded &lt;U&gt;Express&lt;/U&gt;Virtual Controller will &lt;B&gt;NOT&lt;/B&gt; be able to adopt Non-Express APs. So an Express AP 7522&lt;B&gt;E&lt;/B&gt; Virtual Controller on 5.9.2.x will not be able to adopt and manage Non-Express AP7522 APs, but on the contrary, a Non-Express AP 7522 Virtual Controller will be able to adopt and manage upgraded Express AP 7522E APs. 
&lt;/LI&gt;&lt;/OL&gt;&lt;B&gt;Example&lt;/B&gt;:&lt;BR /&gt;
AP 7522i VC can adopt AP 7522E APs&lt;BR /&gt;
AP 7522E VC cannot adopt AP 7522i APs. &lt;BR /&gt;
&lt;OL&gt; 
&lt;LI&gt;Starting in WiNG &lt;B&gt;5.9.3.0&lt;/B&gt; an Express AP virtual controller will be able to adopt Non-Express Enterprise APs, of course following the supported adoption hierarchies listed above.  
&lt;/LI&gt;&lt;/OL&gt;&lt;B&gt;Example:&lt;/B&gt;&lt;BR /&gt;
AP 7522i VC can adopt AP 7522E APs&lt;BR /&gt;
AP 7522E VC can adopt AP 7522i APs &lt;BR /&gt;
&lt;BR /&gt;
Related article:  &lt;A href="https://gtacknowledge.extremenetworks.com/articles/Solution/WiNG-Express-virtual-controller-not-adopting-non-express-APs" target="_blank" rel="nofollow noreferrer noopener"&gt;WiNG Express virtual controller not adopting non-express APs&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Note:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;Image upload capability will only be enabled on the AP that is elected as VC 
&lt;/LI&gt;&lt;LI&gt;VC can manage up to 64 APs 
&lt;/LI&gt;&lt;LI&gt;AP65xx APs do not support heterogeneous AP adoption and management.  
&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Wed, 22 May 2019 19:57:12 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/can-wing-ap-6521-adopt-with-wing-ap-7522/m-p/92098#M8803</guid>
      <dc:creator>RobertZ</dc:creator>
      <dc:date>2019-05-22T19:57:12Z</dc:date>
    </item>
  </channel>
</rss>

