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 * Added support for a configuration file
15 * Fixed typo in help output
16 * SD card check is now included if the parameter '--only chassis' is
18 * The plugin will issue a proper warning if a physical drive is
19 uncertified, instead of an unspecified warning. One or more
20 uncertified drives will make the controller go into a non-critical
22 * Slightly improved reporting of fan status
23 * Exit with value 3 (unknown) if printing debug, help or version
24 info. This is considered best practice for Nagios plugins.
25 * Workaround added for logical SAS connectors to external storage
26 enclosures, when using check_openmanage in local mode with OMSA
27 6.4.0 or later versions. The output from omreport could contain
28 lines that the plugin was unable to parse, which would lead to
34 * Fix counting of components when blacklisting is used. Components
35 should be counted even if blacklisted
36 * Added some unsupported vdisk types to the list. The OMSA MIB
37 identifies these, but lists them as unsupported.
38 * Added option '-B' or '--show-blacklist' to show any blacklistings in
40 * Fixed a bug for checking voltage probes, if the reading is missing
42 * Fixed a regression bug for a power monitoring corner case.
47 * Added more robustness wrt. values from OMSA obtained via SNMP, to
48 avoid internal errors where non-important values are missing.
53 * A few compatibility fixes for OMSA 6.4.0 were added.
58 * Added support for IPv6 when checking via SNMP. IPv6 can be turned on
59 with the option '-6' or '--ipv6'. The default is IPv4 if the option
61 * Added support for TCP when checking vis SNMP. The option '--tcp' can
62 be used to turn on TCP. The default transport protocol is UDP if the
63 option is not present.
64 * The mode of operation (local or SNMP) is shown in the debug
65 output. If SNMP is used, the debug output will also show the SNMP
66 protocol version, IP version and transport protocol (UDP or TCP).
67 * Amperage probe status via SNMP is of type "probe status", not
68 regular status. This has been fixed.
69 * Massive overall robustness improvements to handle OMSA bugs where
70 some information from OMSA is missing.
71 * Memory module enumeration via SNMP changed somewhat to reflect
72 enumeration provided by omreport. This ensures that the plugin's
73 output is identical in SNMP or local mode wrt. dimms IDs.
74 * Fan enumeration via SNMP changed somewhat to reflect enumeration
75 provided by omreport. This ensures that the plugin's output is
76 identical in SNMP or local mode wrt. fan IDs.
81 * Included new check for SD cards. Newer servers such as the R710 can
82 have SD cards installed, these should be monitored. The SD card
83 check is on by default. A new blacklisting keyword 'sd' has been
84 added. The SD card check can be turned off with '--check sdcard=0'.
85 * Handle special cases where power monitoring capability is disabled
86 due to non-redundant and/or non-instrumented power supplies.
87 * For physical disks probed via SNMP, check that values for vendor,
88 product ID and capacity is available before attempting to display
90 * If a physical disk is in sufficiently bad condition, the vendor
91 field reported by OMSA may be empty. The plugin now handles this
92 situation without throwing an internal error.
98 * Storage is no longer allowed to be absent. If the plugin doesn't
99 find a storage controller, it will give an alert. For diskless
100 systems or servers without a Dell controller that OMSA recognizes
101 you will now have to specify '--no-storage' or '--check storage=0'
103 * Report the system revision (if applicable) wherever the model name
104 is printed. E.g. "PowerEdge 2950 III" instead of "PowerEdge 2950".
105 * Small change in search path for omreport: The new location for OMSA
106 6.2.0 and later on Linux will be attempted first.
107 * Small bugfix for the '--check' parameter, if the argument is a
108 filename. The file could not contain a linebreak, this has been
110 * Added an option '--no-storage', which is equivalent to the general
111 option '--check storage=0'.
117 * If a physical disk is a hot spare, display this information in
119 * Report the bus protocol (e.g. SAS, SATA) and media type (e.g. HDD,
120 SDD) for physical disks in the debug output, if applicable
121 * Minor fix for 100GB physical disks, write "100GB" instead of "99GB"
122 * SNMP: Use new features of OMSA 6.3.0 to display occupied and total
123 slots in storage enclosures, if applicable. This information is not
124 available with omreport and check_openmanage will not display this
126 * SNMP: Added new processor IDs from the OMSA 6.3.0 MIBs
127 * SNMP: Use connection tables in a proper way to determine controller
128 and enclosure IDs, for use with physical disks and enclosure
129 components (fan, temp sensors etc.). This fixes a long standing bug
130 for servers with more than one controller, if checked via SNMP.
131 * SNMP: Use the nexus ID as last resort to find the controller for
132 physical disks. Workaround for older, broken OMSA versions.
133 * SNMP: Identify enclosures (e.g. '2:0:0') properly so that the
134 reporting with SNMP corresponds to the same report with omreport.
135 * SNMP: added a couple of workarounds for pre-historic OMSA versions
141 * More fine-grained reporting of temperature warnings for enclosure
143 * Max/min temperature limits for enclosure temp probes are reported in
145 * Report enclosure temperature probes that are "Inactive" as ok
146 * Don't try to print out the reading of enclosure temperature probes
147 if the reading doesn't exist or is not an integer
148 * Report enclosure EMMs that are "Not Installed" as ok, instead of
150 * Corrected typo in the PNP4Nagios template
156 * Remove reporting of which controller a logical drive is "attached"
157 to, since this information can't be reliably extracted via SNMP.
158 * Avoid collecting Lun ID via SNMP for virtual disks, we don't use it
159 * Report total memory and number of dimms in the ok output
160 * Difference in reporting if amperage probes have discrete readings
161 * Workaround for broken amperage probes
162 * Added workaround for bad temperature probes that yields no reading
164 * Get OMSA version via SNMP slightly more efficiently
170 * Added robustness for received SNMP values that are not defined in
171 the MIB. Instead of throwing a perl warning when this happens, the
172 plugin will not report the undefined value.
173 * Defined "Replacing" as a defined state for physical disks in SNMP
174 mode, even though this state is not defined in the MIB. It is
175 reported as such by omreport.
176 * Physical disk brand/model is now reported when the state of the disk
177 is "Rebuilding" or "Replacing".
178 * The state of a physical disk is reported in parentheses when
179 predictive failure is detected. It is useful to know if a disk is
180 online, offline, spare or even failed when predictive failure is
182 * Handling of physical disk predictive failure has been improved
184 * Refactoring of the perfdata code. In conformance with the plugin
185 development guidelines, the UOM (unit of measure) previously
186 reported in the perfdata output has been removed.
187 * The -p or --perfdata option now
188 takes an optional agrument 'minimal', which triggers shorter names
189 for the perfomance data labels. This shortens the output and is a
190 workaround for systems where the amount of output exceeds the 1024
192 * The PNP4Nagios template has been updated. Users of check_openmanage
193 and PNP4Nagios are advised to upgrade. This version of
194 check_openmanage needs the new template.
195 * Lots of other small improvements and updates.
201 * New option '--use-get_table' is added as a workaround for SNMPv3 on
202 Windows using net-snmp. This option will make check_openmanage use
203 the Net::SNMP function get_table() instead of get_entries() to
204 collect information via SNMP.
205 * Include a blacklisting option 'ctrl_pdisk' which takes the
206 controller number as argument. This blacklisting option only works
207 with omreport and is a workaround for broken disk firmwares that
208 contain illegal XML characters. These characters makes openmanage
209 barf and exit with an error. Patch from Bas Couwenberg.
210 * If the blacklisting keyword "all" is supplied for a component type,
211 that component type is not checked at all, i.e. the commands are
212 never executed. This will make check_openmanage execute faster if
213 blacklisting is heavily used.
214 * Option '--htmlinfo' now has a shorter equivalent '-I'
215 * The option '--short-state' now has a shorter equivalent '-S'
221 * Fixed an SNMP bug where the plugin didn't handle OID indexes that
222 were not sequential. Thanks to Gianluca Varenni for reporting.
223 * Fixed an SNMP bug when checking old hardware such as the PE 2650 and
224 PE 750. The controller id for physical drives were collected and
225 displayed incorrectly. This release uses an additional OID to fetch
226 this info, which would otherwise be unavailable. Thanks to Gianluca
227 Varenni for reporting this bug.
228 * Should use %snmp_probestatus, not %snmp_status when checking the
229 status of voltage probes. Thanks to Ken McKinlay for a patch.
230 * Fix when identifying blades via SNMP with very old OMSA
231 versions. Patch from Ken McKinlay.
232 * Better way of finding the ID of physical drives via SNMP
238 * Added support for storport driver version for controllers, only
239 applicable on servers running Windows. A new blacklisting keyword
240 for suppressing storport driver messages was added.
241 * The "all" keyword in blacklisting is now case insensitive.
242 * More fine-grained reporting in the rare case where a controller
243 battery fails during learning and charging states.
244 * New improved way of reporting perl warnings during execution of the
251 * Fix for path to omreport on Linux with OMSA 6.2.0
252 * A couple of other small fixes
258 * Fix for undefined device name for logical drives (thanks to Pontus
260 * Fixed a bug in the PNP4Nagios template, that prevented the template
261 from working with PNP4Nagios 0.6. Thanks to the PNP4Nagios team for
268 * CPU type, family etc. are now reported in case of a CPU failure (and
270 * The debug output now reports Openmanage version and plugin version
276 * New option '-a' or '--all' turns on checking of everything
277 * The manual page (POD info) is removed from the script and is now in
278 a separate file, to make check_openmanage fully ePN compatible
279 * ePN is no longer disabled by default, check_openmanage no longer has
280 an opinion on whether it should run under ePN or not
281 * The '-m' or '--man' option is no longer available
282 * The option '-v' or '--verbose' is renamed to '-d' or '--debug',
283 which makes more sense wrt. its usage
284 * The '-g' or '--global' option is removed. Checking the global health
285 status is now default if applicable
286 * Checking intrusion detection is now turned on by default
287 * The obsolete option '--snmp' is removed
288 * The option '--state' now has a shorter equivalent '-s'
289 * The basename stuff and options '--only-critical' and
290 '--only-warning' are now replaced by an option '--only'
291 * If plugin is run by Nagios, redirect stderr to stdout
292 * Added option '--omreport', that lets the user specify the full path
293 to the omreport binary
294 * Added non-8bit-legacy default search paths for omreport.exe for
296 * Minor changes to the plugin output, for consistency
297 * New blacklisting keyword 'bat_charge' disables warning messages
298 related to controller cache battery charging. Thanks to Robert
299 Heinzmann for a patch.
300 * For blacklisting, the component ID kan now be "ALL", in which all
301 components of that type is blacklisted.
302 * Man page is moved to manual section 8
308 * Fixed a bug that could cause errors and weird results when checking
309 cooling devices (fans) via SNMP. Thanks to Ken McKinlay for spotting
310 this bug and reporting it.
315 * For failed physical drives, check_openmanage will now output the
316 drive's vendor, model and size in GB or TB.
321 * The -s|--snmp option was redundant and no longer does anything. SNMP
322 is triggered automatically if the -H|--hostname option is
323 present. The -s|--snmp option is kept for compatibility, but has no
329 * Added support for performance data (temperatures) from attached
330 storage enclosures such as the MD1000
335 * Fixed a regression in the --htmlinfo option when it is not supplied
341 * New option --htmlinfo adds clickable HTML links in the plugin's
347 * Fixed a regression bug in CPU and power supply reporting that only
348 affects verbose output
349 * If blacklisting is used, the global health check (via the --global
350 option) is now negated. Checking the global health doesn't make
351 sense when one or more components is blacklisted. Thanks to Rene
352 Beaulieu for reporting this bug
353 * The PNP4Nagios template is now included in the tarball and zip
359 * Improved memory error reporting, when using omreport
360 * Collect performance data from pwrmonitoring (amperage probes) that
361 were previously ignored when using omreport
366 * Improved memory error reporting, when using SNMP
367 * Other small ehnancements
372 * The plugin is now compatible with the Nagios embedded Perl
373 interpreter (ePN) in theory. However, the plugin will not not use
374 ePN by default. We don't want any "accidents".
375 * License is now GPLv3, previously only specified as "GPL"
376 * New options --only-critical and --only-warning. With these options
377 the plugin will only print critical or warning alerts, respectively.
378 * Bugfixes and speed enhancements in the storage section, when
379 checking enclosure components via omreport
380 * The --okinfo option is now less verbose and more to the point
381 * Lots of code refactoring for readability, maintainability and
387 * Fixed a bug in the storage section, when checking controllers. This
388 is an obscure bug that only manifests itself in the odd case where a
389 server has multiple controllers, and one of the controllers are
390 missing some of the OIDs, in which case these OIDs will be missing
391 for the other controllers as well. The change is minor and only
392 includes using get_table() instead of get_entries() to collect the
393 SNMP result. Thanks to Stephan Bovet for reporting this bug.
398 * The --perfdata option can now optionally take an argument
399 "multiline", which makes the plugin produce multiline performance
400 data output in a Nagios 3.x way. Not really needed, but the plugin
402 * Added comment within the 10 first lines to disable the nagios
403 embedded perl (ePN) interpreter by default for Nagios 3.x
404 * Improvements in the performance data output. Units are now included
409 * Added --global option, which turns on checking of everything. If
410 used with SNMP, the global system health status is also probed, to
411 protect the user against bugs in the plugin. If used with omreport,
412 the overall chassis health is used.
413 * Support for SNMP version 3
414 * New check added: esmhealth. This checks the overall health of the
415 ESM log, i.e. the fill grade. More than 80% means a warning message
416 * Fixed alert log reporting to use the same format as for the ESM log
417 * Output messages are now sorted by severity
418 * Minor changes in how out-of-date controller firmware/driver is
420 * Code refactoring and cleanup
425 * Use "omreport about" to collect OMSA version. Slightly faster than
426 "omreport system version". This should give a small speedup in
427 certain configurations
428 * Fixed typo in output when a logical drive is rebuilding. Thanks to
429 Andreas Olsson for reporting
430 * Improved reporting of ESM log content
431 * Added omreport.sh as alternate omreport path
432 * Lots of other small fixes and enhancements
434 Plus: A few changes to make the plugin work with old PowerEdge models
435 (e.g. 2550, 2450) and/or old OMSA versions (e.g. version 4.5):
437 * Use the chassisModelName OID to determine if SNMP works (instead of
439 * No longer require a response when checking baseboard type via
440 SNMP. If there is no response, we assume that we're not dealing with
443 Thanks to Christian McHugh for help with testing and debugging this
449 * Use 'omreport system operatingsystem' to collect OS info, instead of
450 'omreport system' version which is incredibly slow. This should speed
451 things up in certain configurations.
452 * A few speedups, don't collect information that isn't needed
458 * New option --linebreak to specify the separator between line in case
460 * Added support for 64bit Windows. Thanks to Patrick Hemmen for a patch
461 * [Patrick Hemmen] Added install.bat for Windows installation
462 * [Patrick Hemmen] Improvements on install.sh. Will now install in
463 /usr/lib64 for x86_64
464 * RPMs are now architecture dependent, because of different libdir
469 * New option -o|--ok-info to display extra information when everything
470 is ok. The plugin can now display storage firmware and driver info,
471 DRAC and BMC firmware, and OMSA version
472 * Support for setting custom minimum temperature thresholds via the
473 -c|--critical and -w|--warning options
474 * Better and more detailed temperature error reporting
475 * Bugfix in the amperage report (including performance data). The
476 plugin now takes into account the correct unit and measurement for
477 amperage probes (other than watts)
478 * New option --port lets the user specify the remote SNMP port number
483 * Regression fix: Use the older Processor Device SNMP OIDs for older
484 PowerEdge models, that don't have the new Processor Device Status
485 OIDs. Thanks to Nicole Hähnel for reporting this bug.
486 * Default output (when there are no alerts) now shows RAC firmware,
487 BMC firmware, info about controllers and enclosures (firmware,
493 * Regression fix: Ignore unoccupied CPU slots with SNMP probing. This
494 fixes a bug introduced in versjon 3.2.1, which would output
495 something like this if one or more CPU slots were empty: CPU 1 needs
501 * Use Processor Device Status Table OIDs instead of Processor Device
502 Table when checking CPUs via SNMP
503 * Bugfix: don't report throttled CPUs as warnings when checking via
504 SNMP (same as for checking locally)
509 * New options --state and --short-state for displaying service state
511 * Lots of small fixes for code readability and maintainability
516 * Support for running natively on Windows (using omreport.exe). Thanks
517 to Peter Jestico for a patch.
518 * Support for compiled Windows version, i.e. check_openmanage.exe is
519 now a legal script name.
520 * Exit with error if script basename is illegal/unknown
521 * Various small fixes
526 * Use of alternate basenames for checking only one class of components
527 * Added support for checking the ESM log via SNMP
528 * Code refactoring for robustness and maintainability
529 * Numerous small fixes and enhancements
530 * Added install script in distribution tarball
535 * The script no longer aborts if it can't get system information via
536 SNMP. Give a warning instead, as this is not a critical error
537 * Increased robustness when checking controllers
542 * Man page fix in the 'check' section. Thanks to Ansgar Dahlen for
544 * Allow invalid command error from 'omreport chassis pwrmonitoring'
545 * Various small fixes
550 * Use unique IDs for storage components with regard to blacklisting,
551 which means that the blacklisting API has changed
552 * Added checks for storage components: connectors (channels),
553 enclosures, enclosure fans, enclosure power supplies, enclosure
554 temperature probes and enclosure management modules (EMMs)
555 * Improved verbose output
556 * New option -t|--timeout for setting the plugin timeout
557 * New option -w|--warning for setting custom temperature warning
559 * New option -c|--critical for setting custom temperature critical
561 * Option --check can no longer be specified in its short form (-c)
562 * Code cleanup and improvements
567 * The workaround for the OMSA bug introduced in OMSA 5.5.0 didn't take
568 multiple controllers into account. This has been fixed.
573 * New option -i|--info prefixes all alerts with the service tag
574 * New option -e|--extinfo gives and extra line of output in case of an
575 alert (model and service tag)
576 * New option --postmsg lets the user specify a post message string,
577 with info such as model, service tag etc.
578 * Options -b|--blacklist and -c|--check can now be specified multiple
579 times (actually quite useful)
584 * Slightly improved output for alerts on logical drives (vdisks)
585 * Now shows a rebuilding physical disk as a warning, as this is
586 usually accompanied by a degraded vdisk. Previous versions didn't
587 show this at all (omreport classifies it as "OK").
592 * Slightly improved output for charging controller batteries
597 * Bugfix for reporting physical drives with predictive failure (both
603 * Fix bug in option handling (ambiguous options)
604 * Slightly improved output if checking the storage subsystem is turned
606 * Don't complain if there are no logical drives. This is OK. Thanks to
607 Jamie Henderson for reporting this
612 * Fix bug in SNMP status level table
617 * Added workaround for a BUG introduced in OpenManage 5.5.0. OM
618 sometimes adds a newline in the controller driver version name,
619 which leads to problems parsing the output. Thanks to Hiren Patel
620 for bringing this to my attention.
625 * (snmp) Improved handling of cases where OM is not working properly
630 * Fixed issue where controller number for physical disks can't be
631 established via SNMP (now identifies as controller no. -1)
636 * Correctly identifies and reports error condition in which OpenManage
637 has stopped working (it happens)
643 * Same options for checking, blacklisting etc. supported with SNMP
644 * Same output with SNMP as with NRPE
649 * Collects performance data if the option '-p' or '--perfdata' is
651 * New blacklisting directives ctrl_fw and ctrl_driver
652 added. Suppresses the "special" warning messages concerning outdated
653 controller firmware and driver. Useful if you can't or won't
659 * Fix getting system model and serial number for newer blades
664 * Three new checks added:
665 - System battery probes (typical CMOS battery). Newer poweredge
667 - Power consumption monitoring (if the server supports it)
668 - ESM log, with same functionality as the alert log check. Disabled
674 * Internal refactoring: use ssv-formatted output from openmanage,
675 resulting in slightly faster execution and increased robustness.
676 * If /usr/bin/omreport doesn't exist, try
677 /opt/dell/srvadmin/oma/bin/omreport.
678 * Allow for no instrumented/redundant power supplies. Needed on
679 low-end poweredge models and blades.
684 * Openmanage reports non-critical warning about throttled CPUs on new
685 hardware models. Most og us use ondemand CPU frequency scaling (with
686 throttled CPUs as a result). This specific non-critical warning (CPU
687 Throttled) is ignored from now on.
688 * Remove superfluous Celcius sign when reporting temperatures.
693 * Accommodate blade systems with no fans or powersupplies, i.e. accept
694 errors from omreport when trying to check fans or powersupplies on
696 * Accommodate newer hardware with slightly different omreport
697 options. Use the newer options if they exist. Not really necessary
698 yet, but deprecated options may be removed in future versions of
704 * When everything is OK, check_openmanage now outputs the same info as
705 Gerhard Lausser's excellent check_hpasm plugin does for HP servers:
707 OK - System: 'poweredge 2850', S/N: 'XXXXXXX', ROM: 'A06
708 10/03/2006', hardware working fine, 2 logical drives, 4 physical