linuser/zabbix-network-topology v5.3.1

v5.3.1 — Network Topology for Zabbix

on GitHub

A maintenance release: fixes, one small addition, and a template update. Full detail in the CHANGELOG.

Updating — one template to re-import

No action was added or renamed, so no rescan: replace the network_topology directory, chown, reload php-fpm. Reload the page once with a cache bypass — the bundle changed.

Templates: nt_lldp_snmp changed

Re-import templates/nt_lldp_snmp_template.yaml with Update existing ticked for discovery rules and item prototypes. It makes LLDP discovery work on switches that omit the TimeMark from the neighbour index; on every other device it changes nothing. nt_health_score and nt_topology_change are unchanged.

UniFi: one item to add yourself

If you monitor UniFi through the official UniFi Network API templates: only their Client template carries uplink.id. For edges between switches, access points and the gateway, add a dependent item uplink.id on details.json with JSONPath $.uplink.deviceId to the UniFi Network API - Device template. Details in LLDP-SETUP.md.

Fixed — worth updating for

• Installation failed on Apache with mod_php (#13). nt-install.sh looked for PHP-FPM only and aborted before copying a single file — on exactly the setup the distribution's zabbix-frontend-php package gives you.
• LLDP discovery found nothing on TP-Link JetStream (#15). The switches omit the TimeMark from the neighbour index; discovery and all six item prototypes required it and dropped every row without an error.
• UniFi edges could never appear. uplink.id was missing from the item search — in the hop view as well. Making it safe also meant teaching the classification that reporting an uplink does not make a phone a switch.
• The port names announced in 5.3.0 never appeared. ifName, ifDescr and ifAlias were never fetched.
• The items table disappeared on very large counter values instead of formatting them.

Numbers that were wrong

• Memory never showed for SNMP hosts — the storage-type OID was destroyed by a numeric cast.
• Multi-core CPU load was halved instead of averaged.
• Synology showed 99 % CPU permanently.
• The tooltip sparkline read eight times the edge value for the common net.if.in[ifHC…] keys.

Map, panels, reports

• A host's only Disaster could be missing from its problem list.
• A red "down" count appeared on perfectly healthy links; the tooltip now shows the same ratio the edge color uses. (r/zabbix)
• Cluster mode discarded saved positions without saying so — now it says so, once. (r/zabbix)
• Positions arranged in the hop view were lost on reload.
• Reports counted host groups as hosts in Group View.
• Severity is no longer carried by color alone: ring width and notches carry it too.
• Smaller: a late refresh could draw the map over the Table tab, the items view could hang on its spinner in hop mode, wallboards leaked toolbar listeners, the port scan called every IPv6 host closed, and a host naming itself got a loop edge.

Added

• The confidence score sanity-checks round-trip times, and MNDP counts as its own source. The check only ever deducts, only on gaps ICMP deprioritisation cannot explain, and stays silent across different proxies and proxy groups.

Thanks

@lechu2375 for #15: the cause, the walk that proves it, a fix for both layers, and the note that fixing only the first would leave every item empty — tested on two switches before he sent it.