<?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: NX5500 as failover for existent RFS6000 and adopt the AP621 in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-as-failover-for-existent-rfs6000-and-adopt-the-ap621/m-p/25707#M2449</link>
    <description>Thank you Andy, &lt;BR /&gt;
I am afraid we are on the same page! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Thu, 28 Jun 2018 18:16:00 GMT</pubDate>
    <dc:creator>theoadon</dc:creator>
    <dc:date>2018-06-28T18:16:00Z</dc:date>
    <item>
      <title>NX5500 as failover for existent RFS6000 and adopt the AP621</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-as-failover-for-existent-rfs6000-and-adopt-the-ap621/m-p/25705#M2447</link>
      <description>A site has 37 AP621 with an RFS6000 5.4.3.0-018R. &lt;BR /&gt;
We must add a second controller for redundancy - high availability. &lt;BR /&gt;
We need to know if an NX5500 can do this job , and if can adopt the existing AP621s.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Jun 2018 18:03:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-as-failover-for-existent-rfs6000-and-adopt-the-ap621/m-p/25705#M2447</guid>
      <dc:creator>theoadon</dc:creator>
      <dc:date>2018-06-28T18:03:00Z</dc:date>
    </item>
    <item>
      <title>RE: NX5500 as failover for existent RFS6000 and adopt the AP621</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-as-failover-for-existent-rfs6000-and-adopt-the-ap621/m-p/25706#M2448</link>
      <description>Hi&lt;BR /&gt;
&lt;BR /&gt;
There are a couple of issues here.&lt;BR /&gt;
&lt;BR /&gt;
1 - to cluster two controllers the need to be the same model You can not cluster an RFS6000 and an NX5500&lt;BR /&gt;
&lt;BR /&gt;
2 - 5.4.3 is extremely out of date. you will need to upgrade, but you be limited due to the AP models you have installed&lt;BR /&gt;
&lt;BR /&gt;
3- AP621's are obsolete. Would recommend investigating upgrading to a newer model&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Jun 2018 18:12:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-as-failover-for-existent-rfs6000-and-adopt-the-ap621/m-p/25706#M2448</guid>
      <dc:creator>aholden</dc:creator>
      <dc:date>2018-06-28T18:12:00Z</dc:date>
    </item>
    <item>
      <title>RE: NX5500 as failover for existent RFS6000 and adopt the AP621</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-as-failover-for-existent-rfs6000-and-adopt-the-ap621/m-p/25707#M2449</link>
      <description>Thank you Andy, &lt;BR /&gt;
I am afraid we are on the same page! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Jun 2018 18:16:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-as-failover-for-existent-rfs6000-and-adopt-the-ap621/m-p/25707#M2449</guid>
      <dc:creator>theoadon</dc:creator>
      <dc:date>2018-06-28T18:16:00Z</dc:date>
    </item>
    <item>
      <title>RE: NX5500 as failover for existent RFS6000 and adopt the AP621</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-as-failover-for-existent-rfs6000-and-adopt-the-ap621/m-p/25708#M2450</link>
      <description>As Andy stated, you must use two of the same model of controller to establish a cluster.&lt;BR /&gt;
5.8.4 is the last version released by Zebra before the WiNG portfolio was sold to Extreme, and that version appears to have AP621 support, and it is within the supported versions of the NX5500, so it is within the realm of possibility to replace the controllers first and then roll out newer APs without incurring significant down time, and then upgrade to the latest firmware release.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Jun 2018 18:35:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-as-failover-for-existent-rfs6000-and-adopt-the-ap621/m-p/25708#M2450</guid>
      <dc:creator>Andrew_Webster</dc:creator>
      <dc:date>2018-06-28T18:35:00Z</dc:date>
    </item>
    <item>
      <title>RE: NX5500 as failover for existent RFS6000 and adopt the AP621</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-as-failover-for-existent-rfs6000-and-adopt-the-ap621/m-p/25709#M2451</link>
      <description>Hi&lt;BR /&gt;
&lt;BR /&gt;
just a follow up, 5.5.6 is the oldest release that can be provided. This is a contractual restriction with Motorola.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Jun 2018 18:41:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-as-failover-for-existent-rfs6000-and-adopt-the-ap621/m-p/25709#M2451</guid>
      <dc:creator>aholden</dc:creator>
      <dc:date>2018-06-28T18:41:00Z</dc:date>
    </item>
    <item>
      <title>RE: NX5500 as failover for existent RFS6000 and adopt the AP621</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-as-failover-for-existent-rfs6000-and-adopt-the-ap621/m-p/25710#M2452</link>
      <description>Thanks Andy , really helpful!&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Jun 2018 18:44:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-as-failover-for-existent-rfs6000-and-adopt-the-ap621/m-p/25710#M2452</guid>
      <dc:creator>theoadon</dc:creator>
      <dc:date>2018-06-28T18:44:00Z</dc:date>
    </item>
  </channel>
</rss>

