- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: conrep does not really switch BIOS settings
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-22-2013 02:41 AM
07-22-2013 02:41 AM
conrep does not really switch BIOS settings
Hi community,
we use conrep v3.30 to enable the BIOS settings necessary for Hyper-V usage
on Proliant DL380p Gen8, that are:
No_Execute_Memory_Protection -> enabled
CPU_Virtualization -> enabled
Intel_VT-d2 -> enabled
Reading the values with conrep subsequently shows success.
However Hyper-V is not working after reboot.
Entering BIOS manually, disabling the values mentioned above, enabling them again - all manually -
results in Hyper-V working after the boot process has been completed !
Does anyone have a hint how to avoid this huge amount of manual work on dozens of servers ?
Thanks and best regards,
Erwin
- Tags:
- bios
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-22-2013 10:17 PM
07-22-2013 10:17 PM
Re: conrep does not really switch BIOS settings
Hi,
There could be two suspects here, one is the BIOS version and the other the version of CONREP.
Check the BIOS version in your server and see if there is any update available with HP that fixes this issue.
Also take a look at this article.
Thank You!
I am a HP employee.
I work for HPE.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-23-2013 07:01 PM
07-23-2013 07:01 PM
Re: conrep does not really switch BIOS settings
conrep v3.30 should work just fine on a Gen8. What is the contents of the data file your using with conrep?
I'm also pretty sure the default values of those 3 settings is enabled? Are these new systems, or something being re-purposed?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2013 02:05 PM
10-02-2013 02:05 PM
Re: conrep does not really switch BIOS settings
hi
for gen8 proliants you should use HPRCU.exe (HP rom configuration utility) which is included in the scripting toolkit.
best regards
ernesto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2013 11:49 AM
12-09-2013 11:49 AM
Re: conrep does not really switch BIOS settings
Related to this question, I have a customer who ran "hprcu" when they were running BIOS version P 74 on an SL-230 Gen 8 but noticed that some settings went away when they updated BIOS to P 75 (09/2013, I believe).
I recommended that they re-run hprcu -s again when updating BIOS on a "golden" node and then push the settings out again across their HPC cluster to ensure all nodes were set exactly the same.
Is there a better way to use this tool to audit *.xml file changes when upgrading BIOS revisions?