cancel
Showing results for 
Search instead for 
Did you mean: 

R650 bricked after upgrade

nls_pct
New Contributor II

Hello,

I had the stupid idea of doing a firmware upgrade on my R650 manually throught the R650 homepage as the autoupdate (through url http://fwupdate1.ruckuswireless.com/ ) was broken . Since then, it shows a simple " Building the Unleashed Network. It may take a few minutes. " when accessing the r650 homepage on my browser.

I took a firmware from the R650 firmware page and here is what shows the fw show all now :

rkscli: fw show all
<Control Info>
control file /writable/fw/main.cntl not in flash
-------------------------------------
current primary boot image is Image2
---------------<Image1 FW header>
Magic:        RCKS
next_image:   0x380000
invalid:      0
hdr_len:      160
compression:  l7
load_address: 0x42000000
entry_point:  0x42008000
timestamp:    Wed Dec 18 01:19:46 2019
binl7_len:    24026976
hdr_version:  4
hdr_cksum:    0xC704
version:      114.0.0.0.1294    ( 114.0.0.0.1294 )
MD5:          3EB8C61483DD5581B458E9E1278EA2D6
product:      r730      (0)
architecture: 0
chipset:      0
board_type:   0
board_class:  0
customer:
Image Sign Type: Fully Signed Image(FSI).
---------------<Image2 FW header>
Magic:        RCKS
next_image:   0x380000
invalid:      0
hdr_len:      160
compression:  l7
load_address: 0x42000000
entry_point:  0x42008000
timestamp:    Tue Aug 11 07:41:50 2020
binl7_len:    46153568
hdr_version:  4
hdr_cksum:    0x0E1B
version:      200.9.10.4.202    ( 200.9.10.4.202 )
MD5:          5C4195B9169D655D59C86C0F9084D9C2
product:      r730      (0)
architecture: 0
chipset:      0
board_type:   0
board_class:  0
customer:
Image Sign Type: Fully Signed Image(FSI).
OK

So I tried reupgrading the firmware through the CLI throught FTP and I keep having this error with any of the following firmware images I tried :


R650_114.0.0.0.1294.bl7
R650-200.9.10.4.233.bl7
R650-200.9.10.4.212.bl7
R650-200.9.10.4.202.bl7

rkscli: fw update
fw: Updating rcks_wlan.main ...
v54_fw_update: download 51.68.11.228 section=rcks_fw.main image=Image1 ctl_file=R650_114.0.0.0.1294.bl7 (/writable/fw/main.cntl)
Error: net_get_buf- FW_CTL_ERROR
Error: net_get_buf- FW_CTL_ERROR
**fw(13240) : CTL Get Error

rkscli: fw update
fw: Updating rcks_wlan.main ...
v54_fw_update: download 51.68.11.228 section=rcks_fw.main image=Image1 ctl_file=R650-200.9.10.4.233.bl7 (/writable/fw/main.cntl)
Error: net_get_buf- FW_CTL_ERROR
Error: net_get_buf- FW_CTL_ERROR
**fw(13833) : CTL Get Error

rkscli: fw update
fw: Updating rcks_wlan.main ...
v54_fw_update: download 51.68.11.228 section=rcks_fw.main image=Image1 ctl_file=R650-200.9.10.4.212.bl7 (/writable/fw/main.cntl)
Error: net_get_buf- FW_CTL_ERROR
Error: net_get_buf- FW_CTL_ERROR
**fw(15746) : CTL Get Error

fw: Updating rcks_wlan.main ...
v54_fw_update: download 51.68.11.228 section=rcks_fw.main image=Image1 ctl_file=R650-200.9.10.4.202.bl7 (/writable/fw/main.cntl)
Error: net_get_buf- FW_CTL_ERROR
Error: net_get_buf- FW_CTL_ERROR
**fw(16211) : CTL Get Error

Would you have any idea before I send my R650 back to RMA ?

Have a nice week,

Nicolas

1 ACCEPTED SOLUTION

eizens_putnins
Valued Contributor

It seems that you still try to upgrade from remote ftp. As you have issues, don't do it. I always never use it, actually. Just make local upgrade.

Start from resetting AP to factory through CLI or button (I would prefer CLI, as you can see if it is reset). You need DHCP server on network to provide AP with address after reset.

When reset, use default credentials and try upgrade it ( see https://support.ruckuswireless.com/articles/000001551 for details about ftp/tftp upgrade . For that you need to run tftp server on your PC, and put there both image and control file (put them into route directory!). Control file actually say to AP which file to download and what is expected file length.

It is just text file with content (make it in notepad):

[rcks_fw.main]
0.0.0.0
*filename of firmware*
*file size of firmware in bytes*

Name of control file can be any, for example cntl650.rcks. Put real image file name and it's size in the file (you need to find size in the image file properties -- size, not "size on disk"). Example of control file content:

[rcks_fw.main]
0.0.0.0

R650_110.0.0.0.675.Bl7
10717180

Commands to upgarde are:

fw set control <the control file name>
fw set proto tftp
fw set port 69
fw set host <IP of TFTP server>
fw upgrade

So, say your PC with TFTP server (TFTP32 for example) has IP 192.168.1.100, controle file name is cntl650.rcks than you can  use such CLI commands to make upgrade:

fw set control cntl650.rcks
fw set proto tftp
fw set port 69
fw set host 192.168.1.100
fw upgrade

If still is any problem, open case with Ruckus support (and probably provide them remote access to AP). Support will fix issue or RMA the device... Without additional support replacement is RTF, and takes 3-4 weeks normally, but as Ruckus APs fail very rarely, it is not a problem to get them replaced if it happens.

View solution in original post

10 REPLIES 10

eizens_putnins
Valued Contributor

Nice that issue is resolved. Good thing about indoor Ruckus APs is that they are very reliable, and even if you manage to get them physically faulty somehow, they have life-time warranty, so you can RMA them. Problems during upgrade are always possible, especially when loading image over Internet. So always better to keep image transfer local. But anything can happen. I had once power outrage in my office, exactly at the moment when we were updating firmware for 25 APs for customer installation. We got than to reimage manually 3 APs, which were got by power outage in the process of writing image, other recovered automatically. 

But Ruckus APs are very long lasting and reliable (actually thge supported wireless standard becomes too outdated before they stop to work. We have some customer still using ZF2942 -- 802.11g APs from 2006. Still work OK, just very outdated standard. 

Labels