Shulou(Shulou.com)06/02 Report--

Zabbix server 4.0 monitors the Graphs of server or switch interface traffic on and off.

Questions such as screenshots:

1. There will be problems when drawing more than 200m [this is the case]; there are more than 400m and 700m on the Internet, it doesn't matter, the problem is the same.

Problem analysis:

1. The tools used are Getif and SNMPWALK

2.zabbix monitors the SNMP protocol used by the switch. The default monitoring template is:

IfInOctets OID:.1.3.6.1.2.1.2.2.1.10 [port receives traffic MIB information] ifOutOctets OID:.1.3.6.1.2.1.2.2.1.16 [port sends traffic MIB information]

Snmpwalk-v 2c-c public 172.184.2.4 1.3.6.1.2.1.2.2.2.1.1.10 equals snmpwalk-v 2c-c public 172.184.2.4 ifinOctets

Principle: snmp counter mechanism, if overflowed, then clear 0 re-record.

In addition, in the case of count32, the maximum supported value is 2 ^ 32 = 4G, that is, if it exceeds 4G, the switch snmp counter automatically overflows and then recounts from 0. Then, because the difference calculated after zero is incorrect, the graph will be broken.

Solution:

Replace the following two parameters and OID values in the zabbix template:

IfInOctets OID:.1.3.6.1.2.1.2.2.1.10 [port receives traffic MIB information] ifOutOctets OID:.1.3.6.1.2.1.2.2.1.16 [port sends traffic MIB information]

To be replaced by:

IfHCInOctets is Counter64 [OID:1.3.6.1.2.1.31.1.1.1.6]

IfHCOutOctets is Counter64 [OID:1.3.6.1.2.1.31.1.1.1.10]

If you replace it with a 64-bit data type, it is almost impossible to break the graph.

Repair effect

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.