<?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: AP 7372 WILL NOT JOIN ZD FIRMWARE UPGRADE LOOP in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/AP-7372-WILL-NOT-JOIN-ZD-FIRMWARE-UPGRADE-LOOP/m-p/10603#M2402</link>
    <description>Thank you for the reply.&lt;BR /&gt;As of this time, the APs have already been recognized by the ZD and have been updated as well.&lt;BR /&gt;1. I took route of a direct firmware upgrade to 104.0.0.0.1347 ;&lt;BR /&gt;2. Configured the static addresses the APs ( yes, I used static addressing for the APS and the ZD), and then after a reboot, the ZD recognized them and provisioned them with 10.1.0.0.1515&lt;BR /&gt;&lt;BR /&gt;Don't want to tinker with it for now &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;</description>
    <pubDate>Wed, 20 Jun 2018 09:48:28 GMT</pubDate>
    <dc:creator>kurt_cedric_sal</dc:creator>
    <dc:date>2018-06-20T09:48:28Z</dc:date>
    <item>
      <title>AP 7372 WILL NOT JOIN ZD FIRMWARE UPGRADE LOOP</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/AP-7372-WILL-NOT-JOIN-ZD-FIRMWARE-UPGRADE-LOOP/m-p/10600#M2399</link>
      <description>When joining two my 7372 (currently at&amp;nbsp;&amp;nbsp;9.7.1.0.17) AP to the ZoneDirector (10.1.0.0.1515)&amp;nbsp; I get the following:&lt;BR /&gt;( MAC ADDRESS INTENTIONALLY DELETED )&lt;BR /&gt;&lt;P&gt;2018/06/20&amp;nbsp; 12:12:55 Medium AP[38:ff:xx:xx:xx:xx] joins with different firmware/custom file version and is being upgraded.&lt;BR /&gt;2018/06/20&amp;nbsp; 12:10:28 Medium AP[38:ff:xx:xx:xx:xx] joins with different firmware/custom file version and is being upgraded.&lt;BR /&gt;2018/06/20&amp;nbsp; 12:07:46 Medium AP[38:ff:xx:xx:xx:xx] joins with different firmware/custom file version and is being upgraded.&lt;BR /&gt;2018/06/20&amp;nbsp; 12:05:14 Medium AP[38:ff:xx:xx:xx:xx] joins with different firmware/custom file version and is being upgraded.&lt;BR /&gt;2018/06/20&amp;nbsp; 12:02:44 Medium AP[38:ff:xx:xx:xx:xx] joins with different firmware/custom file version and is being upgraded.&lt;BR /&gt;2018/06/20&amp;nbsp; 12:00:12 Medium AP[38:ff:xx:xx:xx:xx] joins with different firmware/custom file version and is being upgraded.&lt;BR /&gt;2018/06/20&amp;nbsp; 11:57:40 Medium AP[38:ff:xx:xx:xx:xx] joins with different firmware/custom file version and is being upgraded.&lt;BR /&gt;2018/06/20&amp;nbsp; 11:54:53 Medium AP[38:ff:xx:xx:xx:xx] joins with different firmware/custom file version and is being upgraded.&lt;BR /&gt;2018/06/20&amp;nbsp; 11:52:26 Medium AP[38:ff:xx:xx:xx:xx] joins with different firmware/custom file version and is being upgraded.&lt;BR /&gt;2018/06/20&amp;nbsp; 11:49:55 Medium AP[38:ff:xx:xx:xx:xx] joins with different firmware/custom file version and is being upgraded.&lt;/P&gt;&lt;P&gt;&lt;B&gt;ACTIONS TAKEN&lt;/B&gt;&lt;BR /&gt;&lt;/P&gt;&lt;B&gt;&lt;U&gt;1. Tried several Firmware Versions of the AP (100.x.x.x down to 9.5 ) and the result is the same as above:&lt;BR /&gt;&lt;/U&gt;&lt;/B&gt;* currently AP is at 9.7.1.0.17&lt;BR /&gt;&lt;BR /&gt;&lt;U&gt;&lt;B&gt;2. Entered the CLI and tried to force update the AP with the following:&lt;BR /&gt;&lt;/B&gt;&lt;/U&gt;rkscli: fw force-update xxx.xx.xx.xx&lt;BR /&gt;fw: Updating rcks_wlan.main ...&lt;BR /&gt;**fw(7723) 172.16.17.18: CTL Get Error&lt;BR /&gt;OK&lt;P&gt;&lt;U&gt;&lt;B&gt;3. Enabled FTP on the Zonedirector to look for AP Specific Files:&lt;/B&gt;&lt;/U&gt;&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;




&lt;P&gt;&lt;B&gt;Index of /zf7372/10.1.0.0.1515/&lt;BR /&gt;&lt;/B&gt;&lt;A rel="nofollow" target="_blank" title="Link null"&gt;[parent directory]&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A rel="nofollow" target="_blank"&gt;rcks_fw.bl7&amp;nbsp;&lt;/A&gt;0 B&amp;nbsp;&lt;BR /&gt;&lt;A rel="nofollow" target="_blank"&gt;rcks_fw.bl7.bkup&amp;nbsp;&lt;/A&gt;0 B&lt;BR /&gt;&lt;A rel="nofollow" target="_blank"&gt;rcks_fw.bl7.bkup.version&amp;nbsp;&lt;/A&gt;14 B&lt;BR /&gt;&lt;A rel="nofollow" target="_blank"&gt;rcks_fw.bl7.main&amp;nbsp;&lt;/A&gt;0 B&lt;BR /&gt;&lt;A rel="nofollow" target="_blank"&gt;rcks_fw.bl7.option&amp;nbsp;&lt;/A&gt;28 B&lt;BR /&gt;&lt;A rel="nofollow" target="_blank"&gt;zf7372_1010_cntrl.rcks&amp;nbsp;&lt;/A&gt;140 B&lt;/P&gt;


&lt;P&gt;FILE SIZES SEEM TO BE TOO SMALL ( same sizes appear in all model-specific directories) ?&lt;/P&gt;&lt;P&gt;What is the next step now ?&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;



&lt;P&gt;N.B. I have two (2) other 7372s that have upgraded without a problem.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jun 2018 04:34:04 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/AP-7372-WILL-NOT-JOIN-ZD-FIRMWARE-UPGRADE-LOOP/m-p/10600#M2399</guid>
      <dc:creator>kurt_cedric_sal</dc:creator>
      <dc:date>2018-06-20T04:34:04Z</dc:date>
    </item>
    <item>
      <title>Re: AP 7372 WILL NOT JOIN ZD FIRMWARE UPGRADE LOOP</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/AP-7372-WILL-NOT-JOIN-ZD-FIRMWARE-UPGRADE-LOOP/m-p/10601#M2400</link>
      <description>As an update and after talking to Ruckus Support, the solution is to install firmware version&amp;nbsp;104.0.0.0.1347 on the APs before letting them join the Zone Director.&lt;BR /&gt;&lt;BR /&gt;Thanks to&amp;nbsp;Nayab Khan for the timely assist!</description>
      <pubDate>Wed, 20 Jun 2018 07:01:10 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/AP-7372-WILL-NOT-JOIN-ZD-FIRMWARE-UPGRADE-LOOP/m-p/10601#M2400</guid>
      <dc:creator>kurt_cedric_sal</dc:creator>
      <dc:date>2018-06-20T07:01:10Z</dc:date>
    </item>
    <item>
      <title>Re: AP 7372 WILL NOT JOIN ZD FIRMWARE UPGRADE LOOP</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/AP-7372-WILL-NOT-JOIN-ZD-FIRMWARE-UPGRADE-LOOP/m-p/10602#M2401</link>
      <description>Friend,
&lt;BR /&gt;
I suggest that you do the manual upgrade by following these steps:
&lt;BR /&gt;
1 - Upgrade to version100.1.x.194
&lt;BR /&gt;
2 - After the configuration, point the ap to the controller with the set director IP x.x.x.x
&lt;BR /&gt;
3 - Get the get version (see if the update worked)
&lt;BR /&gt;
3.1 - Get the get director (to see if the LWAPP connection between Ap x wlc is established
&lt;BR /&gt;
3.2 - Do the show fw all (to see if the two images have been updated) - If not, I suggest a new update - or a new note for wlc;
&lt;BR /&gt;
4 - If ap does not provision, repeat these steps with firmware 104.0.1397.
&lt;BR /&gt;&lt;BR /&gt;
Please post the result here.
&lt;BR /&gt;&lt;BR /&gt;
NOTE: You must enter the ruckus site, and verify that this version of the 10.1.15 x controller supports this AP model.</description>
      <pubDate>Wed, 20 Jun 2018 09:43:06 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/AP-7372-WILL-NOT-JOIN-ZD-FIRMWARE-UPGRADE-LOOP/m-p/10602#M2401</guid>
      <dc:creator>jardel_almeida</dc:creator>
      <dc:date>2018-06-20T09:43:06Z</dc:date>
    </item>
    <item>
      <title>Re: AP 7372 WILL NOT JOIN ZD FIRMWARE UPGRADE LOOP</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/AP-7372-WILL-NOT-JOIN-ZD-FIRMWARE-UPGRADE-LOOP/m-p/10603#M2402</link>
      <description>Thank you for the reply.&lt;BR /&gt;As of this time, the APs have already been recognized by the ZD and have been updated as well.&lt;BR /&gt;1. I took route of a direct firmware upgrade to 104.0.0.0.1347 ;&lt;BR /&gt;2. Configured the static addresses the APs ( yes, I used static addressing for the APS and the ZD), and then after a reboot, the ZD recognized them and provisioned them with 10.1.0.0.1515&lt;BR /&gt;&lt;BR /&gt;Don't want to tinker with it for now &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;</description>
      <pubDate>Wed, 20 Jun 2018 09:48:28 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/AP-7372-WILL-NOT-JOIN-ZD-FIRMWARE-UPGRADE-LOOP/m-p/10603#M2402</guid>
      <dc:creator>kurt_cedric_sal</dc:creator>
      <dc:date>2018-06-20T09:48:28Z</dc:date>
    </item>
    <item>
      <title>Re: AP 7372 WILL NOT JOIN ZD FIRMWARE UPGRADE LOOP</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/AP-7372-WILL-NOT-JOIN-ZD-FIRMWARE-UPGRADE-LOOP/m-p/10604#M2403</link>
      <description>That's what I was going to suggest...&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>Wed, 20 Jun 2018 16:21:26 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/AP-7372-WILL-NOT-JOIN-ZD-FIRMWARE-UPGRADE-LOOP/m-p/10604#M2403</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2018-06-20T16:21:26Z</dc:date>
    </item>
    <item>
      <title>Re: AP 7372 WILL NOT JOIN ZD FIRMWARE UPGRADE LOOP</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/AP-7372-WILL-NOT-JOIN-ZD-FIRMWARE-UPGRADE-LOOP/m-p/10605#M2404</link>
      <description>Are there instructions on how to manually upgrade the firmware?</description>
      <pubDate>Tue, 26 Jun 2018 13:45:18 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/AP-7372-WILL-NOT-JOIN-ZD-FIRMWARE-UPGRADE-LOOP/m-p/10605#M2404</guid>
      <dc:creator>jonathan_daigle</dc:creator>
      <dc:date>2018-06-26T13:45:18Z</dc:date>
    </item>
  </channel>
</rss>

