Hot answers tagged hp
Sure. Look up the "hpssacli" utility. You can parse the output. But the HP management agents eliminate the need to roll-your-own. The server logs this, sends SNMP traps and can email you. What's your ultimate goal?
Old, old, old, old... CentOS 6.2 is old (6.2, 6 December 2011 (kernel 2.6.32-220)) HP StorageWorks MSA70 is old. (End of Life - October 2010) HP Smart Array P800 is old. (End of Life - 2010) So this makes me think that firmware and drivers are also old. E.g. there's no reason to run CentOS 6.2 in 2015... And I'm assuming no effort was made to keep ...
I admire your effort to try to automate this process... However, I don't think it's necessary. You don't have to send a diagnostic report to HP to obtain a warranty part. The IML log or RAID controller status is good enough to open a support case. Some things shouldn't be automated. If drive failures are frequent enough to need to automate the case ...
HP uses special firmware on their drives. Controllers may or may not recognize an non-HP drive. I have had some work but in many cases the drive is not recognized. An HP drive may clearly be a Western Digital or other brand but the controller will fail to "see" the drive as a valid HD In some cases we were able to use the array config utility to get the ...
I have an HP Inkjet that won't print pdf with pcl5 or pcl6, but will print word and excel with postscript. I know this because I just spent 3 hours trying all the different combinations of drivers and documents. I can add to that by noting that a generic Linux inkjet driver on my FC20 box just happened to be postscript and was able to print pdf, while the ...
Another disadvantage (don't know if this applies to all iLO versions and all Proliant models) is that when iLO is on shared port, it cannot communicate with host computer. So server can't even ping its own iLO IP address, although all other devices can - this is because of how this NIC sharing works.
Have you upgraded your firmware? Seems like the v1.8 is pretty old for the P400i controller. Having all drives OK and also fail parity seems like a bug to me. I've had a number of cases where HP shipped older firmware and doing the upgrade fixed parity initialization issues (but I needed to reconstruct the array from scratch) and significantly improved ...
We are missing the "what happened before you asked this question?" information. The HP MSA2324sa is not a new product, so is this a used device? How did you get it? Where did you get it from? All you need to do is create your volumes on the MSA in the SMU. Then map those to the server over controller(s). What type of HBA(s) are you using? Did you reboot? ...
This doesn't work. It's one of the downsides to using a shared ILO port.
The 840 EVOs have very significant problems with data retention Non-enterprise SSDs can be fine, but you need to carefully pick the right ones. My suggestions are about Micron M550/M600/MX200 or Intel 730 series.
Press F10 at POST to enter Intelligent Provisioning and use the HP SSA utility to configure your array. The BIOS ORCA utility is not really supposed to be used for anything other than basic functions. If this doesn't work, you have another issue. See: HP Proliant DL360 G6 Maximum Logical Drives
Only top voted, non community-wiki answers of a minimum length are eligible