Powered by System Center
SCVMM 2012 – Adding HP iLO as an OOB provider
In the previous post I went into some detail about Out of Band Management (OOB) options in SCVMM 2012 and how bare metal servers can be discovered via an IP range via an OOB provider. After installation of SCVMM 2012 you’ll discover that HP iLO is not a standard option. However a custom OOB provider for HP iLO is offered and can be configured via the following procedure.
First of all we have to download the HP Lights Out Configuration Utility and install it on the SCVMM 2012 server. You can get this utility from HP’s Software and Drivers site and is located under the ProLiant server model and operating system version. If you install this program, take note of the installation directory which defaults to C:\Program Files (x86)\HP\cpqlocfg because next you’ll have to get the HP Lights-Out XML Scripting Sample for Windows. As a third step you must copy the files to same directory where you installed the iLO Configuration Utility.
Make two copies of Set_Host_Power and rename them to Set_Host_Power_Off and Set_Host_Power_On. Change the command <SET_HOST_POWER HOST_POWER=”No” in the first file and to “Yes in the second. Do not change anything else in these files.
Go to the Microsoft Connect site https://connect.microsoft.com/site799/Downloads (You have to register for SCVMM 2012 beta with a Windows Live account) and download the SCVMM 2012 Beta Configuration Provider for HP ILO2. This supplemental download will allow you to control HP servers that doe not support or are not enabled for IPMI out of band management. The file contains a DLL file and a Powershell script:
Copy these files to a directory on the SCVMM 2012 server.
Start a command prompt with Administrator privileges, start powershell and issue the following commands:
get-ExecutionPolicy –> make a note of the current policy
Set-ExecutionPolicy AllSigned
cd [directory of copied *.dll and *.ps1 files)
.\registeroobprovider.ps1 “c:\program files (x86)\hp\cpqlocfg”
Set-ExecutionPolicy Restricted –> or the policy that was configured before changing it
When these steps have completed successfully you’ll need to restart the Virtual Machine Manager 2012 Console or reconnect to it.
We should now be ready to discover bare metal HP servers via the HP iLO2 OOB provider. Go to the Fabric wunderbar, click on Add Resources from the Ribbon and select Hyper-V Hosts and Clusters.
Choose Physical computers to be provisioned into Hyper-V hosts.
If the previous steps were successful you should be able to see HP Integrated Lights-Out (ILO 2) from the OOBE protocol list.
Supply an IP subnet or a range of IP addresses you know the BMC’s should be in and press Next.
As you can see the custom OOB provider for HP iLO 2 works as expected. Although I haven’t tried out yet, you’ll find that the iLO 3 supports one or more of the built-in standard OOB providers so might not have to go through all these steps.
In my next blog I will describe how to Prepare the Host Profile before we reach our final goal: Bare Metal Configuration and Cluster Creation.
If you’ve been successful using the iLO 3 without the custom provider, please leave a comment.
| Print article | This entry was posted by Hans Vredevoort on April 15, 2011 at 08:10, and is filed under Hans Vredevoort, System Management. Follow any responses to this post through RSS 2.0. You can leave a response or trackback from your own site. |
Whitepaper with some important Hyper-V best practices
about 2 days ago - No comments
A while ago Savision asked me if I would help to write a whitepaper about Hyper-V best practices for them. Of course I said yes to this request and wrote some chapters for the whitepaper. Last week we’ve made the whitepaper final. This whitepaper is neither a tutorial nor step-by-step handbook for common problems. Rather,
HP ProLiant Gen8 Tech Tour
about 1 week ago - No comments
Tomorrow I will fly to Houston from San Diego where I have been staying for a few days after a great TEC2012 event. HP asked me to join them for their HP ProLiant Gen8 Tech Tour. Coming all the way from Europe just for the 2 days would have been crazy, but as I was
VSS Crash-Consistent vs Application-Consistent VSS Backups (1)
about 2 weeks ago - No comments
I can recommend an interesting 2-part series of blogs which helps you get a better understanding of the theory behind successful backups. In the first blog on Altaro’s Hyper-V blog, VSS Crash-Consistent Backups are compared to Application-Consistent VSS Backups. When designing any IT solution, many administrators often consider “Backup” to be little more than another
VHDX Specification Now Available
about 2 weeks ago - No comments
Windows 8 and Windows Server 2012 Hyper-V support the new VHDX Virtual Hard Disk format. If you are interested in the technical details just became available and you can download the VHDX specification: http://www.microsoft.com/en-us/download/details.aspx?id=29681 This specification is released under the Microsoft Open Source Promise (OSP) initiative to help guide development of VHDX virtual hard disk
Virtual Machine Migration Toolkit
about 3 weeks ago - 1 comment
Microsoft at MMS 2012 announced a new toolkit for mass conversion of VMware VM’s to Hyper-V. VMMT is wizard based conversion tool aimed at conversion from VMware to the current version of Hyper-V. Windows Server 2012 support is still under development. Please note that this is a different tool from the Microsoft Solution Accelerator called
Windows 8 Storage & Hyper-V Part 5 – SMB 3.0 and ODX in NetApp
about 1 month ago - 2 comments
[Update: Since I wrote this blog the version of SMB has been updated from 2.2 to 3.0 to reflect the vast amount of changes in the protocol] Today was my first day at MMS2012 in Las Vegas. It is the event for Microsoft System Center and the new 2012 version of the product is inseparable
Windows 8 Storage & Hyper-V part 4 – Offload Data Transfer (ODX)
about 1 month ago - No comments
This is another installment in my series on Windows 8 Storage & Hyper-V. Previous blogs in the series can be found here: Part 1 – Introduction Part 2 – VHDX and PowerShell Part 3 – The Art of Creating a VHD Another promising new storage functionality that can be found in Windows Server 8 is
Windows 8 Storage and Hyper-V – Part 3: The Art of Creating a VHD
about 1 month ago - 1 comment
In the last blog in my series on Windows 8 storage I already touched upon creating a VHDX with PowerShell 3.0 in Windows Server 8. In this blog I will focus on the subject a little bit more, showing the myriad ways of creating VHDs and show you some powerful commands to create multiple VHD
Analysis of Hyper-V.nu blog statistics
about 1 month ago - No comments
Exactly one year ago Jaap Wesselius and I decided to give our Hyper-V.nu site a new look and we started to combine our blogs. On April 1st, Peter Noorderijk and Maarten Wijsman joined the team and started writing their blogs for Hyper-V.nu. Jaap is primarily occupied with Exchange but writes an occasional blog. We all
Windows Server “8” Beta Hyper-V Component Architecture Poster
about 2 months ago - No comments
This poster provides a visual reference for understanding key Hyper-V technologies in Windows Server “8” Beta and focuses on Hyper-V Replica, networking, virtual machine mobility (live migration), storage, failover clustering, and scalability. You can download the poster from the Microsoft download site.







Twitter
RSS
about 1 year ago
Hi
Great blog post here. I too have tried this very process. However, when attempting to discover devices, I get a message saying that a device could not be discovered. I can see that the script is running corretly as a file is generated the the HP iLO Configuration Utility directory with the details of the device, and I can see an XML Login and XML Logout in the iLO log on the server. Have you come across such issues, or is this something which I am doing incorrectly.
Cheers
Shaun
about 1 year ago
Hi again
Just bought I’d let you know that I managed to resolve the issue. It was down to the firmware revision of the lights-out board. The was a 2007 version – 1.7 I believe. I upgraded this yesterday to version 2.05, and it was discovered immediaty. There must be something in the response from the ilo that VMM expects which is not in the response from earlier version of the firmware.
Keep up the great blog.
Cheers
Shaun
about 1 year ago
Thanks for adding that Shaun!
about 1 year ago
Are you aware of any providers for Dell blade servers?
about 1 year ago
Hi Robbie,
Dell DRAC uses IMPI 2.0 protocol. Although I haven’t tried you have a good chance of being able to use the standard BMC providers in SCVMM 2012
See also: http://www.dell.com/downloads/global/power/ps3q06-20050317-Zhuo.pdf
Cheerz, Hans