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)HPcpqlocfg 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.

image

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.

imageimage

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:

image

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)hpcpqlocfg”
Set-ExecutionPolicy Restricted –> or the policy that was configured before changing it

image

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.

image

Choose Physical computers to be provisioned into Hyper-V hosts.

image

If the previous steps were successful you should be able to see HP Integrated Lights-Out (ILO 2) from the OOBE protocol list.

image

Supply an IP subnet or a range of IP addresses you know the BMC’s should be in and press Next.

image

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.

7 Comments

  1. April 22, 2011    

    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

  2. Shaun Laughton's Gravatar Shaun Laughton
    April 24, 2011    

    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

  3. adminHans's Gravatar adminHans
    April 25, 2011    

    Thanks for adding that Shaun!

  4. April 30, 2011    

    Are you aware of any providers for Dell blade servers?

  5. adminHans's Gravatar adminHans
    May 1, 2011    

    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

  6. November 2, 2012    

    Hi Hans

    Currently going though all your post on BMC in SCVMM 2012 – GREAT STUFF!

    one question…

    Do i need to buy the HP ILO license for SCVMM 2012 to be able to push the install?

    You know the license that gives you the option to controle to the server completly? I seem to remember the default license that follow basicly only allows you to power on and off the server…

    /Casper

    • adminHans's Gravatar adminHans
      November 10, 2012    

      You only need the ILO license if you want to take over the server in the GUI and for virtual DVD I think. Just give it a try!

  1. SCVMM 2012 – Out of Band Management (OOB) | Hyper-v.nu on April 17, 2011 at 12:48
  2. System Center VMM 2012 [Beta] Resources - MSDN Blogs on July 3, 2011 at 21:02
  3. How to Bare Metal Deploy a Hyper-V server via VMM2012 and HP iLO | Hyper-v.nu on November 8, 2011 at 20:53

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>