[c-nsp] SNMP/Monitoring Cisco gear

[Sam Silvester]

Depending on how you use MRTG to query your routers, you may want to
have a quick read of the section "SNMP Request Optimization in the
MRTG Configuration Reference...assuming you are not using external
scripts to read data from your routers, I believe if you list the same
OID more than once, MRTG caches the result for each run through

>From http://people.ee.ethz.ch/~oetiker/webtools/mrtg/mrtg-reference.html

"MRTG is designed to economize on its SNMP requests. Where a target
definition appears more than once in the configuration file, MRTG
requests the data from the device only once per round of data
collection and uses the collected data for each instance of a
particular target"

May be useful, but depends as I said on if you are using external
monitoring scripts or not.

Cheers,

Sam


On Wed, 27 Oct 2004 22:03:46 -0300, Javier Szyszlican <javier at szysz.com> wrote:
> Hi Gerald,
> 
> You could try JFFNMS http://www.jffnms.org
> 
> It supports most of what you asked for, except netflow.
> 
> It will track the interface description when you change it, it will stop
> graphing (no errors) when an interface is down, it has tftp config download and
> diff. It also allows you to create "maps" or groups of interface to get
> aggregated data (ie, 2 upstreams in the same graph).
> 
> Javier
> 
> 
> 
> Gerald wrote:
> > I'll ask this here, since I primarily have Ciscos deployed. I'm looking to
> > eventually automate and consolidate my SNMP monitoring of my cisco devices.
> >
> > The things I want to address are:
> >
> > - reduce redundant polling (automatically?)
> > - effectively and easily pool statistics (all T1s traffic are X; all
> > servers are Y;)
> > - automate changes (interface is down, graphing stops with no errors.
> > That's what network monitoring is for, not stats, new customer comes up
> > stats take the interface description and automatically update the stats
> > output. Company changes names, so modifying description on interface
> > updates everything else.)
> >
> > I'm currently using Nagios for monitoring + mrtg for stats. With mrtg I
> > could script a new scan to force changes, but that still doesn't address
> > the redundant polling to get grouped data. Example: I have 2 primary
> > upstreams and in order to graph each one individually and then give a
> > 3rd graph of the combined I have to hit the routers again with a second
> > query.
> >
> > Is there a better way to monitor my cisco gear and provide the output like
> > mrtg AND make it flow with the changes or am I thinking too far ahead?
> >
> > Programs I haven't looked at in detail yet that I'm vaguely aware of:
> > cricket, rrdtool, smokeping, anything that uses Cisco netflows.
> >
> > In my mind this is something like rancid meets mrtg meets a brain that
> > knows how to use information that it already has instead of querying the
> > device again. I can script this into existence pretty shortly, but I
> > hate reinventing the wheel.
> >
> > Gerald
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>