This way I don’t have to enter the boot options each time. Post-install I configured the advanced configuration option to 0 (I unchecked it). HP Lights-Out Mouse Optimization for Remote Console (HPLOMOPT.EXE) Version 1.00 - The RILOE / RILOE II / iLO Remote Console performs more optimally and. ( Note: the argument is noipmiEnabled – I was mistakenly typing noipmiEnable the first few times and nothing happened). The solution is as detailed in this blog post.
HP ILO 2 FIRMWARE UPDATE UPGRADE
Because of the faulty iLO though, ESXi would hang at “loading module ipmi_si_drv” for about 30 minutes each time it would boot (or when I’d run the installer to upgrade to 5.5). I think the faulty iLO was causing SPP to fail. I tried to upgrade its iLO firmware and ROM by physically being in front of the server but it would hang at the pulsating logo as above. One server though had no luck – its iLO chip was faulty I guess. (I have also read reports on the Internet where there was no need to remove/ re-insert the iLO cable so YMMV). I was able to fix some of those servers by completely powering off the server, removing the power cables, removing the iLO cable, waiting a few minutes, putting back the power cable and powering on the server, and once it has loaded the OS put in the iLO cable.
HP ILO 2 FIRMWARE UPDATE HOW TO
How to download and update ilo 4 firmware 2 55 download Samsung are. Anyway, just for upgrading the iLO firmware it is too much hassle to care about that many moving parts. If I just want the ILO 2.73 I would extract the bin file from exe and then do it through ILO web admin. Management Agent (never heard of it) installed. I do my firmware update using the SPP2020.03.01 usung SUM it checks all firmware against the server, mine is esxi. I couldn’t ping the iLO IP address nor could I connect to it. ILO 3 Firmware Update (HP Proliant D元80 G7). Upgrading the iLO sorted that out!Īnd while on the topic of iLO I had some servers whose iLO was not responsive. On a related note, I had some servers with an “Internal Health LED failed” error even though everything seemed to be alright with them. So I could have saved some time for myself with the LeftHand/ StoreVirtual servers by updating the iLO (as above) and upgrading the OS. :-) I used the ancient version of IE on my server and that didn’t do anything, but when I used Firefox I was able to see a progress bar and the firmware actually got updated.Īfter doing this I was able to run the SPP without any issue.Īnother thing I learnt is that for the LeftHand/ StoreVirtual servers, simply upgrading the OS or patching it is enough to upgrade the ROM too. Go to the “Administration” tab, click Browse to select this file, and click “Send firmware image”. This is the binary image of the iLO 2 firmware that you can flash via SSH or the webpage.įlashing via the webpage is easy. The result is a file with a name like “ilo2_225.bin”.
HP ILO 2 FIRMWARE UPDATE ZIP
I downloaded the Windows versions, right clicked on it (it’s an EXE file) via 7-Zip (any other zip tool should do), and extracted the contents. That page lets you download versions of the firmware for flashing via Linux or Windows. For anyone else looking for the latest and greatest version of iLO 2 this HP page is what you want (and the “Revision History” tab on that page gives you older versions too). That should be easy but I had trouble getting it. I used TinyWeb to run a small web server off my desktop machine).īefore upgrading iLO via SSH or the webpage, you need to get iLO first. (Could just be the web server I was running. The blog post I link to before (and also this one) show a way of updating iLO via SSH but that didn’t work for me sadly. In my case the servers had really ancient versions of iLO – “1.87 ” – so I upgraded them via the iLO webpage. And I sorted of worked around the pulsating logo problem.įor the pulsating logo issue apparently the fix is to upgrade iLO first and then run the SPP. I was able to work around the pink screen by using an older version (for instance, I was using 2015.04 and that failed but 2014.09 worked). I couldn’t find any solutions for the servers that power off (I used SPP version 2015.04, 2014.09, 2014.02 – same results for all). For instance some servers simply power off once the SPP CD boots, others give me a Pink Screen of Death, and yet others simply hang with the pulsating HP logo. Interesting thing about the firmware upgrades is that even between servers of the same model, when upgrading with the same Service Pack for Proliant (SPP) CD version, I get different errors. Side by side I have also been upgrading the iLO and ROM of our LeftHand/ StoreVirtual boxes following which I upgrade them from LeftHand OS 8.5 to 12.0.
Using hponcfg is possible from Windows as well when updating the local machines, so it’s quite possible to use the same XML (though I’ve not tested it).Past two weeks I have been upgrading the iLO and ROM of all our servers (a bunch of HP DL 360s basically – Gen6 to Gen8) following which I upgrade them from ESXi 4.1 to 5.5. iLO 3 resetĪnd that’s it, the magic is done.
0 kommentar(er)
