Header RSS Feed
 
If you only want to see the articles of a certain category, please click on the desired category below:
ALL Android Backup BSD Database Hacks Hardware Internet Linux Mail MySQL Monitoring Network Personal PHP Proxy Shell Solaris Unix Virtualization VMware Windows Wyse

check_esxi_hardware and Dell PowerEdge R620: Riser Config Err 0
Friday - Sep 21st 2012 - by - (1 comments)

In the past few weeks I've received a few mails indicating a problem when the Nagios plugin check_esxi_hardware is launched against a Dell PowerEdge R620 server.

The plugin will exit in Warning state and the following warning will be in the output:

WARNING : System Board 1 Riser Config Err 0: Connected - Server: Dell Inc. PowerEdge R620 s/n: xxxxxx System BIOS: 1.1.2 2012-03-08

The reason is that the CIM element shown as warning (System Board 1 Riser Config Err 0) uses an exit code different than 2:

Element Name = System Board 1 Riser Config Err 0: Connected
Element Op Status = 12

By CIM definition the exit code 12 means No Contact.

I'm still waiting for an official statement of DELL why this single element returns the exit code 12 instead of 2 (typo maybe??). So far it seems that only Dell PowerEdge R620 servers are affected.

As a workaround, check_esxi_hardware users may just use the ignore parameter to exclude this element from being checked:

./check_esxi_hardware.py -H esxi-server-ip -U username -P mypass -V dell -i "System Board 1 Riser Config Err 0: Connected"

 

Add a comment

Show form to leave a comment

Comments (newest first):

Bertrand JOMIN from France wrote on Mar 5th, 2013:
Hi Claudio,

I've the same issue for IBM Blade HS22 :

WARNING : Front Panel Board 1 Front Panel: Connected - Server: IBM BladeCenter HS22 -[7870S17]- s/n: ******** System BIOS: -[P9E157AUS-1.18]- 2012-06-14



Go to Homepage home
Linux Howtos how to's
Monitoring Plugins monitoring plugins
Links links

Valid HTML 4.01 Transitional
Valid CSS!
[Valid RSS]

7484 Days
until Death of Computers
Why?