Upgrade Paths

Nokia 7705 SAR: Upgrade Path to the next major release

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 Paths
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need Nokia Customer Care + RMA.

An upgrade on Nokia 7705 SAR 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.

SR OS / SR Linux provides clear pre- and post-checks. `show version` before and after is the bare minimum; ideally also `admin tech-support` so Nokia Customer Care 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 SR OS / SR Linux release notes first.

What this guide covers

Upgrade procedure for Nokia 7705 SAR to the next major release (SR OS / SR Linux).

Notes specific to this combination

Verify the supported upgrade path in the Nokia release notes before proceeding. Some SR OS / SR Linux releases require an intermediate hop; some support direct upgrade.

Step-by-step

Verify current version: show version.
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 file copy cf3:/timos-21.10.R1.tim cf3:/timos.tim.
Reboot: admin reboot now.
Verify; admin save if healthy.

CLI / commands

show version
show chassis
file copy cf3:/timos-21.10.R1.tim cf3:/timos.tim
admin save

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.

Before you start

A few things to confirm so the Nokia 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.

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.