1 # Man page created with:
3 # pod2man -s 8 -r "`./check_openmanage -V | head -n 1`" -c 'Nagios plugin' check_openmanage.pod check_openmanage.8
9 check_openmanage - Nagios plugin for checking the hardware status on
10 Dell servers running OpenManage
14 check_openmanage [I<OPTION>]...
16 check_openmanage -H I<hostname> [I<OPTION>]...
20 check_openmanage is a plugin for Nagios which checks the hardware
21 health of Dell servers running OpenManage Server Administrator
22 (OMSA). The plugin checks the health of the storage subsystem, power
23 supplies, memory modules, temperature probes etc., and gives an alert
24 if any of the components are faulty or operate outside normal
27 check_openmanage is designed to be used by either locally (using NRPE
28 or similar) or remotely (using SNMP). In either mode, the output is
29 (nearly) the same. Note that checking the alert log is not supported
32 =head1 GENERAL OPTIONS
36 =item -t, --timeout I<SECONDS>
38 The number of seconds after which the plugin will abort. Default
39 timeout is 30 seconds if the option is not present.
41 =item -p, --perfdata [I<multline> or I<minimal>]
43 Collect performance data. Performance data collected include
44 temperatures (in Celcius) and fan speeds (in rpm). On systems that
45 support it, power consumption is also collected (in Watts). This
46 option takes one of two arguments, both of which are optional.
48 If the argument C<minimal> is specified, the plugin will use shorter
49 names for the performance data labels, e.g. C<t0> instead of
50 C<temp_0_system_board_ambient>. This can be used as a workaround in
51 cases where the plugin output needs shortening, for example if the
52 1024 character limit of NRPE is reached.
54 If given the argument C<multiline>, the plugin will output the
55 performance data on multiple lines, for Nagios 3.x and above.
57 =item -w, --warning I<STRING> or I<FILE>
59 Override the machine-default temperature warning thresholds. Syntax is
60 C<id1=max[/min],id2=max[/min],...>. The following example sets warning
61 limits to max 50C for probe 0, and max 45C and min 10C for probe 1:
63 check_openmanage -w 0=50,1=45/10
65 The minimum limit can be omitted, if desired. Most often, you are only
66 interested in setting the maximum thresholds.
68 This parameter can be either a string with the limits, or a file
69 containing the limits string. The option can be specified multiple
72 NOTE: This option should only be used to narrow the field of OK
73 temperatures wrt. the OMSA defaults. To expand the field of OK
74 temperatures, increase the OMSA thresholds. See the plugin web page
77 =item -c, --critical I<STRING> or I<FILE>
79 Override the machine-default temperature critical thresholds. Syntax
80 and behaviour is the same as for warning thresholds described above.
82 =item -o, --ok-info I<NUMBER>
84 This option lets you define how much output you want the plugin to
85 give when everything is OK, i.e. the verbosity level. The default
86 value is 0 (one line of output). The output levels are cumulative.
92 - Only one line (default)
96 - BIOS and firmware info on a separate line
100 - Storage controller and enclosure info on separate lines
104 - OMSA version on separate line
108 The reason that OMSA version is separated from the rest is that
109 finding it requires running a really slow omreport command, when the
110 plugin is run locally via NRPE.
112 =item --omreport I<OMREPORT PATH>
114 Specify full path to omreport, if it is not installed in any of the
115 regular places. Usually this option is only needed on Windows, if
116 omreport is not installed on the C: drive.
120 Prefix any alerts with the service tag.
124 Display a short summary of system information (model and service tag)
127 =item -I, --htmlinfo [I<CODE>]
129 Using this option will make the servicetag and model name into
130 clickable HTML links in the output. The model name link will point to
131 the official Dell documentation for that model, while the servicetag
132 link will point to a website containing support info for that
135 This option takes an optional argument, which should be your country
136 code or C<me> for the middle east. If the country code is omitted the
137 servicetag link will still work, but it will not be speficic for your
138 country or area. Example for Germany:
140 check_openmanage --htmlinfo de
142 If this option is used together with either the I<--extinfo> or
143 I<--info> options, it is particularly useful. Only the most common
144 country codes is supported at this time.
146 =item --postmsg I<STRING> or I<FILE>
148 User specified post message. Useful for displaying arbitrary or
149 various system information at the end of alerts. The argument is
150 either a string with the message, or a file containing that
151 string. You can control the format with the following interpreted
174 Operating system name
178 Operating system release
182 Number of physical drives
186 Number of logical drives
190 Line break. Will be a regular line break if run from a TTY, else an
201 Prefix each alert with its corresponding service state (i.e. warning,
202 critical etc.). This is useful in case of several alerts from the same
205 =item -S, --short-state
207 Same as the B<--state> option above, except that the state is
208 abbreviated to a single letter (W=warning, C=critical etc.).
210 =item --linebreak I<STRING>
212 check_openmanage will sometimes report more than one line, e.g. if
213 there are several alerts. If the script has a TTY, it will use regular
214 linebreaks. If not (which is the case with NRPE) it will use HTML
215 linebreaks. Sometimes it can be useful to control what the plugin uses
216 as a line separator, and this option provides that control.
218 The argument is the exact string to be used as the line
219 separator. There are two exceptions, i.e. two keywords that translates
226 Regular linebreaks, i.e. "\n".
230 HTML linebreaks, i.e. "<br/>".
234 This is a rather special option that is normally not needed. The
235 default behaviour should be sufficient for most users.
239 Debug output. Will report status on everything, even if status is
240 ok. Blacklisted or unchecked components are ignored (i.e. no output).
242 NOTE: This option is intended for diagnostics and debugging purposes
243 only. Do not use this option from within Nagios, i.e. in the Nagios
252 Display version info.
260 =item -H, --hostname I<HOSTNAME>
262 The transport address of the destination SNMP device. Using this
263 option triggers SNMP mode.
265 =item -P, --protocol I<PROTOCOL>
267 SNMP protocol version. This option is optional and expects a digit
268 (i.e. C<1>, C<2> or C<3>) to define the SNMP version. The default is
269 C<2>, i.e. SNMP version 2c.
271 =item -C, --community I<COMMUNITY>
273 This option expects a string that is to be used as the SNMP community
274 name when using SNMP version 1 or 2c. By default the community name
275 is set to C<public> if the option is not present.
279 SNMP port of the remote (monitored) system. Defaults to the well-known
282 =item -U, --username I<SECURITYNAME>
284 [SNMPv3] The User-based Security Model (USM) used by SNMPv3 requires
285 that a securityName be specified. This option is required when using
286 SNMP version 3, and expects a string 1 to 32 octets in lenght.
288 =item --authpassword I<PASSWORD>, --authkey I<KEY>
290 [SNMPv3] By default a securityLevel of C<noAuthNoPriv> is assumed. If
291 the --authpassword option is specified, the securityLevel becomes
292 C<authNoPriv>. The --authpassword option expects a string which is at
293 least 1 octet in length as argument.
295 Optionally, instead of the --authpassword option, the --authkey option
296 can be used so that a plain text password does not have to be
297 specified in a script. The --authkey option expects a hexadecimal
298 string produced by localizing the password with the
299 authoritativeEngineID for the specific destination device. The
300 C<snmpkey> utility included with the Net::SNMP distribution can be
301 used to create the hexadecimal string (see L<snmpkey>).
303 =item --authprotocol I<ALGORITHM>
305 [SNMPv3] Two different hash algorithms are defined by SNMPv3 which can
306 be used by the Security Model for authentication. These algorithms are
307 HMAC-MD5-96 C<MD5> (RFC 1321) and HMAC-SHA-96 C<SHA-1> (NIST FIPS PUB
308 180-1). The default algorithm used by the plugin is HMAC-MD5-96. This
309 behavior can be changed by using this option. The option expects
310 either the string C<md5> or C<sha> to be passed as argument to modify
313 =item --privpassword I<PASSWORD>, --privkey I<KEY>
315 [SNMPv3] By specifying the options --privkey or --privpassword, the
316 securityLevel associated with the object becomes
317 C<authPriv>. According to SNMPv3, privacy requires the use of
318 authentication. Therefore, if either of these two options are present
319 and the --authkey or --authpassword arguments are missing, the
320 creation of the object fails. The --privkey and --privpassword
321 options expect the same input as the --authkey and --authpassword
322 options respectively.
324 =item --privprotocol I<ALGORITHM>
326 [SNMPv3] The User-based Security Model described in RFC 3414 defines a
327 single encryption protocol to be used for privacy. This protocol,
328 CBC-DES C<DES> (NIST FIPS PUB 46-1), is used by default or if the
329 string C<des> is passed to the --privprotocol option. The Net::SNMP
330 module also supports RFC 3826 which describes the use of
331 CFB128-AES-128 C<AES> (NIST FIPS PUB 197) in the USM. The AES
332 encryption protocol can be selected by passing C<aes> or C<aes128> to
333 the --privprotocol option.
335 One of the following arguments are required: des, aes, aes128, 3des,
338 =item --use-get_table
340 This option exists as a workaround when using check_openmanage with
341 SNMPv3 on Windows with net-snmp. Using this option will make
342 check_openmanage use the Net::SNMP function get_table() instead of
343 get_entries() while fetching values via SNMP. The latter is faster and
352 =item -b, --blacklist I<STRING> or I<FILE>
354 Blacklist missing and/or failed components, if you do not plan to fix
355 them. The parameter is either the blacklist string, or a file (that
356 may or may not exist) containing the string. The blacklist string
357 contains component names with component IDs separated by slash
358 (/). Blacklisted components are left unchecked.
360 TIP: Use the option C<-d> (or C<--debug>) to get the blacklist ID for
361 devices. The ID is listed in a separate column in the debug output.
363 NOTE: If blacklisting is in effect, the global health of the system is
370 component1=id1[,id2,...]/component2=id1[,id2,...]/...
372 The ID part can also be C<all>, in which all components of that type
377 check_openmanage -b ps=0/fan=3,5/pdisk=1:0:0:1/ctrl_driver=all
381 In the example we blacklist powersupply 0, fans 3 and 5, physical disk
382 1:0:0:1, and warnings about out-of-date drivers for all
383 controllers. Legal component names include:
389 Storage controller. Note that if a controller is blacklisted, all
390 components on that controller (such as physical and logical drives)
391 are blacklisted as well.
395 Suppress the special warning message about old controller
396 firmware. Use this if you can not or will not upgrade the firmware.
400 Suppress the special warning message about old controller driver.
401 Particularly useful on systems where you can not upgrade the driver.
405 Suppress the special warning message about old Storport driver on
410 This blacklisting keyword exists as a possible workaround for physical
411 drives with bad firmware which makes Openmanage choke. It takes the
412 controller number as argument. Use this option to blacklist all
413 physical drives on a specific controller. This blacklisting keyword is
414 only available in local mode, i.e. not with SNMP.
422 Logical drive (virtual disk)
426 Controller cache battery
430 Ignore warnings related to the controller cache battery charging
431 cycle, which happens approximately every 40 days on Dell servers. Note
432 that using this blacklist keyword makes check_openmanage ignore
433 non-critical cache battery errors.
449 Enclosure power supply
453 Enclosure temperature probe
457 Enclosure management module (EMM)
489 Amperage probe (power consumption monitoring)
503 =item --only I<KEYWORD>
505 This option can be specifed once and expects a keyword. The different
506 keywords and the behaviour of check_openmanage is described below.
512 Print only critical alerts. With this option any warning alerts are
517 Print only warning alerts. With this option any critical alerts are
522 Check all chassis components and nothing else.
530 Only check memory modules
538 Only check power supplies
542 Only check temperatures
546 Only check processors
550 Only check voltage probes
558 Only check power usage
562 Only check chassis intrusion
566 Only check ESM log overall health, i.e. fill grade
570 Only check the event log (ESM) content
574 Only check the alert log content
578 =item --check I<STRING> or I<FILE>
580 This parameter allows you to adjust which components that should be
581 checked at all. This is a rougher approach than blacklisting, which
582 require that you specify component id or index. The parameter should
583 be either a string containing the adjustments, or a file containing
584 the string. No errors are raised if the file does not exist.
586 Note: This option is ignored with alternate basenames.
592 check_openmanage --check storage=0,intrusion=1
596 Legal values are described below, along with the default value.
602 Check storage subsystem (controllers, disks etc.). Default: ON
606 Check memory (dimms). Default: ON
610 Check chassis fans. Default: ON
614 Check power supplies. Default: ON
618 Check temperature sensors. Default: ON
622 Check CPUs. Default: ON
626 Check voltage sensors. Default: ON
630 Check system batteries. Default: ON
634 Check amperage probes. Default: ON
638 Check chassis intrusion. Default: ON
642 Check the ESM log health, i.e. fill grade. Default: ON
646 Check the ESM log content. Default: OFF
650 Check the alert log content. Default: OFF
658 The option C<--debug> (or C<-d>) can be specified to display all
659 monitored components.
663 If SNMP is requested, the perl module Net::SNMP is
664 required. Otherwise, only a regular perl distribution is required to
665 run the script. On the target (monitored) system, Dell Openmanage
666 Server Administrator (OMSA) must be installed and running.
670 If no errors are discovered, a value of 0 (OK) is returned. An exit
671 value of 1 (WARNING) signifies one or more non-critical errors, while
672 2 (CRITICAL) signifies one or more critical errors.
674 The exit value 3 (UNKNOWN) is reserved for errors within the script,
675 or errors getting values from Dell OMSA.
679 Written by Trond H. Amundsen <t.h.amundsen@usit.uio.no>
681 =head1 BUGS AND LIMITATIONS
683 Storage info is not collected or checked on very old PowerEdge models
684 and/or old OMSA versions, due to limitations in OMSA. The overall
685 support on those models/versions by this plugin is not well tested.
687 =head1 INCOMPATIBILITIES
689 The plugin should work with the Nagios embedded perl interpreter
690 (ePN). However, this is not thoroughly tested.
692 =head1 REPORTING BUGS
694 Report bugs to <t.h.amundsen@usit.uio.no>
696 =head1 LICENSE AND COPYRIGHT
698 This program is free software: you can redistribute it and/or modify
699 it under the terms of the GNU General Public License as published by
700 the Free Software Foundation, either version 3 of the License, or (at
701 your option) any later version.
703 This program is distributed in the hope that it will be useful, but
704 WITHOUT ANY WARRANTY; without even the implied warranty of
705 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
706 General Public License for more details.
708 You should have received a copy of the GNU General Public License
709 along with this program. If not, see L<http://www.gnu.org/licenses/>.
713 L<http://folk.uio.no/trondham/software/check_openmanage.html>