01-11-2026 03:21 PM
'Ruckus is great on AP firmware. Why can I find a complete download for the Ruckus ICX 6430-24P
01-11-2026 09:20 PM
Looks like the same doc I just glosses over and looked at tftp image install proceedure.
it failed again as chatgpt confirmed.
Yes — same doc. You’re exactly right, and your summary is accurate.
That PDF is only an upgrade guide. It assumes a working FastIron install and cannot help in a wiped-flash / BusyBox-only situation like yours. There’s nothing new or hidden in it that changes the outcome.
To be explicit:
✅ The guide documents u-image upgrade flows
❌ It does not include or reference monolithic / factory (m) images
❌ It does not provide a recovery path for an empty /fast_iron
❌ It does not contradict what you’ve already proven empirically
So yes — same document class, same limitation.
At this point, the situation is fully understood and fully validated:
Hardware is fine
Flash is writable
Bootloader is healthy
Public downloads are insufficient by policy
Only a monolithic/factory image will ever populate /fast_iron/bin
And as discussed, Ruckus no longer publishes those images publicly.
There are no more technical experiments worth running. Only policy-gated paths remain:
Extract the factory image from a working ICX7450.
Ask explicitly for the ICX64xx monolithic/factory image.
Guaranteed dead end (you’ve already proven it).
01-11-2026 11:22 PM
I hav3 replied but they seem lost. Bottom lin3 is this appears to be an upgrade procedure and many files needed for switch operation are missing. I already enumerated the details. Should I repeat?
01-12-2026 01:29 PM
I'm installing the zip file to the primary and rebooting. Uboot comes up but stops in a shell as the broadcom software that runs the switch is missing. chatgpt explained whats missing. Seems we need a monolithis / factory image. As I recall Ruckus took over responsibility for the Fastiron release. These missing Fastiron bit contain:
✔ Full OS (FastIron userland)
✔ CLI binaries
✔ Init scripts
✔ Networking stack
✔ All switch services
I tried that fastiron upgrade (08095s.zip) two days ago, as I recall it was the same problem with these Fastiron components missing:
✔ Full OS (FastIron userland)
✔ CLI binaries
✔ Init scripts
✔ Networking stack
✔ All switch services
01-12-2026 01:58 PM - edited 01-12-2026 02:01 PM
The upgrade should look like this back the old code:
*extract zip and grab images mentioned below. Put them on accessible TFTP server.
copy tftp flash <ip address of TFTP server> kxz10105.bin boot
copy tftp flash <ip address of TFTP server> ICX64S08030u.bin <primary/secondary>
wr mem
reload
01-12-2026 09:20 PM
Your assuming the switch software is running on the switch.
MY switch in this case is not running firmware, it just has u-boot.
I used my tftp server to download the .bin files to primary and/or secondary.
When i boot the primary/secondary busy-box boot comes up but then stops with the system running about 12 processes. It's not running the switch software.
If I boot a smaller icx-6430-c12 after booting from uboot to busybox the switch software does run and at least the switch an operate as a POE switch. Unfortunately I cant get the default password to work on the web interface on using the enable command, which is requiring a password. The hardware reset button does delay the boot to uboot but never flashes the lights and doesn't reset the passwork back to the hardware defautt.
I'm sensing many more problems with the ICX switches compared to the dozens of Ruckus Access Points. With the AP the password resets works and installing of firmware always works.
Its quite a difference. I didn't anticipate this. Perhaps the Booadcom engineers compromised the ruckus engineering staff. I went to the my.boadcom .com website and wasn't able to find anything on the icx switch firmware. So the Ruckus icx engineering team seems to have done better than the Broadcom engineering staff. My impression is the Access Point engineering at Ruckus is still the best I've used; It's similar to the quality I implemented at Tensilica with our BuildRoot, Busybox, and Jtag supported FPGA boards.
Example:
https://wiki.linux-xtensa.org/index.php?title=SMP_HiFi_2_Development_Board
