<?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: Problem assigning AP7662 to Device Group in Extreme Cloud</title>
    <link>https://community.extremenetworks.com/t5/extreme-cloud/problem-assigning-ap7662-to-device-group/m-p/83388#M662</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;  &lt;P&gt;as the “legacy” Accesspoints are not fully supported in ECA 4.76, I think you cannot create new rules for such “legacy” accesspoints, they are only adopted if rules exist before the upgrade, as I understand the release notes of 04.76.2.35:&lt;/P&gt;  &lt;P&gt;---&lt;/P&gt;  &lt;P&gt;Re-introduced support for Distributed site deployments through upgrade. Upgrade process grandfathers Distributed sites through upgrade from 4.56 release or configuration import. &lt;STRONG&gt;Settings and assignments for Legacy WiNG (AP75xx, AP76xx, AP8533/8432) or AP5xx models are preserved on upgrade. Grandfathering supports: - Creation of new sites (per 4.56 adopted device set)&lt;/STRONG&gt; - Adoption of WiNG Legacy or AP5xx devices to existing or new sites - Leveraging auto-adoption rules to Distributed Sites. Caveats: AP4xx access points are supported in a Centralized site only. AP4xx will not adopt or extend a Distributed site. A fresh installation of 4.76.02: - Does not support Distributed sites or adoption of Legacy AP models - AP5xx and AP4xx models adopt only to a Centralized site.&lt;/P&gt;  &lt;HR /&gt;&lt;P&gt;Martin&lt;/P&gt;</description>
    <pubDate>Tue, 21 Jul 2020 02:30:04 GMT</pubDate>
    <dc:creator>Martin8052</dc:creator>
    <dc:date>2020-07-21T02:30:04Z</dc:date>
    <item>
      <title>Problem assigning AP7662 to Device Group</title>
      <link>https://community.extremenetworks.com/t5/extreme-cloud/problem-assigning-ap7662-to-device-group/m-p/83387#M661</link>
      <description>&lt;P&gt;Hi.&lt;/P&gt;  &lt;P&gt;Has anyone had trouble assigning AP7662 APs to a device group in an ECA?&lt;/P&gt;  &lt;P&gt;The ECA is an E3120 and has a version 04.76.02.003.&lt;BR /&gt; I have created an adoption policy and with the models AP7632 and AP8432 I have not had any problem.&lt;/P&gt;  &lt;P&gt;AP 7662 is adopted, but by not falling into any adoption policy rule, I have tried to manually assign it its device group, but was not successful.&lt;/P&gt;  &lt;P&gt;Greetings and in advance thank you.&lt;/P&gt;  &lt;FIGURE&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="57b6ed615b0e48ce8bc7de4e04e13aa5_6e296eff-f4c2-4f8f-923f-73c05b6d2338.jpg"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/912i49A05ADA739A4BAC/image-size/large?v=v2&amp;amp;px=999" role="button" title="57b6ed615b0e48ce8bc7de4e04e13aa5_6e296eff-f4c2-4f8f-923f-73c05b6d2338.jpg" alt="57b6ed615b0e48ce8bc7de4e04e13aa5_6e296eff-f4c2-4f8f-923f-73c05b6d2338.jpg" /&gt;&lt;/span&gt;&lt;/FIGURE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;FIGURE&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="57b6ed615b0e48ce8bc7de4e04e13aa5_38d8bcd3-4aea-4caa-9bcb-d8dec6c5a864.jpg"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/4690iF74C8D7EC0E20CDB/image-size/large?v=v2&amp;amp;px=999" role="button" title="57b6ed615b0e48ce8bc7de4e04e13aa5_38d8bcd3-4aea-4caa-9bcb-d8dec6c5a864.jpg" alt="57b6ed615b0e48ce8bc7de4e04e13aa5_38d8bcd3-4aea-4caa-9bcb-d8dec6c5a864.jpg" /&gt;&lt;/span&gt;&lt;/FIGURE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;FIGURE&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="57b6ed615b0e48ce8bc7de4e04e13aa5_9c30de43-f83c-47fe-bd4a-5bd1c8606b5f.jpg"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/1944iE62EAB73E594EBB5/image-size/large?v=v2&amp;amp;px=999" role="button" title="57b6ed615b0e48ce8bc7de4e04e13aa5_9c30de43-f83c-47fe-bd4a-5bd1c8606b5f.jpg" alt="57b6ed615b0e48ce8bc7de4e04e13aa5_9c30de43-f83c-47fe-bd4a-5bd1c8606b5f.jpg" /&gt;&lt;/span&gt;&lt;/FIGURE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jul 2020 22:44:29 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extreme-cloud/problem-assigning-ap7662-to-device-group/m-p/83387#M661</guid>
      <dc:creator>Jorge_Cota</dc:creator>
      <dc:date>2020-07-15T22:44:29Z</dc:date>
    </item>
    <item>
      <title>Re: Problem assigning AP7662 to Device Group</title>
      <link>https://community.extremenetworks.com/t5/extreme-cloud/problem-assigning-ap7662-to-device-group/m-p/83388#M662</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;  &lt;P&gt;as the “legacy” Accesspoints are not fully supported in ECA 4.76, I think you cannot create new rules for such “legacy” accesspoints, they are only adopted if rules exist before the upgrade, as I understand the release notes of 04.76.2.35:&lt;/P&gt;  &lt;P&gt;---&lt;/P&gt;  &lt;P&gt;Re-introduced support for Distributed site deployments through upgrade. Upgrade process grandfathers Distributed sites through upgrade from 4.56 release or configuration import. &lt;STRONG&gt;Settings and assignments for Legacy WiNG (AP75xx, AP76xx, AP8533/8432) or AP5xx models are preserved on upgrade. Grandfathering supports: - Creation of new sites (per 4.56 adopted device set)&lt;/STRONG&gt; - Adoption of WiNG Legacy or AP5xx devices to existing or new sites - Leveraging auto-adoption rules to Distributed Sites. Caveats: AP4xx access points are supported in a Centralized site only. AP4xx will not adopt or extend a Distributed site. A fresh installation of 4.76.02: - Does not support Distributed sites or adoption of Legacy AP models - AP5xx and AP4xx models adopt only to a Centralized site.&lt;/P&gt;  &lt;HR /&gt;&lt;P&gt;Martin&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jul 2020 02:30:04 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extreme-cloud/problem-assigning-ap7662-to-device-group/m-p/83388#M662</guid>
      <dc:creator>Martin8052</dc:creator>
      <dc:date>2020-07-21T02:30:04Z</dc:date>
    </item>
  </channel>
</rss>

