Upgrade Failure

Sophos XGS 116: How to perform a controlled upgrade with rollback safety net

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 Failure
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 XGS 87 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

Perform a controlled upgrade with rollback safety net on a Sophos XGS 116 (SFOS (Sophos Firewall OS)).

Step-by-step

Back up the current running config and image.
Download the new image and verify checksum.
Activate the new image; do NOT commit if the platform supports staged commit.
Verify production traffic on the new image.
Commit if healthy, or rollback within the safe window if not.

CLI / commands

# Boot recovery prompt: Recovery console (USB)

# Verify image
system version (CLI)

# Upgrade
system firmware-upload type=usb

# Save / commit
(auto-saves in Web UI; CLI changes persist)

# Rollback
system backup-restore restore

Recovery options

Boot loader recovery (Recovery console (USB))
Rollback to the previous image with system backup-restore restore
Force failover to a known-good standby (HA platforms)

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.

Common patterns we see

When this symptom shows up on a Sophos 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 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.

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.