Skip to content
Skip to content
Tutorials

ZTE OLT GPON Provisioning: From Splice to Subscriber

Zill E Ali
May 4, 2026 3 min read
GPON OLT chassis in a telecom rack with dense yellow and blue fiber optic patch cords

A GPON subscriber goes from spliced drop cable to working internet in about ninety seconds of CLI — but only if the optical work before it was done properly. This is the workflow I run on ZTE C320 and C300 OLTs, in the order it actually happens on site.

Before you touch the OLT#

Measure first. Roughly 80% of "provisioning problems" are optical problems wearing a config costume.

ReadingHealthyAction if outside
ONU RX power−15 to −25 dBmRe-clean connectors, inspect splice, re-check splitter ratio
OLT RX from ONU−13 to −27 dBmSuspect a dirty or bent drop fibre
Splice loss< 0.1 dBRe-splice
Connector loss< 0.5 dBClean with a one-click cleaner, re-measure

A 1:32 splitter costs about 17–18 dB of budget on its own. Two cascaded splitters plus a long feeder is how you end up at −28 dBm and a link that only fails when it rains.

1. Discover the ONU#

bash
ZXAN# show gpon onu uncfg
gpon-onu_1/1/1:1 ZTEGC1A2B3C4 unknown

The serial matches the label on the ONU. If nothing appears, stop and go back to the optical table above — do not "try another port".

2. Authenticate and bind#

bash
ZXAN# configure terminal
ZXAN(config)# interface gpon-olt_1/1/1
ZXAN(config-if)# onu 1 type ZTEG-F660 sn ZTEGC1A2B3C4
ZXAN(config-if)# exit

Keep the ONU index deliberate — index 1–32 mapped to a documented customer ID. Random indexes make the second engineer's life miserable.

3. Service configuration#

bash
ZXAN(config)# interface gpon-onu_1/1/1:1
ZXAN(config-if)# name CUST-10432
ZXAN(config-if)# tcont 1 name INTERNET profile 30M-up
ZXAN(config-if)# gemport 1 tcont 1
ZXAN(config-if)# service-port 1 vport 1 user-vlan 100 vlan 100
ZXAN(config-if)# exit

The T-CONT carries the upstream bandwidth contract, the GEM port carries the traffic, and the service port maps the subscriber VLAN. All three or nothing works.

4. Bandwidth profiles#

Define profiles once, reuse them for every plan:

bash
ZXAN(config)# gpon
ZXAN(config-gpon)# profile tcont 30M-up type 3 assured 20480 maximum 30720

Type 3 (assured + maximum) is the right default for residential: a guaranteed floor with burst headroom. Type 1 fixed bandwidth wastes capacity on a shared PON.

5. Verify before you leave#

bash
ZXAN# show gpon onu state gpon-olt_1/1/1
ZXAN# show pon power attenuation gpon-onu_1/1/1:1
ZXAN# show gpon onu detail-info gpon-onu_1/1/1:1

State must read working, and attenuation should sit under 25 dB. Then run an actual speed test from the customer premises — the OLT saying "working" and the customer having internet are different claims.

Recurring field faults#

  • ONU flapping every few minutes. Almost always a marginal splice or a macro-bend in the drop cable at the wall entry. Check RX power over time, not once.
  • LOS on the whole port after a storm. Feeder damage or water in an unsealed closure. Check the port before assuming thirty ONUs failed independently.
  • One subscriber slow, everyone else fine. Wrong T-CONT profile applied, or the ONU's LAN port negotiated at 100 Mbps.
  • New ONU refuses to register. Serial already bound elsewhere. show gpon onu by sn finds it.

Documentation that pays for itself#

For every activation, record: customer ID, ONU serial, OLT/port/index, VLAN, plan profile, RX power at activation. That last figure is the baseline you compare against when the same customer complains eight months later — and it turns a two-hour diagnosis into a two-minute one.

Zill E Ali

MTCNA-certified network engineer & founder of NexaLink. ISP infrastructure, MikroTik, and FTTH.

View all posts by Zill E Ali →

Related articles

Comments coming soon — powered by Giscus in Phase 2.