HPE OneView
1823997 Members
3531 Online
109667 Solutions
New Discussion

Frustration with Gen11 and Oneview

 
Chris_Coates
Advisor

Frustration with Gen11 and Oneview

Our number of Gen 11 (Proliant and Synergy) keeps growing and I am a bit frustrated by something that probably has an easy fix. 

Every time the servers reboot or I do and ILO update I get the following 3 alarms in oneview

 

Profile alert -  Server profile settings conflict with the server hardware configuration. - I have to refresh to profile on each server to get it to clear.

 

Profile Alert - BIOS settings do not match the expected values. - I have to reaply the BIOS setting on each server when this happens. - This seems worst on Synergy.

 

Hardware warning - Platform Configuration Register(PCR) has changed. The firmware component type for the detected changed is iLO at PCR index PCR0  - This one I have to individually clear the alert on each server. 

 

Is there a Oneview, ILO, or BIOS setting to prevent these?  Thanks

 

 

5 REPLIES 5
Rakesh0404
HPE Pro

Re: Frustration with Gen11 and Oneview

Hi, 

Please find the Advisory for the mentioned error : https://support.hpe.com/hpesc/public/docDisplay?docId=a00136896en_us&docLocale=en_US 



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
Rakesh0404
HPE Pro

Re: Frustration with Gen11 and Oneview

Hi Chris, We wanted to follow up and check if the links provided to you addressed the issue. Request you to please respond with a Yes/No. You may also click on "Accept as a solution" button if the issue is resolved.



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
ChrisLynch
HPE Pro

Re: Frustration with Gen11 and Oneview

Rakesh provided a link to the PCR alert.  This is the TPM changing states as firmware is updated.  

Can you share what version of HPE OneView you have in your environment?

I work at HPE
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
diegoaze
Visitor

Re: Frustration with Gen11 and Oneview

Hi Chris!

In my case, I can confirm the issue is NOT related to firmware update. It happens every time a blade is powered on. The advisory a00136896en_us suggests the issue should be investigated prior to clearing the alert. I raised a ticket with support and was told to simply clear the alert (obviously less than ideal).

It appears this issue is dragging along for over a year, from the posts I found online. Also, the advisory doesn't indicate if this is being currently looked into and would be addressed in a future release of Oneview/SSP/iLO update.

Environment details:

Oneview: 9.30
SSP: 2024.11.02
Workload Profile: Virtualization - Max Performance
ESXi 8.0 U3

All Gen11 blades. Issue happens on all blades in two separate rings.

Changing below BIOS Setting seems to make the warning go away though:
Current TPM 2.0 Active PCRs
From: SHA256 and SHA384 (which is the default option)
To: SHA1 and SHA256

Just wondering if you would you be able to confirm:

  1. Why the change clears the alert
  2. The impact of this change
MarioE
Trusted Contributor

Re: Frustration with Gen11 and Oneview

Hello

I have these errors with every new Gen11 server.
But the error only occurs as soon as an OS is installed. It does not matter whether it is VMware, Microsoft Windows or SuSE. The error occurs after every reboot once the OS is installed. The error does not occur if I set the BIOS parameter
Current TPM 2.0 Active PCRs from
“SHA256 and SHA384”
to
“SHA1 and SHA256”
(TpmActivePcrs=Sha256Sha384 to TpmActivePcrs=Sha1Sha256)
-> Re: PCR Measurements Changed, Component Type BIOS ... - Hewlett Packard Enterprise Community
Even after a firmware update, the error no longer occurs.

No information or an advisory is to be expected from HPE here, except that the alert should be deleted!?