DL380 Gen9 is experiencing some iLO 4 configuration difficulties.

[NightshadeInSF]

Hello,

I have acquired a DL380 Gen 9 that I am having some odd prolems.  I've been looking over support posts for almost two weeks without much luck.   It has these ROM Versions:

P89 v2.94 (04/14/2022) System ROM Date 04/14/2022

iLO Firmware Version 2.82 Feb 06 2023

First of all, it displays the 338-HPE RESTful API Error - Unable to communicate with iLO FW. BIOS configuration error during post.  This recommends reverting the manufacturing defaults in the RBSU.   That remedy unfortunately had no effect.  

There are no errors on the iLO diagnostic page.  All of the settings in the RBSU are configurable and they stay how I set them if the system looses AC power for a few minutes.  The date and time do not stay.   

Additionally, when I try to add my ILO advanced license in via iLO Web GUI, it accepts the number as a good licence key, but then the licence page still shows no active license.   Also, if I try to add a new user via the ILO GUI, it fails.   If I try to add a new user via the REST tool, via the iLO Configuration Tool from the F9 menu, or via SSH connection to the ILO, they all report that the operation was successful, but no new user shows up.    The same happens with adding the advanced license if I do it via the REST tool or an ssh connection -  It reports success but never shows an active license.   Just to make sure it wasn't a problem with my license key, I put in some random letters to all of these methods and the response given is very clearly differnt than what I experince with my actual licence key.  

Also attemping to clear the Ilo Event Log or the IML reports success, but it does not clear the log.   The same old enteries are there, many of which have no date and time repoted.  

Because it was suggested in one of the solutions for the 338-HPE RESTful API Error - Unable to communicate with iLO FW.  I reset the resful API through the RESt tool and via an SSH connection to iLO and it had no apparent effct either time.     

I considered formatting my nand because it was the only other thing posting that might fix a system with this error.   I couldn't do it from the GUI because I didn't have the conditions for that button to show up.   I tried it in Windows but the command was not accepted when I passed it exactly as described,.  

Does anyone have any suggestions on how to get my iLO function properly so I can enter in my Advanced license?

Thanks alot...

Jon

[support_s]

System recommended content:

1. HPE Integrated Lights Out 4 (iLO 4) - Troubleshooting Login and iLO Access Issues

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[NightshadeInSF]

While that 1st offered solution was definately an excellent place to start with a problem like this, I have already been through all of those troubleshooting suggestions.   I also went through the solutions posted by HPE for the 338-HPE Restful API error as in my problem description.    Thank you very much for the suggestion though.  I would be grateful for any and all other suggestions as I have been working on this part time for over a week.   Many Thanks

Jon

[BPSingh]

Greetings!

1. Please try resetting iLO to the factory default settings and re-configure.

https://techlibrary.hpe.com/docs/iss/proliant_uefi/UEFI_TM_030617/s_reset_ilo_defaults.html

2. If you still continue to get 338-HPE RESTful API Error - Unable to communicate with iLO FW error. Try the following.

SSH into the iLO and use the command “oemhp_clearRESTAPIstate” and reboot the server + iLO Chip (i.e. Shutdown server, remove power cords & iLo network cable and power supplies, re-install power supplies, re-connect power cords & iLo network cable and power on server)

[NightshadeInSF]

Thank you for your response.

I have tried resetting the restful API many different ways. I completed
this using the restful API tool, the uefi shell, with Powershell, and via
an SSH connection. Finally, because I had not previously removed the
network cable as you suggested, I completed the reset via ssh again using
your method exactly but, unfortunately, the error message still appears.

I would welcome any other suggestions.

Thank you

[BPSingh]

Greetings!

If HPE Online Lights Out (hponcfg) utility installed, you could upload below script on server in question and format NAND flash using hponcfg.
NOTE: iLo4 FW should be 2.42 or above. 

Example save the script as "Force_Format.xml"

****************
<RIBCL VERSION="2.0"> 
<LOGIN USER_LOGIN="Administrator" PASSWORD=""> 
<RIB_INFO MODE="write"> 
<FORCE_FORMAT VALUE="all" /> 
</RIB_INFO> 
</LOGIN> 
</RIBCL>
****************

For Windows OS (if hponcfg installed, it should be at “C:\Program Files\HP\hponcfg”)
>> From command prompt navigate to location (C:\Program Files\HP\hponcfg ) of hponcfg.exe file 
>> Run command “hponcfg.exe /f completepathtoscript” (For e.g. “hponcfg.exe /f C:\Force_Format.xml” if its saved on C:)

It is recommended to re-flash Intelligent Provisioning as well after NAND flash format. 

[NightshadeInSF]

@BPSingh 

I followed your instructions. The iLO4 FW is 2.81. hponcfg connects to
the iLO; I had no problem resetting the iLO or completing other minor
commands but when I upload the RIBCL script I get this:

HPE Lights-Out Online Configuration Utility
Version 6.0.0.0 (c) 2003, 2021 Hewlett Packard Enterprise Development LP
Firmware Revision = 2.82 Device type = iLO 4 Driver name = iLO 4 Channel
Interface Driver

Script failed


What would you suggest?

Thanks!

[BPSingh]

Greetings!

Update the iLO 4 Channel Interface Driver to latest revision and check. If the issue persists, please log a support case for further investigation.