Highlighted
Enthusiast
Enthusiast

Status of other host hardware objects error after upgrade to ESXi 6.7

Jump to solution

Hi Guys,

I get a error message at vCenter 6.7.0U1 on ESXi host after upgrade ESXi 6.5 to 6.7 on HP DL380 Gen10.

VMware-ESXi-6.7.0-9484548-HPE-Gen9plus-670.10.3.5.6-Sep2018.iso

Screenshot - 11.11.2018 , 10_20_32 AM.jpg

It suspect there have "System Chassis 1 UID" Unknown as below.

Screenshot - 11.11.2018 , 11_16_50 AM.jpg

I check with HP iLO, can't found any related to system chassis, I all 3 ESXi 6.7 get the same issue after upgrade to ESXi 6.7.

Any idea?

Regards

Thanks...KEN

1 Solution

Accepted Solutions
Highlighted
Hot Shot
Hot Shot

Known issue, will be fixed in a future iLO update, will not affect server operation, just annoying

View solution in original post

0 Kudos
18 Replies
Highlighted
Hot Shot
Hot Shot

Hi Ken,

Please check the firmware version and check for the compatibility...

Try to upgrade or downgrade the current version and see the alerts...

Regards,

Raj M Please mark helpful or correct if my answer resolved your issue. Visit www.hypervmwarecloud.com for my blog posts, step-by-step procedures etc.,
0 Kudos
Highlighted
Enthusiast
Enthusiast

hi Guys,

After upgrade to ESXi v6.7.0U1 and plus vCenter v6.7.0U1, the warning still come up even acknowledge or set to green, but not all 3 ESXi have the same problem.

It figure out that if the server have "Device" sensor as below, it will have alarm, if the ESXi doesn't have "Device" sensor, it won't have warning, but all three server are same hardware and software.

Screenshot - 12.11.2018 , 7_40_21 PM.jpg

Screenshot - 12.11.2018 , 7_39_25 PM.jpg

Regards

Thanks...KEN

0 Kudos
Highlighted
Hot Shot
Hot Shot

Known issue, will be fixed in a future iLO update, will not affect server operation, just annoying

View solution in original post

0 Kudos
Highlighted
User Moderator
User Moderator

Check if the following VMware KB article helps:

VMware Knowledge Base

Diego Oliveira LinkedIn: http://www.linkedin.com/in/dcodiego
0 Kudos
Highlighted
Contributor
Contributor

Does anyone know when the correct iLO update has been rolled out? We currently have ESX6.7 U2 installed and we still have the same problem.

We have also installed the latest HP iLO firmware (1.40)

Highlighted
Contributor
Contributor

same here, new installation with 6.7 U2 on a ML350 G10 with ilo 1.40

0 Kudos
Highlighted
Contributor
Contributor

Can anyone from VMware answer whether this issue will be fixed in a future update? Has this actually being identified as an issue by VMware or are people assuming it will be fixed? Same issue here after upgrading from 6.0 to 6.5 with HP DL360 G10 Hosts

0 Kudos
Highlighted
Contributor
Contributor

Still problem after iLO update to last v. 1.43

ProLiant DL380 Gen10

HPE-ESXi-6.7.0-Update2-iso-Gen9plus-670.U2.10.4.1.8

iLO 1.43

pastedImage_0.png

0 Kudos
Highlighted
Contributor
Contributor

It appears that 1.45 did the trick for me. I did 1 of 5 of my hosts. I reset the alarms  back to green status, and the one I updated has not triggered the alarm again. The other 4 triggered again within seconds.

Darin

0 Kudos
Highlighted
Contributor
Contributor

We have version 2.10 Oct 30 2019 and the problem is seeing as well.

0 Kudos
Highlighted
Contributor
Contributor

I have similar on ProLiant DL380 Gen10 that is using the HPE Custom VMware ESXi 6.7 Image.

My Hardware Health sensors  have two areas of problems:

System Chassis 1 UID | Unknown state

and three entries for Memory

Memory Device 10 Mem_Stat_C01S11 | Alert state

Memory Device 18 Mem_Stat_C02S03 | Alert state

Memory Device 2 Mem_Stat_C01S03 | Alert state

Server is only using 2x32GB 2933MHz DIMM

Strange thing was that the System Chassis 1 UID issue was present after I upgraded from Esxi 6.5 to 6.7.

Also host was at iLO5 v2.16. I thought that iLO upgrade to latest might clear it.

Now host is at iLO5 v2.30 ... and additionally displaying Memory sensor issues.

When viewing under esxcli ipmi it shows Configuration Error.

System BIOS = U30 v2.36 07/16/2020

iLO5 IML and HPE Support have given the server a clean bill of health.

I also have updated ALL firmware for BIOS, NIC, SPS, Smart Array to latest I can find.

esxi hardware sensors alerts.png

My environment:- vSphere 4.1 : • ESX 4.1 Servers • vCenter Server 4.1 (VM) : - Windows Server 2008 64bit - MS SQL 2005 (VCDB/VUMDB) • NetBackup 6.5.5 - VCB 1.5 U1 • FC SAN
Highlighted
Contributor
Contributor

Hi,

we've got the same Problem after updating vSphere 6.7 Update 3 to the newest build and updating HPE Firmware to the SPP 2020.03.2 and iLO 5 v2.30

The Problem occurs on all updated Gen10 Servers. Were you able to resolve the problem?

Greetings

0 Kudos
Highlighted
Contributor
Contributor

Hi Macgreen

I have the same problem

I tried to downgrade ILO lower than 2.30 (2.16) ,restart ams,reset system event,refresh sensor ,and the problem fixed ,

you can try it.

Highlighted
Contributor
Contributor

hi I have 6.5 U3 ESXi host, ML 350 Gen10 soon for 2 years (Smart Array ) and since beginning (6.0) I never had hard disk status on Health status and Storage. I just updated it with with SPP 2020.09 and HPE Custom image 6.5 (Oct2020) and the same continues, no hard disk status, but new memory alerts I didn't have before. These alerts are exactly the same as mention here "Memory Device 10 Mem_Stat_CO1S11", Device 18 and Device 2.

I know another ML110 Gen10 server which also doesn't have any Storage status on VCSA, but when logged on to the ESXi itself, the HD are visible.

So, for 2 years no fix, I have opened HPE support ticket so will se if there will be any solution, so far opening ticket to HPE vmware support then HPE HW support, and I'm being bounced around without any solution. Have anyone had similar "storage" hard disk not visible problem with Gen 10 servers? Those memory alerts are now new, so buggy updates continue.

0 Kudos
Highlighted
Contributor
Contributor

I spoke with HPE, it's a known problem to both HPE and VMware. here's the HPE advisory:

https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00106468en_us

Funny thing is, if I ignore these sensors with "esxcfg-advcfg -s 2,3,10,11,18,19", it ignores only the odd ones, 2,10,18 cannot be ignored, dunno why.

Because ignoring didn't work for me, I downgraded to 2.18.

0 Kudos
Highlighted
Contributor
Contributor

Its never ending story with HPE and VMware , sick of it , with 6.7U3 and SPP2020.03 i was having nonstop ALOM network adapter sensor warnings, doesn't matter on what iLO version, toss in middle false fan alerts, right now with 7.0.1 and SPP2020.09 all DL360 Gen10 hosts have false positives on memory. This never ends and i have to selectively disable particular alert definitions, just to keep WBEM turned on. No idea anymore whom to blame or it just communication issue between HPE and VMware, but its been round robin of pointing fingers.

0 Kudos
Highlighted
Contributor
Contributor

HPE has released ILO5 2.31 https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_719b3c76e0eb47ab98073490d9#tab5

Inaccurate Memory Sensor status reported in the vSphere web client for HPE ProLiant Gen10 and Gen10 Plus servers running VMware ESXi 6.5/6.7/7.0 (Refer to Customer Advisory)
2.31 fixed the issue on my Gen10.
Highlighted
Contributor
Contributor

I can confirm, the same for 6.5U3 and ML110 Gen10 and ML350 Gen10. The end result of my vmware case about hard disks not shown in Hardware health->Storage is that there is nothing that can be done, "known issue" etc. Recommendation was to update ESXi from 6.5 to 6.7 and see if the problem persist. I suppose I will do an vsphere upgrade to 7.0 U1 after couple moths since it was just released.

0 Kudos