Netxol NMM vs Zabbix for ISPs: monitoring platform vs. ISP operating layer
Zabbix is a first-class general-purpose monitoring platform. It is also not an ISP tool. Here is what changes when you evaluate NMM for an FTTH network.
Zabbix is one of the finest general-purpose monitoring platforms ever built. It also shows up regularly on ISP evaluation shortlists, alongside Netxol NMM. Both can watch a network. Only one is designed for an ISP's operating loop.
Zabbix is a mature, open-source, enterprise-grade monitoring product with agents on every OS, a robust template system, custom trigger language, and a dedicated user community. If you are monitoring servers, databases, applications and a network in parallel, Zabbix is a defensible choice. But it does not know what an OLT, an ONT, an ACS or a subscriber is.
The material differences for an FTTH operator
| Metric | Before | After | Δ |
|---|---|---|---|
| ISP-native primitives (OLT / ONT / subscriber / plan) | Zabbix · none — generic host / item / trigger | Netxol NMM · first-class | — |
| Multi-vendor OLT abstraction | Zabbix · custom SNMP templates per vendor | Netxol NMM · vendor-neutral adapter framework | — |
| TR-069 / TR-369 ACS | Zabbix · none | Netxol NMM · shipping | — |
| Zero-touch CPE activation | Zabbix · none | Netxol NMM · shipping | — |
| RADIUS server | Zabbix · none | Netxol NMM · included | — |
| Optical Tx/Rx power thresholds per ONT | Zabbix · custom SNMP + custom template per vendor | Netxol NMM · shipping across every supported OLT | — |
| Customer-impact analysis (which subscribers are down) | Zabbix · none — no subscriber model | Netxol · every alarm names affected customers | — |
| Deployment | Zabbix · self-hosted server + DB + frontend + proxies | Netxol Core appliance · pre-installed | — |
What Zabbix does that NMM does not try to
Zabbix is optimised to watch anything — a Kubernetes cluster, an Oracle database, a fleet of Windows servers. NMM is deliberately focused on the ISP world: OLT, ONT, CPE, subscriber, service, plan, invoice. If your organisation runs a mixed IT + ISP infrastructure and you need one tool for everything, keep Zabbix for the IT side and consider NMM for the FTTH side.
The operating-loop test
Ask this: when your NOC engineer sees an alarm, can they see the affected subscribers, credit their invoices, silence the reminder SMSes and file the incident, without opening a second tool? On Zabbix the answer is no. On Netxol it is yes — because CRM, Billing and NMM share the graph.
Where the operating loop actually lives
Zabbix trigger, action and escalation are powerful for pure monitoring, but they do not know what a subscriber is. That means an operating loop that includes billing suspension or CoA on plan change has to be built by the operator with external scripts. Netxol NMM ships the loop closed — plan change in CRM triggers a CoA to the correct BNG; non-payment triggers session termination; restoration on payment is symmetric. See the [Netxol NMM module](/products/modules/nmm).
Zabbix
Alarm to ticket integration
Requires external ITSM
Netxol
Alarm to ticket integration
CRM shares the graph — built-in
Zabbix
Plan change to RADIUS CoA
External script
Netxol
Plan change to RADIUS CoA
Automatic on the graph
Coexistence with Zabbix
Zabbix and Netxol NMM can coexist: keep Zabbix for the enterprise IT surface (servers, Windows, VMware) and adopt Netxol NMM for the access and core FTTH network. Netxol Open APIs let Zabbix continue receiving normalised alarms from the ISP side — see the internal [Netxol AI Operating System post](/blog/ai-operating-system-for-isps) for the platform framing.