Upgrade Failure

SonicWall SWS14-24: How to do an emergency image reload from the boot loader

Q: Where can I find the SonicWall official documentation?

https://www.sonicwall.com/support/knowledge-base/ — search the product family + feature name.

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance

Vendor	SonicWall
Operating system	SonicOS
Category	Upgrade Failure
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need SonicWall Support + RMA.

Upgrade work on a SonicWall fleet is mostly about discipline. SonicOS gives you the commands; the failure mode is almost always operator error, wrong image for the platform, integrity not checked, no rollback plan. The SWS14-24 family is no exception.

I always do a one-box pilot before a fleet roll. system upload-firmware ftp://10.10.1.100/firmware.bin on a single representative unit, then 24 hours of soak, then the rest of the fleet in waves. Skipping the soak has bitten me twice.

SonicWall Support will want the exact build string and the upgrade method (CLI vs controller-driven) on every case, so keep that recorded for the change ticket.

What this guide covers

Do an emergency image reload from the boot loader on a SonicWall SWS14-24 (SonicOS).

Step-by-step

At the boot loader, configure IP, gateway, TFTP server.
Download the image.
Set the boot variable to the new image.
Reset to boot.

CLI / commands

# Boot recovery prompt: Safe Mode

# Verify image
show version (CLI)

# Upgrade
system upload-firmware ftp://10.10.1.100/firmware.bin

# Save / commit
commit

# Rollback
system import-settings ftp://10.10.1.100/backup.exp

Recovery options

Boot loader recovery (Safe Mode)
Rollback to the previous image with system import-settings ftp://10.10.1.100/backup.exp
Force failover to a known-good standby (HA platforms)

Frequently asked questions

Will this work on my specific SonicOS version?

The procedure reflects current SonicOS behaviour. Older releases may need minor syntax adjustments: use the CLI help (? or tab-completion) to verify.

Should I open a SonicWall Support case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.

Where can I find the SonicWall official documentation?

https://www.sonicwall.com/support/knowledge-base/, search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

All SonicWall fix guides → /sonicwall/
All vendor guides → /vendors/

Related guides worth a look while you sort this one out:

References

SonicWall support portal: https://www.sonicwall.com/support
SonicWall knowledge base: https://www.sonicwall.com/support/knowledge-base/
SonicWall security advisories: https://psirt.global.sonicwall.com
Open a case: https://www.mysonicwall.com

Reference material, not professional advice. Validate against your specific SonicOS version and test in a non-production environment before applying.

Common patterns we see

When this symptom shows up on a SonicWall device, three patterns repeat:

1. Recent firmware update changed behavior. the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger, temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear: components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.

Knowing which pattern applies saves time on the wrong fix.

Before you start

A few things to confirm so the SonicWall device fix goes cleanly:

Latest firmware downloaded if you're going to update.
Warranty + support contract status checked, opening sealed parts may void it.
Backup of current configuration (where applicable) taken.
Spare parts on hand if you anticipate replacement.
Adequate workspace, lighting, and time. rushing causes regressions.

Quick verification

Before you walk away from a SonicWall device fix, run through:

1. Reproduce the original trigger, does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.

When to call SonicWall support instead

Escalate if:

The same symptom returns within 24 hours of a clean fix.
You see physical damage (burn marks, swollen battery, cracked PCB).
The device is in warranty and a hardware replacement is the cheaper outcome.
Repair requires specialised tools you don't own (alignment jigs, calibration software).
Following the official path keeps the warranty intact, which matters more than the time spent.