Monday, February 13, 2017

Upgrading iLO3 Firmware on HP DL380 G7 1.88



Just a few notes while upgrading my DL360, DL380, or DL580 G7 to the latest iLO3 firmware, 1.88 as of this writing..
  1. HP, if you're listening, simply make the .bin file available, i.e. ilo3_188.bin, for upgrade; do we really have to unzip the .exe file to extract it from your archive?
  2. Disable the HP post logo in the BIOS, life will be easier to configure iLO from there.
  3. You can't upgrade from iLO3 to iLO4 on a G7.. yet.
  4. If your version of iLO3 is prior to 1.28, you must upgrade to 1.28 before moving to 1.88!
  5. If you'd like to ssh (using their horribly insecure hostkey, kex, cipher and mac - lol) into your iLO3 server, try the following command:

ssh -o HostKeyAlgorithms=ssh-dss -o KexAlgorithms=diffie-hellman-group14-sha1 -o Ciphers=aes128-ctr -o MACs=hmac-sha1 username@your_ilo_ip


That's all for now!

Follow-up, shasums for the relevant files: the cp029101.exe is the x64 version, both contain the same ilo3_188.bin, grab it from the following url (if that still works). For whatever it's worth, as of 08/12/2017, version 1.88 is still the latest version of ilo3 for the HP Proliant G7 series.

http://h20564.www2.hpe.com/hpsc/swd/public/detail?sp4ts.oid=4091432&swItemId=MTX_3ef65d13406a41de97e6a75a3c&swEnvOid=4168


$ shasum -a 256 *
f417ba0f624ef7fdd8ee5f2db7101c719618f3c7bc5e6b2b2b8f863c5b35d12f  cp029100.exe
fb87e8c72c23d040a78f4c42b84612913d35c1cb6edc9668ff3236a3197d3b74  cp029101.exe
$ unzip cp029100.exe ilo*.bin
Archive:  cp029100.exe
  inflating: ilo3_188.bin            
$ shasum -a 256 *
f417ba0f624ef7fdd8ee5f2db7101c719618f3c7bc5e6b2b2b8f863c5b35d12f  cp029100.exe
fb87e8c72c23d040a78f4c42b84612913d35c1cb6edc9668ff3236a3197d3b74  cp029101.exe
145f6042eecdb50df27bbd4484ad9228808a2206c94097b5d83e8018532250b9  ilo3_188.bin

A few good sites to find firmware files: 
http://pingtool.org/latest-hp-ilo-firmwares/
https://github.com/seveas/python-hpilo/blob/master/firmware.conf


2 comments:

  1. #1 Are you crazy? That would be far too easy. See, according to HP, EVERYONE runs on Windows and uses Internet explorer for a browser. No, for people on a Mac, it means terminaling into a windows server, downloading the .exe, extracting it, downloading that from the windows server, then uploading it.

    ReplyDelete
    Replies
    1. Well, it's not as bad as VMWare not providing a reasonable (non-crippled) VSphere client and console for Linux or OS X since you can simply unzip the HP-provided executable in an OS X terminal, but that's beside the point. What really matters here is that there are scores of brain-dead developers and engineers locked into a single platform simply begging their potential customers to examine other solutions.

      Delete