HPE OneView
1752541 Members
5175 Online
108788 Solutions
New Discussion

Re: HP OneView Warning - Unable to retrieve asset tag information from the iLO

 
WinstonWolf
Occasional Contributor

HP OneView Warning - Unable to retrieve asset tag information from the iLO

Hello , 

After an Mainboard Change and the Bios Update on an DL380 G9 to Version 1.52 , i receive the following Warning in HP Oneview from the Server : 

Issue

Unable to retrieve asset tag information from the iLO.

Resolution

Refresh the server.

In HP Oneview on the right side i choose "Refresh" more times but without Success . 

What can i do ? 

Thanks 

5 REPLIES 5
ChrisLynch
HPE Pro

Re: HP OneView Warning - Unable to retrieve asset tag information from the iLO

Did the iLO IP Address get changed (either manually because it was statis before, or via DHCP beacuse the iLO MAC address is different)?  If the IP changed, then you will need to add the server hardare again to the appliance.  There isn't a method to update the iLO IP Address on the appliance.


I am an HPE employee

Accept or Kudo

FITEDWORK
Regular Visitor

Re: HP OneView Warning - Unable to retrieve asset tag information from the iLO

i got the Same error, without any solution. 

- Several refresh of the system.

-remove / add the system

- Reboot the System

nothing changed

HP DL580 gen9 iLO FW 2.40

 

oli2344
New Member

Re: HP OneView Warning - Unable to retrieve asset tag information from the iLO

Having the same issue on two DL360 G9 with ILO Firmware 2.40

MeFromil
Frequent Advisor

Re: HP OneView Warning - Unable to retrieve asset tag information from the iLO

hi 

take a look in the server info from the ilo  if the server serial number and the machine type are ok and if you have valid UUID 

Perhaps after replacing the board The serial number and Machine type did Apply or enterd in the bios 

 

FTBZ
Regular Visitor

Re: HP OneView Warning - Unable to retrieve asset tag information from the iLO

I was affected by the same issue, OneView 2.0.7 doesn't like empty Asset Tag in the BIOS. If you enter something in the field using F9 at boot the problem will be solved.

Don't remember this problem with OneView 2.0.