4 * Fix counting of components when blacklisting is used. Components
5 should be counted even if blacklisted
6 * Added some unsupported vdisk types to the list. The OMSA MIB
7 identifies these, but lists them as unsupported.
8 * Added option '-B' or '--show-blacklist' to show any blacklistings in
10 * Fixed a bug for checking voltage probes, if the reading is missing
16 * Added more robustness wrt. values from OMSA obtained via SNMP, to
17 avoid internal errors where non-important values are missing.
22 * A few compatibility fixes for OMSA 6.4.0 were added.
27 * Added support for IPv6 when checking via SNMP. IPv6 can be turned on
28 with the option '-6' or '--ipv6'. The default is IPv4 if the option
30 * Added support for TCP when checking vis SNMP. The option '--tcp' can
31 be used to turn on TCP. The default transport protocol is UDP if the
32 option is not present.
33 * The mode of operation (local or SNMP) is shown in the debug
34 output. If SNMP is used, the debug output will also show the SNMP
35 protocol version, IP version and transport protocol (UDP or TCP).
36 * Amperage probe status via SNMP is of type "probe status", not
37 regular status. This has been fixed.
38 * Massive overall robustness improvements to handle OMSA bugs where
39 some information from OMSA is missing.
40 * Memory module enumeration via SNMP changed somewhat to reflect
41 enumeration provided by omreport. This ensures that the plugin's
42 output is identical in SNMP or local mode wrt. dimms IDs.
43 * Fan enumeration via SNMP changed somewhat to reflect enumeration
44 provided by omreport. This ensures that the plugin's output is
45 identical in SNMP or local mode wrt. fan IDs.
50 * Included new check for SD cards. Newer servers such as the R710 can
51 have SD cards installed, these should be monitored. The SD card
52 check is on by default. A new blacklisting keyword 'sd' has been
53 added. The SD card check can be turned off with '--check sdcard=0'.
54 * Handle special cases where power monitoring capability is disabled
55 due to non-redundant and/or non-instrumented power supplies.
56 * For physical disks probed via SNMP, check that values for vendor,
57 product ID and capacity is available before attempting to display
59 * If a physical disk is in sufficiently bad condition, the vendor
60 field reported by OMSA may be empty. The plugin now handles this
61 situation without throwing an internal error.
67 * Storage is no longer allowed to be absent. If the plugin doesn't
68 find a storage controller, it will give an alert. For diskless
69 systems or servers without a Dell controller that OMSA recognizes
70 you will now have to specify '--no-storage' or '--check storage=0'
72 * Report the system revision (if applicable) wherever the model name
73 is printed. E.g. "PowerEdge 2950 III" instead of "PowerEdge 2950".
74 * Small change in search path for omreport: The new location for OMSA
75 6.2.0 and later on Linux will be attempted first.
76 * Small bugfix for the '--check' parameter, if the argument is a
77 filename. The file could not contain a linebreak, this has been
79 * Added an option '--no-storage', which is equivalent to the general
80 option '--check storage=0'.
86 * If a physical disk is a hot spare, display this information in
88 * Report the bus protocol (e.g. SAS, SATA) and media type (e.g. HDD,
89 SDD) for physical disks in the debug output, if applicable
90 * Minor fix for 100GB physical disks, write "100GB" instead of "99GB"
91 * SNMP: Use new features of OMSA 6.3.0 to display occupied and total
92 slots in storage enclosures, if applicable. This information is not
93 available with omreport and check_openmanage will not display this
95 * SNMP: Added new processor IDs from the OMSA 6.3.0 MIBs
96 * SNMP: Use connection tables in a proper way to determine controller
97 and enclosure IDs, for use with physical disks and enclosure
98 components (fan, temp sensors etc.). This fixes a long standing bug
99 for servers with more than one controller, if checked via SNMP.
100 * SNMP: Use the nexus ID as last resort to find the controller for
101 physical disks. Workaround for older, broken OMSA versions.
102 * SNMP: Identify enclosures (e.g. '2:0:0') properly so that the
103 reporting with SNMP corresponds to the same report with omreport.
104 * SNMP: added a couple of workarounds for pre-historic OMSA versions
110 * More fine-grained reporting of temperature warnings for enclosure
112 * Max/min temperature limits for enclosure temp probes are reported in
114 * Report enclosure temperature probes that are "Inactive" as ok
115 * Don't try to print out the reading of enclosure temperature probes
116 if the reading doesn't exist or is not an integer
117 * Report enclosure EMMs that are "Not Installed" as ok, instead of
119 * Corrected typo in the PNP4Nagios template
125 * Remove reporting of which controller a logical drive is "attached"
126 to, since this information can't be reliably extracted via SNMP.
127 * Avoid collecting Lun ID via SNMP for virtual disks, we don't use it
128 * Report total memory and number of dimms in the ok output
129 * Difference in reporting if amperage probes have discrete readings
130 * Workaround for broken amperage probes
131 * Added workaround for bad temperature probes that yields no reading
133 * Get OMSA version via SNMP slightly more efficiently
139 * Added robustness for received SNMP values that are not defined in
140 the MIB. Instead of throwing a perl warning when this happens, the
141 plugin will not report the undefined value.
142 * Defined "Replacing" as a defined state for physical disks in SNMP
143 mode, even though this state is not defined in the MIB. It is
144 reported as such by omreport.
145 * Physical disk brand/model is now reported when the state of the disk
146 is "Rebuilding" or "Replacing".
147 * The state of a physical disk is reported in parentheses when
148 predictive failure is detected. It is useful to know if a disk is
149 online, offline, spare or even failed when predictive failure is
151 * Handling of physical disk predictive failure has been improved
153 * Refactoring of the perfdata code. In conformance with the plugin
154 development guidelines, the UOM (unit of measure) previously
155 reported in the perfdata output has been removed.
156 * The -p or --perfdata option now
157 takes an optional agrument 'minimal', which triggers shorter names
158 for the perfomance data labels. This shortens the output and is a
159 workaround for systems where the amount of output exceeds the 1024
161 * The PNP4Nagios template has been updated. Users of check_openmanage
162 and PNP4Nagios are advised to upgrade. This version of
163 check_openmanage needs the new template.
164 * Lots of other small improvements and updates.
170 * New option '--use-get_table' is added as a workaround for SNMPv3 on
171 Windows using net-snmp. This option will make check_openmanage use
172 the Net::SNMP function get_table() instead of get_entries() to
173 collect information via SNMP.
174 * Include a blacklisting option 'ctrl_pdisk' which takes the
175 controller number as argument. This blacklisting option only works
176 with omreport and is a workaround for broken disk firmwares that
177 contain illegal XML characters. These characters makes openmanage
178 barf and exit with an error. Patch from Bas Couwenberg.
179 * If the blacklisting keyword "all" is supplied for a component type,
180 that component type is not checked at all, i.e. the commands are
181 never executed. This will make check_openmanage execute faster if
182 blacklisting is heavily used.
183 * Option '--htmlinfo' now has a shorter equivalent '-I'
184 * The option '--short-state' now has a shorter equivalent '-S'
190 * Fixed an SNMP bug where the plugin didn't handle OID indexes that
191 were not sequential. Thanks to Gianluca Varenni for reporting.
192 * Fixed an SNMP bug when checking old hardware such as the PE 2650 and
193 PE 750. The controller id for physical drives were collected and
194 displayed incorrectly. This release uses an additional OID to fetch
195 this info, which would otherwise be unavailable. Thanks to Gianluca
196 Varenni for reporting this bug.
197 * Should use %snmp_probestatus, not %snmp_status when checking the
198 status of voltage probes. Thanks to Ken McKinlay for a patch.
199 * Fix when identifying blades via SNMP with very old OMSA
200 versions. Patch from Ken McKinlay.
201 * Better way of finding the ID of physical drives via SNMP
207 * Added support for storport driver version for controllers, only
208 applicable on servers running Windows. A new blacklisting keyword
209 for suppressing storport driver messages was added.
210 * The "all" keyword in blacklisting is now case insensitive.
211 * More fine-grained reporting in the rare case where a controller
212 battery fails during learning and charging states.
213 * New improved way of reporting perl warnings during execution of the
220 * Fix for path to omreport on Linux with OMSA 6.2.0
221 * A couple of other small fixes
227 * Fix for undefined device name for logical drives (thanks to Pontus
229 * Fixed a bug in the PNP4Nagios template, that prevented the template
230 from working with PNP4Nagios 0.6. Thanks to the PNP4Nagios team for
237 * CPU type, family etc. are now reported in case of a CPU failure (and
239 * The debug output now reports Openmanage version and plugin version
245 * New option '-a' or '--all' turns on checking of everything
246 * The manual page (POD info) is removed from the script and is now in
247 a separate file, to make check_openmanage fully ePN compatible
248 * ePN is no longer disabled by default, check_openmanage no longer has
249 an opinion on whether it should run under ePN or not
250 * The '-m' or '--man' option is no longer available
251 * The option '-v' or '--verbose' is renamed to '-d' or '--debug',
252 which makes more sense wrt. its usage
253 * The '-g' or '--global' option is removed. Checking the global health
254 status is now default if applicable
255 * Checking intrusion detection is now turned on by default
256 * The obsolete option '--snmp' is removed
257 * The option '--state' now has a shorter equivalent '-s'
258 * The basename stuff and options '--only-critical' and
259 '--only-warning' are now replaced by an option '--only'
260 * If plugin is run by Nagios, redirect stderr to stdout
261 * Added option '--omreport', that lets the user specify the full path
262 to the omreport binary
263 * Added non-8bit-legacy default search paths for omreport.exe for
265 * Minor changes to the plugin output, for consistency
266 * New blacklisting keyword 'bat_charge' disables warning messages
267 related to controller cache battery charging. Thanks to Robert
268 Heinzmann for a patch.
269 * For blacklisting, the component ID kan now be "ALL", in which all
270 components of that type is blacklisted.
271 * Man page is moved to manual section 8
277 * Fixed a bug that could cause errors and weird results when checking
278 cooling devices (fans) via SNMP. Thanks to Ken McKinlay for spotting
279 this bug and reporting it.
284 * For failed physical drives, check_openmanage will now output the
285 drive's vendor, model and size in GB or TB.
290 * The -s|--snmp option was redundant and no longer does anything. SNMP
291 is triggered automatically if the -H|--hostname option is
292 present. The -s|--snmp option is kept for compatibility, but has no
298 * Added support for performance data (temperatures) from attached
299 storage enclosures such as the MD1000
304 * Fixed a regression in the --htmlinfo option when it is not supplied
310 * New option --htmlinfo adds clickable HTML links in the plugin's
316 * Fixed a regression bug in CPU and power supply reporting that only
317 affects verbose output
318 * If blacklisting is used, the global health check (via the --global
319 option) is now negated. Checking the global health doesn't make
320 sense when one or more components is blacklisted. Thanks to Rene
321 Beaulieu for reporting this bug
322 * The PNP4Nagios template is now included in the tarball and zip
328 * Improved memory error reporting, when using omreport
329 * Collect performance data from pwrmonitoring (amperage probes) that
330 were previously ignored when using omreport
335 * Improved memory error reporting, when using SNMP
336 * Other small ehnancements
341 * The plugin is now compatible with the Nagios embedded Perl
342 interpreter (ePN) in theory. However, the plugin will not not use
343 ePN by default. We don't want any "accidents".
344 * License is now GPLv3, previously only specified as "GPL"
345 * New options --only-critical and --only-warning. With these options
346 the plugin will only print critical or warning alerts, respectively.
347 * Bugfixes and speed enhancements in the storage section, when
348 checking enclosure components via omreport
349 * The --okinfo option is now less verbose and more to the point
350 * Lots of code refactoring for readability, maintainability and
356 * Fixed a bug in the storage section, when checking controllers. This
357 is an obscure bug that only manifests itself in the odd case where a
358 server has multiple controllers, and one of the controllers are
359 missing some of the OIDs, in which case these OIDs will be missing
360 for the other controllers as well. The change is minor and only
361 includes using get_table() instead of get_entries() to collect the
362 SNMP result. Thanks to Stephan Bovet for reporting this bug.
367 * The --perfdata option can now optionally take an argument
368 "multiline", which makes the plugin produce multiline performance
369 data output in a Nagios 3.x way. Not really needed, but the plugin
371 * Added comment within the 10 first lines to disable the nagios
372 embedded perl (ePN) interpreter by default for Nagios 3.x
373 * Improvements in the performance data output. Units are now included
378 * Added --global option, which turns on checking of everything. If
379 used with SNMP, the global system health status is also probed, to
380 protect the user against bugs in the plugin. If used with omreport,
381 the overall chassis health is used.
382 * Support for SNMP version 3
383 * New check added: esmhealth. This checks the overall health of the
384 ESM log, i.e. the fill grade. More than 80% means a warning message
385 * Fixed alert log reporting to use the same format as for the ESM log
386 * Output messages are now sorted by severity
387 * Minor changes in how out-of-date controller firmware/driver is
389 * Code refactoring and cleanup
394 * Use "omreport about" to collect OMSA version. Slightly faster than
395 "omreport system version". This should give a small speedup in
396 certain configurations
397 * Fixed typo in output when a logical drive is rebuilding. Thanks to
398 Andreas Olsson for reporting
399 * Improved reporting of ESM log content
400 * Added omreport.sh as alternate omreport path
401 * Lots of other small fixes and enhancements
403 Plus: A few changes to make the plugin work with old PowerEdge models
404 (e.g. 2550, 2450) and/or old OMSA versions (e.g. version 4.5):
406 * Use the chassisModelName OID to determine if SNMP works (instead of
408 * No longer require a response when checking baseboard type via
409 SNMP. If there is no response, we assume that we're not dealing with
412 Thanks to Christian McHugh for help with testing and debugging this
418 * Use 'omreport system operatingsystem' to collect OS info, instead of
419 'omreport system' version which is incredibly slow. This should speed
420 things up in certain configurations.
421 * A few speedups, don't collect information that isn't needed
427 * New option --linebreak to specify the separator between line in case
429 * Added support for 64bit Windows. Thanks to Patrick Hemmen for a patch
430 * [Patrick Hemmen] Added install.bat for Windows installation
431 * [Patrick Hemmen] Improvements on install.sh. Will now install in
432 /usr/lib64 for x86_64
433 * RPMs are now architecture dependent, because of different libdir
438 * New option -o|--ok-info to display extra information when everything
439 is ok. The plugin can now display storage firmware and driver info,
440 DRAC and BMC firmware, and OMSA version
441 * Support for setting custom minimum temperature thresholds via the
442 -c|--critical and -w|--warning options
443 * Better and more detailed temperature error reporting
444 * Bugfix in the amperage report (including performance data). The
445 plugin now takes into account the correct unit and measurement for
446 amperage probes (other than watts)
447 * New option --port lets the user specify the remote SNMP port number
452 * Regression fix: Use the older Processor Device SNMP OIDs for older
453 PowerEdge models, that don't have the new Processor Device Status
454 OIDs. Thanks to Nicole Hähnel for reporting this bug.
455 * Default output (when there are no alerts) now shows RAC firmware,
456 BMC firmware, info about controllers and enclosures (firmware,
462 * Regression fix: Ignore unoccupied CPU slots with SNMP probing. This
463 fixes a bug introduced in versjon 3.2.1, which would output
464 something like this if one or more CPU slots were empty: CPU 1 needs
470 * Use Processor Device Status Table OIDs instead of Processor Device
471 Table when checking CPUs via SNMP
472 * Bugfix: don't report throttled CPUs as warnings when checking via
473 SNMP (same as for checking locally)
478 * New options --state and --short-state for displaying service state
480 * Lots of small fixes for code readability and maintainability
485 * Support for running natively on Windows (using omreport.exe). Thanks
486 to Peter Jestico for a patch.
487 * Support for compiled Windows version, i.e. check_openmanage.exe is
488 now a legal script name.
489 * Exit with error if script basename is illegal/unknown
490 * Various small fixes
495 * Use of alternate basenames for checking only one class of components
496 * Added support for checking the ESM log via SNMP
497 * Code refactoring for robustness and maintainability
498 * Numerous small fixes and enhancements
499 * Added install script in distribution tarball
504 * The script no longer aborts if it can't get system information via
505 SNMP. Give a warning instead, as this is not a critical error
506 * Increased robustness when checking controllers
511 * Man page fix in the 'check' section. Thanks to Ansgar Dahlen for
513 * Allow invalid command error from 'omreport chassis pwrmonitoring'
514 * Various small fixes
519 * Use unique IDs for storage components with regard to blacklisting,
520 which means that the blacklisting API has changed
521 * Added checks for storage components: connectors (channels),
522 enclosures, enclosure fans, enclosure power supplies, enclosure
523 temperature probes and enclosure management modules (EMMs)
524 * Improved verbose output
525 * New option -t|--timeout for setting the plugin timeout
526 * New option -w|--warning for setting custom temperature warning
528 * New option -c|--critical for setting custom temperature critical
530 * Option --check can no longer be specified in its short form (-c)
531 * Code cleanup and improvements
536 * The workaround for the OMSA bug introduced in OMSA 5.5.0 didn't take
537 multiple controllers into account. This has been fixed.
542 * New option -i|--info prefixes all alerts with the service tag
543 * New option -e|--extinfo gives and extra line of output in case of an
544 alert (model and service tag)
545 * New option --postmsg lets the user specify a post message string,
546 with info such as model, service tag etc.
547 * Options -b|--blacklist and -c|--check can now be specified multiple
548 times (actually quite useful)
553 * Slightly improved output for alerts on logical drives (vdisks)
554 * Now shows a rebuilding physical disk as a warning, as this is
555 usually accompanied by a degraded vdisk. Previous versions didn't
556 show this at all (omreport classifies it as "OK").
561 * Slightly improved output for charging controller batteries
566 * Bugfix for reporting physical drives with predictive failure (both
572 * Fix bug in option handling (ambiguous options)
573 * Slightly improved output if checking the storage subsystem is turned
575 * Don't complain if there are no logical drives. This is OK. Thanks to
576 Jamie Henderson for reporting this
581 * Fix bug in SNMP status level table
586 * Added workaround for a BUG introduced in OpenManage 5.5.0. OM
587 sometimes adds a newline in the controller driver version name,
588 which leads to problems parsing the output. Thanks to Hiren Patel
589 for bringing this to my attention.
594 * (snmp) Improved handling of cases where OM is not working properly
599 * Fixed issue where controller number for physical disks can't be
600 established via SNMP (now identifies as controller no. -1)
605 * Correctly identifies and reports error condition in which OpenManage
606 has stopped working (it happens)
612 * Same options for checking, blacklisting etc. supported with SNMP
613 * Same output with SNMP as with NRPE
618 * Collects performance data if the option '-p' or '--perfdata' is
620 * New blacklisting directives ctrl_fw and ctrl_driver
621 added. Suppresses the "special" warning messages concerning outdated
622 controller firmware and driver. Useful if you can't or won't
628 * Fix getting system model and serial number for newer blades
633 * Three new checks added:
634 - System battery probes (typical CMOS battery). Newer poweredge
636 - Power consumption monitoring (if the server supports it)
637 - ESM log, with same functionality as the alert log check. Disabled
643 * Internal refactoring: use ssv-formatted output from openmanage,
644 resulting in slightly faster execution and increased robustness.
645 * If /usr/bin/omreport doesn't exist, try
646 /opt/dell/srvadmin/oma/bin/omreport.
647 * Allow for no instrumented/redundant power supplies. Needed on
648 low-end poweredge models and blades.
653 * Openmanage reports non-critical warning about throttled CPUs on new
654 hardware models. Most og us use ondemand CPU frequency scaling (with
655 throttled CPUs as a result). This specific non-critical warning (CPU
656 Throttled) is ignored from now on.
657 * Remove superfluous Celcius sign when reporting temperatures.
662 * Accommodate blade systems with no fans or powersupplies, i.e. accept
663 errors from omreport when trying to check fans or powersupplies on
665 * Accommodate newer hardware with slightly different omreport
666 options. Use the newer options if they exist. Not really necessary
667 yet, but deprecated options may be removed in future versions of
673 * When everything is OK, check_openmanage now outputs the same info as
674 Gerhard Lausser's excellent check_hpasm plugin does for HP servers:
676 OK - System: 'poweredge 2850', S/N: 'XXXXXXX', ROM: 'A06
677 10/03/2006', hardware working fine, 2 logical drives, 4 physical