Problems encountered in using Zabbix: SNMP monitoring port traffic occasionally breaks the graph

When monitoring port traffic using Zabbix SNMP mode, a graph is always intermittent (the monitored device has a large port traffic), and there are often problems with no images in a few minutes.

This is because the item is using the ifinoctets(OID:1.3.6.1.2.1.2.2.1.10) in the MIB and Ifoutoctets(OID:1.3.6.1.2.1.2.2.1.16) as the basis for obtaining port traffic. It represents the total amount of data that an interface flows into or out.

Here's an explanation, because the value we get is the total amount of data, so when we set the item , we use the difference between the previous and the two times to divide the time to obtain an interface rate. When a Zabbix is given a difference of less than or equal to 0 , the value is considered to be incorrect.

However, the data type of the two OID is the first, the maximum value that can be represented is 2^32BYTE=4GB, which is a cumulative value that can be easily exceeded. When the value of the device is accumulated to 4GB , it will clear 0and then accumulate again.

Then, due to the difference in value after 0 (the difference is less than 0), there will be a case of a broken graph.

To solve this problem, you need to change the OID value used to ifhcinoctets (1.3.6.1.2.1.31.1.1.1.6) and ifhcoutoctets ( 1.3.6.1.2.1.31.1.1.1.10), the data type of these two OIDs is in the number of bits, the maximum value that can be represented is 2^64BYTE=16777216TB, It is almost impossible to break the picture again.

Everyone in the Zabbix template to the value of the OID to change to the top of the 64-bit is good ^ ^

Problems encountered in using Zabbix: SNMP monitoring port traffic occasionally breaks the graph