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

[Piet]

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

[Piet]

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).

---

 

[Piet]

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?

[Piet]

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:

1. Donor ICX7450 → extract factory image

2. 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.

.....

[Piet]

I installed the image with 

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

with update_primary cmd.

[Piet]

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)

1. You have a Brocade/Ruckus ICX7450 that boots only to BusyBox.

2. Public downloads contain only update images (u / k) and not m.

3. Upgrade guides assume a working OS — they don’t apply here.

4. 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.

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