Date: Wed, 10 Jan 2001 13:02:18 -0700 From: "Matt Simerson" <mpsimerson@hostpro.com> To: "'freebsd-hackers@freebsd.org'" <freebsd-hackers@freebsd.org> Subject: RE: Link up/down events Message-ID: <8D18712B2604D411A6BB009027F644980DD82F@0SEA01EXSRV1>
next in thread | raw e-mail | index | archive | help
While it can be done (I do it), using MRTG/rateup/Cricket/etc. without SNMP is much like pushing a car down the street. Sometimes it's The Right Thing to do but for the other 99.4% of the time, it's far preferable to use the engine to power it. UCD-SNMP is more than just the UCD SNMP daemon. It's also the client programs and a collection of SNMP utilities. With them you can do most of what you'd ever want to use SNMP for. MRTG is simply a data graphing utility. It uses SNMP to collect the data points but that's pretty much all of the relationship between the two. Matt > -----Original Message----- > From: Chuck Rock [mailto:carock@epconline.net] > Sent: Wednesday, January 10, 2001 11:17 AM > To: FreeBSD Hackers > Subject: RE: Link up/down events > > > Has anyone looked into using SNMP with MRTG or some of the > other utilities that comes with UCD-SNMP? > > I think this would be very easy this way. We use Castle > Rock's SNMPc running > on NT to montior our servers and connections. > > UCD-SNMP is a daemon and SNMP utilities for Linux and FreeBSD > flavors that > work well too. > > http://ucd-snmp.ucdavis.edu/ > http://www.mrtg.org > http://www.castlerock.com > > Chuck > > > -----Original Message----- > > From: owner-freebsd-hackers@FreeBSD.ORG > > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of > Samuel Tardieu > > Sent: Wednesday, January 10, 2001 11:07 AM > > To: Robert Watson > > Cc: Josef Karthauser; hackers@FreeBSD.ORG; n_hibma@FreeBSD.ORG > > Subject: Re: Link up/down events > > > > > > On 10/01, Robert Watson wrote: > > > > | Presumably at some point in the stack, that notification > is translated > > | from a hardware event, which might be associated with devd in > > some manner > > | (and possibly also exposed there). > > > > This is the ideal situation. The other one being that the > status can be > > read, which would require some polling to monitor the link status. > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8D18712B2604D411A6BB009027F644980DD82F>