CommScope RUCKUS Community Forums

nls_pct · ‎04-11-2021

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

eizens_putnins · ‎04-13-2021

I don't work for Ruckus. But I am a Ruckus partner since 2006. I use Ruckus support regularly, and it is very helpful. You just need to know what to ask and form the very beginning provide support with all necessary information to help you efficiently. Ruckus has very good support engineers actually, and they are very helpful. Of cause, we have the support contract...

Also, when I see the messages similar to "Ruckus is frustrating and I am going for different brand", I always feel surprised why people want to change a very good product (in my opinion - best on market currently) to something not that good, hoping that it will work better for them. There are bugs and problems with any product, so service is provided to resolve them, and Ruckus support is definitely better than most leading vendors provide.

But to get real help from support (or forum) you need to be able to provide all necessary information, not just state "I have R710 AP ad it doesn't work, what should I do?".

When I create support case, I start for collecting all background information (controller serial, network structure, IPs, software versions, AP models and firmware versions, other relevant info) and error messages (screenshots) and / or logs, so when case is opened, I post all this info as attachment to case. This way I get useful reply in the very beginning, without wasting time to answer standard questions to establish the issue.

View solution in original post

syamantakomer · ‎04-19-2021

Glad to know.

eizens_putnins · ‎08-18-2021

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.

CommScope RUCKUS Community Forums

R650 bricked after upgrade