[121485] in North American Network Operators' Group
Re: Enhancing automation with network growth
daemon@ATHENA.MIT.EDU (Chris Adams)
Wed Jan 20 23:16:39 2010
Date: Wed, 20 Jan 2010 22:16:09 -0600
From: Chris Adams <cmadams@hiwaay.net>
To: nanog list <nanog@nanog.org>
Mail-Followup-To: Chris Adams <cmadams@hiwaay.net>,
nanog list <nanog@nanog.org>
In-Reply-To: <4B57C1FA.5000207@ibctech.ca>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Once upon a time, Steve Bertrand <steve@ibctech.ca> said:
> One thing that would take a major load off would be if my MRTG system
> could simply update its config/index files for itself, instead of me
> having to do it on each and every port change.
Is MRTG a requirement, or just some type of statistical monitoring?
There are other packages that can do (or be made to do) what you want.
I switched from MRTG to Cricket many years ago, and a big improvement
there is that you configure interface names (and Cricket handles
tracking the index). There are add-ons like genDevConfig (replaces
genRtrConfig) that can auto-generate configs for you. The only downside
to Cricket is that development has stagnated (I think it is a case of
"it works for me" for most everybody using it).
There's also Cacti, which is newer and more current.
--
Chris Adams <cmadams@hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
