

In any case few would argue that HP managed to invent a very interesting engineering solution for the problem of fixing a crash or freezing of a small supplementary computer by shutting down the main production server and removing power cable. Imagine the case when a remote site has no night shift personnel or there is no qualified personnel on the site at all and situation does not look too promising. You need to shutting down, remove power cables and then reboot server such as DL580 or DL 380 to restore ILO functionality. Blades are the most annoying case as there are usually way too many of them.īut ILO freezing in remote production rack servers is nothing short of HP-made disaster. Sometimes the console can't connect tot he server/blade and only button and lights icon at the bottom of the screen are active. If ILO hangs and lose network connectivity for no obvious reasons, there is no reset button for ILO: you need to power server down, disconnect cables (or remove the blade) and power it up again. The first usable version of ILO 3 is 1.85 ( CP026424.scexe) released May 13, 2015, long after server of V7 series became obsolete. It is unsafe to use with any product, but especially with large HP servers and blades. The defining feature of ILO3 in versions up to and including 1.26 is its instability.ILO 3 - HP engineering fiasco May the source be with you, but remember the KISS principle -) iLO 3 - HP engineering fiasco Serial console y Those with the older revision refused to accept the. I tried updating several HP Proliant D元80 G7 ILOs today to firmware version 1.50. The iLO web interface allows me to upload a.bin file (Obtain the firmware image (.bin) file from the Online ROM Flash Component for HP Integrated Lights-Out.) The. Everybody who like me has to search HP for firmware. The component will update the iLO 3 firmware and reset the iLO 3 processor.
