Hello!
esxi with installed lsi cim provider...
Sensors show normal state of raid
PyWBEM returns
Controller 500605B0048F6290 (Intel (R) RAID Controller RS2BL080) = 2
RAID 10 StorageVolume Logical Volume 500605B0048F6290_0 on controller 500605B0048F6290, Drives( - OPTIMAL = 2
Battery 5583 on Controller 500605B0048F6290 = 2
Port 0 on Controller 500605B0048F6290 = 2
Port 1 on Controller 500605B0048F6290 = 2
Port 2 on Controller 500605B0048F6290 = 2
Port 3 on Controller 500605B0048F6290 = 2
I have decided to test a hard drive chrashing from raid array.
PyWBEM returns
Controller 500605B0048F6290 (Intel (R) RAID Controller RS2BL080) = 6
After raid rebuilding status of storage in vsphere cllient is normal
But PyWBEM returns
Controller 500605B0048F6290 (Intel (R) RAID Controller RS2BL080) = 3
RAID 10 StorageVolume Logical Volume 500605B0048F6290_0 on controller 500605B0048F6290, Drives( - OPTIMAL = 2
Battery 5583 on Controller 500605B0048F6290 = 2
Port 0 on Controller 500605B0048F6290 = 2
Port 1 on Controller 500605B0048F6290 = 2
Port 2 on Controller 500605B0048F6290 = 2
Port 3 on Controller 500605B0048F6290 = 2
There is description of element statuses (lsi)
[Description (
"Indicates the current statuses of the element. Various "
"operational statuses are defined. Many of the "
"enumeration\'s values are self-explanatory. However, a "
"few are not and are described here in more detail. \n"
"\"Stressed\" indicates that the element is functioning, "
"but needs attention. Examples of \"Stressed\" states are "
"overload, overheated, and so on. \n"
"\"Predictive Failure\" indicates that an element is "
"functioning nominally but predicting a failure in the "
"near future. \n"
"\"In Service\" describes an element being configured, "
"maintained, cleaned, or otherwise administered. \n"
"\"No Contact\" indicates that the monitoring system has "
"knowledge of this element, but has never been able to "
"establish communications with it. \n"
"\"Lost Communication\" indicates that the ManagedSystem "
"Element is known to exist and has been contacted "
"successfully in the past, but is currently unreachable. \n"
"\"Stopped\" and \"Aborted\" are similar, although the "
"former implies a clean and orderly stop, while the "
"latter implies an abrupt stop where the state and "
"configuration of the element might need to be updated. \n"
"\"Dormant\" indicates that the element is inactive or "
"quiesced. \n"
"\"Supporting Entity in Error\" indicates that this "
"element might be \"OK\" but that another element, on "
"which it is dependent, is in error. An example is a "
"network service or endpoint that cannot function due to "
"lower-layer networking problems. \n"
"\"Completed\" indicates that the element has completed "
"its operation. This value should be combined with either "
"OK, Error, or Degraded so that a client can tell if the "
"complete operation Completed with OK (passed), Completed "
"with Error (failed), or Completed with Degraded (the "
"operation finished, but it did not complete OK or did "
"not report an error). \n"
"\"Power Mode\" indicates that the element has additional "
"power model information contained in the Associated "
"PowerManagementService association. \n"
"OperationalStatus replaces the Status property on "
"ManagedSystemElement to provide a consistent approach to "
"enumerations, to address implementation needs for an "
"array property, and to provide a migration path from "
"today\'s environment to the future. This change was not "
"made earlier because it required the deprecated "
"qualifier. Due to the widespread use of the existing "
"Status property in management applications, it is "
"strongly recommended that providers or instrumentation "
"provide both the Status and OperationalStatus "
"properties. Further, the first value of "
"OperationalStatus should contain the primary status for "
"the element. When instrumented, Status (because it is "
"single-valued) should also provide the primary status of "
"the element." ),
ValueMap { "0", "1", "2", "3", "4", "5", "6", "7", "8", "9",
"10", "11", "12", "13", "14", "15", "16", "17", "18",
"..", "0x8000.." },
Values { "Unknown", "Other", "OK", "Degraded", "Stressed",
"Predictive Failure", "Error", "Non-Recoverable Error",
"Starting", "Stopping", "Stopped", "In Service",
"No Contact", "Lost Communication", "Aborted", "Dormant",
"Supporting Entity in Error", "Completed", "Power Mode",
"DMTF Reserved", "Vendor Reserved" },
Why does vshepere client show normal state and pywbem doesn`t...