Hardware Failure

Nokia 7250 IXR-S won't boot at all: Diagnose & Fix

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance
VendorNokia
Operating systemSR OS / SR Linux
CategoryHardware Failure
Skill levelIntermediate to advanced
DIY-able?Yes with CLI access; some scenarios need Nokia Customer Care + RMA.

If you have ever stared at a Nokia 7250 IXR-R6 that just refused to come up, you know the muscle memory: serial console at 9600 8N1, wait for the BOF> (Boot Options File) line, hope it actually paints. On SR OS / SR Linux the first move is always `show version` and `show chassis environment`, if those return cleanly the box is alive enough to talk to you, which is the difference between a ten-minute fix and an RMA paperwork morning.

I keep a small notebook of Nokia part-numbers next to the rack because the LED legend differs between hardware generations. The SR OS / SR Linux platform tends to tell the truth in `show` output before the front-panel LED catches up, so trust the CLI first.

This guide assumes you have console access and an active Nokia Customer Care entitlement. If the device is out of warranty, skip straight to the recovery section: most of the steps still apply, you just lose the RMA option at the end.

What this guide covers

Diagnose and recover from won't boot at all on a Nokia 7250 IXR-S.

Step-by-step

  1. Confirm power: PSU LED is green? Cable seated? Wall outlet live?
  2. Try a known-good power cable + outlet.
  3. If the device has multiple PSUs, try with only one PSU at a time.
  4. Connect the console cable and watch for ANY output during power-on.
  5. If completely dark (no LEDs, no console), suspect the PSU or motherboard.
  6. Confirm warranty status, open a Nokia Customer Care case, prepare for an RMA.

CLI / commands

# Verify hardware state
show version
show chassis
show chassis environment

# Collect for Nokia Customer Care
admin tech-support

When to RMA

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.

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

References


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

What changed recently?

Fault diagnosis on a Nokia device goes faster when you map the symptom to a recent change:

The answer narrows the root cause to a manageable subset.

Safety + preconditions

Before any work on a Nokia device:

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:

More frequently asked questions

How often should I run preventive checks?

Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.

Will this void my warranty?

Applying official firmware updates and following the user manual will not affect warranty. Opening sealed components, jumping safety circuits, or using third-party parts can void warranty in most jurisdictions.

What if my model isn't exactly the same revision?

Cross-check the model code on the rating plate against the manufacturer support page. Major firmware generations sometimes shift the menu path; the option is usually under a similarly-named section.

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent firmware update (rollback).

Can I roll this back if something breaks?

Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.