2009/9/1 David Dyer-Bennet <[email protected]>: > Is this "best practice" in the opinion of the community? Or is using SNMP > to monitor something inside the router better somehow? And if so, WHAT?
Good question. One person's 'best practice' is another person's over-kill or under-kill. My golden rule is "only monitor something if you're going to be interested in it". For routers this usually means I simply ping them, but often I'm interested in bandwidth of specific interfaces too so I make sure specific WAN links are monitored for bandwidth, errors, discards and so on using the plugins from http://www.manubulon.com It's often a good idea to have the router send you SNMP traps - you'll need to configure snmptt to handle them though, maybe using NagTrap. I often find I get more traps than I'm interested in though - which breaks the golden rule (see above) - so I then need either to filter the traps out in the snmptt config or prevent the router from sending them in the first place. I used to monitor each router interface using ping, but now I think that's usually overkill. It just depends ... ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
