Hi all! On Monday 30 January 2006 08:47, Sand Philipp wrote: > Looks good! Thanks for your affords! > I've got one feature request :) > Is it possible to combine those checks, to have one snmp request to > collect the data. I think this would be very useful with those > cpq/hp checks. You would only have one check then, which could > check the whole hardware environment of the host. Same for the > Cisco and brocade Switches.
Possible? Of course. Sensible? Don't know. I want to? Surely not. The whole project started when the shell scripts I used first started to overload the monitoring server. Thus I wrote the plugins to be as simple as possible, deliberately setting things at compile time. For a "universal-check-this-machine" plug-in you would have to figure out which components need to be monitored and do a lot of run time configuration. Compaq/HP have some aggregate values which can be checked using check_cpq_ida (IDA controller + drives), check_cpq_fcaeac (External Array Controller + drives) and check_cpq_thermal (Guess!). check_brocade_overall and check_netapp_overall both report the overall status of a SAN-Switch or Filer respectively. (No, you don't want to do a snmpwalk on a Filer. They report _many_ values. ;-) > Is it possible to do something like this for Dell-HW, too? Should be possible, but I don't have access to Dell computers and the appropriate MIB files. [...] CU Peter -- Peter Gritsch mail: [EMAIL PROTECTED] web: http://snmp4nagios.sourceforge.net/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ 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
