We will unpack the downloaded archive, it should contain the firmware file with the extension *.bin, this is exactly the firmware.Ĭonnect the cable to the iLO port, open the iLO web interface in Internet Explorer or Edge, enter the username and password (they are usually written on a sticker on the front panel of the server), open the “ Administration ” tab on the left, select “ iLO Firmware “, click “ Browse …” and point to the firmware file, click “ Upload” and wait for the update process to complete.Īfter a successful update, iLO will automatically restart, it will not affect the server, it will work continuously. I’m looking to apply the latest in the coming week.I also saved for you iLO4 version 2.79 in the zip archive here If anyone has applied either of these yet, please share your experience. However, I did see that there was a prior iLO release (2.42) as a customer advisory that does outline this issue and the resolution – There is nothing in the release notes of this one that explicitly states that this issue is corrected. I did see that there was a new iLO 4 firmware released this week – 2.44 – I’ve been holding off until we have a maintenance window to handle that one. We have one of these remaining in the environment – the one in production. I’ve opened three other cases since then and replacing the system board has been the resolution. Support then dispatched a CE to replace the system board and that resolved. All of that was done and there was no change – the error persisted. I opened a case with HP and support had me remove the blade, clear the NVRAM, and clear the iLO. Four of these in our DR environment and one in the production. We had 5 BL460c Gen 8 blades reporting this error with the iLO4. I am blowing up my HP ASM and Account Team about this. Let me know if you need any more details. I just feel a complete reload again is in my future for all 32 just to be safe but I don’t know if the 2.22 firmware is the final change or not? I do have 32 brand new Gen9’s and 4 have the problem, so far. So everyone else please make your own decisions. This is all my personal decision and what I feel needs to be done. 1 is just fine no issue the third is doing the same as the first, phantom VMs and re-Connecting to the vCenter.Īfter all this I feel a reload of each host may be necessary since the Host install to the SD card seems to be compromised. They say, Unknown, Unknown 10 or 11 etc… Also my NTP settings were removed and had to re-enter them again. I now have phantom VMs in my cluster associated with rejoining the Host back again. The host is back but its secure channel with vCenter is lost so I have to do a “Connect” in vCenter and re-enter the userid and password to join it back to my vCenter. The error was still present so I rebooted the host. I put my first of 4 hosts in maintenance mode and updated the firmware to 2.22. We are going to continue on 2.30 as the enhancements with 2.40 isn’t worth the gamble of a new version. We still have not had the issue reoccur on any of our blades running iLo 2.30 firmware. Release notes do not specify this issue specifically, only IPv6 enhancements. EDIT (): HP released iLo 2.40 firmware on April 1st. Awaiting to read the release notes to see if it specifically addresses this issue. Just checked HP Downloads and it isn’t available yet. EDIT (): Bjorn reports HP gave him iLo 2.40 firmware to load. iLo firmware 2.22 should be used until we hear back from HP. Though 2.30 firmware seems to have helped the issue it isn’t a permanent fix. EDIT (): Multiple reports of the issue reoccurring on iLo 2.30 firmware have been received. EDIT (): The 5+ blades we upgraded to iLo 2.30 haven’t had the issue repeat. for reporting his findings from HP!!! EDIT (): The new HP Service Pack for Proliant (SPP) (dated version 2015.10.0) contains updated iLO firmware 2.30! We are rolling this through our environment over the next week. HP should be releasing version 2.30 in the next few weeks that hopefully be a full fix for this issue! Big thanks to Mike B. The firmware should be updated to version 2.22. EDIT (): There seems to be a issue with the iLO firmware version 2.20 causing this issue. This is caused by the version of iLo running on the server. It mounted without issue but to be safe we went ahead and installed a replacement SD Card. We evacuated the host and reseated the SD Card. I logged into iLo, went to Diagnostics and found the system no longer saw the SD Card as mounted: The boot filesystem is on an internal 8 GB SD Card. As a result, host configuration changes will not be saved to persistent storage. vmhba32 : C0 : T0 : L0 backing the boot filesystem / vmfs / devices / disk / mpx.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |