Iftrafic64 CRITICAL

metrics
director
icinga2
icingaweb2

(Nikita) #21

Well, I’m waiting for the results from you.


(Michael Friedrich) #22

Sorry to jump in, where are we heading here?


(Nikita) #23

Sorry, the difficulty of translation, did not understand you.


(Michael Friedrich) #24

@Wolfgang said, that the log output doesn’t conform with the snippets shown in the OP. There’s no further action “required” by him.

You’re saying you are waiting for this result.

This seems like a deadlock to me.

I’d suggest to dig deeper and provide the corresponding correct outputs.


(Nikita) #25

The results do not meet the requirements, because the journal is new results, and those are old ones. Values are not always the same.


#26

CRITICAL - IN bandwidth (12498.62%) too high|inUsage=12498.62%;85;98 outUsage=0.00%;85;98 inBandwidth=15623277779.91B outBandwidth=0.00B inAbsolut=1409272136c outAbsolut=312483901191

This plugin output contains “output” and “performance data” which is showing bandwidth and absolute values.

-->"OK - Average IN: 2.72MB (2.18%), Average OUT: 3.03MB (2.42%)Total RX: 205.72GBytes, Total TX: 758.42GBytes","hard_state"
-->"CRITICAL - OUT bandwidth (7378697629484.44%) too high","hard_state"
-->"[ 1/2 ] CRITICAL - OUT bandwidth (245956572989.93%) too high","soft_state"

-->"OK - Average IN: 4.96MB (3.97%), Average OUT: 4.68MB (3.74%)Total RX: 187.66GBytes, Total TX: 754.11GBytes","hard_state"
-->"2","CRITICAL - OUT bandwidth (14757395258972.17%) too high","hard_state"
-->"2","[ 1/2 ] CRITICAL - OUT bandwidth (245956572991.45%) too high","soft_state"
-->"0","OK - Average IN: 2.80MB (2.24%), Average OUT: 3.18MB (2.54%)Total RX: 182.91GBytes, Total TX: 749.77GBytes","hard_state"
-->,"CRITICAL - OUT bandwidth (14757395258972.94%) too high","hard_state"

This snippet shows “hard_state” and “soft_state” output without state values in the first part, whereas the second shows “2”, resp. “0” as state values.
Having a different structure within one piece of output seems odd.

To separate output of several plugin runs is left to the reader.


(Nikita) #27

I need to perform a check from the console and provide a report?


#28

Depending on your setup you might have a (mysql) database which contains check results / performance data so you could extract the data.

You mentioned that the state switches between error and non-error every eight minutes. So far you haven’t provided information showing that and the relevant values of that period to get a feeling what might be the reason.
We have no access to your system so we have to rely on the data you deliver. If it’s insufficient then the answers are wild guesses at best.

Executing checks over a period of time including a state switch and collecting the output is one option.


(Nikita) #29

Hey, I’m sorry I’m missing. I’ve been performing the team for 5 minutes, and it turns out that there’s no regularity in traffic, it just jumps.

https://pastebin.com/7BAzhrbT - here the results

I also found that you can draw debug

/usr/lib/nagios/plugins# ./check_iftraffic64.pl -H 192.168.20.1 -C publ -i 28 -u m -b 10000 -I 10000 -O 10000 -M 10000 -d 4
DEBUG ENABLED at level: 4
INTERFACE DESCR: 28
UNIT: m
BYTE COUNTER max_value: 10000000000
SNMP:
	ver: 2
	community: publ
	port: 161
USING INT#: 28
OID's:
	IfOperStatus: 1.3.6.1.2.1.2.2.1.8.28
	IfSpeed: 1.3.6.1.2.1.31.1.1.1.15.28
	IfSpeed32: 1.3.6.1.2.1.2.2.1.5.28
	InOctets: 1.3.6.1.2.1.31.1.1.1.6.28
	InOctets32: 1.3.6.1.2.1.2.2.1.10.28
	OutOctets: 1.3.6.1.2.1.31.1.1.1.10.28
	OutOctets32: 1.3.6.1.2.1.2.2.1.16.28
RESULTS:
	Operational Status: 1
	Interface Speed (64bit): 10000 Mbits
	Interface Speed (32bit): 10000 bits
	In Bytes (64bit): 18446743706214385045
	In Bytes (32bit): 1872020885
	Out Bytes (64bit): 1175715479979
	Out Bytes (32bit): 3189408171
USING 64 THEN 32 bit VALUES:
	Using 64bit in bytes value: 18446743706214385045
	Using 64bit out bytes value: 1175715479979
UNITS: B
Interface speed calculated as: 1250000000 B
Interface speed OUT: 1250000000 B
CURRENT timestamp: 1516280694
FILE PATH: /tmp/192.168.20.1_if-28
READ FROM FILE:
	last time: 1516280691
	last in bytes: -367897872945
	last out bytes: 1175005199713

WRITTEN TO FILE:
	time: 1516280694
	in_bytes: 18446743706214385045
	out bytes: 1175715479979
in_traffic: 6148914691370753024.00
out_traffic: 236760088.67
iface_speed: 1250000000 B
in_traffic: 6148914691370753024.00
out_traffic: 236760088.67
OUTPUT:
	label: Bytes
	in_tot: 18446743706214385045
	out_tot: 1175715479979
	in_ave: 6148914691370753024.00
	out_ave: 236760088.67
	in_ave_pct: 491913175309.66
	out_ave_pct: 18.94
	in_bytes_abs: 18446743706214385045
	out_bytes_abs: 1175715479979

CRITICAL - IN bandwidth (491913175309.66%) too high|inUsage=491913175309.66%;85;98 outUsage=18.94%;85;98 inBandwidth=6148914691370753024.00B outBandwidth=236760088.67B inAbsolut=18446743706214385045c outAbsolut=1175715479979c

#30

Looking at these very huge values I’d try to reset the interface and restart measurement.
Even having a 10 Gb interface the value 18.446.743.706.214.385.045 seems to takes about 1.844.674.370 seconds to build up. That’s several DECADES of years!


(Nikita) #31

When I write on the line clear counts Immediately the values are stable first minutes 5


#32

So probably your interface is malfunctioning.


(Nikita) #33

It turns out a funny thing, 1 switch is DGS-1210-28X / TE, so we play ports 5, and 10 G and 1G. And the second DGS-1210-28 / TE and there 1 port gives such data.