In my Lastest batch of DL360 Gen8 sand DL380 Gen8 servers (order of about 40 systems), A little over 25% of them are having iLO issues.
Wondering is anyone has seen any similar isues or has Ideas on what to try next?
Here is what I see:
* the URL to the ilo (https://...) shows the "ILO 4 HP Prolaiant" but never show the "iLO hostname", eventaully I see "Connection with iLO cannot be established. If you recently made changes to the network configurations, you may need to refresh this page to re-negotiate an SSL connection" right below the login button
* Once a system gets in the mode, it never recovers. we can DRAIN the power, the ilo works for a few minutes (10 to 30). we see errors the event log server "iLO watchdog reset" messages HP tech support had us downgrade the ilo firmware 2.00, also tried version 2.02 amd 2.03 no effect.
* Also after a recent system board resplace a DL360 started doing the same thing. these systems are on a deldicate LOM network. on the network I have 562 ILOs, 728 iDracs and 9 Sun iLOMs. I only see the issue on new HP systems or HP system with recently replaced system boards
I got this message also. "Connection with iLO cannot be established. If you recently made changes to the network configurations, you may need to refresh this page to re-negotiate an SSL connection"
This happened after upgrading to iLO2.00, on a Proliant DL360p Gen8.
I tried upgrading Firmware version 2.10, the upgrade said it failed about 35% of the way in, but it seems to have fixed the issue.
I have not full tested this yet, use this solution with caution.
Upgrade Requirement: Critical - HP requires users update to this version immediately.
Intermittent Non-Maskable Interrupt (NMI) Events May Occur on HP ProLiant Gen8 Servers running HP Integrated Lights-Out 4 Firmware Versions 1.30, 1.32, 1.40 and 1.50.
Sorry to resurrect an old thread, but I'm having similar issues.
It started with the "Embedded Flash/SD-CARD: Embedded media manager failed initialization" message which was meant to be only prior to iLO1.50 but I'm using 2.20. And now I can't connect via the HTTP method with the same issues as the OP - it brings up the main login page but without the servername and refusing to allow a username/password entry.
I have two identical servers, both DL360p Gen8, and this issue is only on one of them. Is it possible there's an internal issue either with the chip or the embedded flash card? If so, does anyone know how to get it fixed at all?
Just noticed today, I had the same issue. I did a test with different workstations and browsers but even switching OFF and ON the server is not working for some reason. I unplugged the server from power but the issue still exist.
The server is a DL380p GEN8 V2 with ILO Firmware 2.20
The ILO Configuration Utility for Windows was not working as well, in the meanwhile while searching on the web and this thread the issue disappeared?! Any ideas?
I am having the same issue on a ML350 G8 which I have just updated to latest ILO 4 Firmware V2.22
Connection with iLO cannot be established. If you recently made changes to the network configurations, you may need to refresh this page to re-negotiate an SSL connection.
After reboot ESX Host OS not coming up (could not obtain ping reply)
Tried to connect to iLO with browser -> Sluggish and SSL Error, cannot connect. (Server is in Datacenter!)
Fortunately tried to connect with SSH -> map1/reset (reset iLO)
Tried one more time and HTTPS -> iLO worked again.
Unfortunately, the server booted up before I could obtain a Remote Console KVM view.
Again, only after resetting iLO the server started to boot to me, I could spontaneously ping the host OS after connecting to iLO.
Same Critical Error in Event log, to me: this also stopped booting up the server installed OS (ESX) until a reset of iLO probably corrected the 'critical error' and let the server boot it's OS.
We do utilize the embedded SD-Card reader where ESX is installed on.
HP looked into the AMS logs for all the 3 DL360G9 servers and found the same errors (not visible in the iLO logs) so I was told. Upgraded to iLO 2.30 but the cause is still unknown. Only one server did exhibit the iLO error but all three seems to have some sort of errors visible thru AMS extraction.
Hopefully this can be 'fixed' thru firmware updates OR a major hardware replacement job.
Same here. Microserver Gen 8 with iLO4 suddently is not always accessible with:
Connection with iLO cannot be established. If you recently made changes to the network configurations, you may need to refresh this page to re-negotiate an SSL connection.
"Connection with iLO cannot be established. If you recently made changes to the network configurations, you may need to refresh this page to re-negotiate an SSL connection."
Update: Solved by updating iLO4 FW from 2.50 to 2.54
