Message-ID: <4DDEE580.3040305@catalyst.net.nz>
Date: Fri, 27 May 2011 11:42:56 +1200
From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Greg Smith <greg@2ndquadrant.com>
CC: =?UTF-8?B?R3J6ZWdvcnogSmHFm2tpZXdpY3o=?= <gryzman@gmail.com>,
	postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: serveRAID M5014 SAS
References: <BANLkTi=fE2YCS0Lra42ei1hFrKqXdVk2jA@mail.gmail.com>
	<4DDD81BB.4080801@catalyst.net.nz>	<4DDD85C7.6030109@catalyst.net.nz>
	<BANLkTi=PAymQvudx1eyuuOV9vAAoydan9g@mail.gmail.com>
	<4DDE0E77.6070804@catalyst.net.nz>
	<4DDEDFFF.1060304@2ndquadrant.com>
	<4DDEE0CF.5040800@catalyst.net.nz>
In-Reply-To: <4DDEE0CF.5040800@catalyst.net.nz>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 27/05/11 11:22, Mark Kirkwood wrote:
> On 27/05/11 11:19, Greg Smith wrote:
>> Mark Kirkwood wrote:
>>> You can interrogate the config of the card and the raid 10 array 
>>> using the megaraid cli package - you need to read the (frankly 
>>> terrible) manual to discover which switches to use to determine 
>>> battery and cache status etc. If you email me privately I'll get you 
>>> a link to the relevant docs!
>>
>> That's assuming the MegaCli utility will work against IBM's version 
>> of the card.  They use an LSI chipset for the RAID parts, but I don't 
>> know if the card is so similar that it will talk using that utility 
>> or not.
>
> It does seem to.
>
> Cheers
>
> Mark
>

e.g checking battery status:

root@learn-db2:~# MegaCli64 -AdpBbuCmd -GetBbuStatus -a0

BBU status for Adapter: 0

BatteryType: iBBU
Voltage: 4040 mV
Current: 0 mA
Temperature: 28 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 : No
   Remaining Capacity Low       : No
   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: 99 %
Charger System State: 49168
Charger System Ctrl: 0
Charging current: 0 mA
Absolute state of charge: 99 %
Max Error: 2 %

Exit Code: 0x00


Reminds me of out from DB2 diag commands (years ago...am ok now).