So if the XML has duplicate records after you re-rename the client then you will be able to see what's different that triggered the loss. If the client is still in the XML only once and the MAC and original name haven't changed then it looks like a bug & you should report in the Ruckus forum with the version so they can hopefully bugfix.
Ruckus Wireless as an Unifi alternative?
- Thread starter pcmoore
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
There is only a single record even after re-renaming, example entry being:
<sta mac="04:17:b6:29:61:db" id="34" name="04:17:b6:29:61:db" rename="Eufy Camera Entryway" time="1721544358" />
By Ruckus forum, would it be a forum off their website? They might not be interesting in fixing anything in 200.7.x but it is worth a shot, I suppose
<sta mac="04:17:b6:29:61:db" id="34" name="04:17:b6:29:61:db" rename="Eufy Camera Entryway" time="1721544358" />
By Ruckus forum, would it be a forum off their website? They might not be interesting in fixing anything in 200.7.x but it is worth a shot, I suppose
If you have only WiFi 6 APs then Unleashed 200.16 is out.
support.ruckuswireless.com
Sonos specific settings sounds promising.
ICX 8200 pricing is ridiculous, so someone else will have to try AV profile and comment.
Ruckus Wireless Support
support.ruckuswireless.com
Sonos specific settings sounds promising.
ICX 8200 pricing is ridiculous, so someone else will have to try AV profile and comment.
No. Unleashed 200.16 drops support for all Wifi5 APs (like R710, R720, etc). Only Wifi6 APs (R750, R650, etc..) are supported in 200.16
A couple of things I've noticed:
Nicer UI for channel selection:
More settings for ChannelFly:
More settings for band steering:
Nicer UI for channel selection:
More settings for ChannelFly:
More settings for band steering:
So lots of nice stuff from SmartZone. Excellent.
Ah I misinterpreted "out." I thought it was "out of scope" instead of "out for download."
Updated to 200.16.7.0.325 without any issues. Not much other than some UI changes are apparent to me. I've been having some issues with my R850's only getting 1/2 the download speed as upload speed. One day I'm going to have to figure that out.
Hi...another access point serial recovery question for the experts. 
I have a R650 that has the infamous solid red power LED of doom. Connecting via serial, it shows it's in a boot loop and does not successfully load an image. A factory reset via reset button fails as well. I can get into u-boot and appear to transfer over firmware without error, but it will not boot from any that I've tried (both Solo and Unleashed).
The u-boot options are pretty limited and I'm not sure what my next steps may be. Once I copy over a .bl7 file, is there a process I may try other than what I already have?
I've tried booting to the various transferred files after setting the environment options (IP/Gateway/Subnet/ServerIP/Control file name):
Boot log is attached for review, in case that helps. I looked through it and don't know enough about it to know what errors/failures are important versus background noise.
Thanks!
I have a R650 that has the infamous solid red power LED of doom. Connecting via serial, it shows it's in a boot loop and does not successfully load an image. A factory reset via reset button fails as well. I can get into u-boot and appear to transfer over firmware without error, but it will not boot from any that I've tried (both Solo and Unleashed).
The u-boot options are pretty limited and I'm not sure what my next steps may be. Once I copy over a .bl7 file, is there a process I may try other than what I already have?
I've tried booting to the various transferred files after setting the environment options (IP/Gateway/Subnet/ServerIP/Control file name):
- Both BootID options (1 and 2)...both fail.
- Booting from the backup image (same as #2 above I'm guessing?)
- TFTPBOOT <.bl7 filename>
- BOOTM <.bl7 filename>
- DHCP
- GO 0x40000a0 (and 0x4000f0)
Boot log is attached for review, in case that helps. I looked through it and don't know enough about it to know what errors/failures are important versus background noise.
Thanks!
Code:
[ 1.623363] qca-mdio 90000.mdio: Could not find phy-reset-gpio
...
[ 1.657728] msm-qusb-phy 59000.qusb: QUSB PHY PLL LOCK fails:10I see this a bit further down:
Code:
[ 1.668026] WARNING: CPU: 3 PID: 1 at /home/jenkins/workspace/AP-SCG_5.2.2_MR_P2_R730/linux/kernels/linux-4.4.60/drivers/usb/phy/phy-msm-qusb.c:505 qusb_phy_init+0x784/0x84c()Ruckus uses the same firmware for multiple AP models of they share the same chipset, and the firmware gets labeled with whatever AP was first for that chipset. R730 is what you expect to see in boot logs for an R650.
It looks like a hardware problem - config problems usually get further along the boot process than that.
If this was bought recently then I'd be contacting the seller to report it DOA & requesting a refund.
Dang...it was a side project to try and get it running, but can't be returned (bought cheap AS-IS hoping it might just work).
Do you happen to know the proper commands for copying an image file once that image is TFTP'd over? I'm familiar with the ICX switch configs and primary/secondary boot configs, etc but I don't see how to load the images into either of the BOOTID 1/2 locations (unless I'm misunderstanding the use of those).
Thanks again!