-
Problem report
-
Resolution: Fixed
-
Trivial
-
4.0.11, 4.2.5
-
Sprint 56 (Sep 2019), Sprint 55 (Aug 2019), Sprint 57 (Oct 2019), Sprint 58 (Nov 2019), Sprint 59 (Dec 2019), Sprint 60 (Jan 2020), Sprint 61 (Feb 2020), Sprint 62 (Mar 2020), Sprint 63 (Apr 2020), Sprint 64 (May 2020), Sprint 65 (Jun 2020)
-
0.5
Steps to reproduce:
- Configure a switch device with "Template Module Interfaces SNMPv2" template
- Wait for discovery and new triggers created
- Plug a temporary device on a port
- wait 30s
- Unplug the device
- Wait for the "Link down" problem to appear
Result:
You have now a "Problem" that is sticky with no other way to recover than reconnecting something to that switch port/
Expected:
Some way to easily reset the port status.
One easy way to provide that functionality is to change the following trigger recovery expression from :
{Template Module Interfaces SNMPv2:net.if.statusifOperStatus.{#SNMPINDEX}.last()}<>2
to
{Template Module Interfaces SNMPv2:net.if.statusifOperStatus.{#SNMPINDEX}.last()}<>2 or {Template Module Interfaces SNMPv2:net.if.statusifOperStatus.{#SNMPINDEX}.diff()}=0
So that one has to simply delete the history for that port to recover the problem.
Credit goes to @warpdan on the communities : https://www.zabbix.com/forum/zabbix-help/369997-problem-interface-link-down-manual-recover
