So I recently upgraded my zabbix server and proxies from 4.0.4 to 4.3.2, and after upgrading the server, I was immediately greeted with thousands of trigger warnings, all from devices that use the template "Template Module Interfaces SNMPv2".
The problems were "High Bandwidth usage" and "High Error Rate".
It seems the "Template Module Interfaces SNMPv2" had some changes, although I could not find anything on the zabbix release and upgrade notes.
"High Bandwidth usage" clears itself after the next "Network Interface" discovery which is done every hour by default.
But "High Error Rate" did not clear itself up after discovery although values went from 5 or 3 to 0 after the discovery process finished.
Problem is the trigger definition from "High Bandwidth usage" that says trigger if value > $IF_ERRORS_WARN and recover if value < $IF_ERRORS_WARN -2.
By default, $IF_ERRORS_WARN is "2", so $IF_ERRORS_WARN - 2 = 0 but 0 is not < 0 and you can't get negative error rates.reverse phone lookup
So you can either change $IF_ERRORS_WARN to 3, or change the trigger recovery from "< $IF_ERRORS_WARN -2" to "<= $IF_ERRORS_WARN -2). Otherwise the trigger will never recover.
After making either of these changes, wait for the next Network Interface Discovery and the problems will clear up.
The problems were "High Bandwidth usage" and "High Error Rate".
It seems the "Template Module Interfaces SNMPv2" had some changes, although I could not find anything on the zabbix release and upgrade notes.
"High Bandwidth usage" clears itself after the next "Network Interface" discovery which is done every hour by default.
But "High Error Rate" did not clear itself up after discovery although values went from 5 or 3 to 0 after the discovery process finished.
Problem is the trigger definition from "High Bandwidth usage" that says trigger if value > $IF_ERRORS_WARN and recover if value < $IF_ERRORS_WARN -2.
By default, $IF_ERRORS_WARN is "2", so $IF_ERRORS_WARN - 2 = 0 but 0 is not < 0 and you can't get negative error rates.reverse phone lookup
So you can either change $IF_ERRORS_WARN to 3, or change the trigger recovery from "< $IF_ERRORS_WARN -2" to "<= $IF_ERRORS_WARN -2). Otherwise the trigger will never recover.
After making either of these changes, wait for the next Network Interface Discovery and the problems will clear up.