Update ESXi on HPE server with CLI

[BE MCO]

Currently we are running ESXi 7.0 Update 3 with Image profile (Updated) ESXi-7.0U3c-19193900-standard (Hewlett Packard Enterprise) on our ProLiant ML350 Gen10 server. We want to update to the latest version and are planning on doing so with the following command: 

esxcli software profile update -p ESXi-7.0U3s-24585291-standard \

-d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

 

Can anyone tell me if this will give any problems with the installed HPE drivers or isn't it a problem to update the host this way?

 

Thanks in advance!

[Andrea Consalvi]

Hi,

I’ve been in this exact situation before. If you're currently running an HPE custom image and you're planning to update using the vanilla VMware profile (ESXi-7.0U3s-24585291-standard), yes it will technically work, and your host will boot and run fine.

But here’s the catch:

The update might remove or overwrite some of the HPE-specific VIBs, like amsd, iLO drivers, or Smart Array components.

If you rely on HPE tools for hardware monitoring or ILO integration, you could lose that functionality unless you manually reinstall those VIBs afterward.

Now, if you're just looking to apply the latest patch and don't depend on HPE monitoring agents, it's fine to go ahead with the standard image. I’ve done it myself on non-critical hosts.

You can also check what's installed before and after with:

esxcli software vib list | grep -i hpe 

And list the latest HPE profiles (if they exist) using:

esxcli software sources profile list -d https://vibsdepot.hpe.com/index.xml 

So yes, the command you posted is valid

[Daniel Scasso]

Adding to Andrea, 

You can patch it with Base ESXi 7U3n, then patch it to U3s.

Then you can download the HPe Add-On, and that will then add any missing HPe VIB to the latest release.

[Andrea Consalvi]

Exactly Daniel.

[BE MCO]

Is there a specific reason why I would need to patch to U3n first? And I assume with the following command?

esxcli software profile update -p ESXi-7.0U3n-21930508-standard \
-d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

What exactly is this 'HPe Add-On'? Where can I find it? And how to use it?

[Daniel Scasso]

I don't know why i understood you were coming from U1 or U2 release, that forces you to go to the latest BASE build uploaded by Broadcom and that's build N.

In your case go straight to latest release S as it covers the last 3 CVEs found on VMware code.

The HPE Add-on latest release in the OEM Addons tab in the ESXi download page on BroadcomSupport Site:

https://support.broadcom.com/group/ecx/productfiles?displayGroup=VMware%20vSphere%20-%20Standard&release=7.0&os=&servicePk=202624&language=EN&groupId=204411&viewGroup=true

I normally check the add-on release every 6 months just in case they made any new release (it could be 1 or none in a year).

[BE MCO]

Thank you for your response!

[BE MCO]

1. In case updating through the online repository doesn't work, should I be able to apply the update by following the next procedure?

2. And is vmware-esxi-7.0U3s-24585291-depot.zip the right file?

 

- Upload vmware-esxi-7.0U3s-24585291-depot.zip to for example /vmfs/volumes/datastore1/

- Put Host into Maintenance Mode

- Run: esxcli software profile update -d /vmfs/volumes/datastore1/VMware-ESXi-7.0U3s-24585291-depot.zip -p ESXi-7.0U3s-24585291-standard

- Reboot

[BE MCO]

1. In case updating through the online repository doesn't work, should I be able to apply the update by following the next procedure?

2. And is vmware-esxi-7.0U3s-24585291-depot.zip the right file?

 

- Upload vmware-esxi-7.0U3s-24585291-depot.zip to for example /vmfs/volumes/datastore1/

- Put Host into Maintenance Mode

- Run: esxcli software profile update -d /vmfs/volumes/datastore1/VMware-ESXi-7.0U3s-24585291-depot.zip -p ESXi-7.0U3s-24585291-standard

- Reboot

I tested this and can confirm this works and is the right image.

[BE MCO]

Someone from another forum stated the following:

Why don't you use the HP Image, which should have released a 7.0 U3 image in Feb 2025. Then you also include the extra components and drivers that that image added when installing the host. 

Now you have updated EXSI, but not the manufacturer-specific components, which can also lead to incompatibility or even security risks.

Or update the HP-specific components via the HP Depot: https://vibsdepot.hpe.com/

I didn't see anyone talk about this. Is this because of many people aren't aware of this or isn't there serious risk involved?