[j-nsp] MRTG and ATM interfaces
Kevin Vuong
juniper-nsp at nivek.us
Fri May 21 11:18:18 EDT 2004
Hi all,
I am pointing MRTG at my first Juniper (M10i running 6.1R2.2) and I was
wondering if anyone else has had any issues with it. I am running into a
problem where my ATM interfaces start to flatline for a few hours then come
back with normal graph data. The deltas in the mrtg .log files seem to be
terribly inflated causing it to be ignored by MRTG's MaxBytes.
i.e.
Gigabit Interface (this one's working fine)
1085150833 30091877001 14239736165
1085150535 29967336655 14184379972
---------------------------------------------
298 secs 124540346 in 55356193 out
b/s: 417920.624161074 185759.036912752
B/s: 52240.0780201342 23219.879614094
MRTG .log file entry : 1085150833 417921 185759 417921 185759
So the numbers match up there.
ATM interface (not working)
1085151734 814289676 4093188060
1085151434 813643725 4089949443
---------------------------------------------
300 secs 645951 in 3238617 out
b/s: 2153.17 10795.39
B/s: 269.14625 1349.42375
The MaxBytes is 1496.0 bits/s for this ADSL circuit. Since this measurement
exceeds the MaxBytes, MRTG ignores it and takes the previous value instead.
Here is a mrtg .log for one of the ATM subinterfaces that is flatlining.
1085151734 814289676 4093188060
1085151734 92 155 92 155
1085151434 92 155 92 155
1085151300 92 155 92 155
1085151000 92 155 92 155
1085150700 92 155 92 155
1085150400 92 155 92 155
1085150100 92 155 92 155
1085149800 92 155 92 155
1085149500 92 155 92 155
1085149200 92 155 92 155
1085148900 92 155 92 155
1085148600 92 155 92 155
1085148300 92 155 92 155
1085148000 92 155 92 155
1085147700 92 155 92 155
1085147400 92 155 92 155
1085147100 92 155 92 155
1085146800 92 155 92 155
1085146500 92 155 92 155
1085146200 92 155 92 155
1085145900 92 155 92 155
1085145600 92 155 92 155
1085145300 92 155 92 155
1085145000 124 127 165 155
InOctets: 1.3.6.1.2.1.2.2.1.10
OutOctets: 1.3.6.1.2.1.2.2.1.16
Thanks,
Kevin
More information about the juniper-nsp
mailing list