DBC OLT monitoring and ONU management

DBC’s V1600G runs the same V-SOL firmware family as Syrotech’s GPON line. RadixOLT reads it over SNMP, keeps the chassis’s one CLI login free, and reboots, disables and deletes ONUs over SNMP too.

Start 24-hour free trial Talk to sales

Model: V1600GGPON
Reads: SNMPCLI fallback when SNMP is switched off
Writes: SNMPReboot, disable, enable, delete, save
Verified on: A live DBC V1600GBeside the Syrotech badge of the same platform

What RadixOLT reads

The DBC and Syrotech GPON badges were compared object by object in their own MIB files before either was trusted: every table RadixOLT reads is present in both under the same name and type. One implementation reads both, and each was verified on its own chassis. 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, serial and description	SNMP	The serial comes from the same column the single-ONU poll reads, so an ONU can never show two serials.
Optical power	SNMP	Read ONU by ONU. A down ONU answers the literal `NULL` on every optical column, which is never turned into a number.
Uptime, last deregister reason and its time	SNMP	Uptime is the ONU’s current session, shown only while it is online. The reason is DBC’s own wording.
An open ONU page, live	SNMP	Re-read every 5 seconds while the page is open, with no CLI session.
PON ports and their transceivers	SNMP	Link state, TX power, temperature, voltage and bias, plus module vendor, wavelength and serial.
Uplink ports, uplink and PON traffic, per-ONU traffic	SNMP
MACs behind an ONU, and the whole chassis at once	SNMP	The whole-chassis read feeds Link Radius Server.

What you can do from RadixOLT

Every per-ONU write goes through the firmware’s one ONU action object over SNMP, staged and fired in a single request so two operators can never cross their targets.

Every write asks first, names the OLT and the ONU, and is recorded
Action	How	Notes
Reboot an ONU	SNMP	Refused for an ONU that is not online, since it could not hear the request.
Disable or enable an ONU	SNMP	Confirmed from the ONU’s phase state, which moves a few seconds after the write.
Delete an ONU	SNMP	Confirmed by the ONU disappearing from the chassis’s own table.
Save the running configuration	SNMP	Asks first: it makes permanent whatever the running config holds, including other people’s changes.

Not offered: authorizing ONUs. The V1600G chassis tested so far authorize what they hear on their own, so there was no waiting list to build against. With SNMP switched off there are no writes at all, rather than a guessed CLI form.

Commands one click away in the terminal

The command offered beside the live session. As on every V-SOL box, typing ? after a command runs it rather than only showing help.

show onu state

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.

The firmware answers columns its MIB does not declare

DBC’s MIB file has no last register time, last deregister time, deregister reason or alive time, and the chassis returns all four on every ONU anyway. Both were walked before anything was mapped, which is the only reason DBC got those columns rather than being written off from its own MIB.

Deregister reasons arrive in DBC’s own words

ONU Signal LOS, ONU PLOAM LOS, Manual Deactivate with two spaces. They are kept as the device wrote them, spacing tidied, because a fixed vocabulary would drop whatever it had not seen before.

The system uptime column is the wrong uptime

The per-ONU system uptime has gaps, reading N/A for some online ONUs, and counts power-on time rather than the PON session: one ONU read 2,156,790 seconds where its session was 425,201. RadixOLT reads the session time instead.

Columns are positioned with escape codes

show onu state and the MAC table place columns with ANSI cursor movements instead of spaces, so one row reaches a program as several lines. RadixOLT folds them back before reading a row; the output was captured byte for byte identical on DBC and Syrotech.

The CLI is fast, the session is the cost

The CLI dumps the whole fleet in well under a second, but the chassis allows one CLI login. Sweeping over SNMP is what keeps that login free for an engineer’s terminal.

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 SNMP with the read-write community
The community and the SNMP port. Under a read-only community the reads work and every write times out, which looks like a dead agent.
Give it a CLI login
Telnet or SSH, the port, a username and password, for the terminal and the fallback reads. Stored encrypted and never shown again.
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.