[mrtg] Solution: Always specifify version 2 (WAS: Re: Debugging LoadMIBs)

[Brian A. Seklecki]

On Tue, 13 Nov 2007, Brian A. Seklecki wrote:

> All:
>
> Is there a way to debug if "LoadMIBs" is being properly processed?
>
> I'm getting noSuchName(2) nonsense again.


My config specifies:

     EnableSnmpV3: yes

Here's a functional example the target that explicitly specifices SNMP 
Version 2:

   Target[br0.pfsyncErrs]:
   pfsyncNoMemory.0&pfsyncOutputErrors.0:[snmpcomm]@10.0.0.3:::::2

And the debug output:

--snpo: SNMPfound -- '147', '270', '3 hours, 25:48.95', 'br0'
--snpo: run snmpget from 
pfsyncNoMemory&pfsyncOutputErrors:[snmpcomm]@10.0.0.3
--snpo: simple If: .0
--snpo: simple If: .0
--snpo: SNMPGet from [snmpcomm]@10.0.0.3:::::2 -- 
pfsyncNoMemory.0,pfsyncOutputErrors.0,sysUptime,sysName

This looks clean.  If I don't specificy version 2, I get noSuchName(2):

   Target[br0.pfsyncErrs]:
   pfsyncNoMemory.0&pfsyncOutputErrors.0:[snmpcomm]@10.0.0.3:::::

$ sudo -H -u mrtg mrtg ./mrtg-br0-ng.conf

SNMPGET Problem for pfsyncNoMemory.0 pfsyncOutputErrors.0 sysUptime 
sysName on [snmpcomm]@10.0.0.3::::::v4only: Received noSuchName(2) 
error-status at error-index 2 at /usr/local/bin/mrtg line 2156
2007-11-30 15:56:36: ERROR: Target[br0.pfsyncerrs][_IN_] ' 
$target->[11]{$mode} ' did not eval into defined data
2007-11-30 15:56:36: ERROR: Target[br0.pfsyncerrs][_OUT_] ' 
$target->[11]{$mode} ' did not eval into defined data


--snpo: SNMPGet from [snmpcomm]@10.0.0.3::::: -- 
pfsyncNoMemory.0,pfsyncOutputErrors.0,sysUptime,sysName
SNMPGET Problem for pfsyncNoMemory.0 pfsyncOutputErrors.0 sysUptime 
sysName on [snmpcomm]@10.0.0.3::::::v4only: Received noSuchName(2) 
error-status at error-index 2 at /usr/local/bin/mrtg line 2156
--snpo: SNMPfound -- 'undef', 'undef', 'undef', 'undef'