Wir nutzen Cookies, um Ihnen eine optimale Nutzung dieser Webseite zu ermöglichen. Mehr Informationen finden Sie im Datenschutzhinweis. Wir nehmen an, dass Sie damit einverstanden sind, falls Sie diese Webseite weiter besuchen.

Ihre Cookie-Einstellungen
Ihre Einstellungen wurden aktualisiert.
Damit die Änderungen wirksam werden, löschen Sie bitte Ihre Browser-Cookies und den Cache und laden dann die Seite neu.

Check manual page of if64

Checkmk Manual

Auf dieser Seite

Suche im Handbuch

Monitor Network Interfaces via Standard MIB Using 64-Bit Counters

Distribution: official part of Check_MK
License: GPL
Supported Agents: SNMP

This check does the same as if but uses 64-bit counters from the IF-MIB . This allows to correctly monitor switch ports with a traffic of more then 2GB per check interval.

Also, this check can use ifAlias instead if ifDescr for retrieving the admin-configured interface description. This is useful e.g. for HP ProCurve switches which do not show that aliasses in ifDescr.

Note: This check needs SNMP v2c and thus only works if your hosts are added to bulkwalk_hosts.

Depending on the check parameters, this check can go WARN or CRIT when the port status changes (i.e. is down), when the link speed changes (e.g. a port expected to be set to 1 GBit/s operates only at 100 MBit/s), when the absolute or procentual traffic of a port exceeds certain levels or if the rate of errors or discards exceeds configurable limits.

This check supports averaging the in- and outgoing traffic over a configurable time range by using an exponentially weighted moving average - just as Linux does for the CPU load averages. The averaging can be configured on a per-host and per-interface base. Interfaces with averaging turned on yield two additional performance values: the averaged in- and outgoing traffic in bytes. If you have configured traffic levels, then those levels are applied to the averaged values.

Note that there are some devices with broken firmware which report that they support 64-bit counters even though they do not. In such cases, you can use the rule "Hosts forced to use 'if' instead of 'if64'" to enforce the usage of the 32-bit interface check.


There are three allowed ways to specify an interface: its index ifIndex, its description ifDescr and its alias ifAlias.


One service is created for each interface that fulfills configurable conditions (rule "Network interface and switch port discovery"). By default, these are interfaces which are currently found up and are of type 6, 32, 62, 117, 127, 128, 129, 180, 181, 182, 205 or 229.

Grouping: In some situations, you do not want to monitor a single interface but a group of interfaces that together form a pool. This check supports such pools by defining groups. The data of all members is accumulated and put together in a single grouped interface service.