<?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: Firmware 3.2 in SmartZone and Virtual SmartZone</title>
    <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7606#M306</link>
    <description>&lt;P&gt;There is a new port that needs to be opened for this to work.&amp;nbsp; You likely have port 91, 22 and 443, please add port 11443 for the transfer to take place.&amp;nbsp; This is new in firmware 3.2 and is used for firmware upgrade using HTTPS instead of FTP.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Let me know if this helps.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Tue, 10 Nov 2015 17:19:13 GMT</pubDate>
    <dc:creator>dionis_taveras</dc:creator>
    <dc:date>2015-11-10T17:19:13Z</dc:date>
    <item>
      <title>Firmware 3.2</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7603#M303</link>
      <description>Hi !&lt;BR /&gt;&lt;BR /&gt;I have some problems with my vsz after upgrading to 3.2.&lt;BR /&gt;&lt;BR /&gt;Now when I try to upgrade firmware on the accesspoints it fail ́s in the download process.&lt;BR /&gt;&lt;BR /&gt;The accesspoints are R300 and R500.&lt;BR /&gt;&lt;BR /&gt;The logs from the AP ́s looks like this.&lt;BR /&gt;Nov 10 10:09:03 RuckusAP daemon.notice Firmware Daemon[612]: failed|control file download problemNov 10 10:09:04 RuckusAP daemon.notice Firmware Daemon[612]: working|looking up control server IP&lt;BR /&gt;Nov 10 10:09:04 RuckusAP daemon.notice Firmware Daemon[612]: working|reading control file&lt;BR /&gt;Nov 10 10:09:25 RuckusAP daemon.notice Firmware Daemon[612]: failed|control file download problem&lt;BR /&gt;Nov 10 10:09:26 RuckusAP daemon.notice Firmware Daemon[612]: working|looking up control server IP&lt;BR /&gt;Nov 10 10:09:26 RuckusAP daemon.notice Firmware Daemon[612]: working|reading control file&lt;BR /&gt;Nov 10 10:09:47 RuckusAP daemon.notice Firmware Daemon[612]: failed|control file download problem&lt;BR /&gt;Nov 10 10:09:48 RuckusAP daemon.notice Firmware Daemon[612]: working|looking up control server IP&lt;BR /&gt;Nov 10 10:09:48 RuckusAP daemon.notice Firmware Daemon[612]: working|reading control file&lt;BR /&gt;&lt;BR /&gt;I have tested both internal and external.&lt;BR /&gt;&lt;BR /&gt;Any idea whats wrong?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks in advance!</description>
      <pubDate>Tue, 10 Nov 2015 13:21:21 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7603#M303</guid>
      <dc:creator>henrik_lodel</dc:creator>
      <dc:date>2015-11-10T13:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware 3.2</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7604#M304</link>
      <description>Had a similar problem here when we upgraded from 3.0 to 3.1 and found a workaround by moving the APs into the staging zone and then back to their correct zone. Try it and see does it help.</description>
      <pubDate>Tue, 10 Nov 2015 13:27:00 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7604#M304</guid>
      <dc:creator>paddy_naughton_</dc:creator>
      <dc:date>2015-11-10T13:27:00Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware 3.2</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7605#M305</link>
      <description>Thanks for the tip but unfortunately that did not help &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt; Still "Firmware Upgrade Failed".</description>
      <pubDate>Tue, 10 Nov 2015 13:32:29 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7605#M305</guid>
      <dc:creator>henrik_lodel</dc:creator>
      <dc:date>2015-11-10T13:32:29Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware 3.2</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7606#M306</link>
      <description>&lt;P&gt;There is a new port that needs to be opened for this to work.&amp;nbsp; You likely have port 91, 22 and 443, please add port 11443 for the transfer to take place.&amp;nbsp; This is new in firmware 3.2 and is used for firmware upgrade using HTTPS instead of FTP.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Let me know if this helps.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Tue, 10 Nov 2015 17:19:13 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7606#M306</guid>
      <dc:creator>dionis_taveras</dc:creator>
      <dc:date>2015-11-10T17:19:13Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware 3.2</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7607#M307</link>
      <description>Yes, and it looks like I need to write the KBA asap.</description>
      <pubDate>Tue, 10 Nov 2015 18:55:54 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7607#M307</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2015-11-10T18:55:54Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware 3.2</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7608#M308</link>
      <description>NOTE: Starting in this release, AP firmware upgrade is performed using HTTPS port 11443 (earlier releases use HTTP port 91). &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
To ensure that all APs can be upgraded successfully to the new firmware, open both ports 11443 and 91 in the network firewall.&lt;BR /&gt;&lt;BR /&gt;
KBA-5299: What changes could affect my APs upgrading to SmartZone 3.2 Release?&lt;BR /&gt;&lt;BR /&gt;
&lt;A href="https://support.ruckuswireless.com/answers/000005299" rel="nofollow" target="_blank" title="Link https//supportruckuswirelesscom/answers/000005299"&gt;https://support.ruckuswireless.com/answers/000005299&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
Updated SZ 3.2 GA Release Notes have been posted online:&lt;BR /&gt;&lt;BR /&gt;
&lt;A href="https://ruckus-support.s3.amazonaws.com/private/documents/863/sz-3-2-release-notes-20151109.pdf?AWSAccessKeyId=AKIAJM3QLNNKLOV235TQ&amp;amp;Expires=1447099216&amp;amp;Signature=vSF1mK0ioIWV02lpb1ytpFwkiEk%3D" rel="nofollow" target="_blank" title="Link https//ruckus-supports3amazonawscom/private/documents/863/sz-3-2-release-notes-20151109pdfAWSAccessKeyIdAKIAJM3QLNNKLOV235TQExpires1447099216SignaturevSF1mK0ioIWV02lpb1ytpFwkiEk3D"&gt;&lt;/A&gt;&lt;A href="https://support.ruckuswireless.com/documents/863-smartzone-3-2-ga-release-notes" target="test_blank"&gt;https://support.ruckuswireless.com/documents/863-smartzone-3-2-ga-release-notes&lt;/A&gt; &lt;BR /&gt;</description>
      <pubDate>Tue, 10 Nov 2015 19:00:16 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7608#M308</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2015-11-10T19:00:16Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware 3.2</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7609#M309</link>
      <description>Thanks alot guys ! This solved my problem !</description>
      <pubDate>Tue, 10 Nov 2015 19:58:01 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Firmware-3-2/m-p/7609#M309</guid>
      <dc:creator>henrik_lodel</dc:creator>
      <dc:date>2015-11-10T19:58:01Z</dc:date>
    </item>
  </channel>
</rss>

