Hardware Compatibility check results for ESXi 9..0.X gives the following message "Host model is not supported by any version of ESXi" model HPE ProLiant Compute DL360 Gen12
search cancel

Hardware Compatibility check results for ESXi 9..0.X gives the following message "Host model is not supported by any version of ESXi" model HPE ProLiant Compute DL360 Gen12

book

Article ID: 427039

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

When using the Hardware Compatibility check via 
vCenter > Host > Updates > Hardware Compatibility we received the following message 

Compatibility check results
Checked on <DATE>, <TIME> Re-run Checks

Export
Host model is not supported by any version of ESXi
Skipped checking host devices

Host model compatibility 
<MODEL HERE>                                 HPE ProLiant Compute DL360 Gen12 
Your host model was not found to be supported by any version of ESXi in the Broadcom Compatibility Guide
Please look to the vendor's website and documentation for compatibility information.


However the host is certified, confirmed via VMware by Broadcom, on the Hardware Compatibility List 
https://support.broadcom.com/group/ecx/productfiles?subFamily=VMware%20vSphere%20Foundation&displayGroup=VMware%20vSphere%20Foundation%209&release=9.0.0.0&os=&servicePk=&language=EN     

Logs show the following entries 

# less -i vmware-vum-server.log
<DATE> info vmware-vum-server[18456] [Originator@6876 sub=VumVapiPrivilegeChecker opID=e0557fbf-0793-49b9-82b0-4fbfab9c958e] [PrivilegeCheckerImpl 109] PrivCheck: Requested for Resource:com.vmware.esx.settings.clusters.software.reports.hardware_compatibility.get, opName:com.vmware.esx.settings.clusters.software.reports.hardware_compatibility.get, paramPath:
[...]
<DATE> info vmware-vum-server[11126] [Originator@6876 sub=HostInfo] [Utils 193] Command invocation returned: 0

<DATE> info vmware-vum-server[11126] [Originator@6876 sub=HostInfo] [Utils 196] Result from call is: {
-->     "host": {
-->         "version": {
-->             "major": 9,
-->             "medium": 0,
-->             "minor": 0,
-->             "releaseId": 1,
-->             "releaseUpdate": null,
-->             "version": "ESXi 9.0"
-->         },
-->         "powerState": "poweredOn",
-->         "connectionState": "connected",
-->         "usedByVsan": false,
-->         "fqdn": "<HOST FQDN>"
-->     },
-->     "targetVersion": {
-->         "major": 9,
-->         "medium": 0,
-->         "minor": 0,
-->         "releaseId": 1,
-->         "releaseUpdate": null,
-->         "version": "ESXi 9.0"
-->     },
-->     "serverHcl": {
-->         "server": {
-->             "modelName": "HPE ProLiant Compute DL360 Gen12",
-->             "vendor": "Hewlett Packard Enterprise",
-->             "cpuModel": "Intel(R) Xeon(R) 6517P",
-->             "cpuSeries": "Intel(R) Xeon(R) 6517P",
-->             "cpuFeatures": "0000:0000:0000:1010:0000:0110:1101:0001",
-->             "bios": {
-->                 "vendor": null,
-->                 "version": "1.56"
-->             }
-->         },
-->         "matches": null
-->     },


It's also confirmed in hcl_python_lib.log

 

# less -i hcl_python_lib.log
2026-01-21T10:48:30.710Z INFO hardware_discovery.hw_overrides Checking overrides for host host-10 (/etc/vmware-updatemgr/hcl/host-hardware-overrides/host-10)...

2026-01-21T10:48:30.710Z INFO compatibility.server Getting server compatibility for <model name> for version ESXi 9.0  [our example HPE ProLiant Compute DL360 Gen12]
2026-01-21T10:48:30.717Z INFO compatibility.server Found servers for model HPE ProLiant Compute DL360 Gen12: None



Managed Object Browser value confirms the "wrong" naming convention via the following link

https://<VC_IP>/mob/?moid=<HOST_MOID>&doPath=summary.hardware 



 

Environment

vSphere 9.0.X

Cause

The cause is the naming convention for host certification
We expect/ expected "ProLiant Compute DL360 Gen12" but we received  "HPE ProLiant Compute DL360 Gen12"
Scenario might re-occur depending on Model and Vendor 

Since the HPE value was unknown, the preprogramed was NULL/  NONE, resulting in an error

2026-01-21T10:48:30.710Z INFO compatibility.server Getting server compatibility for <model name> for version ESXi 9.0  [example model HPE ProLiant Compute DL360 Gen12]
2026-01-21T10:48:30.717Z INFO compatibility.server Found servers for model HPE ProLiant Compute DL360 Gen12: None

Resolution

The "HPE ProLiant Compute DL360 Gen12" was addressed via Developer engagement/ update.
Should you encounter a similar scenario [make and model certified on HCL] please open a case with VMware by Broadcom 

Additional Information

[Note] please use the following KB to enable MOB https://knowledge.broadcom.com/external/article?articleNumber=401669 , as MOB is disabled on 9.0.X