ZTE: 10G long-reach SR vs LR vs ER

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

Quick answer

SR (300 m MMF), LR (10 km SMF), ER (40 km SMF). Match wavelength on both ends.

How to pick the right cable / optic

1. Identify the link speed (1G / 10G / 25G / 40G / 100G).
2. Identify the distance (in-rack, in-room, cross-building, long-haul).
3. Identify the connector type on each end (RJ-45, LC, MPO, QSFP).
4. Check the ZTE supported transceiver matrix for your platform.
5. Use OEM-branded for production; third-party for lab or non-critical.

CLI to verify installed optics

show interface brief
show interface gei_1/1/1

Frequently asked questions

Will this work on my specific ZXR10 / ZXROS version?

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

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

https://support.zte.com.cn: 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

• All ZTE fix guides → /zte/
• All vendor guides → /vendors/

Related fixes

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

• Best ZTE firewall for branch office
• Best ZTE firewall for enterprise data centre
• Best ZTE firewall for retail store
• Best ZTE firewall for SD-WAN deployment
• Best ZTE firewall for small office
• Best ZTE firewall for SMB under USD 5000

References

• ZTE support portal: https://support.zte.com.cn
• ZTE knowledge base: https://support.zte.com.cn
• ZTE security advisories: https://support.zte.com.cn/support/news/AnnoucementOverviewLatest.aspx
• Open a case: https://support.zte.com.cn

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

Why this matters for your day-to-day

A ZTE: device that's misbehaving costs more than the fix itself: lost productivity, missed calls, security risk, even safety risk in some categories. Treating the symptom quickly with a documented procedure is cheaper than letting it persist. The steps above are written to get you back to working in under an hour where possible, and to flag clearly when escalation is the right call.

Safety + preconditions

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

Verification checklist

After applying the fix on your ZTE: device, confirm:

• The original symptom is no longer reproducible.
• Related features (status LEDs, app sync, paired accessories) still work.
• The device responds to a soft reboot without the fault returning.
• Any error codes that were on display have cleared.
• Documentation (your service log, the brand companion app) reflects the change.

When to call ZTE: 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

Does this affect other devices on my network?

Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.

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.

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.

Is it safe to apply during business hours?

If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.