mrtg help
David Bandel
david.bandel
Mon Nov 15 11:16:08 PST 2004
On Mon, 15 Nov 2004 09:00:09 -0500 (EST), Net Llama!
<netllama at linux-sxs.org> wrote:
> On Mon, 15 Nov 2004, David Bandel wrote:
>
>
> > On Sun, 14 Nov 2004 18:34:00 -0800, Net Llama! <netllama at linux-sxs.org> wrote:
> > > Good evening,
> > > I'm trying to get mrtg working, and i'm stuck on getting snmpd working.
> > > Each time I try to run mrtg, i'm seeing this error:
> > > SNMP Error:
> > > no response received
> > >
> > > In snmpd.conf, i've got:
> > > com2sec readonly localhost public
> > >
> > > What am i missing?
> >
> > not sure, but try this:
> > first, run snmpwalk from the localhost:
> > snmpwalk -v 2c -c public localhost
> > then try the same thing from the same host, but use the hostname that
> > refers to your ethernet card.
> > Then go to your mrtg system and try to run snmpwalk against the remote host.
> > If the first two work, but the last one doesn't, make sure that your
> > mrtg host is requesting the data from the near ethernet card and not
> > the far card.
> > Explanation:
> > Most routers have more than one ethernet (or other) interface. The
> > mrtg host will normally be pointed to the hostname of the router, but
> > that may resolve to an interface IP that goes _through_ the router
> > rather than hitting the nearest (via routing) interface.
> > Because SNMP uses UDP, if you request data from an interface that is
> > logically on the other side of the router, you'll get your answer back
> > from the near side interface and snmpwalk isn't expecting that, so
> > discards that data (or netfilter blocks it as not RELATED).
> >
> > If the first two snmpwalks don't work on the localhost, keep looking
> > at your snmpd.conf security settings.
>
> I guess i should have mentioned that i'm doing all of this on localhost.
> There is no remote host. I spent about 3 hours last night sorting through
> assorted snmp and mrtg documentation, and then only thing that i learned
> is that there's a ton of conflicting information out there.
>
> Any tips on how to do a barebones, very minimal snmpd.conf ?
Attached is one I use on one of my systems. It is "bare bones" except
for the proc line (which you can comment out) and of course change the
System lines. A complete rundown of the snmpd.conf file would be
quite a few/very large e-mails.
HTH,
David A. Bandel
--
Focus on the dream, not the competition.
- Nemesis Air Racing Team motto
-------------- next part --------------
A non-text attachment was scrubbed...
Name: snmpd.conf
Type: application/octet-stream
Size: 792 bytes
Desc: not available
Url : http://mail.linux-sxs.org/pipermail/linux-users/attachments/20041115/d3d6b36a/snmpd.obj
More information about the Linux-users
mailing list