<?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: Backwards migration - vSCG to ZD in RUCKUS Cloud</title>
    <link>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/10921#M135</link>
    <description>@michael Brado&amp;nbsp;&lt;BR /&gt;we execute an migration fro vSCG to ZD firmware with the folllowing commands&lt;BR /&gt;fw set host xx.xx.xx.xx&lt;BR /&gt;fw set proto ftp&lt;BR /&gt;fw set user ftpuser&lt;BR /&gt;fw set password xxxxxx&lt;BR /&gt;fw set control r700/9.13.3.0.41/r700_9133_cntrl.rcks&lt;BR /&gt;fw update&amp;nbsp;&lt;BR /&gt;reboot&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;After the firmware flash we are able to logon but the AP reboots after 30 seconds&lt;BR /&gt;set scg disable&lt;BR /&gt;set csg ip del&lt;BR /&gt;set director ip xx.xx.xx.xx&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;AP is in Stand-alone mode.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;### Reboot Reason In Detail Recently ###&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Reboot Time &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;UP Time Total Boot Reason&lt;BR /&gt;&amp;nbsp;Wed Aug 16 00:08:10 2017 &amp;nbsp; &amp;nbsp; 0 day 00:01:18 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 89 Monitor: APMgr process not alive&lt;BR /&gt;&amp;nbsp;Wed Aug 16 00:08:10 2017 &amp;nbsp; &amp;nbsp; 0 day 00:01:18 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 90 Monitor: APMgr process not alive&lt;BR /&gt;&lt;BR /&gt;The AP does not want to join the ZD is in the same subnet.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;We would like to script this so that we have a rollback scenario if we migrate from vSCG to ZD.&lt;BR /&gt;&lt;BR /&gt;In the support file we found the following info how can we remove this ?&lt;BR /&gt;migrate_scg/discover_timeout='1200'&lt;BR /&gt;migrate_scg/scg_addr='x.x.x.x'&lt;BR /&gt;migrate_scg/zd_mac='9x_fx_6x_2x_fx_c0'</description>
    <pubDate>Wed, 16 Aug 2017 14:22:05 GMT</pubDate>
    <dc:creator>arthur_hulsman</dc:creator>
    <dc:date>2017-08-16T14:22:05Z</dc:date>
    <item>
      <title>Backwards migration - vSCG to ZD</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/10919#M133</link>
      <description>I've found dozens of posts and even PDFs detailing how to easily migrate APs from a ZD to vSCG, but what about migrating them back to the ZD? &amp;nbsp;For context, we had migrated the APs to vSCG as a temporary measure while the ZD was sent in for RMA, and now we need to move them back since the property does not pay for vSCG licenses.&lt;BR /&gt;&lt;BR /&gt;In the past, we've always had to remove the DHCP option, then SSH into each AP individually, factory default them, then restart and they would usually reach the ZD; for some reason, if we do not default them, they only sometimes (and rarely) reach the ZD for configuration. &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Is there a way to do this without having to SSH into hundreds of APs manually? &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;(Aps are ZF7352 &amp;amp; R500 mixed, the ZD is a ZD1100 with firmware&amp;nbsp;9.9.0.0 build 212)</description>
      <pubDate>Tue, 27 Jun 2017 22:20:11 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/10919#M133</guid>
      <dc:creator>daniel_beaver_6</dc:creator>
      <dc:date>2017-06-27T22:20:11Z</dc:date>
    </item>
    <item>
      <title>Re: Backwards migration - vSCG to ZD</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/10920#M134</link>
      <description>Hello Daniel,&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; This might not be so easy...&amp;nbsp; If the APs have been managed by SZ, they won't join a ZD&lt;BR /&gt;even if you set your DHCP to point them correctly (option 43 vs option 60) and factory&lt;BR /&gt;default them.&amp;nbsp; You'll need to access them and upload a Solo AP image (which joins SZ &lt;BR /&gt;or ZD), and point them.&amp;nbsp; &lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; You might want to use different controller IPs to help do this in batches, instead of trying&lt;BR /&gt;to use the same SZ/ZD IP addresses too.&amp;nbsp; Here are links to your AP solo images:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://support.ruckuswireless.com/software/1017-zoneflex-solo-access-point-104-0-0-0-1347-ga-software-release" rel="nofollow"&gt;https://support.ruckuswireless.com/software/1017-zoneflex-solo-access-point-104-0-0-0-1347-ga-softwa...&lt;/A&gt;</description>
      <pubDate>Thu, 29 Jun 2017 21:28:50 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/10920#M134</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2017-06-29T21:28:50Z</dc:date>
    </item>
    <item>
      <title>Re: Backwards migration - vSCG to ZD</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/10921#M135</link>
      <description>@michael Brado&amp;nbsp;&lt;BR /&gt;we execute an migration fro vSCG to ZD firmware with the folllowing commands&lt;BR /&gt;fw set host xx.xx.xx.xx&lt;BR /&gt;fw set proto ftp&lt;BR /&gt;fw set user ftpuser&lt;BR /&gt;fw set password xxxxxx&lt;BR /&gt;fw set control r700/9.13.3.0.41/r700_9133_cntrl.rcks&lt;BR /&gt;fw update&amp;nbsp;&lt;BR /&gt;reboot&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;After the firmware flash we are able to logon but the AP reboots after 30 seconds&lt;BR /&gt;set scg disable&lt;BR /&gt;set csg ip del&lt;BR /&gt;set director ip xx.xx.xx.xx&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;AP is in Stand-alone mode.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;### Reboot Reason In Detail Recently ###&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Reboot Time &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;UP Time Total Boot Reason&lt;BR /&gt;&amp;nbsp;Wed Aug 16 00:08:10 2017 &amp;nbsp; &amp;nbsp; 0 day 00:01:18 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 89 Monitor: APMgr process not alive&lt;BR /&gt;&amp;nbsp;Wed Aug 16 00:08:10 2017 &amp;nbsp; &amp;nbsp; 0 day 00:01:18 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 90 Monitor: APMgr process not alive&lt;BR /&gt;&lt;BR /&gt;The AP does not want to join the ZD is in the same subnet.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;We would like to script this so that we have a rollback scenario if we migrate from vSCG to ZD.&lt;BR /&gt;&lt;BR /&gt;In the support file we found the following info how can we remove this ?&lt;BR /&gt;migrate_scg/discover_timeout='1200'&lt;BR /&gt;migrate_scg/scg_addr='x.x.x.x'&lt;BR /&gt;migrate_scg/zd_mac='9x_fx_6x_2x_fx_c0'</description>
      <pubDate>Wed, 16 Aug 2017 14:22:05 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/10921#M135</guid>
      <dc:creator>arthur_hulsman</dc:creator>
      <dc:date>2017-08-16T14:22:05Z</dc:date>
    </item>
    <item>
      <title>Re: Backwards migration - vSCG to ZD</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/10922#M136</link>
      <description>Hmm, we do not officially support an AP that was ZD or SZ managed, and then factory defaulted for "standalone mode",&lt;BR /&gt;customers should load the Solo AP images.&lt;BR /&gt;&lt;BR /&gt;A SmartZone controller can convert ZD managed APs, due to an 'lwapp2scg' utility, but a ZD cannot recognize/convert&lt;BR /&gt;a previously SCG managed AP, unless it goes thru the Solo image.&lt;BR /&gt;&lt;BR /&gt;That's creative the way you script the ZD connection info.&amp;nbsp; Perhaps if you re-flashed the SZ managed APs with a Solo&lt;BR /&gt;image, they would join your local ZD.&amp;nbsp; Here is a link to 104.0.0.0.1347 with both 7352 and R500 firmware.&lt;BR /&gt;&lt;A href="https://support.ruckuswireless.com/software/1017-zoneflex-solo-access-point-104-0-0-0-1347-ga-software-release" rel="nofollow" target="_blank" title="Link https//supportruckuswirelesscom/software/1017-zoneflex-solo-access-point-104-0-0-0-1347-ga-software-release"&gt;https://support.ruckuswireless.com/software/1017-zoneflex-solo-access-point-104-0-0-0-1347-ga-softwa...&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;You can direct APs to a ZD or SZ with DHCP option 43 too, using sub-option 03 for ZD or 06 for SZ controllers.&lt;BR /&gt;&lt;A href="https://support.ruckuswireless.com/answers/000002022" rel="nofollow"&gt;https://support.ruckuswireless.com/answers/000002022&lt;/A&gt;</description>
      <pubDate>Thu, 17 Aug 2017 22:33:19 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/10922#M136</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2017-08-17T22:33:19Z</dc:date>
    </item>
    <item>
      <title>Re: Backwards migration - vSCG to ZD</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/10923#M137</link>
      <description>@&amp;nbsp;&lt;A href="https://forums.ruckuswireless.com/ruckuswireless/people/michael_brado" rel="nofollow" target="_blank" title="Link https//forumsruckuswirelesscom/ruckuswireless/people/michael_brado"&gt;Michael Brado&lt;/A&gt;&amp;nbsp;thank you for the quick answer.&amp;nbsp;&lt;BR /&gt;We did some extra tests.&lt;BR /&gt;On our subnet we do not have DHCP options enabled, when we execute "set factory" after we downgrade to the ZD version (see my previous post), the AP will automatically join the ZD with L2 llwap discovery.</description>
      <pubDate>Mon, 21 Aug 2017 12:50:25 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/10923#M137</guid>
      <dc:creator>arthur_hulsman</dc:creator>
      <dc:date>2017-08-21T12:50:25Z</dc:date>
    </item>
    <item>
      <title>Re: Backwards migration - vSCG to ZD</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/10924#M138</link>
      <description>I can confirm to the post of Arthur, it really works thisway, to back-migrate from vSN-e back to ZD1200. &lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;for r500 this is the setting&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;&amp;nbsp; fw set control r500/10.1.1.0.42/r500_1011_cntrl.rcks&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;
&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;and for r510 this is my setting&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;&amp;nbsp; fw set control r510/10.1.1.0.42/r510_1011_cntrl.rcks&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;and please use the correct password &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; You can find out the actual pwd, when you connect a new AP-R510 to the ZD1200 and let the ZD1200 config the R510. Then by CLI make &lt;FW show=""&gt; and you will see the aktual ftp-Password. &lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I believe on new firmware it is now encrypted &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;/FW&gt;</description>
      <pubDate>Sat, 24 Nov 2018 09:34:54 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/10924#M138</guid>
      <dc:creator>christian_rotte</dc:creator>
      <dc:date>2018-11-24T09:34:54Z</dc:date>
    </item>
    <item>
      <title>Re: Backwards migration - vSCG to ZD</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/44270#M921</link>
      <description>&lt;P&gt;You can specify the you! thank you&lt;/P&gt;</description>
      <pubDate>Mon, 07 Mar 2022 14:58:56 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Cloud/Backwards-migration-vSCG-to-ZD/m-p/44270#M921</guid>
      <dc:creator>wzheilong</dc:creator>
      <dc:date>2022-03-07T14:58:56Z</dc:date>
    </item>
  </channel>
</rss>

