vLCM => Patches integrate from SECURITY BULLETIN

[erki72]

Hi,

today is the day where the info regarding the AMD CPUs came.
Critical: 
Document - HPESBHF04504 rev.1 - Certain HPE ProLiant AMD Servers Using AMD EPYC Processors, AMD-SB-7008, Cross-Process Information Leak (Zenbleed) Security Notice, Local Disclosure of Information | HPE Support
Document - HPESBHF04504 rev.1 - Certain HPE ProLiant AMD Servers Using AMD EPYC Processors, AMD-SB-7008, Cross-Process Information Leak (Zenbleed) Security Notice, Local Disclosure of Information | HPE Support
and recommended Software Details - Online ROM Flash Component for Windows x64 - HPE ProLiant DL365/DL385/DL385 v2 Gen10 Plus (A42) Servers | HPE Support

From my previous posts, you know that we patch with the vLCM.
Now the question of all questions: How do I go about patching my hosts with the vLCM?
Do I create a custom SPP, load that into Oneview and activate that via OV4VC so that I can patch with vLCM?

[Kashyap02]

Hi 

Yes, you can create a custom SPP and upload it to vLCM and patch it using OV4VC. 
If you have less servers, you can flash the System ROM individually from ILO.

[erki72]

Hi @Kashyap02 , hi all

I've just tried it and, as so often, failed. I made 2 different custom SPP, one bootable and one is not bootable.
I get the same when validating for both SPP`s.

Setings in vLCM:
ESXi Version -  7.0 U3l - 21424296 (released 03/30/2023)
Vendor Addon -  HPE Customization for HPE Servers 703.0.0.11.3.0-5
Firmware and Drivers Addon  - Custom Baseline 2023 8 17 SPP-1.0.703  (The SPP which was created yesterday)

And yes, when creating the SPP, I took Gen10 for these servers and just selected all DLxxx products.
Anyone an idea what could be the problem?