Page 2 - New Networking/hardware forum?

ok AlCapone,

I don't have any routers to play with, but I do have a couple of slackware boxes, so I figured I'd run some stats of them if I could.

Firstly, I'm assuming I need to have snmpd running on the agent box. I'm then using the same box as the manager.

I am using the cfgmake utility to build my config script in /export/mrtg/cfg/homrtg.cfg like so:

/usr/src/mrtg-2.9.25/bin/cfgmaker --global 'WorkDir: /export/mrtg' --global 'Options[_]:bits, growright' --output /export/mrtg/cfg/homrtg.cfg public@127.0.0.1

on building the config file, I get snmp error messages such as:


running mrtg against the generated config file doesn't come up with much, as you can imagine - well in fact, it does nothing.

And now I don't even know what to ask.. but I think it has something to do with my snmp setup. I'm using net-snmp and the snmpd is definitely running.... er I'll hit submit, sleep on it, and then I'll get back tomorrow !

later
christo

/me wishes we had a forum dedicated to this stuff .. and also has a squillion IP adressing questions for a rainy day </wibble>

christo, I bet ya snmp.conf either doesn't exist or is broken. What did you use to generate it? BTW, community@router never worked for me, so I had to use public@localhost

edit: I did it on freebsd, but point remains.

well I used snmpconf to generate an snmp.conf file and moved it into /usr/local/share/snmp I didn't change any of the settings, ie I just accepted the initial default and then ended the conf file creation and moved it into place.

I am using public@127.0.0.1 or public@localhost, but still get these 'no response received errors'

it's gone 1.30am and I have to do $dayjob tomorrow. I'll post back from my desk

christo

Uh I'm not gonna lie to you - I've set it up after 10 hours coding, followed by 9 hours of partying and 3 hours circling around city trying to remember where I live.

I can hardly recall anything from the next day, so I'm not sure what did I do to get it started. What I do remeber, is that It had to do with smtp not answering mrtg's queries because it didn't know it's supposed to listen and reply. So yeah I reckon it was in snmpt.conf, which I deleted and use some app to configure a new one. I *might* have been smtpconf, not to sure