Shulou(Shulou.com)06/02 Report--

This article mainly introduces how to use the check_openmanage plug-in in nagios, has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let the editor take you to understand.

Check_openmanage is now a project of epel, so once epel-release is installed, you can use yum to install the check_openmanage plug-in.

The premise is that the monitored side has installed the dell omsa (open management server administrator) program.

# yum-y install nagios-plugins-openmanage.x86_64

The plug-in path is:

# / usr/lib64/nagios/plugins/openmanage

# cp / usr/lib64/nagios/plugins/openmanage / usr/local/nagios/libexec/

How to install epel and omsa can be google from the Internet

Whether it is installed on the tested side or on the nagios side depends on the environment of the test.

If you can use snmp, install the plug-in on the Nagios side.

If you can only use nrpe, install the plug-in on the monitored machine.

List of items that can be checked:

Storage components checked:

Controllers

Physical drives

Logical drives

Cache batteries

Connectors (channels)

Enclosures

Enclosure fans

Enclosure power supplies

Enclosure temperature probes

Enclosure management modules (EMMs)

Chassis components checked:

Processors

Memory modules

Cooling fans

Temperature probes

Power supplies

Batteries

Voltage probes

Power usage

Chassis intrusion

Removable flash media (SD cards)

Other:

ESM Log health

ESM Log content (default disabled)

Alert Log content (default disabled, not SNMP)

Nagios can detect the status of the host through snmp, or it can be detected using npre. When using nrpe, you need to define the corresponding command first (similar to the check of other services)

Configuration of command.cfg for nagios when using snmp

# Openmanage check via SNMP

Define command {

Command_name check_openmanage

Command_line / path/to/check_openmanage-H $HOSTADDRESS$

}

Add omsa monitoring to the configuration file of the monitor computer

# Dell OMSA status

Define service {

Use generic-service

Hostgroup_name dell-servers

Service_description Dell OMSA

Check_command check_openmanage

}

By comparison, it is found that the speed of obtaining information by snmp is faster than that of the local self-test. Therefore, when using nrpe, you need to take the parameter-t 30 (delay 30 seconds).

Help information that comes with it:

$check_openmanage-h

Usage: check_openmanage [OPTION]...

GENERAL OPTIONS: (common parameters, snmp and local can be used)

-f,-- config Specify configuration file

-p,-- perfdata Output performance data [default=no]

-t,-- timeout Plugin timeout in seconds [default=30]

-c,-- critical Custom temperature critical limits

-W,-- warning Custom temperature warning limits

-F,-- fahrenheit Use Fahrenheit as temperature unit

-d,-- debug Debug output, reports everything

-h,-- help Display this help text

-V-- version Display version info

SNMP OPTIONS: (SNMP mode)

-H,-- hostname Hostname or IP (required for SNMP) (check_openmanage-H 1.2.3.4)

-C,-- community SNMP community string [default=public]

-P,-- protocol SNMP protocol version [default=2]

-- port SNMP port number [default=161]

-6,-- ipv6 Use IPv6 instead of IPv4 [default=no]

-- tcp Use TCP instead of UDP [default=no]

OUTPUT OPTIONS:

-I-- info Prefix any alerts with the service tag

-e-- extinfo Append system info to alerts

-s-- state Prefix alerts with alert state

-S,-- short-state Prefix alerts with alert state abbreviated

-o,-- okinfo Verbosity when check result is OK

-B,-- show-blacklist Show blacklistings in OK output

-I-- htmlinfo HTML output with clickable links

CHECK CONTROL AND BLACKLISTING:

-a,-all Check everything, even log content

-b,-- blacklist Blacklist missing and/or failed components checks the blacklist

-- only Only check a certain component or alert type check individual item

-- check Fine-tune which components are checked check combination item

-- no-storage Don't check storage

For more information and advanced options, see the manual page or URL:

Http://folk.uio.no/trondham/software/check_openmanage.html

Snmp execution result:

[root@op omsa] # check_openmanage-H localhost

Controller 0 [PERC 6gami Integrated]: Firmware '6.1.1-0047' is out of date

# output information with status prompt

[root@op omsa] # check_openmanage-H localhost-s

WARNING: Controller 0 [PERC 6amp I Integrated]: Firmware '6.1.1-0047' is out of date

# this command uses a blacklist and does not check the Firmware firmware version update prompt.

[root@localhost etc] # / usr/lib/nagios/plugins/check_openmanage-H 1.2.3.4-s-b ctrl_fw=0

OK-System: 'PowerEdge R710, SN:' XXXXXX', 16 GB ram (8 dimms), 1 logical drives, 6 physical drives

# check only the power supply

[root@localhost etc] # / usr/lib/nagios/plugins/check_openmanage-H 1.2.3.4-s-only power

POWER OK-2 power supplies checked

Single item check parameter table

Keyword

Effect

Critical

Only output critical alerts. It is possible to use the-- check option together with this option to adjust checks.

Warning

Only output warning alerts. It is possible to use the-- check option together with this option to adjust checks.

Chassis

Only check chassis components, i.e. Everything but storage and log content.

Storage

Only check storage components

Memory

Only check memory modules

Fans

Only check fans

Power

Only check power supplies

Temp

Only check temperatures

Cpu

Only check processors

Voltage

Only check voltage probes

Batteries

Only check batteries

Amperage

Only check power usage

Intrusion

Only check chassis intrusion

Sdcard

Only check removable flash media

Servicetag

Only check for sane service tag

Esmhealth

Only check ESM log health

Esmlog

Only check ESM log content

Alertlog

Only check alertlog content

# check the storage information, not the FirmWare information

[root@localhost etc] # / usr/lib/nagios/plugins/check_openmanage-H 1.2.3.4-s-only storage-b ctrl_fw=0

STORAGE OK-6 physical drives, 1 logical drives

# if you want to know which information is on the blacklist when the information is displayed, you can add the parameter-B at the end of the command

[root@localhost etc] # / usr/lib/nagios/plugins/check_openmanage-H 1.2.3.4-s-b ctrl_fw=0-B

OK-System: 'PowerEdge R710, SN:' XXXXXX', 16 GB ram (8 dimms), 1 logical drives, 6 physical drives

-BLACKLISTED: ctrl_fw=0

Table of parameters that can be used in the blacklist function

Component

Comment

Ctrl

Controller

Ctrl_fw

Suppress the "special" warning message about old controller firmware. Use this if you can't or won't upgrade the firmware.

Ctrl_driver

Suppress the "special" warning message about old controller driver. Particularly useful on systems where you can't upgrade the driver.

Ctrl_stdr

Suppress the "special" warning message about old Windows storport driver.

Pdisk

Physical disk.

Pdisk_cert

Ignore warnings for non-certified physical drives unconfigured disk

Pdisk_foreign

Ignore warnings for foreign physical drives external disk for example: pdisk_foreign=1:0:5

Vdisk

Logical drive (virtual disk)

Bat

Controller cache battery

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.

Conn

Connector (channel)

Encl

Enclosure

Encl_fan

Enclosure fan

Encl_ps

Enclosure power supply

Encl_temp

Enclosure temperature probe

Encl_emm

Enclosure management module (EMM)

Dimm

Memory module

Fan

Fan (Cooling device)

Ps

Powersupply

Temp

Temperature sensor

Cpu

Processor (CPU)

Volt

Voltage probe

Bp

System battery

Amp

Amperage probe (power consumption monitoring)

Intr

Intrusion sensor

Sd

Removable flash media (SD card)

# Personalized output information

Parameter-postmsg

Check_openmanage-- postmsg 'NOTE: Service tag:% s-Dell support: 555-1234-5678'

Power Supply 0 [AC]: Presence Detected, Failure Detected, AC Lost

Controller 0 [PERC 6gami Integrated]: Driver '00.00.03.15 Murray RH1' is out of date

NOTE: Service tag: JV8KH0J-Dell support: 555-1234-5678

Parameter table:

Code

Replaced with

% m

System model

% s

Service tag

% b

BIOS version

% d

BIOS release date

% o

Operating system name

% r

Operating system release

% p

Number of physical drives

% l

Number of logical drives

% n

Line break

%%

A literal%

You can use-d or-- debug to display all check items:

[root@localhost etc] # / usr/lib/nagios/plugins/check_openmanage-H 1.2.3.4-d

System: PowerEdge R710 OMSA version: 7.2.0

ServiceTag: XXXXXX Plugin version: 3.7.9

BIOS/date: 1.0.4 03/09/2009 Checking mode: SNMPv2c UDP/IPv4

Storage Components

=

STATE | ID | MESSAGE TEXT

-+-

WARNING | 0 | Controller 0 [PERC 6CMI Integrated]: Firmware '6.1.1-0047' is out of date

OK | 0 | Controller 0 [PERC 6 Integrated] is Degraded

OK | 0 SAS-HDD 146GB 0 on ctrl 0 | Physical Disk 0:0:0 [SAS-HDD 146GB] 0 is Online

OK | 0 SAS-HDD 146GB 0 on ctrl 0 1 | Physical Disk 0:0:1 [SAS-HDD 146GB] 0 is Online

OK | 0 SAS-HDD 146GB 0 on ctrl 0 is Online 2 | Physical Disk 0:0:2 [SAS-HDD 146GB]

OK | 0 SAS-HDD 146GB 0 on ctrl 0 is Online | Physical Disk 0:0:3 [SAS-HDD 146GB] 0 is Online

OK | 0 SAS-HDD 146GB 1 on ctrl 0 is Online 4 | Physical Disk 1:0:4 [SAS-HDD 146GB] 0 is Online

OK | 0 SAS-HDD 146GB 1 on ctrl 0 is Ready 5 | Physical Disk 1:0:5 [SAS-HDD 146GB] 0 is Ready (Dedicated HS)

OK | 0:0 | Logical Drive'/ dev/sda' [RAID-5, 544.50 GB] is Ready

OK | 0:0 | Cache Battery 0 in controller 0 is Ready

OK | 0:0 | Connector 0 [SAS] on controller 0 is Ready

OK | 0:1 | Connector 1 [SAS] on controller 0 is Ready

OK | 0:0:0 | Enclosure 0:0:0 [Backplane] on controller 0 is Ready

OK | 0:1:0 | Enclosure 0:1:0 [Backplane] on controller 0 is Ready

Chassis Components

=

STATE | ID | MESSAGE TEXT

-+-

OK | 0 | Memory module 0 [DIMM_A2, 2048 MB] is Ok

OK | 1 | Memory module 1 [DIMM_A3, 2048 MB] is Ok

OK | 2 | Memory module 2 [DIMM_A5, 2048 MB] is Ok

OK | 3 | Memory module 3 [DIMM_A6, 2048 MB] is Ok

OK | 4 | Memory module 4 [DIMM_B2, 2048 MB] is Ok

OK | 5 | Memory module 5 [DIMM_B3, 2048 MB] is Ok

OK | 6 | Memory module 6 [DIMM_B5, 2048 MB] is Ok

OK | 7 | Memory module 7 [DIMM_B6, 2048 MB] is Ok

OK | 0 | Chassis fan 0 [System Board FAN 1 RPM] reading: 3960 RPM

OK | 1 | Chassis fan 1 [System Board FAN 2 RPM] reading: 3960 RPM

OK | 2 | Chassis fan 2 [System Board FAN 3 RPM] reading: 3960 RPM

OK | 3 | Chassis fan 3 [System Board FAN 4 RPM] reading: 3960 RPM

OK | 4 | Chassis fan 4 [System Board FAN 5 RPM] reading: 3840 RPM

OK | 0 | Power Supply 0 [AC]: Presence detected

OK | 1 | Power Supply 1 [AC]: Presence detected

OK | 0 | Temperature Probe 0 [System Board Ambient Temp] reads 27C (min=8/3, max=42/47)

OK | 0 | Processor 0 [Intel Xeon E5506 2.13GHz] is Present

OK | 1 | Processor 1 [Intel Xeon E5506 2.13GHz] is Present

OK | 0 | Voltage sensor 0 [CPU1 VCORE] is Good

OK | 1 | Voltage sensor 1 [CPU2 VCORE] is Good

OK | 2 | Voltage sensor 2 [CPU2 0.75 VTT CPU2 PG] is Good

OK | 3 | Voltage sensor 3 [CPU1 0.75 VTT CPU1 PG] is Good

OK | 4 | Voltage sensor 4 [System Board 1.5V PG] is Good

OK | 5 | Voltage sensor 5 [System Board 1.8V PG] is Good

OK | 6 | Voltage sensor 6 [System Board 3.3V PG] is Good

OK | 7 | Voltage sensor 7 [System Board 5V PG] is Good

OK | 8 | Voltage sensor 8 [CPU2 MEM PG] is Good

OK | 9 | Voltage sensor 9 [CPU1 MEM PG] is Good

OK | 10 | Voltage sensor 10 [CPU2 VTT] is Good

OK | 11 | Voltage sensor 11 [CPU1 VTT] is Good

OK | 12 | Voltage sensor 12 [System Board 0.9V PG] is Good

OK | 13 | Voltage sensor 13 [CPU2 1.8 PLL PG] is Good

OK | 14 | Voltage sensor 14 [CPU1 1.8 PLL PG] is Good

OK | 15 | Voltage sensor 15 [System Board 8.0V PG] is Good

OK | 16 | Voltage sensor 16 [System Board 1.1V PG] is Good

OK | 17 | Voltage sensor 17 [System Board 1.0 LOM PG] is Good

OK | 18 | Voltage sensor 18 [System Board 1.0 AUX PG] is Good

OK | 19 | Voltage sensor 19 [System Board 1.05V PG] is Good

OK | 0 | Battery probe 0 [System Board CMOS Battery] is Presence Detected

OK | 0 | Chassis intrusion 0 detection: Ok (Not Breached)

Other messages

=

STATE | MESSAGE TEXT

-+-

OK | ESM log health is Ok (less than 80% full)

OK | Chassis Service Tag is sane

# Personalized project checks using inspection profiles. Use the parameter-f

Check_openmanage-f / etc/check_openmanage.conf

Installation and use of check_openmange

Client 1, download the software version of Openmange:

Cd / opt/ wget http:/support.dell.com (here is the online address) mon02-001 / opt/DELL/dell there is an OM_6.1.0_ManNode_A00.tar to download this.

Tar zxvf omsa...*.tgz

Sh. / setup.sh

There are three choices.

Enter y to accept the agreement

Enter 6 to select all components

Enter I to indicate the installation selected

Prompt for the installation path during installation, and select the default path (/ opt/dell/srvadmin/). It is recommended to define the directory location / usr/local/openmanage.

The following are the errors (for reference only) that occurred during my installation:

1. Libstdc++.so.5 can't find it

Install: compat-libstdc related version of the software is fine

2.libcurl.so.3 can't find it.

Install curl and OK.

What we're doing now is using the client side and the server side together.

Wget http://folk.uio.no/trondham/software/files/check_openmanage-3.6.5.tar.gz (mon02-001 / opt/DELL has this package)

Tar zxvf check_openmanage-3.6.5.tar.gz

The Perl script cp / tar package / check_openmanage is put in / usr/local/nagios/libexec

Client side: defining nrpe.cfg

Vi / usr/local/nagios/etc/nrpe.cfg

Add one line to add

Commanded [check _ dell_hardware] = / usr/local/nagios/libexec/check_openmanage-e-- only critical

Save it.

Run / usr/local/nagios/libexec/check_openmanage-e-- only critical to see if there is a return value. If all OK is returned, the client is set up.

Set the server side as follows:

Server end defines service:

Define service {

Use saa-service

Host_name localhost

Service_description check_hardware

Check_command check_nrpe!check_dell_hardware

}

The localhost changes the host name according to the monitored machine.

Check whether the monitoring is successful:

Server / usr/local/nagios/libexec/check_nrpe-H hostIP-c check_dell_hardware

If there is a problem, check if the NRPE is normal.

The following installs the server using SNMP

Server side

Install: 1, install the relevant Perl-snmp package

Perl-Crypt-DES-2.05-3.2.el5.rf.i386.rpm

Perl-Digest-HMAC-1.01-2.2.el5.rf.noarch.rpm

Perl-Digest-SHA1-2.12-2.el5.rf.i386.rpm

Perl-Net-SNMP-5.2.0-1.2.el5.rf.noarch.rpm

Perl-Socket6-0.23-1.el5.rf.i386.rpm

Install the other packages in the installation sequence, and finally install perl-Net-SNMP-5.2.0-1.2.el5.rf.noarch.rpm

Download the check_openmanage plug-in (http://folk.uio.no/trondham/software/check_openmanage.html#download) downloads different software depending on the system.

Wget http://folk.uio.no/trondham/software/files/check_openmanage-3.6.5.tar.gz

Wget http://folk.uio.no/trondham/software/files/nagios-plugins-check-openmanage-3.6.5-1.el5.x86_64.rpm

The above is a simple installation, and in some places it is copied directly from others. There is nothing fancy to install, so you should be able to take a look at it.

The following are clips that use some parameters.

Check_openmanage-s displays detailed service status alarm check_openmanage-S shows a short service status alarm (that is, critcal is abbreviated to C)

Check_openmanage-I service status alarm prefixed with service number

Example: [JV8KH0J] Controller 0 [PERC 6 Integrated]: Driver '00.00.03.15 Mel RH1' is out of date

Check_openmanage-e displays the type of machine and alarm information (using a single line as a distinguishing number to display the system model service number of the machine)

Example: Power Supply 0 [AC]: Presence Detected, Failure Detected, AC Lost Controller 0 [PERC 6 Integrated]: Driver '00.00.03.15 RH1' is out of date

-SYSTEM: PowerEdge 1950, SN: JV8KH0J

Check_openmanage-- postmsg 'NOTE: Service tag:% s-Dell support: 800-8888-8888' can customize the prompt information according to the parameter-- postmsg.

Power Supply 0 [AC]: Presence Detected, Failure Detected, AC Lost Controller 0 [PERC 6 Integrated]: Driver '00.00.03.15 muri RH1' is out of date NOTE: Service tag: JV8KH0J-Dell support: 800-8888-8888

Where% s is a variable call within the system, here are all internal variables

% m System model machine model

% s Service tag Service number

% b BIOS version bios version

% d BIOS release date Bios release date

% o Operating system name system name

Version of r Operating system release operating system

% number of p Number of physical drives physical drives

Number of l Number of logical drives logical drives

% n Line break newline character

A literal a text

The above alarm information can be used together with multiple parameters. For example: check_openmanage-I-s

Check_openmanage-o by default, the output of OK information is one line, we can control, you can enter check_openmanage-o 3 to display 3 lines, and show some of the underlying hardware.

Check_openmanage-H localhost-b ctrl_driver=all-b pdisk=1:0:0:1-B Openmanage can control the blacklist, that is, the monitoring that has nothing to do with Jing. Use the parameter-b to add items that do not need to be monitored, but when there are too many blacklists, we will not know what has been removed. At this time, add a-B = (show-blacklist) to show the blacklist.

Check_openmanage-d displays the debug information after the software is running. (this is for manual debugging. Do not use this option in nagios)

Custom temperature threshold

Omreport, this is a self-test program with openmanage installed.

Omreport chassis temps displays the temperature of the machine

Check_openmanage-H myhost-- only temp-d this is the debugging of check_openmanage, showing the temperature of the machine, we can define the threshold alarm.

Check_openmanage-w 05030-c 040change the temperature alarm threshold

This means 15 minutes if the temperature is greater than 30 minutes and the temperature is greater than 40 check_openmanage critcal. This can be written on your own and need to change the time.

Add a blacklist

When we don't want to see some unimportant information, we can debug it according to-b.

For example:

Check_openmanage-s-b ctrl_driver=0,1 does not detect driver problems with the Controller. If all Controller drivers do not need monitoring, you can use ctrl_driver=all

The following is the code name (abbreviation) of the device:

=-- use-- check to detect a single item. 0 means off, 1 means on.

Check_openmanage-- check storage=0,esmlog=1 closes the test storage to view esmlog information

We can also define a file and use-- check to execute the check project defined in the file (to facilitate our repeated operations each time) vi / tmp/check_openmanage.check storage=0,esmlog=1

Check_openmanage-check / tmp/check_openmanage.check

Use-- only to monitor the specified project

Check_openmanage-- only storage only checks storage and does not monitor anything else

Here are some parameters for Only

If you want to check all, check_openmanage-a will have check.

Finally, it is combined with PNP4Nagios to display information in pictures.

Note:

When I was pretending, I found a serious problem:

Openmange software should not be uninstalled and installed on the server repeatedly. This will lead to many more processes. Each time they install it, they will generate 3 processes in groups such as the following:

Root 30672 0.0 0.0 21688 1056? S Jun08 0:00\ _ hald-runner

68 30680 0.0 0.0 12320 848? S Jun08 0:00\ _ hald-addon-acpi: listening on acpid socket / var/run/acpid.socket

68 30693 0.0 0.0 12320 844? S Jun08 0:00\ _ hald-addon-keyboard: listening on / dev/input/event0

And after you uninstall the software, the process will not Kill, only manual kill, and this process takes up a lot of CPU resources after a lot of more, there is a fluctuation in CPU LOAD every ten minutes. Our company's app server is because the installation of this load will fluctuate every ten minutes, from 1 to 20, and then drop immediately, so we must be careful not to install and uninstall repeatedly in the production environment.

There is no problem in other aspects, the software is quite easy to use, you can combine nagios and zabbix to achieve hardware monitoring.

DELL openmanage and nagios on ubuntu 10.04PDFPrintE-mail

Linux

Written by Michael

Thursday, 28 July 2011 19:51

The dell openmanage tools are quite good for monitoring Dell servers. Although it slows down boot time (which shouldn't happen often with servers anyway), it provides some great ways to monitor your server.

Install Dell OMSA

Add the repositories to a new file / etc/apt/sources.list.d/linux.dell.com.sources.list with the following content:

Deb http://linux.dell.com/repo/community/deb/latest /

Apt-get update

Gpg-keyserver pgpkeys.mit.edu-recv-key E74433E25E3D7775

Gpg-a-- export E74433E25E3D7775 | apt-key add-

Apt-get install srvadmin-all

Install the nagios check_openmanage plugin

Download the latest check_openmanage package from http://folk.uio.no/trondham/software/check_openmanage.html#download

Wget http://folk.uio.no/trondham/software/files/check-openmanage_3.6.8-1_all.deb

Install the openManage package:

Dpkg-I check-openmanage_3.6.6-1_all.deb

Check theoutput of:

/ usr/lib/nagios/plugins/check_openmanage

If you get the following output:

Storage Error! No controllers found

Problem running 'omreport chassis memory': Error: Memory object not found

Problem running 'omreport chassis fans': Error! No fan probes found on this system.

Problem running 'omreport chassis temps': Error! No temperature probes found on this system.

Problem running 'omreport chassis volts': Error! No voltage probes found on this system.

Do:

/ etc/init.d/dataeng restart

Rerun it, and blacklist warnings like 'Not certified drives' and controller firmware out of date like (or resolve them by swapping to certified disks and upgrade the raidcontroller firmware):

/ usr/lib/nagios/plugins/check_openmanage-b ctrl_fw=0/pdisk=0:0:0:0,0:0:0:1

If you run it, it should show something like:

/ usr/lib/nagios/plugins/check_openmanage-b ctrl_fw=0/pdisk=0:0:0:0,0:0:0:1

OK-System: 'PowerEdge R310, SN:' somenumber', 4 GB ram (2 dimms), 1 logical drives, 2 physical drives

Only uncertified hard drives should be blacklisted, certified disks do not have to be blacklisted.

Make sure that dataeng starts at boot

Update-rc.d dataeng defaults

Edit:

/ etc/nagios/nrpe_local.cfg

And add the command without warnings to it, like:

Commanded [check _ openmanage] = / usr/lib/nagios/plugins/check_openmanage-b ctrl_fw=0/pdisk=0:0:0:0,0:0:0:1

Restart the service:

/ etc/init.d/nagios-nrpe-server restart

Add the host to the nagios configuration on your Nagios server.

Optionally, you can start the openmanage built in webserver with

Omconfig system webserver action=start

The webserver is running on port 1311 https by default. You can login with the root account or other local accounts of the linux system.

Thank you for reading this article carefully. I hope the article "how to learn how to use check_openmanage plug-ins in nagios" shared by the editor will be helpful to everyone. At the same time, I also hope you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.