snmp_disk help

[Joe Morris]

On Mon, 8 Sep 2003, Damian Gerow wrote:

| I've got Nagios 1.1 installed and working for a number of active checks
| (_http, _ftp, _pop, _imap, _smtp, ...).  I'm starting to work with SNMP
| to be able to watch remote disk usage, CPU load, etc., but I've run into
| a few snags.

| Does anyone have a working check_snmp definition that will iterate
| through the various mounted disks, instead of needing to use one
| definition per disk?  It'd be a fair bit faster, and put a little less
| load on everyone, I think.  I'd like to avoid having six different
| snmp_disk definitions, and define as many as needed per host.

I cobbled together a simple ksh script (meets most of the plugin
standards) that uses snmpdf from the net-snmp package.  It fetches all
filesystem info via snmpdf and then looks up all of the parameters for the
the filesystems I want to monitor for that host.  It simply gives the all
clear they all passed or warning/critical threshold information for that
filesystem(s).  This means I have one service defined for each host that
checks all of the filesystems I'm interested in and I can update the
configuration file on the fly.  If you don't have the snmpdf tool, I'm
sure there's an wasy way to get what you want with snmpwalk and the right
oid.

I'll be glad to share what I did with you and others.  I've put a few
other ksh scripts like this to monitor the load avg and remote processes
by fetching the data I need with snmp.

_______________________________________________
Joe Morris, Web Systems Manager
Academic Technology and Networks
The University of North Carolina at Chapel Hill


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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