This template allows you to quickly get up and running with monitoring of Ubiquiti's EdgeRouter line of devices. It allows for auto-discovering of network interfaces and automatically applies some triggers for the discovered network interfaces. Many more triggers are included but disabled by default. It also includes a modifed version of the default template "Generic by SNMP" to add graphs for packet loss and response time.
- Select a branch according to your Zabbix version and download the xml.
- Import zbx_edgemax_template.xml to Zabbix (Configuration -> Templates -> Import)
- Add the template EdgeMAX SNMPv2 to your host and configure
- Add {$SNMP_COMMUNITY} to your host's macros and configure it. (default is usually public)
- Enable the SNMP agent on your EdgeMAX device.
- Set SNMP community to the same value as your macro or the other way around.
- ✔️ Monitoring of memory utiliziation of system
- ✔️ Monitoring of CPU load
- ✔️ Auto discovering of network interfaces
- ✔️ Monitoring address per network interface
- ✔️ Monitoring traffic in/out per network interface
- ✔️ Monitoring up/down status per network interface
⚠️ Monitoring link speed per network interface (see issues)- 🔶 Linked with Generic by SNMP (now included).
Items with checks are enable by default. Those with Xs are disabled by default. You can customise your triggers to your needs per network interfaces.
From linked template:
- ✅ High ping loss
- ✅ High response time
- ✅ Host has been restarted
- ✅ No SNMP data
- ✅ System name has changed
- ✅ Unavailable by ping
From this template:
- ✅ High memory usage
- ✅ High system load
- ✅ Interface address has changed
- ✅ Interface status has changed
- ❎ Interface is not up (1)
This should work with all EdgeRouters. Partial compatibility with Edgeswitches.
Updated as of 2023-11-08.
-
EdgeRouter
- ER-X
- ER-4 (Reported by notfixingit3)
- ER-5 ( + poe)
- ER-6 ( + poe)
- ER-12P (Reported by andymarden)
- ER-Pro (Reported by notfixingit3)
-
EdgeSwitch
- ES-10XP
- Wrong ethernet link status/speed via SNMP (some of this issue is due to how ubiquiti is treating "standard" SNMP OIDs. The link status should be fixed but the speed is still troublesome)