Upgrade Failure

Nokia 7250 IXR-X: How to rollback to the previous image after a failed upgrade

Q: Where can I find the Nokia official documentation?

https://documentation.nokia.com — 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	Nokia
Operating system	SR OS / SR Linux
Category	Upgrade Failure
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need Nokia Customer Care + RMA.

Upgrade work on a Nokia fleet is mostly about discipline. SR OS / SR Linux gives you the commands; the failure mode is almost always operator error: wrong image for the platform, integrity not checked, no rollback plan. The 7250 IXR-R6 family is no exception.

I always do a one-box pilot before a fleet roll. file copy cf3:/timos-21.10.R1.tim cf3:/timos.tim on a single representative unit, then 24 hours of soak, then the rest of the fleet in waves. Skipping the soak has bitten me twice.

Nokia Customer Care will want the exact build string and the upgrade method (CLI vs controller-driven) on every case, so keep that recorded for the change ticket.

What this guide covers

Rollback to the previous image after a failed upgrade on a Nokia 7250 IXR-X (SR OS / SR Linux).

Step-by-step

Confirm there's a previous image still on flash.
Set the boot variable to that previous image.
Reboot.
Verify the version is back to the prior release.
Investigate the upgrade failure separately, do not re-attempt without root cause.

CLI / commands

# Boot recovery prompt: BOF> (Boot Options File)

# Verify image
show version

# Upgrade
file copy cf3:/timos-21.10.R1.tim cf3:/timos.tim

# Save / commit
admin save

# Rollback
rollback

Recovery options

Boot loader recovery (BOF> (Boot Options File))
Rollback to the previous image with rollback
Force failover to a known-good standby (HA platforms)

Frequently asked questions

Will this work on my specific SR OS / SR Linux version?

The procedure reflects current SR OS / SR Linux behaviour. Older releases may need minor syntax adjustments. use the CLI help (? or tab-completion) to verify.

Should I open a Nokia Customer Care 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 Nokia official documentation?

https://documentation.nokia.com, 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 Nokia fix guides → /nokia/
All vendor guides → /vendors/

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

References

Nokia support portal: https://customer.nokia.com
Nokia knowledge base: https://documentation.nokia.com
Nokia security advisories: https://www.nokia.com/about-us/security/vulnerability-management/
Open a case: https://customer.nokia.com

Reference material, not professional advice. Validate against your specific SR OS / SR Linux version and test in a non-production environment before applying.

Common patterns we see

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

Safety + preconditions

Before any work on a Nokia 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 Nokia 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.

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