Upgrade Paths

Sophos AP6 420: Upgrade Path to latest LTS / GA

Q: Where can I find the Sophos official documentation?

https://support.sophos.com/support/s/ — 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	Sophos
Operating system	SFOS (Sophos Firewall OS)
Category	Upgrade Paths
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need Sophos Support + RMA.

Image upgrades on Sophos platforms have one cardinal rule: verify the running image first. `system version (CLI)` on SFOS (Sophos Firewall OS) is the single most useful command in a change window because it tells you exactly what you are rolling back to if something breaks.

Across the AP6 420 family the upgrade syntax is `system firmware-upload type=usb`: pay attention to the activation step because SFOS (Sophos Firewall OS) treats download and activate as separate transactions. Forgetting the activation step is the single most common reason an 'upgrade' silently does nothing.

Sophos Support expects you to capture pre-upgrade state and have a console session open during the change window. Anything less is a support-case waste of time if it goes sideways.

What this guide covers

Upgrade procedure for Sophos AP6 420 to latest LTS / GA (SFOS (Sophos Firewall OS)).

Notes specific to this combination

Verify the supported upgrade path in the Sophos release notes before proceeding. Some SFOS (Sophos Firewall OS) releases require an intermediate hop; some support direct upgrade.

Step-by-step

Verify current version: system version (CLI).
Read the release notes for supported upgrade paths.
Confirm minimum RAM / disk for the target release.
Download target image; verify checksum.
Schedule maintenance window.
Back up running configuration.
Copy image to local flash.
Run system firmware-upload type=usb.
Reboot: system reboot.
Verify; (auto-saves in Web UI; CLI changes persist) if healthy.

CLI / commands

system version (CLI)
system status
system firmware-upload type=usb
(auto-saves in Web UI; CLI changes persist)

Frequently asked questions

Will this work on my specific SFOS (Sophos Firewall OS) version?

The procedure reflects current SFOS (Sophos Firewall OS) behaviour. Older releases may need minor syntax adjustments, use the CLI help (? or tab-completion) to verify.

Should I open a Sophos 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 Sophos official documentation?

https://support.sophos.com/support/s/. 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 Sophos fix guides → /sophos/
All vendor guides → /vendors/

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

References

Sophos support portal: https://support.sophos.com
Sophos knowledge base: https://support.sophos.com/support/s/
Sophos security advisories: https://www.sophos.com/en-us/security-advisories
Open a case: https://secure2.sophos.com/en-us/support.aspx

Reference material, not professional advice. Validate against your specific SFOS (Sophos Firewall OS) version and test in a non-production environment before applying.

Why this matters for your day-to-day

A Sophos device that's misbehaving costs more than the fix itself: lost productivity, missed calls, security risk, even safety risk in some categories. Treating the symptom quickly with a documented procedure is cheaper than letting it persist. The steps above are written to get you back to working in under an hour where possible, and to flag clearly when escalation is the right call.

Before you start

A few things to confirm so the Sophos 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.

How to confirm it's actually fixed

On a Sophos device, the test is rarely "reboot and see". Use this list:

Active reproduction: trigger the original failure path on purpose.
Indirect reproduction: do an activity that would expose the same subsystem.
Status indicator review: every LED / display / app status should be green.
24-hour soak: leave the device under normal load overnight; check the next morning.
Telemetry check: review the device or app's diagnostic log for new error entries.

When to call Sophos 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.