4 * Added support for storport driver version for controllers, only
5 applicable on servers running Windows. A new blacklisting keyword
6 for suppressing storport driver messages was added.
7 * The "all" keyword in blacklisting is now case insensitive.
8 * More fine-grained reporting in the rare case where a controller
9 battery fails during learning and charging states.
10 * New improved way of reporting perl warnings during execution of the
17 * Fix for path to omreport on Linux with OMSA 6.2.0
18 * A couple of other small fixes
24 * Fix for undefined device name for logical drives (thanks to Pontus
26 * Fixed a bug in the PNP4Nagios template, that prevented the template
27 from working with PNP4Nagios 0.6. Thanks to the PNP4Nagios team for
34 * CPU type, family etc. are now reported in case of a CPU failure (and
36 * The debug output now reports Openmanage version and plugin version
42 * New option '-a' or '--all' turns on checking of everything
43 * The manual page (POD info) is removed from the script and is now in
44 a separate file, to make check_openmanage fully ePN compatible
45 * ePN is no longer disabled by default, check_openmanage no longer has
46 an opinion on whether it should run under ePN or not
47 * The '-m' or '--man' option is no longer available
48 * The option '-v' or '--verbose' is renamed to '-d' or '--debug',
49 which makes more sense wrt. its usage
50 * The '-g' or '--global' option is removed. Checking the global health
51 status is now default if applicable
52 * Checking intrusion detection is now turned on by default
53 * The obsolete option '--snmp' is removed
54 * The option '--state' now has a shorter equivalent '-s'
55 * The basename stuff and options '--only-critical' and
56 '--only-warning' are now replaced by an option '--only'
57 * If plugin is run by Nagios, redirect stderr to stdout
58 * Added option '--omreport', that lets the user specify the full path
59 to the omreport binary
60 * Added non-8bit-legacy default search paths for omreport.exe for
62 * Minor changes to the plugin output, for consistency
63 * New blacklisting keyword 'bat_charge' disables warning messages
64 related to controller cache battery charging. Thanks to Robert
65 Heinzmann for a patch.
66 * For blacklisting, the component ID kan now be "ALL", in which all
67 components of that type is blacklisted.
68 * Man page is moved to manual section 8
74 * Fixed a bug that could cause errors and weird results when checking
75 cooling devices (fans) via SNMP. Thanks to Ken McKinlay for spotting
76 this bug and reporting it.
81 * For failed physical drives, check_openmanage will now output the
82 drive's vendor, model and size in GB or TB.
87 * The -s|--snmp option was redundant and no longer does anything. SNMP
88 is triggered automatically if the -H|--hostname option is
89 present. The -s|--snmp option is kept for compatibility, but has no
95 * Added support for performance data (temperatures) from attached
96 storage enclosures such as the MD1000
101 * Fixed a regression in the --htmlinfo option when it is not supplied
107 * New option --htmlinfo adds clickable HTML links in the plugin's
113 * Fixed a regression bug in CPU and power supply reporting that only
114 affects verbose output
115 * If blacklisting is used, the global health check (via the --global
116 option) is now negated. Checking the global health doesn't make
117 sense when one or more components is blacklisted. Thanks to Rene
118 Beaulieu for reporting this bug
119 * The PNP4Nagios template is now included in the tarball and zip
125 * Improved memory error reporting, when using omreport
126 * Collect performance data from pwrmonitoring (amperage probes) that
127 were previously ignored when using omreport
132 * Improved memory error reporting, when using SNMP
133 * Other small ehnancements
138 * The plugin is now compatible with the Nagios embedded Perl
139 interpreter (ePN) in theory. However, the plugin will not not use
140 ePN by default. We don't want any "accidents".
141 * License is now GPLv3, previously only specified as "GPL"
142 * New options --only-critical and --only-warning. With these options
143 the plugin will only print critical or warning alerts, respectively.
144 * Bugfixes and speed enhancements in the storage section, when
145 checking enclosure components via omreport
146 * The --okinfo option is now less verbose and more to the point
147 * Lots of code refactoring for readability, maintainability and
153 * Fixed a bug in the storage section, when checking controllers. This
154 is an obscure bug that only manifests itself in the odd case where a
155 server has multiple controllers, and one of the controllers are
156 missing some of the OIDs, in which case these OIDs will be missing
157 for the other controllers as well. The change is minor and only
158 includes using get_table() instead of get_entries() to collect the
159 SNMP result. Thanks to Stephan Bovet for reporting this bug.
164 * The --perfdata option can now optionally take an argument
165 "multiline", which makes the plugin produce multiline performance
166 data output in a Nagios 3.x way. Not really needed, but the plugin
168 * Added comment within the 10 first lines to disable the nagios
169 embedded perl (ePN) interpreter by default for Nagios 3.x
170 * Improvements in the performance data output. Units are now included
175 * Added --global option, which turns on checking of everything. If
176 used with SNMP, the global system health status is also probed, to
177 protect the user against bugs in the plugin. If used with omreport,
178 the overall chassis health is used.
179 * Support for SNMP version 3
180 * New check added: esmhealth. This checks the overall health of the
181 ESM log, i.e. the fill grade. More than 80% means a warning message
182 * Fixed alert log reporting to use the same format as for the ESM log
183 * Output messages are now sorted by severity
184 * Minor changes in how out-of-date controller firmware/driver is
186 * Code refactoring and cleanup
191 * Use "omreport about" to collect OMSA version. Slightly faster than
192 "omreport system version". This should give a small speedup in
193 certain configurations
194 * Fixed typo in output when a logical drive is rebuilding. Thanks to
195 Andreas Olsson for reporting
196 * Improved reporting of ESM log content
197 * Added omreport.sh as alternate omreport path
198 * Lots of other small fixes and enhancements
200 Plus: A few changes to make the plugin work with old PowerEdge models
201 (e.g. 2550, 2450) and/or old OMSA versions (e.g. version 4.5):
203 * Use the chassisModelName OID to determine if SNMP works (instead of
205 * No longer require a response when checking baseboard type via
206 SNMP. If there is no response, we assume that we're not dealing with
209 Thanks to Christian McHugh for help with testing and debugging this
215 * Use 'omreport system operatingsystem' to collect OS info, instead of
216 'omreport system' version which is incredibly slow. This should speed
217 things up in certain configurations.
218 * A few speedups, don't collect information that isn't needed
224 * New option --linebreak to specify the separator between line in case
226 * Added support for 64bit Windows. Thanks to Patrick Hemmen for a patch
227 * [Patrick Hemmen] Added install.bat for Windows installation
228 * [Patrick Hemmen] Improvements on install.sh. Will now install in
229 /usr/lib64 for x86_64
230 * RPMs are now architecture dependent, because of different libdir
235 * New option -o|--ok-info to display extra information when everything
236 is ok. The plugin can now display storage firmware and driver info,
237 DRAC and BMC firmware, and OMSA version
238 * Support for setting custom minimum temperature thresholds via the
239 -c|--critical and -w|--warning options
240 * Better and more detailed temperature error reporting
241 * Bugfix in the amperage report (including performance data). The
242 plugin now takes into account the correct unit and measurement for
243 amperage probes (other than watts)
244 * New option --port lets the user specify the remote SNMP port number
249 * Regression fix: Use the older Processor Device SNMP OIDs for older
250 PowerEdge models, that don't have the new Processor Device Status
251 OIDs. Thanks to Nicole Hähnel for reporting this bug.
252 * Default output (when there are no alerts) now shows RAC firmware,
253 BMC firmware, info about controllers and enclosures (firmware,
259 * Regression fix: Ignore unoccupied CPU slots with SNMP probing. This
260 fixes a bug introduced in versjon 3.2.1, which would output
261 something like this if one or more CPU slots were empty: CPU 1 needs
267 * Use Processor Device Status Table OIDs instead of Processor Device
268 Table when checking CPUs via SNMP
269 * Bugfix: don't report throttled CPUs as warnings when checking via
270 SNMP (same as for checking locally)
275 * New options --state and --short-state for displaying service state
277 * Lots of small fixes for code readability and maintainability
282 * Support for running natively on Windows (using omreport.exe). Thanks
283 to Peter Jestico for a patch.
284 * Support for compiled Windows version, i.e. check_openmanage.exe is
285 now a legal script name.
286 * Exit with error if script basename is illegal/unknown
287 * Various small fixes
292 * Use of alternate basenames for checking only one class of components
293 * Added support for checking the ESM log via SNMP
294 * Code refactoring for robustness and maintainability
295 * Numerous small fixes and enhancements
296 * Added install script in distribution tarball
301 * The script no longer aborts if it can't get system information via
302 SNMP. Give a warning instead, as this is not a critical error
303 * Increased robustness when checking controllers
308 * Man page fix in the 'check' section. Thanks to Ansgar Dahlen for
310 * Allow invalid command error from 'omreport chassis pwrmonitoring'
311 * Various small fixes
316 * Use unique IDs for storage components with regard to blacklisting,
317 which means that the blacklisting API has changed
318 * Added checks for storage components: connectors (channels),
319 enclosures, enclosure fans, enclosure power supplies, enclosure
320 temperature probes and enclosure management modules (EMMs)
321 * Improved verbose output
322 * New option -t|--timeout for setting the plugin timeout
323 * New option -w|--warning for setting custom temperature warning
325 * New option -c|--critical for setting custom temperature critical
327 * Option --check can no longer be specified in its short form (-c)
328 * Code cleanup and improvements
333 * The workaround for the OMSA bug introduced in OMSA 5.5.0 didn't take
334 multiple controllers into account. This has been fixed.
339 * New option -i|--info prefixes all alerts with the service tag
340 * New option -e|--extinfo gives and extra line of output in case of an
341 alert (model and service tag)
342 * New option --postmsg lets the user specify a post message string,
343 with info such as model, service tag etc.
344 * Options -b|--blacklist and -c|--check can now be specified multiple
345 times (actually quite useful)
350 * Slightly improved output for alerts on logical drives (vdisks)
351 * Now shows a rebuilding physical disk as a warning, as this is
352 usually accompanied by a degraded vdisk. Previous versions didn't
353 show this at all (omreport classifies it as "OK").
358 * Slightly improved output for charging controller batteries
363 * Bugfix for reporting physical drives with predictive failure (both
369 * Fix bug in option handling (ambiguous options)
370 * Slightly improved output if checking the storage subsystem is turned
372 * Don't complain if there are no logical drives. This is OK. Thanks to
373 Jamie Henderson for reporting this
378 * Fix bug in SNMP status level table
383 * Added workaround for a BUG introduced in OpenManage 5.5.0. OM
384 sometimes adds a newline in the controller driver version name,
385 which leads to problems parsing the output. Thanks to Hiren Patel
386 for bringing this to my attention.
391 * (snmp) Improved handling of cases where OM is not working properly
396 * Fixed issue where controller number for physical disks can't be
397 established via SNMP (now identifies as controller no. -1)
402 * Correctly identifies and reports error condition in which OpenManage
403 has stopped working (it happens)
409 * Same options for checking, blacklisting etc. supported with SNMP
410 * Same output with SNMP as with NRPE
415 * Collects performance data if the option '-p' or '--perfdata' is
417 * New blacklisting directives ctrl_fw and ctrl_driver
418 added. Suppresses the "special" warning messages concerning outdated
419 controller firmware and driver. Useful if you can't or won't
425 * Fix getting system model and serial number for newer blades
430 * Three new checks added:
431 - System battery probes (typical CMOS battery). Newer poweredge
433 - Power consumption monitoring (if the server supports it)
434 - ESM log, with same functionality as the alert log check. Disabled
440 * Internal refactoring: use ssv-formatted output from openmanage,
441 resulting in slightly faster execution and increased robustness.
442 * If /usr/bin/omreport doesn't exist, try
443 /opt/dell/srvadmin/oma/bin/omreport.
444 * Allow for no instrumented/redundant power supplies. Needed on
445 low-end poweredge models and blades.
450 * Openmanage reports non-critical warning about throttled CPUs on new
451 hardware models. Most og us use ondemand CPU frequency scaling (with
452 throttled CPUs as a result). This specific non-critical warning (CPU
453 Throttled) is ignored from now on.
454 * Remove superfluous Celcius sign when reporting temperatures.
459 * Accommodate blade systems with no fans or powersupplies, i.e. accept
460 errors from omreport when trying to check fans or powersupplies on
462 * Accommodate newer hardware with slightly different omreport
463 options. Use the newer options if they exist. Not really necessary
464 yet, but deprecated options may be removed in future versions of
470 * When everything is OK, check_openmanage now outputs the same info as
471 Gerhard Lausser's excellent check_hpasm plugin does for HP servers:
473 OK - System: 'poweredge 2850', S/N: 'XXXXXXX', ROM: 'A06
474 10/03/2006', hardware working fine, 2 logical drives, 4 physical