1 # Man page created with:
3 # pod2man -s 3pm -r "`./check_openmanage -V | head -n 1`" -c 'Nagios plugin' check_openmanage.pod check_openmanage.3pm
9 check_openmanage - Nagios plugin for checking the hardware status on
10 Dell servers running OpenManage
14 check_openmanage [I<OPTION>]...
18 check_openmanage is a plugin for Nagios which checks the hardware
19 health of Dell servers running OpenManage Server Administrator
20 (OMSA). The plugin checks the health of the storage subsystem, power
21 supplies, memory modules, temperature probes etc., and gives an alert
22 if any of the components are faulty or operate outside normal
25 check_openmanage is designed to be used by either locally (using NRPE
26 or similar) or remotely (using SNMP). In either mode, the output is
27 (nearly) the same. Note that checking the alert log is not supported
30 =head1 GENERAL OPTIONS
34 =item -t, --timeout I<SECONDS>
36 The number of seconds after which the plugin will abort. Default
37 timeout is 30 seconds if the option is not present.
39 =item -p, --perfdata [I<multline>]
41 Collect performance data. Performance data collected include
42 temperatures (in Celcius) and fan speeds (in rpm). On systems that
43 support it, power consumption is also collected (in Watts).
45 If given the argument C<multiline>, the plugin will output the
46 performance data on multiple lines, for Nagios 3.x and above.
48 =item -w, --warning I<STRING> or I<FILE>
50 Override the machine-default temperature warning thresholds. Syntax is
51 C<id1=max[/min],id2=max[/min],...>. The following example sets warning
52 limits to max 50C for probe 0, and max 45C and min 10C for probe 1:
54 check_openmanage -w 0=50,1=45/10
56 The minimum limit can be omitted, if desired. Most often, you are only
57 interested in setting the maximum thresholds.
59 This parameter can be either a string with the limits, or a file
60 containing the limits string. The option can be specified multiple
63 =item -c, --critical I<STRING> or I<FILE>
65 Override the machine-default temperature critical thresholds. Syntax
66 and behaviour is the same as for warning thresholds described above.
68 =item -o, --ok-info I<NUMBER>
70 This option lets you define how much output you want the plugin to
71 give when everything is OK, i.e. the verbosity level. The default
72 value is 0 (one line of output). The output levels are cumulative.
78 - Only one line (default)
82 - BIOS and firmware info on a separate line
86 - Storage controller and enclosure info on separate lines
90 - OMSA version on separate line
94 The reason that OMSA version is separated from the rest is that
95 finding it requires running a really slow omreport command, when the
96 plugin is run locally via NRPE.
98 =item --omreport I<OMREPORT PATH>
100 Specify full path to omreport, if it is not installed in any of the
101 regular places. Usually this option is only needed on Windows, if
102 omreport is not installed on the C: drive.
106 Prefix any alerts with the service tag.
110 Display a short summary of system information (model and service tag)
113 =item --htmlinfo [I<CODE>]
115 Using this option will make the servicetag and model name into
116 clickable HTML links in the output. The model name link will point to
117 the official Dell documentation for that model, while the servicetag
118 link will point to a website containing support info for that
121 This option takes an optional argument, which should be your country
122 code or C<me> for the middle east. If the country code is omitted the
123 servicetag link will still work, but it will not be speficic for your
124 country or area. Example for Germany:
126 check_openmanage --htmlinfo de
128 If this option is used together with either the I<--extinfo> or
129 I<--info> options, it is particularly useful. Only the most common
130 country codes is supported at this time.
132 =item --postmsg I<STRING> or I<FILE>
134 User specified post message. Useful for displaying arbitrary or
135 various system information at the end of alerts. The argument is
136 either a string with the message, or a file containing that
137 string. You can control the format with the following interpreted
160 Operating system name
164 Operating system release
168 Number of physical drives
172 Number of logical drives
176 Line break. Will be a regular line break if run from a TTY, else an
187 Prefix each alert with its corresponding service state (i.e. warning,
188 critical etc.). This is useful in case of several alerts from the same
193 Same as the B<--state> option above, except that the state is
194 abbreviated to a single letter (W=warning, C=critical etc.).
196 =item --linebreak I<STRING>
198 check_openmanage will sometimes report more than one line, e.g. if
199 there are several alerts. If the script has a TTY, it will use regular
200 linebreaks. If not (which is the case with NRPE) it will use HTML
201 linebreaks. Sometimes it can be useful to control what the plugin uses
202 as a line separator, and this option provides that control.
204 The argument is the exact string to be used as the line
205 separator. There are two exceptions, i.e. two keywords that translates
212 Regular linebreaks, i.e. "\n".
216 HTML linebreaks, i.e. "<br/>".
220 This is a rather special option that is normally not needed. The
221 default behaviour should be sufficient for most users.
225 Debug output. Will report status on everything, even if status is
226 ok. Blacklisted or unchecked components are ignored (i.e. no output).
228 NOTE: This option is intended for diagnostics and debugging purposes
229 only. Do not use this option from within Nagios, i.e. in the Nagios
238 Display version info.
246 =item -H, --hostname I<HOSTNAME>
248 The transport address of the destination SNMP device. Using this
249 option triggers SNMP mode.
251 =item -P, --protocol I<PROTOCOL>
253 SNMP protocol version. This option is optional and expects a digit
254 (i.e. C<1>, C<2> or C<3>) to define the SNMP version. The default is
255 C<2>, i.e. SNMP version 2c.
257 =item -C, --community I<COMMUNITY>
259 This option expects a string that is to be used as the SNMP community
260 name when using SNMP version 1 or 2c. By default the community name
261 is set to C<public> if the option is not present.
265 SNMP port of the remote (monitored) system. Defaults to the well-known
268 =item -U, --username I<SECURITYNAME>
270 [SNMPv3] The User-based Security Model (USM) used by SNMPv3 requires
271 that a securityName be specified. This option is required when using
272 SNMP version 3, and expects a string 1 to 32 octets in lenght.
274 =item --authpassword I<PASSWORD>, --authkey I<KEY>
276 [SNMPv3] By default a securityLevel of C<noAuthNoPriv> is assumed. If
277 the --authpassword option is specified, the securityLevel becomes
278 C<authNoPriv>. The --authpassword option expects a string which is at
279 least 1 octet in length as argument.
281 Optionally, instead of the --authpassword option, the --authkey option
282 can be used so that a plain text password does not have to be
283 specified in a script. The --authkey option expects a hexadecimal
284 string produced by localizing the password with the
285 authoritativeEngineID for the specific destination device. The
286 C<snmpkey> utility included with the Net::SNMP distribution can be
287 used to create the hexadecimal string (see L<snmpkey>).
289 =item --authprotocol I<ALGORITHM>
291 [SNMPv3] Two different hash algorithms are defined by SNMPv3 which can
292 be used by the Security Model for authentication. These algorithms are
293 HMAC-MD5-96 C<MD5> (RFC 1321) and HMAC-SHA-96 C<SHA-1> (NIST FIPS PUB
294 180-1). The default algorithm used by the plugin is HMAC-MD5-96. This
295 behavior can be changed by using this option. The option expects
296 either the string C<md5> or C<sha> to be passed as argument to modify
299 =item --privpassword I<PASSWORD>, --privkey I<KEY>
301 [SNMPv3] By specifying the options --privkey or --privpassword, the
302 securityLevel associated with the object becomes
303 C<authPriv>. According to SNMPv3, privacy requires the use of
304 authentication. Therefore, if either of these two options are present
305 and the --authkey or --authpassword arguments are missing, the
306 creation of the object fails. The --privkey and --privpassword
307 options expect the same input as the --authkey and --authpassword
308 options respectively.
310 =item --privprotocol I<ALGORITHM>
312 [SNMPv3] The User-based Security Model described in RFC 3414 defines a
313 single encryption protocol to be used for privacy. This protocol,
314 CBC-DES C<DES> (NIST FIPS PUB 46-1), is used by default or if the
315 string C<des> is passed to the --privprotocol option. The Net::SNMP
316 module also supports RFC 3826 which describes the use of
317 CFB128-AES-128 C<AES> (NIST FIPS PUB 197) in the USM. The AES
318 encryption protocol can be selected by passing C<aes> or C<aes128> to
319 the --privprotocol option.
321 One of the following arguments are required: des, aes, aes128, 3des,
330 =item -b, --blacklist I<STRING> or I<FILE>
332 Blacklist missing and/or failed components, if you do not plan to fix
333 them. The parameter is either the blacklist string, or a file (that
334 may or may not exist) containing the string. The blacklist string
335 contains component names with component IDs separated by slash
336 (/). Blacklisted components are left unchecked.
338 TIP: Use the option C<-d> (or C<--debug>) to get the blacklist ID for
339 devices. The ID is listed in a separate column in the debug output.
341 NOTE: If blacklisting is in effect, the use of the I<--global> option
348 component1=id1[,id2,...]/component2=id1[,id2,...]/...
352 check_openmanage -b ps=0/fan=3,5/pdisk=1:0:0:1
356 In the example we blacklist powersupply 0, fans 3 and 5, and
357 physical disk 1:0:0:1. Legal component names include:
367 Suppress the special warning message about old controller
368 firmware. Use this if you can not or will not upgrade the firmware.
372 Suppress the special warning message about old controller driver.
373 Particularly useful on systems where you can not upgrade the driver.
381 Logical drive (virtual disk)
385 Controller cache battery
389 Ignore warnings related to the controller cache battery charging
390 cycle, which happens approximately every 40 days on Dell servers.
406 Enclosure power supply
410 Enclosure temperature probe
414 Enclosure management module (EMM)
446 Amperage probe (power consumption monitoring)
460 =item --only I<KEYWORD>
462 This option can be specifed once and expects a keyword. The different
463 keywords and the behaviour of check_openmanage is described below.
469 Print only critical alerts. With this option any warning alerts are
474 Print only warning alerts. With this option any critical alerts are
479 Check all chassis components and nothing else.
487 Only check memory modules
495 Only check power supplies
499 Only check temperatures
503 Only check processors
507 Only check voltage probes
515 Only check power usage
519 Only check chassis intrusion
523 Only check ESM log overall health, i.e. fill grade
527 Only check the event log (ESM) content
531 Only check the alert log content
535 =item --check I<STRING> or I<FILE>
537 This parameter allows you to adjust which components that should be
538 checked at all. This is a rougher approach than blacklisting, which
539 require that you specify component id or index. The parameter should
540 be either a string containing the adjustments, or a file containing
541 the string. No errors are raised if the file does not exist.
543 Note: This option is ignored with alternate basenames.
549 check_openmanage --check storage=0,intrusion=1
553 Legal values are described below, along with the default value.
559 Check storage subsystem (controllers, disks etc.). Default: ON
563 Check memory (dimms). Default: ON
567 Check chassis fans. Default: ON
571 Check power supplies. Default: ON
575 Check temperature sensors. Default: ON
579 Check CPUs. Default: ON
583 Check voltage sensors. Default: ON
587 Check system batteries. Default: ON
591 Check amperage probes. Default: ON
595 Check chassis intrusion. Default: ON
599 Check the ESM log health, i.e. fill grade. Default: ON
603 Check the ESM log content. Default: OFF
607 Check the alert log content. Default: OFF
615 The option C<--debug> (or C<-d>) can be specified to display all
616 monitored components.
620 If SNMP is requested, the perl module Net::SNMP is
621 required. Otherwise, only a regular perl distribution is required to
622 run the script. On the target (monitored) system, Dell Openmanage
623 Server Administrator (OMSA) must be installed and running.
627 If no errors are discovered, a value of 0 (OK) is returned. An exit
628 value of 1 (WARNING) signifies one or more non-critical errors, while
629 2 (CRITICAL) signifies one or more critical errors.
631 The exit value 3 (UNKNOWN) is reserved for errors within the script,
632 or errors getting values from Dell OMSA.
636 Written by Trond H. Amundsen <t.h.amundsen@usit.uio.no>
638 =head1 BUGS AND LIMITATIONS
640 Storage info is not collected or checked on very old PowerEdge models
641 and/or old OMSA versions, due to limitations in OMSA. The overall
642 support on those models/versions by this plugin is not well tested.
644 =head1 INCOMPATIBILITIES
646 The plugin should work with the Nagios embedded perl interpreter
647 (ePN). However, this is not thoroughly tested.
649 =head1 REPORTING BUGS
651 Report bugs to <t.h.amundsen@usit.uio.no>
653 =head1 LICENSE AND COPYRIGHT
655 This program is free software: you can redistribute it and/or modify
656 it under the terms of the GNU General Public License as published by
657 the Free Software Foundation, either version 3 of the License, or (at
658 your option) any later version.
660 This program is distributed in the hope that it will be useful, but
661 WITHOUT ANY WARRANTY; without even the implied warranty of
662 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
663 General Public License for more details.
665 You should have received a copy of the GNU General Public License
666 along with this program. If not, see L<http://www.gnu.org/licenses/>.
670 L<http://folk.uio.no/trondham/software/check_openmanage.html>