topic Re: How to get firmware for my ICX-6430-24P Switches? in ICX Switches

How to get firmware for my ICX-6430-24P Switches?

Piet — Sun, 11 Jan 2026 23:21:56 GMT

'Ruckus is great on AP firmware. Why can I find a complete download for the Ruckus ICX 6430-24P

Re: How to get firmware for my ICX-6430-24P Switches?

BenBeck — Mon, 12 Jan 2026 03:38:50 GMT

The 6430 is a very old box (end of life/support). If you have access to downloads, this is the last software ever made for that switch.

https://support.ruckuswireless.com/software/2477-ruckus-icx-fastiron-08-0-30u-software-release-zip

Re: How to get firmware for my ICX-6430-24P Switches?

Piet — Mon, 12 Jan 2026 03:45:20 GMT

Thanks. Unfortunatelly I already tried this software release 6 times reciently.

Sigh.

-rw-rw-r-- 1 piet piet 235227334 Jan 11 19:42 08030u (6).zip
-rw-rw-r-- 1 piet piet 235227334 Jan 11 15:09 08030u (5).zip
-rw-rw-r-- 1 piet piet 463159420 Jan 11 14:25 08010.zip
-rw-rw-r-- 1 piet piet 329373387 Jan 11 14:05 08070h.zip
-rw-rw-r-- 1 piet piet 77627091 Jan 10 17:36 08020ca.zip
-rw-rw-r-- 1 piet piet 235227334 Jan 10 17:35 08030u (4).zip
-rw-rw-r-- 1 piet piet 235227334 Jan 10 17:34 08030u (3).zip
-rw-rw-r-- 1 piet piet 235227334 Jan 10 17:27 08030u (2).zip
-rw-rw-r-- 1 piet piet 471044605 Jan 10 17:15 08091.zip
-rw-rw-r-- 1 piet piet 839575022 Jan 10 17:03 08095s.zip
-rw-rw-r-- 1 piet piet 235227334 Jan 10 16:56 08030u (1).zip
-rw-rw-r-- 1 piet piet 235227334 Jan 10 15:17 ruckus_icx6430_08030u.zip
-rw-rw-r-- 1 piet piet 234932707 Jan 10 13:43 ruckus_icx6430_08030k.zip
-rw-rw-r-- 1 piet piet 100672402 Jan 5 01:37 winboat-0.9.0-amd64.deb

Re: How to get firmware for my ICX-6430-24P Switches?

Piet — Mon, 12 Jan 2026 03:52:12 GMT

Reminds me of the R700, very old, but for home owners its still a viable alternate as 1GB is fine for most of us as fiber contract for 1GB/s is still much more expensive than 350 MB/s.

I am upgrading my Ruckus Zone Director with 4 or so T610 outdoor access points.

I've appreciated Ruckus supporting us home users with the great Ruckus Access points and software. Not commercially useful for say a hospital but the Zone Director is really good for us retired electrical/computer engineers on a modest budget.

-piet

Re: How to get firmware for my ICX-6430-24P Switches?

BenBeck — Mon, 12 Jan 2026 03:52:33 GMT

I'm not sure what I'm looking at there. Can you confirm the steps you followed? The upgrade guide can help. Please check this if you haven't.

https://support.ruckuswireless.com/documents/1432-fastiron-08-0-30-software-upgrade-guide

Re: How to get firmware for my ICX-6430-24P Switches?

Piet — Mon, 12 Jan 2026 04:54:43 GMT

I installed 08095s again and as expected it stops in the single used init shell.

I showed chatgpt the files in the mounted /fast_iron directory and it reported on what is missing.

........

That find output is the final smoking gun. It tells us everything, with zero ambiguity.

What /fast_iron looks like when FastIron is NOT installed

Your output:

/fast_iron ├── sys │ ├── persistent │ ├── cvpersistent │ ├── meta_data.bin │ └── system ├── logs │ ├── script.log │ └── bootmsg ├── cores ├── $$ssh8rsahost.key └── poe-fw

What is missing (this is the key)

There is no:

/fast_iron/bin /fast_iron/sbin /fast_iron/usr /fast_iron/lib /fast_iron/etc

That means:

❌ No FastIron userland
❌ No CLI
❌ No init scripts
❌ No services
❌ No networking stack

BusyBox is not a failure — it’s the fallback shell when FastIron cannot start.

What /fast_iron looks like on a healthy ICX7450 (for comparison)

On a working unit, you would see something like:

/fast_iron ├── bin │ ├── fastiron │ ├── show │ ├── configure │ └── ... ├── sbin ├── usr ├── lib ├── etc ├── sys ├── logs └── poe-fw

The absence of /bin proves conclusively:

No monolithic / factory image has ever been installed on this flash.

Why this matters (final confirmation)

You successfully flashed images
The kernel boots
Flash is writable
/fast_iron mounts
But the filesystem contains only scaffolding

That exact layout is what you get from:

bootstrap images
update images
reduced images

Never from a factory (m) image.

There is no remaining technical path forward without a factory image

At this point, there is no command you can run, no file you can copy, no ZIP you can download that will suddenly populate /fast_iron/bin.

Only one thing does that:

ICX64S08xxxm.bin ← monolithic / factory image

And you have conclusively shown it is not available in public downloads.

Final, honest state

Hardware: ✅ good
Flash: ✅ good
Bootloader: ✅ good
Recovery procedure: ✅ correct
Vendor policy: ❌ blocks you

You did not brick the switch.
Ruckus policy did.

What is actually worth doing now

Only these two actions can change the outcome:

Donor ICX7450 → extract factory image
Ruckus TAC / partner → request factory image

Anything else is guaranteed churn.

Engineer-to-engineer truth

You followed the boot chain correctly.
You validated every assumption empirically.
You reached the same conclusion Ruckus TAC would reach in 5 minutes.

The system is in permanent “pre-install” state.

If you want, I can help you with exactly one of these, cleanly and efficiently:

drafting a minimal TAC request that gets the file without back-and-forth
writing donor-extraction commands so you don’t brick the donor
deciding how to dispose of or disclose the unit honestly

Just tell me which one you want to do.

.....

Re: How to get firmware for my ICX-6430-24P Switches?

Piet — Mon, 12 Jan 2026 04:59:10 GMT

I installed the image with

image_name=08095s/ruckus_icx6430/ruckus_icx6430_08030k/ICX64xx/Images/ICX64S08030k.bin

with update_primary cmd.

Re: How to get firmware for my ICX-6430-24P Switches?

Piet — Mon, 12 Jan 2026 05:14:20 GMT

I looked over the upgrade instructions and its going over the TFTP approach that I am using but it remains as an update solution and Im starting with switches that have be cleaned and I think I need to do a full install.

It's a long doc and I may have missed something. So I have chatgpt read it as well. It continues to think that this update procedure isn't going to un-brick my switches.

-------------------------------------

Thanks for the link — you just shared a FastIron 08.0.30 upgrade guide PDF. That’s useful for overall understanding of how switch upgrades work, but it does not contain the factory/monolithic image (ICX64S…m.bin) you need to recover your switch.

Here’s the key distinction:

📌 What that PDF is

This document (FastIron 08.0.30 Upgrade Guide):

✅ Explains how to upgrade from one version to another
✅ Shows the supported procedures using u images
✅ Has examples of using TFTP, Bootloader, CLI commands
✅ Is great for normal switch maintenance

But it does not provide:

❌ The monolithic firmware image
❌ Any URLs to factory blobs
❌ A way to install an OS on a wiped switch

So reading that guide won’t fix the fact your switch currently boots only to BusyBox.

🚫 Why this doesn’t help your specific problem

Your switch is in a state where:

Flash is essentially blank
Only bootloader and minimal kernel are present
/fast_iron contains no userland
ICX CLI doesn’t exist on the box
No CLI will ever appear without a factory image

The upgrade guide assumes:

The switch already has a complete FastIron install

That’s exactly what your switch doesn’t have, which is why referencing an upgrade guide won’t fix your situation.

✅ What a recovery/factory image would look like

What you actually need is a file such as:

ICX64S08010m.bin ICX64S08030m.bin

or equivalently named monolithic / factory images for the ICX64xx platform.

Those contain:

✔ Full OS (FastIron userland)
✔ CLI binaries
✔ Init scripts
✔ Networking stack
✔ All switch services

Without one of these in flash, the switch always drops to BusyBox.

Why the monolithic image isn’t in that PDF

Upgrade guides never include huge firmware blobs. They describe how to upgrade, not provide the firmware.

That’s why:

📄 You saw an upgrade guide
❌ You did not see factory images anywhere
✔ Because those are part of the binary firmware packages — not documentation

But as we discussed earlier, Ruckus no longer publicly publishes the factory images in their zip bundles.

Your real situation (quick summary)

You have a Brocade/Ruckus ICX7450 that boots only to BusyBox.
Public downloads contain only update images (u / k) and not m.
Upgrade guides assume a working OS — they don’t apply here.
You need a monolithic factory image, which is not in the public download you have.

This is a policy/packaging issue with the vendor — not a user error.

Options that would actually solve this

Here are the paths that genuinely address the underlying problem:

✅ Option 1 — Extract from another working ICX7450

If you (or a colleague) have any working ICX7450:

copy flash primary tftp <your-ip> ICX64S_factory.bin

That file will restore your switch.

This is the most practical recovery path people use in labs.

✅ Option 2 — Ruckus TAC / Partner access

Open a support case and request:

“ICX64xx / ICX7450 monolithic/factory image — flash erased, only BusyBox boot.”

Under support/contract, Ruckus will provide the appropriate m.bin.

⚠️ Option 3 — Community archive

In some community forums or old mirrors, the monolithic image may still exist.
But these are unofficial, have varying availability, and I can help you verify a file before you use it if you find one.

Next step (practical)

If you want, I can help you with precise wording to ask Ruckus TAC so they understand your exact recovery situation and provide the correct file without back-and-forth.

Or if you find a potential monolithic image on a mirror, paste its name or link here and I’ll confirm whether it’s the right one.

Just tell me which direction you want to go:

✔ Get the exact TAC request text
OR
✔ I’ll help you search specific community mirrors for the factory image

Either one will move you forward — just pick one.

-------------------------

Re: How to get firmware for my ICX-6430-24P Switches?

Piet — Mon, 12 Jan 2026 05:20:07 GMT

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.

Where that leaves you (clean decision point)

There are no more technical experiments worth running. Only policy-gated paths remain:

✔ Path A — Donor switch (fastest in practice)

Extract the factory image from a working ICX7450.

✔ Path B — Ruckus TAC / partner

Ask explicitly for the ICX64xx monolithic/factory image.

✖ Path C — More ZIPs / guides

Guaranteed dead end (you’ve already proven it).

Re: How to get firmware for my ICX-6430-24P Switches?

Piet — Mon, 12 Jan 2026 07:22:51 GMT

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?

Re: How to get firmware for my ICX-6430-24P Switches?

Piet — Mon, 12 Jan 2026 21:29:40 GMT

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

Re: How to get firmware for my ICX-6430-24P Switches?

BenBeck — Mon, 12 Jan 2026 22:01:45 GMT

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

Re: How to get firmware for my ICX-6430-24P Switches?

Piet — Tue, 13 Jan 2026 05:20:27 GMT

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

Re: How to get firmware for my ICX-6430-24P Switches?

BenBeck — Wed, 14 Jan 2026 13:47:09 GMT

Here is the full recovery from bootmon if that is where you are stuck:

setenv ipaddr <device IP address> - set ip address
setenv netmask <255.255.255.0> - set subnet mask
setenv serverip <xxx.xxx.xxx.xxx> - set tftp server address
setenv gatewayip <xxx.xxx.xxx.xxx> - set gateway address
printenv
- Try to ping your TFTP server. If you cannot ping, check your connections. Once ping is successful, enter these commands:
setenv uboot <boot-code-bin> (change boot code image as needed)
setenv image_name <OS-image-bin> (change OS image as needed)
saveenv
tftpboot

Once booted, you will need to do a normal tftp copy from the fastiron OS to save it in flash. (tftpboot is one time; temporary)

Re: How to get firmware for my ICX-6430-24P Switches?

Piet — Fri, 16 Jan 2026 02:11:41 GMT

Im not having any problems installing. The problem is that the installed bits are incomplete.

I've done the install proceedure with about a dozen on the available images.

Perhaps The //fast_iron bits seem to be incomplete:

/ # find /fast_iron -print
/fast_iron
/fast_iron/sys
/fast_iron/sys/cvpersistent
/fast_iron/sys/persistent
/fast_iron/sys/cvpersistent.bkup
/fast_iron/sys/meta_data.bin
/fast_iron/sys/persistent.bkup
/fast_iron/sys/system
/fast_iron/sys/system.bkup
/fast_iron/logs
/fast_iron/logs/script.log
/fast_iron/logs/bootmsg
/fast_iron/cores
/fast_iron/$$ssh8rsahost.key
/fast_iron/poe-fw
/ #
CTRL-A Z for help | 9600 8N1 | NOR | Minicom 2.9 | VT102 | Offline | ttyUSB1

The /fast_iron/logs/script.log shows:

/dev/mtd3 partition's magic Number = 6533
JFFS2 magic number found.
Config partition mounted.
FIPS reset is enable.
Removing startup config & backup
Removing stacking.boot
Removing SSL_CERT_FILE
Removing SSH_RSA_HOSTKEY_FILE
Removing SSH_DSA_HOSTKEY_FILE
Inserting the module with watchdog disabled.
bunzip2: /bin/core.sh.bz2: No such file or directory <<<<<< BUG
mkdir: can't create directory '/dev/net': File exists
mknod: /dev/net/tun: File exists
Creating the first Tap interface
Set 'tap0' persistent and owned by uid 0
route: resolving br0
ERROR: Failure in gw add

The # ls /bin/core directory is EMPTY:
ls: /bin/core: No such file or directory
/ #

Also the /net directory is missing.

Re: How to get firmware for my ICX-6430-24P Switches?

Mayank — Fri, 24 Apr 2026 05:25:14 GMT

Hi Piet,

Thank you for the update,

Please log a ticket with the below link so that we will help you further

https://support.ruckuswireless.com/contact-us

Mayank Meena

Sr Tech Support Engineer - EMEA

Ruckus Networks