ZTE: How to enable NETCONF or vendor API over SSH

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

What this guide covers

How to enable NETCONF or vendor API over SSH on ZTE devices (ZXR10 / ZXROS).

Recommendation

Modern automation needs API access. Enable NETCONF / vendor API only over SSH or TLS.

CLI / commands

# Entered from: configure terminal
interface gei_1/1/1
  ip address 10.0.0.1 255.255.255.0
  no shutdown

# Save / commit
write

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 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:

• ZTE: How to enable control-plane policing / rate-limiting
• ZTE: How to enable HTTPS-only management
• ZTE: How to enable management ACL to lock down access
• ZTE: How to replace Telnet with SSH
• ZTE: How to configure logging to a central SIEM
• ZTE: How to disable unused services and protocols

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.

What changed recently?

Fault diagnosis on a ZTE: 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 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.

Escalation guide

For a ZTE: device, the right escalation depends on impact:

• Cosmetic / minor: log a ticket via the ZTE: app or web portal. Response 1-3 business days.
• Mid-impact: phone support. Have your serial number ready.
• Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
• Out of warranty: third-party repair shop with manufacturer-certified technicians.

More frequently asked questions

Should I update firmware first or last?

Update firmware first if a release note specifically mentions your symptom. Otherwise, finish the troubleshooting flow first, then update; that way you can isolate whether the update or the underlying fix solved it.

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.

How long does this fix usually take?

Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.

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.

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.