Quantcast
Channel: VMware Communities : Discussion List - ESXi
Viewing all articles
Browse latest Browse all 8132

ESXi 4.1 Update 2 Host Battery Status does not detect BBU Failure

$
0
0

We have several hosts running on Cisco UCS C210M2 with LSI MegaRaid SAS 9261-8i and ESXi 4.1 Build 582267. We are observing in Vsphere Client Hardware Status the "Battery" status is Normal and the respective "Host Battery Status" alarm is NOT raised on this host when in fact the BBU has failed and marked as "needs to be replaced"

 

Only after enabling SSH and uploading the MegaCLI utility and manually querying the BBU status we are able to conclude the BBU is bad. This NOT alarmed condition of the BBU in turn puts the Virtual Disk's Write Cache policy in to Write Through mode impacting IO performance.

 

Has anyone using the LSI MegaRaid with ESXi come across such BBU failure that is not detected by VMWare ?

 

Here is what the MegaCli reports in this condition

 

/bin # ./MegaCli -AdpBbuCmd -GetBbuStatus -aALL
BBU status for Adapter: 0
BatteryType: iBBU
Voltage: 4018 mV
Current: 0 mA
Temperature: 30 C
BBU Firmware Status:
Charging Status              : None
Voltage                      : OK
Temperature                  : OK
Learn Cycle Requested            : No
Learn Cycle Active           : No
Learn Cycle Status           : OK
Learn Cycle Timeout          : No
I2c Errors Detected          : No
Battery Pack Missing         : No
Battery Replacement required : Yes
Remaining Capacity Low       : Yes
Periodic Learn Required      : No
Transparent Learn            : No
Battery state:
GasGuageStatus:
Fully Discharged        : No
Fully Charged           : Yes
Discharging             : Yes
Initialized             : Yes
Remaining Time Alarm    : No
Remaining Capacity Alarm: No
Discharge Terminated    : No
Over Temperature        : No
Charging Terminated     : No
Over Charged            : No
Relative State of Charge: 96 %
Charger System State: 49168
Charger System Ctrl: 0
Charging current: 0 mA
Absolute state of charge: 29 %
Max Error: 2 %
Exit Code: 0x00

 

If I query the VMWare_HHRCBattery CIM Class there is no indication that the battery is bad

 

~$ date;wbemcli ei -noverify 'https://root@esxi-host.com:5989/root/cimv2:VMware_HHRCBattery//root@esxi-host.com:5989/root/cimv2:VMware_HHRCBattery'

Wed May  9 15:06:53 EDT 2012

Enter password:

esxi-host.com:5989/root/cimv2:VMware_HHRCBattery.CreationClassName="VMware_HHRCBattery",DeviceID="vmwControllerBattery0",SystemCreationClassName="OMC_UnitaryComputerSystem",SystemName="dc5fdc64-9cad-11e0-bfac-e8b7487c201c" CardType=2,TransitioningToState=12,SystemName="dc5fdc64-9cad-11e0-bfac-e8b7487c201c",SystemCreationClassName="OMC_UnitaryComputerSystem",RequestedState=11,OperationalStatus=2,HealthState=5,EnabledState=2,EnabledDefault=2,ElementName="Battery on Controller 0 ",DeviceID="vmwControllerBattery0",CreationClassName="VMware_HHRCBattery",Caption="Battery on Controller 0 ",BatteryStatus=3,RemainingCapacityMaxError=,RemainingCapacity=,MaxRechargeCount=,RechargeCount=,MaxRechargeTime=,ExpectedLife=,TimeToFullCharge=,SmartBatteryVersion=,DesignVoltage=,FullChargeCapacity=,DesignCapacity=,Chemistry=,EstimatedChargeRemaining=,EstimatedRunTime=,TimeOnBattery=,LocationIndicator=,MaxQuiesceTime=,AdditionalAvailability=,IdentifyingDescriptions=,TotalPowerOnHours=,PowerOnHours=,OtherIdentifyingInfo=,ErrorCleared=,ErrorDescription=,LastErrorCode=,StatusInfo=,Availability=,PowerManagementCapabilities=,PowerManagementSupported=,Generation=,Description=,InstanceID=,InstallDate=,Name=,StatusDescriptions=,Status=,PrimaryStatus=,DetailedStatus=,OperatingStatus=,CommunicationStatus=,OtherEnabledState=,TimeOfLastStateChange=,AvailableRequestedStates=,RatedMaxOutputPower=,OutputPowerUnits=,IsACOutput=

 

I'm assuming this CIM class is used to trigger the built in "Host battery status" alarm anyone know for sure ?


Viewing all articles
Browse latest Browse all 8132

Trending Articles