Type
  • Best Practice
Description
  • This article describes the different HP agents available to monitor HP ProLiant servers running Linux, Solaris, Windows, or VMWare ESX.
Additional Keywords
  • HP, HP ProLiant

Related Topics

Knowledge Base

Monitoring an HP ProLiant Server running Linux / Solaris / Windows / VMWare ESX

KB1038 - Sep 06, 2010 - Last reviewed on Dec 07, 2016

1. Choose an Appropriate HP Agent

Different hardware monitoring agents are available for HP servers running Linux, Solaris, and Windows. Depending on the server model, operating system and available protocols, you will have to choose between these HP agents:

To ensure proper functioning of the Hardware Agent, the version of the Hardware Agent should be newer than the server, Operating System and preferably the Server's firmware revision.  Using a Hardware agent whose release date is older than the server / Operating System / Firmware usually results in failed installation or incomplete monitoring.

HP Insight Management Agents for Windows Server (HP's SNMP based hardware agent for Windows):

Available for all supported versions of Windows, it requires Windows's SNMP service to be installed. 
The following connectors are used in conjunction with this agent:

  • HP Insight Management Agent - Server                             
  • HP Insight Management Agent - iLO
  • HP Insight Management Agent - Drive Array    
  • HP Insight Management Agent - Fiber Array
  • HP Insight Management Agent - HBA                  
  • HP Insight Management Agent - IDE Storage
  • HP Insight Management Agent - SCSI Storage  
  • HP Insight Management Agent (v8.25 or higher) - Memory
  • HP Insight Management Agent (v8.20 or lower) - Memory

HP Insight Management WBEM Providers for Windows Server (HP's WMI based hardware agent):

This agent is only available for newer HP servers running recent versions of Microsoft Windows (2003/2008).

The following connector is used in conjunction with this agent:

  • HP Insight Management Agent - Server - WMI

HP SNMP Agents (hp-snmp-agents) HP System Health Application and Command Line Utilities (hp-health) (HP's SNMP based hardware agents for Linux):

Available for all supported versions of Linux, it requires appropriate SNMP daemon to be installed before installing the agent.
The following connectors are used in conjunction with this agent:

  • HP Insight Management Agent - Server
  • HP Insight Management Agent - iLO
  • HP Insight Management Agent - Drive Array    
  • HP Insight Management Agent - Fiber Array
  • HP Insight Management Agent - HBA                  
  • HP Insight Management Agent - IDE Storage
  • HP Insight Management Agent - SCSI Storage  
  • HP Insight Management Agent (v8.25 or higher) - Memory
  • HP Insight Management Agent (v8.20 or lower) - Memory

HP Insight Management WBEM Providers for Linux and VMware ESXi Distribution (hpmgmtbase  and hp-smx) - HP's WBEM based hardware monitoring agent:

This agent is only available for newer HP servers running recent versions of Linux (RH5 / SLES 11). 

The following connector is used in conjunction with this agent:

  • HP Insight Management Agent – Server - WBEM

HP ProLiant Insight Management Agents for Solaris (HP's SNMP based hardware agents for Solaris 10):

Available for approximately 40 HP servers on which Solaris is a supported operating system, it requires net-SNMP to be installed and working before installing the agent. The following connectors are used in conjunction with this agent:

  • HP Insight Management Agent - Server                             
  • HP Insight Management Agent - iLO
  • HP Insight Management Agent - Drive Array    
  • HP Insight Management Agent - Fiber Array
  • HP Insight Management Agent - HBA                  
  • HP Insight Management Agent - IDE Storage
  • HP Insight Management Agent - SCSI Storage  
  • HP Insight Management Agent (v8.25 or higher) - Memory

HP Management Agents for VMware ESX (HP's SNMP based hardware agents for Solaris 10)

Available for approximately 40 HP servers on which Solaris is a supported operating system, it requires net-SNMP to be installed and working before installing the agent. The HP Management Agents for VMware ESX only works with RedHat based versions of ESX.  ESXi and some versions of ESX servers are BusyBox based and cannot have additional agents installed on them. HP servers running ESX or ESXi can also be monitored using VMWare's built in WBEM based hardware monitoring system.  See the "Monitoring VMWare ESX/ESXi" Knowledge Base article on Sentry Software's website.
The following connectors are used in conjunction with this agent:

  • HP Insight Management Agent - Server                             
  • HP Insight Management Agent - iLO
  • HP Insight Management Agent - Drive Array    
  • HP Insight Management Agent - Fiber Array
  • HP Insight Management Agent - HBA                  
  • HP Insight Management Agent - IDE Storage
  • HP Insight Management Agent - SCSI Storage  
  • HP Insight Management Agent (v8.25 or higher) - Memory

2. Download the HP Agent

  1. Go to www.hp.com
  2. Under Support & Drivers, click Drivers & Downloads
  3. Enter the server model you wish to monitor.
  4. Select the Operating System
  5. Select "Software - System Management"
  6. Download the required HP Agent

3. Install and Configure SNMP

Windows Settings

The SNMP service will need to be installed and configured before installing the HP Insight Management Agents for Windows Server. SNMP does not need to be installed when using the HP Insight Management WBEM Providers for Windows Server agent. See Microsoft's documentation for information about how to install the SNMP service.

The community string should be specified under the security tab of the SNMP service configuration page. If the option "Accept SNMP packets from these hosts" is selected, all hosts from which monitoring is done should be specified.  In the case of local monitoring using the KM this should be local host. For remote monitoring using the PM, all RSMs should be specified.

Linux and Solaris Settings

For most Linux distributions, the net-snmp service will need to be installed before installing the HP Agent. See the documentation for the Linux Distribution for information about how to install net-snmp.
The configuration of the SNMP service is done after the installation of the HP Agent.

IPMI Driver (Linux) Settings

In order for the HP agent to collect environmental information from the BMC chip (Power Supply Status, Fans Speed, Temperatures, Voltages) a valid IPMI driver must be installed. 

On Windows systems, the IPMI driver is either incorporated into the Operating System or is installed automatically during the HP Insight Manager Agent installation.

Most recent Linux systems have the open-source OpenIPMI driver installed by default which the HP Insight Manage agent can use. 
HP have a customized version of the OpenIPMI agent, called  hp-OpenIPMI, which has been enhanced to better work with HP hardware in addition to supporting a PCI Base Management Controller.  We would recommend installing hp-OpenIPMI driver should there be any issues with Power Supply, Fans, Temperature, Voltages or iLO monitoring.

4. Install the HP Agent

Windows Settings

See instructions included with the installation files.

Linux Settings

See instructions included with the installation files.

For HP's SNMP based hardware agents for Linux:

  1. Install the HP System Health Application and Command Line Utilities (hp-health), then HP SNMP Agents (hp-snmp-agents).
  2. After installing the agent check the status of the HP SNMP Agent: /etc/init.d/hp-snmp-agents status
  3. To configure the snmp service and to integrate it with the HP agent, run the following command: /sbin/hpsnmpconfig
  4. This will create a new /etc/snmp/snmpd.conf.  In this file, the following line should be added, which links the HP agent to the main SNMP daemon:
    • (64-bit OS) - dlmod cmaX /usr/lib64/libcmaX64.so
    • (32-bit OS) - dlmod cmaX /usr/lib/libcmaX.so

Solaris Settings

See instructions included with the installation files.
The SNMP service will be reconfigured as part of the installation.

5. Configure Hardware Sentry KM for PATROL

In the PATROL Console

To add the monitoring of a remote HP ProLiant server:

  1. Right-click the Hardware icon and select KM Commands > Add a Remote System or an External Device...
    Adding a Remote Host — System Identification

    Adding a Remote Host — System Identification

  2. Identify the HP ProLiant server you want to monitor remotely:
    • System or Device name: Enter the name of the HP ProLiant server you wish to monitor. In our example: “fermat-sp2010” (a HP ProLiant BL260c G5 server).
    • IP address or fully qualified name: Enter the IP address or the fully qualified name of the HP ProLiant server you wish to monitor. You can leave this field blank if you specified the host name in the System or Device name field and it’s resolvable by your DNS/hosts file.
    • From the System or Device type drop-down list, select the system type used by your HP ProLiant server. In our example: “Microsoft Windows”.
  3. Click Next.
    Adding a Remote Host — Connector Selection Mode

    Adding a Remote Host — Connector Selection Mode

  4. Specify the connector selection mode:
    • (Default and Recommended) Automatically detect the suitable connectors based on: In this mode, Hardware Sentry will run tests at each discovery and select the connectors that best match your HP ProLiant server.
    • (Advanced) Manually choose which connectors to use: With this mode, you will have to manually select the connectors Hardware Sentry will use to monitor your HP ProLiant server.
  5. If you have previously selected the “automatic” option:
    • Select the protocol(s) to be tested by Hardware Sentry. In our example: “SNMP”.
    • Click Next.
  6. If you have previously selected the “manual” option:
  7. You now need to configure the Connection Settings for all the protocols (SNMP, WMI, WBEM, etc.) that will be used by Hardware Sentry to collect information. In our example: SNMP.
    Adding a Remote Host — SNMP Connection Settings

    Adding a Remote Host — SNMP Connection Settings

  8. Select the SNMP version to be used and click Next.
  9. If you have previously selected SNMP version 1, indicate:
    • the Community to be used.
    • the Port number (default: 161).
  10. If you have previously selected SNMP version 2c, indicate:
    • the Community to be used.
    • the Port number (default: 161).
    • the number of seconds Hardware Sentry will wait for an SNMP response (Default timeout: 120 seconds). This timeout covers all the sub-queries that compose the parent query.
  11. If you have previously selected SNMP version 3, indicate:
    • The Username to be used to perform the SNMP query.
    • The Authentication protocol to be used to authenticate the SNMP v3 messages. Possible values are: None, MD5, SHA.
    • The Authentication password to be used to authenticate the SNMP v3 messages.
    • The Privacy protocol to be used to  authenticate SNMP v3 messages. Possible values are: None, AES, DES.
    • The Privacy password associated with the privacy protocol.
    • The Context name accessible to the SNMP entity.
    • The Port number (default: 161).
    • The number of seconds Hardware Sentry will wait for an SNMP response (Default timeout: 120 seconds). This timeout covers all the subqueries that compose the parent query.
  12. Click Next.
  13. Nothing else needs to be configured. Click Finish.

Hardware Sentry will perform a new full discovery to detect your HP ProLiant server. An icon labeled Hardware on <remote hostname> will appear. It represents the server you are now monitoring remotely, along with icons for all of the detected components of this remote server.

In TrueSight Operations Management

To configure the monitoring of a remote HP ProLiant server in CMA:

  1. Create a new policy or edit an existing one.
    Adding a Remote Host — Device Information

    Adding a Remote Host — Device Information

  2. In the Device Information section, identify the HP ProLiant server you want to monitor remotely:
    • Device Name: Enter the name of the HP ProLiant server you wish to monitor.
    • IP Address: Enter the IP address of your HP ProLiant server. You can leave this field blank if you specified the host name in the Device Name field and if the IP address can be resolved by your DNS/hosts file.
  3. From the Device type drop-down list, select the system type used by your HP ProLiant server. Configuring the Protocol/Connection Information

    Configuring the Protocol/Connection Information

  4. In the Protocol/Connection Information section, click SNMP.
  5. Define the SNMP Information:
    • Select the version of the SNMP protocol used by the device to be monitored. Possible values are 1, 2c, or 3.
    • Use the spin button to indicate the SNMP port number you wish to use to perform SNMP queries. By default the SNMP queries are performed through port 161.
  6. If you selected SNMP Version 1, indicate the SNMP Community string to use to perform SNMP v1 queries.
  7. If you selected SNMP Version 2c, indicate:
    • the SNMP Community string to use to perform SNMP v2c queries.
    • the number of seconds Hardware Sentry will wait for an SNMP response. By default, the timeout is set to 120 seconds to cover all the sub-queries that compose the “parent"queries.
  8. If you selected SNMP Version 3, indicate:
    • The Username to be used to perform the SNMP v3 queries.
    • The Authentication Protocol to be used to authenticate the SNMP v3 messages. Possible values are: None, MD5, SHA.
    • The Authentication password to be used to authenticate the SNMP v3 messages.
    • The Privacy protocol to be used to  authenticate SNMP v3 messages. Possible values are: None, AES, DES.
    • The Privacy password associated with the privacy protocol.
    • The Context name accessible to the SNMP entity.
    • The Port number (default: 161).
    • The number of seconds Hardware Sentry will wait for an SNMP response. By default, the timeout is set to 120 seconds to cover all the sub-queries that compose the 'parent' queries.
  9. Click Close to validate.
  10. Nothing else needs to be configured. Click the Add to List button to validate and add the defined device to the list below.
  11. In the Add Monitor Types dialog box, click Add or Update.

6. Start Monitoring HP Blade Systems

On older P-series chassis, only each individual blade needs to be monitored.  The components of the chassis will appear as components of each blade.
To fully monitor a C-Class HP Blade System, each individual blade needs to be monitored as well as the chassis itself. 

Each individual blade should be monitored as per the instructions above.  No power supplies or fans (sometimes an "overall cooling status" will exist) will be shown for a blade as these components reside in the blade chassis.

To monitor the blade chassis using Hardware Sentry KM for PATROL, add a remote monitoring of the chassis (See Hardware Sentry KM for PATROL documentation – Configuring Remote Hosts Monitoring)