Home

Search Exchange

Search All Sites

Nagios Live Webinars

Let our experts show you how Nagios can help your organization.

Contact Us

Phone: 1-888-NAGIOS-1
Email: sales@nagios.com

Login

RSS Feeds

New Listings

Updated Listings

Directory Quicklinks

Home

All Categories

Add Listing

New Listings

Directory Tree

check_esxi_hardware.py

Submit review Recommend Print Visit

Rating

70 votes

Favoured:

Current Version

20220708

Last Release Date

2022-07-08

Compatible With

Nagios 1.x
Nagios 2.x
Nagios 3.x
Nagios 4.x
Nagios XI

Owner

Napsty

Website

www.claudiokuenzler.com/monitoring-plugins/check_esxi_hardwa

Download URL

www.claudiokuenzler.com/monitoring-plugins/check_esxi_hardwa...

License

GPL

Hits

344995

Meet The New Nagios Core Services Platform

Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.

Download Now

Monitoring Made Magically Better

Nagios Core on Overdrive
Powerful Monitoring Dashboards
Time-Saving Configuration Wizards
Open Source Powered Monitoring On Steroids
And So Much More!

View gallery

check_esxi_hardware (formerly known as check_esx_wbem) is an open source monitoring plugin to monitor the hardware of ESXi (and previously ESX) servers. It queries the CIM (Common Information Model) server running on the ESXi server to retrieve the current status of all discovered hardware parts. The plugin can also be used as standalone script to check the hardware. The plugin is written in python and uses the pywbem module. It supports both python2 and python3. See Requirements for more information.

Please find the plugin, more information and full documentation, including FAQ, here:

https://www.claudiokuenzler.com/monitoring-plugins/check_esxi_hardware.php

Version History
------------------
20080820 Initial release by David Ligeret
20080821 Add verbose mode by David Ligeret
20090219 Add try/except to catch AuthError and CIMError by Joshua Daniel Franklin
20100202 Added HP Support (HealthState) by Branden Schneider
20100512 Combined different versions (Joshua and Branden) and added hardware type switch
20100628 Outputs server model, s/n and bios version and set Unknown as default exit code by Samir Ibradzic
20100702 GlobalStatus was incorrectly getting (re)set to OK with every CIM element check by Aaron Rogers
20100705 After last version all Dell servers return UNKNOWN instead of OK, added Aaron's logic for Dell checks as well
20101028 Changed text in Usage and Example so people dont forget to use https://
20110110 If Dell Blade Servers were used, Serial Number of Chassis instead of Blade was returned - by Ludovic Huttin
20110207 Bugfix/new feature for Intel server systems by Carsten Schoene
20110215 Plugin now catches Socket Error (Timeout Error) and added a timeout parameter by Ludovic Hutin
20110221 Removed recently added timeout parameter due to incompatibility on Windows systems
20110221 Changed plugin name from check_esxi_wbem.py to check_esxi_hardware.py
20110426 Added 'ibm' hardware type (compatible to Dell output). Tested by Keith Erekson on an IBM x3550.
20110503 Plugin rewritten, added automatic hardware detection, opt params, perfdata and much more by Phil Randal
20110504 Some minor code changes, removed typo, bugfix for voltage sensors on IBM server by Phil Randal
20110505 Added possibility to use first line of a file as password (file:) by Fredrik Åslund
20110507 A lot of bugfixes and enhancements from Phil Randal (see changelog in plugin for details)
20110520 Bugfix for IBM Blade Servers by Bertrand Jomin
20110614 Rewrote external file handling, file can now be used for password AND username
20111003 Added ignore option to ignore certain elements by Ian Chard
20120402 Making plugin GPL compatible (Copyright) and preparing for OpenBSD port
20120405 Fix lookup of warranty info for Dell by Phil Randal
20120501 Bugfix in manufacturer discovery when cim entry not found or empty by Craig Hart
20121027 Workaround for Dell PE x620 for Riser Config Err 0: Connected element (wrong return code)
20130424 Another workaround for Dell systems "System Board 1 LCD Cable Pres 0: Connected"
20130702 Improving wrong authentication timeout and exit UNKNOWN by Carl R. Friend
20130725 Fix lookup of warranty info for Dell by Phil Randal
20140319 Another workaround for Dell systems "System Board 1 VGA Cable Pres 0: Connected"
20150109 Output serial number of chassis if a blade server is checked
20150119 Fix NoneType element bug by Andreas Gottwald
20150626 Added support for patched pywbem 0.7.0 and new version 0.8.0, handle SSL error exception
20150710 Exit Unknown instead of Critical for timeouts and auth errors by Stanislav German-Evtushenko
20151111 Cleanup and define variables by Stefan Roos
20160411 Distinguish between/add support for minor versions of pywbem 0.7 and 0.8
20160531 Add parameter for variable CIM port (useful when behind NAT)
20161013 Added support for pywbem 0.9.x (and upcoming releases)
20170905 Added option to ignore LCD/Display related elements (--no-lcd)
20180329 Try to use internal pywbem function to determine version
20180411 Throw an unknown if we can't fetch the data for some reason by Peter Newman
20181001 python3 compatibility
20180510 Allow regular expressions from ignore list (-r)
20190701 Fix lookup of warranty info for Dell (again) by Phil Randal
20200605 Added otion to ignore chassis intrusion elements (--no-intrusion) by Luca Berra
20200605 Add parameter (-S) for custom SSL/TLS protocol version
20200710 Improve missing mandatory parameter error text (issue #47), Delete temporary openssl config file after use (issue #48)
20210809 Fix TLSv1 usage (issue #51)
20220708 Added JSON-output (Zabbix needs it) by Marco Markgraf

Requirements
------------------
- Python must be installed (both Python2 and Python3 are supported)
- The Python extension pywbem must be installed
- If there is a firewall between your monitoring and ESXi server, open tcp port 5989 (or the port you define with -C)
- The CIM server and agent must be running on the ESXi server. Starting from ESXi 6.5 the CIM agent is disabled by default. See VMware KB 1025757 for more information.

Usage
------------------
./check_esxi_hardware.py -H esxi-server-ip -U username -P mypass [-C -S -V -i -r -v -p -I]

Reviews (55)

love it - stopped working latest vmware

bynarf41, August 5, 2022

Just updated to the latest esxi below and am getting an error I hope you can help with:

running against dell R440

sudo python -t check_esxi_hardware.py -H x.x.x.x -U myuser -P mypassword -V "dell" -S "TLSv1.2"
Traceback (most recent call last):
File "check_esxi_hardware.py", line 805, in
except pywbem._cim_operations.CIMError as args:
AttributeError: 'module' object has no attribute '_cim_operations'

Python 3.6 and current pwwbem installed centos 7 fully patched

ESXi Version 7.0.3
Hypervisor VMware ESXi
Build 20036589

any advice appreciated!

Error when connecting

bydmanson79, August 22, 2021

HAve an issue connecting to one esxi host after upgrading from esxi 6 to 6.7,
Checked Firewall, prereqs etc but just cannot connect to this host no matter what. I can connect to another host from the same place I have Python installed. If anyone has any ideas they are most welcome!

Below is what is returned when trying to connect via command prompt

Traceback (most recent call last):
File "C:\Program Files (x86)\Python39-32\lib\site-packages\urllib3\connection.
py", line 169, in _new_conn
conn = connection.create_connection(
File "C:\Program Files (x86)\Python39-32\lib\site-packages\urllib3\util\connec
tion.py", line 96, in create_connection
raise err
File "C:\Program Files (x86)\Python39-32\lib\site-packages\urllib3\util\connec
tion.py", line 86, in create_connection
sock.connect(sa)
ConnectionRefusedError: [WinError 10061] No connection could be made because the
target machine actively refused it

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "C:\Program Files (x86)\Python39-32\lib\site-packages\urllib3\connectionp
ool.py", line 699, in urlopen
httplib_response = self._make_request(
File "C:\Program Files (x86)\Python39-32\lib\site-packages\urllib3\connectionp
ool.py", line 382, in _make_request
self._validate_conn(conn)
File "C:\Program Files (x86)\Python39-32\lib\site-packages\urllib3\connectionp
ool.py", line 1010, in _validate_conn
conn.connect()
File "C:\Program Files (x86)\Python39-32\lib\site-packages\urllib3\connection.
py", line 353, in connect
conn = self._new_conn()
File "C:\Program Files (x86)\Python39-32\lib\site-packages\urllib3\connection.
py", line 181, in _new_conn
raise NewConnectionError(
urllib3.exceptions.NewConnectionError: : Failed to establish a new connection: [WinError 10061] No conn
ection could be made because the target machine actively refused it

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "C:\Program Files (x86)\Python39-32\lib\site-packages\requests\adapters.p
y", line 439, in send
resp = conn.urlopen(
File "C:\Program Files (x86)\Python39-32\lib\site-packages\urllib3\connectionp
ool.py", line 783, in urlopen
return self.urlopen(
File "C:\Program Files (x86)\Python39-32\lib\site-packages\urllib3\connectionp
ool.py", line 783, in urlopen
return self.urlopen(
File "C:\Program Files (x86)\Python39-32\lib\site-packages\urllib3\connectionp
ool.py", line 755, in urlopen
retries = retries.increment(
File "C:\Program Files (x86)\Python39-32\lib\site-packages\urllib3\util\retry.
py", line 574, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='192.168.7.11', port=
5989): Max retries exceeded with url: /cimom (Caused by NewConnectionError(': Failed to establish a new
connection: [WinError 10061] No connection could be made because the target mac
hine actively refused it'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "C:\Program Files (x86)\Python39-32\lib\site-packages\pywbem\_cim_http.py
", line 315, in wbem_request
resp = conn.session.post(
File "C:\Program Files (x86)\Python39-32\lib\site-packages\requests\sessions.p
y", line 590, in post
return self.request('POST', url, data=data, json=json, **kwargs)
File "C:\Program Files (x86)\Python39-32\lib\site-packages\requests\sessions.p
y", line 542, in request
resp = self.send(prep, **send_kwargs)
File "C:\Program Files (x86)\Python39-32\lib\site-packages\requests\sessions.p
y", line 655, in send
r = adapter.send(request, **kwargs)
File "C:\Program Files (x86)\Python39-32\lib\site-packages\requests\adapters.p
y", line 516, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='192.168.7.11', po
rt=5989): Max retries exceeded with url: /cimom (Caused by NewConnectionError(': Failed to establish a
new connection: [WinError 10061] No connection could be made because the target
machine actively refused it'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "C:\Program Files (x86)\Python39-32\check_esxi_hardware.py", line 780, in

instance_list = wbemclient.EnumerateInstances(classe)
File "C:\Program Files (x86)\Python39-32\lib\site-packages\pywbem\_cim_operati
ons.py", line 2775, in EnumerateInstances
result = self._imethodcall(
File "C:\Program Files (x86)\Python39-32\lib\site-packages\pywbem\_cim_operati
ons.py", line 1823, in _imethodcall
reply_data, self._last_server_response_time = wbem_request(
File "C:\Program Files (x86)\Python39-32\lib\site-packages\pywbem\_cim_http.py
", line 323, in wbem_request
raise ConnectionError(msg, conn_id=conn.conn_id)
pywbem._exceptions.ConnectionError: Failed to establish a new connection: [WinEr
ror 10061] No connection could be made because the target machine actively refus
ed it; OpenSSL version used: OpenSSL 1.1.1k 25 Mar 2021

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "C:\Program Files (x86)\Python39-32\check_esxi_hardware.py", line 781, in

except pywbem.cim_operations.CIMError as args:
AttributeError: module 'pywbem' has no attribute 'cim_operations'

not detecting fan problem on hpe servers

bykamtec1, May 4, 2021

Cool plugin but it cat determine fan problem - Fan Block 7
Hpedl360 server gen
----

20210504 14:03:54 Element Name = System Board 9 Fans
20210504 14:03:54 Element HealthState = 10
20210504 14:03:54 Element Name = Power Supply 3 Power Supplies
20210504 14:03:54 Element HealthState = 5
20210504 14:03:54 Element Name = System Chassis 1 UID Light
20210504 14:03:54 Check classe OMC_Fan
20210504 14:03:55 Element Name = Fan Block 8
20210504 14:03:55 Element HealthState = 5
20210504 14:03:55 Element Name = Fan Block 7
20210504 14:03:55 Element HealthState = 0
20210504 14:03:55 Element Name = Fan Block 6
20210504 14:03:55 Element HealthState = 5
20210504 14:03:55 Element Name = Fan Block 5
20210504 14:03:55 Element HealthState = 5
20210504 14:03:55 Element Name = Fan Block 4
20210504 14:03:55 Element HealthState = 5
20210504 14:03:55 Element Name = Fan Block 3
20210504 14:03:55 Element HealthState = 5
20210504 14:03:55 Element Name = Fan Block 2
20210504 14:03:55 Element HealthState = 5
20210504 14:03:55 Element Name = Fan Block 1
20210504 14:03:55 Element HealthState = 5
20210504 14:03:55 Check classe OMC_PowerSupply

----

6.7U2 restart of sfcbd-watchdog solved my M2Crypto.SSL.SSLError connect error...

bynagios@register.digi.nl, September 28, 2019

I ran this on the esxi server:

/etc/init.d/sfcbd-watchdog restart

after receiving this from the check_esxi_hardware script:

Traceback (most recent call last):
File "/opt/nagios/cv/libexec/check_esxi_hardware", line 617, in
c=wbemclient.EnumerateInstances('CIM_Chassis')
File "/opt/lib/python2.7/site-packages/pywbem-0.8.0rc3-py2.7.egg/pywbem/cim_operations.py", line 1019, in EnumerateInstances
**params)
File "/opt/lib/python2.7/site-packages/pywbem-0.8.0rc3-py2.7.egg/pywbem/cim_operations.py", line 593, in imethodcall
timeout=self.timeout)
File "/opt/lib/python2.7/site-packages/pywbem-0.8.0rc3-py2.7.egg/pywbem/cim_http.py", line 544, in wbem_request
h.endheaders()
File "/opt/lib/python2.7/httplib.py", line 1049, in endheaders
self._send_output(message_body)
File "/opt/lib/python2.7/httplib.py", line 893, in _send_output
self.send(msg)
File "/opt/lib/python2.7/site-packages/pywbem-0.8.0rc3-py2.7.egg/pywbem/cim_http.py", line 333, in send
self.connect()
File "/opt/lib/python2.7/site-packages/pywbem-0.8.0rc3-py2.7.egg/pywbem/cim_http.py", line 419, in connect
"SSL error %s: %s" % (str(arg.__class__), arg))
pywbem.cim_http.ConnectionError: SSL error : (104, 'Connection reset by peer')

esxcli system version get
Product: VMware ESXi
Version: 6.7.0
Build: Releasebuild-13981272
Update: 2
Patch: 60

Broken after ESXi v6.7U2

bybridrod, May 17, 2019

Traceback (most recent call last):
File "/tmp/check_esxi_hardware.py", line 717, in
instance_list = wbemclient.EnumerateInstances(classe)
File "/usr/lib64/python2.7/site-packages/pywbem/cim_operations.py", line 1585, in EnumerateInstances
**extra)
File "/usr/lib64/python2.7/site-packages/pywbem/cim_operations.py", line 914, in _imethodcall
recorder=self.operation_recorder)
File "/usr/lib64/python2.7/site-packages/pywbem/cim_http.py", line 756, in wbem_request
client.endheaders()
File "/usr/lib64/python2.7/httplib.py", line 1038, in endheaders
self._send_output(message_body)
File "/usr/lib64/python2.7/httplib.py", line 882, in _send_output
self.send(msg)
File "/usr/lib64/python2.7/site-packages/pywbem/cim_http.py", line 446, in send
self.connect()
File "/usr/lib64/python2.7/site-packages/pywbem/cim_http.py", line 550, in connect
ret = self.sock.connect_ssl()
File "/usr/lib64/python2.7/site-packages/M2Crypto/SSL/Connection.py", line 295, in connect_ssl
return m2.ssl_connect(self.ssl, self._timeout)
M2Crypto.SSL.SSLError: (104, 'Connection reset by peer')

Owner's reply

Please check out the FAQ: https://www.claudiokuenzler.com/blog/308/check-esxi-hardware-faq-frequently-asked-questions

Works great with 6.7 (have a question about using with lockdown mode)

bychr00ted, April 4, 2019

I'm using it with 6.7, I am testing placing the hosts in lockdown mode, but the check fails after placing it in lockdown mode, looking for help getting it to work inn lockdown mode.

Fix for Esxi 6.7

byVitalyZ, February 26, 2019

1 of 1 people found this review helpful

To get it to work with ESXi 6.7 you will need to enable CIM service and SSH. next ssh into shell and you will need to enable to CIM agent on the console.
#"cd /etc/init.d"
#"./wsman status"
#"./wsman start"
#"esxcli system wbem set --enable true"
#"./wsman status"
Disable SSH service unless you need it for something else
https://kb.vmware.com/s/article/1025757
Many Thanks,
Vitaly Z

Error popping up

byThomasC., September 11, 2018

getting this error:

(No output on stdout) stderr: Traceback (most recent call last):
File "/usr/local/nagios/libexec/check_esxi_hardware.py", line 648, in
wbemclient = pywbem.WBEMConnection(hosturl, (user,password), no_verification=True)
TypeError: __init__() got an unexpected keyword argument 'no_verification'

pywbem.exceptions.ConnectionError: SSL error

byWirerush, June 17, 2018

os version: centos7
esxi version: esxi 6.5
python version: python 2.7.5
pywbem version: 0.12.3

Traceback (most recent call last):
File "/usr/lib64/nagios/plugins/check_esxi_hardware.py", line 703, in
instance_list = wbemclient.EnumerateInstances(classe)
File "/usr/lib/python2.7/site-packages/pywbem/cim_operations.py", line 2229, in EnumerateInstances
**extra)
File "/usr/lib/python2.7/site-packages/pywbem/cim_operations.py", line 1616, in _imethodcall
conn_id=self.conn_id)
File "/usr/lib/python2.7/site-packages/pywbem/cim_http.py", line 790, in wbem_request
client.endheaders()
File "/usr/lib64/python2.7/httplib.py", line 1037, in endheaders
self._send_output(message_body)
File "/usr/lib64/python2.7/httplib.py", line 881, in _send_output
self.send(msg)
File "/usr/lib/python2.7/site-pac kages/pywbem/cim_http.py", line 468, in send
self.connect() # pylint: disable=no-member
File "/usr/lib/python2.7/site-packages/pywbem/cim_http.py", line 594, in connect
"SSL error %s: %s" % (arg.__class__, arg))
pywbem.exceptions.ConnectionError: SSL error : unexpected eof

The script appears to be able to connect as the OK alarm identifies the system information and serial number etc.

Do you have any idea what this error means?

Thanks

no_verification

bynagiosql, May 17, 2018

Seems not working on opensuse 42.3

# ./check_esxi_hardware.py -H serverip -U user -P password -V hp -i "IPMI SEL"
Traceback (most recent call last):
File "./check_esxi_hardware.py", line 648, in
wbemclient = pywbem.WBEMConnection(hosturl, (user,password), no_verification=True)
TypeError: __init__() got an unexpected keyword argument 'no_verification'

python-2.7.13-26.1
python-pywbem-0.7.0-10.4

ESXi 6.7 caused error "The web server returned a bad status line: ''"

bychowy1029, May 14, 2018

1 of 1 people found this review helpful

I just upgrade 1 of my ESXi from 6.5 to 6.7 and now all I get is errors (6.5 still working just fine thought):

20180514 14:35:25 Connection to https://xxxxxxx
20180514 14:35:25 Found pywbem version 0.7.0
20180514 14:35:25 Connection error, disable SSL certification verification (probably patched pywbem)
20180514 14:35:25 Check classe OMC_SMASHFirmwareIdentity
20180514 14:35:28 Unknown CIM Error: (0, "The web server returned a bad status line: ''")
20180514 14:35:28 Check classe CIM_Chassis
20180514 14:35:30 Unknown CIM Error: (0, "The web server returned a bad status line: ''")
20180514 14:35:30 Check classe CIM_Card
20180514 14:35:32 Unknown CIM Error: (0, "The web server returned a bad status line: ''")
20180514 14:35:32 Check classe CIM_ComputerSystem
20180514 14:35:34 Unknown CIM Error: (0, "The web server returned a bad status line: ''")
20180514 14:35:34 Check classe CIM_NumericSensor
20180514 14:35:36 Unknown CIM Error: (0, "The web server returned a bad status line: ''")
20180514 14:35:36 Check classe CIM_Memory
....
....

Only works with Admin-Rights

bymirkosoukup, April 29, 2018

Hi, it works really great, but i don't want to run it as an admin.

Is there a way to solve this. I also tried only Read-Right. But I got an "no_verification" error.

Do you have an idea?

Thanks

is it Active Directory Login supported?

bydataassurehk, April 23, 2018

I have tried but it's getting error on windows logon

[Errno 13] Permission denied

bysysc000, April 19, 2018

Hi all, in command line this check works fine but in Icinga2 GUI I receive this error:

UNKNOWN: (0, 'Socket error: [Errno 13] Permission denied')

Any idea why?

Issues with ESXi 6.5

bystuart3003, March 7, 2018

Excellent plugin but can't get it working with ESXi 6.5

Version check_esxi_hardware.py 20111003 gives this error:

CRITICAL: (0, "Socket error: (1, 'error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure')")

Upgraded to version 20170905 but now get:
pkg_resources.DistributionNotFound: pywbem

How to upgrade pywbem since I get errors trying to install - wrong version of python maybe?

# python -V
Python 2.4.3

Owner's reply

Cannot tell for sure, but python 2.4 is very very old. Try at least 2.7.

ESXi host NFS file share Monitoring using check_esxi_hardware plugin

bybsivavani, January 18, 2018

Hi,
We are already using this plugin to Monitor ESXi hardware health status and it is working fine.

With this plugin is it possible to Monitor ESXi host NFS file share Monitoring ?

Kindly advice ?

Owner's reply

No, hardware only. Please check the FAQ at https://www.claudiokuenzler.com/blog/308/check-esxi-hardware-faq-frequently-asked-questions .

(0, 'Socket error: [Errno 111] Connection refused')

bycurzondax, November 14, 2017

1 of 1 people found this review helpful

Had the same problem as the previous poster, this is what solved the issue: To enable the CIM agent on the ESXi 6.5 host, run this command via CLI:

esxcli system wbem set --enable true

Documentation:
https://kb.vmware.com/s/article/2148910

and

https://kb.vmware.com/s/article/1025757?r=2&Quarterback.validateRoute=1&KM_Utility.getArticleData=1&KM_Utility.getGUser=1&KM_Utility.getArticleLanguage=2&KM_Utility.getArticle=1

ESXi 6.5

byGromek, July 18, 2017

I love this plugin but it doesn't work on any of my ESXi's with 6.5 version. Do you have any plans on upgrading it ?

I keep getting UNKNOWN: (0, 'Socket error: [Errno 111] Connection refused')" on all of them.

Owner's reply

It works with 6.5. Please check the FAQ at https://www.claudiokuenzler.com/blog/308/check-esxi-hardware-faq-frequently-asked-questions .

check_esxi_hardware.py failed after VM patching

bycyc1979, April 17, 2017

After ESXi600-201703003 Offline Bundle patching on VMware ESXI 6.0 Update 2, check_esxi_hardware.py failed to work. Is this the new bug with check_esxi_hardware.py?

ERROR:
20170418 15:37:55 Unknown CIM Error: (0, "The web server returned a bad status line: ''")
::::::::::
20170418 15:47:59 Unknown CIM Error: (1, u'Timeout (or other socket error) waiting for response from provider')

FULL OUTPUT:
[root@amk-123 libexec]# ./check_esxi_hardware.py -H 10.168.70.230 -U nagios -P @3xsKQruw -V dell -v
20170418 15:37:49 Connection to https://10.168.70.230
20170418 15:37:49 Found pywbem version 0.7.0
20170418 15:37:49 Connection worked
20170418 15:37:49 Check classe OMC_SMASHFirmwareIdentity
20170418 15:37:49 Element Name = System BIOS
20170418 15:37:49 VersionString = 2.2.3
20170418 15:37:49 Check classe CIM_Chassis
20170418 15:37:50 Element Name = Chassis
20170418 15:37:50 Manufacturer = Dell Inc.
20170418 15:37:50 SerialNumber = HBTT82S
20170418 15:37:50 Model = PowerEdge R810
20170418 15:37:50 Element Op Status = 0
20170418 15:37:50 Check classe CIM_Card
20170418 15:37:50 Element Name = unknown
20170418 15:37:50 Element Op Status = 0
20170418 15:37:50 Check classe CIM_ComputerSystem
20170418 15:37:52 Element Name = System Board 7:1
20170418 15:37:52 Element Op Status = 0
20170418 15:37:52 Element Name = Add-in Card 11:1
20170418 15:37:52 Element Op Status = 0
20170418 15:37:52 Element Name = Add-in Card 11:2
20170418 15:37:52 Element Op Status = 0
20170418 15:37:52 Element Name = System Internal Expansion Board 16:1
20170418 15:37:52 Element Op Status = 0
20170418 15:37:52 Element Name = System Internal Expansion Board 16:2
20170418 15:37:52 Element Op Status = 0
20170418 15:37:52 Element Name = obh3amk-vmw-host3
20170418 15:37:52 Element Name = Hardware Management Controller (Node 0)
20170418 15:37:52 Element Op Status = 0
20170418 15:37:52 Check classe CIM_NumericSensor
20170418 15:37:53 Element Name = System Board 1 System Level
20170418 15:37:53 sensorType = 4 - Current
20170418 15:37:53 BaseUnits = 7
20170418 15:37:53 Scaled by = 0.010000
20170418 15:37:53 Current Reading = 450.000000
20170418 15:37:53 Upper Threshold Non Critical = 1310.000000
20170418 15:37:53 Upper Threshold Critical = 1380.000000
20170418 15:37:53 Element Op Status = 2
20170418 15:37:53 Element Name = Power Supply 2 Voltage
20170418 15:37:53 sensorType = 3 - Voltage
20170418 15:37:53 BaseUnits = 5
20170418 15:37:53 Scaled by = 0.010000
20170418 15:37:53 Current Reading = 226.000000
20170418 15:37:53 Element Op Status = 2
20170418 15:37:53 Element Name = Power Supply 1 Voltage
20170418 15:37:53 sensorType = 3 - Voltage
20170418 15:37:53 BaseUnits = 5
20170418 15:37:53 Scaled by = 0.010000
20170418 15:37:53 Current Reading = 222.000000
20170418 15:37:53 Element Op Status = 2
20170418 15:37:53 Element Name = Power Supply 2 Current
20170418 15:37:53 sensorType = 4 - Current
20170418 15:37:53 BaseUnits = 6
20170418 15:37:53 Scaled by = 0.010000
20170418 15:37:53 Current Reading = 1.000000
20170418 15:37:53 Element Op Status = 2
20170418 15:37:53 Element Name = Power Supply 1 Current
20170418 15:37:53 sensorType = 4 - Current
20170418 15:37:53 BaseUnits = 6
20170418 15:37:53 Scaled by = 0.010000
20170418 15:37:53 Current Reading = 1.000000
20170418 15:37:53 Element Op Status = 2
20170418 15:37:53 Element Name = System Board 1 FAN 6 RPM
20170418 15:37:53 sensorType = 5 - Tachometer
20170418 15:37:53 BaseUnits = 19
20170418 15:37:53 Scaled by = 0.010000
20170418 15:37:53 Current Reading = 4680.000000
20170418 15:37:53 Lower Threshold Critical = 720.000000
20170418 15:37:53 Element Op Status = 2
20170418 15:37:53 Element Name = System Board 1 FAN 5 RPM
20170418 15:37:53 sensorType = 5 - Tachometer
20170418 15:37:53 BaseUnits = 19
20170418 15:37:53 Scaled by = 0.010000
20170418 15:37:53 Current Reading = 4800.000000
20170418 15:37:53 Lower Threshold Critical = 720.000000
20170418 15:37:53 Element Op Status = 2
20170418 15:37:53 Element Name = System Board 1 FAN 4 RPM
20170418 15:37:53 sensorType = 5 - Tachometer
20170418 15:37:53 BaseUnits = 19
20170418 15:37:53 Scaled by = 0.010000
20170418 15:37:53 Current Reading = 4800.000000
20170418 15:37:53 Lower Threshold Critical = 720.000000
20170418 15:37:53 Element Op Status = 2
20170418 15:37:53 Element Name = System Board 1 FAN 3 RPM
20170418 15:37:53 sensorType = 5 - Tachometer
20170418 15:37:53 BaseUnits = 19
20170418 15:37:53 Scaled by = 0.010000
20170418 15:37:53 Current Reading = 4800.000000
20170418 15:37:53 Lower Threshold Critical = 720.000000
20170418 15:37:53 Element Op Status = 2
20170418 15:37:53 Element Name = System Board 1 FAN 2 RPM
20170418 15:37:53 sensorType = 5 - Tachometer
20170418 15:37:53 BaseUnits = 19
20170418 15:37:53 Scaled by = 0.010000
20170418 15:37:53 Current Reading = 4800.000000
20170418 15:37:53 Lower Threshold Critical = 720.000000
20170418 15:37:53 Element Op Status = 2
20170418 15:37:53 Element Name = System Board 1 FAN 1 RPM
20170418 15:37:53 sensorType = 5 - Tachometer
20170418 15:37:53 BaseUnits = 19
20170418 15:37:53 Scaled by = 0.010000
20170418 15:37:53 Current Reading = 4800.000000
20170418 15:37:53 Lower Threshold Critical = 720.000000
20170418 15:37:53 Element Op Status = 2
20170418 15:37:53 Element Name = System Board 1 Ambient Temp
20170418 15:37:53 sensorType = 2 - Temperature
20170418 15:37:53 BaseUnits = 2
20170418 15:37:53 Scaled by = 0.010000
20170418 15:37:53 Current Reading = 13.000000
20170418 15:37:53 Lower Threshold Non Critical = 8.000000
20170418 15:37:53 Upper Threshold Non Critical = 42.000000
20170418 15:37:53 Lower Threshold Critical = 3.000000
20170418 15:37:53 Upper Threshold Critical = 47.000000
20170418 15:37:53 Element Op Status = 2
20170418 15:37:53 Element Name = System Internal Expansion Board 1 IO1 Planar Temp
20170418 15:37:53 sensorType = 2 - Temperature
20170418 15:37:53 BaseUnits = 2
20170418 15:37:53 Scaled by = 0.010000
20170418 15:37:53 Current Reading = 33.000000
20170418 15:37:53 Lower Threshold Non Critical = 8.000000
20170418 15:37:53 Upper Threshold Non Critical = 92.000000
20170418 15:37:53 Lower Threshold Critical = 3.000000
20170418 15:37:53 Upper Threshold Critical = 97.000000
20170418 15:37:53 Element Op Status = 2
20170418 15:37:53 Check classe CIM_Memory
20170418 15:37:54 Element Name = CPU1 Level-1 Cache
20170418 15:37:54 Element Op Status = 0
20170418 15:37:54 Element Name = CPU1 Level-2 Cache
20170418 15:37:54 Element Op Status = 0
20170418 15:37:54 Element Name = CPU1 Level-3 Cache
20170418 15:37:54 Element Op Status = 0
20170418 15:37:54 Element Name = CPU2 Level-1 Cache
20170418 15:37:54 Element Op Status = 0
20170418 15:37:54 Element Name = CPU2 Level-2 Cache
20170418 15:37:54 Element Op Status = 0
20170418 15:37:54 Element Name = CPU2 Level-3 Cache
20170418 15:37:54 Element Op Status = 0
20170418 15:37:54 Element Name = CPU3 Level-1 Cache
20170418 15:37:54 Element Op Status = 0
20170418 15:37:54 Element Name = CPU3 Level-2 Cache
20170418 15:37:54 Element Op Status = 0
20170418 15:37:54 Element Name = CPU3 Level-3 Cache
20170418 15:37:54 Element Op Status = 0
20170418 15:37:54 Element Name = CPU4 Level-1 Cache
20170418 15:37:54 Element Op Status = 0
20170418 15:37:54 Element Name = CPU4 Level-2 Cache
20170418 15:37:54 Element Op Status = 0
20170418 15:37:54 Element Name = CPU4 Level-3 Cache
20170418 15:37:54 Element Op Status = 0
20170418 15:37:54 Element Name = Memory
20170418 15:37:54 Element Op Status = 2
20170418 15:37:54 Check classe CIM_Processor
20170418 15:37:55 Element Name = CPU1
20170418 15:37:55 Family = 179
20170418 15:37:55 CurrentClockSpeed = 2000MHz
20170418 15:37:55 Element Op Status = 2
20170418 15:37:55 Element Name = CPU2
20170418 15:37:55 Family = 179
20170418 15:37:55 CurrentClockSpeed = 2000MHz
20170418 15:37:55 Element Op Status = 15
20170418 15:37:55 Element Name = CPU3
20170418 15:37:55 Family = 179
20170418 15:37:55 CurrentClockSpeed = 2000MHz
20170418 15:37:55 Element Op Status = 15
20170418 15:37:55 Element Name = CPU4
20170418 15:37:55 Family = 179
20170418 15:37:55 CurrentClockSpeed = 2000MHz
20170418 15:37:55 Element Op Status = 15
20170418 15:37:55 Check classe CIM_RecordLog
20170418 15:37:55 Unknown CIM Error: (0, "The web server returned a bad status line: ''")
20170418 15:37:55 Check classe OMC_DiscreteSensor
20170418 15:37:58 Element Name = Add-in Card 2 VFlash 1
20170418 15:37:58 Element Name = Add-in Card 1 SD1 Status 1
20170418 15:37:58 Element Name = System Board 1 DKM Status 65
20170418 15:37:58 Element Name = Disk Drive Bay 1 Cable SAS B 65: Connected
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Cable SAS B 65: Config Error
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Cable SAS A 65: Connected
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Cable SAS A 65: Config Error
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 5: Drive Present
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 5: Drive Fault
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 5: Predictive Failure
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 5: Hot Spare
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 5: Parity Check In Progress
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 5: In Critical Array
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 5: In Failed Array
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 5: Rebuild In Progress
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 5: Rebuild Aborted
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 4: Drive Present
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 4: Drive Fault
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 4: Predictive Failure
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 4: Hot Spare
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 4: Parity Check In Progress
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 4: In Critical Array
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 4: In Failed Array
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 4: Rebuild In Progress
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 4: Rebuild Aborted
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 3: Drive Present
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 3: Drive Fault
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 3: Predictive Failure
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 3: Hot Spare
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 3: Parity Check In Progress
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 3: In Critical Array
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 3: In Failed Array
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 3: Rebuild In Progress
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 3: Rebuild Aborted
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 2: Drive Present
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 2: Drive Fault
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 2: Predictive Failure
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 2: Hot Spare
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 2: Parity Check In Progress
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 2: In Critical Array
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 2: In Failed Array
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 2: Rebuild In Progress
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 2: Rebuild Aborted
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 1: Drive Present
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 1: Drive Fault
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 1: Predictive Failure
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 1: Hot Spare
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 1: Parity Check In Progress
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 1: In Critical Array
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 1: In Failed Array
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 1: Rebuild In Progress
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 1: Rebuild Aborted
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 0: Drive Present
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 0: Drive Fault
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 0: Predictive Failure
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 0: Hot Spare
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 0: Parity Check In Progress
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 0: In Critical Array
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 0: In Failed Array
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 0: Rebuild In Progress
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 1 Drive 0: Rebuild Aborted
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 Power Optimized 0: OEM
20170418 15:37:58 Element Name = System Board 1 Power Optimized 0: Unknown
20170418 15:37:58 Element Name = System Board 1 Power Optimized 0: Unknown
20170418 15:37:58 Element Name = System Board 1 Power Optimized 0: Unknown
20170418 15:37:58 Element Name = System Board 1 Power Optimized 0: Unknown
20170418 15:37:58 Element Name = System Board 1 Fan Redundancy 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 PS Redundancy 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 Intrusion 0: General Chassis intrusion
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 OS Watchdog 0: Timer expired
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 OS Watchdog 0: Hard reset
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 OS Watchdog 0: Power down
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 OS Watchdog 0: Power cycle
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 Riser Config 0: Connected
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 Riser Config 0: Config Error
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Power Supply 2 Status 0: Presence detected
20170418 15:37:58 Element Name = Power Supply 2 Status 0: Failure status
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Power Supply 2 Status 0: Predictive failure
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Power Supply 2 Status 0: Power Supply AC lost
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Power Supply 2 Status 0: Config Error: Vendor Mismatch
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Power Supply 1 Status 0: Presence detected
20170418 15:37:58 Element Name = Power Supply 1 Status 0: Failure status
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Power Supply 1 Status 0: Predictive failure
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Power Supply 1 Status 0: Power Supply AC lost
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Power Supply 1 Status 0: Config Error: Vendor Mismatch
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 4 Status 0: IERR
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 4 Status 0: Thermal Trip
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 4 Status 0: FRB3/Processor startup/init failure
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 4 Status 0: Configuration Error
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 4 Status 0: Presence detected
20170418 15:37:58 Element Name = Processor 4 Status 0: Throttled
20170418 15:37:58 Element Name = Processor 3 Status 0: IERR
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 3 Status 0: Thermal Trip
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 3 Status 0: FRB3/Processor startup/init failure
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 3 Status 0: Configuration Error
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 3 Status 0: Presence detected
20170418 15:37:58 Element Name = Processor 3 Status 0: Throttled
20170418 15:37:58 Element Name = Processor 2 Status 0: IERR
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 2 Status 0: Thermal Trip
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 2 Status 0: FRB3/Processor startup/init failure
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 2 Status 0: Configuration Error
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 2 Status 0: Presence detected
20170418 15:37:58 Element Name = Processor 2 Status 0: Throttled
20170418 15:37:58 Element Name = Processor 1 Status 0: IERR
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 1 Status 0: Thermal Trip
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 1 Status 0: FRB3/Processor startup/init failure
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 1 Status 0: Configuration Error
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 1 Status 0: Presence detected
20170418 15:37:58 Element Name = Processor 1 Status 0: Throttled
20170418 15:37:58 Element Name = Disk Drive Bay 1 Presence 0: Present
20170418 15:37:58 Element Name = Disk Drive Bay 1 Presence 0: Absent
20170418 15:37:58 Element Name = Power Supply 2 Presence 1: Present
20170418 15:37:58 Element Name = Power Supply 2 Presence 1: Absent
20170418 15:37:58 Element Name = Power Supply 1 Presence 1: Present
20170418 15:37:58 Element Name = Power Supply 1 Presence 1: Absent
20170418 15:37:58 Element Name = Processor 4 Presence 1: Present
20170418 15:37:58 Element Name = Processor 4 Presence 1: Absent
20170418 15:37:58 Element Name = Processor 3 Presence 1: Present
20170418 15:37:58 Element Name = Processor 3 Presence 1: Absent
20170418 15:37:58 Element Name = Processor 2 Presence 1: Present
20170418 15:37:58 Element Name = Processor 2 Presence 1: Absent
20170418 15:37:58 Element Name = Processor 1 Presence 1: Present
20170418 15:37:58 Element Name = Processor 1 Presence 1: Absent
20170418 15:37:58 Element Name = System Board 1 IO Riser Pres 0: Present
20170418 15:37:58 Element Name = System Board 1 IO Riser Pres 0: Absent
20170418 15:37:58 Element Name = System Board 1 PCIe Riser Pres 0: Present
20170418 15:37:58 Element Name = System Board 1 PCIe Riser Pres 0: Absent
20170418 15:37:58 Element Name = System Board 1 Stor Adapt Pres 0: Present
20170418 15:37:58 Element Name = System Board 1 Stor Adapt Pres 0: Absent
20170418 15:37:58 Element Name = System Board 1 USB Cable Pres 0: Present
20170418 15:37:58 Element Name = System Board 1 USB Cable Pres 0: Absent
20170418 15:37:58 Element Name = System Board 1 iDRAC6 Ent Pres 0: Present
20170418 15:37:58 Element Name = System Board 1 iDRAC6 Ent Pres 0: Absent
20170418 15:37:58 Element Name = System Board 1 Heatsink Pres 0: Present
20170418 15:37:58 Element Name = System Board 1 Heatsink Pres 0: Absent
20170418 15:37:58 Element Name = System Board 1 VR P1V2 MAIN LOM 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 VR P1V5 IOH 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Internal Expansion Board 1 VR PLX RISER 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 VR PLX PG 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR P075 MEM4 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR P075 MEM3 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR P075 MEM2 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR P075 MEM1 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR P1V1 MEM4 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR P1V1 MEM3 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR P1V1 MEM2 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR P1V1 MEM1 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR PSI MEM4 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR PSI MEM3 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR PSI MEM2 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR PSI MEM1 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR P1V5 MEM4 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR P1V5 MEM3 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR P1V5 MEM2 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Memory Module 8 VR P1V5 MEM1 65
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 0.9V PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 1.1V PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 1.8V PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 3.3V PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 5V CPU PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 5V IO PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 8V PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 CPU 1.8 PLL PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 2 VIO 24 PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 1 VIO 13 PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 4 VCACHE 3 PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 3 VCACHE 2 PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 2 VCACHE 1 PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 1 VCACHE 0 PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 4 VCORE 3 PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 3 VCORE 2 PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 2 VCORE 1 PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Processor 1 VCORE 0 PG 0
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 3 ROMB Battery 0: Low
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = Disk Drive Bay 3 ROMB Battery 0: Failed
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Element Name = System Board 1 CMOS Battery 0: Failed
20170418 15:37:58 Element Op Status = 2
20170418 15:37:58 Check classe OMC_Fan
20170418 15:37:59 Element Name = FAN 6 RPM
20170418 15:37:59 Element Op Status = 2
20170418 15:37:59 Element Name = FAN 5 RPM
20170418 15:37:59 Element Op Status = 2
20170418 15:37:59 Element Name = FAN 4 RPM
20170418 15:37:59 Element Op Status = 2
20170418 15:37:59 Element Name = FAN 3 RPM
20170418 15:37:59 Element Op Status = 2
20170418 15:37:59 Element Name = FAN 2 RPM
20170418 15:37:59 Element Op Status = 2
20170418 15:37:59 Element Name = FAN 1 RPM
20170418 15:37:59 Element Op Status = 2
20170418 15:37:59 Check classe OMC_PowerSupply
20170418 15:47:59 Unknown CIM Error: (1, u'Timeout (or other socket error) waiting for response from provider')
20170418 15:47:59 Check classe VMware_StorageExtent
20170418 15:48:01 Check classe VMware_Controller
20170418 15:48:01 Check classe VMware_StorageVolume
20170418 15:48:02 Check classe VMware_Battery
20170418 15:48:02 Check classe VMware_SASSATAPort
OK - Server: Dell Inc. PowerEdge R810 s/n: HBTT82S System BIOS: 2.2.3 2011-04-05
[root@root@amk-123 libexec]#

Define class CIM_Card failing on IBM ESXi for version 6.0

byYELLOWDOG, January 25, 2017

This plugin is working with most of version of ESXi and DELL, HP and IBM manufacturers.
But I was unable to use it for IBM System X3650 M4 installed with version 6.0 of ESXi.
I had to uncomment the class CIM_Card in the source of the plugin in order to make it work properly. Otherwise I got the following error:
Check classe CIM_Card
Traceback (most recent call last):
File "./check_esxi_hardware.py", line 561, in ?
verboseoutput(" Element Name = "+elementName)
TypeError: cannot concatenate 'str' and 'NoneType' objects

<< Start < Prev 1 2 3 Next > End >>

Page 1 of 3

Nagios, the Nagios logo, and Nagios graphics are the servicemarks, trademarks, or registered trademarks owned by Nagios Enterprises. All other servicemarks and trademarks are the property of their respective owner. The files and information on this site are the property of their respective owner(s). Nagios Enterprises makes no claims or warranties as to the fitness of any file or information on this website, for any purpose whatsoever. In fact, we officially disclaim all liability. We do, however, think these community contributions are pretty damn cool. Website Copyright © 2009-2024 Nagios Enterprises, LLC. All rights reserved.