Knowledge Base

Monitoring IBM xSeries Servers with Hardware Sentry

KB1041 - Sep 17, 2010 - Last reviewed on Jan 29, 2020

Type: Best Practice

Description: Monitoring IBM xSeries servers with Hardware Sentry KM. Supported communication protocols and discovered hardware components.

Additional Keywords: Adaptec, IBM, IBM Director Agent, LSI, xSeries

Related Topics


  • The Hardware Instrumentation section covers the basic IBM© xSeries server hardware components and the supported communication protocols.
  • The Setting up... section provides detailed instructions for installing and configuring Hardware Sentry KM for PATROL to properly monitor IBM© xSeries servers.
  • The Discovered Components and Monitored Parameters section lists the components automatically discovered and monitored by Hardware Sentry KM for PATROL.

This document covers IBM© xSeries servers running either Microsoft Windows or any supported distribution of Linux.

About IBM xSeries Servers

IBM’s xSeries product line is based on the X86/X64 processor architecture and represents a large portion of the Windows and Linux server market (along with HP’s ProLiant and Dell’s PowerEdge servers).

IBM xSeries servers were formerly known as IBM Netfinity servers.

Very much like any other PC, these systems are based on standard Intel or AMD processors (both the X86 and X64 architectures are represented) and include various standard memory, network and I/O components.

In addition, IBM xSeries also include a RAID adapter, called ServeRaid. IBM ServeRaid cards are OEM’d from either Adaptec or LSI.

Hardware Instrumentation

Out-of-band: IMM2

Most M4 and all M5/M6 Generation IBM xSeries have an Integrated Management Module II (IMM2) service processor, which facilitates out-of-band monitoring via SNMP.

This is the recommended method for most M4 and all M5/M6 generation IBM xSeries, as well as Lenovo xSeries, and does not require the Director Agent.

This method is compatible with the following servers:

  • All Lenovo branded xSeries Servers
  • IBM System x3100 M4/M5
  • IBM System x3250 M4/M5/M6
  • IBM System x3300 M4
  • IBM System x3500 M4/M5
  • IBM System x3530 M4
  • IBM System x3550 M4/M5
  • IBM System x3630 M4
  • IBM System x3650 M4/M4BD/M4HD/M5
  • IBM System x3750 M4
  • IBM System x3850 X6
  • IBM System x3950 X6
  • IBM iDataPlex dx360 M4
  • IBM NeXtScale nx360 M4/M5

For further information on monitoring these systems, please see: Monitoring Lenovo Servers with Hardware Sentry

Systems not listed, including those with the older IMM or RSA cards, are not able to be monitored in this way, and must instead use the Director Agent.

In-band: IBM Director Agent

IBM provides a systems management tool called IBM Director Agent. For older xSeries systems, this agent is required to connect to the Hardware instrumentation of the servers and relay information to Hardware Sentry.

Depending on the server's configuration, installation of the Director Agent may not be sufficient by itself. Some other tools and drivers may be required to be installed and properly configured on the IBM xSeries servers before monitoring with Hardware Sentry.

The IBM Director relies on the WBEM standard. On Windows systems, it registers itself as a WMI provider and can be accessed through the WMI layer and API of Windows. On Linux systems, it installs a complete Pegasus CIM server which can be accessed through a standard WBEM client (XML-HTTP and HTTPS on TCP/5988 and TCP/5989).

Setting up Hardware Sentry on IBM xSeries Servers

Configuring Systems Running Windows

1. Install the IBM Director Agent

Please refer to the following link for the installation procedure: IBM Systems Director 6.3 Best Practices

For IPMI-based systems running Windows Server 2008 R1 and older, installation of the OSA IPMI driver and IBM Mapping layer for OSA IPMI from IBM may also be required.

2. Configure WMI

In most cases, there is no need for any customization in order to get the PATROL Agent, Hardware Sentry KM and the IBM Director Agent work together on Windows systems. However, if the systems is within a highly secured Windows environment and the PATROL Agent’s default account is not a member of the local Administrators group, you may need to:

  • Configure the WMI component (Windows WBEM layer) to authorize the PATROL Agent default account to make WBEM requests to the /root, /root/WMI and /root/ibmsd namespaces.
  • Authorize the PATROL Agent default account to use the WBEM DCOM component (through the dcomcnfg MMC applet).

Configuring Systems Running Linux

1. Install the IBM Director Agent

Please refer to the following link for the installation procedure: IBM Systems Director 6.3 Best Practices

IPMI systems running very old Linux versions may also require installation of the appropriate OSA IPMI driver and IBM Mapping layer for OSA IPMI from IBM.

Older Non-IPMI systems may require the installation of the lm78 and smbus drivers. These must be compiled against the specific version of the Linux kernel running on the managed server. Please carefully review the compilation and installation instructions provided by IBM for these drivers.

2. Configure the CIM server

By default, the CIM server installed with the IBM Director Agent only authorizes root to perform WBEM queries. You will need to either provide the PATROL Agent and Hardware Sentry KM with the root credentials or configure the CIM server to allow the PATROL Agent and Hardware Sentry to perform WBEM queries.

The procedure below is valid with the version 5.10 or later of IBM Director.

Option A: Configure Hardware Sentry KM to use the root account for WBEM requests

In the PATROL Console, right-click on the main Hardware Sentry icon, [KM Commands] › [This System’s Settings] › [Connection, Credentials and Connectors]. On the WBEM page, enter the root username and password and the WBEM ports as 15988 (http / non-encrypted) and 15989 (https / encrypted).

If using the TrueSight Console, edit the Hardware Monitoring Configuration within the Infrastructure Policy, and edit the List of Devices. Within the List of Devices window, find the WBEM section, and enter the root username and password, and port as 15988 (http / non-encrypted) or 15989 (https / encrypted), checking the "Encryption" option appropriately.

Option B: Configure the CIM server to allow the PATROL Agent’s default account to make WBEM requests

Log in to the system as root. Execute the following command:

/opt/ibm/icc/cimom/bin/cimconfig -p -s authorizedUserGroups= ‹group›

…where ‹group› is the group of the PATROL Agent’s default account.

Restart the cimserver and cimlistener daemons with the following commands:

/etc/init.d/cimlistenerd stop /etc/init.d/cimserverd stop /etc/init.d/cimlistenerd start /etc/init.d/cimserverd start

If you leave the authorizedUserGroups variable empty (instead of specifying a specific group), any valid account will be allowed to make requests to the IBM Director Agent through the WBEM protocol.

After successfully testing this on one machine, subsequent machines can be automatically reconfigured by copying the configuration file at the path below from the first machine, then restarting the cimserver and cimlistener daemons: /opt/ibm/icc/cimom/cimserver_planned.conf

Discovered Components and Monitored Parameters

The following components and parameters are discovered and monitored:

  • Server model and serial number
  • Processors, model and frequency, status
  • Fans, fan speed
  • Memory modules, size and type, status
  • Power supplies, status
  • Temperature sensors, actual temperature
  • Voltage sensors, actual voltage
  • RAID disk controllers, controller status
  • Physical disks, vendor, size, model number, status
  • Logical disks (RAID volumes), size, RAID type, status
  • Network cards, vendor, model, connection speed, status, link status and error percentage

Known Issues

Operating System Compatibility

IBM has not published a new version of the Systems Director Agent since 2015, and as such it may not be compatible with newer Linux distributions, in particular RedHat/Centos 7 (64-bit).

Missing components

  • Power Supplies – Some xSeries models do not have sensors for Power Supplies (x3200 M3 for example). Thus, power supplies will not be monitored on these affected systems.

  • Physical Disks - RAID – The ServeRAID subagent should be included as part of the Director Agent installation. If RAID information is missing, check that it has been installed, and that its version is compatible with the RAID controller firmware version.

  • Physical Disks – Non-RAID – On Linux systems, these are monitored via SmartMon Tools, using the smartctl command. If sudo/root OS credentials are not provided, this connector will not work.

  • Physical Disks – Blades (USB Stick) – Many IBM blades ship with USB sticks to boot ESX and thus don’t contain local disks, so on these systems, no disks will be found to monitor.