Nokia: How to replace Telnet with SSH
By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30
| Vendor | Nokia |
|---|---|
| Operating system | SR OS / SR Linux |
| Category | Hardening & Safe Protocols |
| Skill level | Intermediate to advanced |
| DIY-able? | Yes with CLI access; some scenarios need Nokia Customer Care + RMA. |
What this guide covers
How to replace Telnet with SSH on Nokia devices (SR OS / SR Linux).
Recommendation
Enable SSHv2 only; remove Telnet from the management interface; restrict to admin source IPs.
CLI / commands
# Entered from: configure
/configure router interface to-customer address 10.0.0.1/24
commit
# Save / commit
admin save
Verify
- Test from a non-admin workstation.
- Confirm fallback works if AAA or external service is down.
- Document the change in your CMDB / change-control.
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
Related fixes
Related guides worth a look while you sort this one out:
- Nokia: How to enable NETCONF or vendor API over SSH
- Nokia: How to replace SNMPv2c with SNMPv3
- Nokia: How to configure logging to a central SIEM
- Nokia: How to disable unused services and protocols
- Nokia: How to enable control-plane policing / rate-limiting
- Nokia: How to enable HTTPS-only management
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.
What changed recently?
Fault diagnosis on a Nokia: device goes faster when you map the symptom to a recent change:
- Did firmware update in the last 7 days?
- Did the network (router, ISP, VPN) change?
- Was the device moved physically?
- Did paired devices (phone, hub, app) update?
- Were any accessories swapped in or out?
The answer narrows the root cause to a manageable subset.
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.
More frequently asked questions
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).
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.
Why is this happening on a brand-new unit?
Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a factory reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.
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.
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.