Upgrade Paths

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

An upgrade on Sophos XGS 87 is really three jobs: stage the image, verify integrity, activate. Skipping verify is how you end up with a half-bricked unit at 2am. I have done it exactly once and learned for life.

SFOS (Sophos Firewall OS) provides clear pre- and post-checks. `system version (CLI)` before and after is the bare minimum; ideally also `system support-tools generate-debug-info` so Sophos Support has a clean before/after diff.

The procedure below assumes you can take a maintenance window. If you cannot, ISSU / hitless options exist on some platforms but vary by code train, check SFOS (Sophos Firewall OS) release notes first.

What this guide covers

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

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.