HP Server Monitoring with HPE SCOM Integration Kit (x64/x86) v3.1. Overview

Chiyo OdikaOpsMgr, SCOM5 Comments

This is the first article in a series of articles on how to monitor HP Servers and Storage with SCOM. This article will provide an overview of the requirements for installing and configuring the HPE SCOM Integration Kit v3.1. This article is based on the kit that was last updated December 9, 2015. The HPE SCOM Integration kit provides the following for SCOM:

  • Identifies, groups, and displays supported Hewlett Packard Enterprise devices and servers
  • Provides links to lower-level Hewlett Packard Enterprise management tools
  • Displays the properties of supported Hewlett Packard Enterprise devices and servers
  • Monitors the state of supported Hewlett Packard Enterprise devices and servers
  • Identifies, translates, and displays traps/indications/events of supported Hewlett Packard
    Enterprise devices and servers

This kit supports the following versions of SCOM:

  • SCOM 2007
  • SCOM 2007 R2
  • SCOM 2012
  • SCOM 2012 SP1
  • SCOM 2012 R2

The following infrastructure is supported:

image

NOTE: If you manage your Virtual Connects and Blade Enclosures with OneView, you will need a different SCOM Integration kit than that upon which this article is based.

The following servers and operating systems are supported:

image

The integration kit is comprised of the following components:

1. Management Packs

2. Device Monitor Service (DMS): This component acts as a proxy to facilitate communication between management packs and non-Windows monitored devices. It is used by all the HP Management packs. This component requires the following:

  • physical or virtual machjine
  • Windows Server 2003 or later
  • .NET Framework 3.5 SP1
  • PowerShell 1.0 or later
  • SNMP Trap service is installed and enabled
  • SCOM agent is installed and configured
  • HPE SCVMM 2012 console Integration kit is not installed

3. Device Monitor Console (DMC): This component is used to add or remove devices from a DMS. It requires the following:

  • physical or virtual machine
  • Windows Server 2003 or later
  • .NET Framework 3.5 SP1
  • SCOM console (preferred)

The following are supported configurations and environment considerations:

Each component can be installed on the SCOM management server in a small environment

image

 

For larger environments, multiple DMS instances may be required.

image

In the next article, I will review steps for installing and configuring the kit.

Cheers!

The following two tabs change content below.
Chiyo's expertise spans multiple platforms. He holds Microsoft Private Cloud, and Server Infrastructure certifications, and avidly enjoys working on deployments of Microsoft's Server and Cloud Platforms, including Microsoft Systems Center, Windows Server, and Microsoft Azure.

Latest posts by Chiyo Odika (see all)

Chiyo OdikaHP Server Monitoring with HPE SCOM Integration Kit (x64/x86) v3.1. Overview