<?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: Network refresh 7363s to r510s in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31622#M8889</link>
    <description>Sounds like there is no real solution here. The standalone firmware will be too time consuming to accomplish, and we can't use unleashed. I think we're just going to do a live cutover and hang APs as we go. I do like the idea of transitioning the old APs to an old ZD for temporary, I think we might have a few lying around.</description>
    <pubDate>Thu, 25 Oct 2018 14:25:14 GMT</pubDate>
    <dc:creator>nathan_mechlowi</dc:creator>
    <dc:date>2018-10-25T14:25:14Z</dc:date>
    <item>
      <title>Network refresh 7363s to r510s</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31617#M8884</link>
      <description>I don't see a compatible firmware that supports both 7363s and r510s. The only way I can think of to avoid downtime is to sever the connection from 7363 radios and the 1200 on firmware 9.12 to force them to operate autonomously until I connect a new AP and repair the connection, with newer firmware on the ZD. I'll probably do it with VLANs. Would this work, and if so, for how long will the 7363s continue to operate?</description>
      <pubDate>Wed, 24 Oct 2018 23:21:21 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31617#M8884</guid>
      <dc:creator>nathan_mechlowi</dc:creator>
      <dc:date>2018-10-24T23:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: Network refresh 7363s to r510s</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31618#M8885</link>
      <description>not sure what features you're using on the 7363 (like radius / 802.1x auth, dpsk, etc). Very few features allow the AP to work in "survivability" mode. You might have better luck disconnecting those APs and loading the stand-alone firmware on them and running them stand-alone (if the features needed are available on stand-alone). Then upgrade the system to allow the R510s to join and swap the APs one by one?&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Wed, 24 Oct 2018 23:29:13 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31618#M8885</guid>
      <dc:creator>diego_garcia_de</dc:creator>
      <dc:date>2018-10-24T23:29:13Z</dc:date>
    </item>
    <item>
      <title>Re: Network refresh 7363s to r510s</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31619#M8886</link>
      <description>The 7363 is supported thru 9.12.x releases, but R510 begins support on 9.13 GA.&lt;BR /&gt;You can upgrade your ZD1200 for the R510s, but might need to run Solo AP firmware on the 7363s.&lt;BR /&gt;Best if not next to your ZD controlled APs, as re-authentication is required when clients roam.</description>
      <pubDate>Wed, 24 Oct 2018 23:29:26 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31619#M8886</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2018-10-24T23:29:26Z</dc:date>
    </item>
    <item>
      <title>Re: Network refresh 7363s to r510s</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31620#M8887</link>
      <description>Probably not long. The timer is set in your ZD. AP will reboot if it cannot contact the ZD, by default in 30 min. You may extend that time, but in most cases, if there is authentication on your WLANs, the wifi will fail almost immediately, since authentication will fail.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I would hang the new APs. They will not be able to connect to the ZD, because they will not be able to downgrade to the ZD version. Old APs would continue to work.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Upgrade the ZD. Now the new APs will start connecting and taking config, while the old ones will fail.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;That's all depends if the license on your ZD supports the two types of APs and their numbers &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;</description>
      <pubDate>Wed, 24 Oct 2018 23:30:36 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31620#M8887</guid>
      <dc:creator>victor_cenac</dc:creator>
      <dc:date>2018-10-24T23:30:36Z</dc:date>
    </item>
    <item>
      <title>Re: Network refresh 7363s to r510s</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31621#M8888</link>
      <description>I'm not sure how many APs you have, but you could keep the ZD on 9.12 and convert the R510 APs to Unleashed.&amp;nbsp; You can maintain current functionality on the 7363 and have close to full ZD functionality on the R510s (25 APs max, 512 users max, no DPSK).&amp;nbsp; &amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Another possibility is to search ebay for a cheap ZD1100 (preferred) or even a ZD1000 with enough licenses and use that for the 7363 APs. Downgrade the code to 9.7.2 if ZD1100 or 9.3.4 if ZD1000.&amp;nbsp; Then you can upgrade the 1200 9.13 or higher for the R510s.&amp;nbsp; The right long term answer is to replace the 7363 APs with a newer model and put everything on the ZD1200. &amp;nbsp; &amp;nbsp; &amp;nbsp;</description>
      <pubDate>Thu, 25 Oct 2018 04:40:30 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31621#M8888</guid>
      <dc:creator>david_black_594</dc:creator>
      <dc:date>2018-10-25T04:40:30Z</dc:date>
    </item>
    <item>
      <title>Re: Network refresh 7363s to r510s</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31622#M8889</link>
      <description>Sounds like there is no real solution here. The standalone firmware will be too time consuming to accomplish, and we can't use unleashed. I think we're just going to do a live cutover and hang APs as we go. I do like the idea of transitioning the old APs to an old ZD for temporary, I think we might have a few lying around.</description>
      <pubDate>Thu, 25 Oct 2018 14:25:14 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31622#M8889</guid>
      <dc:creator>nathan_mechlowi</dc:creator>
      <dc:date>2018-10-25T14:25:14Z</dc:date>
    </item>
    <item>
      <title>Re: Network refresh 7363s to r510s</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31623#M8890</link>
      <description>Actually, creating an Unleashed network with the R510s was a good idea from David...&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://support.ruckuswireless.com/software/1811-ruckus-unleashed-ap-200-6-10-1-312-ga-refresh2-software-for-r510" rel="nofollow"&gt;https://support.ruckuswireless.com/software/1811-ruckus-unleashed-ap-200-6-10-1-312-ga-refresh2-soft...&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You can re-flash the AP code, but if you bought non-Unleashed R510s, you'd get the same for return if warranted.(and would need to re-flash the AP to join your Unleashed)</description>
      <pubDate>Thu, 25 Oct 2018 16:06:59 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31623#M8890</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2018-10-25T16:06:59Z</dc:date>
    </item>
    <item>
      <title>Re: Network refresh 7363s to r510s</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31624#M8891</link>
      <description>We have more than 25 APs at this deployment, and a number of client devices approaching 500. Otherwise, that might be a reasonable solution.</description>
      <pubDate>Thu, 25 Oct 2018 16:19:39 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31624#M8891</guid>
      <dc:creator>nathan_mechlowi</dc:creator>
      <dc:date>2018-10-25T16:19:39Z</dc:date>
    </item>
    <item>
      <title>Re: Network refresh 7363s to r510s</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31625#M8892</link>
      <description>I would hang the new APs. They won't have the capacity to associate with the ZD, in light of the fact that they won't have the capacity to downsize to the ZD variant. Old APs would keep on working&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;see:&amp;nbsp;&lt;A href="https://cleanmaster.me/" rel="nofollow" title="Link: https://cleanmaster.me/"&gt;https://cleanmaster.me/&lt;/A&gt; , &lt;A href="https://downloader.vip/facebook-lite/" rel="nofollow"&gt;https://downloader.vip/facebook-lite/&lt;/A&gt; , &lt;A href="https://mathway.vip/" rel="nofollow"&gt;https://mathway.vip/&lt;/A&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Mon, 05 Nov 2018 07:34:43 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31625#M8892</guid>
      <dc:creator>wahidovic</dc:creator>
      <dc:date>2018-11-05T07:34:43Z</dc:date>
    </item>
    <item>
      <title>Re: Network refresh 7363s to r510s</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31626#M8893</link>
      <description>buy a 2nd 1200 and RDY support (it doesnt cost much). Create a HA pair so the licenses sync. Then break the pair (it will keep licenses for a period of time) , upgrade the secondary to the new load, connect the R510's to the upgraded controller and then when all 7363's are removed, default the primary controller and recreate the HA pair</description>
      <pubDate>Thu, 08 Nov 2018 11:24:52 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31626#M8893</guid>
      <dc:creator>robert_lowe_722</dc:creator>
      <dc:date>2018-11-08T11:24:52Z</dc:date>
    </item>
    <item>
      <title>Re: Network refresh 7363s to r510s</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31627#M8894</link>
      <description>Made a mistake on this, you must remove the primary (the initial ZD1200) and let the new secondary work in failover mode.&amp;nbsp;</description>
      <pubDate>Thu, 08 Nov 2018 23:05:40 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Network-refresh-7363s-to-r510s/m-p/31627#M8894</guid>
      <dc:creator>robert_lowe_722</dc:creator>
      <dc:date>2018-11-08T23:05:40Z</dc:date>
    </item>
  </channel>
</rss>

