Sophos AP6 420: Upgrade Path to the next major release
By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30
| 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. |
Every Sophos upgrade I have shipped to production was paired with a written rollback. SFOS (Sophos Firewall OS) on the AP6 420 family makes rollback cheap if you saved the previous image and config. and expensive if you did not.
The system firmware-upload type=usb command on SFOS (Sophos Firewall OS) is straightforward once you have the right artifact staged. The trap is mismatched hardware-to-image, always cross-reference platform IDs from `system version (CLI)` against the image name.
I file every upgrade run under a change number and attach the before/after `system version (CLI)` and tech-support bundle. Sophos Support appreciates it; future me appreciates it even more.
What this guide covers
Upgrade procedure for Sophos AP6 420 to the next major release (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.
Related guides
Related fixes
Related guides worth a look while you sort this one out:
- Sophos AP6 420E: Upgrade Path to the next major release
- Sophos XGS 107: Upgrade Path to the next major release
- Sophos XGS 116: Upgrade Path to the next major release
- Sophos XGS 126: Upgrade Path to the next major release
- Sophos XGS 87: Upgrade Path to the next major release
- Sophos AP6 420: How to do an emergency image reload from the boot loader
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.
Safety + preconditions
Before any work on a Sophos device:
- Unplug from mains for any internal-access procedure.
- Discharge stored energy (capacitors in PSUs, residual battery charge) per manufacturer guidance.
- Use ESD-safe handling for boards and modules. no carpet, no wool sleeves.
- Avoid moisture; never apply liquids near vents or connectors.
- If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.
Verification checklist
After applying the fix on your Sophos device, confirm:
- The original symptom is no longer reproducible.
- Related features (status LEDs, app sync, paired accessories) still work.
- The device responds to a soft reboot without the fault returning.
- Any error codes that were on display have cleared.
- Documentation (your service log, the brand companion app) reflects the change.
Escalation guide
For a Sophos device, the right escalation depends on impact:
- Cosmetic / minor: log a ticket via the Sophos app or web portal. Response 1-3 business days.
- Mid-impact: phone support. Have your serial number ready.
- Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
- Out of warranty: third-party repair shop with manufacturer-certified technicians.
More frequently asked questions
Will the procedure work on the international variant?
Some features and firmware paths are region-locked. Check the model spec sheet to confirm your variant supports the menu option referenced. If you're outside the US/EU, look for the regional support portal.
How long does this fix usually take?
Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.
Are there safer alternatives for non-technical users?
Yes, the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.
What if my model isn't exactly the same revision?
Cross-check the model code on the rating plate against the manufacturer support page. Major firmware generations sometimes shift the menu path; the option is usually under a similarly-named section.
Is it safe to apply during business hours?
If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.