Troubleshooting
Fixes for the messages ICX Setup shows, grouped by where they appear. If none of these resolves it, contact support.
Connecting over the console cable
Section titled “Connecting over the console cable”“Could not detect baud rate” / “Connected to the cable but can’t communicate with the switch. Try power cycling the switch.” — the cable is connected but the switch isn’t responding on any baud rate.
- Power-cycle the switch and try again — it may be mid-boot.
- Confirm the cable is in the switch’s console port, not a data port.
- If your adapter wasn’t flagged Recommended, make sure you picked the right
/dev/cu.*port under Show other ports. See Connecting to a switch.
Connecting over SSH
Section titled “Connecting over SSH”“The switch rejected the login credentials.” — the switch answered but the login failed. Add the correct password under Settings → Switch Passwords and reconnect. Remember the username is always super. See Logins and passwords.
“SSH handshake failed — the switch closed the connection…” — usually authentication failed or the switch rejected the SSH algorithms. Verify the credentials and that SSH is enabled on the switch. Note SSH needs FastIron 9.0 or later — for older firmware, use the console cable.
“Timed out connecting to <host>:<port>…” — the device accepted the TCP
connection but never completed the SSH handshake. Confirm the host and port, and
that it’s actually a switch listening for SSH.
”The switch’s SSH identity has changed”
Section titled “”The switch’s SSH identity has changed””Full message: “The switch’s SSH identity has changed since you last connected. This can happen after a factory reset — or it may mean someone is intercepting the connection. Only reconnect if you know this switch was reset.”
ICX Setup pinned this switch’s SSH host key on the first connection and it’s now presenting a different key, so it refuses to connect.
- If you know the switch was factory-reset or replaced, use Reset Pin & Reconnect to trust the new key.
- If you don’t, stop and investigate before continuing.
A related message — “Could not save the switch’s SSH host key to the Keychain…” or “Could not read the pinned SSH host key from the Keychain…” — means ICX Setup couldn’t verify the key and refused the connection by design. See Security and privacy.
Firmware upgrade
Section titled “Firmware upgrade”“Please select a .bin firmware image or .zip download” — the file you chose
isn’t a firmware image. Select the .bin, or the .zip from the support portal.
“This firmware file is for <X>. Select the correct file for your switch
model.” — the image family doesn’t match your switch. Download the image for
your model.
“No firmware image found for <model> in the zip file.” — the .zip didn’t
contain an image for this model. Use the correct download.
Missing intermediate images — “This upgrade needs intermediate firmware image(s) that weren’t provided… Add the missing image(s) to the firmware folder and try again.” A multi-hop upgrade needs every release on the path. Put them all in the same folder as the target image. See Upgrading firmware.
“Switch did not come back after reboot within 10 minutes” — the switch is taking longer than expected to restart. Wait a little longer, or power-cycle it if it doesn’t respond.
Transfers stall — if your Mac has several network interfaces, set a specific Server IP in Settings → Firmware Server on the same network as the switch, and raise the Transfer timeout if needed. See Settings.
“Could not load upgrade matrix.” / “Cannot determine current firmware
version.” / “Could not determine target version from <filename>.” — ICX
Setup couldn’t read the current version, the target from the filename, or its
upgrade rules. Re-assess the switch, and confirm you selected the right firmware
file.
Building a stack
Section titled “Building a stack”“<actual> of <expected> switches joined the stack. Check cables on the
missing units.” — fewer members joined than requested. Recheck the stacking
cables on the units that didn’t join and run Check Cables again. Remember
Check Again has a short cooldown. See
Building a stack.
“Firmware mismatch detected” — a member is on a different firmware version and will sync from the active controller as it joins; the wizard waits longer while it re-images. This is expected, not an error.
Adoption
Section titled “Adoption”“Configuration applied, but the switch hasn’t reported a controller connection yet…” — the config saved fine but the switch hadn’t registered within the two-minute window. This isn’t a failure; it keeps trying. Check the management platform in a few minutes, or Retry. For RUCKUS One, confirm the switch has working DNS — see Adopting to a platform.
“The management controller setting wasn’t saved. Check the terminal log for errors.” — the controller line didn’t apply. Open the terminal drawer to see what the switch reported, and retry.