[j-nsp] MRTG and ATM interfaces

[Kevin Vuong]

When running cfgmaker against it specifying snmp v2 I get this:

--base: check for HighspeedCounters faild ... Droping back to V1
--base: snmpget <community at router>:::::2:v4only for ifHighSpeed.167 -> 0 Mb/s
--base: snmpget <community at router>:::::2:v4only for ifHCInOctets.167 -> 
77213564

so I think that's dropping me back to 32-bit counters for these ATM 
interfaces.

Also, I just noticed that the problem seems to be happening on our 4x T3 
ATM-II and not on the 2x OC-3 ATM-II, SMIR card.  The HighspeedCounters check 
is succeeding on the OC-3 subinterfaces but not the DS3 subinterfaces.


Thanks,

-Kevin


On Friday 21 May 2004 10:29 am, Brian W. Gemberling wrote:
> Are you using 64-bit counters for this interface?
>
> On Fri, 21 May 2004, Kevin Vuong wrote:
> > 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
> >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/juniper-nsp