OLT monitoring software
Every ONU's optical signal read every five minutes, LOS alarms raised and cleared on their own, and each ONU matched to the subscriber behind it — so a failing line shows up as a customer's name before it shows up as a complaint, not as port 3, ONU 17 after one.
What it reads
An OLT's own web page tells you about the OLT. This tells you which subscribers a problem on it is about to reach.
Receive and transmit power for every ONU, and the optical readings of each PON port — so a line drifting towards trouble is visible days before it drops.
An alarm is opened when the signal crosses into trouble, raised in severity if it gets worse, and resolved when the reading recovers. Nobody has to tidy the list.
Every ten minutes the OLT's MAC table is compared with the PPPoE sessions on your routers, and each ONU is tied to the subscriber using it.
Uptime, CPU, memory and port traffic over SNMP. One poll lost over a lossy management link is not reported as an outage.
The OLT's uplink throughput recorded every five minutes, so you can see how full the pipe was at nine last night, not only how full it is now.
Somebody is told when a signal moves into a worse band — once. A marginal line that sits in the same band for a week does not send a message every five minutes.
From the panel
What a technician would otherwise do over telnet, done from the same panel as the subscriber record — and recorded against the person who did it.
ONUs waiting on a PON port are discovered and listed. Authorise one with a service profile and a subscriber, or reject it, from one screen.
A remote reboot for the customer on the phone, logged with who asked for it and why.
Read the OLT's log and its port and link states in the panel, next to the alarms they explain.
Which OLTs
Every reading here was checked against a real device before the panel was allowed to show it.
Running something else? Say which OLT when you ask for a demo. A brand is added from a device that has answered, not from a datasheet.
Questions
No. The polling only reads. Authorising, rejecting or rebooting an ONU happens when a person asks for it from the panel, and each is recorded.
Every five minutes, with the OLT itself polled every two. The matching of ONUs to subscribers runs every ten.
No. Alerts are sent when a line moves into a worse band, not for every reading in it — a weak link that stays weak tells you once.
It compares the MAC addresses the OLT sees on each ONU with the PPPoE sessions on your routers. Where those agree, the ONU is tied to that subscriber; you can also set it by hand when authorising a new ONU.
The rest of SKYNITY
Billing, the routers and the fibre share one set of records, so a payment, a package change or a failing ONU is the same fact everywhere it shows up.
Tell us how many subscribers, which routers and what packages, and the demo is set up the way you actually run.
Request a demoor email support@skynity.net
SKYNITY