HP Agentless Monitoring with SCOM 2012 R2

 

I recently visited a customer who wanted to implement the HP Agentless Monitoring Management Pack in their environment. I hadn't used this pack before and I couldn't find much (easy reading) online about the requirements or installation procedure therefore it required quite a bit of research to fully understand what is required to use it. Here's a high-level overview:

1. Install the HP Device Monitoring Service (DMS) on a utility server, ideally not on any of your management servers, but some other suitable Windows server.
2. Deploy the SCOM agent to the server that is running the DMS service. See step #1 above.
3. Install the HP management packs required for agentless monitoring. Import them using the SCOM Management Console.
4. Install the HP Device Monitoring Console (DMC) on one or more servers. (This can be installed on your management servers if you wish, and/or the utility server from step #1. This will enable you to launch the DMC tool from a task within the SCOM console if you want. )
5. Run the DMC tool to register your HP servers with their iLO interface addresses.
6. The SCOM agent on the utility server (from step #1) communicates with the DMS service to discover the registered iLO interfaces/servers. Once the SCOM agent adds the interfaces into inventory, the monitoring workflows being.

Step by Step: (Environment: SCOM 2012 R2 UR3)

Download the latest OneView ISO image from HP. At the time of this writing, this is what I have: HP_OneView_for_Microsoft_System_Center_7.4_July_2014_Z7550-01413.iso

Burn the ISO to disc or use either WinRAR or the "Mount" feature of Windows 2012 to get at the contents of the ISO.

Extract this folder:  "HP SCOM Management Packs". Inside this folder there two exe files; one for x86 and x64. You know which one you need.

 

On a utility server (not a SCOM management server) run the HP intall program (HPSCOMManagementPacks-x64.exe). Install only the DMS service and the DMC component.

*NOTE: For the DMS service/component make sure you have the prerequisites installed: .NET 3.5, SNMP Trap Service (and it is "Enabled"), and at least Powershell v1.0.

 

Deploy the SCOM agent to the utility server.

On a SCOM management server, run the HP install program (HPSCOMManagementPacks-x64.exe) and choose to extract the HP management packs. Optionally you can choose to install the DMC. This tool could prove to be useful on the SCOM management server.
Import these three management packs using the SCOM Management Console:

1. HewlettPackard.ProLiant.Monitored.Agentless.mp
2. HewlettPackard.ProLiant.Monitored.Library.mp
3. HewlettPackard.Servers.Library.mp

 

 

Connect to the HP Device Monitor Console (DMC). If you have trouble connecting to the console, look for this log file:

C:\Program Files\HP SCOM Management Packs \ HP Device Monitor Service\HPDeviceMonitor.log

You may have to launch the DMC as an "Administrator" or you may run into the error shown below:

2015-09-14 14:57:17.9588 HPDeviceMonitor 1800:5 WARN
CheckUser User not authorized to access the HP Device Monitor Service.

Run the DMC tool to register your HP servers with their iLO addresses, use the "Add Agentless Server" task.

HP Servers eventually get discovered. This may take a few minutes.

 

That's about all there is to it. Please let me know if you have suggestions to improve this post.

 

2017.6.7: added additional text to clarify some of the steps.
2015.9.14: added a note about the prerequisites for the DMS service/component

Comments

• Anonymous
  October 10, 2015
  Hi Thanks for helpful guide. i have a question. when i click on 'add agentless server' need community string. what shall i do?

• Anonymous
  November 12, 2015
  Hi Paul, Does this solution require the purchasing of HP OneView licenses? Thanks

• Anonymous
  November 12, 2015
  @Nigel: not that I know of.

• Anonymous
  December 01, 2015
  Hi Paul, Is it suppose to work with ILO 2 ? Thank you

• Anonymous
  April 05, 2016
  This is almost perfect .. 'cept "add agentless server" need a community string, and cannot find information on how to set this, or what the default should be

• Anonymous
  April 05, 2016
  Answer to SNMP community string .. set it in iLO .. GRRR!

  • Anonymous
    April 07, 2016
    The comment has been removed
    • Anonymous
      June 23, 2016
      The comment has been removed
      • Anonymous
        July 13, 2016
        @Bryan, I don't have access to those servers to research this. However, if you provide more info about your servers you may get responses from others in the community on this issue.
      • Anonymous
        July 27, 2016
        I configure the Read Community in the iLO -> Management -> SNMP Settings. This works for me. You should have the admin rights to configure the iLO.