Used Bandwidth rule potential bug

[nathanIQ]

CMK version : 16
*OS version : Ubuntu 22.04.3

** Speed: 200 GBit/s, In: 72.5 GB/s (warn/crit at 17.5 GB/s/20.0 GB/s) (289.84%)CRIT , Out: 9.99 GB/s (39.96%)**

Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins)
cmk --debug -vvn QFX5120-JAX2.txt (606.4 KB)
Attached output from command. Attached screenshot of rule set applied to this interface

Seeing the check report in both GB and Gbit, not sure if this is a bug. It is causing some false alarms in our monitoring. Has anyone come across this before?

[zsuperben (Benjamin Godard)]

Hi,
I’m having the same issue with a Cisco nexus9000 switch.
nexus9000.txt (18.8 KB)

Is it something wrong in our config or is it an issue with check mk ?

Thank you !

[andreas-doehler (Andreas)]

For this problem one important question is the following one.
Is in your system a rule defined for “Fetch intervals for SNMP sections”, if yes please disable this rules and check again if the shown values are correct.
The fetch interval should only be defined for non rate checks that only say a status.
If you define such a rule for rate checks than you need to define a greater check interval for your check_mk service on these hosts.

[nathanIQ]

We do not have this rule defined/applied in any way