Secure Boot

[NZamp]

Hello guys,

i have a pair of new SimpliVity nodes deployed at a customer site. Now i get the error "Host TPM attension alarm".

Normaly i would acitvate Secure boot and all the TPM stuff needed but i´m unsure if this can also be done withe the SimpliVity nodes or if this isn´t supported.

i´ve found the following:

https://community.hpe.com/t5/hpe-simplivity/secure-boot-with-simplivity/m-p/7170783#M3429

but the answers is one time YES and one time NO so this doesn´t clarify the problem

So what is true?

Best regards,

Nick

[FabrizioDV · Accepted solution]

from this document : HPE OmniStack 4.2.0 for vSphere Release Notes.pdf

link : https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00131390en_us 

[NZamp]

Hello Fabrizio,

secure boot is not supported, got it

Thanks for clarifying answer.

Best regards,

Nick

[Sunitha_Mod]

Hello Nick, 

We are glad to know your concern has been addressed. 

[Matt4istal]

VMware ESX 9 "Unable to acquire ownership of TPM 2.0 device. Please clear TPM through the BIOS." on HPE DL380 Gen11 server solution.
The solution was a 4-step process in the HPE DL380 Gen11 server BIOS. The configuration steps that fixed the TPM issue with VMware in this case were as follows:

Step 1 – Enable Secure Boot in System Configuration > BIOS/Platform Configuration (RBSU) > Server Security.
Reboot server.
Step 2 – Enable the following Advanced Trusted Platform Module Options in System Configuration > BIOS/Platform Configuration (RBSU) > Server Security > Trusted Platform Module Options
• TPM UEFI Option ROM Measurement: Default = Disabled --> Change to Enabled
• TPM 2.0 Endorsement Hierarchy: Default = Disabled --> Change to Enabled
• TPM 2.0 Storage Hierarchy: Default = Disabled --> Change to Enabled
Reboot server.
Step 3 – Clear the TPM in System Configuration > BIOS/Platform Configuration (RBSU) > Server Security > Trusted Platform Module Options > TPM 2.0 Operation
Step 4 – Perform a Cold Boot of server (full power off and back on) to clear the TPM.

After performing these 4 steps, the TPM attestation alert message was cleared in vCenter on the ESX 9 hosts. (Note: Also have to disconnect / reconnect each host to vCenter since the TPM settings were changed on hosts that were already joined to vCenter in order to clear attestation failed messages that were in the "Cluster -> Security" menu).