4 * New option '-a' or '--all' turns on checking of everything
5 * The manual page (POD info) is removed from the script and is now in
6 a separate file, to make check_openmanage fully ePN compatible
7 * ePN is no longer disabled by default, check_openmanage no longer has
8 an opinion on whether it should run under ePN or not
9 * The '-m' or '--man' option is no longer available
10 * The option '-v' or '--verbose' is renamed to '-d' or '--debug'
11 * The '-g' or '--global' option is removed. Checking the global health
12 status is now default if applicable
13 * Checking intrusion detection is now turned on by default
14 * The option '--snmp' is removed
15 * The option '--state' now has a shorter equivalent '-s'
16 * The basename stuff and options '--only-critical' and
17 '--only-warning' are now replaced by an option '--only'
18 * If plugin is run by Nagios, redirect stderr to stdout
23 * Fixed a bug that could cause errors and weird results when checking
24 cooling devices (fans) via SNMP. Thanks to Ken McKinlay for spotting
25 this bug and reporting it.
30 * For failed physical drives, check_openmanage will now output the
31 drive's vendor, model and size in GB or TB.
36 * The -s|--snmp option was redundant and no longer does anything. SNMP
37 is triggered automatically if the -H|--hostname option is
38 present. The -s|--snmp option is kept for compatibility, but has no
44 * Added support for performance data (temperatures) from attached
45 storage enclosures such as the MD1000
50 * Fixed a regression in the --htmlinfo option when it is not supplied
56 * New option --htmlinfo adds clickable HTML links in the plugin's
62 * Fixed a regression bug in CPU and power supply reporting that only
63 affects verbose output
64 * If blacklisting is used, the global health check (via the --global
65 option) is now negated. Checking the global health doesn't make
66 sense when one or more components is blacklisted. Thanks to Rene
67 Beaulieu for reporting this bug
68 * The PNP4Nagios template is now included in the tarball and zip
74 * Improved memory error reporting, when using omreport
75 * Collect performance data from pwrmonitoring (amperage probes) that
76 were previously ignored when using omreport
81 * Improved memory error reporting, when using SNMP
82 * Other small ehnancements
87 * The plugin is now compatible with the Nagios embedded Perl
88 interpreter (ePN) in theory. However, the plugin will not not use
89 ePN by default. We don't want any "accidents".
90 * License is now GPLv3, previously only specified as "GPL"
91 * New options --only-critical and --only-warning. With these options
92 the plugin will only print critical or warning alerts, respectively.
93 * Bugfixes and speed enhancements in the storage section, when
94 checking enclosure components via omreport
95 * The --okinfo option is now less verbose and more to the point
96 * Lots of code refactoring for readability, maintainability and
102 * Fixed a bug in the storage section, when checking controllers. This
103 is an obscure bug that only manifests itself in the odd case where a
104 server has multiple controllers, and one of the controllers are
105 missing some of the OIDs, in which case these OIDs will be missing
106 for the other controllers as well. The change is minor and only
107 includes using get_table() instead of get_entries() to collect the
108 SNMP result. Thanks to Stephan Bovet for reporting this bug.
113 * The --perfdata option can now optionally take an argument
114 "multiline", which makes the plugin produce multiline performance
115 data output in a Nagios 3.x way. Not really needed, but the plugin
117 * Added comment within the 10 first lines to disable the nagios
118 embedded perl (ePN) interpreter by default for Nagios 3.x
119 * Improvements in the performance data output. Units are now included
124 * Added --global option, which turns on checking of everything. If
125 used with SNMP, the global system health status is also probed, to
126 protect the user against bugs in the plugin. If used with omreport,
127 the overall chassis health is used.
128 * Support for SNMP version 3
129 * New check added: esmhealth. This checks the overall health of the
130 ESM log, i.e. the fill grade. More than 80% means a warning message
131 * Fixed alert log reporting to use the same format as for the ESM log
132 * Output messages are now sorted by severity
133 * Minor changes in how out-of-date controller firmware/driver is
135 * Code refactoring and cleanup
140 * Use "omreport about" to collect OMSA version. Slightly faster than
141 "omreport system version". This should give a small speedup in
142 certain configurations
143 * Fixed typo in output when a logical drive is rebuilding. Thanks to
144 Andreas Olsson for reporting
145 * Improved reporting of ESM log content
146 * Added omreport.sh as alternate omreport path
147 * Lots of other small fixes and enhancements
149 Plus: A few changes to make the plugin work with old PowerEdge models
150 (e.g. 2550, 2450) and/or old OMSA versions (e.g. version 4.5):
152 * Use the chassisModelName OID to determine if SNMP works (instead of
154 * No longer require a response when checking baseboard type via
155 SNMP. If there is no response, we assume that we're not dealing with
158 Thanks to Christian McHugh for help with testing and debugging this
164 * Use 'omreport system operatingsystem' to collect OS info, instead of
165 'omreport system' version which is incredibly slow. This should speed
166 things up in certain configurations.
167 * A few speedups, don't collect information that isn't needed
173 * New option --linebreak to specify the separator between line in case
175 * Added support for 64bit Windows. Thanks to Patrick Hemmen for a patch
176 * [Patrick Hemmen] Added install.bat for Windows installation
177 * [Patrick Hemmen] Improvements on install.sh. Will now install in
178 /usr/lib64 for x86_64
179 * RPMs are now architecture dependent, because of different libdir
184 * New option -o|--ok-info to display extra information when everything
185 is ok. The plugin can now display storage firmware and driver info,
186 DRAC and BMC firmware, and OMSA version
187 * Support for setting custom minimum temperature thresholds via the
188 -c|--critical and -w|--warning options
189 * Better and more detailed temperature error reporting
190 * Bugfix in the amperage report (including performance data). The
191 plugin now takes into account the correct unit and measurement for
192 amperage probes (other than watts)
193 * New option --port lets the user specify the remote SNMP port number
198 * Regression fix: Use the older Processor Device SNMP OIDs for older
199 PowerEdge models, that don't have the new Processor Device Status
200 OIDs. Thanks to Nicole Hähnel for reporting this bug.
201 * Default output (when there are no alerts) now shows RAC firmware,
202 BMC firmware, info about controllers and enclosures (firmware,
208 * Regression fix: Ignore unoccupied CPU slots with SNMP probing. This
209 fixes a bug introduced in versjon 3.2.1, which would output
210 something like this if one or more CPU slots were empty: CPU 1 needs
216 * Use Processor Device Status Table OIDs instead of Processor Device
217 Table when checking CPUs via SNMP
218 * Bugfix: don't report throttled CPUs as warnings when checking via
219 SNMP (same as for checking locally)
224 * New options --state and --short-state for displaying service state
226 * Lots of small fixes for code readability and maintainability
231 * Support for running natively on Windows (using omreport.exe). Thanks
232 to Peter Jestico for a patch.
233 * Support for compiled Windows version, i.e. check_openmanage.exe is
234 now a legal script name.
235 * Exit with error if script basename is illegal/unknown
236 * Various small fixes
241 * Use of alternate basenames for checking only one class of components
242 * Added support for checking the ESM log via SNMP
243 * Code refactoring for robustness and maintainability
244 * Numerous small fixes and enhancements
245 * Added install script in distribution tarball
250 * The script no longer aborts if it can't get system information via
251 SNMP. Give a warning instead, as this is not a critical error
252 * Increased robustness when checking controllers
257 * Man page fix in the 'check' section. Thanks to Ansgar Dahlen for
259 * Allow invalid command error from 'omreport chassis pwrmonitoring'
260 * Various small fixes
265 * Use unique IDs for storage components with regard to blacklisting,
266 which means that the blacklisting API has changed
267 * Added checks for storage components: connectors (channels),
268 enclosures, enclosure fans, enclosure power supplies, enclosure
269 temperature probes and enclosure management modules (EMMs)
270 * Improved verbose output
271 * New option -t|--timeout for setting the plugin timeout
272 * New option -w|--warning for setting custom temperature warning
274 * New option -c|--critical for setting custom temperature critical
276 * Option --check can no longer be specified in its short form (-c)
277 * Code cleanup and improvements
282 * The workaround for the OMSA bug introduced in OMSA 5.5.0 didn't take
283 multiple controllers into account. This has been fixed.
288 * New option -i|--info prefixes all alerts with the service tag
289 * New option -e|--extinfo gives and extra line of output in case of an
290 alert (model and service tag)
291 * New option --postmsg lets the user specify a post message string,
292 with info such as model, service tag etc.
293 * Options -b|--blacklist and -c|--check can now be specified multiple
294 times (actually quite useful)
299 * Slightly improved output for alerts on logical drives (vdisks)
300 * Now shows a rebuilding physical disk as a warning, as this is
301 usually accompanied by a degraded vdisk. Previous versions didn't
302 show this at all (omreport classifies it as "OK").
307 * Slightly improved output for charging controller batteries
312 * Bugfix for reporting physical drives with predictive failure (both
318 * Fix bug in option handling (ambiguous options)
319 * Slightly improved output if checking the storage subsystem is turned
321 * Don't complain if there are no logical drives. This is OK. Thanks to
322 Jamie Henderson for reporting this
327 * Fix bug in SNMP status level table
332 * Added workaround for a BUG introduced in OpenManage 5.5.0. OM
333 sometimes adds a newline in the controller driver version name,
334 which leads to problems parsing the output. Thanks to Hiren Patel
335 for bringing this to my attention.
340 * (snmp) Improved handling of cases where OM is not working properly
345 * Fixed issue where controller number for physical disks can't be
346 established via SNMP (now identifies as controller no. -1)
351 * Correctly identifies and reports error condition in which OpenManage
352 has stopped working (it happens)
358 * Same options for checking, blacklisting etc. supported with SNMP
359 * Same output with SNMP as with NRPE
364 * Collects performance data if the option '-p' or '--perfdata' is
366 * New blacklisting directives ctrl_fw and ctrl_driver
367 added. Suppresses the "special" warning messages concerning outdated
368 controller firmware and driver. Useful if you can't or won't
374 * Fix getting system model and serial number for newer blades
379 * Three new checks added:
380 - System battery probes (typical CMOS battery). Newer poweredge
382 - Power consumption monitoring (if the server supports it)
383 - ESM log, with same functionality as the alert log check. Disabled
389 * Internal refactoring: use ssv-formatted output from openmanage,
390 resulting in slightly faster execution and increased robustness.
391 * If /usr/bin/omreport doesn't exist, try
392 /opt/dell/srvadmin/oma/bin/omreport.
393 * Allow for no instrumented/redundant power supplies. Needed on
394 low-end poweredge models and blades.
399 * Openmanage reports non-critical warning about throttled CPUs on new
400 hardware models. Most og us use ondemand CPU frequency scaling (with
401 throttled CPUs as a result). This specific non-critical warning (CPU
402 Throttled) is ignored from now on.
403 * Remove superfluous Celcius sign when reporting temperatures.
408 * Accommodate blade systems with no fans or powersupplies, i.e. accept
409 errors from omreport when trying to check fans or powersupplies on
411 * Accommodate newer hardware with slightly different omreport
412 options. Use the newer options if they exist. Not really necessary
413 yet, but deprecated options may be removed in future versions of
419 * When everything is OK, check_openmanage now outputs the same info as
420 Gerhard Lausser's excellent check_hpasm plugin does for HP servers:
422 OK - System: 'poweredge 2850', S/N: 'XXXXXXX', ROM: 'A06
423 10/03/2006', hardware working fine, 2 logical drives, 4 physical