[mrtg] Problem with mrtg and snmp version 2
Daniel J McDonald
dan.mcdonald at austinenergy.com
Thu Mar 20 13:06:22 CET 2008
On Tue, 2008-03-18 at 16:37 -0600, Karina Gómez wrote:
> ifInOctets.2&ifOutOctets.2:Canopy at 192.168.13.49:::::2
> isn't activated with that last 2 ?
Yes, but until 2.15.2, if it detected from ifHighSpeed that the 64 bit
counters were not used, then it would drop back to snmp V1 and use
ifInOctets and ifOutOctets.
In 2.15.2, I introduced a change to poll using snmp v2, but force the
use of ifInOctets and ifOutOctets. The change in behavior is signaled
by the NoHC directive. That was needed for snmp v3 boxes, since you
can't just fall back from v3 to v1. But it also works for snmp V2
> Sean Cheesman wrote:
> > Some devices only respond to v2 queries. Just enable v2 polling for that device in your config and you should be ok.
> > Sean
> > I have a problem with some devices that only responds to snmp version 2c. snmpwalk and snmpget with the -v 2c option works ok. Mrtg doesn't send any errors but the log file is full with zeroes. I think that it's trying to query the device with snmp version 1 so the device doesn't respond.
> > Thanks for your help,
> > Karina.
> > IF-MIB::ifLastChange.1 = Timeticks: (397661) 1:06:16.61
> > IF-MIB::ifLastChange.2 = Timeticks: (397662) 1:06:16.62
> > IF-MIB::ifInOctets.1 = Counter32: 1245356
> > IF-MIB::ifInOctets.2 = Counter32: 4432502
> > IF-MIB::ifInUcastPkts.1 = Counter32: 10636
> > IF-MIB::ifHighSpeed.1 = Gauge32: 0
> > IF-MIB::ifHighSpeed.2 = Gauge32: 0
Daniel J McDonald, CCIE #2495, CISSP #78281, CNX
More information about the mrtg