<?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: 9.13 MR2: R710 fails to upgrade in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6736#M1331</link>
    <description>Please open a ticket with Support asap!&amp;nbsp; Thanks John.</description>
    <pubDate>Thu, 10 Nov 2016 22:27:57 GMT</pubDate>
    <dc:creator>michael_brado</dc:creator>
    <dc:date>2016-11-10T22:27:57Z</dc:date>
    <item>
      <title>9.13 MR2: R710 fails to upgrade</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6734#M1329</link>
      <description>It looks like there's a serious problem with the 9.13.2 update just posted. I upgraded my ZD1200 to this firmware and unfortunately after the upgrade, both of my R710's failed to upgrade to the new firmware:
&lt;BR /&gt;&lt;BR /&gt;
  2 23:26:46 R710 local2.err syslog: Firmware update error(-29)  
&lt;BR /&gt;
Jan  2 23:26:48 R710 kern.warn kernel: [  147.710684] : vid[1:0]=1,0
&lt;BR /&gt;
Jan  2 23:26:48 R710 kern.warn kernel: [  147.710684] : vid[1:0]=1,0
&lt;BR /&gt;
Jan  2 23:26:51 R710 daemon.notice Firmware Daemon[2890]: working|looking up control server IP
&lt;BR /&gt;
Jan  2 23:26:51 R710 daemon.notice Firmware Daemon[2890]: working|reading control file
&lt;BR /&gt;
Jan  2 23:26:51 R710 daemon.notice Firmware Daemon[2890]: working|reading firmware file header
&lt;BR /&gt;
Jan  2 23:26:51 R710 kern.warn kernel: [  150.222774] : vid[1:0]=1,0
&lt;BR /&gt;
Jan  2 23:26:51 R710 kern.warn kernel: [  150.222774] : vid[1:0]=1,0
&lt;BR /&gt;
Jan  2 23:27:01 R710 daemon.notice Firmware Daemon[2890]: failed|AP Image Signing : Firmware public key verification failed.
&lt;BR /&gt;
Jan  2 23:27:01 R710 local2.err syslog: Firmware update error(-29)  
&lt;BR /&gt;
Jan  2 23:27:06 R710 daemon.notice Firmware Daemon[3029]: working|looking up control server IP
&lt;BR /&gt;
Jan  2 23:27:06 R710 daemon.notice Firmware Daemon[3029]: working|reading control file
&lt;BR /&gt;
Jan  2 23:27:06 R710 daemon.notice Firmware Daemon[3029]: working|reading firmware file header
&lt;BR /&gt;
Jan  2 23:27:16 R710 daemon.notice Firmware Daemon[3029]: failed|AP Image Signing : Firmware public key verification failed.
&lt;BR /&gt;
Jan  2 23:27:16 R710 local2.err syslog: Firmware update error(-29)  
&lt;BR /&gt;
Jan  2 23:27:21 R710 daemon.notice Firmware Daemon[3192]: working|looking up control server IP
&lt;BR /&gt;
Jan  2 23:27:21 R710 daemon.notice Firmware Daemon[3192]: working|reading control file
&lt;BR /&gt;
Jan  2 23:27:21 R710 daemon.notice Firmware Daemon[3192]: working|reading firmware file header
&lt;BR /&gt;
Jan  2 23:27:30 R710 authpriv.info dropbear[2116]: Exit before auth: Exited normally
&lt;BR /&gt;
Jan  2 23:27:31 R710 daemon.notice Firmware Daemon[3192]: failed|AP Image Signing : Firmware public key verification failed.
&lt;BR /&gt;
Jan  2 23:27:31 R710 local2.err syslog: Firmware update error(-29)  
&lt;BR /&gt;
Jan  2 23:27:33 R710 kern.warn kernel: [  192.711871] : vid[1:0]=1,0
&lt;BR /&gt;
Jan  2 23:27:33 R710 kern.warn kernel: [  192.711871] : vid[1:0]=1,0
&lt;BR /&gt;
Jan  2 23:27:33 R710 authpriv.info dropbear[3306]: Child connection from 10.0.200.240:50893
&lt;BR /&gt;
Jan  2 23:27:34 R710 authpriv.notice dropbear[3306]: Deferring to RKS shell to authenticate password.
&lt;BR /&gt;
Jan  2 23:27:34 R710 authpriv.err dropbear[3306]: chown(/dev/ttyp0, 0, 5) failed: Read-only file system
&lt;BR /&gt;
Jan  2 23:27:34 R710 authpriv.err dropbear[3306]: chmod(/dev/ttyp0, 0620) failed: Read-only file system
&lt;BR /&gt;
Jan  2 23:27:36 R710 daemon.notice Firmware Daemon[3324]: working|looking up control server IP
&lt;BR /&gt;
Jan  2 23:27:36 R710 daemon.notice Firmware Daemon[3324]: working|reading control file
&lt;BR /&gt;
Jan  2 23:27:36 R710 daemon.notice Firmware Daemon[3324]: working|reading firmware file header
&lt;BR /&gt;
Jan  2 23:27:36 R710 kern.warn kernel: [  195.648359] : vid[1:0]=1,0
&lt;BR /&gt;
Jan  2 23:27:36 R710 kern.warn kernel: [  195.648391] : vid[1:0]=1,0
&lt;BR /&gt;
Jan  2 23:27:46 R710 daemon.notice Firmware Daemon[3324]: failed|AP Image Signing : Firmware public key verification failed.
&lt;BR /&gt;
Jan  2 23:27:46 R710 local2.err syslog: Firmware update error(-29)  
&lt;BR /&gt;
Jan  2 23:27:51 R710 daemon.notice Firmware Daemon[3465]: working|looking up control server IP
&lt;BR /&gt;
Jan  2 23:27:51 R710 daemon</description>
      <pubDate>Thu, 10 Nov 2016 22:07:06 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6734#M1329</guid>
      <dc:creator>john_d</dc:creator>
      <dc:date>2016-11-10T22:07:06Z</dc:date>
    </item>
    <item>
      <title>Re: 9.13 MR2: R710 fails to upgrade</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6735#M1330</link>
      <description>I was able to downgrade back to 9.13.1 MR1 Refresh and bring my network back online.</description>
      <pubDate>Thu, 10 Nov 2016 22:09:55 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6735#M1330</guid>
      <dc:creator>john_d</dc:creator>
      <dc:date>2016-11-10T22:09:55Z</dc:date>
    </item>
    <item>
      <title>Re: 9.13 MR2: R710 fails to upgrade</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6736#M1331</link>
      <description>Please open a ticket with Support asap!&amp;nbsp; Thanks John.</description>
      <pubDate>Thu, 10 Nov 2016 22:27:57 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6736#M1331</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2016-11-10T22:27:57Z</dc:date>
    </item>
    <item>
      <title>Re: 9.13 MR2: R710 fails to upgrade</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6737#M1332</link>
      <description>Will do! Opened case&amp;nbsp;00501296</description>
      <pubDate>Thu, 10 Nov 2016 22:33:37 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6737#M1332</guid>
      <dc:creator>john_d</dc:creator>
      <dc:date>2016-11-10T22:33:37Z</dc:date>
    </item>
    <item>
      <title>Re: 9.13 MR2: R710 fails to upgrade</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6738#M1333</link>
      <description>Hi John,&lt;BR /&gt;&lt;BR /&gt;
&amp;nbsp;&amp;nbsp; I've given DevEng a heads-up, and a TAC engineer will contact you shortly.&lt;BR /&gt;&lt;BR /&gt;
Can we have a ZD debug log, and that APs support info file?&amp;nbsp; Thanks.</description>
      <pubDate>Thu, 10 Nov 2016 23:11:26 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6738#M1333</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2016-11-10T23:11:26Z</dc:date>
    </item>
    <item>
      <title>Re: 9.13 MR2: R710 fails to upgrade</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6739#M1334</link>
      <description>Yep I'll attach both soon. I am on 9.13.1 MR1 Refresh again, so hopefully the logs still contain something useful. At the moment unfortunately I can't risk further downtime until early next week.</description>
      <pubDate>Thu, 10 Nov 2016 23:15:45 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6739#M1334</guid>
      <dc:creator>john_d</dc:creator>
      <dc:date>2016-11-10T23:15:45Z</dc:date>
    </item>
    <item>
      <title>Re: 9.13 MR2: R710 fails to upgrade</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6740#M1335</link>
      <description>Hi John&lt;BR /&gt;&lt;BR /&gt;Did this go anywhere or get resolved? There are a couple of things in this release that would be quite useful, but I've got some R710's and really don't want to risk it failing and having to downgrade.&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Tue, 15 Nov 2016 21:32:50 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6740#M1335</guid>
      <dc:creator>dave_watkins_74</dc:creator>
      <dc:date>2016-11-15T21:32:50Z</dc:date>
    </item>
    <item>
      <title>Re: 9.13 MR2: R710 fails to upgrade</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6741#M1336</link>
      <description>My case is still open. We exchanged some more logs on Friday when I was able to reproduce the issue again. &lt;BR /&gt;&lt;BR /&gt;
I suspect it's something related to either my AP's or my configuration but I'm waiting to hear back.</description>
      <pubDate>Tue, 15 Nov 2016 21:34:31 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6741#M1336</guid>
      <dc:creator>john_d</dc:creator>
      <dc:date>2016-11-15T21:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: 9.13 MR2: R710 fails to upgrade</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6742#M1337</link>
      <description>Thanks, I'll hold off then, I've got a couple of 710s forming a mesh link, with R600's on the other side of that link&amp;nbsp;</description>
      <pubDate>Tue, 15 Nov 2016 21:36:16 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6742#M1337</guid>
      <dc:creator>dave_watkins_74</dc:creator>
      <dc:date>2016-11-15T21:36:16Z</dc:date>
    </item>
    <item>
      <title>Re: 9.13 MR2: R710 fails to upgrade</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6743#M1338</link>
      <description>I have 5 R700s that are failing to allocate DHCP addresses post 9.13.2 upgrade to ZD1200 although it shows that the APs are upgraded with the new cert.</description>
      <pubDate>Tue, 06 Dec 2016 16:43:08 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/9-13-MR2-R710-fails-to-upgrade/m-p/6743#M1338</guid>
      <dc:creator>jill_eldridge_e</dc:creator>
      <dc:date>2016-12-06T16:43:08Z</dc:date>
    </item>
  </channel>
</rss>

