Firmware versions and upgrade rules

Before it touches a switch, the Upgrade wizard checks the target release against a built-in matrix: is this release safe to run at all, does this model still support it, and what has to be installed on the way there. This page is that matrix, written out.

Releases ICX Setup refuses

Three releases are marked pulled and cannot be chosen as a target. Picking one stops the wizard with “Version <x> has been pulled and should not be used”:

• 09.0.00
• 09.0.00a
• 09.0.10

Note that 09.0.10 is pulled but 09.0.10a is not — 09.0.10a is the intermediate release the matrix routes through on the way to 10.0.10.

Per-family version support

Family	First release	Last supported release	Max stack
ICX 8200	10.0.10	—	12
ICX 8100	10.0.10f	—	4 (from 10.0.10h)
ICX 7850	08.0.90	—	12
ICX 7650	08.0.90	—	12
ICX 7550	08.0.95	—	12
ICX 7450	08.0.90	09.0.10a	not supported
ICX 7250	08.0.90	09.0.10a	not supported
ICX 7150	08.0.90	—	12, dropping to 8 from 10.0.10f

The last supported release column is the one the wizard enforces: targeting a release past it stops the upgrade with “<model> is not supported past <version>”. ICX 7450 and ICX 7250 were dropped in 10.0.10, so ICX Setup will not take either past 09.0.10a.

ICX 7150 is absent from 10.0.x before 10.0.10f — 10.0.10f is the first 10.0.x release for that family, and it is also where the stack limit drops from 12 to 8.

ICX 7450 and ICX 7250 can't be stacked from ICX Setup

Both models are recognised, assessed, and upgraded, but ICX Setup carries no stacking-port data for them, so the Stack wizard can’t build a stack of either. Build those stacks from the switch CLI.

The hops ICX Setup inserts

FastIron does not allow every version-to-version jump. When your current and target releases are separated by one of these rules, ICX Setup inserts the required release as its own step and runs the steps in order:

Current version	Target version	Hop inserted first
Below 08.0.80 (non-UFI)	08.0.90 or later	08.0.80f
08.0.80 – 08.0.89	09.0.10a or later	08.0.95
08.0.90 – 08.0.94	09.0.10a or later	08.0.95d
08.0.95 – 08.0.99	10.0.10 or later	09.0.10a
09.0.10a or later	10.0.10 or later	none — direct
08.0.90 or later	below 09.0.00	none — direct

Hops chain: a switch on 08.0.70 going to 10.0.10 passes through 08.0.80f, then 08.0.95, then 09.0.10a. Each hop is a full transfer-and-reboot cycle, which is why the wizard estimates roughly 8 minutes per step.

The image filename each step looks for

ICX Setup serves each step’s image by name from the folder holding the file you selected — so every release on the path must be present in that folder, under the vendor’s own filename. These are the names it looks for:

Family	Prefix	Known images
ICX 7150, 7450, 7250	SPR	SPR08080f.bin, SPR08090ufi.bin, SPR08095ufi.bin, SPR08095dufi.bin, SPR09010aufi.bin, SPR10010fufi.bin
ICX 7850, 7650	TNR	TNR08090ufi.bin, TNR08095ufi.bin, TNR09010aufi.bin, TNR10010ufi.bin
ICX 7550	GZR	GZR08095ufi.bin, GZR09010aufi.bin, GZR10010ufi.bin
ICX 8200	RDR	RDR10010ufi.bin

For a release not in that list, ICX Setup builds the name from the convention — prefix, then two-digit major, one-digit minor, two-digit patch, the letter suffix, then ufi.bin. So 10.0.10g on an ICX 7150 is SPR10010gufi.bin.

If a required name isn’t in the folder, the upgrade stops before changing anything, listing what’s missing. Rename nothing: the check is on the filename, so a correct image saved under a different name will not be found.

ICX 8100 firmware images aren't in the matrix yet

ICX Setup knows no image filenames for the ICX 8100 family. An 8100 upgrade builds a placeholder name beginning TBDR…, which no shipped RUCKUS image matches, so the wizard stops with a missing-image error. Assessment, stacking, and adoption work normally on the ICX 8100 — only the upgrade path is affected. Contact support if you need to upgrade one.

Version-specific gotchas

For releases that change behaviour, the Upgrade Path screen shows notes against the step that installs them. They are reproduced here because most of them describe work to do before or after the upgrade, not during it.

Upgrading to 09.0.10

• SHA1 password users are removed on upgrade — re-create them with SHA256 or better afterwards, or you will lose those logins.
• cli timeout replaces ip ssh idle-time, telnet timeout, and console timeout — the old lines don’t survive.
• Stack-port commands require the ethernet keyword (stack-port ethernet 1/2/1). ICX Setup already emits the right form for the version it is talking to.
• ICX 7750 is no longer supported — remove it from the stack before you upgrade.

Upgrading to 10.0.10

• The switch (L2) image is discontinued — 10.0.10 ships a router (L3) image only.
• ICX 7450 and ICX 7250 are no longer supported.
• ICX 7150 max stack size drops from 12 to 8, and units with IDs above 8 must be renumbered before the upgrade.
• Forwarding-profile migration is required on ICX 7550.
• Usernames containing colons must be renamed before upgrading.
• Management VLAN config syntax changes — this one is migrated automatically.

Errors from these checks

Message	What it means
”Version <v> has been pulled and should not be used”	The target is one of the three pulled releases above.
”<model> is not supported past <version>”	The target is later than the family’s last supported release.
”<model> is not supported on firmware <version>”	The model and target release aren’t a valid pairing.
”Stack has <n> units but <version> only supports <max>”	The target release caps the stack smaller than its current size — renumber or split first.
”No upgrade path exists from <a> to <b>”	No rule chain connects the two releases.

All five stop the wizard before anything is sent to the switch.

Next steps

Upgrading firmware Run the upgrade — choosing the image, reviewing the path, and what each step does to the switch.

Building a stack Stack sizes, topology, and the cable check — including the per-family limits above.

Troubleshooting What to do when an upgrade stops on a missing image or a reboot timeout.

---

Contact support.