Build precise queries to find exactly what you need
Press ESC to close
Join our next live webinar: “Advanced Nagios Monitoring Techniques” – Register Now
Your review has been submitted and is pending approval.
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.
Current Version
20220708
Last Release Date
2022-07-08
Owner
Claudio Kuenzler
Website
https://www.claudiokuenzler.com/monitoring-plugins/check_esxi_hardware.php
Download URL
https://www.claudiokuenzler.com/monitoring-plugins/check_esxi_hardware.py
License
GPL
Compatible With
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]
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!
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-32libsite-packagesurllib3connection. py", line 169, in _new_conn conn = connection.create_connection( File "C:Program Files (x86)Python39-32libsite-packagesurllib3utilconnec tion.py", line 96, in create_connection raise err File "C:Program Files (x86)Python39-32libsite-packagesurllib3utilconnec 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-32libsite-packagesurllib3connectionp ool.py", line 699, in urlopen httplib_response = self._make_request( File "C:Program Files (x86)Python39-32libsite-packagesurllib3connectionp ool.py", line 382, in _make_request self._validate_conn(conn) File "C:Program Files (x86)Python39-32libsite-packagesurllib3connectionp ool.py", line 1010, in _validate_conn conn.connect() File "C:Program Files (x86)Python39-32libsite-packagesurllib3connection. py", line 353, in connect conn = self._new_conn() File "C:Program Files (x86)Python39-32libsite-packagesurllib3connection. 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-32libsite-packagesrequestsadapters.p y", line 439, in send resp = conn.urlopen( File "C:Program Files (x86)Python39-32libsite-packagesurllib3connectionp ool.py", line 783, in urlopen return self.urlopen( File "C:Program Files (x86)Python39-32libsite-packagesurllib3connectionp ool.py", line 783, in urlopen return self.urlopen( File "C:Program Files (x86)Python39-32libsite-packagesurllib3connectionp ool.py", line 755, in urlopen retries = retries.increment( File "C:Program Files (x86)Python39-32libsite-packagesurllib3utilretry. 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-32libsite-packagespywbem_cim_http.py ", line 315, in wbem_request resp = conn.session.post( File "C:Program Files (x86)Python39-32libsite-packagesrequestssessions.p y", line 590, in post return self.request('POST', url, data=data, json=json, **kwargs) File "C:Program Files (x86)Python39-32libsite-packagesrequestssessions.p y", line 542, in request resp = self.send(prep, **send_kwargs) File "C:Program Files (x86)Python39-32libsite-packagesrequestssessions.p y", line 655, in send r = adapter.send(request, **kwargs) File "C:Program Files (x86)Python39-32libsite-packagesrequestsadapters.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-32check_esxi_hardware.py", line 780, in instance_list = wbemclient.EnumerateInstances(classe) File "C:Program Files (x86)Python39-32libsite-packagespywbem_cim_operati ons.py", line 2775, in EnumerateInstances result = self._imethodcall( File "C:Program Files (x86)Python39-32libsite-packagespywbem_cim_operati ons.py", line 1823, in _imethodcall reply_data, self._last_server_response_time = wbem_request( File "C:Program Files (x86)Python39-32libsite-packagespywbem_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-32check_esxi_hardware.py", line 781, in except pywbem.cim_operations.CIMError as args: AttributeError: module 'pywbem' has no attribute 'cim_operations'
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 ----
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
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')
Please check out the FAQ: https://www.claudiokuenzler.com/blog/308/check-esxi-hardware-faq-frequently-asked-questions
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.
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
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'
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
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
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 .... ....
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
I have tried but it's getting error on windows logon
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?
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
Cannot tell for sure, but python 2.4 is very very old. Try at least 2.7.
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 ?
No, hardware only. Please check the FAQ at https://www.claudiokuenzler.com/blog/308/check-esxi-hardware-faq-frequently-asked-questions .
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
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.
It works with 6.5. Please check the FAQ at https://www.claudiokuenzler.com/blog/308/check-esxi-hardware-faq-frequently-asked-questions .
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]#
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
I have been using this product for about 2 years now. i recently updated one of my hosts to ESXi 6.0 U2 and am now having issues with the hardware check. I wanted to see if there was an update coming or if anyone else had experience this? Also is there any planned support for the new 6.5 release?
I tried to run the command but I get an error. Traceback (most recent call last): File "./check_esxi_hardware.py", line 608, in ? pywbemversion = pkg_resources.get_distribution("pywbem").version File "/usr/lib/python2.4/site-packages/pkg_resources.py", line 229, in get_distribution if isinstance(dist,Requirement): dist = get_provider(dist) File "/usr/lib/python2.4/site-packages/pkg_resources.py", line 115, in get_provider return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0] File "/usr/lib/python2.4/site-packages/pkg_resources.py", line 585, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python2.4/site-packages/pkg_resources.py", line 483, in resolve raise DistributionNotFound(req) # XXX put more info here pkg_resources.DistributionNotFound: pywbem I have the following version of pywbem on the system. pywbem.noarch 0:0.7.0-3.el5 I tried reinstalling that package but no change. Anyone have any ideas please?
Hello, I'm runing this check on 3 ESXi Servers. On 2 Server it's all OK. The third Server is making problems. The result of the check says "Memory Critical". I checked the Memory of the Server and all the memory is OK. I think the problem is here: 20160713 12:24:21 Check classe CIM_Memory 20160713 12:24:22 Element Name = Socket 1 Level-1 Cache 20160713 12:24:22 Element Op Status = 0 20160713 12:24:22 Element Name = Socket 1 Level-2 Cache 20160713 12:24:22 Element Op Status = 0 20160713 12:24:22 Element Name = Socket 1 Level-3 Cache 20160713 12:24:22 Element Op Status = 0 20160713 12:24:22 Element Name = Socket 2 Level-1 Cache 20160713 12:24:22 Element Op Status = 0 20160713 12:24:22 Element Name = Socket 2 Level-2 Cache 20160713 12:24:22 Element Op Status = 0 20160713 12:24:22 Element Name = Socket 2 Level-3 Cache 20160713 12:24:22 Element Op Status = 0 20160713 12:24:22 Element Name = Memory 20160713 12:24:22 Element Op Status = 6 When I comment out the line "CIM_Memory" then all is OK. This is no solution because I want to monitor the Memory. Can anyone please help me ?
Hi, i'm checking 3 same ESXI Servers with the plugin. With 2 Servers all is OK. The third Server is giving me a Memory Critical, I checked the Server Memory and all the Memory is okay there is no failure. I think the problem is here: Check classe CIM_Memory 20160713 11:00:09 Element Name = Socket 1 Level-1 Cache 20160713 11:00:09 Element Op Status = 0 20160713 11:00:09 Element Name = Socket 1 Level-2 Cache 20160713 11:00:09 Element Op Status = 0 20160713 11:00:09 Element Name = Socket 1 Level-3 Cache 20160713 11:00:09 Element Op Status = 0 20160713 11:00:09 Element Name = Socket 2 Level-1 Cache 20160713 11:00:09 Element Op Status = 0 20160713 11:00:09 Element Name = Socket 2 Level-2 Cache 20160713 11:00:09 Element Op Status = 0 20160713 11:00:09 Element Name = Socket 2 Level-3 Cache 20160713 11:00:09 Element Op Status = 0 20160713 11:00:09 Element Name = Memory 20160713 11:00:09 Element Op Status = 6 20160713 11:00:09 Global exit set to CRITICAL If I comment out "CIM_Memory" then the plugin shows "OK", but thats no solution because I want to monitor the memory. Can anyone help me please?
Hello! I trying to monitor VMware ESXi 5.1.0 build-1065491 (Update 1) on the server ProLiant DL360p Gen8. My enviroment: Centos 5.9 x386 Python 2.7 Nagios 4.0.8 check_esxi_hardware.py version 20150710. I installed python-pywbem (0.7.0) extension from here http://pywbem.github.io/pywbem/installation.html When I try to check I receive the error: # ./check_esxi_hardware.py -H 192.168.33.252 -U root -P passw -V hp Traceback (most recent call last): File "./check_esxi_hardware.py", line 646, in instance_list = wbemclient.EnumerateInstances(classe) File "/usr/local/lib/python2.7/site-packages/pywbem/cim_operations.py", line 404, in EnumerateInstances **params) File "/usr/local/lib/python2.7/site-packages/pywbem/cim_operations.py", line 168, in imethodcall verify_callback = self.verify_callback) File "/usr/local/lib/python2.7/site-packages/pywbem/cim_http.py", line 184, in wbem_request h.putheader('Content-length', len(data)) File "/usr/local/lib/python2.7/httplib.py", line 924, in putheader str = '%s: %s' % (header, 'rnt'.join(values)) TypeError: sequence item 0: expected string, int found Can anybody help me? Please)
Please try it with the newest version (20160411 as of today) and the new and stable pywbem 0.8.x.
Realy nice script but no esxi 6.0 support. It is planned?
It works with ESXi 6.x.
Not much of a Review, but a reply to @itheodoridis On Claudios website, there's a very good faq section with all the latest infos - but to make things short: downgrade pybwm like this apt install python-pywbem=0.7.0-4 this should temporarily fix the issue until they release an update. for updates on this issue, look here: https://bugs.launchpad.net/ubuntu/+source/pywbem/+bug/1434991 Happy Easter everyone =)
Thanks for that hint. This is now solved with the current version 20150626.
Hello. The plugin worked like a charm with Ubuntu 12.04 LTS Server and nagios 3.5. I decided to upgrade to Ubuntu 14.04.02 LTS (and then possibly to Nagios 4) but right after the upgrade the plugin started producing errors. When I try this on the command line: ./check_esxi_hardware.py -H hostname -U root -P password -V hp Traceback (most recent call last): File "./check_esxi_hardware.py", line 619, in instance_list = wbemclient.EnumerateInstances(classe) File "/usr/lib/pymodules/python2.7/pywbem/cim_operations.py", line 421, in EnumerateInstances **params) File "/usr/lib/pymodules/python2.7/pywbem/cim_operations.py", line 183, in imethodcall no_verification = self.no_verification) File "/usr/lib/pymodules/python2.7/pywbem/cim_http.py", line 268, in wbem_request h.endheaders() File "/usr/lib/python2.7/httplib.py", line 969, in endheaders self._send_output(message_body) File "/usr/lib/python2.7/httplib.py", line 829, in _send_output self.send(msg) File "/usr/lib/pymodules/python2.7/pywbem/cim_http.py", line 115, in send self.connect() File "/usr/lib/pymodules/python2.7/pywbem/cim_http.py", line 167, in connect except ( Err.SSLError, SSL.SSLError, SSL.SSLTimeoutError AttributeError: 'module' object has no attribute 'SSLTimeoutError' Any ideas? I have found similar problems reported elsewhere some are refering to failed module imports. I can't say I know my way around Python but I am willing to try.
This is fixed in version 20150626.
Works great, but after problem with one of the memory WARNING : System Board 8 Memory: Correctable ECC logging limit reached - Server: HP ProLiant DL380 G7 after replacing it to the new one I have another problem: WARNING : Memory - Server: HP ProLiant DL380 G7 I think that the problem is in the section "Element Op Status = 3" 20150203 11:20:32 Check classe CIM_Memory 20150203 11:20:32 Element Name = Proc 1 Level-1 Cache 20150203 11:20:32 Element Op Status = 0 20150203 11:20:32 Element Name = Proc 1 Level-2 Cache 20150203 11:20:32 Element Op Status = 0 20150203 11:20:32 Element Name = Proc 1 Level-3 Cache 20150203 11:20:32 Element Op Status = 0 20150203 11:20:32 Element Name = Proc 2 Level-1 Cache 20150203 11:20:32 Element Op Status = 0 20150203 11:20:32 Element Name = Proc 2 Level-2 Cache 20150203 11:20:32 Element Op Status = 0 20150203 11:20:32 Element Name = Proc 2 Level-3 Cache 20150203 11:20:32 Element Op Status = 0 20150203 11:20:32 Element Name = Memory 20150203 11:20:32 Element Op Status = 3 20150203 11:20:32 GLobal exit set to WARNING
The script is great!! I've implemented it a couple of weeks ago. It worked perfectly fine but since about a week ago, one of the checks is giving an error. Error: CRITICAL: (0, 'Socket error: [Errno 8] _ssl.c:490: EOF occurred in violation of protocol') I've searched the web and also searched for solutions myself but I couldn't find anything. The webinterface is reachable and the SSL certificate is working just fine. It works on all the other ESXi servers except for this one. Does somebody know the solution for this error? Gr, Channing The Netherlands
Another user had the same problem and it seemed to be a problem of the ESXi host. After a restart of this particular ESXi host, the check worked again.
Adding nagios user to the root group is a big security hole. I suggest never doing this. Here is a better work around until VMware fixes 'CIM interaction' permission (which doesn't work at least since 4.0 and up to the recent 5.5): 1) Create a local user 'nagios' on a ESXi host 2) Add a cron job to check and update /etc/security/access.conf user=nagios; access=/etc/security/access.conf; crontab=/var/spool/cron/crontabs/root; grep $access $crontab > /dev/null || cat $crontab */5 * * * * grep '^+:$user:sfcb$' $access > /dev/null || sed -i '2i +:$user:sfcb' $access EOF 3) Done! Now you can use nagios user to check check_esxi_hardware.py, no special roles or permissions are needed.
Hy! One of the best scripts i found for monitoring ESXi Hosts without vCenter! I'm using it on Fujitsu Servers, Hardware Option = intel. The Script detects Disk Errors without Problems, but if an BBU needs to be replaces the Scrips returns OK?? Scriptoutput: OK - Server: FUJITSU System BIOS: V4.6.5.3 R1.15.0 for D2939-A1x 2012-09-12 ESXi 4.1 Status = Critical BBU on Controller 0 (Health State Not Good) Maybe anybody can help to find an solution cheers Roland
Hi, I have latest patches updated on ESXi5.1 and when I monitor the esxi dell r710 hardware using the plugin, it shows me warning that my RAID controller is not working properly i.e. "WARNING : Controller XXXXXXXXXXXXXXX(PERC H700 Integrated) WARNING : Controller XXXXXXXXXXXXXXX(PERC H700 Integrated)" However there is no warning in vSphere Hardware Status tab. Is the plugin showing wrong info or vSphere not showing correct information. I am confused. Please suggest.
This is because vsphere client uses the CIM "HealthState" while the plugin uses "OperationalState" responses for Dell servers. Hence the difference. There is a simple reason to this: In the past, Dell servers rarely submitted good HealthState information. Since more or less 2013, Dell seems to have switched to HealthState. I intend to change this in the future.
Great avenue to add a basic health check. Works perfectly, out of the box for my Dell R905s & R620s
Ran into an instance where I too got the "invalid tokens" errors when running the script. It turns out that my Chassis had an unprintable character in it (Thanks HP!). As an ugly patch, I inserted the following before line 198 in pywbem/cim_operations.py. resp_xml = filter(lambda x: x in string.printable, resp_xml)
Thanks a lot for this great work! I'm running it on Esxi 5.1 UP2 and BL460c G8.
It works fine on an IBM with ESXi 4.1 but it doesn't work on a HP ProLiant DL380 G5 with ESXi 5.5. Enabling verbose mode it waits forever at VMware_Controller: ... 20131227 06:42:09 Element Name = Fan 1 20131227 06:42:09 Element Op Status = 2 20131227 06:42:09 Check classe OMC_PowerSupply 20131227 06:42:09 Element Name = Power Supply 1 20131227 06:42:09 Element Op Status = 2 20131227 06:42:09 Element Name = Power Supply 2 20131227 06:42:09 Element Op Status = 0 20131227 06:42:09 Check classe VMware_StorageExtent 20131227 06:42:10 Check classe VMware_Controller Any idea why? Thanks Daniel
Please refer to the FAQ, maybe you'll find your solution: http://www.claudiokuenzler.com/blog/308/check-esxi-hardware-faq-frequently-asked-questions
I am unable to get it to return anything in NagiosXI Output empty
This works great when running it from CentOS terminal with root, but when I created the command in /etc/nagios/objects/commands.cfg and called it in services.cfg nagios gives me the following status(Return code of 126 is out of bounds - plugin may not be executable. define command{ command_name check_esxi_hardware command_line $USER1$/check_esxi_hardware.py -H $HOSTADDRESS$ -U $ARG1$ -P $ARG2$ -V $ARG3$ } define service{ use generic-service hostgroup_name VMWare-servers service_description System: ESXi Hardware status check_command check_esxi_hardware!root!mypass!hp } I have verified that the check_esxi_hardware.py is executable, considering I am able to run it from the command line. I used chmod -R 755 root.root /usr/lib64/nagios/plugins/check_esxi_hardware.py. So why am I getting a return code 126 from Nagios when the command is executable?
Check your resources.cfg and make sure that $USER1$ is actually /usr/lib64/nagios/plugins.
Hi, When I use the command /usr/lib64/nagios/plugins/check_esxi_hardware.py -H xx.xx.xx.xxx -U root -P password -V dell it work. OK - Server: Dell Inc. PowerEdge XXX s/n: XXXXXX System BIOS: XX.xx.XX However when I use the check_nrpe command /usr/lib64/nagios/plugins/check_nrpe -H 127.0.0.1 -c VMwareESXi I got this error. CRITICAL: (0, 'Socket error: [Errno 13] Permission denied') Can you advice me what when wrong?
I love the plugin but I cannot get it to execute in the command defintion if I use %HOSTADDRESS% instead of the full IP. Obviously, I need to be able to use vars to apply the service to all my VMware servers. Any ideas? HEre are my command and service defs: ############## Command Definitions for VMWare Servers ################################## define command { command_name check_vmware_hardware command_line /usr/lib/nagios/plugins/check_esxi_hardware.py -H %HOSTADDRESS% -U root -P 'MYPASS' } ############## Service Definitions for vmware Servers ################################### define service{ use generic-service ; Name of service template to use hostgroup_name vmware-servers service_description System: ESXi HArdware Status check_command check_vmware_hardware }
It should be $HOSTADDRESS$ (not percentage signs).
This plugin is just the job! It worked a treat and along with the contribution from nicola.sarobba (made against the previous version) about using a non-root user (see below), this has made my day. One of the 8 hosts I'm checking, shows up some weird results (no server details): - "OK Server: " Running with " -v" shows lots of this kind of thing: - # /usr/local/nagios/libexec/check_esxi_hardware.py -H vmserver01 -U nagios -P 'wonkydonky' -I uk -v -V dell 20130807 23:31:26 Connection to https://vmserver01 20130807 23:31:26 Check classe OMC_SMASHFirmwareIdentity 20130807 23:31:26 Unknown CIM Error: (1, u'ThreadPool --- Failed to enqueue request. Too many queued requests already: vmware_base, active 5, queued 11 ') 20130807 23:33:52 Check classe VMware_StorageExtent 20130807 23:33:53 Check classe VMware_Controller 20130807 23:33:55 Check classe VMware_StorageVolume 20130807 23:33:57 Check classe VMware_Battery 20130807 23:33:59 Check classe VMware_SASSATAPort OK - Server: When I log in to vSphere it's looking quite like the server has some problems (health check shows all "unknown"), so not really the script's fault, though a "WARNING: couldn't get any info or similar" might be more appropriate? Comments to other reviewers now: - ## turner2151uk, have you tried "escaping" the exclaimation mark like this? Pa55w0rD!s ## Perematko, nicola.sarobba suggested this (which worked a treat for me): - in vSphere - create a nagios user - add this user to the root group - Assign the "No access" role to the nagios user ## Pentangle, perhaps it's not executable? I had to do the following to get it to run: - "chmod +x check_esxi_hardware.py"
Great plugin! Completely works fine. One thing I cant get to work is an exclamation mark in my password '!'.
Hi, i have the strange issue with memory. There is verbose output from check_esxi_hardware.py: http://pastebin.com/vm5fbXS3 And i dont have any idea about this CRITICAL error. I checked memory on this server by memtest and there is no errors. By the way, there is no any alerts in vSphere Client on this hypervisor. So, why i have this CRITICAL output?
Your CRITICAL comes from this: 20130403 11:54:11 Element Name = Memory 20130403 11:54:11 Element Op Status = 6 20130403 11:54:11 Global exit set to CRITICAL According to the CIM table, exit code 6 means "error". The whole check class seems to be strange on your hardware. Try to run the plugin without CIM_Memory (comment/disable it in the plugin) and see if that helps.
Plugin worked very well for me with vmware 4.1 & 5.1. The only problem was getting user with proper permissions set up on the vmware side. Running without Administrator privileges requires a small hack: there is a way to make it work without Administrator role ( with No Access). You need to add your monitoring account to root group on the host. Vi-client won't let you do that, so just ssh to your host , vi /etc/group and modify existing line to look like this : root:x:0:root,monitor I'm not sure if it opens some kind of other horrible security hole somewhere, but it works and looks reasonably secure.
First off, thank you for your work on the plugin. Works well as root, etc. I perform the following and it will not work, unless supplying root password or making nagios user an Administrator: 0 - Run plugin with root credentials and works 100% 1 - Create nagios role 2 - Add CIM access to role 3 - Create nagios user 4 - Assign user to role 5 - Run plugin and receive " : Authentication Error! - Server:" 6 - Edit role and select the "Check All" box enabling this nagios user full permissions 7 - Run plugin and receive " : Authentication Error! - Server:" So at this point a new user with full control cannot access the CIM information at all. 8 - Change Nagios user to "Administrator" role 9 - Completes check 100% This will allow me to not supply root password for this system as it is a central root password. But the full on access is still scary. Am I doing something wrong? I must be because other people are doing fine. Please correct me :) PS: ESXi 5.1 with most recent patches applied.
It is actually mandatory to grant the "Administrator" role. This is because of the implementation design of CIM in ESXi. Please see http://www.claudiokuenzler.com/blog/114/check-esxi-wbem-esxi-4.1-user-authorization for more information (also look at the comments).
My service status says OK eventhough there should be a warning. When I run the script, it does correctly give a warning about one of my power supply being unplugged.
If there's a difference in Nagios output and the manually launched script output, then you should check your Nagios config.
Hello, I used the script for SUN Fire X4540. The script detect the SUN server with SN, not the model. But I dont know how to interpret the disk and power supply status. For a test I cut a power-supply, but nothing changed in output-file. Thanks Wolfgang Here ist the output: 20121024 08:17:26 Connection to https://10.3.21.2 20121024 08:17:26 Check classe OMC_SMASHFirmwareIdentity 20121024 08:17:26 Element Name = System BIOS 20121024 08:17:26 VersionString = 080014 20121024 08:17:26 Check classe CIM_Chassis 20121024 08:17:26 Element Name = Chassis 20121024 08:17:26 Manufacturer = Sun Microsystems 20121024 08:17:26 SerialNumber = 0905AMR011 20121024 08:17:26 Element Op Status = 0 20121024 08:17:26 Element Name = Chassis 20121024 08:17:26 Manufacturer = Sun Microsystems 20121024 08:17:26 SerialNumber = 0000000-0000000000 20121024 08:17:26 Element Op Status = 0 20121024 08:17:26 Check classe CIM_Card 20121024 08:17:27 Element Name = Motherboard 20121024 08:17:27 Element Op Status = 0 20121024 08:17:27 Check classe CIM_ComputerSystem 20121024 08:17:27 Element Name = modular enclosure of localhost.kli-ma 20121024 08:17:27 Element Name = System Board 7:0 20121024 08:17:27 Element Op Status = 0 20121024 08:17:27 Element Name = localhost.kli-ma 20121024 08:17:27 Element Name = Hardware Management Controller (Node 0) 20121024 08:17:27 Element Op Status = 0 20121024 08:17:27 Check classe CIM_NumericSensor 20121024 08:17:28 Element Name = Fan Device 9 ft4.f1.speed 20121024 08:17:28 sensorType = 5 - Tachometer 20121024 08:17:28 BaseUnits = 19 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 5800.000000 20121024 08:17:28 Lower Threshold Non Critical = 4000.000000 20121024 08:17:28 Upper Threshold Non Critical = 8500.000000 20121024 08:17:28 Lower Threshold Critical = 3000.000000 20121024 08:17:28 Upper Threshold Critical = 9000.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Fan Device 8 ft4.f0.speed 20121024 08:17:28 sensorType = 5 - Tachometer 20121024 08:17:28 BaseUnits = 19 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 5700.000000 20121024 08:17:28 Lower Threshold Non Critical = 4000.000000 20121024 08:17:28 Upper Threshold Non Critical = 8500.000000 20121024 08:17:28 Lower Threshold Critical = 3000.000000 20121024 08:17:28 Upper Threshold Critical = 9000.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Fan Device 7 ft3.f1.speed 20121024 08:17:28 sensorType = 5 - Tachometer 20121024 08:17:28 BaseUnits = 19 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 5700.000000 20121024 08:17:28 Lower Threshold Non Critical = 4000.000000 20121024 08:17:28 Upper Threshold Non Critical = 8500.000000 20121024 08:17:28 Lower Threshold Critical = 3000.000000 20121024 08:17:28 Upper Threshold Critical = 9000.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Fan Device 6 ft3.f0.speed 20121024 08:17:28 sensorType = 5 - Tachometer 20121024 08:17:28 BaseUnits = 19 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 5700.000000 20121024 08:17:28 Lower Threshold Non Critical = 4000.000000 20121024 08:17:28 Upper Threshold Non Critical = 8500.000000 20121024 08:17:28 Lower Threshold Critical = 3000.000000 20121024 08:17:28 Upper Threshold Critical = 9000.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Fan Device 5 ft2.f1.speed 20121024 08:17:28 sensorType = 5 - Tachometer 20121024 08:17:28 BaseUnits = 19 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 5800.000000 20121024 08:17:28 Lower Threshold Non Critical = 4000.000000 20121024 08:17:28 Upper Threshold Non Critical = 8500.000000 20121024 08:17:28 Lower Threshold Critical = 3000.000000 20121024 08:17:28 Upper Threshold Critical = 9000.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Fan Device 4 ft2.f0.speed 20121024 08:17:28 sensorType = 5 - Tachometer 20121024 08:17:28 BaseUnits = 19 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 5800.000000 20121024 08:17:28 Lower Threshold Non Critical = 4000.000000 20121024 08:17:28 Upper Threshold Non Critical = 8500.000000 20121024 08:17:28 Lower Threshold Critical = 3000.000000 20121024 08:17:28 Upper Threshold Critical = 9000.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Fan Device 3 ft1.f1.speed 20121024 08:17:28 sensorType = 5 - Tachometer 20121024 08:17:28 BaseUnits = 19 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 5700.000000 20121024 08:17:28 Lower Threshold Non Critical = 4000.000000 20121024 08:17:28 Upper Threshold Non Critical = 8500.000000 20121024 08:17:28 Lower Threshold Critical = 3000.000000 20121024 08:17:28 Upper Threshold Critical = 9000.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Fan Device 2 ft1.f0.speed 20121024 08:17:28 sensorType = 5 - Tachometer 20121024 08:17:28 BaseUnits = 19 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 5800.000000 20121024 08:17:28 Lower Threshold Non Critical = 4000.000000 20121024 08:17:28 Upper Threshold Non Critical = 8500.000000 20121024 08:17:28 Lower Threshold Critical = 3000.000000 20121024 08:17:28 Upper Threshold Critical = 9000.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Fan Device 1 ft0.f1.speed 20121024 08:17:28 sensorType = 5 - Tachometer 20121024 08:17:28 BaseUnits = 19 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 5800.000000 20121024 08:17:28 Lower Threshold Non Critical = 4000.000000 20121024 08:17:28 Upper Threshold Non Critical = 8500.000000 20121024 08:17:28 Lower Threshold Critical = 3000.000000 20121024 08:17:28 Upper Threshold Critical = 9000.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Fan Device 0 ft0.f0.speed 20121024 08:17:28 sensorType = 5 - Tachometer 20121024 08:17:28 BaseUnits = 19 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 5800.000000 20121024 08:17:28 Lower Threshold Non Critical = 4000.000000 20121024 08:17:28 Upper Threshold Non Critical = 8500.000000 20121024 08:17:28 Lower Threshold Critical = 3000.000000 20121024 08:17:28 Upper Threshold Critical = 9000.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 io.v_+1v2 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 1.210000 20121024 08:17:28 Lower Threshold Non Critical = 1.080000 20121024 08:17:28 Upper Threshold Non Critical = 1.320000 20121024 08:17:28 Lower Threshold Critical = 1.020000 20121024 08:17:28 Upper Threshold Critical = 1.380000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 io.v_+1v8 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 1.830000 20121024 08:17:28 Lower Threshold Non Critical = 1.620000 20121024 08:17:28 Upper Threshold Non Critical = 1.970000 20121024 08:17:28 Lower Threshold Critical = 1.530000 20121024 08:17:28 Upper Threshold Critical = 2.060000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 io.v_+1v4 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 1.400000 20121024 08:17:28 Lower Threshold Non Critical = 1.260000 20121024 08:17:28 Upper Threshold Non Critical = 1.530000 20121024 08:17:28 Lower Threshold Critical = 1.180000 20121024 08:17:28 Upper Threshold Critical = 1.600000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 io.v_+1v5 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 1.510000 20121024 08:17:28 Lower Threshold Non Critical = 1.340000 20121024 08:17:28 Upper Threshold Non Critical = 1.640000 20121024 08:17:28 Lower Threshold Critical = 1.270000 20121024 08:17:28 Upper Threshold Critical = 1.710000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 io.v_+5v_disk 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 5.160000 20121024 08:17:28 Lower Threshold Non Critical = 4.480000 20121024 08:17:28 Upper Threshold Non Critical = 5.490000 20121024 08:17:28 Lower Threshold Critical = 4.240000 20121024 08:17:28 Upper Threshold Critical = 5.730000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 io.v_+12v 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 12.150000 20121024 08:17:28 Lower Threshold Non Critical = 10.770000 20121024 08:17:28 Upper Threshold Non Critical = 13.160000 20121024 08:17:28 Lower Threshold Critical = 10.140000 20121024 08:17:28 Upper Threshold Critical = 13.790000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 io.v_+5v 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 4.940000 20121024 08:17:28 Lower Threshold Non Critical = 4.490000 20121024 08:17:28 Upper Threshold Non Critical = 5.480000 20121024 08:17:28 Lower Threshold Critical = 4.230000 20121024 08:17:28 Upper Threshold Critical = 5.740000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 io.v_+3v3 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 3.350000 20121024 08:17:28 Lower Threshold Non Critical = 2.950000 20121024 08:17:28 Upper Threshold Non Critical = 3.610000 20121024 08:17:28 Lower Threshold Critical = 2.800000 20121024 08:17:28 Upper Threshold Critical = 3.780000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 io.v_+3v3stby 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 3.260000 20121024 08:17:28 Lower Threshold Non Critical = 2.950000 20121024 08:17:28 Upper Threshold Non Critical = 3.610000 20121024 08:17:28 Lower Threshold Critical = 2.800000 20121024 08:17:28 Upper Threshold Critical = 3.780000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 io.v_bat 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 3.080000 20121024 08:17:28 Lower Threshold Non Critical = 2.600000 20121024 08:17:28 Upper Threshold Non Critical = 3.400000 20121024 08:17:28 Lower Threshold Critical = 2.400000 20121024 08:17:28 Upper Threshold Critical = 3.600000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Drive Backplane 0 dbp.t_amb 20121024 08:17:28 sensorType = 2 - Temperature 20121024 08:17:28 BaseUnits = 2 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 21.000000 20121024 08:17:28 Upper Threshold Critical = 33.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 io.front.t_amb 20121024 08:17:28 sensorType = 2 - Temperature 20121024 08:17:28 BaseUnits = 2 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 44.000000 20121024 08:17:28 Upper Threshold Non Critical = 90.000000 20121024 08:17:28 Upper Threshold Critical = 95.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 io.rear.t_amb 20121024 08:17:28 sensorType = 2 - Temperature 20121024 08:17:28 BaseUnits = 2 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 50.000000 20121024 08:17:28 Upper Threshold Non Critical = 90.000000 20121024 08:17:28 Upper Threshold Critical = 95.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Processor 1 p1.v_+0v9 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 0.900000 20121024 08:17:28 Lower Threshold Non Critical = 0.800000 20121024 08:17:28 Upper Threshold Non Critical = 0.980000 20121024 08:17:28 Lower Threshold Critical = 0.750000 20121024 08:17:28 Upper Threshold Critical = 1.030000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Processor 1 p1.v_+1v8 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 1.830000 20121024 08:17:28 Lower Threshold Non Critical = 1.620000 20121024 08:17:28 Upper Threshold Non Critical = 1.970000 20121024 08:17:28 Lower Threshold Critical = 1.520000 20121024 08:17:28 Upper Threshold Critical = 2.060000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Processor 1 p1.t_core 20121024 08:17:28 sensorType = 2 - Temperature 20121024 08:17:28 BaseUnits = 2 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 19.000000 20121024 08:17:28 Upper Threshold Non Critical = 62.000000 20121024 08:17:28 Upper Threshold Critical = 67.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Processor 1 p1.v_vddcore 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 1.080000 20121024 08:17:28 Lower Threshold Non Critical = 0.800000 20121024 08:17:28 Upper Threshold Non Critical = 1.910000 20121024 08:17:28 Lower Threshold Critical = 0.710000 20121024 08:17:28 Upper Threshold Critical = 2.040000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Processor 0 p0.v_+0v9 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 0.900000 20121024 08:17:28 Lower Threshold Non Critical = 0.800000 20121024 08:17:28 Upper Threshold Non Critical = 0.980000 20121024 08:17:28 Lower Threshold Critical = 0.750000 20121024 08:17:28 Upper Threshold Critical = 1.030000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Processor 0 p0.v_+1v8 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 1.830000 20121024 08:17:28 Lower Threshold Non Critical = 1.620000 20121024 08:17:28 Upper Threshold Non Critical = 1.970000 20121024 08:17:28 Lower Threshold Critical = 1.520000 20121024 08:17:28 Upper Threshold Critical = 2.060000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Processor 0 p0.v_vddcore 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 1.080000 20121024 08:17:28 Lower Threshold Non Critical = 0.800000 20121024 08:17:28 Upper Threshold Non Critical = 1.910000 20121024 08:17:28 Lower Threshold Critical = 0.710000 20121024 08:17:28 Upper Threshold Critical = 2.040000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Processor 0 p0.t_core 20121024 08:17:28 sensorType = 2 - Temperature 20121024 08:17:28 BaseUnits = 2 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 19.000000 20121024 08:17:28 Upper Threshold Non Critical = 62.000000 20121024 08:17:28 Upper Threshold Critical = 67.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Processor Module 0 proc.rear.t_amb 20121024 08:17:28 sensorType = 2 - Temperature 20121024 08:17:28 BaseUnits = 2 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 32.000000 20121024 08:17:28 Upper Threshold Non Critical = 90.000000 20121024 08:17:28 Upper Threshold Critical = 95.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Processor Module 0 proc.front.t_amb 20121024 08:17:28 sensorType = 2 - Temperature 20121024 08:17:28 BaseUnits = 2 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 29.000000 20121024 08:17:28 Upper Threshold Non Critical = 90.000000 20121024 08:17:28 Upper Threshold Critical = 95.000000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 sys.v_+1v2ht 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 1.200000 20121024 08:17:28 Lower Threshold Non Critical = 1.000000 20121024 08:17:28 Upper Threshold Non Critical = 1.500000 20121024 08:17:28 Lower Threshold Critical = 0.800000 20121024 08:17:28 Upper Threshold Critical = 1.690000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 sys.v_+12v 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 12.090000 20121024 08:17:28 Lower Threshold Non Critical = 10.770000 20121024 08:17:28 Upper Threshold Non Critical = 13.160000 20121024 08:17:28 Lower Threshold Critical = 10.140000 20121024 08:17:28 Upper Threshold Critical = 13.790000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = Processor Module 0 bat.v_bat 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 3.080000 20121024 08:17:28 Lower Threshold Non Critical = 2.600000 20121024 08:17:28 Upper Threshold Non Critical = 3.400000 20121024 08:17:28 Lower Threshold Critical = 2.400000 20121024 08:17:28 Upper Threshold Critical = 3.600000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 sys.v_+3v3 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 3.280000 20121024 08:17:28 Lower Threshold Non Critical = 2.950000 20121024 08:17:28 Upper Threshold Non Critical = 3.610000 20121024 08:17:28 Lower Threshold Critical = 2.800000 20121024 08:17:28 Upper Threshold Critical = 3.780000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = System Board 0 sys.v_+3v3stby 20121024 08:17:28 sensorType = 3 - Voltage 20121024 08:17:28 BaseUnits = 5 20121024 08:17:28 Scaled by = 0.010000 20121024 08:17:28 Current Reading = 3.250000 20121024 08:17:28 Lower Threshold Non Critical = 2.950000 20121024 08:17:28 Upper Threshold Non Critical = 3.610000 20121024 08:17:28 Lower Threshold Critical = 2.800000 20121024 08:17:28 Upper Threshold Critical = 3.780000 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Check classe CIM_Memory 20121024 08:17:28 Element Name = CPU 1 Level-1 Cache 20121024 08:17:28 Element Op Status = 0 20121024 08:17:28 Element Name = CPU 1 Level-2 Cache 20121024 08:17:28 Element Op Status = 0 20121024 08:17:28 Element Name = CPU 1 Level-3 Cache 20121024 08:17:28 Element Op Status = 0 20121024 08:17:28 Element Name = CPU 2 Level-1 Cache 20121024 08:17:28 Element Op Status = 0 20121024 08:17:28 Element Name = CPU 2 Level-2 Cache 20121024 08:17:28 Element Op Status = 0 20121024 08:17:28 Element Name = CPU 2 Level-3 Cache 20121024 08:17:28 Element Op Status = 0 20121024 08:17:28 Element Name = Memory 20121024 08:17:28 Check classe CIM_Processor 20121024 08:17:28 Element Name = CPU 1 20121024 08:17:28 Family = 138 20121024 08:17:28 CurrentClockSpeed = 2300MHz 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Element Name = CPU 2 20121024 08:17:28 Family = 138 20121024 08:17:28 CurrentClockSpeed = 2300MHz 20121024 08:17:28 Element Op Status = 2 20121024 08:17:28 Check classe CIM_RecordLog 20121024 08:17:29 Element Name = IPMI SEL 20121024 08:17:29 Element Op Status = 2 20121024 08:17:29 Check classe OMC_DiscreteSensor 20121024 08:17:32 Element Name = Disk or Disk Bay 47 hdd47.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 47 hdd47.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 47 hdd47.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 47 hdd47.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 47 hdd47.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 47 hdd47.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 47 hdd47.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 46 hdd46.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 46 hdd46.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 46 hdd46.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 46 hdd46.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 46 hdd46.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 46 hdd46.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 46 hdd46.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 45 hdd45.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 45 hdd45.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 45 hdd45.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 45 hdd45.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 45 hdd45.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 45 hdd45.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 45 hdd45.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 44 hdd44.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 44 hdd44.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 44 hdd44.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 44 hdd44.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 44 hdd44.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 44 hdd44.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 44 hdd44.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 43 hdd43.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 43 hdd43.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 43 hdd43.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 43 hdd43.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 43 hdd43.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 43 hdd43.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 43 hdd43.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 42 hdd42.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 42 hdd42.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 42 hdd42.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 42 hdd42.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 42 hdd42.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 42 hdd42.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 42 hdd42.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 41 hdd41.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 41 hdd41.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 41 hdd41.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 41 hdd41.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 41 hdd41.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 41 hdd41.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 41 hdd41.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 40 hdd40.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 40 hdd40.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 40 hdd40.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 40 hdd40.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 40 hdd40.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 40 hdd40.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 40 hdd40.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 39 hdd39.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 39 hdd39.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 39 hdd39.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 39 hdd39.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 39 hdd39.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 39 hdd39.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 39 hdd39.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 38 hdd38.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 38 hdd38.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 38 hdd38.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 38 hdd38.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 38 hdd38.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 38 hdd38.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 38 hdd38.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 37 hdd37.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 37 hdd37.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 37 hdd37.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 37 hdd37.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 37 hdd37.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 37 hdd37.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 37 hdd37.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 36 hdd36.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 36 hdd36.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 36 hdd36.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 36 hdd36.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 36 hdd36.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 36 hdd36.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 36 hdd36.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 35 hdd35.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 35 hdd35.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 35 hdd35.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 35 hdd35.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 35 hdd35.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 35 hdd35.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 35 hdd35.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 34 hdd34.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 34 hdd34.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 34 hdd34.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 34 hdd34.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 34 hdd34.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 34 hdd34.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 34 hdd34.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 33 hdd33.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 33 hdd33.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 33 hdd33.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 33 hdd33.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 33 hdd33.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 33 hdd33.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 33 hdd33.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 32 hdd32.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 32 hdd32.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 32 hdd32.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 32 hdd32.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 32 hdd32.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 32 hdd32.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 32 hdd32.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 31 hdd31.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 31 hdd31.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 31 hdd31.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 31 hdd31.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 31 hdd31.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 31 hdd31.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 31 hdd31.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 30 hdd30.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 30 hdd30.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 30 hdd30.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 30 hdd30.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 30 hdd30.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 30 hdd30.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 30 hdd30.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 29 hdd29.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 29 hdd29.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 29 hdd29.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 29 hdd29.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 29 hdd29.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 29 hdd29.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 29 hdd29.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 28 hdd28.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 28 hdd28.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 28 hdd28.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 28 hdd28.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 28 hdd28.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 28 hdd28.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 28 hdd28.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 27 hdd27.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 27 hdd27.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 27 hdd27.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 27 hdd27.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 27 hdd27.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 27 hdd27.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 27 hdd27.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 26 hdd26.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 26 hdd26.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 26 hdd26.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 26 hdd26.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 26 hdd26.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 26 hdd26.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 26 hdd26.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 25 hdd25.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 25 hdd25.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 25 hdd25.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 25 hdd25.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 25 hdd25.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 25 hdd25.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 25 hdd25.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 24 hdd24.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 24 hdd24.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 24 hdd24.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 24 hdd24.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 24 hdd24.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 24 hdd24.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 24 hdd24.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 23 hdd23.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 23 hdd23.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 23 hdd23.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 23 hdd23.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 23 hdd23.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 23 hdd23.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 23 hdd23.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 22 hdd22.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 22 hdd22.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 22 hdd22.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 22 hdd22.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 22 hdd22.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 22 hdd22.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 22 hdd22.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 21 hdd21.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 21 hdd21.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 21 hdd21.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 21 hdd21.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 21 hdd21.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 21 hdd21.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 21 hdd21.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 20 hdd20.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 20 hdd20.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 20 hdd20.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 20 hdd20.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 20 hdd20.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 20 hdd20.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 20 hdd20.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 19 hdd19.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 19 hdd19.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 19 hdd19.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 19 hdd19.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 19 hdd19.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 19 hdd19.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 19 hdd19.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 18 hdd18.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 18 hdd18.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 18 hdd18.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 18 hdd18.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 18 hdd18.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 18 hdd18.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 18 hdd18.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 17 hdd17.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 17 hdd17.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 17 hdd17.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 17 hdd17.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 17 hdd17.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 17 hdd17.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 17 hdd17.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 16 hdd16.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 16 hdd16.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 16 hdd16.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 16 hdd16.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 16 hdd16.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 16 hdd16.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 16 hdd16.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 15 hdd15.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 15 hdd15.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 15 hdd15.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 15 hdd15.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 15 hdd15.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 15 hdd15.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 15 hdd15.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 14 hdd14.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 14 hdd14.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 14 hdd14.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 14 hdd14.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 14 hdd14.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 14 hdd14.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 14 hdd14.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 13 hdd13.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 13 hdd13.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 13 hdd13.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 13 hdd13.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 13 hdd13.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 13 hdd13.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 13 hdd13.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 12 hdd12.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 12 hdd12.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 12 hdd12.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 12 hdd12.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 12 hdd12.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 12 hdd12.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 12 hdd12.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 11 hdd11.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 11 hdd11.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 11 hdd11.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 11 hdd11.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 11 hdd11.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 11 hdd11.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 11 hdd11.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 10 hdd10.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 10 hdd10.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 10 hdd10.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 10 hdd10.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 10 hdd10.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 10 hdd10.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 10 hdd10.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 9 hdd9.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 9 hdd9.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 9 hdd9.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 9 hdd9.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 9 hdd9.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 9 hdd9.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 9 hdd9.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 8 hdd8.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 8 hdd8.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 8 hdd8.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 8 hdd8.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 8 hdd8.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 8 hdd8.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 8 hdd8.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 7 hdd7.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 7 hdd7.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 7 hdd7.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 7 hdd7.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 7 hdd7.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 7 hdd7.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 7 hdd7.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 6 hdd6.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 6 hdd6.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 6 hdd6.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 6 hdd6.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 6 hdd6.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 6 hdd6.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 6 hdd6.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 5 hdd5.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 5 hdd5.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 5 hdd5.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 5 hdd5.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 5 hdd5.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 5 hdd5.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 5 hdd5.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 4 hdd4.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 4 hdd4.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 4 hdd4.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 4 hdd4.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 4 hdd4.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 4 hdd4.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 4 hdd4.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 3 hdd3.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 3 hdd3.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 3 hdd3.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 3 hdd3.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 3 hdd3.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 3 hdd3.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 3 hdd3.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 2 hdd2.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 2 hdd2.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 2 hdd2.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 2 hdd2.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 2 hdd2.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 2 hdd2.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 2 hdd2.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 1 hdd1.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 1 hdd1.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 1 hdd1.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 1 hdd1.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 1 hdd1.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 1 hdd1.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 1 hdd1.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 0 hdd0.hba.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 0 hdd0.hba.state 1: Predictive Failure 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 0 hdd0.hba.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 0 hdd0.state 1: Drive Present 20121024 08:17:32 Element Name = Disk or Disk Bay 0 hdd0.state 1: Drive Fault 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Disk or Disk Bay 0 hdd0.state 1: Hot Spare 20121024 08:17:32 Element Name = Disk or Disk Bay 0 hdd0.state 1: Rebuild In Progress 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = Power Supply 2 ps2.prsnt 1 20121024 08:17:32 Element Name = Power Supply 2 ps2.pwrok 1 20121024 08:17:32 Element Name = Power Supply 2 ps2.vinok 1 20121024 08:17:32 Element Name = Power Supply 1 ps1.prsnt 1 20121024 08:17:32 Element Name = Power Supply 0 ps0.prsnt 1 20121024 08:17:32 Element Name = Power Supply 1 ps1.pwrok 1 20121024 08:17:32 Element Name = Power Supply 1 ps1.vinok 1 20121024 08:17:32 Element Name = Power Supply 0 ps0.pwrok 1 20121024 08:17:32 Element Name = Power Supply 0 ps0.vinok 1 20121024 08:17:32 Element Name = Cooling Unit 4 ft4.prsnt 1 20121024 08:17:32 Element Name = Cooling Unit 3 ft3.prsnt 1 20121024 08:17:32 Element Name = Cooling Unit 2 ft2.prsnt 1 20121024 08:17:32 Element Name = Cooling Unit 1 ft1.prsnt 1 20121024 08:17:32 Element Name = Cooling Unit 0 ft0.prsnt 1 20121024 08:17:32 Element Name = Processor 1 p1.hot 1 20121024 08:17:32 Element Name = Processor 1 p1.prsnt 1 20121024 08:17:32 Element Name = Processor 0 p0.hot 1 20121024 08:17:32 Element Name = Processor 0 p0.prsnt 1 20121024 08:17:32 Element Name = Processor Module 2 proc.prsnt 1 20121024 08:17:32 Element Name = System Board 0 sys.locate.btn 1 20121024 08:17:32 Element Name = System Board 0 sys.acpi 1: S0/G0: working 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = System Board 0 sys.acpi 1: S5/G2: soft-off 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = System Board 0 sys.reset.btn 1: Reset Button pressed 20121024 08:17:32 Element Name = System Chassis 0 sys.nmi 1: NMI/Diag Interrupt 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Element Name = System Chassis 0 sys.intsw 1: General Chassis intrusion 20121024 08:17:32 Element Op Status = 2 20121024 08:17:32 Check classe OMC_Fan 20121024 08:17:34 Element Name = ft4.f1.speed 20121024 08:17:34 Element Op Status = 2 20121024 08:17:34 Element Name = ft4.f0.speed 20121024 08:17:34 Element Op Status = 2 20121024 08:17:34 Element Name = ft3.f1.speed 20121024 08:17:34 Element Op Status = 2 20121024 08:17:34 Element Name = ft3.f0.speed 20121024 08:17:34 Element Op Status = 2 20121024 08:17:34 Element Name = ft2.f1.speed 20121024 08:17:34 Element Op Status = 2 20121024 08:17:34 Element Name = ft2.f0.speed 20121024 08:17:34 Element Op Status = 2 20121024 08:17:34 Element Name = ft1.f1.speed 20121024 08:17:34 Element Op Status = 2 20121024 08:17:34 Element Name = ft1.f0.speed 20121024 08:17:34 Element Op Status = 2 20121024 08:17:34 Element Name = ft0.f1.speed 20121024 08:17:34 Element Op Status = 2 20121024 08:17:34 Element Name = ft0.f0.speed 20121024 08:17:34 Element Op Status = 2 20121024 08:17:34 Check classe OMC_PowerSupply 20121024 08:17:34 Element Name = Power Supply 0 20121024 08:17:34 Element Op Status = 0 20121024 08:17:34 Element Name = Power Supply 1 20121024 08:17:34 Element Op Status = 0 20121024 08:17:34 Element Name = Power Supply 2 20121024 08:17:34 Element Op Status = 0 20121024 08:17:34 Check classe VMware_StorageExtent 20121024 08:17:35 Check classe VMware_Controller 20121024 08:17:35 Check classe VMware_StorageVolume 20121024 08:17:35 Check classe VMware_Battery 20121024 08:17:35 Check classe VMware_SASSATAPort OK - Server: Sun Microsystems 0000000-0000000000 System BIOS: 080014 2008-11-04
Looks like a hardware incompatibility issue to me. The Element Operating Status' of the Power Supplies show a value of 0. Here to compare with a Dell server: 20121026 15:51:33 Check classe OMC_PowerSupply 20121026 15:51:34 Element Name = Power Supply 1 20121026 15:51:34 Element Op Status = 2 20121026 15:51:34 Element Name = Power Supply 2 20121026 15:51:34 Element Op Status = 2 If the disconnected Power Supply doesn't show up in vSphere either, then your hardware is definitely not "ready" for the CIM API.
I have this running on about 8 hosts and 6 of them are not reporting errors and it actually caught a motherboard error we happened to miss in the past. However I am getting the error "WARNING Memory" on two hosts and have absolutely no idea what it means. The hosts are not out of memory, there are not any errors in ESXi that I can find. So besides this error, it appears to be working correctly. Hopefully I can find a solution to the Memory error so I can clear up Nagios instead of having two yellow servers. If anyone has any ideas feel free to let me know.
There can be several reasons for this error. Please send me the verbose output (-v parameter). You'll find a contact form on my website.
you have to set the correct pythonpath PYTHONPATH="" ./check_esxi_hardware.py --host=https://host ......
If I try to run either a) ./check_esxi_hardware.py https://esxi-server-ip username mypass hw_type [verbose] or b) ./check_esxi_hardware.py -H esxi-server-ip -U username -P mypass [-V -i -v -p -I xx] I get an error saying './check_esxi_hardware.py: command not found' I have it downloaded and I am in the folder that contains the file. What am I doing wrong? p.s. I do have python and pywbem
You can't copy the usage line one to one. You must enter your own information... See examples on the documentation website.
With the openSUSE Update from 11.3 to 11.4 python was updated from 2.6 to 2.7. Now I get these errors: Traceback (most recent call last): File "./check_esxi_hardware.py", line 544, in instance_list = wbemclient.EnumerateInstances(classe) File "/usr/lib/python2.7/site-packages/pywbem/cim_operations.py", line 404, in EnumerateInstances **params) File "/usr/lib/python2.7/site-packages/pywbem/cim_operations.py", line 168, in imethodcall verify_callback = self.verify_callback) File "/usr/lib/python2.7/site-packages/pywbem/cim_http.py", line 184, in wbem_request h.putheader('Content-length', len(data)) File "/usr/lib64/python2.7/httplib.py", line 924, in putheader str = '%s: %s' % (header, 'rnt'.join(values)) TypeError: sequence item 0: expected string, int found
You might have to recompile pywbem to the new python version.
The plugin works fine with ESXi 4.1 (the new licensed version). Tested with IBM xSeries and HP Proliant. If you do not want to use the root account, but a dedicated account for monitoring, you can try this steps: in vSphere - create a nagios user - add this user to the root group - Assign the "No access" role to the nagios user Youll'have the right to access from the plugin, but the nagios user will not be able to access with the vsphere client, the console and, SSH.
same error here but i suspect a perl library update to have it broken because it worked before. here the verbose log i get on a cisco server 20110824 09:53:36 Connection to https://10.47.5.251 20110824 09:53:36 Check classe OMC_SMASHFirmwareIdentity 20110824 09:53:36 Element Name = System BIOS 20110824 09:53:36 VersionString = C200.1.3.1c.0.021920110242 20110824 09:53:36 Check classe CIM_Chassis 20110824 09:53:37 Element Name = Chassis 20110824 09:53:37 Manufacturer = Cisco Systems Inc 20110824 09:53:37 SerialNumber = QCI1424A0WS 20110824 09:53:37 Model = R210-2121605W 20110824 09:53:37 Element Op Status = 0 20110824 09:53:37 Check classe CIM_Card 20110824 09:53:37 Element Name = Server Blade 20110824 09:53:37 SerialNumber = QCI1423A2CW 20110824 09:53:37 Element Op Status = 0 20110824 09:53:37 Check classe CIM_ComputerSystem 20110824 09:53:38 Element Name = System Board 7:0 20110824 09:53:38 Element Op Status = 0 20110824 09:53:38 Element Name = System Board 7:24 20110824 09:53:38 Element Op Status = 0 20110824 09:53:38 Element Name = System Board 7:29 20110824 09:53:38 Element Op Status = 0 20110824 09:53:38 Element Name = System Board 7:30 20110824 09:53:38 Element Op Status = 0 20110824 09:53:38 Element Name = System Board 7:31 20110824 09:53:38 Element Op Status = 0 20110824 09:53:38 Element Name = System Board 7:32 20110824 09:53:38 Element Op Status = 0 20110824 09:53:38 Element Name = System Board 7:33 20110824 09:53:38 Element Op Status = 0 20110824 09:53:38 Element Name = Add-in Card 11:0 20110824 09:53:38 Element Op Status = 0 20110824 09:53:38 Element Name = Add-in Card 11:1 20110824 09:53:38 Element Op Status = 0 20110824 09:53:38 Element Name = esx01.sab.be 20110824 09:53:38 Element Name = Hardware Management Controller (Node 0) 20110824 09:53:38 Element Op Status = 0 20110824 09:53:38 Element Name = Controller 0 (LSI MegaRAID SAS 9261-8i) 20110824 09:53:38 Element Op Status = 2 20110824 09:53:38 Check classe CIM_NumericSensor Traceback (most recent call last): File "check_esxi_hardware.py", line 493, in ? instance_list = wbemclient.EnumerateInstances(classe) File "/usr/lib/python2.4/site-packages/pywbem/cim_operations.py", line 403, in EnumerateInstances ClassName = CIMClassName(ClassName), File "/usr/lib/python2.4/site-packages/pywbem/cim_operations.py", line 178, in imethodcall reply_dom = minidom.parseString(resp_xml) File "/usr/lib/python2.4/site-packages/_xmlplus/dom/minidom.py", line 1925, in parseString return expatbuilder.parseString(string) File "/usr/lib/python2.4/site-packages/_xmlplus/dom/expatbuilder.py", line 942, in parseString return builder.parseString(string) File "/usr/lib/python2.4/site-packages/_xmlplus/dom/expatbuilder.py", line 223, in parseString parser.Parse(string, True) xml.parsers.expat.ExpatError: not well-formed (invalid token): line 2759, column 7
Its run softly and nice on dell systems but on Sun Blade X6440 I have this error using unknown or auto ... File "./check_esxi_hardware.py", line 477, in c=wbemclient.EnumerateInstances('CIM_Chassis') File "/usr/local/lib/python2.6/site-packages/pywbem/cim_operations.py", line 404, in EnumerateInstances **params) File "/usr/local/lib/python2.6/site-packages/pywbem/cim_operations.py", line 178, in imethodcall reply_dom = minidom.parseString(resp_xml) File "/usr/local/lib/python2.6/xml/dom/minidom.py", line 1928, in parseString return expatbuilder.parseString(string) File "/usr/local/lib/python2.6/xml/dom/expatbuilder.py", line 940, in parseString return builder.parseString(string) File "/usr/local/lib/python2.6/xml/dom/expatbuilder.py", line 223, in parseString parser.Parse(string, True) xml.parsers.expat.ExpatError: not well-formed (invalid token): line 199, column 17
You must be logged in to submit a review.
To:
From: