Warning - iLO 4 not responding. System health monitoring has been disable

[ApolloPT]

Hello everyone,

A friend of mine has bought a HP Proliant ML310e Gen8 v2, that camei with a problem in iLO, this server fans are working at full rpm, from prompt its not possible to enter on iLO configuration, the iLO dedicated NIC is getting an IP and the hostname on that port is related with iLO.

From a first approach this iLO seems somehow corrupted, and I think that needs to be reflashed. After some search I found some situations where it was indeed corrupted, and now I was trying to reinstall a iLO 4 firmware from scratch through an usb pendrive.

Want I've done was:

- Installed USB key Utility from HPE.

- Downloaded Smart Update Firmware DVD version 10.10.

- Used USB key Utility, and add the DVD ISO, successfully.

- After that, I add the SCEXE file that contains the iLO 4 firmware in: D:\HPFWUP1010\hp\swpackages

After doing this, I trid to boot from this pen drive on that server, but no luck.

Do you think that this is in fact an iLO corrupted?

To reflash, is this the way?

How can I reflash an iLO?

Thanks in advance!

[Torsten.]

Smart Update Firmware DVD version 10.10. is meanwhile more than 10 years old - much too old.

This is the famous NAND issue.

Can you get the Web GUI of ILO?

[ApolloPT]

There is no webgui available, and from boot prompt there is no option available to access.

[Mike Texter]

Sorry to necro but I just ran across this same problem.  What's the famous NAND issue?  Are these known to become corrupt / suddenly fail at iLO 2.10?  That's the version I'm at and encountered this error.  This is a replacement for a node that failed to take updates past iLO 2.55.  System in question is an SL4540 Gen8, single node.  Swapping the iLO port from one chassis to another didn't change a thing.  

[Sunitha_Mod]

Hello @Mike Texter, 

Since you have posted in an old topic and there is no response yet, we would recommend you to create a new topic using the create "New Discussion" button, so the experts can check and assist you further. 

[Mike Texter]

I was hoping to keep the discussion of the issue all in one thread, that way future searchers can find the answer more easily.  No worries though, we replaced the node and all is well!  My take on the "famous NAND issue" is that the NAND just gets killed if iLO sits at v 2.10 for too long, requiring a full system board replacement.  Guess that's part of why new versions get released