topic Re: SimpliVity BIOS settings not as recomended in HPE SimpliVity

SimpliVity BIOS settings not as recomended

jlangmead — Wed, 26 Mar 2025 04:04:33 GMT

Hello all

We've just deployed a small number of 2-node clusters and are now recieving an vCenter critical alert from one node within one of the clusters saying the BIOS settings are not as recommended. I undertsand this is a new feature and also that it is indicating the BIOS settings on this node are not configured correctly. My question is how I then identify which BIOS setting is incorrect so I can remediate the alert?

Is there a published set of BIOS settings I can reference? Each cluster deployment has been deployed and configured the same so I also don't know why this single node should be different from the others (which are not showing any alerts).

I don't really want to have to check every BIOS setting with a 'working' node - but is this the only way to fix the alert?

These are Gen11 servers, I've found a document for recommended BIOS settings for Gen10 servers - would this be the same??

kind regards

Re: SimpliVity BIOS settings not as recomended

Kipp_Glover — Tue, 25 Mar 2025 21:55:22 GMT

Good day jlangmead,

What Gen11 nodes do you have? 380 Gen11 or 325 Gen11. Also, what version of OmniStack did you install? There is an issue that is fixed in the next OmniStack release, 5.3.1, that is coming in April. The fix is to prevent some of the VCenter alert and allow others to be ignored. In the attached guides, you can find the default BIOS settings for both Gen10 and Gen11 nodes. With the release of 5.3.1 these guides will be posted on the HPE Support Center. Looks like I am not allowed to attach documents here. Let me try to DM them to you.

/Kipp

Re: SimpliVity BIOS settings not as recomended

jlangmead — Wed, 26 Mar 2025 06:53:17 GMT

Hi Kipp
We have 4 clusters. 2 are using DL325s Gen11 and the other 2 are using DL380 Gen 11. All clusters are two-node only. We have a single Federation annd are running version 5.2 on the OVCs and also for the plug-in. The latest firmware bundle has been deployed throughout.
As an update- we have since rebooted every host an now all hosts are showing this alert

Many thanks
Jon

Re: SimpliVity BIOS settings not as recomended

ICPMuenchen — Thu, 27 Mar 2025 07:08:29 GMT

the error appears when you have optimal cooling selected in Bios/iLO thats why the error appears in vcenter.

in early times maximum cooling was the default settings. it has changed some years ago, where also optimal cooling is allowed to be used.

just reset the sensor to green in vcenter and everything is fine for the moment.

but glad to know there will be a fix in next SVT Update

Re: SimpliVity BIOS settings not as recomended

jlangmead — Sat, 29 Mar 2025 08:05:20 GMT

Thanks Peter
This turned out to be one of the settings due to be updated in the next release. So for now I can just acknowledge the alert and reset it to Green
Thanks

Re: SimpliVity BIOS settings not as recomended

Marto20635 — Tue, 08 Apr 2025 07:48:15 GMT

@Kipp_Glover

can you send me the information please

Re: SimpliVity BIOS settings not as recomended

Kipp_Glover — Tue, 08 Apr 2025 13:31:26 GMT

Hi Marto20635, I sent you a direct message last week.

/Kipp

Re: SimpliVity BIOS settings not as recomended

TechISO33 — Fri, 11 Apr 2025 07:11:46 GMT

Hello I have the same problem can you send me the the document too please ?

Re: SimpliVity BIOS settings not as recomended

Kipp_Glover — Fri, 11 Apr 2025 14:18:32 GMT

Yesterday, a Customer Advisory was released for this issue. Here is the link: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00147454en_us

Cheers!
/Kipp

Re: SimpliVity BIOS settings not as recomended

Selector — Tue, 26 Aug 2025 09:16:44 GMT

I have recently deployed Simplivity 380 Gen11 cluster with 5.3.1.

The healthcheck alarms were raised about the following setings:

1. DeadBlockPredictor changed from Enabled to Disabled;

- this one I will change to enabled manualy

2. ThermalConfig changed from OptimalCooling to EnhancedCPUCooling;

- this is actually a recommended setting as per the documentation:

HPE SimpliVity 380 Gen11-specific BIOS/Platform Configuration (RBSU) Settings | HPE SimpliVity 5.3.1 for vSphere Documentation

3. UncoreFrequencyMIN changed from 0 to 22;

4. UncoreFrequencyMAX changed from 0 to 22.

- this last two I could not find in BIOS or the doc but see only "Uncore_Frequency_Scaling to Maximum setting" which is already set.

After making the change, I will have to disable this alarm, at least until the next svt release

Re: SimpliVity BIOS settings not as recomended

Stefano_Colombo — Tue, 02 Dec 2025 13:46:00 GMT

Hello,

I just upgraded to 5.3.1.8 and the alarm is still happening, I thought it would have been fixed in 5.3.1.

The warning is as below
The following BIOS attributes of the host differ from HPE SimpliVity recommended values: PowerRegulator changed from StaticHighPerf to OsControl; RedundantPowerSupply changed from HighEfficiencyAuto to BalancedMode; Slot10NicBoot1 changed from NetworkBoot to Disabled; Slot1NicBoot1 changed from NetworkBoot to Disabled; NvmeOptionRom changed from Disabled to Enabled; PostDiscoveryMode changed from ForceFullDiscovery to Auto; ThermalConfig changed from OptimalCooling to IncreasedCooling.

Can we still safely ignore them ?

thanks

Re: SimpliVity BIOS settings not as recomended

egoqed — Mon, 19 Jan 2026 10:43:50 GMT

May an update for those who still search. Official HPE case statement

This is actually a known issue with a new SimpliVity Alarm defined in vCenter which was implemented with SVT 5.2.0 (and further) as a feature. Even that the current configured BIOS settings are the same as recommended sometimes there are some BIOS attributes which differs and that is causing the alarm to appear. This can be ignored.
See detailed description in blow documents:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00147454en_us&docLocale=en_US
https://support.hpe.com/hpesc/public/docDisplay?docId=sf000105763en_us&docLocale=en_US
Unfortunately it seems that this was not fixed in 5.3.1 and it is already escalated internally with us.
For now you can use both workarounds -acknowledge these alarms or disable the alarm in vCenter.
Note: If you decide to take the option with acknowledging that alarm, please note that it will appear after each monthly health check or after server reboot and will need to be acknowledged again!

Best regards
EgoQED