4 * Major overhaul of the perfdata code. This includes API breakage and
6 - Probes were not sorted correctly
7 - Voltage data was not included
8 * The PNP template check_openmanage.php has been redone to work with
9 the changes in perfdata output from the plugin
10 * A new option '--legacy-perfdata' will make the the plugin output the
11 performance data in the old format
12 * The old PNP template for performance data is available in the
13 distribution as 'check_openmanage_legacy.php'
14 * Added support for a configuration file
15 * If using html output, URLs will now open in a new window
16 * Added a compatibility fix for OMSA 6.5.0, related to performance
17 data for amperage probes when the plugin is used in local mode
22 * Added workaround for a rare condition in which blade detection fails
23 because the chassis IDs for the blade and interconnect board have
24 switched places in the BaseBoardType SNMP table.
29 * A regression wrt. non-certified drives were fixed. The plugin failed
30 to identify non-certified physical drives via SNMP.
31 * Added the ability to blacklist non-certified drives with the
32 'pdisk_cert' blacklisting keyword.
37 * Fixed typo in help output
38 * SD card check is now included if the parameter '--only chassis' is
40 * The plugin will issue a proper warning if a physical drive is
41 uncertified, instead of an unspecified warning. One or more
42 uncertified drives will make the controller go into a non-critical
44 * Slightly improved reporting of fan status
45 * Exit with value 3 (unknown) if printing debug, help or version
46 info. This is considered best practice for Nagios plugins.
47 * Workaround added for logical SAS connectors to external storage
48 enclosures, when using check_openmanage in local mode with OMSA
49 6.4.0 or later versions. The output from omreport could contain
50 lines that the plugin was unable to parse, which would lead to
56 * Fix counting of components when blacklisting is used. Components
57 should be counted even if blacklisted
58 * Added some unsupported vdisk types to the list. The OMSA MIB
59 identifies these, but lists them as unsupported.
60 * Added option '-B' or '--show-blacklist' to show any blacklistings in
62 * Fixed a bug for checking voltage probes, if the reading is missing
64 * Fixed a regression bug for a power monitoring corner case.
69 * Added more robustness wrt. values from OMSA obtained via SNMP, to
70 avoid internal errors where non-important values are missing.
75 * A few compatibility fixes for OMSA 6.4.0 were added.
80 * Added support for IPv6 when checking via SNMP. IPv6 can be turned on
81 with the option '-6' or '--ipv6'. The default is IPv4 if the option
83 * Added support for TCP when checking vis SNMP. The option '--tcp' can
84 be used to turn on TCP. The default transport protocol is UDP if the
85 option is not present.
86 * The mode of operation (local or SNMP) is shown in the debug
87 output. If SNMP is used, the debug output will also show the SNMP
88 protocol version, IP version and transport protocol (UDP or TCP).
89 * Amperage probe status via SNMP is of type "probe status", not
90 regular status. This has been fixed.
91 * Massive overall robustness improvements to handle OMSA bugs where
92 some information from OMSA is missing.
93 * Memory module enumeration via SNMP changed somewhat to reflect
94 enumeration provided by omreport. This ensures that the plugin's
95 output is identical in SNMP or local mode wrt. dimms IDs.
96 * Fan enumeration via SNMP changed somewhat to reflect enumeration
97 provided by omreport. This ensures that the plugin's output is
98 identical in SNMP or local mode wrt. fan IDs.
103 * Included new check for SD cards. Newer servers such as the R710 can
104 have SD cards installed, these should be monitored. The SD card
105 check is on by default. A new blacklisting keyword 'sd' has been
106 added. The SD card check can be turned off with '--check sdcard=0'.
107 * Handle special cases where power monitoring capability is disabled
108 due to non-redundant and/or non-instrumented power supplies.
109 * For physical disks probed via SNMP, check that values for vendor,
110 product ID and capacity is available before attempting to display
112 * If a physical disk is in sufficiently bad condition, the vendor
113 field reported by OMSA may be empty. The plugin now handles this
114 situation without throwing an internal error.
120 * Storage is no longer allowed to be absent. If the plugin doesn't
121 find a storage controller, it will give an alert. For diskless
122 systems or servers without a Dell controller that OMSA recognizes
123 you will now have to specify '--no-storage' or '--check storage=0'
125 * Report the system revision (if applicable) wherever the model name
126 is printed. E.g. "PowerEdge 2950 III" instead of "PowerEdge 2950".
127 * Small change in search path for omreport: The new location for OMSA
128 6.2.0 and later on Linux will be attempted first.
129 * Small bugfix for the '--check' parameter, if the argument is a
130 filename. The file could not contain a linebreak, this has been
132 * Added an option '--no-storage', which is equivalent to the general
133 option '--check storage=0'.
139 * If a physical disk is a hot spare, display this information in
141 * Report the bus protocol (e.g. SAS, SATA) and media type (e.g. HDD,
142 SDD) for physical disks in the debug output, if applicable
143 * Minor fix for 100GB physical disks, write "100GB" instead of "99GB"
144 * SNMP: Use new features of OMSA 6.3.0 to display occupied and total
145 slots in storage enclosures, if applicable. This information is not
146 available with omreport and check_openmanage will not display this
148 * SNMP: Added new processor IDs from the OMSA 6.3.0 MIBs
149 * SNMP: Use connection tables in a proper way to determine controller
150 and enclosure IDs, for use with physical disks and enclosure
151 components (fan, temp sensors etc.). This fixes a long standing bug
152 for servers with more than one controller, if checked via SNMP.
153 * SNMP: Use the nexus ID as last resort to find the controller for
154 physical disks. Workaround for older, broken OMSA versions.
155 * SNMP: Identify enclosures (e.g. '2:0:0') properly so that the
156 reporting with SNMP corresponds to the same report with omreport.
157 * SNMP: added a couple of workarounds for pre-historic OMSA versions
163 * More fine-grained reporting of temperature warnings for enclosure
165 * Max/min temperature limits for enclosure temp probes are reported in
167 * Report enclosure temperature probes that are "Inactive" as ok
168 * Don't try to print out the reading of enclosure temperature probes
169 if the reading doesn't exist or is not an integer
170 * Report enclosure EMMs that are "Not Installed" as ok, instead of
172 * Corrected typo in the PNP4Nagios template
178 * Remove reporting of which controller a logical drive is "attached"
179 to, since this information can't be reliably extracted via SNMP.
180 * Avoid collecting Lun ID via SNMP for virtual disks, we don't use it
181 * Report total memory and number of dimms in the ok output
182 * Difference in reporting if amperage probes have discrete readings
183 * Workaround for broken amperage probes
184 * Added workaround for bad temperature probes that yields no reading
186 * Get OMSA version via SNMP slightly more efficiently
192 * Added robustness for received SNMP values that are not defined in
193 the MIB. Instead of throwing a perl warning when this happens, the
194 plugin will not report the undefined value.
195 * Defined "Replacing" as a defined state for physical disks in SNMP
196 mode, even though this state is not defined in the MIB. It is
197 reported as such by omreport.
198 * Physical disk brand/model is now reported when the state of the disk
199 is "Rebuilding" or "Replacing".
200 * The state of a physical disk is reported in parentheses when
201 predictive failure is detected. It is useful to know if a disk is
202 online, offline, spare or even failed when predictive failure is
204 * Handling of physical disk predictive failure has been improved
206 * Refactoring of the perfdata code. In conformance with the plugin
207 development guidelines, the UOM (unit of measure) previously
208 reported in the perfdata output has been removed.
209 * The -p or --perfdata option now
210 takes an optional agrument 'minimal', which triggers shorter names
211 for the perfomance data labels. This shortens the output and is a
212 workaround for systems where the amount of output exceeds the 1024
214 * The PNP4Nagios template has been updated. Users of check_openmanage
215 and PNP4Nagios are advised to upgrade. This version of
216 check_openmanage needs the new template.
217 * Lots of other small improvements and updates.
223 * New option '--use-get_table' is added as a workaround for SNMPv3 on
224 Windows using net-snmp. This option will make check_openmanage use
225 the Net::SNMP function get_table() instead of get_entries() to
226 collect information via SNMP.
227 * Include a blacklisting option 'ctrl_pdisk' which takes the
228 controller number as argument. This blacklisting option only works
229 with omreport and is a workaround for broken disk firmwares that
230 contain illegal XML characters. These characters makes openmanage
231 barf and exit with an error. Patch from Bas Couwenberg.
232 * If the blacklisting keyword "all" is supplied for a component type,
233 that component type is not checked at all, i.e. the commands are
234 never executed. This will make check_openmanage execute faster if
235 blacklisting is heavily used.
236 * Option '--htmlinfo' now has a shorter equivalent '-I'
237 * The option '--short-state' now has a shorter equivalent '-S'
243 * Fixed an SNMP bug where the plugin didn't handle OID indexes that
244 were not sequential. Thanks to Gianluca Varenni for reporting.
245 * Fixed an SNMP bug when checking old hardware such as the PE 2650 and
246 PE 750. The controller id for physical drives were collected and
247 displayed incorrectly. This release uses an additional OID to fetch
248 this info, which would otherwise be unavailable. Thanks to Gianluca
249 Varenni for reporting this bug.
250 * Should use %snmp_probestatus, not %snmp_status when checking the
251 status of voltage probes. Thanks to Ken McKinlay for a patch.
252 * Fix when identifying blades via SNMP with very old OMSA
253 versions. Patch from Ken McKinlay.
254 * Better way of finding the ID of physical drives via SNMP
260 * Added support for storport driver version for controllers, only
261 applicable on servers running Windows. A new blacklisting keyword
262 for suppressing storport driver messages was added.
263 * The "all" keyword in blacklisting is now case insensitive.
264 * More fine-grained reporting in the rare case where a controller
265 battery fails during learning and charging states.
266 * New improved way of reporting perl warnings during execution of the
273 * Fix for path to omreport on Linux with OMSA 6.2.0
274 * A couple of other small fixes
280 * Fix for undefined device name for logical drives (thanks to Pontus
282 * Fixed a bug in the PNP4Nagios template, that prevented the template
283 from working with PNP4Nagios 0.6. Thanks to the PNP4Nagios team for
290 * CPU type, family etc. are now reported in case of a CPU failure (and
292 * The debug output now reports Openmanage version and plugin version
298 * New option '-a' or '--all' turns on checking of everything
299 * The manual page (POD info) is removed from the script and is now in
300 a separate file, to make check_openmanage fully ePN compatible
301 * ePN is no longer disabled by default, check_openmanage no longer has
302 an opinion on whether it should run under ePN or not
303 * The '-m' or '--man' option is no longer available
304 * The option '-v' or '--verbose' is renamed to '-d' or '--debug',
305 which makes more sense wrt. its usage
306 * The '-g' or '--global' option is removed. Checking the global health
307 status is now default if applicable
308 * Checking intrusion detection is now turned on by default
309 * The obsolete option '--snmp' is removed
310 * The option '--state' now has a shorter equivalent '-s'
311 * The basename stuff and options '--only-critical' and
312 '--only-warning' are now replaced by an option '--only'
313 * If plugin is run by Nagios, redirect stderr to stdout
314 * Added option '--omreport', that lets the user specify the full path
315 to the omreport binary
316 * Added non-8bit-legacy default search paths for omreport.exe for
318 * Minor changes to the plugin output, for consistency
319 * New blacklisting keyword 'bat_charge' disables warning messages
320 related to controller cache battery charging. Thanks to Robert
321 Heinzmann for a patch.
322 * For blacklisting, the component ID kan now be "ALL", in which all
323 components of that type is blacklisted.
324 * Man page is moved to manual section 8
330 * Fixed a bug that could cause errors and weird results when checking
331 cooling devices (fans) via SNMP. Thanks to Ken McKinlay for spotting
332 this bug and reporting it.
337 * For failed physical drives, check_openmanage will now output the
338 drive's vendor, model and size in GB or TB.
343 * The -s|--snmp option was redundant and no longer does anything. SNMP
344 is triggered automatically if the -H|--hostname option is
345 present. The -s|--snmp option is kept for compatibility, but has no
351 * Added support for performance data (temperatures) from attached
352 storage enclosures such as the MD1000
357 * Fixed a regression in the --htmlinfo option when it is not supplied
363 * New option --htmlinfo adds clickable HTML links in the plugin's
369 * Fixed a regression bug in CPU and power supply reporting that only
370 affects verbose output
371 * If blacklisting is used, the global health check (via the --global
372 option) is now negated. Checking the global health doesn't make
373 sense when one or more components is blacklisted. Thanks to Rene
374 Beaulieu for reporting this bug
375 * The PNP4Nagios template is now included in the tarball and zip
381 * Improved memory error reporting, when using omreport
382 * Collect performance data from pwrmonitoring (amperage probes) that
383 were previously ignored when using omreport
388 * Improved memory error reporting, when using SNMP
389 * Other small ehnancements
394 * The plugin is now compatible with the Nagios embedded Perl
395 interpreter (ePN) in theory. However, the plugin will not not use
396 ePN by default. We don't want any "accidents".
397 * License is now GPLv3, previously only specified as "GPL"
398 * New options --only-critical and --only-warning. With these options
399 the plugin will only print critical or warning alerts, respectively.
400 * Bugfixes and speed enhancements in the storage section, when
401 checking enclosure components via omreport
402 * The --okinfo option is now less verbose and more to the point
403 * Lots of code refactoring for readability, maintainability and
409 * Fixed a bug in the storage section, when checking controllers. This
410 is an obscure bug that only manifests itself in the odd case where a
411 server has multiple controllers, and one of the controllers are
412 missing some of the OIDs, in which case these OIDs will be missing
413 for the other controllers as well. The change is minor and only
414 includes using get_table() instead of get_entries() to collect the
415 SNMP result. Thanks to Stephan Bovet for reporting this bug.
420 * The --perfdata option can now optionally take an argument
421 "multiline", which makes the plugin produce multiline performance
422 data output in a Nagios 3.x way. Not really needed, but the plugin
424 * Added comment within the 10 first lines to disable the nagios
425 embedded perl (ePN) interpreter by default for Nagios 3.x
426 * Improvements in the performance data output. Units are now included
431 * Added --global option, which turns on checking of everything. If
432 used with SNMP, the global system health status is also probed, to
433 protect the user against bugs in the plugin. If used with omreport,
434 the overall chassis health is used.
435 * Support for SNMP version 3
436 * New check added: esmhealth. This checks the overall health of the
437 ESM log, i.e. the fill grade. More than 80% means a warning message
438 * Fixed alert log reporting to use the same format as for the ESM log
439 * Output messages are now sorted by severity
440 * Minor changes in how out-of-date controller firmware/driver is
442 * Code refactoring and cleanup
447 * Use "omreport about" to collect OMSA version. Slightly faster than
448 "omreport system version". This should give a small speedup in
449 certain configurations
450 * Fixed typo in output when a logical drive is rebuilding. Thanks to
451 Andreas Olsson for reporting
452 * Improved reporting of ESM log content
453 * Added omreport.sh as alternate omreport path
454 * Lots of other small fixes and enhancements
456 Plus: A few changes to make the plugin work with old PowerEdge models
457 (e.g. 2550, 2450) and/or old OMSA versions (e.g. version 4.5):
459 * Use the chassisModelName OID to determine if SNMP works (instead of
461 * No longer require a response when checking baseboard type via
462 SNMP. If there is no response, we assume that we're not dealing with
465 Thanks to Christian McHugh for help with testing and debugging this
471 * Use 'omreport system operatingsystem' to collect OS info, instead of
472 'omreport system' version which is incredibly slow. This should speed
473 things up in certain configurations.
474 * A few speedups, don't collect information that isn't needed
480 * New option --linebreak to specify the separator between line in case
482 * Added support for 64bit Windows. Thanks to Patrick Hemmen for a patch
483 * [Patrick Hemmen] Added install.bat for Windows installation
484 * [Patrick Hemmen] Improvements on install.sh. Will now install in
485 /usr/lib64 for x86_64
486 * RPMs are now architecture dependent, because of different libdir
491 * New option -o|--ok-info to display extra information when everything
492 is ok. The plugin can now display storage firmware and driver info,
493 DRAC and BMC firmware, and OMSA version
494 * Support for setting custom minimum temperature thresholds via the
495 -c|--critical and -w|--warning options
496 * Better and more detailed temperature error reporting
497 * Bugfix in the amperage report (including performance data). The
498 plugin now takes into account the correct unit and measurement for
499 amperage probes (other than watts)
500 * New option --port lets the user specify the remote SNMP port number
505 * Regression fix: Use the older Processor Device SNMP OIDs for older
506 PowerEdge models, that don't have the new Processor Device Status
507 OIDs. Thanks to Nicole Hähnel for reporting this bug.
508 * Default output (when there are no alerts) now shows RAC firmware,
509 BMC firmware, info about controllers and enclosures (firmware,
515 * Regression fix: Ignore unoccupied CPU slots with SNMP probing. This
516 fixes a bug introduced in versjon 3.2.1, which would output
517 something like this if one or more CPU slots were empty: CPU 1 needs
523 * Use Processor Device Status Table OIDs instead of Processor Device
524 Table when checking CPUs via SNMP
525 * Bugfix: don't report throttled CPUs as warnings when checking via
526 SNMP (same as for checking locally)
531 * New options --state and --short-state for displaying service state
533 * Lots of small fixes for code readability and maintainability
538 * Support for running natively on Windows (using omreport.exe). Thanks
539 to Peter Jestico for a patch.
540 * Support for compiled Windows version, i.e. check_openmanage.exe is
541 now a legal script name.
542 * Exit with error if script basename is illegal/unknown
543 * Various small fixes
548 * Use of alternate basenames for checking only one class of components
549 * Added support for checking the ESM log via SNMP
550 * Code refactoring for robustness and maintainability
551 * Numerous small fixes and enhancements
552 * Added install script in distribution tarball
557 * The script no longer aborts if it can't get system information via
558 SNMP. Give a warning instead, as this is not a critical error
559 * Increased robustness when checking controllers
564 * Man page fix in the 'check' section. Thanks to Ansgar Dahlen for
566 * Allow invalid command error from 'omreport chassis pwrmonitoring'
567 * Various small fixes
572 * Use unique IDs for storage components with regard to blacklisting,
573 which means that the blacklisting API has changed
574 * Added checks for storage components: connectors (channels),
575 enclosures, enclosure fans, enclosure power supplies, enclosure
576 temperature probes and enclosure management modules (EMMs)
577 * Improved verbose output
578 * New option -t|--timeout for setting the plugin timeout
579 * New option -w|--warning for setting custom temperature warning
581 * New option -c|--critical for setting custom temperature critical
583 * Option --check can no longer be specified in its short form (-c)
584 * Code cleanup and improvements
589 * The workaround for the OMSA bug introduced in OMSA 5.5.0 didn't take
590 multiple controllers into account. This has been fixed.
595 * New option -i|--info prefixes all alerts with the service tag
596 * New option -e|--extinfo gives and extra line of output in case of an
597 alert (model and service tag)
598 * New option --postmsg lets the user specify a post message string,
599 with info such as model, service tag etc.
600 * Options -b|--blacklist and -c|--check can now be specified multiple
601 times (actually quite useful)
606 * Slightly improved output for alerts on logical drives (vdisks)
607 * Now shows a rebuilding physical disk as a warning, as this is
608 usually accompanied by a degraded vdisk. Previous versions didn't
609 show this at all (omreport classifies it as "OK").
614 * Slightly improved output for charging controller batteries
619 * Bugfix for reporting physical drives with predictive failure (both
625 * Fix bug in option handling (ambiguous options)
626 * Slightly improved output if checking the storage subsystem is turned
628 * Don't complain if there are no logical drives. This is OK. Thanks to
629 Jamie Henderson for reporting this
634 * Fix bug in SNMP status level table
639 * Added workaround for a BUG introduced in OpenManage 5.5.0. OM
640 sometimes adds a newline in the controller driver version name,
641 which leads to problems parsing the output. Thanks to Hiren Patel
642 for bringing this to my attention.
647 * (snmp) Improved handling of cases where OM is not working properly
652 * Fixed issue where controller number for physical disks can't be
653 established via SNMP (now identifies as controller no. -1)
658 * Correctly identifies and reports error condition in which OpenManage
659 has stopped working (it happens)
665 * Same options for checking, blacklisting etc. supported with SNMP
666 * Same output with SNMP as with NRPE
671 * Collects performance data if the option '-p' or '--perfdata' is
673 * New blacklisting directives ctrl_fw and ctrl_driver
674 added. Suppresses the "special" warning messages concerning outdated
675 controller firmware and driver. Useful if you can't or won't
681 * Fix getting system model and serial number for newer blades
686 * Three new checks added:
687 - System battery probes (typical CMOS battery). Newer poweredge
689 - Power consumption monitoring (if the server supports it)
690 - ESM log, with same functionality as the alert log check. Disabled
696 * Internal refactoring: use ssv-formatted output from openmanage,
697 resulting in slightly faster execution and increased robustness.
698 * If /usr/bin/omreport doesn't exist, try
699 /opt/dell/srvadmin/oma/bin/omreport.
700 * Allow for no instrumented/redundant power supplies. Needed on
701 low-end poweredge models and blades.
706 * Openmanage reports non-critical warning about throttled CPUs on new
707 hardware models. Most og us use ondemand CPU frequency scaling (with
708 throttled CPUs as a result). This specific non-critical warning (CPU
709 Throttled) is ignored from now on.
710 * Remove superfluous Celcius sign when reporting temperatures.
715 * Accommodate blade systems with no fans or powersupplies, i.e. accept
716 errors from omreport when trying to check fans or powersupplies on
718 * Accommodate newer hardware with slightly different omreport
719 options. Use the newer options if they exist. Not really necessary
720 yet, but deprecated options may be removed in future versions of
726 * When everything is OK, check_openmanage now outputs the same info as
727 Gerhard Lausser's excellent check_hpasm plugin does for HP servers:
729 OK - System: 'poweredge 2850', S/N: 'XXXXXXX', ROM: 'A06
730 10/03/2006', hardware working fine, 2 logical drives, 4 physical