ZTE OLT monitoring and ONU management

RadixOLT reads ZTE ZXA10 C600-series chassis over SNMP, finds unauthorized ONUs without taking a CLI login, and authorizes them with everything a working subscriber needs, including the service-port that ZTE leaves out by default.

Start 24-hour free trial Talk to sales

Models: ZXA10 C600, C610, C620, C650GPON
Reads: SNMPChassis health and alarms over the CLI
Writes: CLIUplink admin state over SNMP
Verified on: ZXA10 C610, software V1.2.2Two separate chassis

What RadixOLT reads

Everything polled is SNMP. The few readings this firmware keeps only in its CLI are read when you open the panel that shows them, and never on a timer. SNMP reads take none of the OLT’s CLI logins, which most chassis allow only one or two of. CLI means a session over SSH or Telnet, whichever the OLT is set to.

Read on every sweep or on request
Reading	How	Notes
ONU list, status and serial	SNMP	Identical answers on two C610 chassis with no code change between them.
ONU optical power	SNMP	Every column in thousandths of its unit; 2147483647 is the chassis’s no-reading marker and is shown as a blank.
ONU vendor and equipment id	SNMP	The equipment id reads `F601` where the CLI says `ZTE-F601`. This firmware reports no ONU software version over SNMP, so that column stays empty rather than showing a model.
ONU uptime	SNMP	Checked against the chassis’s own uptime first. See the notes below for why.
An open ONU page, live	SNMP	Re-read every 5 seconds while the page is open, with no CLI session.
Unauthorized ONUs waiting on a port (autofind)	SNMP	With software version and both find times, which the CLI’s own list does not print.
PON ports, their transceivers and authorized ONU count	SNMP	Link state, module presence, TX power and temperature for all 16 ports in about a second.
Uplink ports and their VLANs	SNMP	Tagged and untagged membership, with the port’s native VLAN folded in.
Uplink, PON and per-ONU traffic	SNMP
CPU, memory, temperatures, fans and power supplies	CLI	`show processor`, `show temperature detail`, `show fan`, `show power`. Read on request, not polled.
The chassis’s own active alarms	CLI	`show alarm current`. This firmware has no alarm table in SNMP.
Chassis model and software version	SNMP	From `sysDescr`, at no session cost.

What you can do from RadixOLT

Writes run over the CLI except one, and each is pre-flighted against the chassis’s own read so a command aimed at an empty slot cannot report success.

Every write asks first, names the OLT and the ONU, and is recorded
Action	How	Notes
Authorize an ONU	CLI	`onu <id> type <ONU type> sn <serial>`, the T-CONT and GEM port, the service VLAN, and the service-port on the ONU’s vport. ONU types and T-CONT profiles are read off the chassis.
Reboot an ONU	CLI	`reboot` from the ONU’s management context, answering the chassis’s yes/no question explicitly.
Delete an ONU	CLI	`no onu <id>`, which takes the ONU’s vport and service-port with it. Confirmed by reading the port again afterwards.
Add or remove uplink VLANs	CLI	`switchport vlan <list> tag`. Read back and compared, so a change that did not land is reported as a refusal.
Shut or open an uplink port	SNMP	Written, then read back. The chassis’s running-config confirmed the change during verification.

Not on ZTE yet: disabling and re-enabling an ONU, the MACs learned behind one ONU, the whole-chassis MAC read that Link Radius Server uses, and saving the running configuration.

Commands one click away in the terminal

Config mode names interfaces gpon_olt- and gpon_onu- on this line, not the C320’s gpon-olt_. These are the ZTE commands offered beside the live session.

show gpon onu state
show card
show gpon onu baseinfo gpon_olt-<shelf/slot/port>
show gpon onu detail-info gpon_onu-<shelf/slot/port:id>
show pon power attenuation gpon_onu-<shelf/slot/port:id>
show pon power onu-rx gpon_olt-<shelf/slot/port>
show optical-module-info gpon_olt-<shelf/slot/port>
show interface gpon_olt-<shelf/slot/port>
show snmp

Notes from live chassis

What reading this platform taught us, written down so you do not have to find it out on your own plant.

An authorized ONU can pass no traffic at all

Adding the T-CONT and GEM port creates the ONU’s vport in no VLAN. The ONU registers, reads working, shows real optical power, and forwards nothing until a service-port puts that vport in the VLAN. RadixOLT’s authorization writes it, and a vport’s map type cannot be changed afterwards, which is why it is done at once.

Discovered is not registered

A GPON port reads line protocol down until an ONU is actually working on it, even with three ONUs waiting in autofind. RadixOLT shows the port as the chassis reports it; a down port with ONUs queued on it is not a cut fibre.

Adding a VLAN to an uplink can create it

switchport vlan 1005 tag answered nothing and created VLAN 1005, which did not exist. There is no “VLAN does not exist” refusal on this line, so RadixOLT asks before writing a VLAN the chassis does not already have.

The online-duration counter cannot be trusted

On one C610 an ONU’s online duration went from 166 days to 335 days in 75 seconds while the CLI said 6 minutes. An ONU’s session cannot outlive the OLT it registered on, so any uptime longer than the chassis’s own is dropped rather than shown.

Health lives in the CLI only

The whole ZTE enterprise tree was walked, about 22,000 objects, and none of the CLI’s fan, temperature, CPU or memory readings appears in it. Those are read over the CLI when you open the health panel, and the panel does not poll them.

A power module can be abnormal while every status reads normal

show power prints two tables keyed by the same module number. On the tested chassis module 1 read abnormal in its run status while its other statuses all read normal, which is what its power alarms were about. RadixOLT joins the two tables before showing either.

Adding one to RadixOLT

Everything the onboarding form asks for, in the order it asks.

Make the management address reachable
RadixOLT polls from its own servers, so the OLT’s management IP, or a NAT forward to it, has to answer from outside. If it cannot, the self-hosted install runs the same product inside your network.
Give it a CLI login
SSH or Telnet, the port, and a username and password. Polling never uses it; authorization, reboots, deletes and VLAN edits do. Stored encrypted and never shown again.
Give it SNMP
The community and the SNMP port. Reads, discovery and the uplink admin write all go this way, so the CLI stays free for the operator.
Pick the model if you know it
C600, C610, C620 or C650. Optional: one adapter reads them all, and the model is kept because the record is hard to rebuild later.
Turn on auto-poll
Every 15 minutes by default, spread per OLT.

Other platforms

The same product on the rest of your plant. Compare every platform side by side.