Hardware Status Alerts - Unconfigured Disk : Disk Error HPSA

[nitzerebbs]

Hi,

I am running a single ESX Host 7.0 U1 (HP Microserver Gen10 plus) with HPE E208i-p SR on 4x 2TB SSDs (single lun).

I am getting many hardware errors with unconfigured disks, system runs normal: 

I also tried searching for any help, but all infomation is based on older ESX versions...
Does someone have a solution for this ? 

Thanks 

Jan

 

[E_Espinel]

Hello
It is generally recommended to install VMware vSphere with the manufacturer's custom ISO image in this case HPE which includes manufacturers own drivers and tools.
Most manufacturers provide tools to manage their disk controllers in VMware from CLI.
Attached links

https://itsimple.info/?p=1732

:https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX-ecd489e042ff4821b90abdd305#tab3

You may need to install the indicated Tools.

 

[nitzerebbs]

Thank you for the answer, but of course, I used the HPE custom VMware ISO - that is not the problem.

 

[nitzerebbs]

I did several checks now with the HPE Smart Storage Administrator CLI, and everything is ok, there are absolutely no errors.

 

[E_Espinel]

Hello.
If from the HPE Smart Storage Administrator CLI no error was found, we are fine physically.
You should check if the current firmware of the controller and disks, has no problems reported in HPE, or if there is a higher or recommended level to upgrade.
Another point to check is the version of the driver you are using for the disk controller, if there is a higher level it is recommended to update it.
Please read all the requirements before upgrading either the firmware or the driver.
Always have a full backup of the data (VMs) and the ESXi configuration.

The following commands will help you identify the controller and driver you are using.

# esxcli storage core adapter list

Run this command to get get the specifics of the device driver

# vmkload_mod -s HBADriver |grep Version

# esxcli software vib list | grep HBADriver

 

[nitzerebbs]

Hi, no new firmware available for the controller, because I am already using V 3.53.

Maybe I try using the drivers from ESX 7.0U2a for "smartpqi", this is newer than my actual one:
old: 70.4000.0.100-4vmw.701.0.25.17325551
new: 70.4000.0.100-6vmw.702.0.0.17867351

I don't know if this is a solution...

No one else having these kind of alerts ?

[DanGolan]

I am

[Ricko10]

Hi, has anyone tried the 4.11 firmware released last week?
Software Details - Online ROM Flash Component for VMware ESXi - HPE Smart Array P408i-p, P408e-p, P408i-a, P408i-c, E208i-p, E208e-p, E208i-c, E208i-a, P408i-sb, P408e-m, P204i-c, P204i-b, P816i-a and P416ie-m SR Gen10 | HPE Support

 

[nitzerebbs]

Yes, it does not fix the issue

[Lukas Minarik]

Yes, we have installed it today and the error is still present.

We are using HP DL580 G10 with Smart Array P408i-p. 

ESXi version 7.0.3, 18644231 installed from VMware-ESXi-7.0.3-18644231-HPE-703.0.0.10.7.1.16-Oct2021.iso

The only workaround for now is downgrade to firmware 3.00 

 

We have tried also this and it didn't help at all: https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00117054en_us

[nitzerebbs]

Hi, no new firmware available for the controller, because I am already using V 3.53.

Maybe I try using the drivers from ESX 7.0U2a for "smartpqi", this is newer than my actual one:
old: 70.4000.0.100-4vmw.701.0.25.17325551
new: 70.4000.0.100-6vmw.702.0.0.17867351

I don't know if this is a solution...

No one else having these kind of alerts ?

[kevinw9521]

Hello,

 

i have the same problem  i am running  HPE Customized ESXi 7.0.2 Image version 702.0.0.10.6.3 for HPE Servers based on VMware ESXi 7.0.2 release.with the newest Service Pack Prolian installed (2021 )

 

(HPE-Custom-AddOn_702.0.0.10.6.3-24 (Hewlett Packard Enterprise))

 

 

[MauAnd]

Hello,

I have the same problem on two new servers with the latest version of Esxi "VMware-ESXi-7.0.2-17867351-HPE-702.0.0.10.7.0.52".

[nitzerebbs]

seems to be a general problem, which controllers are you guys using ?

[MauAnd]

I use the HPE P408i-a SR Gen10.

In addition I have a third server with similar configuration but the problem is not present.

1. Server Dl360 Gen10 - 3 hd sas 1.8tB - 3 hd sata ssd - Has the problem
2. Ml350 Gen 10 Server - 3 hd sas - 3 hd sas ssd - Has the Problem
3. Ml350 Gen 10 Server - 3 hd sas - Doesn't Have The Problem

I am not sure, but Server 2 with the two sas ssd disks up to last week did not have the problem, I doubt that the problem is activated when adding ssd disks.
But as said I'm not sure

 

[E_Espinel]

Hello
According to the VMware compatibility matrix (online) for the HPE Smart Array E208i-p SR Gen10 with Firmware 3.53,
VMware ESXi 7.0 smartpqi 70.4054.2.118 driver is required.
https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=43646

Download driver from https://my.vmware.com/en/web/vmware/downloads/details?downloadGroup=DT-ESXI70-MICROSEMI-SMARTPQI-7040542118&productId=974

How to download and install async drivers in VMware ESXi (2005205)

https://kb.vmware.com/s/article/2005205

 

[nitzerebbs]

does anyone have the possibility to try the required driver, maybe in a test environment?

For me it is only possible with a downtime, and if it does not help, it's a waste of time...

[MauAnd]

Hi, I have tried on the server that I am preparing,
I don't have the "HPE Smart Array E208i-p SR Gen10 with Firmware 3.53" controller but the "HPE P408i-a SR Gen10 3.53" the driver present is the same as the one I'm downloading.

[root@localhost:~] esxcli software vib install -d /vmfs/volumes/datastore1/App/drv.zip
Installation Result
Message: Host is not changed.
Reboot Required: false
VIBs Installed:
VIBs Removed:
VIBs Skipped: MIS_bootbank_smartpqi_70.4054.2.118-1OEM.700.1.0.15843807

[root@localhost:~] esxcli software vib list |grep smart
smartpqi 70.4054.2.118-1OEM.700.1.0.15843807 MIS VMwareCertified 2021-05-19

[nitzerebbs]

Thank you...
...so the required driver does not fix the problem 

[MauAnd]

unfortunately not

[E_Espinel]

Hello.
First if we change server to test the driver, let's know which driver is using the controller of that server.

This command lists the adapters and their drivers, we are going to assume that it uses the same smartpqi driver, but you should verify that it does.
# esxcli storage core adapter list

This command tells us which driver is loaded i.e. in use
# vmkload_mod -s smartpqi |grep Version

This command tells us which vib or vibs are installed, they can be of different versions, but only one is the one in use
# esxcli software vib list | grep smartpqi 

or

# esxcli software vib list | grep smart

The VIBs Skipped: means that it was not installed, so the message is clear Message: Host is not changed

Whenever a driver is installed or updated, a reboot will be required.

 

[sponsz]

Hello,

i have the same error on multiple DL385 Gen 10 Plus servers on a new working vSAN cluster.

VMware ESXi 7.0.2 Build-17867351 Update 2
HPE Customization for HPE Servers 702.0.0.10.7.0-52
HPE Smart Array E208i-a SR Gen10 3.53
System ROM A42 v2.40
iLO Firmware Version 2.44

 

# esxcli storage core adapter list
HBA Name  Driver     Link State  UID                   Capabilities  Description
--------  ---------  ----------  --------------------  ------------  -----------
vmhba0    nvme_pcie  link-n/a    pcie.300                            (0000:03:00.0) Marvell Technology Group Ltd Marvell NR2241 NVMe Controller
vmhba1    smartpqi   link-n/a    sas.51402ec015714e80                (0000:04:00.0) Microsemi HPE E208i-p SR Gen10
vmhba2    smartpqi   link-n/a    sas.51402ec01640a970                (0000:64:00.0) Microsemi HPE E208i-a SR Gen10
vmhba3    nvme_pcie  link-n/a    pcie.2300                           (0000:23:00.0) Samsung Electronics Co Ltd NVMe SSD Controller PM173X
vmhba4    nvme_pcie  link-n/a    pcie.2500                           (0000:25:00.0) Samsung Electronics Co Ltd NVMe SSD Controller PM173X
vmhba5    nvme_pcie  link-n/a    pcie.2600                           (0000:26:00.0) Samsung Electronics Co Ltd NVMe SSD Controller PM173X

# vmkload_mod -s smartpqi |grep Version
Version: 70.4054.2.118-1OEM.700.1.0.15843807

# esxcli software vib list | grep smartpqi 
smartpqi                       70.4054.2.118-1OEM.700.1.0.15843807  MIS      VMwareCertified   2021-05-15
lsuv2-smartpqiv2-plugin        1.0.0-6vmw.702.0.0.17867351          VMware   VMwareCertified   2021-05-15

 

 

I would like to try FW 3.00 but where can get smartpqi 70.4000.0.100-6vmw.702 which is mentioned here https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=vsanio&productid=41773&deviceCategory=vsanio&details=1&vsan_type=vsanio&keyword=E208i-a&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc

Could the attached drives cause that problem? I have 9x VO007680JWZJL with FW HPD4 per server. https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=ssd&productid=46362&deviceCategory=ssd&details=1&vsan_type=vsanssd&ssd_partner=41&ssd_devicetype=4&ssd_tier=3&keyword=P19909-B21&vsanrncomp=true&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc

 

 

[E_Espinel]

Hello.
I have checked HPE for the latest Firmware and Driver levels for the Smart Array controllers, and there are no more. But if entering through the HPE Smart Storage Administrator CLI no errors are found, then physically there is no problem.
We will have to wait for new drivers or Firmware to be generated to correct this false positive.Or maybe some magic trick to solve it.

Personally I am not in a hurry to move to version 7, most of my customers are on version 6 comfortably.

 

[MauAnd]

Hello,
as information I also tested the
ESXi 6.7 U3 May 2021 - Support Gen9 Servers and forward.
But even with this version the problem arises.
I haven't checked with previous versions.

Greetings, have a nice day.

[shineknoxTN]

I'm having the same problem with HP Custom image 6.7 U3 build 17700523  DL380 Gen10.  I updated all firmware before upgrading from 6.5 to 6.7, using the latest SPP.  The firmware and driver versions are listed in the recommended compatibility tool, from vmware.  There are no issues reported in HP Storage administrator cli or issues reported in ilo.  I did not have this problem with 6.5.

Here are the version currently running.

the driver for smartpqi is 67.4054.2.118-1OEM.670.0.0.8169922

firmware version 3.53

[Srijithk]

To resolve this issue, remove the "smx-providers" 

For VMware ESXi 6.5 / 6.7

esxcli software vib remove -n smx-provider

For VMware ESXi 7.0

esxcli software component remove -n smxProvider

reboot for the changes to be effective

Please refer --> https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00117054en_us

Note: you may also downgrade the fw to a version earlier say 3.00

Below is the HPE reference link for the same

https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_1b05b3627f244efebc5553b7f4#tab3

Please upvote or mark this answer as a solution

Thanks,
Srijith Karamchander

[vjrk83]

yes removing the smx-provider fixes the issue. 

[DanGolan]

Would you please provide directions on how to remove and what else is affected when removed?  TIA

[vjrk83]

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

For VMware ESXi 6.5 / 6.7

esxcli software vib remove -n smx-provider

For VMware ESXi 7.0

esxcli software component remove -n smxProvider

 

 

[David Nixon]

DL360 G10 w/ Gen10 Service Pack for ProLiant version 2021.10.0

HPE Smart Array P408i-a SR Gen10 4.11

ESXi 7u3c using imaged based management

HPE Driver pack: HPE Customization for HPE Servers 703.0.0.10.8.1-3

results in: smx-provider 700.03.16.00.12-14828939 HPE VMwareAccepted 2022-01-05

 

Same problem.

[wattebausch]

VSAN Skyline Health for ESXi 7u3 recommends Firmware 4.11. If you want use 7U3 you couldn't downgrade to 3.00.

I ask myself, is it better to remove the smx-provider and not see anything like controller battery, connected disk, logical disk.....or ignore the error message of non-existent disk?

what do you think?

[_Kostek_]

I think a better solution is to ignore the non-existent disks error and have the rest of the components monitored.

 

Jarek

[DanGolan]

Yeah, easier if you do not have monitoring software constantly alert about this errors and having to repeatly explain that VMWARE is unable to resolve this issue.

[_Kostek_]

Maybe it is possible to silence only this alarm (it was possible for me)?

[David Nixon]

I've still been fighting with HPE on this matter.  VMware showed me in the MOB where the hardware is reporting the problem as a critical error.  With that, I'm targeting HPE for a fix.  The suggestions have included rolling back firmware to 3.x (not supported on ESXi 7u3) and to remove the smx-providers VIB (disable all hardware alerting).  For us, we are monitoring hardware health via vCenter through ESXi, rather than trying to alert on the iLO so I need hardware insight via ESXi.

[vjrk83]

It was so annoying that the latest release didn't have a fix for smxprovider. We have clusters mixed with Gen9 & Gen10 managed under single image and had to disable our monitoring software on Gen10s and enable vcenter alarms. Hope the next release have a fix. 

[googol13]

I just upgraded my HP DL360 Gen10 P408i-a controller from v4.11 (came from Oct 2021 SPP I ran prior) to v5.00 that just got released a few days ago, still having the same issue.

 

Running the latest HPE OEM, fresh off the presses a few days ago in April 2022, 7.0 U3d

 

need a real fix from HPE, still need to monitor hardware...

[David Nixon]

For what it's worth, HPE told me that they weren't going to fix it, even after I escalated with my sales rep.  That will lead to a painful conversation in the near future.  We did find that using SolarWinds Application Monitor as our monitoring tool, we were able to disable the false-positive errors so that we can continue to monitor the rest of the system.

Settings > All Settings> Manage Hardware Sensors> Filter by machine name > disable all erroring disks.  

[bradhs123]

Same problem, is HP going to fix this?  Do they need additional information from us to fix it?

[bradhs123]

I followed this article: Document - Advisory: (Revision) HPE Smart Array SR Gen10 Controllers - Additional Disks Are Displayed In ESXi /vCenter GUI and smx-provider Errors Are Logged On Platforms Configured With Controllers With FW v3.53 (Or Later) | HPE Support

 

Which removed smxProvider.

BUT! No more monitoring data... How do I reinstall smxProvider?

[Mike Gerolami]

Thanks for this link and info

[markdcb]

Yes it does fix the issue,

 

however: the sfcbd-watchdog / CIM server won't start anymore so you cant use remote monitoring tools to view status' anymore.

"The Small Footprint CIM Broker Daemon (SFCBD) is not running. Storage health data is reported by this daemon. Please see this KB article for information on enabling this service."

[Infra SDEUXI]

Hello,

same issue for us with 2 new HPE Proliant DL380 Gen 10, just out of the box.

We just installed the following :

• HPE Service Pack for Proliant 2021.04
• VMware-ESXi-7.0.2-17867351-HPE-702.0.0.10.7.0.52-May2021

And we also have the "Unconfigured disk : Disk Error" issue on 36 non present disks.

Thanks.

 

[nitzerebbs]

Does anyone have the possibility to open an official call with VMware ?

[MythenIT]

Same here

HPE DL380 G10 - ESXi 6.7u3 May21

I think the Problem is the new v3.53 firmware of HPE Smart Array P408i-a SR Gen10

[paguti20]

Same problem.

HPE DL360 G10 - ESXi 6.7u3 

I think the Problem is in HPE Smart Array P408i-a SR Gen10 driver.

HPE or VMware any solution??

[Patrik Kernstock]

Hi all,

I got an update from a colleague, stating that HPE told that this is a known issue and has been introduced in the latest firmware of the P408i controller with release 3.53 (as  correctly stated). It's known to exist in ESXi 6.7 and 7.0.

The only workaround (known so far) seems to downgrade to firmware version 3.00. But as the firmware is up to HPE, please consult HPE in case you have further questions, if instructions for the downgrade are needed or when a written statement is required. I'd recommend reaching out to HPE for clarification or next steps.

(Please note that this is just a cosmetic issue.)

Kind regards,
Patrik

[BartD80]

I can confirm that the same issue also exists on Vmware 6.5U2

[MDM79]

Hello everybody,

same here on HP DL380 G10. I performed following upgrades and problem occurred:

1. HPE SPP from version 2020.09.1 to 2021.05.0

2. VMware ESXi (HPE Custom ISO) from version 7.0 Update 2 Build 17630552 to version 7.0 Update 2a Build 17867351

I opened a case in VMware and they told me that it could be a Controller firmware issue and asked to open a case in HP.

I opened a case in HP and they told me to downgrade to 3.00 version and, in case that wouldn't work, I should replace the controller. I tried the firmware downgrade but system has returned this message: "“Update not attempted. All selected devices are either up-to-date or have newer versions installed”. I think that replace the controller won't fix the issue based on an HW that is working correctly.

HP fix this firmware and driver bug!!!

 

 

 

 

 

[BartD80]

Same answer from HPE on my ticket:

This is a Known Issue and HPE is working on the same to fix the reporting issue.

Work Around:

Downgrade Smart Array Firmware to v3.00

 
I have not tried the downgrade and will wait for new firmware release from HPE.

[Michael_LNZ]

We got the same problem with a 

• ProLiant DL20 Gen10

with a VMware ESXi 6.7.0 U3 HPE Custom Image installed

after Update with Gen10 Service Pack for ProLiant 2021.04.0 (19 Apr 2021)  the HPE Smart Array P408i-a SR Gen10 firmware go up to 3.53 

and than the VM Hardware -> Storage went crazy 

i used the Workaround https://kb.vmware.com/s/article/74607  to got time because the errors will fill up the event log 

"You can avoid this issue by disabling the WBEM services. To disable the WBEM services on the ESXi host, run this command:
esxcli system wbem set --enable false "

I used the https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_1b05b3627f244efebc5553b7f4 3.00 Driver File from HPE for downgrade

• Login as root. (You must be root in order to apply the update.)
• Place the Smart Component zip file in a temporary directory.
• Unzip the file CPXXXXXX.zip
• Ensure that CPXXXXXX.vmexe is executable by using the command:

             chmod +x CPXXXXXX.vmexe

• From the same directory, execute the Smart Component. For example: ./CPXXXXXX.vmexe  --downgrade
• Follow the directions given by the Smart Component.

and the problem with the "Sensor -1 type, Description Disk XX " errors are gone 

we got one more problem with a memory sensor 

after clearing the system sensors event log this problem was also gone

 

I hope HPE will fix that in a newer firmeware of the raidcontroller

 

i added a screenshot of the downgrad on the esxi server

 

 

 

 

 

 

 

[techy1337]

7.0 U1c - 17325551  HP ISO

 

We got the same problem with DL160 Gen 10's. I only upgrade one server at a time for testing purposes. Upgrading to v3.53 caused the issue and the remaining servers on v3.00 are fine. The only real issue I'm seeing out of these warnings on v3.53 is that the hardware health is no longer updated correctly. Take a look at the last updated date in Hardware Health under the Sensor Tab. This update is causing VMware to no longer pull the correct server health info for me at least. 

[RockyBalboa_]

Thank you Michael ! It works

 

As everyone, we are waiting for a good firmware from HPE... Hope soon !

[shineknoxTN]

Which request did you do, from Michael?  He had an option to downgrade and disable or try driver.  Thanks for the help.

[Michael_LNZ]

Have anyone tryd Smart Array Controller Firmware 3.53 with the new drivers

https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_c9d0851fba6d4775b233f93b7c

Type:	Driver - Storage Controller
Version:	2021.04.01(B) (4 May 2021)
Operating System(s):	VMware vSphere 6.7

 

or

https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_ff8a3aa9a1de4b78ab3ee5d19c

Type:	Driver - Storage Controller
Version:	2021.04.01(B) (4 May 2021)
Operating System(s):	VMware ESXi 7.0

 

if it maybe fixes the problem ?

 

 

 

[JaapHoetmer]

Hi Michael,

I am running this same version (70.4054.2.118-1OEM.700.1.0.15843807), and the problem is still present. Waiting for HPE to deliver a newer version.

Kind regards,

Jaap

[EntreCS]

I too am having this same issue on ESXi 7.0 Update 2. The count of the number of drives in the host is actually only 6 Disks, but I've seen as many as 106 in a status of "Red" while the true 6 have all remained in a Green status. 

Out of curiosity, is anyone else using Veeam 11 to replicate between their host that is seeing this behavior?

[a_p_]

In the meantime, HPE published an advisory with a resolution for this issue.
https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00117054en_us

André

[nihateris]

Hello,
Has this problem been fixed with version 5.12?

[stefanbrun]

any update on this case? have the same error with CheckMK Monitoring Software, but only with one Gen10 server.

[Gothar_svk]

Nothing new, we still use firmware 3.00 for the storage controllers.

It is still the same with SPP 2022.03.0 and ESXi 7.0.3.

PS: the new ilo 5 2.65 fails to report status periodically so Nagios puts alarms to flapping status. We had to downgrade to version 2.55 for now.

[David Nixon]

So after further testing, a workaround has been provided.  Uninstalling the SMX provider, reboot, then let monitoring system fire alarm when it's reman aged.  Clear the alarm and it doesn't re-fire.  At least with SolarWinds, it seems to rember the error state, fire alarm, then perform inventory and then clear the alarm.  Problem is, vLCM will show the image as out of compliance because it's missing the driver.  Additionally, each time you use vLCM to update the drivers from HPE, it would reinstall the SMX provider and you would need to manually uninstall before monitoring is re-enabled.  The SMX Provider is needed for Gen9 and they don't expect it to go away soon.  Hardware monitoring seems to be ok w/o SMX installed on our Gen10+.  I suggested another driver image w/o the SMX provider to be sent to HPE but I don' think HPE really cares about the issue.

[Beny1700]

Same problem here on esxi 7.03

Proliant dl380 Gen10

HPE Smart Array E208i-a SR Gen10
Firmware version 5

[00BaSe00]

Anyone tested Version: 5.32(B) (28 Sep 2022) with DL380 GEN Plus ? Is the error still present?

https://support.hpe.com/connect/s/softwaredetails?language=de&softwareId=MTX_c6530ac4ce4e49f5a0719f8924&tab=revisionHistory

[golfperson]

So far still the same issue with controller firmware 5.32(B), so HPE has still not bothered fixing this over a year later. Version 3.00 remains the latest version without this problem.

This 'resolution' from HPE of removing the smx provider is not acceptable either for multiple reasons:

1. After doing so you cannot view the storage sensor status of the hosts in question
2. As mentioned in this thread, using image-based management in vCenter 7.x leads all hosts to show non-compliant once the vib is removed
3. Updating the hosts again will just re-install it since they continue to provide it in their customizations even though it has this problem..

 

 

[00BaSe00]

I opened a case with HPE and got the following response on the issue:

I have received the following FB from L2 colleagues:

================================================================

Agentless Management System is doing that instead, smx-provider is only intended for usage on Gen 9 systems, and on Gen 10 results in a memory leak and repeated crashes on the ESXi host. However, HPE cannot remove the SMX providers from the HPE Custom Images, vibsdepot or the VMware unified depot deliverables for any Operating System release that still support HPE Gen9

================================================================

[SvenVanRoeyen]

What an unsatifying answer from HPE support. Then they should provide seperate images for Gen9 and Gen10 if they are unable to fix this issue in another way.

[BartD80]

Yeah... for us as customer, HPE is unable to:

- make their ILO command line tools work with the latest ILO firmware. They recommend downgrading while the current version is a critical update. HPE is unable to confirm this as a bug or set a timeframe for a fix

- their own diagnostics runs on completely new servers fail, their solution is to swap the mainboard on a completely new devi

 

- unable to support their HPE Power Protector for Vmware ESXi7, an OS that is out for more than 2 years

- unable to ship replacement parts for server hardware under 24/7 4h maitenance contracts in a timely manner (required at least 5 days to get the part).

Now this driver related fiasco as well... HPE has lost the plot.

[BartD80]

For your interest, the issue is no longer seen with the following ISO version:
VMware-ESXi-7.0.3-21424296-HPE-703.0.0.11.3.0.5-Apr2023.iso

[David Nixon]

I think it cleared for me in the December 2022 driver pack when using vLCM.

[vjrk83]

yes we had to manually remove SMXProvider and updated the cluster image with VMware-ESXi-7.0.3-21424296-HPE-703.0.0.11.3.0.5-Apr2023.iso which has fixed the issues.