Detecting Partial PON Port Failures Before Customers Call
Detecting Partial PON Port Failures Before Customers Call
Why Partial PON Down Matters
When a PON port goes fully down, the problem is clear: everyone on that port is offline, and operators rush to fix it. But what happens when only a subset of ONUs connected to that port go dark? The OLT still reports the PON as up, yet dozens of customers may already be suffering connectivity issues. That’s what we call a Partial PON Port Down—and until now, most operators had no easy way of detecting it.
With our latest update, NetSense NMS introduces Partial PON Port Down detection.
Business Benefits
For ISPs, customer experience hinges on speed: the faster an outage is identified, the less frustration builds up in your call center and on social media.
A partial outage often points to a fiber cut or splitter issue, affecting more than one subscriber. If treated like an isolated single-customer fault, troubleshooting gets bogged down—support staff waste time rebooting routers or escalating tickets, while the real problem remains hidden.
By surfacing a Partial Down alert right inside NetSense NMS, support teams can immediately understand:
- This is not just one customer’s problem
- It’s a broader issue affecting a group of subscribers on the same PON branch
- Action is required as urgently as with a full PON Down
This clarity translates directly into faster resolutions, fewer unnecessary truck rolls, and a smoother customer experience.
How It Works
The new alert relies on NetSense NMS’s ability to classify ONU down reasons. Specifically:
- ONUs that go offline due to dying gasp (loss of power at the customer premises) are ignored.
- ONUs that go offline without dying gasp signals are counted as potential fiber-related issues.
- When the number of such ONUs crosses a configured threshold (absolute value or percentage), NetSense-NMS raises a Partial PON Port Down alert.
The logic ensures you’re only alerted for real network-side problems, not scattered power cuts at customer homes.
Because not all OLT vendors and models report down reasons consistently, we’ve also built in flexibility: operators can exclude specific OLT manufacturers or models from the Partial Down alert definition. This way, your alerts remain actionable and precise, even in a mixed-vendor environment.
Putting It Into Action
With this feature, your call center agents and field engineers now have a crucial piece of visibility:
- They’ll know right away when a cluster of customers is impacted.
- They won’t waste time treating the issue as isolated.
- They can escalate to fiber teams immediately, shortening time-to-repair.
And your customers? They’ll notice the difference in how quickly issues are addressed—long before frustration sets in.
From Our Changelog
Partial PON Port DOWN Alert - An absolute number of the DOWN ONUs or ONUs DOWN not because of dying gasp can be configured against a baseline. When the baseline is breached - alert will be created. When the number of the DOWN ONUs with the preselected criteria is not breaching the threshold and there is an alert - it will be closed.
👉 This feature is now available in NetSense NMS. If you’re running fiber access networks, Partial PON Down detection could be the difference between chasing symptoms and fixing root causes—fast.
Frequently Asked Questions
- What is a partial PON port failure?
- A partial PON port failure ("partial PON down") is when only a subset of the ONUs on a PON port go offline while the OLT still reports the PON port as up. Often caused by a secondary splitter cut or a branch fiber break, it can leave dozens of customers offline while legacy monitoring tools show the port as healthy and UP.
- Why are partial PON failures so easy to miss?
- Because the OLT reports the port as up, most tools only flag a full port-down event. The affected customers look like unrelated single-subscriber faults, so staff waste time rebooting routers and escalating individual tickets while the real branch-level fiber problem stays hidden.
- How does NetSense detect a partial PON down?
- It classifies ONU down reasons: ONUs sending a dying gasp (power loss at the home) are ignored, while ONUs that go offline without a dying gasp are counted as potential fiber faults. When their number on a port crosses a configured threshold (absolute count or percentage), NetSense raises a Partial PON Port Down alert - so you're only alerted for genuine network-side problems.
- How does partial PON detection reduce truck rolls?
- It tells support immediately that a cluster of customers on the same PON branch is affected - not one isolated subscriber - so they escalate straight to the fiber team instead of dispatching technicians or rebooting CPEs one by one, shortening time-to-repair.
- Does it work in mixed-vendor OLT environments?
- Yes. Because vendors report down reasons inconsistently, operators can exclude specific manufacturers or models from the partial-down alert definition, keeping alerts accurate across a multi-vendor network.