Upgrade Paths

Sophos XGS 126: 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.

On Sophos kit the upgrade ritual matters more than the speed. `system version (CLI)` first, `system support-tools generate-debug-info` second, then the actual `system firmware-upload type=usb`. that order on SFOS (Sophos Firewall OS) saves the most support-case time when something goes wrong on the XGS 87 unit.

Integrity verification is non-negotiable. Vendor mirrors get corrupted, internal staging servers serve stale files, and the checksum step on SFOS (Sophos Firewall OS) is the only thing standing between you and a chassis that boots to a recovery prompt.

What follows is the safe-rollback variant. If you need an in-place upgrade with zero rollback path, this guide is not it, and frankly that is not a thing you should be doing on production gear.

What this guide covers

Upgrade procedure for Sophos XGS 126 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.

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.

Quick verification

Before you walk away from a Sophos 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.

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.