|
[-]
[+]
|
Changed |
check_openmanage.changes
|
|
|
|
[-]
[+]
|
Changed |
check_openmanage.spec
^
|
|
|
|
[-]
[+]
|
Deleted |
check_openmanage-3.7.5.tar.bz2/check_openmanage.8
^
|
| @@ -1,781 +0,0 @@
-.\" Automatically generated by Pod::Man 2.22 (Pod::Simple 3.13)
-.\"
-.\" Standard preamble:
-.\" ========================================================================
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Vb \" Begin verbatim text
-.ft CW
-.nf
-.ne \\$1
-..
-.de Ve \" End verbatim text
-.ft R
-.fi
-..
-.\" Set up some character translations and predefined strings. \*(-- will
-.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
-.\" double quote, and \*(R" will give a right double quote. \*(C+ will
-.\" give a nicer C++. Capital omega is used to do unbreakable dashes and
-.\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
-.\" nothing in troff, for use with C<>.
-.tr \(*W-
-.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
-.ie n \{\
-. ds -- \(*W-
-. ds PI pi
-. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
-. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
-. ds L" ""
-. ds R" ""
-. ds C` ""
-. ds C' ""
-'br\}
-.el\{\
-. ds -- \|\(em\|
-. ds PI \(*p
-. ds L" ``
-. ds R" ''
-'br\}
-.\"
-.\" Escape single quotes in literal strings from groff's Unicode transform.
-.ie \n(.g .ds Aq \(aq
-.el .ds Aq '
-.\"
-.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
-.\" entries marked with X<> in POD. Of course, you'll have to process the
-.\" output yourself in some meaningful fashion.
-.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
-..
-. nr % 0
-. rr F
-.\}
-.el \{\
-. de IX
-..
-.\}
-.\"
-.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
-.\" Fear. Run. Save yourself. No user-serviceable parts.
-. \" fudge factors for nroff and troff
-.if n \{\
-. ds #H 0
-. ds #V .8m
-. ds #F .3m
-. ds #[ \f1
-. ds #] \fP
-.\}
-.if t \{\
-. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
-. ds #V .6m
-. ds #F 0
-. ds #[ \&
-. ds #] \&
-.\}
-. \" simple accents for nroff and troff
-.if n \{\
-. ds ' \&
-. ds ` \&
-. ds ^ \&
-. ds , \&
-. ds ~ ~
-. ds /
-.\}
-.if t \{\
-. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
-. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
-. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
-. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
-. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
-. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
-.\}
-. \" troff and (daisy-wheel) nroff accents
-.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
-.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
-.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
-.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
-.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
-.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
-.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
-.ds ae a\h'-(\w'a'u*4/10)'e
-.ds Ae A\h'-(\w'A'u*4/10)'E
-. \" corrections for vroff
-.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
-.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
-. \" for low resolution devices (crt and lpr)
-.if \n(.H>23 .if \n(.V>19 \
-\{\
-. ds : e
-. ds 8 ss
-. ds o a
-. ds d- d\h'-1'\(ga
-. ds D- D\h'-1'\(hy
-. ds th \o'bp'
-. ds Th \o'LP'
-. ds ae ae
-. ds Ae AE
-.\}
-.rm #[ #] #H #V #F C
-.\" ========================================================================
-.\"
-.IX Title "CHECK_OPENMANAGE 8"
-.TH CHECK_OPENMANAGE 8 "2012-03-09" "check_openmanage 3.7.5" "Nagios plugin"
-.\" For nroff, turn off justification. Always turn off hyphenation; it makes
-.\" way too many mistakes in technical documents.
-.if n .ad l
-.nh
-.SH "NAME"
-check_openmanage \- Nagios plugin for checking the hardware status on
- Dell servers running OpenManage
-.SH "SYNOPSIS"
-.IX Header "SYNOPSIS"
-check_openmanage [\fI\s-1OPTION\s0\fR]...
-.PP
-check_openmanage \-H \fIhostname\fR [\fI\s-1OPTION\s0\fR]...
-.SH "DESCRIPTION"
-.IX Header "DESCRIPTION"
-check_openmanage is a plugin for Nagios which checks the hardware
-health of Dell servers running OpenManage Server Administrator
-(\s-1OMSA\s0). The plugin checks the health of the storage subsystem, power
-supplies, memory modules, temperature probes etc., and gives an alert
-if any of the components are faulty or operate outside normal
-parameters.
-.PP
-check_openmanage is designed to be used by either locally (using \s-1NRPE\s0
-or similar) or remotely (using \s-1SNMP\s0). In either mode, the output is
-(nearly) the same. Note that checking the alert log is not supported
-in \s-1SNMP\s0 mode.
-.SH "GENERAL OPTIONS"
-.IX Header "GENERAL OPTIONS"
-.IP "\-f, \-\-config \fI\s-1FILE\s0\fR" 4
-.IX Item "-f, --config FILE"
-Specify a configuration file. For reference on the config file syntax
-and options, consult the \fIcheck_openmanage.conf\fR\|(5) manual page.
-.IP "\-t, \-\-timeout \fI\s-1SECONDS\s0\fR" 4
-.IX Item "-t, --timeout SECONDS"
-The number of seconds after which the plugin will abort. Default
-timeout is 30 seconds if the option is not present.
-.IP "\-p, \-\-perfdata [\fImultline\fR or \fIminimal\fR]" 4
-.IX Item "-p, --perfdata [multline or minimal]"
-Collect performance data. Performance data collected include
-temperatures (in Celsius) and fan speeds (in rpm). On systems that
-support it, power consumption is also collected (in Watts). This
-option takes one of two arguments, both of which are optional.
-.Sp
-If the argument \f(CW\*(C`minimal\*(C'\fR is specified, the plugin will use shorter
-names for the performance data labels, e.g. \f(CW\*(C`t0\*(C'\fR instead of
-\&\f(CW\*(C`temp_0_system_board_ambient\*(C'\fR. This can be used as a workaround in
-cases where the plugin output needs shortening, for example if the
-1024 character limit of \s-1NRPE\s0 is reached.
-.Sp
-If given the argument \f(CW\*(C`multiline\*(C'\fR, the plugin will output the
-performance data on multiple lines, for Nagios 3.x and above.
-.IP "\-\-legacy\-perfdata" 4
-.IX Item "--legacy-perfdata"
-With version 3.7.0, performance data output changed. The new format is
-not compatible with the old format. Users who wish to postpone
-switching to the new performance data \s-1API\s0 may set this option.
-.IP "\-w, \-\-warning \fI\s-1STRING\s0\fR or \fI\s-1FILE\s0\fR" 4
-.IX Item "-w, --warning STRING or FILE"
-Override the machine-default temperature warning thresholds. Syntax is
-\&\f(CW\*(C`id1=max[/min],id2=max[/min],...\*(C'\fR. The following example sets warning
-limits to max 50C for probe 0, and max 45C and min 10C for probe 1:
-.Sp
-check_openmanage \-w 0=50,1=45/10
-.Sp
-The minimum limit can be omitted, if desired. Most often, you are only
-interested in setting the maximum thresholds.
-.Sp
-This parameter can be either a string with the limits, or a file
-containing the limits string. The option can be specified multiple
-times.
-.Sp
-\&\s-1NOTE:\s0 This option should only be used to narrow the field of \s-1OK\s0
-temperatures wrt. the \s-1OMSA\s0 defaults. To expand the field of \s-1OK\s0
-temperatures, increase the \s-1OMSA\s0 thresholds. See the plugin web page
-for more information.
-.IP "\-c, \-\-critical \fI\s-1STRING\s0\fR or \fI\s-1FILE\s0\fR" 4
-.IX Item "-c, --critical STRING or FILE"
-Override the machine-default temperature critical thresholds. Syntax
-and behaviour is the same as for warning thresholds described above.
-.IP "\-F, \-\-fahrenheit" 4
-.IX Item "-F, --fahrenheit"
-Set Fahrenheit as unit for all temperatures. This option will override
-the \f(CW\*(C`\-\-tempunit\*(C'\fR option, if used simultaneously.
-.IP "\-\-tempunit \fI\s-1CHAR\s0\fR" 4
-.IX Item "--tempunit CHAR"
-Set temperature unit. Legal values are \f(CW\*(C`F\*(C'\fR for Fahrenheit, \f(CW\*(C`C\*(C'\fR for
-Celsius, \f(CW\*(C`K\*(C'\fR for Kelvin and \f(CW\*(C`R\*(C'\fR for Rankine.
-.IP "\-o, \-\-ok\-info \fI\s-1NUMBER\s0\fR" 4
-.IX Item "-o, --ok-info NUMBER"
-This option lets you define how much output you want the plugin to
-give when everything is \s-1OK\s0, i.e. the verbosity level. The default
-value is 0 (one line of output). The output levels are cumulative.
-.RS 4
-.IP "\fB0\fR" 4
-.IX Item "0"
-\&\- Only one line (default)
-.IP "\fB1\fR" 4
-.IX Item "1"
-\&\- \s-1BIOS\s0 and firmware info on a separate line
-.IP "\fB2\fR" 4
-.IX Item "2"
-\&\- Storage controller and enclosure info on separate lines
-.IP "\fB3\fR" 4
-.IX Item "3"
-\&\- \s-1OMSA\s0 version on separate line
-.RE
-.RS 4
-.Sp
-The reason that \s-1OMSA\s0 version is separated from the rest is that
-finding it requires running a really slow omreport command, when the
-plugin is run locally via \s-1NRPE\s0.
-.RE
-.IP "\-B, \-\-show\-blacklist" 4
-.IX Item "-B, --show-blacklist"
-If used together with blacklisting, this option will make the plugin
-output all blacklistings that are being used. The output will have the
-correct blacklisting syntax, and will make it easy to maintain control
-over which blacklistings that are used for each server, as any
-blacklistings can be viewed from Nagios.
-.Sp
-When blacklisting is not used, this option has no effect.
-.IP "\-\-omreport \fI\s-1OMREPORT\s0 \s-1PATH\s0\fR" 4
-.IX Item "--omreport OMREPORT PATH"
-Specify full path to omreport, if it is not installed in any of the
-regular places. Usually this option is only needed on Windows, if
-omreport is not installed on the C: drive.
-.IP "\-i, \-\-info" 4
-.IX Item "-i, --info"
-Prefix any alerts with the service tag.
-.IP "\-e, \-\-extinfo" 4
-.IX Item "-e, --extinfo"
-Display a short summary of system information (model and service tag)
-in case of an alert.
-.IP "\-I, \-\-htmlinfo [\fI\s-1CODE\s0\fR]" 4
-.IX Item "-I, --htmlinfo [CODE]"
-Using this option will make the servicetag and model name into
-clickable \s-1HTML\s0 links in the output. The model name link will point to
-the official Dell documentation for that model, while the servicetag
-link will point to a website containing support info for that
-particular server.
-.Sp
-This option takes an optional argument, which should be your country
-code or \f(CW\*(C`me\*(C'\fR for the middle east. If the country code is omitted the
-servicetag link will still work, but it will not be speficic for your
-country or area. Example for Germany:
-.Sp
-.Vb 1
-\& check_openmanage \-\-htmlinfo de
-.Ve
-.Sp
-If this option is used together with either the \fI\-\-extinfo\fR or
-\&\fI\-\-info\fR options, it is particularly useful. Only the most common
-country codes is supported at this time.
-.IP "\-\-postmsg \fI\s-1STRING\s0\fR or \fI\s-1FILE\s0\fR" 4
-.IX Item "--postmsg STRING or FILE"
-User specified post message. Useful for displaying arbitrary or
-various system information at the end of alerts. The argument is
-either a string with the message, or a file containing that
-string. You can control the format with the following interpreted
-sequences:
-.RS 4
-.ie n .IP "\fB\fB%m\fB\fR" 4
-.el .IP "\fB\f(CB%m\fB\fR" 4
-.IX Item "%m"
-System model
-.ie n .IP "\fB\fB%s\fB\fR" 4
-.el .IP "\fB\f(CB%s\fB\fR" 4
-.IX Item "%s"
-Service tag
-.ie n .IP "\fB\fB%b\fB\fR" 4
-.el .IP "\fB\f(CB%b\fB\fR" 4
-.IX Item "%b"
-\&\s-1BIOS\s0 version
-.ie n .IP "\fB\fB%d\fB\fR" 4
-.el .IP "\fB\f(CB%d\fB\fR" 4
-.IX Item "%d"
-\&\s-1BIOS\s0 release date
-.ie n .IP "\fB\fB%o\fB\fR" 4
-.el .IP "\fB\f(CB%o\fB\fR" 4
-.IX Item "%o"
-Operating system name
-.ie n .IP "\fB\fB%r\fB\fR" 4
-.el .IP "\fB\f(CB%r\fB\fR" 4
-.IX Item "%r"
-Operating system release
-.ie n .IP "\fB\fB%p\fB\fR" 4
-.el .IP "\fB\f(CB%p\fB\fR" 4
-.IX Item "%p"
-Number of physical drives
-.ie n .IP "\fB\fB%l\fB\fR" 4
-.el .IP "\fB\f(CB%l\fB\fR" 4
-.IX Item "%l"
-Number of logical drives
-.ie n .IP "\fB\fB%n\fB\fR" 4
-.el .IP "\fB\f(CB%n\fB\fR" 4
-.IX Item "%n"
-Line break. Will be a regular line break if run from a \s-1TTY\s0, else an
-\&\s-1HTML\s0 line break.
-.IP "\fB%%\fR" 4
-.IX Item "%%"
-A literal \f(CW\*(C`%\*(C'\fR
-.RE
-.RS 4
-.RE
-.IP "\-s, \-\-state" 4
-.IX Item "-s, --state"
-Prefix each alert with its corresponding service state (i.e. warning,
-critical etc.). This is useful in case of several alerts from the same
-monitored system.
-.IP "\-S, \-\-short\-state" 4
-.IX Item "-S, --short-state"
-Same as the \fB\-\-state\fR option above, except that the state is
-abbreviated to a single letter (W=warning, C=critical etc.).
-.IP "\-\-hide\-servicetag" 4
-.IX Item "--hide-servicetag"
-This option will replace the servicetag (serial number) in the output
-with \f(CW\*(C`XXXXXXX\*(C'\fR. Use this option to suppress or censor the servicetag
-in the plugin output.
-.IP "\-\-linebreak \fI\s-1STRING\s0\fR" 4
-.IX Item "--linebreak STRING"
-check_openmanage will sometimes report more than one line, e.g. if
-there are several alerts. If the script has a \s-1TTY\s0, it will use regular
-linebreaks. If not (which is the case with \s-1NRPE\s0) it will use \s-1HTML\s0
-linebreaks. Sometimes it can be useful to control what the plugin uses
-as a line separator, and this option provides that control.
-.Sp
-The argument is the exact string to be used as the line
-separator. There are two exceptions, i.e. two keywords that translates
-to the following:
-.RS 4
-.IP "\fB\s-1REG\s0\fR" 4
-.IX Item "REG"
-Regular linebreaks, i.e. \*(L"\en\*(R".
-.IP "\fB\s-1HTML\s0\fR" 4
-.IX Item "HTML"
-\&\s-1HTML\s0 linebreaks, i.e. \*(L"<br/>\*(R".
-.RE
-.RS 4
-.Sp
-This is a rather special option that is normally not needed. The
-default behaviour should be sufficient for most users.
-.RE
-.IP "\-d, \-\-debug" 4
-.IX Item "-d, --debug"
-Debug output. Will report status on everything, even if status is
-ok. Blacklisted or unchecked components are ignored (i.e. no output).
-.Sp
-\&\s-1NOTE:\s0 This option is intended for diagnostics and debugging purposes
-only. Do not use this option from within Nagios, i.e. in the Nagios
-config.
-.IP "\-h, \-\-help" 4
-.IX Item "-h, --help"
-Display help text.
-.IP "\-V, \-\-version" 4
-.IX Item "-V, --version"
-Display version info.
-.SH "SNMP OPTIONS"
-.IX Header "SNMP OPTIONS"
-.IP "\-H, \-\-hostname \fI\s-1HOSTNAME\s0\fR" 4
-.IX Item "-H, --hostname HOSTNAME"
-The transport address of the destination \s-1SNMP\s0 device. Using this
-option triggers \s-1SNMP\s0 mode.
-.IP "\-P, \-\-protocol \fI\s-1PROTOCOL\s0\fR" 4
-.IX Item "-P, --protocol PROTOCOL"
-\&\s-1SNMP\s0 protocol version. This option is optional and expects either of
-the following:
-.Sp
-.Vb 3
-\& "1" : SNMP version 1
-\& "2c" or "2" : SNMP version 2c
-\& "3" : SNMP version 3
-.Ve
-.Sp
-The default is \f(CW\*(C`2c\*(C'\fR.
-.IP "\-C, \-\-community \fI\s-1COMMUNITY\s0\fR" 4
-.IX Item "-C, --community COMMUNITY"
-This option expects a string that is to be used as the \s-1SNMP\s0 community
-name when using \s-1SNMP\s0 version 1 or 2c. By default the community name
-is set to \f(CW\*(C`public\*(C'\fR if the option is not present.
-.IP "\-\-port \fI\s-1PORT\s0\fR" 4
-.IX Item "--port PORT"
-\&\s-1SNMP\s0 port of the remote (monitored) system. Defaults to the well-known
-\&\s-1SNMP\s0 port 161.
-.IP "\-6, \-\-ipv6" 4
-.IX Item "-6, --ipv6"
-This option will cause the plugin to use IPv6. The default is IPv4 if
-the option is not present.
-.IP "\-\-tcp" 4
-.IX Item "--tcp"
-This option will cause the plugin to use \s-1TCP\s0 as transport
-protocol. The default is \s-1UDP\s0 if the option is not present.
-.IP "\-U, \-\-username \fI\s-1SECURITYNAME\s0\fR" 4
-.IX Item "-U, --username SECURITYNAME"
-[SNMPv3] The User-based Security Model (\s-1USM\s0) used by SNMPv3 requires
-that a securityName be specified. This option is required when using
-\&\s-1SNMP\s0 version 3, and expects a string 1 to 32 octets in lenght.
-.IP "\-\-authpassword \fI\s-1PASSWORD\s0\fR, \-\-authkey \fI\s-1KEY\s0\fR" 4
-.IX Item "--authpassword PASSWORD, --authkey KEY"
-[SNMPv3] By default a securityLevel of \f(CW\*(C`noAuthNoPriv\*(C'\fR is assumed. If
-the \-\-authpassword option is specified, the securityLevel becomes
-\&\f(CW\*(C`authNoPriv\*(C'\fR. The \-\-authpassword option expects a string which is at
-least 1 octet in length as argument.
-.Sp
-Optionally, instead of the \-\-authpassword option, the \-\-authkey option
-can be used so that a plain text password does not have to be
-specified in a script. The \-\-authkey option expects a hexadecimal
-string produced by localizing the password with the
-authoritativeEngineID for the specific destination device. The
-\&\f(CW\*(C`snmpkey\*(C'\fR utility included with the Net::SNMP distribution can be
-used to create the hexadecimal string (see snmpkey).
-.IP "\-\-authprotocol \fI\s-1ALGORITHM\s0\fR" 4
-.IX Item "--authprotocol ALGORITHM"
-[SNMPv3] Two different hash algorithms are defined by SNMPv3 which can
-be used by the Security Model for authentication. These algorithms are
-\&\s-1HMAC\-MD5\-96\s0 \f(CW\*(C`MD5\*(C'\fR (\s-1RFC\s0 1321) and \s-1HMAC\-SHA\-96\s0 \f(CW\*(C`SHA\-1\*(C'\fR (\s-1NIST\s0 \s-1FIPS\s0 \s-1PUB\s0
-180\-1). The default algorithm used by the plugin is \s-1HMAC\-MD5\-96\s0. This
-behavior can be changed by using this option. The option expects
-either the string \f(CW\*(C`md5\*(C'\fR or \f(CW\*(C`sha\*(C'\fR to be passed as argument to modify
-the hash algorithm.
-.IP "\-\-privpassword \fI\s-1PASSWORD\s0\fR, \-\-privkey \fI\s-1KEY\s0\fR" 4
-.IX Item "--privpassword PASSWORD, --privkey KEY"
-[SNMPv3] By specifying the options \-\-privkey or \-\-privpassword, the
-securityLevel associated with the object becomes
-\&\f(CW\*(C`authPriv\*(C'\fR. According to SNMPv3, privacy requires the use of
-authentication. Therefore, if either of these two options are present
-and the \-\-authkey or \-\-authpassword arguments are missing, the
-creation of the object fails. The \-\-privkey and \-\-privpassword
-options expect the same input as the \-\-authkey and \-\-authpassword
-options respectively.
-.IP "\-\-privprotocol \fI\s-1ALGORITHM\s0\fR" 4
-.IX Item "--privprotocol ALGORITHM"
-[SNMPv3] The User-based Security Model described in \s-1RFC\s0 3414 defines a
-single encryption protocol to be used for privacy. This protocol,
-CBC-DES \f(CW\*(C`DES\*(C'\fR (\s-1NIST\s0 \s-1FIPS\s0 \s-1PUB\s0 46\-1), is used by default or if the
-string \f(CW\*(C`des\*(C'\fR is passed to the \-\-privprotocol option. The Net::SNMP
-module also supports \s-1RFC\s0 3826 which describes the use of
-\&\s-1CFB128\-AES\-128\s0 \f(CW\*(C`AES\*(C'\fR (\s-1NIST\s0 \s-1FIPS\s0 \s-1PUB\s0 197) in the \s-1USM\s0. The \s-1AES\s0
-encryption protocol can be selected by passing \f(CW\*(C`aes\*(C'\fR or \f(CW\*(C`aes128\*(C'\fR to
-the \-\-privprotocol option.
-.Sp
-One of the following arguments are required: des, aes, aes128, 3des,
-3desde
-.IP "\-\-use\-get_table" 4
-.IX Item "--use-get_table"
-This option exists as a workaround when using check_openmanage with
-SNMPv3 on Windows with net-snmp. Using this option will make
-check_openmanage use the Net::SNMP function \fIget_table()\fR instead of
-\&\fIget_entries()\fR while fetching values via \s-1SNMP\s0. The latter is faster and
-is the default.
-.SH "BLACKLISTING"
-.IX Header "BLACKLISTING"
-.IP "\-b, \-\-blacklist \fI\s-1STRING\s0\fR or \fI\s-1FILE\s0\fR" 4
-.IX Item "-b, --blacklist STRING or FILE"
-Blacklist missing and/or failed components, if you do not plan to fix
-them. The parameter is either the blacklist string, or a file (that
-may or may not exist) containing the string. The blacklist string
-contains component names with component IDs separated by slash
-(/). Blacklisted components are left unchecked.
-.Sp
-\&\s-1TIP:\s0 Use the option \f(CW\*(C`\-d\*(C'\fR (or \f(CW\*(C`\-\-debug\*(C'\fR) to get the blacklist \s-1ID\s0 for
-devices. The \s-1ID\s0 is listed in a separate column in the debug output.
-.Sp
-\&\s-1NOTE:\s0 If blacklisting is in effect, the global health of the system is
-not checked.
-.RS 4
-.IP "\fBSyntax:\fR" 9
-.IX Item "Syntax:"
-component1=id1[,id2,...]/component2=id1[,id2,...]/...
-.Sp
-The \s-1ID\s0 part can also be \f(CW\*(C`all\*(C'\fR, in which all components of that type
-is blacklisted.
-.IP "\fBExample:\fR" 9
-.IX Item "Example:"
-check_openmanage \-b ps=0/fan=3,5/pdisk=1:0:0:1/ctrl_driver=all
-.RE
-.RS 4
-.Sp
-In the example we blacklist powersupply 0, fans 3 and 5, physical disk
-1:0:0:1, and warnings about out-of-date drivers for all
-controllers. Legal component names include:
-.IP "\fBctrl\fR" 8
-.IX Item "ctrl"
-Storage controller. Note that if a controller is blacklisted, all
-components on that controller (such as physical and logical drives)
-are blacklisted as well.
-.IP "\fBctrl_fw\fR" 8
-.IX Item "ctrl_fw"
-Suppress the special warning message about old controller
-firmware. Use this if you can not or will not upgrade the firmware.
-.IP "\fBctrl_driver\fR" 8
-.IX Item "ctrl_driver"
-Suppress the special warning message about old controller driver.
-Particularly useful on systems where you can not upgrade the driver.
-.IP "\fBctrl_stdr\fR" 8
-.IX Item "ctrl_stdr"
-Suppress the special warning message about old Storport driver on
-Windows.
-.IP "\fBctrl_pdisk\fR" 8
-.IX Item "ctrl_pdisk"
-This blacklisting keyword exists as a possible workaround for physical
-drives with bad firmware which makes Openmanage choke. It takes the
-controller number as argument. Use this option to blacklist all
-physical drives on a specific controller. This blacklisting keyword is
-only available in local mode, i.e. not with \s-1SNMP\s0.
-.IP "\fBpdisk\fR" 8
-.IX Item "pdisk"
-Physical disk.
-.IP "\fBpdisk_cert\fR" 8
-.IX Item "pdisk_cert"
-Suppress warning message about non-certified physical disk.
-.IP "\fBpdisk_foreign\fR" 8
-.IX Item "pdisk_foreign"
-Suppress warning message about foreign physical disk.
-.IP "\fBvdisk\fR" 8
-.IX Item "vdisk"
-Logical drive (virtual disk)
-.IP "\fBbat\fR" 8
-.IX Item "bat"
-Controller cache battery
-.IP "\fBbat_charge\fR" 8
-.IX Item "bat_charge"
-Ignore warnings related to the controller cache battery charging
-cycle, which happens approximately every 40 days on Dell servers. Note
-that using this blacklist keyword makes check_openmanage ignore
-non-critical cache battery errors.
-.IP "\fBconn\fR" 8
-.IX Item "conn"
-Connector (channel)
-.IP "\fBencl\fR" 8
-.IX Item "encl"
-Enclosure
-.IP "\fBencl_fan\fR" 8
-.IX Item "encl_fan"
-Enclosure fan
-.IP "\fBencl_ps\fR" 8
-.IX Item "encl_ps"
-Enclosure power supply
-.IP "\fBencl_temp\fR" 8
-.IX Item "encl_temp"
-Enclosure temperature probe
-.IP "\fBencl_emm\fR" 8
-.IX Item "encl_emm"
-Enclosure management module (\s-1EMM\s0)
-.IP "\fBdimm\fR" 8
-.IX Item "dimm"
-Memory module
-.IP "\fBfan\fR" 8
-.IX Item "fan"
-Fan
-.IP "\fBps\fR" 8
-.IX Item "ps"
-Powersupply
-.IP "\fBtemp\fR" 8
-.IX Item "temp"
-Temperature sensor
-.IP "\fBcpu\fR" 8
-.IX Item "cpu"
-Processor (\s-1CPU\s0)
-.IP "\fBvolt\fR" 8
-.IX Item "volt"
-Voltage probe
-.IP "\fBbp\fR" 8
-.IX Item "bp"
-System battery
-.IP "\fBamp\fR" 8
-.IX Item "amp"
-Amperage probe (power consumption monitoring)
-.IP "\fBintr\fR" 8
-.IX Item "intr"
-Intrusion sensor
-.IP "\fBsd\fR" 8
-.IX Item "sd"
-\&\s-1SD\s0 card
-.RE
-.RS 4
-.RE
-.SH "CHECK CONTROL"
-.IX Header "CHECK CONTROL"
-.IP "\-\-no\-storage" 4
-.IX Item "--no-storage"
-Turn off storage checking. This is an alias for \f(CW\*(C`\-\-check storage=0\*(C'\fR.
-.IP "\-\-only \fI\s-1KEYWORD\s0\fR" 4
-.IX Item "--only KEYWORD"
-This option can be specifed once and expects a keyword. The different
-keywords and the behaviour of check_openmanage is described below.
-.RS 4
-.IP "\fBcritical\fR" 4
-.IX Item "critical"
-Print only critical alerts. With this option any warning alerts are
-suppressed.
-.IP "\fBwarning\fR" 4
-.IX Item "warning"
-Print only warning alerts. With this option any critical alerts are
-suppressed.
-.IP "\fBchassis\fR" 4
-.IX Item "chassis"
-Check all chassis components and nothing else.
-.IP "\fBstorage\fR" 4
-.IX Item "storage"
-Only check storage
-.IP "\fBmemory\fR" 4
-.IX Item "memory"
-Only check memory modules
-.IP "\fBfans\fR" 4
-.IX Item "fans"
-Only check fans
-.IP "\fBpower\fR" 4
-.IX Item "power"
-Only check power supplies
-.IP "\fBtemp\fR" 4
-.IX Item "temp"
-Only check temperatures
-.IP "\fBcpu\fR" 4
-.IX Item "cpu"
-Only check processors
-.IP "\fBvoltage\fR" 4
-.IX Item "voltage"
-Only check voltage probes
-.IP "\fBbatteries\fR" 4
-.IX Item "batteries"
-Only check batteries
-.IP "\fBamperage\fR" 4
-.IX Item "amperage"
-Only check power usage
-.IP "\fBintrusion\fR" 4
-.IX Item "intrusion"
-Only check chassis intrusion
-.IP "\fBsdcard\fR" 4
-.IX Item "sdcard"
-Only check \s-1SD\s0 cards
-.IP "\fBesmhealth\fR" 4
-.IX Item "esmhealth"
-Only check \s-1ESM\s0 log overall health, i.e. fill grade
-.IP "\fBesmlog\fR" 4
-.IX Item "esmlog"
-Only check the event log (\s-1ESM\s0) content
-.IP "\fBalertlog\fR" 4
-.IX Item "alertlog"
-Only check the alert log content
-.RE
-.RS 4
-.RE
-.IP "\-\-check \fI\s-1STRING\s0\fR or \fI\s-1FILE\s0\fR" 4
-.IX Item "--check STRING or FILE"
-This parameter allows you to adjust which components that should be
-checked at all. This is a rougher approach than blacklisting, which
-require that you specify component id or index. The parameter should
-be either a string containing the adjustments, or a file containing
-the string. No errors are raised if the file does not exist.
-.Sp
-Note: This option is ignored with alternate basenames.
-.RS 4
-.IP "\fBExample:\fR" 9
-.IX Item "Example:"
-check_openmanage \-\-check storage=0,intrusion=1
-.RE
-.RS 4
-.Sp
-Legal values are described below, along with the default value.
-.IP "\fBstorage\fR" 4
-.IX Item "storage"
-Check storage subsystem (controllers, disks etc.). Default: \s-1ON\s0
-.IP "\fBmemory\fR" 4
-.IX Item "memory"
-Check memory (dimms). Default: \s-1ON\s0
-.IP "\fBfans\fR" 4
-.IX Item "fans"
-Check chassis fans. Default: \s-1ON\s0
-.IP "\fBpower\fR" 4
-.IX Item "power"
-Check power supplies. Default: \s-1ON\s0
-.IP "\fBtemp\fR" 4
-.IX Item "temp"
-Check temperature sensors. Default: \s-1ON\s0
-.IP "\fBcpu\fR" 4
-.IX Item "cpu"
-Check CPUs. Default: \s-1ON\s0
-.IP "\fBvoltage\fR" 4
-.IX Item "voltage"
-Check voltage sensors. Default: \s-1ON\s0
-.IP "\fBbatteries\fR" 4
-.IX Item "batteries"
-Check system batteries. Default: \s-1ON\s0
-.IP "\fBamperage\fR" 4
-.IX Item "amperage"
-Check amperage probes. Default: \s-1ON\s0
-.IP "\fBintrusion\fR" 4
-.IX Item "intrusion"
-Check chassis intrusion. Default: \s-1ON\s0
-.IP "\fBsdcard\fR" 4
-.IX Item "sdcard"
-Check \s-1SD\s0 cards. Default: \s-1ON\s0
-.IP "\fBesmhealth\fR" 4
-.IX Item "esmhealth"
-Check the \s-1ESM\s0 log health, i.e. fill grade. Default: \s-1ON\s0
-.IP "\fBesmlog\fR" 4
-.IX Item "esmlog"
-Check the \s-1ESM\s0 log content. Default: \s-1OFF\s0
-.IP "\fBalertlog\fR" 4
-.IX Item "alertlog"
-Check the alert log content. Default: \s-1OFF\s0
-.RE
-.RS 4
-.RE
-.SH "DIAGNOSTICS"
-.IX Header "DIAGNOSTICS"
-The option \f(CW\*(C`\-\-debug\*(C'\fR (or \f(CW\*(C`\-d\*(C'\fR) can be specified to display all
-monitored components.
-.SH "DEPENDENCIES"
-.IX Header "DEPENDENCIES"
-If \s-1SNMP\s0 is requested, the perl module Net::SNMP is
-required. Otherwise, only a regular perl distribution is required to
-run the script. On the target (monitored) system, Dell Openmanage
-Server Administrator (\s-1OMSA\s0) must be installed and running.
-.SH "EXIT STATUS"
-.IX Header "EXIT STATUS"
-If no errors are discovered, a value of 0 (\s-1OK\s0) is returned. An exit
-value of 1 (\s-1WARNING\s0) signifies one or more non-critical errors, while
-2 (\s-1CRITICAL\s0) signifies one or more critical errors.
-.PP
-The exit value 3 (\s-1UNKNOWN\s0) is reserved for errors within the script,
-or errors getting values from Dell \s-1OMSA\s0.
-.SH "AUTHOR"
-.IX Header "AUTHOR"
-Written by Trond H. Amundsen <t.h.amundsen@usit.uio.no>
-.SH "BUGS AND LIMITATIONS"
-.IX Header "BUGS AND LIMITATIONS"
-Storage info is not collected or checked on very old PowerEdge models
-and/or old \s-1OMSA\s0 versions, due to limitations in \s-1OMSA\s0. The overall
-support on those models/versions by this plugin is not well tested.
-.SH "INCOMPATIBILITIES"
-.IX Header "INCOMPATIBILITIES"
-The plugin should work with the Nagios embedded perl interpreter
-(ePN). However, this is not thoroughly tested.
-.SH "REPORTING BUGS"
-.IX Header "REPORTING BUGS"
-Report bugs to <t.h.amundsen@usit.uio.no>
-.SH "LICENSE AND COPYRIGHT"
-.IX Header "LICENSE AND COPYRIGHT"
-This program is free software: you can redistribute it and/or modify
-it under the terms of the \s-1GNU\s0 General Public License as published by
-the Free Software Foundation, either version 3 of the License, or (at
-your option) any later version.
-.PP
-This program is distributed in the hope that it will be useful, but
-\&\s-1WITHOUT\s0 \s-1ANY\s0 \s-1WARRANTY\s0; without even the implied warranty of
-\&\s-1MERCHANTABILITY\s0 or \s-1FITNESS\s0 \s-1FOR\s0 A \s-1PARTICULAR\s0 \s-1PURPOSE\s0. See the \s-1GNU\s0
-General Public License for more details.
-.PP
-You should have received a copy of the \s-1GNU\s0 General Public License
-along with this program. If not, see <http://www.gnu.org/licenses/>.
-.SH "SEE ALSO"
-.IX Header "SEE ALSO"
-\&\fIcheck_openmanage.conf\fR\|(5)
-<http://folk.uio.no/trondham/software/check_openmanage.html>
|
|
[-]
[+]
|
Deleted |
check_openmanage-3.7.5.tar.bz2/check_openmanage.conf.5
^
|
| @@ -1,503 +0,0 @@
-.\" Automatically generated by Pod::Man 2.22 (Pod::Simple 3.13)
-.\"
-.\" Standard preamble:
-.\" ========================================================================
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Vb \" Begin verbatim text
-.ft CW
-.nf
-.ne \\$1
-..
-.de Ve \" End verbatim text
-.ft R
-.fi
-..
-.\" Set up some character translations and predefined strings. \*(-- will
-.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
-.\" double quote, and \*(R" will give a right double quote. \*(C+ will
-.\" give a nicer C++. Capital omega is used to do unbreakable dashes and
-.\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
-.\" nothing in troff, for use with C<>.
-.tr \(*W-
-.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
-.ie n \{\
-. ds -- \(*W-
-. ds PI pi
-. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
-. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
-. ds L" ""
-. ds R" ""
-. ds C` ""
-. ds C' ""
-'br\}
-.el\{\
-. ds -- \|\(em\|
-. ds PI \(*p
-. ds L" ``
-. ds R" ''
-'br\}
-.\"
-.\" Escape single quotes in literal strings from groff's Unicode transform.
-.ie \n(.g .ds Aq \(aq
-.el .ds Aq '
-.\"
-.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
-.\" entries marked with X<> in POD. Of course, you'll have to process the
-.\" output yourself in some meaningful fashion.
-.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
-..
-. nr % 0
-. rr F
-.\}
-.el \{\
-. de IX
-..
-.\}
-.\"
-.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
-.\" Fear. Run. Save yourself. No user-serviceable parts.
-. \" fudge factors for nroff and troff
-.if n \{\
-. ds #H 0
-. ds #V .8m
-. ds #F .3m
-. ds #[ \f1
-. ds #] \fP
-.\}
-.if t \{\
-. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
-. ds #V .6m
-. ds #F 0
-. ds #[ \&
-. ds #] \&
-.\}
-. \" simple accents for nroff and troff
-.if n \{\
-. ds ' \&
-. ds ` \&
-. ds ^ \&
-. ds , \&
-. ds ~ ~
-. ds /
-.\}
-.if t \{\
-. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
-. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
-. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
-. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
-. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
-. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
-.\}
-. \" troff and (daisy-wheel) nroff accents
-.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
-.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
-.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
-.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
-.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
-.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
-.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
-.ds ae a\h'-(\w'a'u*4/10)'e
-.ds Ae A\h'-(\w'A'u*4/10)'E
-. \" corrections for vroff
-.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
-.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
-. \" for low resolution devices (crt and lpr)
-.if \n(.H>23 .if \n(.V>19 \
-\{\
-. ds : e
-. ds 8 ss
-. ds o a
-. ds d- d\h'-1'\(ga
-. ds D- D\h'-1'\(hy
-. ds th \o'bp'
-. ds Th \o'LP'
-. ds ae ae
-. ds Ae AE
-.\}
-.rm #[ #] #H #V #F C
-.\" ========================================================================
-.\"
-.IX Title "CHECK_OPENMANAGE.CONF 5"
-.TH CHECK_OPENMANAGE.CONF 5 "2012-03-09" "check_openmanage 3.7.5" "Nagios plugin"
-.\" For nroff, turn off justification. Always turn off hyphenation; it makes
-.\" way too many mistakes in technical documents.
-.if n .ad l
-.nh
-.SH "NAME"
-\&\fIcheck_openmanage.conf\fR \- Configuration file for check_openmanage
-.SH "FILE FORMAT"
-.IX Header "FILE FORMAT"
-The file has an ini-style syntax and consists of sections and
-parameters. A section begins with the name of the section in square
-brackets and continues until the next section begins. An example of
-section with two keywords and parameters:
-.Sp
-.RS 8
-\&\fI[section]\fR
- \fIkey1\fR = \fIboolean\fR
- \fIkey2\fR = \fIstring\fR
-.RE
-.PP
-The data types used are string (no quotes needed) and bool (with
-values of \f(CW\*(C`TRUE/FALSE\*(C'\fR). For boolean values, \f(CW1\fR, \f(CW\*(C`on\*(C'\fR and \f(CW\*(C`true\*(C'\fR
-are equivalent, likewise for \f(CW0\fR, \f(CW\*(C`off\*(C'\fR and \f(CW\*(C`false\*(C'\fR. They are also
-case insensitive.
-.PP
-The root section or global section has no section name in brackets,
-example:
-.PP
-.Vb 2
-\& key1 = false
-\& key2 = foo
-\&
-\& [section]
-\& key1 = true
-\& key2 = bar
-.Ve
-.PP
-The values set in a bracket section will override those set in the
-root section, in case of conflicts.
-.PP
-Lines starting with \f(CW\*(C`#\*(C'\fR or \f(CW\*(C`;\*(C'\fR are considered comments and ignored, as
-are blank lines.
-.PP
-The configuration file must be a regular file. Owner and group does
-not matter, but the Nagios user must have read access.
-.SH "SECTIONS AND ORDERING"
-.IX Header "SECTIONS AND ORDERING"
-The section name should correspond to the hostname, i.e. the value
-passed to the \f(CW\*(C`\-H\*(C'\fR or \f(CW\*(C`\-\-hostname\*(C'\fR parameter. The section name
-itself can be either an exact match to the hostname, or a glob
-pattern, as this example shows:
-.PP
-.Vb 2
-\& key1 = true
-\& key2 = foo
-\&
-\& [192.168.1.2]
-\& key1 = true
-\&
-\& [192.168.*]
-\& key1 = false
-\& key2 = bar
-.Ve
-.PP
-The sections are read in order of significance. The root section is
-read first. Then any sections with glob patterns that match the
-hostname are read (alphabetically). Any section whose name is an exact
-match to the hostname is read last.
-.PP
-For boolean values, any conflicts are resolved by letting the section
-with the most significance (closest match to the hostname) override
-any previous definitions. For string values, they are simply added
-together.
-.PP
-In the example above, for the host \f(CW192.168.1.2\fR the value of \fIkey1\fR
-will be \fItrue\fR and \fIkey2\fR will be \fIbar\fR. Any other host that
-matches \f(CW\*(C`192.168.*\*(C'\fR will have \fIkey1 = false\fR and \fIkey2 = bar\fR. All
-other hosts will have \fIkey1 = true\fR and \fIkey2 = foo\fR.
-.PP
-Normal shell globbing may be used for the section names. This is
-limited to \f(CW\*(C`*\*(C'\fR, \f(CW\*(C`?\*(C'\fR and \f(CW\*(C`[]\*(C'\fR. Some examples:
-.PP
-.Vb 2
-\& [192.168.*]
-\& # matches e.g. 192.168.10.20
-\&
-\& [192.168.10[34].1]
-\& # matches 192.168.103.1 and 192.168.104.1
-\&
-\& [login?.example.com]
-\& # mathces e.g. login1.example.com
-.Ve
-.PP
-\&\s-1CAUTION\s0! Be careful not to have more than one glob pattern section
-match any single host. This may lead to unpredictable results.
-.SH "COMMAND LINE OPTIONS"
-.IX Header "COMMAND LINE OPTIONS"
-Unless otherwise noted, options given in the configuration file will
-override any corresponding command line options.
-.PP
-In general, avoid using the same options on command line and in the
-configuration file.
-.SH "CONFIGURATION"
-.IX Header "CONFIGURATION"
-.SS "\s-1GENERAL\s0"
-.IX Subsection "GENERAL"
-.IP "Check control" 4
-.IX Item "Check control"
-Any keyword to the \f(CW\*(C`\-\-check\*(C'\fR parameter are accepted in the
-configuration file, as \f(CW\*(C`check_\f(CIKEYWORD\f(CW\*(C'\fR. These options take boolean
-values (\f(CW\*(C`true\*(C'\fR or \f(CW\*(C`false\*(C'\fR). The following keywords are accepted for
-check control, listed here with their default values:
-.Sp
-.Vb 10
-\& check_storage = true
-\& check_memory = true
-\& check_fans = true
-\& check_power = true
-\& check_temp = true
-\& check_cpu = true
-\& check_voltage = true
-\& check_batteries = true
-\& check_amperage = true
-\& check_intrusion = true
-\& check_sdcard = true
-\& check_esmhealth = true
-\& check_esmlog = false
-\& check_alertlog = false
-\& check_everything = false
-.Ve
-.Sp
-If used together with the \f(CW\*(C`\-\-check\*(C'\fR command line option, the command
-line option will override the configuration file, if there is a
-conflict.
-.Sp
-The option \f(CW\*(C`check_everything\*(C'\fR is special and turns on all
-checks. Setting this option to \*(L"true\*(R" will effectively negate any
-other check options. This option corresponds to the \f(CW\*(C`\-a\*(C'\fR or \f(CW\*(C`\-\-all\*(C'\fR
-command line option.
-.Sp
-For more information about check control, see
-\&\*(L"\s-1CHECK\s0 \s-1CONTROL\s0\*(R" in \fIcheck_openmanage\fR\|(8).
-.IP "Blacklisting" 4
-.IX Item "Blacklisting"
-For blacklisting the keyword \f(CW\*(C`blacklist\*(C'\fR is used, and the value is a
-string that uses the same syntax as the \f(CW\*(C`\-b\*(C'\fR or \f(CW\*(C`\-\-blacklist\*(C'\fR
-parameter. Example:
-.Sp
-.Vb 1
-\& blacklist = ctrl_fw=all/pdisk=0:0:1
-.Ve
-.Sp
-If used together with the \f(CW\*(C`\-b\*(C'\fR or \f(CW\*(C`\-\-blacklist\*(C'\fR command line option,
-the two blacklists from the config file and command line are merged
-together.
-.Sp
-For more information about blacklisting, including syntax, see
-\&\*(L"\s-1BLACKLISTING\s0\*(R" in \fIcheck_openmanage\fR\|(8).
-.IP "Timeout" 4
-.IX Item "Timeout"
-The plugin timeout can be configured with the \f(CW\*(C`timeout\*(C'\fR keyword. The
-argument is number of seconds and should be a positive
-integer. Example:
-.Sp
-.Vb 1
-\& timeout = 60
-.Ve
-.Sp
-The corresponding command line option is \f(CW\*(C`\-t\*(C'\fR or \f(CW\*(C`\-\-timeout\*(C'\fR.
-.IP "Performance data" 4
-.IX Item "Performance data"
-Performance data can be turned on in the configuration file with
-\&\f(CW\*(C`performance_data\*(C'\fR. Accepted values are boolean (\s-1TRUE/FALSE\s0) or
-either of the keywords \*(L"minimal\*(R" and \*(L"multiline\*(R". Example:
-.Sp
-.Vb 1
-\& performance_data = true
-.Ve
-.Sp
-The corresponding command line option is \f(CW\*(C`\-p\*(C'\fR or \f(CW\*(C`\-\-perfdata\*(C'\fR.
-.IP "Legacy Performance data" 4
-.IX Item "Legacy Performance data"
-With version 3.7.0, performance data output changed. The new format is
-not compatible with the old format. Users who wish to postpone
-switching to the new performance data \s-1API\s0 may use this option. This
-option takes a boolean value. Example:
-.Sp
-.Vb 1
-\& legacy_performance_data = true
-.Ve
-.Sp
-The corresponding command line option is \f(CW\*(C`\-\-legacy\-perfdata\*(C'\fR.
-.IP "Temperature unit" 4
-.IX Item "Temperature unit"
-The temperature unit used for reporting, performance data etc. can be
-set with the \f(CW\*(C`temperature_unit\*(C'\fR option. Allowed values are \f(CW\*(C`F\*(C'\fR for
-Fahrenheit, \f(CW\*(C`C\*(C'\fR for Celsius, \f(CW\*(C`K\*(C'\fR for Kelvin and \f(CW\*(C`R\*(C'\fR for
-Rankine. Example:
-.Sp
-.Vb 1
-\& temperature_unit = F
-.Ve
-.Sp
-The corresponding command line option is \f(CW\*(C`\-\-tempunit\*(C'\fR. Note that the
-command line option \f(CW\*(C`\-F\*(C'\fR or \f(CW\*(C`\-\-fahrenheit\*(C'\fR will override both the
-command line option and the configuration file option.
-.IP "Temperature limits" 4
-.IX Item "Temperature limits"
-Custom temperature limits may be configured with the options
-\&\f(CW\*(C`temp_threshold_warning\*(C'\fR and \f(CW\*(C`temp_threshold_critical\*(C'\fR. These
-options corresponds to the command line options \f(CW\*(C`\-w\*(C'\fR or \f(CW\*(C`\-\-warning\*(C'\fR
-and \f(CW\*(C`\-c\*(C'\fR or \f(CW\*(C`\-\-critical\*(C'\fR, respectively. They take the same arguments
-as the command line options. Examples:
-.Sp
-.Vb 2
-\& temp_threshold_warning = 0=30/10
-\& temp_threshold_critical = 0=35/8
-.Ve
-.SS "\s-1SNMP\s0 \s-1OPTIONS\s0"
-.IX Subsection "SNMP OPTIONS"
-Several \s-1SNMP\s0 related options may be set in the configuration file. The
-configuration file may contain the following \s-1SNMP\s0 options:
-.IP "\s-1SNMP\s0 community string" 4
-.IX Item "SNMP community string"
-The \s-1SNMP\s0 community string can be set with \f(CW\*(C`snmp_community\*(C'\fR. Example:
-.Sp
-.Vb 1
-\& snmp_community = mycommunity
-.Ve
-.Sp
-Corresponding command line option: \f(CW\*(C`\-C\*(C'\fR or \f(CW\*(C`\-\-community\*(C'\fR
-.IP "\s-1SNMP\s0 protocol version" 4
-.IX Item "SNMP protocol version"
-The \s-1SNMP\s0 protocol version can be set with \f(CW\*(C`snmp_version\*(C'\fR. Example:
-.Sp
-.Vb 1
-\& snmp_version = 2c
-.Ve
-.Sp
-Corresponding command line option: \f(CW\*(C`\-P\*(C'\fR or \f(CW\*(C`\-\-protocol\*(C'\fR
-.IP "\s-1SNMP\s0 port number" 4
-.IX Item "SNMP port number"
-The remote port number used with \s-1SNMP\s0 can be set with
-\&\f(CW\*(C`snmp_port\*(C'\fR. Example:
-.Sp
-.Vb 1
-\& snmp_port = 161
-.Ve
-.Sp
-Corresponding command line option: \f(CW\*(C`\-\-port\*(C'\fR
-.IP "Use IPv6 instead of IPv4" 4
-.IX Item "Use IPv6 instead of IPv4"
-The option \f(CW\*(C`snmp_use_ipv6\*(C'\fR instructs the plugin to use IPv6 instead
-of IPv4. This option takes a boolean value. Example:
-.Sp
-.Vb 1
-\& snmp_use_ipv6 = true
-.Ve
-.Sp
-Corresponding command line option: \f(CW\*(C`\-6\*(C'\fR or \f(CW\*(C`\-\-ipv6\*(C'\fR
-.IP "Use \s-1TCP\s0 instead of \s-1UDP\s0" 4
-.IX Item "Use TCP instead of UDP"
-The option \f(CW\*(C`snmp_use_ipv6\*(C'\fR instructs the plugin to use IPv6 instead
-of IPv4. This option takes a boolean value. Example:
-.Sp
-.Vb 1
-\& snmp_use_tcp = true
-.Ve
-.Sp
-Corresponding command line option: \f(CW\*(C`\-\-tcp\*(C'\fR
-.SS "\s-1OUTPUT\s0 \s-1CONTROL\s0"
-.IX Subsection "OUTPUT CONTROL"
-These options gives some control over the output given by the plugin.
-.IP "Include servicetag in alerts" 4
-.IX Item "Include servicetag in alerts"
-The option \f(CW\*(C`output_servicetag\*(C'\fR will make the plugin include the
-servers servicetag (serial number) in every alert. This option takes a
-boolean value. Example:
-.Sp
-.Vb 1
-\& output_servicetag = true
-.Ve
-.Sp
-Corresponding command line option: \f(CW\*(C`\-i\*(C'\fR or \f(CW\*(C`\-\-info\*(C'\fR
-.IP "Include service state in alerts" 4
-.IX Item "Include service state in alerts"
-The option \f(CW\*(C`output_servicestate\*(C'\fR will make the plugin include the
-service state in any alerts. This option takes a boolean
-value. Example:
-.Sp
-.Vb 1
-\& output_servicestate = true
-.Ve
-.Sp
-Corresponding command line option: \f(CW\*(C`\-s\*(C'\fR or \f(CW\*(C`\-\-state\*(C'\fR
-.IP "Include abbreviated service state in alerts" 4
-.IX Item "Include abbreviated service state in alerts"
-The option \f(CW\*(C`output_servicestate_abbr\*(C'\fR will make the plugin include
-the abbreviated service state in any alerts. This option takes a
-boolean value. Example:
-.Sp
-.Vb 1
-\& output_servicestate_abbr = true
-.Ve
-.Sp
-Corresponding command line option: \f(CW\*(C`\-S\*(C'\fR or \f(CW\*(C`\-\-short\-state\*(C'\fR
-.IP "Show system info with alerts" 4
-.IX Item "Show system info with alerts"
-The option \f(CW\*(C`output_sysinfo\*(C'\fR will make the plugin output some system
-information with alerts. This option takes a boolean value. Example:
-.Sp
-.Vb 1
-\& output_sysinfo = true
-.Ve
-.Sp
-Corresponding command line option: \f(CW\*(C`\-e\*(C'\fR or \f(CW\*(C`\-\-extinfo\*(C'\fR
-.IP "Show blacklistings in \s-1OK\s0 output" 4
-.IX Item "Show blacklistings in OK output"
-The option \f(CW\*(C`output_blacklist\*(C'\fR will make the plugin show any
-blacklistings in the \s-1OK\s0 output. This option takes a boolean
-value. Example:
-.Sp
-.Vb 1
-\& output_blacklist = true
-.Ve
-.Sp
-Corresponding command line option: \f(CW\*(C`\-B\*(C'\fR or \f(CW\*(C`\-\-show\-blacklist\*(C'\fR
-.IP "Verbosity of \s-1OK\s0 output" 4
-.IX Item "Verbosity of OK output"
-The option \f(CW\*(C`output_ok_verbosity\*(C'\fR lets you adjust how much information
-is shown in the \s-1OK\s0 output. This option takes a positive integer as
-parameter. Example:
-.Sp
-.Vb 1
-\& output_ok_verbosity = 3
-.Ve
-.Sp
-Corresponding command line option: \f(CW\*(C`\-o\*(C'\fR or \f(CW\*(C`\-\-ok\-info\*(C'\fR
-.IP "\s-1HTML\s0 output" 4
-.IX Item "HTML output"
-The output \f(CW\*(C`output_html\*(C'\fR makes the plugin produce \s-1HTML\s0 output. This
-option takes either a boolean value, or a country or area
-code. Example:
-.Sp
-.Vb 1
-\& output_html = de
-.Ve
-.Sp
-Corresponding command line option: \f(CW\*(C`\-I\*(C'\fR or \f(CW\*(C`\-\-htmlinfo\*(C'\fR
-.IP "Custom line after alerts" 4
-.IX Item "Custom line after alerts"
-The option \f(CW\*(C`output_post_message\*(C'\fR lets you specify one line of
-information to be shown after any alerts. This option takes a string
-as parameter. Examples:
-.Sp
-.Vb 2
-\& output_post_message = OS: %o %r
-\& output_post_message = NOTE: Handled in ticket 123456
-.Ve
-.Sp
-For more information about codes and formatting, see the corresponding
-command line option \f(CW\*(C`\-\-postmsg\*(C'\fR in \fIcheck_openmanage\fR\|(8).
-.IP "Suppress or censor the servicetag" 4
-.IX Item "Suppress or censor the servicetag"
-The option \f(CW\*(C`output_hide_servicetag\*(C'\fR will censor the servicetag
-(serial number) in any output from the plugin. This option takes a
-boolean value. Example:
-.Sp
-.Vb 1
-\& output_hide_servicetag = true
-.Ve
-.Sp
-Corresponding command line option: \f(CW\*(C`\-\-hide\-servicetag\*(C'\fR
-.SH "SEE ALSO"
-.IX Header "SEE ALSO"
-\&\fIcheck_openmanage\fR\|(8)
-<http://folk.uio.no/trondham/software/check_openmanage.html>
|
|
[-]
[+]
|
Deleted |
check_openmanage-3.7.5.tar.bz2/check_openmanage.conf.pod
^
|
| @@ -1,374 +0,0 @@
-# Man page created with:
-#
-# pod2man -s 5 -r "`./check_openmanage -V | head -n 1`" -c 'Nagios plugin' check_openmanage.conf.pod check_openmanage.conf.5
-#
-# $Id: check_openmanage.pod 20039 2011-04-26 09:56:56Z trondham $
-
-=head1 NAME
-
-F<check_openmanage.conf> - Configuration file for check_openmanage
-
-=head1 FILE FORMAT
-
-The file has an ini-style syntax and consists of sections and
-parameters. A section begins with the name of the section in square
-brackets and continues until the next section begins. An example of
-section with two keywords and parameters:
-
-=over 8
-
-I<[section]>
- I<key1> = I<boolean>
- I<key2> = I<string>
-
-=back
-
-The data types used are string (no quotes needed) and bool (with
-values of C<TRUE/FALSE>). For boolean values, C<1>, C<on> and C<true>
-are equivalent, likewise for C<0>, C<off> and C<false>. They are also
-case insensitive.
-
-The root section or global section has no section name in brackets,
-example:
-
- key1 = false
- key2 = foo
-
- [section]
- key1 = true
- key2 = bar
-
-The values set in a bracket section will override those set in the
-root section, in case of conflicts.
-
-Lines starting with C<#> or C<;> are considered comments and ignored, as
-are blank lines.
-
-The configuration file must be a regular file. Owner and group does
-not matter, but the Nagios user must have read access.
-
-=head1 SECTIONS AND ORDERING
-
-The section name should correspond to the hostname, i.e. the value
-passed to the C<-H> or C<--hostname> parameter. The section name
-itself can be either an exact match to the hostname, or a glob
-pattern, as this example shows:
-
- key1 = true
- key2 = foo
-
- [192.168.1.2]
- key1 = true
-
- [192.168.*]
- key1 = false
- key2 = bar
-
-The sections are read in order of significance. The root section is
-read first. Then any sections with glob patterns that match the
-hostname are read (alphabetically). Any section whose name is an exact
-match to the hostname is read last.
-
-For boolean values, any conflicts are resolved by letting the section
-with the most significance (closest match to the hostname) override
-any previous definitions. For string values, they are simply added
-together.
-
-In the example above, for the host C<192.168.1.2> the value of I<key1>
-will be I<true> and I<key2> will be I<bar>. Any other host that
-matches C<192.168.*> will have I<key1 = false> and I<key2 = bar>. All
-other hosts will have I<key1 = true> and I<key2 = foo>.
-
-Normal shell globbing may be used for the section names. This is
-limited to C<*>, C<?> and C<[]>. Some examples:
-
- [192.168.*]
- # matches e.g. 192.168.10.20
-
- [192.168.10[34].1]
- # matches 192.168.103.1 and 192.168.104.1
-
- [login?.example.com]
- # mathces e.g. login1.example.com
-
-CAUTION! Be careful not to have more than one glob pattern section
-match any single host. This may lead to unpredictable results.
-
-=head1 COMMAND LINE OPTIONS
-
-Unless otherwise noted, options given in the configuration file will
-override any corresponding command line options.
-
-In general, avoid using the same options on command line and in the
-configuration file.
-
-=head1 CONFIGURATION
-
-=head2 GENERAL
-
-=over 4
-
-=item Check control
-
-Any keyword to the C<--check> parameter are accepted in the
-configuration file, as C<check_I<KEYWORD>>. These options take boolean
-values (C<true> or C<false>). The following keywords are accepted for
-check control, listed here with their default values:
-
- check_storage = true
- check_memory = true
- check_fans = true
- check_power = true
- check_temp = true
- check_cpu = true
- check_voltage = true
- check_batteries = true
- check_amperage = true
- check_intrusion = true
- check_sdcard = true
- check_esmhealth = true
- check_esmlog = false
- check_alertlog = false
- check_everything = false
-
-If used together with the C<--check> command line option, the command
-line option will override the configuration file, if there is a
-conflict.
-
-The option C<check_everything> is special and turns on all
-checks. Setting this option to "true" will effectively negate any
-other check options. This option corresponds to the C<-a> or C<--all>
-command line option.
-
-For more information about check control, see
-L<check_openmanage(8)/CHECK CONTROL>.
-
-=item Blacklisting
-
-For blacklisting the keyword C<blacklist> is used, and the value is a
-string that uses the same syntax as the C<-b> or C<--blacklist>
-parameter. Example:
-
- blacklist = ctrl_fw=all/pdisk=0:0:1
-
-If used together with the C<-b> or C<--blacklist> command line option,
-the two blacklists from the config file and command line are merged
-together.
-
-For more information about blacklisting, including syntax, see
-L<check_openmanage(8)/BLACKLISTING>.
-
-=item Timeout
-
-The plugin timeout can be configured with the C<timeout> keyword. The
-argument is number of seconds and should be a positive
-integer. Example:
-
- timeout = 60
-
-The corresponding command line option is C<-t> or C<--timeout>.
-
-=item Performance data
-
-Performance data can be turned on in the configuration file with
-C<performance_data>. Accepted values are boolean (TRUE/FALSE) or
-either of the keywords "minimal" and "multiline". Example:
-
- performance_data = true
-
-The corresponding command line option is C<-p> or C<--perfdata>.
-
-=item Legacy Performance data
-
-With version 3.7.0, performance data output changed. The new format is
-not compatible with the old format. Users who wish to postpone
-switching to the new performance data API may use this option. This
-option takes a boolean value. Example:
-
- legacy_performance_data = true
-
-The corresponding command line option is C<--legacy-perfdata>.
-
-=item Temperature unit
-
-The temperature unit used for reporting, performance data etc. can be
-set with the C<temperature_unit> option. Allowed values are C<F> for
-Fahrenheit, C<C> for Celsius, C<K> for Kelvin and C<R> for
-Rankine. Example:
-
- temperature_unit = F
-
-The corresponding command line option is C<--tempunit>. Note that the
-command line option C<-F> or C<--fahrenheit> will override both the
-command line option and the configuration file option.
-
-=item Temperature limits
-
-Custom temperature limits may be configured with the options
-C<temp_threshold_warning> and C<temp_threshold_critical>. These
-options corresponds to the command line options C<-w> or C<--warning>
-and C<-c> or C<--critical>, respectively. They take the same arguments
-as the command line options. Examples:
-
- temp_threshold_warning = 0=30/10
- temp_threshold_critical = 0=35/8
-
-=back
-
-=head2 SNMP OPTIONS
-
-Several SNMP related options may be set in the configuration file. The
-configuration file may contain the following SNMP options:
-
-=over 4
-
-=item SNMP community string
-
-The SNMP community string can be set with C<snmp_community>. Example:
-
- snmp_community = mycommunity
-
-Corresponding command line option: C<-C> or C<--community>
-
-=item SNMP protocol version
-
-The SNMP protocol version can be set with C<snmp_version>. Example:
-
- snmp_version = 2c
-
-Corresponding command line option: C<-P> or C<--protocol>
-
-=item SNMP port number
-
-The remote port number used with SNMP can be set with
-C<snmp_port>. Example:
-
- snmp_port = 161
-
-Corresponding command line option: C<--port>
-
-=item Use IPv6 instead of IPv4
-
-The option C<snmp_use_ipv6> instructs the plugin to use IPv6 instead
-of IPv4. This option takes a boolean value. Example:
-
- snmp_use_ipv6 = true
-
-Corresponding command line option: C<-6> or C<--ipv6>
-
-=item Use TCP instead of UDP
-
-The option C<snmp_use_ipv6> instructs the plugin to use IPv6 instead
-of IPv4. This option takes a boolean value. Example:
-
- snmp_use_tcp = true
-
-Corresponding command line option: C<--tcp>
-
-=back
-
-=head2 OUTPUT CONTROL
-
-These options gives some control over the output given by the plugin.
-
-=over 4
-
-=item Include servicetag in alerts
-
-The option C<output_servicetag> will make the plugin include the
-servers servicetag (serial number) in every alert. This option takes a
-boolean value. Example:
-
- output_servicetag = true
-
-Corresponding command line option: C<-i> or C<--info>
-
-=item Include service state in alerts
-
-The option C<output_servicestate> will make the plugin include the
-service state in any alerts. This option takes a boolean
-value. Example:
-
- output_servicestate = true
-
-Corresponding command line option: C<-s> or C<--state>
-
-=item Include abbreviated service state in alerts
-
-The option C<output_servicestate_abbr> will make the plugin include
-the abbreviated service state in any alerts. This option takes a
-boolean value. Example:
-
- output_servicestate_abbr = true
-
-Corresponding command line option: C<-S> or C<--short-state>
-
-=item Show system info with alerts
-
-The option C<output_sysinfo> will make the plugin output some system
-information with alerts. This option takes a boolean value. Example:
-
- output_sysinfo = true
-
-Corresponding command line option: C<-e> or C<--extinfo>
-
-=item Show blacklistings in OK output
-
-The option C<output_blacklist> will make the plugin show any
-blacklistings in the OK output. This option takes a boolean
-value. Example:
-
- output_blacklist = true
-
-Corresponding command line option: C<-B> or C<--show-blacklist>
-
-=item Verbosity of OK output
-
-The option C<output_ok_verbosity> lets you adjust how much information
-is shown in the OK output. This option takes a positive integer as
-parameter. Example:
-
- output_ok_verbosity = 3
-
-Corresponding command line option: C<-o> or C<--ok-info>
-
-=item HTML output
-
-The output C<output_html> makes the plugin produce HTML output. This
-option takes either a boolean value, or a country or area
-code. Example:
-
- output_html = de
-
-Corresponding command line option: C<-I> or C<--htmlinfo>
-
-=item Custom line after alerts
-
-The option C<output_post_message> lets you specify one line of
-information to be shown after any alerts. This option takes a string
-as parameter. Examples:
-
- output_post_message = OS: %o %r
- output_post_message = NOTE: Handled in ticket 123456
-
-For more information about codes and formatting, see the corresponding
-command line option C<--postmsg> in L<check_openmanage(8)>.
-
-=item Suppress or censor the servicetag
-
-The option C<output_hide_servicetag> will censor the servicetag
-(serial number) in any output from the plugin. This option takes a
-boolean value. Example:
-
- output_hide_servicetag = true
-
-Corresponding command line option: C<--hide-servicetag>
-
-=back
-
-=head1 SEE ALSO
-
-L<check_openmanage(8)>
-L<http://folk.uio.no/trondham/software/check_openmanage.html>
-
-=cut
|
|
[-]
[+]
|
Deleted |
check_openmanage-3.7.5.tar.bz2/check_openmanage.pod
^
|
| @@ -1,792 +0,0 @@
-# Man page created with:
-#
-# pod2man -s 8 -r "`./check_openmanage -V | head -n 1`" -c 'Nagios plugin' check_openmanage.pod check_openmanage.8
-#
-# $Id$
-
-=head1 NAME
-
-check_openmanage - Nagios plugin for checking the hardware status on
- Dell servers running OpenManage
-
-=head1 SYNOPSIS
-
-check_openmanage [I<OPTION>]...
-
-check_openmanage -H I<hostname> [I<OPTION>]...
-
-=head1 DESCRIPTION
-
-check_openmanage is a plugin for Nagios which checks the hardware
-health of Dell servers running OpenManage Server Administrator
-(OMSA). The plugin checks the health of the storage subsystem, power
-supplies, memory modules, temperature probes etc., and gives an alert
-if any of the components are faulty or operate outside normal
-parameters.
-
-check_openmanage is designed to be used by either locally (using NRPE
-or similar) or remotely (using SNMP). In either mode, the output is
-(nearly) the same. Note that checking the alert log is not supported
-in SNMP mode.
-
-=head1 GENERAL OPTIONS
-
-=over 4
-
-=item -f, --config I<FILE>
-
-Specify a configuration file. For reference on the config file syntax
-and options, consult the L<check_openmanage.conf(5)> manual page.
-
-=item -t, --timeout I<SECONDS>
-
-The number of seconds after which the plugin will abort. Default
-timeout is 30 seconds if the option is not present.
-
-=item -p, --perfdata [I<multline> or I<minimal>]
-
-Collect performance data. Performance data collected include
-temperatures (in Celsius) and fan speeds (in rpm). On systems that
-support it, power consumption is also collected (in Watts). This
-option takes one of two arguments, both of which are optional.
-
-If the argument C<minimal> is specified, the plugin will use shorter
-names for the performance data labels, e.g. C<t0> instead of
-C<temp_0_system_board_ambient>. This can be used as a workaround in
-cases where the plugin output needs shortening, for example if the
-1024 character limit of NRPE is reached.
-
-If given the argument C<multiline>, the plugin will output the
-performance data on multiple lines, for Nagios 3.x and above.
-
-=item --legacy-perfdata
-
-With version 3.7.0, performance data output changed. The new format is
-not compatible with the old format. Users who wish to postpone
-switching to the new performance data API may set this option.
-
-=item -w, --warning I<STRING> or I<FILE>
-
-Override the machine-default temperature warning thresholds. Syntax is
-C<id1=max[/min],id2=max[/min],...>. The following example sets warning
-limits to max 50C for probe 0, and max 45C and min 10C for probe 1:
-
-check_openmanage -w 0=50,1=45/10
-
-The minimum limit can be omitted, if desired. Most often, you are only
-interested in setting the maximum thresholds.
-
-This parameter can be either a string with the limits, or a file
-containing the limits string. The option can be specified multiple
-times.
-
-NOTE: This option should only be used to narrow the field of OK
-temperatures wrt. the OMSA defaults. To expand the field of OK
-temperatures, increase the OMSA thresholds. See the plugin web page
-for more information.
-
-=item -c, --critical I<STRING> or I<FILE>
-
-Override the machine-default temperature critical thresholds. Syntax
-and behaviour is the same as for warning thresholds described above.
-
-=item -F, --fahrenheit
-
-Set Fahrenheit as unit for all temperatures. This option will override
-the C<--tempunit> option, if used simultaneously.
-
-=item --tempunit I<CHAR>
-
-Set temperature unit. Legal values are C<F> for Fahrenheit, C<C> for
-Celsius, C<K> for Kelvin and C<R> for Rankine.
-
-=item -o, --ok-info I<NUMBER>
-
-This option lets you define how much output you want the plugin to
-give when everything is OK, i.e. the verbosity level. The default
-value is 0 (one line of output). The output levels are cumulative.
-
-=over 4
-
-=item B<0>
-
-- Only one line (default)
-
-=item B<1>
-
-- BIOS and firmware info on a separate line
-
-=item B<2>
-
-- Storage controller and enclosure info on separate lines
-
-=item B<3>
-
-- OMSA version on separate line
-
-=back
-
-The reason that OMSA version is separated from the rest is that
-finding it requires running a really slow omreport command, when the
-plugin is run locally via NRPE.
-
-=item -B, --show-blacklist
-
-If used together with blacklisting, this option will make the plugin
-output all blacklistings that are being used. The output will have the
-correct blacklisting syntax, and will make it easy to maintain control
-over which blacklistings that are used for each server, as any
-blacklistings can be viewed from Nagios.
-
-When blacklisting is not used, this option has no effect.
-
-=item --omreport I<OMREPORT PATH>
-
-Specify full path to omreport, if it is not installed in any of the
-regular places. Usually this option is only needed on Windows, if
-omreport is not installed on the C: drive.
-
-=item -i, --info
-
-Prefix any alerts with the service tag.
-
-=item -e, --extinfo
-
-Display a short summary of system information (model and service tag)
-in case of an alert.
-
-=item -I, --htmlinfo [I<CODE>]
-
-Using this option will make the servicetag and model name into
-clickable HTML links in the output. The model name link will point to
-the official Dell documentation for that model, while the servicetag
-link will point to a website containing support info for that
-particular server.
-
-This option takes an optional argument, which should be your country
-code or C<me> for the middle east. If the country code is omitted the
-servicetag link will still work, but it will not be speficic for your
-country or area. Example for Germany:
-
- check_openmanage --htmlinfo de
-
-If this option is used together with either the I<--extinfo> or
-I<--info> options, it is particularly useful. Only the most common
-country codes is supported at this time.
-
-=item --postmsg I<STRING> or I<FILE>
-
-User specified post message. Useful for displaying arbitrary or
-various system information at the end of alerts. The argument is
-either a string with the message, or a file containing that
-string. You can control the format with the following interpreted
-sequences:
-
-=over 4
-
-=item B<%m>
-
-System model
-
-=item B<%s>
-
-Service tag
-
-=item B<%b>
-
-BIOS version
-
-=item B<%d>
-
-BIOS release date
-
-=item B<%o>
-
-Operating system name
-
-=item B<%r>
-
-Operating system release
-
-=item B<%p>
-
-Number of physical drives
-
-=item B<%l>
-
-Number of logical drives
-
-=item B<%n>
-
-Line break. Will be a regular line break if run from a TTY, else an
-HTML line break.
-
-=item B<%%>
-
-A literal C<%>
-
-=back
-
-=item -s, --state
-
-Prefix each alert with its corresponding service state (i.e. warning,
-critical etc.). This is useful in case of several alerts from the same
-monitored system.
-
-=item -S, --short-state
-
-Same as the B<--state> option above, except that the state is
-abbreviated to a single letter (W=warning, C=critical etc.).
-
-=item --hide-servicetag
-
-This option will replace the servicetag (serial number) in the output
-with C<XXXXXXX>. Use this option to suppress or censor the servicetag
-in the plugin output.
-
-=item --linebreak I<STRING>
-
-check_openmanage will sometimes report more than one line, e.g. if
-there are several alerts. If the script has a TTY, it will use regular
-linebreaks. If not (which is the case with NRPE) it will use HTML
-linebreaks. Sometimes it can be useful to control what the plugin uses
-as a line separator, and this option provides that control.
-
-The argument is the exact string to be used as the line
-separator. There are two exceptions, i.e. two keywords that translates
-to the following:
-
-=over 4
-
-=item B<REG>
-
-Regular linebreaks, i.e. "\n".
-
-=item B<HTML>
-
-HTML linebreaks, i.e. "<br/>".
-
-=back
-
-This is a rather special option that is normally not needed. The
-default behaviour should be sufficient for most users.
-
-=item -d, --debug
-
-Debug output. Will report status on everything, even if status is
-ok. Blacklisted or unchecked components are ignored (i.e. no output).
-
-NOTE: This option is intended for diagnostics and debugging purposes
-only. Do not use this option from within Nagios, i.e. in the Nagios
-config.
-
-=item -h, --help
-
-Display help text.
-
-=item -V, --version
-
-Display version info.
-
-=back
-
-=head1 SNMP OPTIONS
-
-=over 4
-
-=item -H, --hostname I<HOSTNAME>
-
-The transport address of the destination SNMP device. Using this
-option triggers SNMP mode.
-
-=item -P, --protocol I<PROTOCOL>
-
-SNMP protocol version. This option is optional and expects either of
-the following:
-
- "1" : SNMP version 1
- "2c" or "2" : SNMP version 2c
- "3" : SNMP version 3
-
-The default is C<2c>.
-
-=item -C, --community I<COMMUNITY>
-
-This option expects a string that is to be used as the SNMP community
-name when using SNMP version 1 or 2c. By default the community name
-is set to C<public> if the option is not present.
-
-=item --port I<PORT>
-
-SNMP port of the remote (monitored) system. Defaults to the well-known
-SNMP port 161.
-
-=item -6, --ipv6
-
-This option will cause the plugin to use IPv6. The default is IPv4 if
-the option is not present.
-
-=item --tcp
-
-This option will cause the plugin to use TCP as transport
-protocol. The default is UDP if the option is not present.
-
-=item -U, --username I<SECURITYNAME>
-
-[SNMPv3] The User-based Security Model (USM) used by SNMPv3 requires
-that a securityName be specified. This option is required when using
-SNMP version 3, and expects a string 1 to 32 octets in lenght.
-
-=item --authpassword I<PASSWORD>, --authkey I<KEY>
-
-[SNMPv3] By default a securityLevel of C<noAuthNoPriv> is assumed. If
-the --authpassword option is specified, the securityLevel becomes
-C<authNoPriv>. The --authpassword option expects a string which is at
-least 1 octet in length as argument.
-
-Optionally, instead of the --authpassword option, the --authkey option
-can be used so that a plain text password does not have to be
-specified in a script. The --authkey option expects a hexadecimal
-string produced by localizing the password with the
-authoritativeEngineID for the specific destination device. The
-C<snmpkey> utility included with the Net::SNMP distribution can be
-used to create the hexadecimal string (see L<snmpkey>).
-
-=item --authprotocol I<ALGORITHM>
-
-[SNMPv3] Two different hash algorithms are defined by SNMPv3 which can
-be used by the Security Model for authentication. These algorithms are
-HMAC-MD5-96 C<MD5> (RFC 1321) and HMAC-SHA-96 C<SHA-1> (NIST FIPS PUB
-180-1). The default algorithm used by the plugin is HMAC-MD5-96. This
-behavior can be changed by using this option. The option expects
-either the string C<md5> or C<sha> to be passed as argument to modify
-the hash algorithm.
-
-=item --privpassword I<PASSWORD>, --privkey I<KEY>
-
-[SNMPv3] By specifying the options --privkey or --privpassword, the
-securityLevel associated with the object becomes
-C<authPriv>. According to SNMPv3, privacy requires the use of
-authentication. Therefore, if either of these two options are present
-and the --authkey or --authpassword arguments are missing, the
-creation of the object fails. The --privkey and --privpassword
-options expect the same input as the --authkey and --authpassword
-options respectively.
-
-=item --privprotocol I<ALGORITHM>
-
-[SNMPv3] The User-based Security Model described in RFC 3414 defines a
-single encryption protocol to be used for privacy. This protocol,
-CBC-DES C<DES> (NIST FIPS PUB 46-1), is used by default or if the
-string C<des> is passed to the --privprotocol option. The Net::SNMP
-module also supports RFC 3826 which describes the use of
-CFB128-AES-128 C<AES> (NIST FIPS PUB 197) in the USM. The AES
-encryption protocol can be selected by passing C<aes> or C<aes128> to
-the --privprotocol option.
-
-One of the following arguments are required: des, aes, aes128, 3des,
-3desde
-
-=item --use-get_table
-
-This option exists as a workaround when using check_openmanage with
-SNMPv3 on Windows with net-snmp. Using this option will make
-check_openmanage use the Net::SNMP function get_table() instead of
-get_entries() while fetching values via SNMP. The latter is faster and
-is the default.
-
-=back
-
-=head1 BLACKLISTING
-
-=over 4
-
-=item -b, --blacklist I<STRING> or I<FILE>
-
-Blacklist missing and/or failed components, if you do not plan to fix
-them. The parameter is either the blacklist string, or a file (that
-may or may not exist) containing the string. The blacklist string
-contains component names with component IDs separated by slash
-(/). Blacklisted components are left unchecked.
-
-TIP: Use the option C<-d> (or C<--debug>) to get the blacklist ID for
-devices. The ID is listed in a separate column in the debug output.
-
-NOTE: If blacklisting is in effect, the global health of the system is
-not checked.
-
-=over 9
-
-=item B<Syntax:>
-
-component1=id1[,id2,...]/component2=id1[,id2,...]/...
-
-The ID part can also be C<all>, in which all components of that type
-is blacklisted.
-
-=item B<Example:>
-
-check_openmanage -b ps=0/fan=3,5/pdisk=1:0:0:1/ctrl_driver=all
-
-=back
-
-In the example we blacklist powersupply 0, fans 3 and 5, physical disk
-1:0:0:1, and warnings about out-of-date drivers for all
-controllers. Legal component names include:
-
-=over 8
-
-=item B<ctrl>
-
-Storage controller. Note that if a controller is blacklisted, all
-components on that controller (such as physical and logical drives)
-are blacklisted as well.
-
-=item B<ctrl_fw>
-
-Suppress the special warning message about old controller
-firmware. Use this if you can not or will not upgrade the firmware.
-
-=item B<ctrl_driver>
-
-Suppress the special warning message about old controller driver.
-Particularly useful on systems where you can not upgrade the driver.
-
-=item B<ctrl_stdr>
-
-Suppress the special warning message about old Storport driver on
-Windows.
-
-=item B<ctrl_pdisk>
-
-This blacklisting keyword exists as a possible workaround for physical
-drives with bad firmware which makes Openmanage choke. It takes the
-controller number as argument. Use this option to blacklist all
-physical drives on a specific controller. This blacklisting keyword is
-only available in local mode, i.e. not with SNMP.
-
-=item B<pdisk>
-
-Physical disk.
-
-=item B<pdisk_cert>
-
-Suppress warning message about non-certified physical disk.
-
-=item B<pdisk_foreign>
-
-Suppress warning message about foreign physical disk.
-
-=item B<vdisk>
-
-Logical drive (virtual disk)
-
-=item B<bat>
-
-Controller cache battery
-
-=item B<bat_charge>
-
-Ignore warnings related to the controller cache battery charging
-cycle, which happens approximately every 40 days on Dell servers. Note
-that using this blacklist keyword makes check_openmanage ignore
-non-critical cache battery errors.
-
-=item B<conn>
-
-Connector (channel)
-
-=item B<encl>
-
-Enclosure
-
-=item B<encl_fan>
-
-Enclosure fan
-
-=item B<encl_ps>
-
-Enclosure power supply
-
-=item B<encl_temp>
-
-Enclosure temperature probe
-
-=item B<encl_emm>
-
-Enclosure management module (EMM)
-
-=item B<dimm>
-
-Memory module
-
-=item B<fan>
-
-Fan
-
-=item B<ps>
-
-Powersupply
-
-=item B<temp>
-
-Temperature sensor
-
-=item B<cpu>
-
-Processor (CPU)
-
-=item B<volt>
-
-Voltage probe
-
-=item B<bp>
-
-System battery
-
-=item B<amp>
-
-Amperage probe (power consumption monitoring)
-
-=item B<intr>
-
-Intrusion sensor
-
-=item B<sd>
-
-SD card
-
-=back
-
-=back
-
-=head1 CHECK CONTROL
-
-=over 4
-
-=item --no-storage
-
-Turn off storage checking. This is an alias for C<--check storage=0>.
-
-=item --only I<KEYWORD>
-
-This option can be specifed once and expects a keyword. The different
-keywords and the behaviour of check_openmanage is described below.
-
-=over 4
-
-=item B<critical>
-
-Print only critical alerts. With this option any warning alerts are
-suppressed.
-
-=item B<warning>
-
-Print only warning alerts. With this option any critical alerts are
-suppressed.
-
-=item B<chassis>
-
-Check all chassis components and nothing else.
-
-=item B<storage>
-
-Only check storage
-
-=item B<memory>
-
-Only check memory modules
-
-=item B<fans>
-
-Only check fans
-
-=item B<power>
-
-Only check power supplies
-
-=item B<temp>
-
-Only check temperatures
-
-=item B<cpu>
-
-Only check processors
-
-=item B<voltage>
-
-Only check voltage probes
-
-=item B<batteries>
-
-Only check batteries
-
-=item B<amperage>
-
-Only check power usage
-
-=item B<intrusion>
-
-Only check chassis intrusion
-
-=item B<sdcard>
-
-Only check SD cards
-
-=item B<esmhealth>
-
-Only check ESM log overall health, i.e. fill grade
-
-=item B<esmlog>
-
-Only check the event log (ESM) content
-
-=item B<alertlog>
-
-Only check the alert log content
-
-=back
-
-=item --check I<STRING> or I<FILE>
-
-This parameter allows you to adjust which components that should be
-checked at all. This is a rougher approach than blacklisting, which
-require that you specify component id or index. The parameter should
-be either a string containing the adjustments, or a file containing
-the string. No errors are raised if the file does not exist.
-
-Note: This option is ignored with alternate basenames.
-
-=over 9
-
-=item B<Example:>
-
-check_openmanage --check storage=0,intrusion=1
-
-=back
-
-Legal values are described below, along with the default value.
-
-=over 4
-
-=item B<storage>
-
-Check storage subsystem (controllers, disks etc.). Default: ON
-
-=item B<memory>
-
-Check memory (dimms). Default: ON
-
-=item B<fans>
-
-Check chassis fans. Default: ON
-
-=item B<power>
-
-Check power supplies. Default: ON
-
-=item B<temp>
-
-Check temperature sensors. Default: ON
-
-=item B<cpu>
-
-Check CPUs. Default: ON
-
-=item B<voltage>
-
-Check voltage sensors. Default: ON
-
-=item B<batteries>
-
-Check system batteries. Default: ON
-
-=item B<amperage>
-
-Check amperage probes. Default: ON
-
-=item B<intrusion>
-
-Check chassis intrusion. Default: ON
-
-=item B<sdcard>
-
-Check SD cards. Default: ON
-
-=item B<esmhealth>
-
-Check the ESM log health, i.e. fill grade. Default: ON
-
-=item B<esmlog>
-
-Check the ESM log content. Default: OFF
-
-=item B<alertlog>
-
-Check the alert log content. Default: OFF
-
-=back
-
-=back
-
-=head1 DIAGNOSTICS
-
-The option C<--debug> (or C<-d>) can be specified to display all
-monitored components.
-
-=head1 DEPENDENCIES
-
-If SNMP is requested, the perl module Net::SNMP is
-required. Otherwise, only a regular perl distribution is required to
-run the script. On the target (monitored) system, Dell Openmanage
-Server Administrator (OMSA) must be installed and running.
-
-=head1 EXIT STATUS
-
-If no errors are discovered, a value of 0 (OK) is returned. An exit
-value of 1 (WARNING) signifies one or more non-critical errors, while
-2 (CRITICAL) signifies one or more critical errors.
-
-The exit value 3 (UNKNOWN) is reserved for errors within the script,
-or errors getting values from Dell OMSA.
-
-=head1 AUTHOR
-
-Written by Trond H. Amundsen <t.h.amundsen@usit.uio.no>
-
-=head1 BUGS AND LIMITATIONS
-
-Storage info is not collected or checked on very old PowerEdge models
-and/or old OMSA versions, due to limitations in OMSA. The overall
-support on those models/versions by this plugin is not well tested.
-
-=head1 INCOMPATIBILITIES
-
-The plugin should work with the Nagios embedded perl interpreter
-(ePN). However, this is not thoroughly tested.
-
-=head1 REPORTING BUGS
-
-Report bugs to <t.h.amundsen@usit.uio.no>
-
-=head1 LICENSE AND COPYRIGHT
-
-This program is free software: you can redistribute it and/or modify
-it under the terms of the GNU General Public License as published by
-the Free Software Foundation, either version 3 of the License, or (at
-your option) any later version.
-
-This program is distributed in the hope that it will be useful, but
-WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-General Public License for more details.
-
-You should have received a copy of the GNU General Public License
-along with this program. If not, see L<http://www.gnu.org/licenses/>.
-
-=head1 SEE ALSO
-
-L<check_openmanage.conf(5)>
-L<http://folk.uio.no/trondham/software/check_openmanage.html>
-
-=cut
|
|
[-]
[+]
|
Changed |
check_openmanage-3.7.6.tar.bz2/CHANGES
^
|
| @@ -1,3 +1,24 @@
+3.7.6 2012-06-28
+------------------
+
+* Support for PCI attached storage (new in OMSA 7.0.0) was added
+* Support was added for negative temperature readings and thresholds
+ from temp probes
+* Fix for physical disk check. If a disk was marked as predictive
+ failure, and also had other failure conditions of a more severe
+ nature, check_openmange only reported the predictive failure
+ state. This has been fixed so that the most severe failure takes
+ precedence.
+* The iDRAC6 and iDRAC7 controllers was identified via SNMP using
+ integer values that are not defined in the MIB. This resulted in
+ internal error warnings if the '-o' option was used. The plugin now
+ defines these integer identifiers even though they are undocumented
+ in the MIB.
+* The PNP template now contains comments which identifies which plugin
+ version it was built for.
+* The manual pages were revised and completely rewritten from perl POD
+ to Docbook XML format.
+
3.7.5 2012-04-13
------------------
|
|
[-]
[+]
|
Changed |
check_openmanage-3.7.6.tar.bz2/README
^
|
| @@ -6,11 +6,12 @@
check_openmanage - The plugin
check_openmanage.exe - Win32 standalone executable
- check_openmanage.8 - Program man page
- check_openmanage.conf.5 - Config file man page
- check_openmanage.pod - Program man page source
- check_openmanage.conf.pod - Config file man page source
+ man/check_openmanage.8 - Program man page
+ man/check_openmanage.conf.5 - Config file man page
+ man/check_openmanage.5.xml - Program man page source
+ man/check_openmanage.conf.5.xml - Config file man page source
check_openmanage.php - PNP4Nagios template
+ check_openmanage_legacy.php - Legacy PNP4Nagios template
example.conf - An example configuration file
nagios-plugins-openmanage.spec - RPM spec file
COPYING - License information
@@ -62,6 +63,7 @@
* Power usage
* Chassis intrusion
* Removable flash media (SD cards)
+* Sane and not empty service tag (serial number)
Other:
|
|
[-]
[+]
|
Changed |
check_openmanage-3.7.6.tar.bz2/check_openmanage
^
|
| @@ -49,7 +49,7 @@
# Version and similar info
$NAME = 'check_openmanage';
-$VERSION = '3.7.5';
+$VERSION = '3.7.6';
$AUTHOR = 'Trond H. Amundsen';
$CONTACT = 't.h.amundsen@usit.uio.no';
@@ -1813,6 +1813,7 @@
6 => 'USB',
7 => 'SATA',
8 => 'SAS',
+ 9 => 'PCIe',
);
my %pdisk_state
@@ -1825,6 +1826,7 @@
6 => 'Degraded',
7 => 'Recovering',
11 => 'Removed',
+ 13 => 'Non-RAID',
15 => 'Resynching',
22 => 'Replacing', # FIXME: this one is not defined in the OMSA MIBs
24 => 'Rebuilding',
@@ -1943,12 +1945,11 @@
elsif (! defined $bus && defined $media) { $busmedia = "$media "; }
# Special case: Failure predicted
- if ($fpred) {
+ if ($fpred and $status eq 'Ok') {
my $msg = sprintf '%s [%s %s, %s] on ctrl %d needs attention: Failure Predicted',
$name, $vendor, $product, $capacity, $ctrl;
$msg .= " ($state)" if $state ne 'Predictive failure';
- report('storage', $msg,
- ($status2nagios{$status} == $E_CRITICAL ? $E_CRITICAL : $E_WARNING), $nexus);
+ report('storage', $msg, $E_WARNING, $nexus);
}
# Special case: Rebuilding / Replacing
elsif ($state =~ m{\A Rebuilding|Replacing \z}xms) {
@@ -2217,6 +2218,7 @@
4 => 'Timed out',
8 => 'Requested',
16 => 'Idle',
+ 32 => 'Due',
);
# This property displays the battery's ability to be charged
@@ -3507,11 +3509,11 @@
$discrete = $out->{temperatureProbeDiscreteReading} || '[N/A]';
# If numeric values, i.e. not discrete
- $reading /= 10 if $reading =~ m{\A \d+ \z}xms;
- $max_crit /= 10 if $max_crit =~ m{\A \d+ \z}xms;
- $max_warn /= 10 if $max_warn =~ m{\A \d+ \z}xms;
- $min_crit /= 10 if $min_crit =~ m{\A \d+ \z}xms;
- $min_warn /= 10 if $min_warn =~ m{\A \d+ \z}xms;
+ $reading /= 10 if $reading =~ m{\A -?\d+ \z}xms;
+ $max_crit /= 10 if $max_crit =~ m{\A -?\d+ \z}xms;
+ $max_warn /= 10 if $max_warn =~ m{\A -?\d+ \z}xms;
+ $min_crit /= 10 if $min_crit =~ m{\A -?\d+ \z}xms;
+ $min_warn /= 10 if $min_warn =~ m{\A -?\d+ \z}xms;
# workaround for bad temp probes
if ($type eq 'AmbientESM' and $reading !~ m{\A \d+(\.\d+)? \z}xms) {
@@ -3535,7 +3537,7 @@
$min_crit =~ s{\.0\s+C}{}xms;
$min_warn =~ s{\.0\s+C}{}xms;
- $type = $reading =~ m{\A\d+\z}xms ? 'AmbientESM' : 'Discrete';
+ $type = $reading =~ m{\A-?\d+\z}xms ? 'AmbientESM' : 'Discrete';
$discrete = $reading;
}
@@ -4013,8 +4015,20 @@
$count{volt}++;
next VOLT if blacklisted('volt', $index);
- my $msg = sprintf 'Voltage sensor %d [%s] is %s',
- $index, $location, $reading;
+ # remove trailing zeroes (if reading is an integer)
+ $reading =~ s{\A (\d+)\.000\sV \z}{$1 V}xms;
+
+ my $msg = undef;
+ if ($reading =~ m{\A \d+(:?\.\d+)?\sV \z}xms) {
+ # number reading
+ $msg = sprintf 'Voltage sensor %d [%s] reads %s',
+ $index, $location, $reading;
+ }
+ else {
+ # discrete reading
+ $msg = sprintf 'Voltage sensor %d [%s] is %s',
+ $index, $location, $reading;
+ }
my $err = $snmp ? $probestatus2nagios{$status} : $status2nagios{$status};
report('chassis', $msg, $err, $index);
@@ -4989,9 +5003,10 @@
15 => 'secondaryBackPlaneESM3And4', # Secondary Backplane for ESM 3 and 4 systems
16 => 'rac', # Remote Access Controller
17 => 'iDRAC', # Integrated Dell Remote Access Controller
- 18 => 'iDRAC', # Same as above (OMSA 7.0.0 bug!)
+ 18 => 'iDRAC6', # iDRAC6 (not defined in 7.0.0 MIB!)
19 => 'unifiedServerConfigurator', # Unified Server Configurator
20 => 'lifecycleController', # Lifecycle Controller
+ 21 => 'iDRAC7', # iDRAC7 (not defined in 7.0.0 MIB!)
);
@@ -5001,7 +5016,7 @@
$sysinfo{'bmc'} = 1;
$sysinfo{'bmc_fw'} = $out->{firmwareVersionName};
}
- elsif ($fw_type{$out->{firmwareType}} =~ m{\A rac|iDRAC \z}xms) {
+ elsif ($fw_type{$out->{firmwareType}} =~ m{\A rac|iDRAC. \z}xms) {
my $name = $out->{firmwareTypeName}; $name =~ s/\s//gxms;
$sysinfo{'rac'} = 1;
$sysinfo{'rac_name'} = $name;
|
|
|
Changed |
check_openmanage-3.7.6.tar.bz2/check_openmanage.exe
^
|
|
[-]
[+]
|
Changed |
check_openmanage-3.7.6.tar.bz2/check_openmanage.php
^
|
| @@ -1,14 +1,14 @@
<?php
#
-# PNP4Nagios template for check_openmanage
+# PNP4Nagios template for check_openmanage
+#
# Author: Trond Hasle Amundsen
# Contact: t.h.amundsen@usit.uio.no
# Website: http://folk.uio.no/trondham/software/check_openmanage.html
-# Date: 2011-08-15
-#
-# $Id$
+# Date: 2012-06-28
+# Version: 3.7.6
#
-# Copyright (C) 2008-2011 Trond H. Amundsen
+# Copyright (C) 2008-2012 Trond Hasle Amundsen
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
|
|
[-]
[+]
|
Added |
check_openmanage-3.7.6.tar.bz2/check_openmanage_legacy.php
^
|
| @@ -0,0 +1,221 @@
+<?php
+#
+# PNP4Nagios template for check_openmanage
+# Author: Trond Hasle Amundsen
+# Contact: t.h.amundsen@usit.uio.no
+# Website: http://folk.uio.no/trondham/software/check_openmanage.html
+# Date: 2010-03-16
+
+# Array with different colors
+$colors = array("0022ff", "22ff22", "ff0000", "00aaaa", "ff00ff",
+ "ffa500", "cc0000", "0000cc", "0080C0", "8080C0",
+ "FF0080", "800080", "688e23", "408080", "808000",
+ "000000", "00FF00", "0080FF", "FF8000", "800000",
+ "FB31FB");
+
+# Color for power usage in watts
+$PWRcolor = "66FF00";
+
+# Counters
+$count = 0; # general counter
+$f = 0; # fan probe counter
+$t = 0; # temp probe counter
+$a = 0; # amp probe counter
+$e = 0; # enclosure counter
+
+# Flags
+$visited_fan = 0;
+$visited_temp = 0;
+$visited_pwr = 0;
+
+# Enclosure id
+$enclosure_id = '';
+
+# Default title
+$def_title = 'Dell OpenManage';
+
+# Loop through the performance data
+foreach ($DS as $i) {
+
+ # AMPERAGE PROBE
+ if(preg_match('/^pwr_mon_/', $NAME[$i]) || preg_match('/^p\d+[aw]$/', $NAME[$i])) {
+
+ # Watt
+ if (preg_match('/system/', $NAME[$i]) || preg_match('/^p\d+w$/', $NAME[$i])) {
+
+ # Long label
+ $NAME[$i] = preg_replace('/^pwr_mon_\d+_/', '', $NAME[$i]);
+ $NAME[$i] = preg_replace('/_/', ' ', $NAME[$i]);
+
+ # Short label
+ $NAME[$i] = preg_replace('/^p(\d+)w$/', 'Power Probe $1', $NAME[$i]);
+
+ ++$count;
+ $ds_name[$count] = "Power Consumption";
+ $vlabel = "Watt";
+
+ $title = $ds_name[$count];
+
+ $opt[$count] = "--slope-mode --vertical-label \"$vlabel\" --title \"$def_title: $title\" ";
+
+ if(isset($def[$count])){
+ $def[$count] .= "DEF:var$i=$rrdfile:$DS[$i]:AVERAGE " ;
+ }
+ else {
+ $def[$count] = "DEF:var$i=$rrdfile:$DS[$i]:AVERAGE " ;
+ }
+ $def[$count] .= "AREA:var$i#$PWRcolor:\"$NAME[$i]\" " ;
+ $def[$count] .= "LINE:var$i#000000: " ;
+ $def[$count] .= "GPRINT:var$i:LAST:\"%6.0lf W last \" ";
+ $def[$count] .= "GPRINT:var$i:MAX:\"%6.0lf W max \" ";
+ $def[$count] .= "GPRINT:var$i:AVERAGE:\"%6.2lf W avg \\n\" ";
+ }
+ # Ampere
+ elseif (preg_match('/current/', $NAME[$i]) || preg_match('/^p\d+a$/', $NAME[$i])) {
+
+ # Long label
+ $NAME[$i] = preg_replace('/^pwr_mon_\d+_/', '', $NAME[$i]);
+ $NAME[$i] = preg_replace('/_/', ' ', $NAME[$i]);
+ $NAME[$i] = preg_replace('/ current \d+$/', '', $NAME[$i]);
+ $NAME[$i] = preg_replace('/ps/', 'PowerSupply', $NAME[$i]);
+
+ # Short label
+ $NAME[$i] = preg_replace('/^p(\d+)a$/', 'Amperage Probe $1', $NAME[$i]);
+
+ if ($visited_pwr == 0) {
+ ++$count;
+ $visited_pwr = 1;
+ }
+ $ds_name[$count] = "Amperage Probes";
+ $vlabel = "Ampere";
+
+ $title = $ds_name[$count];
+
+ $opt[$count] = "-X0 --lower-limit 0 --slope-mode --vertical-label \"$vlabel\" --title \"$def_title: $title\" ";
+ if(isset($def[$count])){
+ $def[$count] .= "DEF:var$i=$rrdfile:$DS[$i]:AVERAGE " ;
+ }
+ else {
+ $def[$count] = "DEF:var$i=$rrdfile:$DS[$i]:AVERAGE " ;
+ }
+ $def[$count] .= "LINE:var$i#".$colors[$a].":\"$NAME[$i]\" " ;
+ $def[$count] .= "AREA:var$i#".$colors[$a++]."20: " ;
+ $def[$count] .= "GPRINT:var$i:LAST:\"%4.2lf A last \" ";
+ $def[$count] .= "GPRINT:var$i:MAX:\"%4.2lf A max \" ";
+ $def[$count] .= "GPRINT:var$i:AVERAGE:\"%4.4lf A avg \\n\" ";
+ }
+ }
+
+ # FANS (RPMs)
+ if(preg_match('/^fan_/', $NAME[$i]) || preg_match('/^f\d+$/', $NAME[$i])){
+ if ($visited_fan == 0) {
+ ++$count;
+ $visited_fan = 1;
+ }
+
+ # Long label
+ $NAME[$i] = preg_replace('/^fan_\d+_/', '', $NAME[$i]);
+ $NAME[$i] = preg_replace('/_rpm$/', '', $NAME[$i]);
+ $NAME[$i] = preg_replace('/_/', ' ', $NAME[$i]);
+
+ # Short label
+ $NAME[$i] = preg_replace('/^f(\d+)$/', 'Fan Probe $1', $NAME[$i]);
+
+ $ds_name[$count] = "Fan Speed";
+
+ $opt[$count] = "-X0 --slope-mode --vertical-label \"RPMs\" --title \"$def_title: Fan Speeds\" ";
+ if(isset($def[$count])){
+ $def[$count] .= "DEF:var$i=$rrdfile:$DS[$i]:AVERAGE " ;
+ }
+ else {
+ $def[$count] = "DEF:var$i=$rrdfile:$DS[$i]:AVERAGE " ;
+ }
+ $def[$count] .= "LINE:var$i#".$colors[$f++].":\"$NAME[$i]\" " ;
+ $def[$count] .= "GPRINT:var$i:LAST:\"%6.0lf RPM last \" ";
+ $def[$count] .= "GPRINT:var$i:MAX:\"%6.0lf RPM max \" ";
+ $def[$count] .= "GPRINT:var$i:AVERAGE:\"%6.2lf RPM avg \\n\" ";
+ }
+
+ # TEMPERATURES (Celsius)
+ if(preg_match('/^temp_/', $NAME[$i]) || preg_match('/^t\d+$/', $NAME[$i])){
+ if ($visited_temp == 0) {
+ ++$count;
+ $visited_temp = 1;
+ }
+
+ # Long label
+ $NAME[$i] = preg_replace('/^temp_\d+_/', '', $NAME[$i]);
+ $NAME[$i] = preg_replace('/_/', ' ', $NAME[$i]);
+
+ # Short label
+ $NAME[$i] = preg_replace('/^t(\d+)$/', 'Temperature Probe $1', $NAME[$i]);
+
+ $ds_name[$count] = "Chassis Temperatures";
+
+ $warnThresh = "INF";
+ $critThresh = "INF";
+
+ if ($WARN[$i] != "") {
+ $warnThresh = $WARN[$i];
+ }
+ if ($CRIT[$i] != "") {
+ $critThresh = $CRIT[$i];
+ }
+
+ $opt[$count] = "--slope-mode --vertical-label \"Celsius\" --title \"$def_title: Chassis Temperatures\" ";
+ if(isset($def[$count])){
+ $def[$count] .= "DEF:var$i=$rrdfile:$DS[$i]:AVERAGE " ;
+ }
+ else {
+ $def[$count] = "DEF:var$i=$rrdfile:$DS[$i]:AVERAGE " ;
+ }
+ $def[$count] .= "LINE:var$i#".$colors[$t++].":\"$NAME[$i]\" " ;
+ $def[$count] .= "GPRINT:var$i:LAST:\"%6.0lf C last \" ";
+ $def[$count] .= "GPRINT:var$i:MAX:\"%6.0lf C max \" ";
+ $def[$count] .= "GPRINT:var$i:AVERAGE:\"%6.2lf C avg \\n\" ";
+ }
+
+ # ENCLOSURE TEMPERATURES (Celsius)
+ if(preg_match('/^enclosure_(?P<id>.+?)_temp_\d+$/', $NAME[$i], $matches)
+ || preg_match('/^e(?P<id>.+?)t\d+$/', $NAME[$i], $matches)) {
+ $this_id = $matches['id'];
+
+ if ($enclosure_id != $this_id) {
+ $e = 0;
+ ++$count;
+ $enclosure_id = $this_id;
+ }
+
+ # Long label
+ $NAME[$i] = preg_replace('/^enclosure_.+?_temp_(\d+)$/', 'Probe $1', $NAME[$i]);
+
+ # Short label
+ $NAME[$i] = preg_replace('/^e.+?t(\d+)$/', 'Probe $1', $NAME[$i]);
+
+ $ds_name[$count] = "Enclosure $enclosure_id Temperatures";
+
+ $warnThresh = "INF";
+ $critThresh = "INF";
+
+ if ($WARN[$i] != "") {
+ $warnThresh = $WARN[$i];
+ }
+ if ($CRIT[$i] != "") {
+ $critThresh = $CRIT[$i];
+ }
+
+ $opt[$count] = "--slope-mode --vertical-label \"Celsius\" --title \"$def_title: Enclosure $enclosure_id Temperatures\" ";
+
+ if(isset($def[$count])){
+ $def[$count] .= "DEF:var$i=$rrdfile:$DS[$i]:AVERAGE " ;
+ }
+ else {
+ $def[$count] = "DEF:var$i=$rrdfile:$DS[$i]:AVERAGE " ;
+ }
+ $def[$count] .= "LINE:var$i#".$colors[$e++].":\"$NAME[$i]\" " ;
+ $def[$count] .= "GPRINT:var$i:LAST:\"%6.0lf C last \" ";
+ $def[$count] .= "GPRINT:var$i:MAX:\"%6.0lf C max \" ";
+ $def[$count] .= "GPRINT:var$i:AVERAGE:\"%6.2lf C avg \\n\" ";
+ }
+}
+?>
|
|
[-]
[+]
|
Changed |
check_openmanage-3.7.6.tar.bz2/debian/changelog
^
|
| @@ -1,3 +1,9 @@
+check-openmanage (3.7.6-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Trond Hasle Amundsen <t.h.amundsen@usit.uio.no> Thu, 28 Jun 2012 12:00:00 +0200
+
check-openmanage (3.7.5-1) unstable; urgency=low
* New upstream release.
|
|
[-]
[+]
|
Changed |
check_openmanage-3.7.6.tar.bz2/debian/rules
^
|
| @@ -43,9 +43,9 @@
dh_testroot
dh_installchangelogs CHANGES
dh_installdocs
- dh_installexamples check_openmanage.php
- dh_installman check_openmanage.8
- dh_installman check_openmanage.conf.5
+ dh_installexamples check_openmanage.php example.conf
+ dh_installman man/check_openmanage.8
+ dh_installman man/check_openmanage.conf.5
dh_link
dh_strip
dh_compress
|
|
[-]
[+]
|
Changed |
check_openmanage-3.7.6.tar.bz2/install.sh
^
|
| @@ -51,8 +51,8 @@
# Install
install -p -m 0755 check_openmanage $plugindir
-install -m 0644 check_openmanage.8 $man8dir
-install -m 0644 check_openmanage.conf.5 $man5dir
+install -m 0644 man/check_openmanage.8 $man8dir
+install -m 0644 man/check_openmanage.conf.5 $man5dir
# Done
echo "done."
|
|
[-]
[+]
|
Added |
check_openmanage-3.7.6.tar.bz2/man
^
|
| +(directory)
|
|
[-]
[+]
|
Added |
check_openmanage-3.7.6.tar.bz2/man/Makefile
^
|
| @@ -0,0 +1,27 @@
+# Special variables
+DOCBOOK_XSLT = http://docbook.sourceforge.net/release/xsl/current/manpages/profile-docbook.xsl
+XSLTPROC = /usr/bin/xsltproc
+XSLTPROC_FLAGS = --catalogs --xinclude --nonet --stringparam profile.condition "with_false"
+XMLLINT = /usr/bin/xmllint
+XMLLINT_FLAGS = --catalogs --postvalid --nonet --xinclude --noout
+SGML_CATALOG_FILES = /etc/xml/catalog
+
+export SGML_CATALOG_FILES
+
+MANS = check_openmanage.8 check_openmanage.conf.5
+
+default: man
+
+man: $(MANS)
+
+clean:
+ rm $(MANS)
+
+check_openmanage.8: check_openmanage.8.xml
+ $(XMLLINT) $(XMLLINT_FLAGS) $<
+ $(XSLTPROC) -o $@ $(XSLTPROC_FLAGS) $(DOCBOOK_XSLT) $<
+
+check_openmanage.conf.5: check_openmanage.conf.5.xml
+ $(XMLLINT) $(XMLLINT_FLAGS) $<
+ $(XSLTPROC) -o $@ $(XSLTPROC_FLAGS) $(DOCBOOK_XSLT) $<
+
|
|
[-]
[+]
|
Added |
check_openmanage-3.7.6.tar.bz2/man/check_openmanage.8
^
|
| @@ -0,0 +1,949 @@
+'\" t
+.\" Title: check_openmanage
+.\" Author: Trond Hasle Amundsen <t.h.amundsen@usit.uio.no>
+.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
+.\" Date: 06/28/2012
+.\" Manual: Nagios plugin
+.\" Source: check_openmanage
+.\" Language: English
+.\"
+.TH "CHECK_OPENMANAGE" "8" "06/28/2012" "check_openmanage" "Nagios plugin"
+.\" -----------------------------------------------------------------
+.\" * set default formatting
+.\" -----------------------------------------------------------------
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.\" -----------------------------------------------------------------
+.\" * MAIN CONTENT STARTS HERE *
+.\" -----------------------------------------------------------------
+.SH "NAME"
+check_openmanage \- Nagios plugin for checking the hardware status on Dell servers running OpenManage
+.SH "SYNOPSIS"
+.HP \w'\fBcheck_openmanage\fR\ 'u
+\fBcheck_openmanage\fR [\fIoption\fR\&.\&.\&.]
+.HP \w'\fBcheck_openmanage\fR\ 'u
+\fBcheck_openmanage\fR \-H\ \fIhostname\fR [\fIoption\fR\&.\&.\&.]
+.SH "DESCRIPTION"
+.PP
+
+\fBcheck_openmanage\fR
+is a plugin for Nagios which checks the hardware health of Dell servers running OpenManage Server Administrator (OMSA)\&. The plugin checks the health of the storage subsystem, power supplies, memory modules, temperature probes etc\&., and gives an alert if any of the components are faulty or operate outside normal parameters\&.
+.PP
+
+\fBcheck_openmanage\fR
+is designed to be used by either locally (using NRPE or similar) or remotely (using SNMP)\&. In either mode, the output is (nearly) the same\&. Note that checking the alert log is not supported in SNMP mode\&.
+.SH "GENERAL OPTIONS"
+.PP
+\fB\-f\fR, \fB\-\-config \fR\fB\fIfile\fR\fR
+.RS 4
+Specify a configuration file\&. For reference on the config file syntax and options, consult the
+\fBcheck_openmanage.conf\fR(5)
+manual page\&.
+.RE
+.PP
+\fB\-t\fR, \fB\-\-timeout \fR\fB\fIseconds\fR\fR
+.RS 4
+The number of seconds after which the plugin will abort\&. Default timeout is 30 seconds if the option is not present\&.
+.RE
+.PP
+\fB\-p\fR, \fB\-\-perfdata\fR [\fIargument\fR]
+.RS 4
+Collect performance data\&. Performance data collected include temperatures (in Celsius) and fan speeds (in rpm)\&. On systems that support it, power consumption is also collected (in Watts)\&. This option takes one of two arguments, both of which are optional:
+.PP
+\fIminimal\fR
+.RS 4
+If
+\fIminimal\fR
+is specified as argument, the plugin will use shorter names for the performance data labels, e\&.g\&.
+\(lqt0\(rq
+instead of
+\(lqtemp_0_system_board_ambient\(rq\&. This can be used as a workaround in cases where the plugin output needs shortening, for example if the 1024 character limit of NRPE is reached\&.
+.RE
+.PP
+\fImultiline\fR
+.RS 4
+If
+\fImultiline\fR
+is specified as argument, the plugin will output the performance data on multiple lines, for Nagios 3\&.x and above\&.
+.RE
+.sp
+The default behaviour should be sufficient for most users\&.
+.RE
+.PP
+\fB\-\-legacy\-perfdata\fR
+.RS 4
+With version 3\&.7\&.0, performance data output changed\&. The new format is not compatible with the old format\&. Users who wish to postpone switching to the new performance data API may set this option\&.
+.RE
+.PP
+\fB\-w\fR, \fB\-\-warning\fR \fIstring\fR | \fIfile\fR
+.RS 4
+Override the machine\-default temperature warning thresholds\&. Syntax is:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+\fIid1\fR=\fImax\fR[/\fImin\fR],\fIid2\fR=\fImax\fR[/\fImin\fR],\&.\&.\&.
+
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+The following example sets warning limits to max 50C for probe 0, and max 45C and min 10C for probe 1:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+check_openmanage \-w 0=50,1=45/10
+
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+The minimum limit can be omitted, if desired\&. Most often, you are only interested in setting the maximum thresholds\&.
+.sp
+This parameter can be either a string with the limits, or a file containing the limits string\&. The option can be specified multiple times\&.
+.sp
+
+\fINOTE\fR: This option should only be used to narrow the field of OK temperatures wrt\&. the OMSA defaults\&. To expand the field of OK temperatures, increase the OMSA thresholds\&. See the plugin web page for more information\&.
+.RE
+.PP
+\fB\-c\fR, \fB\-\-critical\fR \fIstring\fR | \fIfile\fR
+.RS 4
+Override the machine\-default temperature critical thresholds\&. Syntax and behaviour is the same as for warning thresholds described above\&.
+.RE
+.PP
+\fB\-F\fR, \fB\-\-fahrenheit\fR
+.RS 4
+Set Fahrenheit as unit for all temperatures\&. This option will override the
+\fB\-\-tempunit\fR
+option, if used simultaneously\&.
+.RE
+.PP
+\fB\-\-tempunit\fR \fIunit\fR
+.RS 4
+Set temperature unit\&. Legal values are:
+.sp
+\fIF\fR: Fahrenheit
+.sp
+\fIC\fR: Celsius
+.sp
+\fIK\fR: Kelvin
+.sp
+\fIR\fR: Rankine
+.sp
+Default: C
+.RE
+.PP
+\fB\-\-omreport\fR \fIpath\fR
+.RS 4
+Specify full path to omreport, if it is not installed in any of the regular places\&. Usually this option is only needed on Windows, if omreport is not installed on the C: drive\&.
+.RE
+.PP
+\fB\-d\fR, \fB\-\-debug\fR
+.RS 4
+Debug output\&. Will report status on everything, even if status is ok\&. Blacklisted or unchecked components are ignored (i\&.e\&. no output)\&.
+.sp
+
+\fINOTE\fR: This option is intended for diagnostics and debugging purposes only\&. Do not use this option from within Nagios, i\&.e\&. in the Nagios config\&.
+.RE
+.PP
+\fB\-h\fR, \fB\-\-help\fR
+.RS 4
+Display help message and exit\&.
+.RE
+.PP
+\fB\-V\fR, \fB\-\-version\fR
+.RS 4
+Print version info and exit\&.
+.RE
+.SH "OUTPUT OPTIONS"
+.PP
+\fB\-o\fR, \fB\-\-ok\-info\fR \fIlevel\fR
+.RS 4
+This option lets you define how much output you want the plugin to give when everything is OK, i\&.e\&. the verbosity level\&. The default value is 0 (one line of output)\&. The output levels are cumulative\&.
+.sp
+
+\fI0\fR: Only one line
+.sp
+
+\fI1\fR: BIOS and firmware info on a separate line
+.sp
+
+\fI2\fR: Storage controller and enclosure info on separate lines
+.sp
+
+\fI3\fR: OMSA version on separate line
+.sp
+Default: 0
+.sp
+The reason that OMSA version is separated from the rest is that finding it requires running a really slow omreport command, when the plugin is run locally via NRPE\&.
+.RE
+.PP
+\fB\-B\fR, \fB\-\-show\-blacklist\fR
+.RS 4
+If used together with blacklisting, this option will make the plugin output all blacklistings that are being used\&. The output will have the correct blacklisting syntax, and will make it easy to maintain control over which blacklistings that are used for each server, as any blacklistings can be viewed from Nagios\&.
+.sp
+When blacklisting is not used, this option has no effect\&.
+.RE
+.PP
+\fB\-i\fR, \fB\-\-info\fR
+.RS 4
+Prefix any alerts with the service tag\&.
+.RE
+.PP
+\fB\-e\fR, \fB\-\-extinfo\fR
+.RS 4
+Display a short summary of system information (model and service tag) in case of an alert\&.
+.RE
+.PP
+\fB\-I\fR, \fB\-\-htmlinfo\fR [\fIcode\fR]
+.RS 4
+Using this option will make the servicetag and model name into clickable HTML links in the output\&. The model name link will point to the official Dell documentation for that model, while the servicetag link will point to a website containing support info for that particular server\&.
+.sp
+This option takes an optional argument, which should be a country or area code or\&. If the country code is omitted the servicetag link will still work, but it will not be speficic for your country or area\&. Example for Germany:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+check_openmanage \-\-htmlinfo de
+
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+If this option is used together with either the
+\fB\-\-extinfo\fR
+or
+\fB\-\-info\fR
+options, it is particularly useful\&. Only the most common country codes is supported at this time:
+.TS
+expand tab(:);
+l s s
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l s s
+l s s
+l l l
+l l l
+l s s
+l s s
+l l l
+l l l.
+T{
+Europe, Middle East and Africa (EMEA)
+T}
+T{
+\fIat\fR: Austria
+T}:T{
+\fIbe\fR: Belgium
+T}:T{
+\fIcz\fR: Czech Republic
+T}
+T{
+\fIde\fR: Germany
+T}:T{
+\fIdk\fR: Denmark
+T}:T{
+\fIes\fR: Spain
+T}
+T{
+\fIfi\fR: Finland
+T}:T{
+\fIfr\fR: France
+T}:T{
+\fIgr\fR: Greece
+T}
+T{
+\fIit\fR: Italy
+T}:T{
+\fIil\fR: Israel
+T}:T{
+\fIme\fR: Middle East
+T}
+T{
+\fIno\fR: Norway
+T}:T{
+\fInl\fR: The Netherlands
+T}:T{
+\fIpl\fR: Poland
+T}
+T{
+\fIpt\fR: Portugal
+T}:T{
+\fIru\fR: Russia
+T}:T{
+\fIse\fR: Sweden
+T}
+T{
+\fIuk\fR: United Kingdom
+T}:T{
+\fIza\fR: South Africa
+T}:T{
+
+T}
+T{
+\ \&
+T}
+T{
+America
+T}
+T{
+\fIbr\fR: Brazil
+T}:T{
+\fIca\fR: Canada
+T}:T{
+\fImx\fR: Mexico
+T}
+T{
+\fIus\fR: USA
+T}:T{
+
+T}:T{
+
+T}
+T{
+\ \&
+T}
+T{
+Asia / Pacific
+T}
+T{
+\fIau\fR: Australia
+T}:T{
+\fIcn\fR: China
+T}:T{
+\fIin\fR: India
+T}
+T{
+\fIjp\fR: Japan
+T}:T{
+
+T}:T{
+
+T}
+.TE
+.sp 1
+.RE
+.PP
+\fB\-\-postmsg\fR \fIstring\fR | \fIfile\fR
+.RS 4
+User specified post message\&. Useful for displaying arbitrary or various system information at the end of alerts\&. The argument is either a string with the message, or a file containing that string\&. You can control the format with the following interpreted sequences:
+.sp
+
+\fI%m\fR: System model
+.sp
+
+\fI%s\fR: Service tag
+.sp
+
+\fI%b\fR: BIOS version
+.sp
+
+\fI%d\fR: BIOS release date
+.sp
+
+\fI%o\fR: Operating system name
+.sp
+
+\fI%r\fR: Operating system release
+.sp
+
+\fI%p\fR: Number of physical drives
+.sp
+
+\fI%l\fR: Number of logical drives
+.sp
+
+\fI%n\fR: Line break\&. Will be a regular line break if run from a TTY, else an HTML line break\&.
+.sp
+
+\fI%%\fR: A literal
+\(lq%\(rq
+.RE
+.PP
+\fB\-s\fR, \fB\-\-state\fR
+.RS 4
+Prefix each alert with its corresponding service state (i\&.e\&. warning, critical etc\&.)\&. This is useful in case of several alerts from the same monitored system\&.
+.RE
+.PP
+\fB\-S\fR, \fB\-\-short\-state\fR
+.RS 4
+Same as the
+\fB\-\-state\fR
+option above, except that the state is abbreviated to a single letter (\fIW\fR=warning,
+\fIC\fR=critical etc\&.)\&.
+.RE
+.PP
+\fB\-\-hide\-servicetag\fR
+.RS 4
+This option will replace the servicetag (serial number) in the output with
+\(lqXXXXXXX\(rq\&. Use this option to suppress or censor the servicetag in the plugin output\&.
+.RE
+.PP
+\fB\-\-linebreak\fR \fIstring\fR
+.RS 4
+check_openmanage will sometimes report more than one line, e\&.g\&. if there are several alerts\&. If the script has a TTY, it will use regular linebreaks\&. If not (which is the case with NRPE) it will use HTML linebreaks\&. Sometimes it can be useful to control what the plugin uses as a line separator, and this option provides that control\&.
+.sp
+The argument is the exact string to be used as the line separator\&. There are two exceptions, i\&.e\&. two keywords that translates to the following:
+.sp
+
+\fIREG\fR: Regular linebreaks, i\&.e\&.
+\(lq\en\(rq\&.
+.sp
+
+\fIHTML\fR: HTML linebreaks, i\&.e\&.
+\(lq<br/>\(rq\&.
+.sp
+This is a rather special option that is normally not needed\&. The default behaviour should be sufficient for most users\&.
+.RE
+.SH "SNMP OPTIONS"
+.PP
+\fB\-H\fR, \fB\-\-hostname \fR\fB\fIhostname\fR\fR
+.RS 4
+The transport address of the destination SNMP device\&. Using this option triggers SNMP mode\&.
+.RE
+.PP
+\fB\-P\fR, \fB\-\-protocol\fR \fIprotocol\-number\fR
+.RS 4
+SNMP protocol version\&. This option is optional and expects either of the following:
+.sp
+\fI1\fR: SNMP version 1
+.sp
+\fI2\fR,
+\fI2c\fR: SNMP version 2c
+.sp
+\fI3\fR: SNMP version 3
+.sp
+Default: 2c
+.RE
+.PP
+\fB\-\-port\fR \fIport\-number\fR
+.RS 4
+SNMP port of the remote (monitored) system\&. Defaults to the well\-known SNMP port 161\&.
+.RE
+.PP
+\fB\-6\fR, \fB\-\-ipv6\fR
+.RS 4
+This option will cause the plugin to use IPv6\&. The default is IPv4 if the option is not present\&.
+.RE
+.PP
+\fB\-\-tcp\fR
+.RS 4
+This option will cause the plugin to use TCP as transport protocol\&. The default is UDP if the option is not present\&.
+.RE
+.PP
+\fB\-U\fR, \fB\-\-username\fR \fIsecurityname\fR
+.RS 4
+[SNMPv3] The User\-based Security Model (USM) used by SNMPv3 requires that a securityName be specified\&. This option is required when using SNMP version 3, and expects a string 1 to 32 octets in lenght\&.
+.RE
+.PP
+\fB\-\-authpassword\fR \fIpassword\fR, \fB\-\-authkey\fR \fIkey\fR
+.RS 4
+[SNMPv3] By default a securityLevel of
+\fInoAuthNoPriv\fR
+is assumed\&. If the
+\fB\-\-authpassword\fR
+option is specified, the securityLevel becomes
+\fIauthNoPriv\fR\&. The
+\fB\-\-authpassword\fR
+option expects a string which is at least 1 octet in length as argument\&.
+.sp
+Optionally, instead of the
+\fB\-\-authpassword\fR
+option, the
+\fB\-\-authkey\fR
+option can be used so that a plain text password does not have to be specified in a script\&. The
+\fB\-\-authkey\fR
+option expects a hexadecimal string produced by localizing the password with the authoritativeEngineID for the specific destination device\&. The
+\fBsnmpkey\fR
+utility included with the Net::SNMP distribution can be used to create the hexadecimal string\&. See
+\fBsnmpkey\fR(1)
+for more information\&.
+.RE
+.PP
+\fB\-\-authprotocol\fR \fIalgorithm\fR
+.RS 4
+[SNMPv3] Two different hash algorithms are defined by SNMPv3 which can be used by the Security Model for authentication\&. These algorithms are HMAC\-MD5\-96
+\(lqMD5\(rq
+(RFC 1321) and HMAC\-SHA\-96
+\(lqSHA\-1\(rq
+(NIST FIPS PUB 180\-1)\&. The default algorithm used by the plugin is HMAC\-MD5\-96\&. This behavior can be changed by using this option\&. The option expects either the string
+\fImd5\fR
+or
+\fIsha\fR
+to be passed as argument to modify the hash algorithm\&.
+.RE
+.PP
+\fB\-\-privpassword\fR \fIpassword\fR, \fB\-\-privkey\fR \fIkey\fR
+.RS 4
+[SNMPv3] By specifying the options
+\fB\-\-privkey\fR
+or
+\fB\-\-privpassword\fR, the securityLevel associated with the object becomes
+\fIauthPriv\fR\&. According to SNMPv3, privacy requires the use of authentication\&. Therefore, if either of these two options are present and the
+\fB\-\-authkey\fR
+or
+\fB\-\-authpassword\fR
+arguments are missing, the creation of the object fails\&. The
+\fB\-\-privkey\fR
+and
+\fB\-\-privpassword\fR
+options expect the same input as the
+\fB\-\-authkey\fR
+and
+\fB\-\-authpassword\fR
+options respectively\&.
+.RE
+.PP
+\fB\-\-privprotocol\fR \fIalgorithm\fR
+.RS 4
+[SNMPv3] The User\-based Security Model described in RFC 3414 defines a single encryption protocol to be used for privacy\&. This protocol, CBC\-DES
+\(lqDES\(rq
+(NIST FIPS PUB 46\-1), is used by default or if the string
+\fIdes\fR
+is passed to the
+\fB\-\-privprotocol\fR
+option\&. The Net::SNMP module also supports RFC 3826 which describes the use of CFB128\-AES\-128
+\(lqAES\(rq
+(NIST FIPS PUB 197) in the USM\&. The AES encryption protocol can be selected by passing
+\fIaes\fR
+or
+\fIaes128\fR
+to the
+\fB\-\-privprotocol\fR
+option\&.
+.sp
+One of the following arguments are required: des, aes, aes128, 3des, 3desde
+.RE
+.PP
+\fB\-\-use\-get_table\fR
+.RS 4
+This option exists as a workaround when using check_openmanage with SNMPv3 on Windows with net\-snmp\&. Using this option will make check_openmanage use the Net::SNMP function get_table() instead of get_entries() while fetching values via SNMP\&. The latter is faster and is the default\&.
+.RE
+.SH "BLACKLISTING"
+.PP
+\fB\-b\fR, \fB\-\-blacklist\fR \fIstring\fR | \fIfile\fR
+.RS 4
+Blacklist missing and/or failed components, if you do not plan to fix them\&. The parameter is either the blacklist string, or a file (that may or may not exist) containing the string\&. The blacklist string contains component names with component IDs separated by slash
+\(lq/\(rq\&. Blacklisted components are left unchecked\&.
+.sp
+
+\fITIP\fR: Use the option
+\fB\-d\fR
+or
+\fB\-\-debug\fR
+to get the blacklist ID for devices\&. The ID is listed in a separate column in the debug output\&.
+.sp
+
+\fINOTE\fR: If blacklisting is in effect, the global health of the system is not checked\&.
+.sp
+Syntax:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+\fIcomponent1\fR=\fIid1\fR[,\fIid2\fR,\&.\&.\&.]/\fIcomponent2\fR=\fIid1\fR[,\fIid2\fR,\&.\&.\&.]/\&.\&.\&.
+
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+The ID part can also be
+\(lqall\(rq, in which all components of that type is blacklisted\&.
+.sp
+Example:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+check_openmanage \-b ps=0/fan=3,5/pdisk=1:0:0:1/ctrl_driver=all
+
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+In the example we blacklist powersupply 0, fans 3 and 5, physical disk 1:0:0:1, and warnings about out\-of\-date drivers for all controllers\&. Legal component names include:
+.PP
+\fIctrl\fR
+.RS 4
+Storage controller\&. Note that if a controller is blacklisted, all components on that controller (such as physical and logical drives) are blacklisted as well\&.
+.RE
+.PP
+\fIctrl_fw\fR
+.RS 4
+Suppress the special warning message about old controller firmware\&. Use this if you can not or will not upgrade the firmware\&.
+.RE
+.PP
+\fIctrl_driver\fR
+.RS 4
+Suppress the special warning message about old controller driver\&. Particularly useful on systems where you can not upgrade the driver\&.
+.RE
+.PP
+\fIctrl_stdr\fR
+.RS 4
+Suppress the special warning message about old Storport driver on Windows\&.
+.RE
+.PP
+\fIctrl_pdisk\fR
+.RS 4
+This blacklisting keyword exists as a possible workaround for physical drives with bad firmware which makes Openmanage choke\&. It takes the controller number as argument\&. Use this option to blacklist all physical drives on a specific controller\&. This blacklisting keyword is only available in local mode, i\&.e\&. not with SNMP\&.
+.RE
+.PP
+\fIpdisk\fR
+.RS 4
+Physical disk\&.
+.RE
+.PP
+\fIpdisk_cert\fR
+.RS 4
+Suppress warning message about non\-certified physical disk\&.
+.RE
+.PP
+\fIpdisk_foreign\fR
+.RS 4
+Suppress warning message about foreign physical disk\&.
+.RE
+.PP
+\fIvdisk\fR
+.RS 4
+Logical drive (virtual disk)\&.
+.RE
+.PP
+\fIbat\fR
+.RS 4
+Controller cache battery\&.
+.RE
+.PP
+\fIbat_charge\fR
+.RS 4
+Ignore warnings related to the controller cache battery charging cycle, which happens approximately every 40\-90 days on Dell servers\&. Note that using this blacklist keyword makes check_openmanage ignore non\-critical cache battery errors\&.
+.RE
+.PP
+\fIconn\fR
+.RS 4
+Connector (channel)\&.
+.RE
+.PP
+\fIencl\fR
+.RS 4
+Storage enclosure\&.
+.RE
+.PP
+\fIencl_fan\fR
+.RS 4
+Enclosure fan\&.
+.RE
+.PP
+\fIencl_ps\fR
+.RS 4
+Enclosure power supply\&.
+.RE
+.PP
+\fIencl_temp\fR
+.RS 4
+Enclosure temperature probe\&.
+.RE
+.PP
+\fIencl_emm\fR
+.RS 4
+Enclosure management module (EMM)\&.
+.RE
+.PP
+\fIdimm\fR
+.RS 4
+Memory module\&.
+.RE
+.PP
+\fIfan\fR
+.RS 4
+Chassis fan\&.
+.RE
+.PP
+\fIps\fR
+.RS 4
+Power supply\&.
+.RE
+.PP
+\fItemp\fR
+.RS 4
+Temperature sensor\&.
+.RE
+.PP
+\fIcpu\fR
+.RS 4
+Processor (CPU)\&.
+.RE
+.PP
+\fIvolt\fR
+.RS 4
+Voltage probe\&.
+.RE
+.PP
+\fIbp\fR
+.RS 4
+System battery\&.
+.RE
+.PP
+\fIamp\fR
+.RS 4
+Amperage probe (power consumption monitoring)\&.
+.RE
+.PP
+\fIintr\fR
+.RS 4
+Intrusion detection sensor\&.
+.RE
+.PP
+\fIsd\fR
+.RS 4
+SD card
+.RE
+.sp
+.RE
+.SH "CHECK CONTROL"
+.PP
+\fB\-\-no\-storage\fR
+.RS 4
+Turn off storage checking\&. This is an alias for
+\(lq\-\-check storage=0\(rq\&.
+.RE
+.PP
+\fB\-\-only\fR \fIkeyword\fR
+.RS 4
+Makes check_openmanage check and/or report on a single class of components or warning level\&. This option can be specifed once and expects an argument\&. The different arguments and the corresponding behaviour are described below\&.
+.PP
+\fIcritical\fR
+.RS 4
+Print only critical alerts\&. With this option any warning alerts are suppressed\&.
+.RE
+.PP
+\fIwarning\fR
+.RS 4
+Print only warning alerts\&. With this option any critical alerts are suppressed\&.
+.RE
+.PP
+\fIchassis\fR
+.RS 4
+Check all chassis components and nothing else\&.
+.RE
+.PP
+\fIstorage\fR
+.RS 4
+Only check storage
+.RE
+.PP
+\fImemory\fR
+.RS 4
+Only check memory modules
+.RE
+.PP
+\fIfans\fR
+.RS 4
+Only check fans
+.RE
+.PP
+\fIpower\fR
+.RS 4
+Only check power supplies
+.RE
+.PP
+\fItemp\fR
+.RS 4
+Only check temperatures
+.RE
+.PP
+\fIcpu\fR
+.RS 4
+Only check processors
+.RE
+.PP
+\fIvoltage\fR
+.RS 4
+Only check voltage probes
+.RE
+.PP
+\fIbatteries\fR
+.RS 4
+Only check batteries
+.RE
+.PP
+\fIamperage\fR
+.RS 4
+Only check power usage
+.RE
+.PP
+\fIintrusion\fR
+.RS 4
+Only check chassis intrusion
+.RE
+.PP
+\fIsdcard\fR
+.RS 4
+Only check SD cards
+.RE
+.PP
+\fIesmhealth\fR
+.RS 4
+Only check ESM log overall health, i\&.e\&. fill grade
+.RE
+.PP
+\fIservicetag\fR
+.RS 4
+Only check for sane service tag
+.RE
+.PP
+\fIesmlog\fR
+.RS 4
+Only check the event log (ESM) content
+.RE
+.PP
+\fIalertlog\fR
+.RS 4
+Only check the alert log content
+.RE
+.sp
+.RE
+.PP
+\fB\-\-check\fR \fIstring\fR | \fIfile\fR
+.RS 4
+This parameter allows you to adjust which components that should be checked at all\&. This is a rougher approach than blacklisting, which require that you specify component id or index\&. The parameter should be either a string containing the adjustments, or a file containing the string\&. No errors are raised if the file does not exist\&.
+.sp
+Example:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+check_openmanage \-\-check storage=0,intrusion=1
+
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+Legal values are described below, along with the default value\&.
+.PP
+\fIstorage\fR
+.RS 4
+Check storage subsystem (controllers, disks etc\&.)\&. Default: ON
+.RE
+.PP
+\fImemory\fR
+.RS 4
+Check memory (dimms)\&. Default: ON
+.RE
+.PP
+\fIfans\fR
+.RS 4
+Check chassis fans\&. Default: ON
+.RE
+.PP
+\fIpower\fR
+.RS 4
+Check power supplies\&. Default: ON
+.RE
+.PP
+\fItemp\fR
+.RS 4
+Check temperature sensors\&. Default: ON
+.RE
+.PP
+\fIcpu\fR
+.RS 4
+Check CPUs\&. Default: ON
+.RE
+.PP
+\fIvoltage\fR
+.RS 4
+Check voltage sensors\&. Default: ON
+.RE
+.PP
+\fIbatteries\fR
+.RS 4
+Check system batteries\&. Default: ON
+.RE
+.PP
+\fIamperage\fR
+.RS 4
+Check amperage probes\&. Default: ON
+.RE
+.PP
+\fIintrusion\fR
+.RS 4
+Check chassis intrusion\&. Default: ON
+.RE
+.PP
+\fIsdcard\fR
+.RS 4
+Check SD cards\&. Default: ON
+.RE
+.PP
+\fIesmhealth\fR
+.RS 4
+Check the ESM log health, i\&.e\&. fill grade\&. Default: ON
+.RE
+.PP
+\fIservicetag\fR
+.RS 4
+Check that the service tag (serial number) is sane and not empty\&. Default: ON
+.RE
+.PP
+\fIesmlog\fR
+.RS 4
+Check the ESM log content\&. Default: OFF
+.RE
+.PP
+\fIalertlog\fR
+.RS 4
+Check the alert log content\&. Default: OFF
+.RE
+.sp
+.RE
+.SH "DIAGNOSTICS"
+.PP
+The option
+\fB\-d\fR
+or
+\fB\-\-debug\fR
+can be specified to display all monitored components\&.
+.SH "EXIT STATUS"
+.PP
+If no errors are discovered, a value of 0 (OK) is returned\&. An exit value of 1 (WARNING) signifies one or more non\-critical errors, while 2 (CRITICAL) signifies one or more critical errors\&.
+.PP
+The exit value 3 (UNKNOWN) is reserved for errors within the script, or errors getting values from Dell OMSA\&.
+.SH "BUGS AND LIMITATIONS"
+.PP
+Storage info is not collected or checked on very old PowerEdge models and/or old OMSA versions, due to limitations in OMSA\&. The overall support on those models/versions by this plugin is not well tested\&.
+.SH "LICENSE AND COPYRIGHT"
+.PP
+This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version\&.
+.PP
+This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\&. See the GNU General Public License for more details\&.
+.PP
+You should have received a copy of the GNU General Public License along with this program\&. If not, see http://www\&.gnu\&.org/licenses/\&.
+.SH "SEE ALSO"
+.PP
+
+\fBcheck_openmanage.conf\fR(5),
+\fBNet::SNMP\fR(3),
+http://folk\&.uio\&.no/trondham/software/check_openmanage\&.html
+.SH "AUTHORS"
+.PP
+\fBTrond Hasle Amundsen <t\&.h\&.amundsen@usit\&.uio\&.no>\fR
|
|
[-]
[+]
|
Added |
check_openmanage-3.7.6.tar.bz2/man/check_openmanage.8.xml
^
|
| @@ -0,0 +1,1436 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DocBook V4.4//EN"
+"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
+<reference>
+<title>Nagios plugin</title>
+<refentry>
+
+ <refentryinfo>
+ <productname>check_openmanage</productname>
+ <orgname>Trond Hasle Amundsen <t.h.amundsen@usit.uio.no></orgname>
+ </refentryinfo>
+
+ <refmeta>
+ <refentrytitle>check_openmanage</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </refmeta>
+
+ <refnamediv id='name'>
+ <refname>check_openmanage</refname>
+ <refpurpose>
+ Nagios plugin for checking the hardware status on Dell servers
+ running OpenManage
+ </refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv id='synopsis'>
+ <cmdsynopsis>
+ <command>check_openmanage</command>
+ <arg choice='opt'>
+ <replaceable>option</replaceable>...
+ </arg>
+ </cmdsynopsis>
+ <cmdsynopsis>
+ <command>check_openmanage</command>
+ <arg choice='plain'>
+ -H <replaceable>hostname</replaceable>
+ </arg>
+ <arg choice='opt'>
+ <replaceable>option</replaceable>...
+ </arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsect1 id='description'>
+ <title>DESCRIPTION</title>
+ <para>
+ <command>check_openmanage</command> is a plugin for Nagios which
+ checks the hardware health of Dell servers running OpenManage
+ Server Administrator (<acronym>OMSA</acronym>). The plugin
+ checks the health of the storage subsystem, power supplies,
+ memory modules, temperature probes etc., and gives an alert if
+ any of the components are faulty or operate outside normal
+ parameters.
+ </para>
+ <para>
+ <command>check_openmanage</command> is designed to be used by
+ either locally (using NRPE or similar) or remotely (using
+ SNMP). In either mode, the output is (nearly) the same. Note
+ that checking the alert log is not supported in SNMP mode.
+ </para>
+ </refsect1>
+
+ <refsect1 id='general_options'>
+ <title>GENERAL OPTIONS</title>
+ <variablelist remap='IP'>
+ <varlistentry>
+ <term>
+ <option>-f</option>, <option>--config <replaceable>file</replaceable></option>
+ </term>
+ <listitem>
+ <para>
+ Specify a configuration file. For reference on the config
+ file syntax and options, consult the
+ <citerefentry>
+ <refentrytitle>check_openmanage.conf</refentrytitle>
+ <manvolnum>5</manvolnum>
+ </citerefentry>
+ manual page.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-t</option>, <option>--timeout <replaceable>seconds</replaceable></option>
+ </term>
+ <listitem>
+ <para>
+ The number of seconds after which the plugin will
+ abort. Default timeout is 30 seconds if the option is not
+ present.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-p</option>, <option>--perfdata</option>
+ [<replaceable>argument</replaceable>]
+ </term>
+ <listitem>
+ <para>
+ Collect performance data. Performance data collected
+ include temperatures (in Celsius) and fan speeds (in
+ rpm). On systems that support it, power consumption is
+ also collected (in Watts). This option takes one of two
+ arguments, both of which are optional:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><emphasis>minimal</emphasis></term>
+ <listitem>
+ <para>
+ If <emphasis>minimal</emphasis> is specified as
+ argument, the plugin will use shorter names for the
+ performance data labels, e.g. <quote>t0</quote>
+ instead of
+ <quote>temp_0_system_board_ambient</quote>. This can
+ be used as a workaround in cases where the plugin
+ output needs shortening, for example if the 1024
+ character limit of NRPE is reached.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>multiline</emphasis></term>
+ <listitem>
+ <para>
+ If <emphasis>multiline</emphasis> is specified as
+ argument, the plugin will output the performance
+ data on multiple lines, for Nagios 3.x and above.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ The default behaviour should be sufficient for most users.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--legacy-perfdata</option>
+ </term>
+ <listitem>
+ <para>
+ With version 3.7.0, performance data output changed. The
+ new format is not compatible with the old format. Users
+ who wish to postpone switching to the new performance data
+ API may set this option.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-w</option>, <option>--warning</option>
+ <replaceable>string</replaceable> | <replaceable>file</replaceable>
+ </term>
+ <listitem>
+ <para>
+ Override the machine-default temperature warning thresholds. Syntax is:
+ <programlisting>
+<replaceable>id1</replaceable>=<replaceable>max</replaceable>[/<replaceable>min</replaceable>],<replaceable>id2</replaceable>=<replaceable>max</replaceable>[/<replaceable>min</replaceable>],...
+ </programlisting>
+ The following example sets warning limits to max 50C for
+ probe 0, and max 45C and min 10C for probe 1:
+ <programlisting>
+check_openmanage -w 0=50,1=45/10
+ </programlisting>
+ The minimum limit can be omitted, if desired. Most often, you are only
+ interested in setting the maximum thresholds.
+ </para>
+ <para>
+ This parameter can be either a string with the limits, or a file
+ containing the limits string. The option can be specified multiple
+ times.
+ </para>
+ <para>
+ <emphasis>NOTE</emphasis>: This option should only be used
+ to narrow the field of OK temperatures wrt. the OMSA
+ defaults. To expand the field of OK temperatures, increase
+ the OMSA thresholds. See the plugin web page for more
+ information.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-c</option>, <option>--critical</option>
+ <replaceable>string</replaceable> | <replaceable>file</replaceable>
+ </term>
+ <listitem>
+ <para>
+ Override the machine-default temperature critical
+ thresholds. Syntax and behaviour is the same as for
+ warning thresholds described above.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-F</option>, <option>--fahrenheit</option>
+ </term>
+ <listitem>
+ <para>
+ Set Fahrenheit as unit for all temperatures. This option will override
+ the <option>--tempunit</option> option, if used simultaneously.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--tempunit</option> <replaceable>unit</replaceable>
+ </term>
+ <listitem>
+ <para>
+ Set temperature unit. Legal values are:
+ </para>
+ <para><emphasis>F</emphasis>: Fahrenheit</para>
+ <para><emphasis>C</emphasis>: Celsius</para>
+ <para><emphasis>K</emphasis>: Kelvin</para>
+ <para><emphasis>R</emphasis>: Rankine</para>
+ <para>
+ Default: C
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--omreport</option> <replaceable>path</replaceable>
+ </term>
+ <listitem>
+ <para>
+ Specify full path to omreport, if it is not installed in
+ any of the regular places. Usually this option is only
+ needed on Windows, if omreport is not installed on the C:
+ drive.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-d</option>, <option>--debug</option>
+ </term>
+ <listitem>
+ <para>
+ Debug output. Will report status on everything, even if
+ status is ok. Blacklisted or unchecked components are
+ ignored (i.e. no output).
+ </para>
+ <para>
+ <emphasis>NOTE</emphasis>: This option is intended for
+ diagnostics and debugging purposes only. Do not use this
+ option from within Nagios, i.e. in the Nagios config.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-h</option>, <option>--help</option>
+ </term>
+ <listitem>
+ <para>
+ Display help message and exit.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-V</option>, <option>--version</option>
+ </term>
+ <listitem>
+ <para>
+ Print version info and exit.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsect1>
+
+ <refsect1 id='output_options'>
+ <title>OUTPUT OPTIONS</title>
+ <variablelist remap='IP'>
+ <varlistentry>
+ <term>
+ <option>-o</option>, <option>--ok-info</option>
+ <replaceable>level</replaceable>
+ </term>
+ <listitem>
+ <para>
+ This option lets you define how much output you want the
+ plugin to give when everything is OK, i.e. the verbosity
+ level. The default value is 0 (one line of output). The
+ output levels are cumulative.
+ </para>
+ <para>
+ <emphasis>0</emphasis>: Only one line
+ </para>
+ <para>
+ <emphasis>1</emphasis>: BIOS and firmware info on a
+ separate line
+ </para>
+ <para>
+ <emphasis>2</emphasis>: Storage controller and enclosure
+ info on separate lines
+ </para>
+ <para>
+ <emphasis>3</emphasis>: OMSA version on separate line
+ </para>
+ <para>
+ Default: 0
+ </para>
+ <para>
+ The reason that OMSA version is separated from the rest is that
+ finding it requires running a really slow omreport command, when the
+ plugin is run locally via NRPE.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-B</option>, <option>--show-blacklist</option>
+ </term>
+ <listitem>
+ <para>
+ If used together with blacklisting, this option will make
+ the plugin output all blacklistings that are being
+ used. The output will have the correct blacklisting
+ syntax, and will make it easy to maintain control over
+ which blacklistings that are used for each server, as any
+ blacklistings can be viewed from Nagios.
+ </para>
+ <para>
+ When blacklisting is not used, this option has no effect.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-i</option>, <option>--info</option>
+ </term>
+ <listitem>
+ <para>
+ Prefix any alerts with the service tag.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-e</option>, <option>--extinfo</option>
+ </term>
+ <listitem>
+ <para>
+ Display a short summary of system information (model and
+ service tag) in case of an alert.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-I</option>, <option>--htmlinfo</option>
+ [<replaceable>code</replaceable>]
+ </term>
+ <listitem>
+ <para>
+ Using this option will make the servicetag and model name
+ into clickable HTML links in the output. The model name
+ link will point to the official Dell documentation for
+ that model, while the servicetag link will point to a
+ website containing support info for that particular
+ server.
+ </para>
+ <para>
+ This option takes an optional argument, which should be a
+ country or area code or. If the country code is omitted
+ the servicetag link will still work, but it will not be
+ speficic for your country or area. Example for Germany:
+ <programlisting>
+check_openmanage --htmlinfo de
+ </programlisting>
+ If this option is used together with either the
+ <option>--extinfo</option> or <option>--info</option>
+ options, it is particularly useful. Only the most common
+ country codes is supported at this time:
+ </para>
+ <informaltable frame='none' pgwide='1'>
+ <tgroup cols='3'>
+ <colspec colname='c1'/>
+ <colspec colname='c2'/>
+ <colspec colname='c3'/>
+ <tbody>
+ <row>
+ <entry namest='c1' nameend='c3'>Europe, Middle East and Africa (EMEA)</entry>
+ </row>
+ <row>
+ <entry><emphasis>at</emphasis>: Austria</entry>
+ <entry><emphasis>be</emphasis>: Belgium</entry>
+ <entry><emphasis>cz</emphasis>: Czech Republic</entry>
+ </row>
+ <row>
+ <entry><emphasis>de</emphasis>: Germany</entry>
+ <entry><emphasis>dk</emphasis>: Denmark</entry>
+ <entry><emphasis>es</emphasis>: Spain</entry>
+ </row>
+ <row>
+ <entry><emphasis>fi</emphasis>: Finland</entry>
+ <entry><emphasis>fr</emphasis>: France</entry>
+ <entry><emphasis>gr</emphasis>: Greece</entry>
+ </row>
+ <row>
+ <entry><emphasis>it</emphasis>: Italy</entry>
+ <entry><emphasis>il</emphasis>: Israel</entry>
+ <entry><emphasis>me</emphasis>: Middle East</entry>
+ </row>
+ <row>
+ <entry><emphasis>no</emphasis>: Norway</entry>
+ <entry><emphasis>nl</emphasis>: The Netherlands</entry>
+ <entry><emphasis>pl</emphasis>: Poland</entry>
+ </row>
+ <row>
+ <entry><emphasis>pt</emphasis>: Portugal</entry>
+ <entry><emphasis>ru</emphasis>: Russia</entry>
+ <entry><emphasis>se</emphasis>: Sweden</entry>
+ </row>
+ <row>
+ <entry><emphasis>uk</emphasis>: United Kingdom</entry>
+ <entry><emphasis>za</emphasis>: South Africa</entry>
+ <entry><emphasis></emphasis></entry>
+ </row>
+ <row>
+ <entry namest='c1' nameend='c3'></entry>
+ </row>
+ <row>
+ <entry namest='c1' nameend='c3'>America</entry>
+ </row>
+ <row>
+ <entry><emphasis>br</emphasis>: Brazil</entry>
+ <entry><emphasis>ca</emphasis>: Canada</entry>
+ <entry><emphasis>mx</emphasis>: Mexico</entry>
+ </row>
+ <row>
+ <entry><emphasis>us</emphasis>: USA</entry>
+ <entry><emphasis></emphasis></entry>
+ <entry><emphasis></emphasis></entry>
+ </row>
+ <row>
+ <entry namest='c1' nameend='c3'></entry>
+ </row>
+ <row>
+ <entry namest='c1' nameend='c3'>Asia / Pacific</entry>
+ </row>
+ <row>
+ <entry><emphasis>au</emphasis>: Australia</entry>
+ <entry><emphasis>cn</emphasis>: China</entry>
+ <entry><emphasis>in</emphasis>: India</entry>
+ </row>
+ <row>
+ <entry><emphasis>jp</emphasis>: Japan</entry>
+ <entry><emphasis></emphasis></entry>
+ <entry><emphasis></emphasis></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--postmsg</option>
+ <replaceable>string</replaceable> | <replaceable>file</replaceable>
+ </term>
+ <listitem>
+ <para>
+ User specified post message. Useful for displaying arbitrary or
+ various system information at the end of alerts. The argument is
+ either a string with the message, or a file containing that
+ string. You can control the format with the following interpreted
+ sequences:
+ </para>
+ <para>
+ <emphasis>%m</emphasis>: System model
+ </para>
+ <para>
+ <emphasis>%s</emphasis>: Service tag
+ </para>
+ <para>
+ <emphasis>%b</emphasis>: BIOS version
+ </para>
+ <para>
+ <emphasis>%d</emphasis>: BIOS release date
+ </para>
+ <para>
+ <emphasis>%o</emphasis>: Operating system name
+ </para>
+ <para>
+ <emphasis>%r</emphasis>: Operating system release
+ </para>
+ <para>
+ <emphasis>%p</emphasis>: Number of physical drives
+ </para>
+ <para>
+ <emphasis>%l</emphasis>: Number of logical drives
+ </para>
+ <para>
+ <emphasis>%n</emphasis>: Line break. Will be a regular
+ line break if run from a TTY, else an HTML line break.
+ </para>
+ <para>
+ <emphasis>%%</emphasis>: A literal <quote>%</quote>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-s</option>, <option>--state</option>
+ </term>
+ <listitem>
+ <para>
+ Prefix each alert with its corresponding service state
+ (i.e. warning, critical etc.). This is useful in case of
+ several alerts from the same monitored system.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-S</option>, <option>--short-state</option>
+ </term>
+ <listitem>
+ <para>
+ Same as the <option>--state</option> option above, except
+ that the state is abbreviated to a single letter
+ (<emphasis>W</emphasis>=warning,
+ <emphasis>C</emphasis>=critical etc.).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--hide-servicetag</option>
+ </term>
+ <listitem>
+ <para>
+ This option will replace the servicetag (serial number) in
+ the output with <quote>XXXXXXX</quote>. Use this option to
+ suppress or censor the servicetag in the plugin output.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--linebreak</option> <replaceable>string</replaceable>
+ </term>
+ <listitem>
+ <para>
+ check_openmanage will sometimes report more than one line, e.g. if
+ there are several alerts. If the script has a TTY, it will use regular
+ linebreaks. If not (which is the case with NRPE) it will use HTML
+ linebreaks. Sometimes it can be useful to control what the plugin uses
+ as a line separator, and this option provides that control.
+ </para>
+ <para>
+ The argument is the exact string to be used as the line
+ separator. There are two exceptions, i.e. two keywords
+ that translates to the following:
+ </para>
+ <para>
+ <emphasis>REG</emphasis>: Regular linebreaks,
+ i.e. <quote>\n</quote>.
+ </para>
+ <para>
+ <emphasis>HTML</emphasis>: HTML linebreaks,
+ i.e. <quote><br/></quote>.
+ </para>
+ <para>
+ This is a rather special option that is normally not
+ needed. The default behaviour should be sufficient for
+ most users.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsect1>
+
+ <refsect1 id='snmp_options'>
+ <title>SNMP OPTIONS</title>
+ <variablelist remap='IP'>
+ <varlistentry>
+ <term>
+ <option>-H</option>, <option>--hostname <replaceable>hostname</replaceable></option>
+ </term>
+ <listitem>
+ <para>
+ The transport address of the destination SNMP
+ device. Using this option triggers SNMP mode.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-P</option>, <option>--protocol</option>
+ <replaceable>protocol-number</replaceable>
+ </term>
+ <listitem>
+ <para>
+ SNMP protocol version. This option is optional and expects either of
+ the following:
+ </para>
+ <para><emphasis>1</emphasis>: SNMP version 1</para>
+ <para><emphasis>2</emphasis>, <emphasis>2c</emphasis>: SNMP version 2c</para>
+ <para><emphasis>3</emphasis>: SNMP version 3</para>
+ <para>
+ Default: 2c
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--port</option> <replaceable>port-number</replaceable>
+ </term>
+ <listitem>
+ <para>
+ SNMP port of the remote (monitored) system. Defaults to
+ the well-known SNMP port 161.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-6</option>, <option>--ipv6</option>
+ </term>
+ <listitem>
+ <para>
+ This option will cause the plugin to use IPv6. The default
+ is IPv4 if the option is not present.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--tcp</option>
+ </term>
+ <listitem>
+ <para>
+ This option will cause the plugin to use TCP as transport
+ protocol. The default is UDP if the option is not present.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-U</option>, <option>--username</option>
+ <replaceable>securityname</replaceable>
+ </term>
+ <listitem>
+ <para>
+ [SNMPv3] The User-based Security Model (USM) used by
+ SNMPv3 requires that a securityName be specified. This
+ option is required when using SNMP version 3, and expects
+ a string 1 to 32 octets in lenght.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--authpassword</option> <replaceable>password</replaceable>,
+ <option>--authkey</option> <replaceable>key</replaceable>
+ </term>
+ <listitem>
+ <para>
+ [SNMPv3] By default a securityLevel of
+ <emphasis>noAuthNoPriv</emphasis> is assumed. If the
+ <option>--authpassword</option> option is specified, the
+ securityLevel becomes <emphasis>authNoPriv</emphasis>. The
+ <option>--authpassword</option> option expects a string
+ which is at least 1 octet in length as argument.
+ </para>
+ <para>
+ Optionally, instead of the <option>--authpassword</option>
+ option, the <option>--authkey</option> option can be used
+ so that a plain text password does not have to be
+ specified in a script. The <option>--authkey</option>
+ option expects a hexadecimal string produced by localizing
+ the password with the authoritativeEngineID for the
+ specific destination device. The
+ <command>snmpkey</command> utility included with the
+ Net::SNMP distribution can be used to create the
+ hexadecimal string. See
+ <citerefentry>
+ <refentrytitle>snmpkey</refentrytitle>
+ <manvolnum>1</manvolnum>
+ </citerefentry>
+ for more information.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--authprotocol</option> <replaceable>algorithm</replaceable>
+ </term>
+ <listitem>
+ <para>
+ [SNMPv3] Two different hash algorithms
+ are defined by SNMPv3 which can be used by the Security
+ Model for authentication. These algorithms are HMAC-MD5-96
+ <quote>MD5</quote> (RFC 1321) and HMAC-SHA-96
+ <quote>SHA-1</quote> (NIST FIPS PUB 180-1). The default
+ algorithm used by the plugin is HMAC-MD5-96. This
+ behavior can be changed by using this option. The option
+ expects either the string <replaceable>md5</replaceable>
+ or <replaceable>sha</replaceable> to be passed as argument
+ to modify the hash algorithm.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--privpassword</option> <replaceable>password</replaceable>,
+ <option>--privkey</option> <replaceable>key</replaceable>
+ </term>
+ <listitem>
+ <para>
+ [SNMPv3] By specifying the options
+ <option>--privkey</option> or
+ <option>--privpassword</option>, the securityLevel
+ associated with the object becomes
+ <emphasis>authPriv</emphasis>. According to SNMPv3,
+ privacy requires the use of authentication. Therefore, if
+ either of these two options are present and the
+ <option>--authkey</option> or
+ <option>--authpassword</option> arguments are missing, the
+ creation of the object fails. The
+ <option>--privkey</option> and
+ <option>--privpassword</option> options expect the same
+ input as the <option>--authkey</option> and
+ <option>--authpassword</option> options respectively.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--privprotocol</option> <replaceable>algorithm</replaceable>
+ </term>
+ <listitem>
+ <para>
+ [SNMPv3] The User-based Security Model described in RFC
+ 3414 defines a single encryption protocol to be used for
+ privacy. This protocol, CBC-DES <quote>DES</quote> (NIST
+ FIPS PUB 46-1), is used by default or if the string
+ <replaceable>des</replaceable> is passed to the
+ <option>--privprotocol</option> option. The Net::SNMP
+ module also supports RFC 3826 which describes the use of
+ CFB128-AES-128 <quote>AES</quote> (NIST FIPS PUB 197) in
+ the USM. The AES encryption protocol can be selected by
+ passing <replaceable>aes</replaceable> or
+ <replaceable>aes128</replaceable> to the
+ <option>--privprotocol</option> option.
+ </para>
+ <para>
+ One of the following arguments are required: des, aes,
+ aes128, 3des, 3desde
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--use-get_table</option>
+ </term>
+ <listitem>
+ <para>
+ This option exists as a workaround when using
+ check_openmanage with SNMPv3 on Windows with
+ net-snmp. Using this option will make check_openmanage use
+ the Net::SNMP function get_table() instead of
+ get_entries() while fetching values via SNMP. The latter
+ is faster and is the default.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsect1>
+
+ <refsect1 id='blacklisting'>
+ <title>BLACKLISTING</title>
+ <variablelist remap='IP'>
+ <varlistentry>
+ <term>
+ <option>-b</option>, <option>--blacklist</option>
+ <replaceable>string</replaceable> | <replaceable>file</replaceable>
+ </term>
+ <listitem>
+ <para>
+ Blacklist missing and/or failed components, if you do not
+ plan to fix them. The parameter is either the blacklist
+ string, or a file (that may or may not exist) containing
+ the string. The blacklist string contains component names
+ with component IDs separated by slash
+ <quote>/</quote>. Blacklisted components are left
+ unchecked.
+ </para>
+ <para>
+ <emphasis>TIP</emphasis>: Use the option
+ <option>-d</option> or <option>--debug</option> to get the
+ blacklist ID for devices. The ID is listed in a separate
+ column in the debug output.
+ </para>
+ <para>
+ <emphasis>NOTE</emphasis>: If blacklisting is in effect,
+ the global health of the system is not checked.
+ </para>
+ <para>
+ Syntax:
+ <programlisting>
+<replaceable>component1</replaceable>=<replaceable>id1</replaceable>[,<replaceable>id2</replaceable>,...]/<replaceable>component2</replaceable>=<replaceable>id1</replaceable>[,<replaceable>id2</replaceable>,...]/...
+ </programlisting>
+ The ID part can also be <quote>all</quote>, in which all
+ components of that type is blacklisted.
+ </para>
+ <para>
+ Example:
+ <programlisting>
+check_openmanage -b ps=0/fan=3,5/pdisk=1:0:0:1/ctrl_driver=all
+ </programlisting>
+ In the example we blacklist powersupply 0, fans 3 and 5, physical disk
+ 1:0:0:1, and warnings about out-of-date drivers for all
+ controllers. Legal component names include:
+ <variablelist>
+ <varlistentry>
+ <term><emphasis>ctrl</emphasis></term>
+ <listitem>
+ <para>
+ Storage controller. Note that if a controller is
+ blacklisted, all components on that controller
+ (such as physical and logical drives) are
+ blacklisted as well.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>ctrl_fw</emphasis></term>
+ <listitem>
+ <para>
+ Suppress the special warning message about old
+ controller firmware. Use this if you can not or
+ will not upgrade the firmware.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>ctrl_driver</emphasis></term>
+ <listitem>
+ <para>
+ Suppress the special warning message about old
+ controller driver. Particularly useful on systems
+ where you can not upgrade the driver.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>ctrl_stdr</emphasis></term>
+ <listitem>
+ <para>
+ Suppress the special warning message about old
+ Storport driver on Windows.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>ctrl_pdisk</emphasis></term>
+ <listitem>
+ <para>
+ This blacklisting keyword exists as a possible
+ workaround for physical drives with bad firmware
+ which makes Openmanage choke. It takes the
+ controller number as argument. Use this option to
+ blacklist all physical drives on a specific
+ controller. This blacklisting keyword is only
+ available in local mode, i.e. not with SNMP.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>pdisk</emphasis></term>
+ <listitem>
+ <para>Physical disk.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>pdisk_cert</emphasis></term>
+ <listitem>
+ <para>
+ Suppress warning message about non-certified
+ physical disk.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>pdisk_foreign</emphasis></term>
+ <listitem>
+ <para>
+ Suppress warning message about foreign physical
+ disk.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>vdisk</emphasis></term>
+ <listitem>
+ <para>Logical drive (virtual disk).</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>bat</emphasis></term>
+ <listitem>
+ <para>Controller cache battery.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>bat_charge</emphasis></term>
+ <listitem>
+ <para>
+ Ignore warnings related to the controller cache
+ battery charging cycle, which happens
+ approximately every 40-90 days on Dell
+ servers. Note that using this blacklist keyword
+ makes check_openmanage ignore non-critical cache
+ battery errors.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>conn</emphasis></term>
+ <listitem>
+ <para>Connector (channel).</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>encl</emphasis></term>
+ <listitem>
+ <para>Storage enclosure.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>encl_fan</emphasis></term>
+ <listitem>
+ <para>Enclosure fan.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>encl_ps</emphasis></term>
+ <listitem>
+ <para>Enclosure power supply.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>encl_temp</emphasis></term>
+ <listitem>
+ <para>Enclosure temperature probe.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>encl_emm</emphasis></term>
+ <listitem>
+ <para>Enclosure management module (EMM).</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>dimm</emphasis></term>
+ <listitem>
+ <para>Memory module.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>fan</emphasis></term>
+ <listitem>
+ <para>Chassis fan.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>ps</emphasis></term>
+ <listitem>
+ <para>Power supply.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>temp</emphasis></term>
+ <listitem>
+ <para>Temperature sensor.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>cpu</emphasis></term>
+ <listitem>
+ <para>Processor (CPU).</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>volt</emphasis></term>
+ <listitem>
+ <para>Voltage probe.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>bp</emphasis></term>
+ <listitem>
+ <para>System battery.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>amp</emphasis></term>
+ <listitem>
+ <para>
+ Amperage probe (power consumption monitoring).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>intr</emphasis></term>
+ <listitem>
+ <para>Intrusion detection sensor.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>sd</emphasis></term>
+ <listitem>
+ <para>SD card</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsect1>
+
+ <refsect1 id='check_control'>
+ <title>CHECK CONTROL</title>
+ <variablelist remap='IP'>
+ <varlistentry>
+ <term>
+ <option>--no-storage</option>
+ </term>
+ <listitem>
+ <para>
+ Turn off storage checking. This is an alias for
+ <quote>--check storage=0</quote>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--only</option> <replaceable>keyword</replaceable>
+ </term>
+ <listitem>
+ <para>
+ Makes check_openmanage check and/or report on a single
+ class of components or warning level. This option can be
+ specifed once and expects an argument. The different
+ arguments and the corresponding behaviour are described
+ below.
+ <variablelist remap='IP'>
+ <varlistentry>
+ <term><emphasis>critical</emphasis></term>
+ <listitem>
+ <para>
+ Print only critical alerts. With this option any
+ warning alerts are suppressed.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>warning</emphasis></term>
+ <listitem>
+ <para>
+ Print only warning alerts. With this option any
+ critical alerts are suppressed.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>chassis</emphasis></term>
+ <listitem>
+ <para>
+ Check all chassis components and nothing else.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>storage</emphasis></term>
+ <listitem>
+ <para>
+ Only check storage
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>memory</emphasis></term>
+ <listitem>
+ <para>
+ Only check memory modules
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>fans</emphasis></term>
+ <listitem>
+ <para>
+ Only check fans
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>power</emphasis></term>
+ <listitem>
+ <para>
+ Only check power supplies
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>temp</emphasis></term>
+ <listitem>
+ <para>
+ Only check temperatures
+ </para>
+ </listitem></varlistentry><varlistentry>
+ <term><emphasis>cpu</emphasis></term>
+ <listitem>
+ <para>
+ Only check processors
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>voltage</emphasis></term>
+ <listitem>
+ <para>
+ Only check voltage probes
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>batteries</emphasis></term>
+ <listitem>
+ <para>
+ Only check batteries
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>amperage</emphasis></term>
+ <listitem>
+ <para>
+ Only check power usage
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>intrusion</emphasis></term>
+ <listitem>
+ <para>
+ Only check chassis intrusion
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>sdcard</emphasis></term>
+ <listitem>
+ <para>
+ Only check SD cards
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>esmhealth</emphasis></term>
+ <listitem>
+ <para>
+ Only check ESM log overall health, i.e. fill grade
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>servicetag</emphasis></term>
+ <listitem>
+ <para>
+ Only check for sane service tag
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>esmlog</emphasis></term>
+ <listitem>
+ <para>
+ Only check the event log (ESM) content
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>alertlog</emphasis></term>
+ <listitem>
+ <para>
+ Only check the alert log content
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>--check</option>
+ <replaceable>string</replaceable> | <replaceable>file</replaceable>
+ </term>
+ <listitem>
+ <para>
+ This parameter allows you to adjust which components that
+ should be checked at all. This is a rougher approach than
+ blacklisting, which require that you specify component id
+ or index. The parameter should be either a string
+ containing the adjustments, or a file containing the
+ string. No errors are raised if the file does not exist.
+ </para>
+ <para>
+ Example:
+ <programlisting>
+check_openmanage --check storage=0,intrusion=1
+ </programlisting>
+ Legal values are described below, along with the default value.
+ <variablelist remap='IP'>
+ <varlistentry>
+ <term><emphasis>storage</emphasis></term>
+ <listitem>
+ <para>
+ Check storage subsystem (controllers, disks
+ etc.). Default: ON
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>memory</emphasis></term>
+ <listitem>
+ <para>
+ Check memory (dimms). Default: ON
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>fans</emphasis></term>
+ <listitem>
+ <para>
+ Check chassis fans. Default: ON
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>power</emphasis></term>
+ <listitem>
+ <para>
+ Check power supplies. Default: ON
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>temp</emphasis></term>
+ <listitem>
+ <para>
+ Check temperature sensors. Default: ON
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>cpu</emphasis></term>
+ <listitem>
+ <para>
+ Check CPUs. Default: ON
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>voltage</emphasis></term>
+ <listitem>
+ <para>
+ Check voltage sensors. Default: ON
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>batteries</emphasis></term>
+ <listitem>
+ <para>
+ Check system batteries. Default: ON
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>amperage</emphasis></term>
+ <listitem>
+ <para>
+ Check amperage probes. Default: ON
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>intrusion</emphasis></term>
+ <listitem>
+ <para>
+ Check chassis intrusion. Default: ON
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>sdcard</emphasis></term>
+ <listitem>
+ <para>
+ Check SD cards. Default: ON
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>esmhealth</emphasis></term>
+ <listitem>
+ <para>
+ Check the ESM log health, i.e. fill
+ grade. Default: ON
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>servicetag</emphasis></term>
+ <listitem>
+ <para>
+ Check that the service tag (serial number) is sane
+ and not empty. Default: ON
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>esmlog</emphasis></term>
+ <listitem>
+ <para>
+ Check the ESM log content. Default: OFF
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>alertlog</emphasis></term>
+ <listitem>
+ <para>
+ Check the alert log content. Default: OFF
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsect1>
+
+ <refsect1 id='diagnostics'>
+ <title>DIAGNOSTICS</title>
+ <para>
+ The option <option>-d</option> or <option>--debug</option> can
+ be specified to display all monitored components.
+ </para>
+ </refsect1>
+
+ <refsect1 id='exit_status'>
+ <title>EXIT STATUS</title>
+ <para>
+ If no errors are discovered, a value of 0 (OK) is returned. An
+ exit value of 1 (WARNING) signifies one or more non-critical
+ errors, while 2 (CRITICAL) signifies one or more critical
+ errors.
+ </para>
+ <para>
+ The exit value 3 (UNKNOWN) is reserved for errors within the
+ script, or errors getting values from Dell OMSA.
+ </para>
+ </refsect1>
+
+ <refsect1 id='bugs_and_limitations'>
+ <title>BUGS AND LIMITATIONS</title>
+ <para>
+ Storage info is not collected or checked on very old PowerEdge
+ models and/or old OMSA versions, due to limitations in OMSA. The
+ overall support on those models/versions by this plugin is not
+ well tested.
+ </para>
+ </refsect1>
+
+ <refsect1 id='license_and_copyright'>
+ <title>LICENSE AND COPYRIGHT</title>
+ <para>
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or (at
+ your option) any later version.
+ </para>
+ <para>
+ This program is distributed in the hope that it will be useful, but
+ WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ General Public License for more details.
+ </para>
+ <para>
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see http://www.gnu.org/licenses/.
+ </para>
+ </refsect1>
+
+ <refsect1 id='see_also'>
+ <title>SEE ALSO</title>
+ <para>
+ <citerefentry>
+ <refentrytitle>check_openmanage.conf</refentrytitle><manvolnum>5</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>Net::SNMP</refentrytitle><manvolnum>3</manvolnum>
+ </citerefentry>,
+ <uri>
+ http://folk.uio.no/trondham/software/check_openmanage.html
+ </uri>
+<!--
+ <citerefentry>
+ <refentrytitle>tele</refentrytitle><manvolnum>1</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>ng</refentrytitle><manvolnum>1</manvolnum>
+ </citerefentry>.
+-->
+ </para>
+ </refsect1>
+
+</refentry>
+</reference>
+
|
|
[-]
[+]
|
Added |
check_openmanage-3.7.6.tar.bz2/man/check_openmanage.conf.5
^
|
| @@ -0,0 +1,474 @@
+'\" t
+.\" Title: check_openmanage.conf
+.\" Author: Trond Hasle Amundsen <t.h.amundsen@usit.uio.no>
+.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
+.\" Date: 06/28/2012
+.\" Manual: Nagios plugin
+.\" Source: check_openmanage
+.\" Language: English
+.\"
+.TH "CHECK_OPENMANAGE\&.C" "5" "06/28/2012" "check_openmanage" "Nagios plugin"
+.\" -----------------------------------------------------------------
+.\" * set default formatting
+.\" -----------------------------------------------------------------
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.\" -----------------------------------------------------------------
+.\" * MAIN CONTENT STARTS HERE *
+.\" -----------------------------------------------------------------
+.SH "NAME"
+check_openmanage.conf \- Configuration file for check_openmanage
+.SH "FILE FORMAT"
+.PP
+The file has an ini\-style syntax and consists of sections and parameters\&. A section begins with the name of the section in square brackets and continues until the next section begins\&. An example of section with two keywords and parameters:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+ \fI[section]\fR
+ \fIkey1\fR = \fIboolean\fR
+ \fIkey2\fR = \fIstring\fR
+
+.fi
+.if n \{\
+.RE
+.\}
+.PP
+The data types used are string (no quotes needed) and bool (with values of
+\(lqTRUE/FALSE\(rq)\&. For boolean values,
+\(lq1\(rq,
+\(lqon\(rq
+and
+\(lqtrue\(rq
+are equivalent, likewise for
+\(lq0\(rq,
+\(lqoff\(rq
+and
+\(lqfalse\(rq\&. They are also case insensitive\&.
+.PP
+The root section or global section has no section name in brackets:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+ \fIkey1\fR = \fIvalue1\fR
+ \fIkey2\fR = \fIvalue2\fR
+
+ \fI[section]\fR
+ \fIkey3\fR = \fIvalue3\fR
+ \fIkey4\fR = \fIvalue4\fR
+
+.fi
+.if n \{\
+.RE
+.\}
+.PP
+The values set in a bracket section will override those set in the root section, in case of conflicts\&.
+.PP
+Lines starting with
+\(lq#\(rq
+or
+\(lq;\(rq
+are considered comments and ignored, as are blank lines\&.
+.PP
+The configuration file must be a regular file\&. Owner and group does not matter, but the Nagios user must have read access\&.
+.SH "SECTIONS AND ORDERING"
+.PP
+The section name should correspond to the hostname, i\&.e\&. the value passed to the
+\fB\-H\fR
+or
+\fB\-\-hostname\fR
+command line option\&. The section name itself can be either an exact match to the hostname, or a glob pattern\&.
+.PP
+The sections are read in order of significance\&. The root section is read first\&. Then any sections with glob patterns that match the hostname are read (alphabetically)\&. Any section whose name is an exact match to the hostname is read last\&.
+.PP
+For boolean values, any conflicts are resolved by letting the section with the most significance (closest match to the hostname) override any previous definitions\&. For string values, they are simply added together\&.
+.PP
+Normal shell globbing may be used for the section names\&. This is limited to
+\(lq*\(rq,
+\(lq?\(rq
+and
+\(lq[]\(rq\&. Some examples:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+ [web*\&.example\&.com]
+ # matches e\&.g\&. webmail\&.example\&.com
+
+ [pgsql\-[34]\&.example\&.com]
+ # matches pgsql\-3\&.example\&.com and pgsql\-4\&.example\&.com
+
+ [login?\&.example\&.com]
+ # mathces e\&.g\&. login1\&.example\&.com
+
+.fi
+.if n \{\
+.RE
+.\}
+.PP
+
+\fICAUTION\fR: Be careful not to have more than one glob pattern section match any single host\&. This may lead to unpredictable results\&.
+.SH "CONFIGURATION"
+.PP
+All configuration file options have a corresponding command line option\&. Usually, the command line option will override the configuration file option, if used simultaneously\&.
+.PP
+Each option is described briefly\&. For more information about syntax, legal values etc\&. refer to the corresponding command line option in
+\fBcheck_openmanage\fR(8)\&.
+.SS "Check control configuration options"
+.PP
+Any keyword to the
+\fB\-\-check\fR
+command line option are accepted in the configuration file, as
+\(lqcheck_<\fIkeyword\fR>\(rq\&. These options take boolean values (\(lqtrue\(rq
+or
+\(lqfalse\(rq)\&. The following keywords are accepted for check control, listed here with their default values:
+.PP
+\fIcheck_storage\fR
+.RS 4
+Check storage subsystem (controllers, disks etc\&.)\&. Default: TRUE
+.RE
+.PP
+\fIcheck_memory\fR
+.RS 4
+Check memory (dimms)\&. Default: TRUE
+.RE
+.PP
+\fIcheck_fans\fR
+.RS 4
+Check chassis fans\&. Default: TRUE
+.RE
+.PP
+\fIcheck_power\fR
+.RS 4
+Check power supplies\&. Default: TRUE
+.RE
+.PP
+\fIcheck_temp\fR
+.RS 4
+Check temperature sensors\&. Default: TRUE
+.RE
+.PP
+\fIcheck_cpu\fR
+.RS 4
+Check CPUs\&. Default: TRUE
+.RE
+.PP
+\fIcheck_voltage\fR
+.RS 4
+Check voltage sensors\&. Default: TRUE
+.RE
+.PP
+\fIcheck_batteries\fR
+.RS 4
+Check system batteries\&. Default: TRUE
+.RE
+.PP
+\fIcheck_amperage\fR
+.RS 4
+Check amperage probes\&. Default: TRUE
+.RE
+.PP
+\fIcheck_intrusion\fR
+.RS 4
+Check chassis intrusion\&. Default: TRUE
+.RE
+.PP
+\fIcheck_sdcard\fR
+.RS 4
+Check SD cards\&. Default: TRUE
+.RE
+.PP
+\fIcheck_esmhealth\fR
+.RS 4
+Check the ESM log health, i\&.e\&. fill grade\&. Default: TRUE
+.RE
+.PP
+\fIcheck_servicetag\fR
+.RS 4
+Check that the service tag (serial number) is sane and not empty\&. Default: TRUE
+.RE
+.PP
+\fIcheck_esmlog\fR
+.RS 4
+Check the ESM log content\&. Default: FALSE
+.RE
+.PP
+\fIcheck_alertlog\fR
+.RS 4
+Check the alert log content\&. Default: FALSE
+.RE
+.PP
+\fIcheck_everything\fR
+.RS 4
+Special option that turns on all checks\&. Setting this option to "true" will effectively negate any other check options\&. This option corresponds to the
+\fB\-a\fR
+or
+\fB\-\-all\fR
+command line option\&.
+.RE
+.PP
+If used together with the
+\fB\-\-check\fR
+command line option, the command line option will override the configuration file, if there is a conflict\&.
+.PP
+For more information about check control, see the CHECK CONTROL section in
+\fBcheck_openmanage\fR(8)\&.
+.SS "General configuration options"
+.PP
+\fIblacklist\fR (string)
+.RS 4
+Blacklist components\&. The argument is a string that uses the same syntax as the
+\fB\-b\fR
+or
+\fB\-\-blacklist\fR
+command line option\&.
+.sp
+If used together with the
+\fB\-b\fR
+or
+\fB\-\-blacklist\fR
+command line option, the two blacklists from the config file and command line are merged together\&.
+.sp
+For more information about blacklisting, including syntax, see the BLACKLISTING section in
+\fBcheck_openmanage\fR(8)\&.
+.RE
+.PP
+\fItimeout\fR (integer)
+.RS 4
+The plugin timeout\&. The argument is number of seconds and should be a positive integer\&.
+.sp
+Corresponding command line option:
+\fB\-t\fR,
+\fB\-\-timeout\fR
+.RE
+.PP
+\fIperformance_data\fR (boolean or string)
+.RS 4
+Turn on/off performance data reporting\&. Accepted values are boolean (TRUE/FALSE) or either of the keywords
+\(lqminimal\(rq
+and
+\(lqmultiline\(rq\&.
+.sp
+Corresponding command line option:
+\fB\-p\fR,
+\fB\-\-perfdata\fR
+.RE
+.PP
+\fIlegacy_performance_data\fR (boolean)
+.RS 4
+With version 3\&.7\&.0, performance data output changed\&. The new format is not compatible with the old format\&. Users who wish to postpone switching to the new performance data API may use this option\&. This option takes a boolean value\&.
+.sp
+Corresponding command line option:
+\fB\-\-legacy\-perfdata\fR
+.RE
+.PP
+\fItemperature_unit\fR (char)
+.RS 4
+The temperature unit used for reporting, performance data etc\&. can be set with the this option\&.
+.sp
+Corresponding command line option:
+\fB\-\-tempunit\fR
+.sp
+
+\fINOTE\fR: The command line option
+\fB\-F\fR
+or
+\fB\-\-fahrenheit\fR
+will override both the command line option and the configuration file option\&.
+.RE
+.PP
+\fItemp_threshold_warning\fR (string)
+.RS 4
+Custom temperature warning limits\&.
+.sp
+Corresponding command line option:
+\fB\-w\fR,
+\fB\-\-warning\fR
+.RE
+.PP
+\fItemp_threshold_critical\fR (string)
+.RS 4
+Custom temperature critical limits\&.
+.sp
+Corresponding command line option:
+\fB\-c\fR,
+\fB\-\-critical\fR
+.RE
+.SS "SNMP configuration options"
+.PP
+Several SNMP related options may be set in the configuration file\&. The configuration file may contain the following SNMP options:
+.PP
+\fIsnmp_community\fR (string)
+.RS 4
+The SNMP community string\&.
+.sp
+Corresponding command line option:
+\fB\-C\fR,
+\fB\-\-community\fR
+.RE
+.PP
+\fIsnmp_version\fR (string)
+.RS 4
+The SNMP protocol version\&.
+.sp
+Corresponding command line option:
+\fB\-P\fR,
+\fB\-\-protocol\fR
+.RE
+.PP
+\fIsnmp_port\fR (integer)
+.RS 4
+The remote port number used with SNMP\&.
+.sp
+Corresponding command line option:
+\fB\-\-port\fR
+.RE
+.PP
+\fIsnmp_use_ipv6\fR (boolean)
+.RS 4
+Toggle using IPv6 instead of IPv4\&.
+.sp
+Corresponding command line option:
+\fB\-6\fR,
+\fB\-\-ipv6\fR
+.RE
+.PP
+\fIsnmp_use_tcp\fR (boolean)
+.RS 4
+Toggle using TCP instead of UDP as transport protocol\&.
+.sp
+Corresponding command line option:
+\fB\-\-tcp\fR
+.RE
+.SS "Output configuration options"
+.PP
+These options gives some control over the output given by the plugin\&.
+.PP
+\fIoutput_servicetag\fR (boolean)
+.RS 4
+Toggle inclusion of the service tag (serial number) of the monitored host in alerts\&.
+.sp
+Corresponding command line option:
+\fB\-i\fR,
+\fB\-\-info\fR
+.RE
+.PP
+\fIoutput_servicestate\fR (boolean)
+.RS 4
+Toggle inclusion of the service state in alerts\&.
+.sp
+Corresponding command line option:
+\fB\-s\fR,
+\fB\-\-state\fR
+.RE
+.PP
+\fIoutput_servicestate_abbr\fR (boolean)
+.RS 4
+Toggle inclusion of the abbreviated service state in alerts\&.
+.sp
+Corresponding command line option:
+\fB\-S\fR,
+\fB\-\-short\-state\fR
+.RE
+.PP
+\fIoutput_sysinfo\fR (boolean)
+.RS 4
+Toggle inclusion of a short system information summary in case of alerts\&.
+.sp
+Corresponding command line option:
+\fB\-e\fR,
+\fB\-\-extinfo\fR
+.RE
+.PP
+\fIoutput_blacklist\fR (boolean)
+.RS 4
+Toggle showing any blacklistings in the OK output\&.
+.sp
+Corresponding command line option:
+\fB\-B\fR,
+\fB\-\-show\-blacklist\fR
+.RE
+.PP
+\fIoutput_ok_verbosity\fR (integer)
+.RS 4
+This option specifies how much information is shown in the OK output\&.
+.sp
+Corresponding command line option:
+\fB\-o\fR,
+\fB\-\-ok\-info\fR
+.RE
+.PP
+\fIoutput_html\fR (boolean or code)
+.RS 4
+This option toggles HTML output\&. Argument is either a boolean value, or a country or area code\&. Se
+\fBcheck_openmanage\fR(8)
+for more information and list of supported country and area codes\&.
+.sp
+Corresponding command line option:
+\fB\-I\fR,
+\fB\-\-htmlinfo\fR
+.RE
+.PP
+\fIoutput_post_message\fR (string)
+.RS 4
+Specify one line of information to be shown after alerts\&.
+.sp
+Corresponding command line option:
+\fB\-\-postmsg\fR
+.RE
+.PP
+\fIoutput_hide_servicetag\fR (boolean)
+.RS 4
+This option toggles censoring of the service tag (serial number) in any output from the plugin\&.
+.sp
+Corresponding command line option:
+\fB\-\-hide\-servicetag\fR
+.RE
+.SH "EXAMPLE"
+.PP
+The following example shows a typical check_openmanage config, with a global section and a few host sections\&.
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+# Global definitions
+output_blacklist = true
+output_ok_verbosity = 3
+output_sysinfo = true
+output_html = us
+
+# Local definitions (exact or glob pattern)
+[esx??\&.example\&.com]
+ blacklist = ctrl_fw=all
+ check_storage = false
+
+[mysql01\&.example\&.com]
+ performance_data = true
+
+[web0[123]\&.example\&.com]
+ performance_data = true
+ blacklist = ctrl_driver=all
+
+[*\&.hpc\&.example\&.com]
+ performance_data = true
+
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+.SH "SEE ALSO"
+.PP
+
+\fBcheck_openmanage\fR(8),
+http://folk\&.uio\&.no/trondham/software/check_openmanage\&.html
+.SH "AUTHORS"
+.PP
+\fBTrond Hasle Amundsen <t\&.h\&.amundsen@usit\&.uio\&.no>\fR
|
|
[-]
[+]
|
Added |
check_openmanage-3.7.6.tar.bz2/man/check_openmanage.conf.5.xml
^
|
| @@ -0,0 +1,658 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DocBook V4.4//EN"
+"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
+<reference>
+<title>Nagios plugin</title>
+<refentry>
+
+ <refentryinfo>
+ <productname>check_openmanage</productname>
+ <orgname>Trond Hasle Amundsen <t.h.amundsen@usit.uio.no></orgname>
+ </refentryinfo>
+
+ <refmeta>
+ <refentrytitle>check_openmanage.conf</refentrytitle>
+ <manvolnum>5</manvolnum>
+ </refmeta>
+
+ <refnamediv id='name'>
+ <refname>check_openmanage.conf</refname>
+ <refpurpose>
+ Configuration file for check_openmanage
+ </refpurpose>
+ </refnamediv>
+
+ <refsect1 id='file_format'>
+ <title>FILE FORMAT</title>
+ <para>
+ The file has an ini-style syntax and consists of sections and
+ parameters. A section begins with the name of the section in
+ square brackets and continues until the next section begins. An
+ example of section with two keywords and parameters:
+ <programlisting>
+ <replaceable>[section]</replaceable>
+ <replaceable>key1</replaceable> = <replaceable>boolean</replaceable>
+ <replaceable>key2</replaceable> = <replaceable>string</replaceable>
+ </programlisting>
+ </para>
+ <para>
+ The data types used are string (no quotes needed) and bool (with
+ values of <quote>TRUE/FALSE</quote>). For boolean values,
+ <quote>1</quote>, <quote>on</quote> and <quote>true</quote> are
+ equivalent, likewise for <quote>0</quote>, <quote>off</quote>
+ and <quote>false</quote>. They are also case insensitive.
+ </para>
+ <para>
+ The root section or global section has no section name in
+ brackets:
+ <programlisting>
+ <replaceable>key1</replaceable> = <replaceable>value1</replaceable>
+ <replaceable>key2</replaceable> = <replaceable>value2</replaceable>
+
+ <replaceable>[section]</replaceable>
+ <replaceable>key3</replaceable> = <replaceable>value3</replaceable>
+ <replaceable>key4</replaceable> = <replaceable>value4</replaceable>
+ </programlisting>
+ </para>
+ <para>
+ The values set in a bracket section will override those set in the
+ root section, in case of conflicts.
+ </para>
+ <para>
+ Lines starting with <quote>#</quote> or <quote>;</quote> are
+ considered comments and ignored, as are blank lines.
+ </para>
+ <para>
+ The configuration file must be a regular file. Owner and group
+ does not matter, but the Nagios user must have read access.
+ </para>
+ </refsect1>
+
+ <refsect1 id='sections_and_ordering'>
+ <title>SECTIONS AND ORDERING</title>
+ <para>
+ The section name should correspond to the hostname, i.e. the
+ value passed to the <option>-H</option> or
+ <option>--hostname</option> command line option. The section
+ name itself can be either an exact match to the hostname, or a
+ glob pattern.
+ </para>
+ <para>
+ The sections are read in order of significance. The root section
+ is read first. Then any sections with glob patterns that match
+ the hostname are read (alphabetically). Any section whose name
+ is an exact match to the hostname is read last.
+ </para>
+ <para>
+ For boolean values, any conflicts are resolved by letting the
+ section with the most significance (closest match to the
+ hostname) override any previous definitions. For string values,
+ they are simply added together.
+ </para>
+ <para>
+ Normal shell globbing may be used for the section names. This is
+ limited to <quote>*</quote>, <quote>?</quote> and
+ <quote>[]</quote>. Some examples:
+ <programlisting>
+ [web*.example.com]
+ # matches e.g. webmail.example.com
+
+ [pgsql-[34].example.com]
+ # matches pgsql-3.example.com and pgsql-4.example.com
+
+ [login?.example.com]
+ # mathces e.g. login1.example.com
+ </programlisting>
+ </para>
+ <para>
+ <emphasis>CAUTION</emphasis>: Be careful not to have more than
+ one glob pattern section match any single host. This may lead to
+ unpredictable results.
+ </para>
+ </refsect1>
+
+ <refsect1 id='configuration'>
+ <title>CONFIGURATION</title>
+ <para>
+ All configuration file options have a corresponding command line
+ option. Usually, the command line option will override the
+ configuration file option, if used simultaneously.
+ </para>
+ <para>
+ Each option is described briefly. For more information about
+ syntax, legal values etc. refer to the corresponding command
+ line option in
+ <citerefentry>
+ <refentrytitle>check_openmanage</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>.
+ </para>
+
+ <refsect2 id='check_control'>
+ <title>Check control configuration options</title>
+ <para>
+ Any keyword to the <option>--check</option> command line
+ option are accepted in the configuration file, as
+ <quote>check_<<replaceable>keyword</replaceable>></quote>. These
+ options take boolean values (<quote>true</quote> or
+ <quote>false</quote>). The following keywords are accepted for
+ check control, listed here with their default values:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><emphasis>check_storage</emphasis></term>
+ <listitem>
+ <para>
+ Check storage subsystem (controllers, disks
+ etc.). Default: TRUE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_memory</emphasis></term>
+ <listitem>
+ <para>
+ Check memory (dimms). Default: TRUE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_fans</emphasis></term>
+ <listitem>
+ <para>
+ Check chassis fans. Default: TRUE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_power</emphasis></term>
+ <listitem>
+ <para>
+ Check power supplies. Default: TRUE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_temp</emphasis></term>
+ <listitem>
+ <para>
+ Check temperature sensors. Default: TRUE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_cpu</emphasis></term>
+ <listitem>
+ <para>
+ Check CPUs. Default: TRUE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_voltage</emphasis></term>
+ <listitem>
+ <para>
+ Check voltage sensors. Default: TRUE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_batteries</emphasis></term>
+ <listitem>
+ <para>
+ Check system batteries. Default: TRUE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_amperage</emphasis></term>
+ <listitem>
+ <para>
+ Check amperage probes. Default: TRUE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_intrusion</emphasis></term>
+ <listitem>
+ <para>
+ Check chassis intrusion. Default: TRUE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_sdcard</emphasis></term>
+ <listitem>
+ <para>
+ Check SD cards. Default: TRUE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_esmhealth</emphasis></term>
+ <listitem>
+ <para>
+ Check the ESM log health, i.e. fill grade. Default: TRUE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_servicetag</emphasis></term>
+ <listitem>
+ <para>
+ Check that the service tag (serial number) is sane and
+ not empty. Default: TRUE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_esmlog</emphasis></term>
+ <listitem>
+ <para>
+ Check the ESM log content. Default: FALSE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_alertlog</emphasis></term>
+ <listitem>
+ <para>
+ Check the alert log content. Default: FALSE
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>check_everything</emphasis></term>
+ <listitem>
+ <para>
+ Special option that turns on all checks. Setting this
+ option to "true" will effectively negate any other check
+ options. This option corresponds to the
+ <option>-a</option> or <option>--all</option> command
+ line option.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ If used together with the <option>--check</option>
+ command line option, the command line option will
+ override the configuration file, if there is a conflict.
+ </para>
+ <para>
+ For more information about check control, see the CHECK
+ CONTROL section in
+ <citerefentry>
+ <refentrytitle>check_openmanage</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>.
+ </para>
+ </refsect2>
+
+ <refsect2 id='general'>
+ <title>General configuration options</title>
+ <variablelist>
+ <varlistentry>
+ <term><emphasis>blacklist</emphasis> (string)</term>
+ <listitem>
+ <para>
+ Blacklist components. The argument is a string that uses
+ the same syntax as the <option>-b</option> or
+ <option>--blacklist</option> command line
+ option.
+ </para>
+ <para>
+ If used together with the <option>-b</option> or
+ <option>--blacklist</option> command line option, the
+ two blacklists from the config file and command line are
+ merged together.
+ </para>
+ <para>
+ For more information about blacklisting, including syntax,
+ see the BLACKLISTING section in
+ <citerefentry>
+ <refentrytitle>check_openmanage</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>timeout</emphasis> (integer)</term>
+ <listitem>
+ <para>
+ The plugin timeout. The argument is number of seconds
+ and should be a positive integer.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>-t</option>, <option>--timeout</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>performance_data</emphasis> (boolean or string)</term>
+ <listitem>
+ <para>
+ Turn on/off performance data reporting. Accepted values
+ are boolean (TRUE/FALSE) or either of the keywords
+ <quote>minimal</quote> and
+ <quote>multiline</quote>.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>-p</option>, <option>--perfdata</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>legacy_performance_data</emphasis> (boolean)</term>
+ <listitem>
+ <para>
+ With version 3.7.0, performance data output changed. The
+ new format is not compatible with the old format. Users
+ who wish to postpone switching to the new performance
+ data API may use this option. This option takes a
+ boolean value.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>--legacy-perfdata</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>temperature_unit</emphasis> (char)</term>
+ <listitem>
+ <para>
+ The temperature unit used for reporting, performance data etc. can be
+ set with the this option.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>--tempunit</option>
+ </para>
+ <para>
+ <emphasis>NOTE</emphasis>: The command line option
+ <option>-F</option> or <option>--fahrenheit</option>
+ will override both the command line option and the
+ configuration file option.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>temp_threshold_warning</emphasis> (string)</term>
+ <listitem>
+ <para>
+ Custom temperature warning limits.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>-w</option>, <option>--warning</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>temp_threshold_critical</emphasis> (string)</term>
+ <listitem>
+ <para>
+ Custom temperature critical limits.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>-c</option>, <option>--critical</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsect2>
+
+ <refsect2 id='snmp_configuration_options'>
+ <title>SNMP configuration options</title>
+ <para>
+ Several SNMP related options may be set in the configuration
+ file. The configuration file may contain the following SNMP
+ options:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><emphasis>snmp_community</emphasis> (string)</term>
+ <listitem>
+ <para>
+ The SNMP community string.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>-C</option>, <option>--community</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>snmp_version</emphasis> (string)</term>
+ <listitem>
+ <para>
+ The SNMP protocol version.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>-P</option>, <option>--protocol</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>snmp_port</emphasis> (integer)</term>
+ <listitem>
+ <para>
+ The remote port number used with SNMP.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>--port</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>snmp_use_ipv6</emphasis> (boolean)</term>
+ <listitem>
+ <para>
+ Toggle using IPv6 instead of IPv4.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>-6</option>, <option>--ipv6</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>snmp_use_tcp</emphasis> (boolean)</term>
+ <listitem>
+ <para>
+ Toggle using TCP instead of UDP as transport
+ protocol.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>--tcp</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsect2>
+
+ <refsect2 id='output_configuration_options'>
+ <title>Output configuration options</title>
+ <para>
+ These options gives some control over the output given by the
+ plugin.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><emphasis>output_servicetag</emphasis> (boolean)</term>
+ <listitem>
+ <para>
+ Toggle inclusion of the service tag (serial number) of
+ the monitored host in alerts.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>-i</option>, <option>--info</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>output_servicestate</emphasis> (boolean)</term>
+ <listitem>
+ <para>
+ Toggle inclusion of the service state in alerts.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>-s</option>, <option>--state</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>output_servicestate_abbr</emphasis> (boolean)</term>
+ <listitem>
+ <para>
+ Toggle inclusion of the abbreviated service state in
+ alerts.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>-S</option>, <option>--short-state</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>output_sysinfo</emphasis> (boolean)</term>
+ <listitem>
+ <para>
+ Toggle inclusion of a short system information summary
+ in case of alerts.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>-e</option>, <option>--extinfo</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>output_blacklist</emphasis> (boolean)</term>
+ <listitem>
+ <para>
+ Toggle showing any blacklistings in the OK output.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>-B</option>, <option>--show-blacklist</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>output_ok_verbosity</emphasis> (integer)</term>
+ <listitem>
+ <para>
+ This option specifies how much information is shown in
+ the OK output.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>-o</option>, <option>--ok-info</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>output_html</emphasis> (boolean or code)</term>
+ <listitem>
+ <para>
+ This option toggles HTML output. Argument is either a
+ boolean value, or a country or area code. Se
+ <citerefentry>
+ <refentrytitle>check_openmanage</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>
+ for more information and list of supported country and
+ area codes.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>-I</option>, <option>--htmlinfo</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>output_post_message</emphasis> (string)</term>
+ <listitem>
+ <para>
+ Specify one line of information to be shown after
+ alerts.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>--postmsg</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis>output_hide_servicetag</emphasis> (boolean)</term>
+ <listitem>
+ <para>
+ This option toggles censoring of the service tag (serial
+ number) in any output from the plugin.
+ </para>
+ <para>
+ Corresponding command line option:
+ <option>--hide-servicetag</option>
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsect2>
+ </refsect1>
+
+ <refsect1 id='example'>
+ <title>EXAMPLE</title>
+ <para>
+ The following example shows a typical check_openmanage config,
+ with a global section and a few host sections.
+ <programlisting>
+# Global definitions
+output_blacklist = true
+output_ok_verbosity = 3
+output_sysinfo = true
+output_html = us
+
+# Local definitions (exact or glob pattern)
+[esx??.example.com]
+ blacklist = ctrl_fw=all
+ check_storage = false
+
+[mysql01.example.com]
+ performance_data = true
+
+[web0[123].example.com]
+ performance_data = true
+ blacklist = ctrl_driver=all
+
+[*.hpc.example.com]
+ performance_data = true
+ </programlisting>
+ </para>
+ </refsect1>
+
+ <refsect1 id='see_also'>
+ <title>SEE ALSO</title>
+ <para>
+ <citerefentry>
+ <refentrytitle>check_openmanage</refentrytitle><manvolnum>8</manvolnum>
+ </citerefentry>,
+ <uri>
+ http://folk.uio.no/trondham/software/check_openmanage.html
+ </uri>
+ </para>
+ </refsect1>
+
+</refentry>
+</reference>
+
|
|
[-]
[+]
|
Changed |
check_openmanage-3.7.6.tar.bz2/nagios-plugins-openmanage.spec
^
|
| @@ -14,7 +14,7 @@
%endif
Name: nagios-plugins-openmanage
-Version: 3.7.5
+Version: 3.7.6
Release: 1%{?dist}
Summary: Nagios plugin to monitor hardware health on Dell servers
@@ -25,8 +25,10 @@
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
-# Building requires pod2man
-BuildRequires: perl
+# Building requires Docbook XML
+BuildRequires: libxslt
+BuildRequires: libxml2
+BuildRequires: docbook-style-xsl
# Rpmbuild doesn't find these perl dependencies
Requires: perl(Config::Tiny)
@@ -56,14 +58,15 @@
rm -f %{plugin}.exe
%build
-pod2man -s 8 -r "%{plugin} %{version}" -c "Nagios plugin" %{plugin}.pod %{plugin}.8
-pod2man -s 5 -r "%{plugin} %{version}" -c "Nagios plugin" %{plugin}.conf.pod %{plugin}.5
+pushd man
+make clean && make
+popd
%install
rm -rf %{buildroot}
install -Dp -m 0755 %{plugin} %{buildroot}%{nagiospluginsdir}/%{plugin}
-install -Dp -m 0644 %{plugin}.8 %{buildroot}%{_mandir}/man8/%{plugin}.8
-install -Dp -m 0644 %{plugin}.conf.5 %{buildroot}%{_mandir}/man5/%{plugin}.conf.5
+install -Dp -m 0644 man/%{plugin}.8 %{buildroot}%{_mandir}/man8/%{plugin}.8
+install -Dp -m 0644 man/%{plugin}.conf.5 %{buildroot}%{_mandir}/man5/%{plugin}.conf.5
%clean
rm -rf %{buildroot}
@@ -77,6 +80,11 @@
%changelog
+* Wed Jun 28 2012 Trond Hasle Amundsen <t.h.amundsen@usit.uio.no> - 3.7.6-1
+- Version 3.7.6
+- Added BuildRequires for Docbook XML (manual pages)
+- Changed building of manual pages
+
* Fri Apr 13 2012 Trond Hasle Amundsen <t.h.amundsen@usit.uio.no> - 3.7.5-1
- Version 3.7.5
|
