eCloud OLT Controller — NMS & ACS

Platform

Everything between the OLT and the subscriber’s router, in one panel.

Eight modules working on the same data: the signal that monitoring measures feeds the forecasts, alerts know your outside plant, and the subscriber’s router sits on the same page as their fiber. For each module we also tell you what it doesn’t do yet.

Monitoring

Every ONU, every port, every uplink, with its history.

Optical power, traffic and OLT health as time series, read over SNMP or CLI depending on what each device exposes.

  • RX and TX power for every ONU, over SNMP or CLI. An impossible reading is discarded: a value is never made up.
  • Uplink, PON port and ONU traffic through standard IF-MIB, with 64-bit counters.
  • OLT CPU, temperature and uptime, with history and trend.
  • Extended optical monitoring (DDM/DOM): what the OLT receives from each ONU and each port’s optical module, with laser bias current, temperature and voltage.
  • SLA reports that separate availability from measurement coverage, exportable to CSV.
What it doesn’t do yet
  • Many OLTs don’t expose per-ONU traffic; in that case you see the port’s.
  • OLT memory is only read if its OID is loaded: no profile ships with it.
  • Extended optical monitoring is confirmed on the ZTE C320; other vendors don’t report upstream signal.
  • ONU distance and temperature show up only if the OLT reports them.
North OLT · ZTE C320 · port 1/2/3live
CPU 23 %Temperature 41 °CUptime 38 d 4 h
RX power · gpon-onu_1/2/3:14−19.2 dBmPort traffic · Gbps↓ 2.23 · ↑ 0.89

Demo data

Forecasts

The curve before the drop.

eCloud projects four series 90 days ahead and tells you when they will cross their threshold, and how confident it is.

  • RX power of every ONU.
  • Laser bias current of every PON port, as a percentage of the module’s maximum.
  • Uplink and PON port usage: daily 95th percentile against 80% of their speed.
  • Peak temperature of every OLT.
  • It also warns when an ONU drops 3 dB below its own 7-day history, even if it’s still above the threshold.
What it doesn’t do yet
  • Forecasts need at least 7 days of data: a newly connected network will show “no data” for the first weeks.
  • With low confidence the result is shown as uncertain, not as a date.
  • It’s recalculated every 6 hours: it’s for planning, not a replacement for real-time alerts.
threshold −27 dBmtoday−60 d+90 d
Forecast value−26.0 dBm
Threshold crossingin 46 days
Confidencehigh

In 30 days it’s still within range.

Demo data · recalculated every 6 h

Alerts & root cause

One notification per failure, not one per ONU.

When a port goes down, eCloud groups the affected ONUs and tells you the cause, not every symptom.

  • Over 20 alert types: OLT down or rebooted, ONU with no signal or low power, PON port or NAP down, uplink saturated or down, VPN tunnel down, optical module, overdue backup and more.
  • Root cause: VPN tunnel → OLT → port or NAP → ONU. Only the failing link is notified.
  • Escalation from warning to critical with a single re-notification, and automatic closing on recovery.
  • Thresholds editable live from the panel.
  • Notifications by Telegram, email or HMAC-SHA256 signed webhook.
  • Maintenance windows: alerts are logged but not notified, and that time doesn’t count against the SLA.
What it doesn’t do yet
  • There are no SMS or WhatsApp notifications.
  • The VPN tunnel as a cause applies only to OLTs connected through the built-in VPN.
  • The cause of each outage (LOS, dying gasp…) is shown only if the OLT reports it.
Simulate where the failure is
  1. VPN tunnelto the ISP’s MikroTikonline
  2. North OLTZTE C320online
  3. PON port 1/2/338 ONUscause
  4. NAP N-148 ONUsconsequence
  5. Subscriber ONU #20417gpon-onu_1/2/3:14consequence
Without correlation40 alertsone for each affected device
With root cause1 notificationPON port 1/2/3 down · 38 ONUs affected · cause: LOS
TelegramEmailSigned webhook

Provisioning

From the box to a live subscriber, without opening a terminal.

Authorize, move and replace ONUs from the panel, with preview and rollback. Field technicians work from their phones.

  • Expected ONUs: load the serial ahead of time and, when the ONU shows up, it’s authorized with your template.
  • Pre-authorization with the ports you already know.
  • Installer on the phone: barcode reading, live signal measurement and an installation record with GPS that can’t be edited.
  • Move to another port or replace the device: if the OLT rejects the change, it rolls back on its own.
  • Bulk actions with preview: up to 50 at once or up to 5,000 in the background, with a brake if an OLT rejects 3 in a row.
  • Reconciliation between the OLT and the inventory, without sending commands to the device.
What it doesn’t do yet
  • Your team writes and validates the authorization template for each OLT model.
  • Automatic authorization ships turned off: you turn it on once the template is tested.
  • The barcode reader depends on the browser: it works in Chrome for Android, not in Safari for iOS.
Installation · Subscriber #20533

ZTEGC8A31F20

Serial read from the ONU label

Demo data

ACS / TR-069

The subscriber’s WiFi, without a home visit.

Built-in ACS on top of GenieACS: the WiFi, connection and voice of the subscriber’s router, on the same page as their fiber.

  • WiFi: name, password and channel, on TR-098 and TR-181. Reboot and factory reset.
  • Internet: PPPoE username, password and VLAN.
  • Voice: the router’s SIP account (TR-104 v1).
  • Cross diagnosis: if the WiFi is fine and the optical power is falling, the problem is in the fiber.
  • WireGuard VPN to the ISP’s MikroTik (RouterOS 7.1 or later) to reach devices on private networks.
What it doesn’t do yet
  • It edits existing WAN connections; it doesn’t create new ones.
  • TR-104 v2 is not supported.
  • VLAN on TR-098 depends on the router vendor exposing it.
Subscriber router #20417 · ZTE F670Lonline
Fiber: RX −24.6 dBm · fallingWiFi: RSSI −52 dBm · stable

Demo data · reboot and factory reset too

Firmware

Update hundreds of devices without staying up all night.

OLTs, ONUs and subscriber routers, in scheduled batches, with a verified image and a brake that pauses the batch if something goes wrong.

  • OLT over SSH: the OLT downloads the image over TFTP, FTP, HTTP or HTTPS.
  • ONU through the OLT (OMCI), and subscriber router over TR-069.
  • Image verified with SHA-256, and a compatible model is required.
  • Batches of up to 200 devices, with a time window in your local time and controlled parallelism.
  • Automatic brake: if failures reach √n (minimum 2), the batch pauses. What’s in progress finishes and nothing else starts.
What it doesn’t do yet
  • Update commands are loaded per device model: they don’t come out of the box.
  • The brake pauses; it doesn’t roll back what was already updated.
  • Some OLTs don’t report the ONU firmware version (for example, ZTE C320 V2.1.0).
Updated0
Failed0 / 11
Not started120

Simulation with random failures · time window and parallelism are configurable

FTTx maps

Your outside plant, drawn and live.

Cables, closures, splitters, NAP boxes and poles on the map, with every ONU’s status on top.

  • Plant editor: 1 to 288 fiber cables, closures, 1:2 to 1:64 splitters and poles.
  • Coverage and occupancy of every NAP box, and ONUs down per NAP.
  • Network status on the map, refreshed every minute.
  • Live topology, from the OLT to the subscriber.
  • Import from Excel or CSV.
What it doesn’t do yet
  • Only items with coordinates show up on the map.
NAP N-1412 of 16 ports in use1 ONU down

Tap a NAP box · demo data

Integrations & API

Let your billing suspend and reconnect on its own.

Connect your billing system and automate suspensions and reconnections, with a brake that prevents mass cut-offs by mistake.

  • WispHub: instant notifications and periodic review.
  • Mikrowisp: periodic review.
  • eCloud-ISP: instant notifications.
  • Brake: nothing is suspended if a review asks to cut off more than 10 ONUs or more than 10%.
  • Public API to check, suspend and reactivate contracts, with API keys.
  • Signed webhooks for alerts, OLT status changes, authorized ONUs and maintenance.
What it doesn’t do yet
  • Mikrowisp has no webhooks: the cut-off happens at the next review, not instantly.
  • The OpenAPI docs are generated automatically; most routes don’t have a written description yet.
WispHubInstant notifications + periodic review
MikrowispPeriodic review
eCloud-ISPInstant notifications
6 ONUs are suspended on the OLTBelow the limit of 10 ONUs and 10%.
Signed webhooks (HMAC-SHA256)
alerta.creadaalerta.resueltaolt.estado_cambiadoonu.autorizadaonu.perfil_cambiadomantenimiento.iniciado

Simulation · example operator with 300 ONUs

Compatibility

How well tested each vendor is.

We tell you the real level of each profile. “Validated” means it runs in production with a customer’s OLT; “profile included” means support is written and gets tuned with your team during onboarding.

VendorModelsLevelDetails
ZTEC320 (V2.1.0)Validated in productionIn production with real customers.
ZTEC300, C600Profile includedProfile included; OIDs are confirmed per firmware.
HuaweiMA5608T, MA5683T, MA5800Profile includedProfile included; OIDs are confirmed per firmware.
V-SOLV1600G (GPON), V1600D (EPON)Profile includedProfile included; the OLT’s OIDs are loaded during onboarding.
C-DataFD12xx and FD13xx (EPON), FD16xx (GPON)Profile includedProfile included; not yet validated against a real device.
Any OLTGeneric SNMPMonitoring onlyReachability, uptime, traffic and SLA. No provisioning.

See the per-vendor detail →

Also included

What you don’t see, keeping operations safe.

  • Isolated multi-tenancyEach ISP sees only its own data: isolation lives in the database, with PostgreSQL Row-Level Security.
  • Strong sign-inTwo-factor authentication (TOTP) and passkeys, with sign-in attempt limits.
  • Encrypted credentialsYour OLT passwords are stored encrypted with AES-256-GCM. The audit log exports to CSV.
  • Configuration backupsOn OLTs whose profile supports it, the configuration is backed up when they’re added and, if you enable it, on a schedule.
  • Signed updatesEach new version arrives signed, is applied now or at the time you choose, and you can roll back.
  • On the phoneThe panel installs as an app on the technician’s phone.
  • Knowledge baseOver 170 articles with procedures for V-SOL, ZTE, Huawei, C-Data and HALNy ONTs.
  • Read-only explorersQuery an OLT’s CLI and SNMP from the panel, with no risk of changing anything.

Fewer trucks on the street. More subscribers who stay.

We’ll walk you through eCloud OLT Controller with your own OLTs, in 30 minutes.

Watch the prediction again