Managing Ruckus ICX switches or Access Points (APs) can be challenging, especially when devices are inherited, misconfigured, or stuck in an unstable state. Whether it’s a forgotten password, a boot loop, or a corrupt configuration, knowing how to properly reset your Ruckus hardware is essential.
For enterprise environments, a reset isn’t just about clearing settings—it may also affect licenses, firmware, and ongoing network operations. This guide walks IT professionals, network engineers, and system integrators through safe, repeatable procedures for Ruckus ICX switches and Ruckus APs, with practical advice to restore devices efficiently and minimize downtime.
Table of Contents
- Part 1: Understanding Your Reset Scenario
- Part 2: Ruckus ICX Switches – Hard Reset (Physical Button)
- Part 3: Soft Reset and CLI-Based Recovery
- Part 4: Ruckus Access Point Reset
- Part 5: Post-Reset Best Practices
- Part 6: Deciding When to Repair or Replace
- Part 7: Conclusion
Part 1: Understanding Your Reset Scenario
Before pressing any buttons or issuing commands, determine your goal. Not every reset method is appropriate for every problem.
| Scenario | Goal | Recommended Method | Risk Level |
| Lost admin password | Retain configuration (VLANs, routing) | Password Recovery (CLI / Bootloader) | Low |
| Switch stuck in boot loop | Restore functional state | Physical Hard Reset (ICX) | High (licenses lost) |
| Inherited / Pre-deployment unit | Wipe all settings | Bootloader Reset (ICX) or CLI `set factory` (AP) | Medium/High |
| Configuration errors | Start fresh | CLI Factory Reset (FOS/ICX Legacy) | Medium (if backup available) |
Part 2: Ruckus ICX Switches – Hard Reset (Physical Button)
The physical hard reset is necessary when the switch is stuck in boot mode or when CLI access is unavailable. Indicators typically include Amber/Orange SYST LED with a Green PWR LED.
Warning: License Loss Risk
Physical hard resets on ICX switches, like the RUCKUS ICX-7150-C12P, erase:
- Startup configuration
- Logs and core dumps
- Firmware cached files
- Licenses (10G ports, Layer 3 features, etc.)
You must reapply licenses after the reset. Consider backing up license files before proceeding.
Step-by-Step Hard Reset
- Locate and Power Off: Identify the reset button (often front panel). Disconnect the power cable.
- Press and Hold: Use a straightened paper clip to hold the button for 10–15 seconds.
- Power On While Holding: Reconnect power while holding the reset button. Wait until LEDs start blinking.
- Release and Wait: Release the button once LEDs blink. Wait 3–5 minutes for the system to reboot fully.
- Verify:
- PWR LED: solid green
- STAT LED: blinking green
- Configuration: empty (`show run` should be blank)
- Default credentials: typically `admin` / `password`
Tip: Avoid unplugging power during reset. Interruptions can leave the device unstable.
Part 3: Soft Reset and CLI-Based Recovery
Soft Reset (Configuration Wipe Without Physical Button)
If you have admin access:
- Connect via SSH or Console.
- Enter privileged mode:
enable - Erase startup configuration:
erase startup-config - Reload:
reload - Confirm No when prompted to save old configuration.
Bootloader Factory Reset (Lost Password / Corrupt Config)
- Connect a console cable and watch the boot sequence.
- Stop autoboot by pressing
b. Enter Boot Monitor. - Factory reset from bootloader:
factory set-default -> Y reset - Device will reboot. Afterward, verify configuration is cleared.
Password Recovery (Non-Destructive)
- Log in via CLI with root or SecurityAdmin.
- Change password:
passwd admin - Set strong new password following company policy.
Notes:
- Preserves VLANs and routing settings.
- FOS 9.x: root account may be disabled; use maintenance account as needed.
Part 4: Ruckus Access Point Reset
For Ruckus APs (RXX0, HXX0, TXX0 series):
| AP Series | Physical Reset | CLI Method |
| R-series | Near Ethernet/USB port, hold 8–10 sec |
|
| H-series | Separate Reset / Factory Default buttons | CLI `set factory` |
| T-series | Inside PoE plug | CLI `set factory` |
Cloud-managed APs cannot reset via CLI; use Cloud UI or physical button.
Part 5: Post-Reset Best Practices
- Change default credentials immediately.
- Reapply licenses (if lost during hard reset).
- Restore configuration if backups exist (
configupload). - Update firmware to stable version (ICX 08.0.95s recommended for legacy switches).
- Test device stability before returning to production.
Troubleshooting Common Issues
| Issue | Diagnosis & Action |
| Switch stuck in boot loop | Repeat physical reset (hold 10–12 sec). If unresolved, console recovery needed. |
| Reset interrupted | Reissue reset commands; do not unplug power. |
| No login via web console | CLI credentials may conflict; reset via console. |
| Device shows no lights | Check power source and cables; try a known-good outlet. |
Part 6: Deciding When to Repair or Replace
Repeated factory resets, persistent boot loops, or frequent failures often indicate:
- End-of-Life device (e.g., ICX 64xx/66xx series)
- Firmware unable to handle flash corruption
- Performance limitations for modern workloads (Wi-Fi 6, multi-gig networks)
Router-switch.com supports decision-making with:
- Verified inventory: Original Ruckus/Brocade devices, serial-verified
- Fast shipping: Global delivery in 1–5 days
- Expert support: CCIE-certified guidance for configuration and recovery
- Strategic procurement: Quick replacement and multi-vendor sourcing
Part 7: Conclusion
A Ruckus switch reset is more than pressing a button—it’s a decision that impacts configuration, licenses, and uptime. By choosing the right method—soft reset, hard reset, or password recovery—network teams can safely restore devices and continue operations with minimal downtime.
For devices showing repeated failures, Router-switch.com offers reliable replacement options and expert support to keep your network running efficiently.
Expertise Builds Trust
20+ Years • 200+ Countries • 21500+ Customers/Projects
CCIE · JNCIE · NSE7 · ACDX · HPE Master ASE · Dell Server/AI Expert