[ZBX-13129] Template Module Interface high bandwidth usage should check for available speed Created: 2017 Dec 02  Updated: 2024 Apr 10  Resolved: 2017 Dec 03

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 3.4.3
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Joakim Plate Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Team: Team D

 Description   

Steps to reproduce:
Use Template Module Interface (Simple) SNMPx against router with vpn connections

Result:
Trigger like: "Interface tun15: High bandwidth usage >95%" is triggered for interfaces with no speed defined.

Expected:
Either

  • Trigger for high bandwidth usage is either not created by discovery for items without a maximum speed
  • Trigger contains check for maxspeed > 0 in problem expression
  • An option to set an explicit maximum speed by macros.

 Comments   
Comment by Vitaly Zhuravlev [ 2017 Dec 03 ]

I think speed is defined , but might be less than your interface can really handle. Please tell me what it is? 

net.if.speed[ifHighSpeed.{#SNMPINDEX}]
Comment by Vitaly Zhuravlev [ 2017 Dec 03 ]

Trigger contains check for maxspeed > 0 in problem expression

This check is alredy in the expression:

({Template Module Interfaces SNMPv2:net.if.in[ifHCInOctets.{#SNMPINDEX}].avg(15m)}>({$IF_UTIL_MAX:"{#IFNAME}"}/100)*{Template Module Interfaces SNMPv2:net.if.speed[ifHighSpeed.{#SNMPINDEX}].last()} or
{Template Module Interfaces SNMPv2:net.if.out[ifHCOutOctets.{#SNMPINDEX}].avg(15m)}>({$IF_UTIL_MAX:"{#IFNAME}"}/100)*{Template Module Interfaces SNMPv2:net.if.speed[ifHighSpeed.{#SNMPINDEX}].last()}) and
{Template Module Interfaces SNMPv2:net.if.speed[ifHighSpeed.{#SNMPINDEX}].last()}>0
Comment by Joakim Plate [ 2017 Dec 03 ]

Seems this was resolved in 3.4.2 update. My templates are from 3.4.0 release. I missed that in my due diligigence. Issue can be closed.

Comment by Joakim Plate [ 2017 Dec 03 ]

Was already fixed in one of the 3.4.x bugfix releases

Generated at Sun Jun 07 04:01:17 EEST 2026 using Jira 10.3.18#10030018-sha1:5642e4ad348b6c2a83ebdba689d04763a2393cab.