bsp set model R850
, bsp set name R850
, bsp commit
).Technical.Support-xxxx
SSID.Admin & Services
> Administration
> Network Management
> Unleashed Multi-Site Manager
) with an unreachable IP, then immediately disabling it again. It has, so far, stayed gone.I got a R730 with poe port no ethernet signal, but still poe, sencond port is OKI received an R730 today (thanks @e97 !).
I set the model and name to R850 (by installing ZD 10.1.2.0.120 firmware and exiting to a root shell then runningbsp set model R850
,bsp set name R850
,bsp commit
).
I had no problem installing Unleashed (200.14.6.1.199), which has run flawlessly all day so far.
I bought the R730 to run as a dedicated master, but I'll leave it as my main AP for a few weeks to see if there are any issues/gotchas.
If you're wanting to do this, then there were a few tricky things...
- When I factory reset the ZD firmware after changing the model and name then the main PoE network port stopped working, so I had to connect to the 2nd port.
Then once Unleashed was running the 2nd ethernet port stopped working, so I had to connect back to the main port.
So I would definitely avoid factory reseting the ZD firmware if you're just using it to install Unleashed.- The AP won't show up in Unleashed until it picks up a DHCP lease or you manually set the IP.
So don't leave DHCP enabled if you want to setup Unleashed while the AP is directly connected to your PC.- After I'd setup Unleashed, I had an extra
Technical.Support-xxxx
SSID.
I killed this the usual way by enabling Unleashed Multi-Site Manager (Admin & Services
>Administration
>Network Management
>Unleashed Multi-Site Manager
) with an unreachable IP, then immediately disabling it again. It has, so far, stayed gone.
@asuz also ran into the problem with the AP rebooting back to the other xclaim partition. This is why my guide first installs solo firmware, then unleashed. The initial flash into solo, followed by the flash into Unleashed we actually wanted, is only in the guide to fix the reboot-to-xclaim issue.Hi,
my two cents to the awesome guide for reflashing the Xclaim-APs:
I think there might be an easier way to flash another FW to the ap (just in case it may help someone somewhere):
set rpmkey wsgclient/ignore-fw 1 # this will force the AP to accept any firmware as valid, this will also disable auto-FW-update when connected to a controller (vSZ and maybe ZoneDirector)
fw set host 1.1.1.1 #tftp server
fw set proto tftp
fw set control rcks_fw.bl7 # FW-binary at tftp server
fw up #start the upload process
Could the model be set with the rpmkey command as well?
When I tried to join the ap my to my test vSZ, I found that the AP rebooted and came back with the xclaim-FW but with the ruckus user/pw. Therefore I had to flash the AP again using the ruckus credentials for SSH access (super/sp-admin).
Is it possible that the join process somehow uses the other firmware on the AP to boot? What would happen if I flash the new firmware on both firmware partitions (mtd5 and mtd7)?
Furthermore I had to issue the following command on my vSZ to allow the xlcaim AP to join:
enable
config
no ap-cert-check
This is due an expired device certificate which prevents joining the AP to a vSZ. Maybe there is a similar behaviour with ZoneDirectors (I'm not sure if the ZoneDirector requires a device cert for inital connection as well), unleashed seems to be not affected.
RUCKUS Forums - New AP’s not joining the vSZ/SZ due to expired AP ... - CommScope RUCKUS Community Forums (ruckuswireless.com)
Years ago there was a semi-automated cert update process, when an outdated AP connected to a vSZ but this process seems to be gone.
APs have a key-value db on the writable filesystem, whichCould the model be set with the rpmkey command as well?
rpmkey
reads/writes. Configuration entries are copied here from the /defaults
folder during a factory reset.bsp
/rbd
settings, like model
/name
/antinfo
etc. are read from /proc/v54bsp/
, which has a /dev/mtd
flash partition as its backing store.rpmkey
isn't fussy, and the CLI will let you ruin this database if you're not careful, safe in the knowledge that a factory reset will fix it.rbd
/bsp
can brick your AP, so the CLI only lets a very few commands through and santizes their arguments.Unfortunately, you can't write to an in-use mtd partition. You can get around this in two ways:-What would happen if I flash the new firmware on both firmware partitions (mtd5 and mtd7)
Great result.I picked up a R730 after seeing this thread, and got it running the latest version unleashed without too many hassles. I didn't have any issues with ports going dead, the thing just flashed and booted right up over PoE. It was blasting out wifi happily on the unleashed firmware, and then I kicked it over to the dedicated master. Been up a day now, handled a power cycle and appears to be acting fine.
I think the 730 was the model that came out shortly before a new wifi standard was ratified and caused problems...R730 from ebay ($95 each seems like a steal for this?
R710 or R720 (I prefer R720) if Wifi6 is not a hard requirement.Thanks for the quick response. Is there another model that you think would be a better choice? still reading this thread as you responded.
This is great input. I currently have 5gb internet and was hoping to just "get faster" on wifi. I don't think I'll ever hit speeds that I'll notice a difference past ~500mb/s on wifi. I have few devices that actually support those speeds. This is for my residence, I was thinking I'd put one in my office, maybe one in the upstairs depending on penetration through walls, and one in my detached garage for my workshop and backyard. I am currently on Eero's that I bought used for $20 and they don't support VLANs. My current POE Switch only has gigabit ports (Brocade icx-6450), I was thinking that in a year or so I'd upgrade to different switch with multigig poe and it would be nice to already have the AP's in.I think it depends on your risk tolerance, and how many WAPs you intend to deploy. I'm quite fond of the R710, especially given its current used pricing being ~$65-75 USD shipped. It only does gigabit backhaul, but the dramatically increased power consumption and reduced sensitivity on the R720 and R730 don't offset the small bandwidth gains for me. Plus the operating temp range is wider, if you had any intent to deploy them into unconditioned spaces that are otherwise protected from the weather. I would lean towards deploying R710's today over a hacked R730, but if you're willing to fiddle, the R730's do appear to work. They consume something like ~3x the power of the R710. With a 2 stream client, I was getting around 650/900 on the hacked 730. I normally see around 500/700 on the 710s. For my clients, 400mbit is typically sufficient, and if it isn't, get R770s and go zoom.
That said, I have barely used mesh. Presumably a 6E unit with 3 radios would help a lot here? They're still quite pricy, however.
Definitely the R610/R710 is a much better choice for home.R730 has limited Wifi6 support and was removed from SmartZone recently. It does NOT support Unleashed (you can "crossflash" it to R850 and use it as Dedicated Unleashed Master without Wifi / Radio enabled)
For WiFi 5 definitively.Definitely the R610/R710 is a much better choice for home.