HPE Integrity Superdome X WBEM
Providers for Linux
Technical white paper
Technical white paper
Contents
Introduction ....................................................................................................................................................................................................................................................................................................................................................3
Linux WBEM architecture .................................................................................................................................................................................................................................................................................................................3
Linux WBEM provider details ....................................................................................................................................................................................................................................................................................................... 5
HP Management Base .................................................................................................................................................................................................................................................................................................................. 5
Server Manageability eXtensions ....................................................................................................................................................................................................................................................................................... 6
System Health Daemon ............................................................................................................................................................................................................................................................................................................... 8
Server Manageability eXtensions WEBAPP .............................................................................................................................................................................................................................................................. 9
Linux WBEM provider indications ..........................................................................................................................................................................................................................................................................................10
View from System Management Homepage .........................................................................................................................................................................................................................................................10
View from HPE BladeSystem Onboard Administrator ................................................................................................................................................................................................................................... 11
Viewing information through HPE Insight Remote Support ..........................................................................................................................................................................................................................12
OpenWSMAN ...................................................................................................................................................................................................................................................................................................................................... 12
Test events............................................................................................................................................................................................................................................................................................................................................ 12
Appendix: Troubleshooting .......................................................................................................................................................................................................................................................................................................... 13
HPSMX–WEBAPP shows no items/timeout ........................................................................................................................................................................................................................................................... 13
Restart service .................................................................................................................................................................................................................................................................................................................................... 13
View logs ................................................................................................................................................................................................................................................................................................................................................. 13
Resources ...................................................................................................................................................................................................................................................................................................................................................... 15
Technical white paper
Page 3
Introduction
Web-Based Enterprise Management (WBEM) is an industry standard sponsored by the Distributed Management Task Force (DMTF) based on
the Common Information Management (CIM) model. WBEM allows customers to manage their systems consistently across multiple platforms
and operating systems, providing integrated solutions that optimize your infrastructure for greater operational efficiency. WBEM enables
management applications to retrieve system information and request system operations wherever and whenever required. Linux® WBEM
providers are based on the Server Manageability eXtensions (SMX) 3.2 technology for Red Hat Enterprise Linux (RHEL) versions 6 /7, and SUSE
Linux Enterprise Server (SLES) 11/12 running on HPE Integrity Superdome X (SD-X) Systems.
This document describes the Linux WBEM providers, the variety of tools included, required registration files, and installation scripts bundled into
several RPM packages for easy installation on Linux systems. In addition, you will find descriptions of Linux WBEM provider architecture, provider
details, provider indications, and troubleshooting commands. The information in this document can help you understand, install, run, and
troubleshoot Linux providers on HPE Integrity SD-X Systems.
Linux WBEM architecture
Figure 1 is a representation of the Linux WBEM provider architecture running on the HPE Integrity SD-X System. This simplified diagram shows
the relationships and data transition between Linux WBEM Providers, HPE SW Solution, open source software/driver, and hardware/firmware.
The HP System Management Homepage (HPSMH) is a web-based interface that consolidates and simplifies single system management for HPE
servers on HPE-UX, Linux, and Windows operating systems. You can also use HPE Insight Remote Support (IRS) to view HPE Integrity SD-X
System information the same operating systems.
Figure 1.
Technical white paper
Page 4
The Common Information Model Object Manager (CIMOM) is a central component that routes information about objects and events between
components. For more information about the Common Information Model and CIMOM, go to the Distributed Management Task Force, Inc.
website at dmtf.org/.
The Linux WBEM providers include:
• HPE Management Base (hpemgmtbase)
• HPE Server Manageability eXtensions (HPESMX)
• HPE Server Manageability eXtensions WEBAPP (HPESMX-WEBAPP)
• HPE System Health Daemon (HPESHD)
You do not have to install all of the providers listed above. hpemgmtbase, HPESMX, and HPESHD are required. If you want to view WBEM
information through HPESMH, you also need to install HPESMX-WEBAPP.
There are five packages available:
• hpmgmtbase-VV.UU.RR-BB.distro.arch.rpm
• hp-smx-VV.UU.RR-BB.distro.arch.rpm
• hpsmx-webapp.VV.UU.RR-BB.distro.noarch.rpm
• hpshd-VV.UU.RR-BB.distro.arch.rpm
• hp-smx-EnableWsman-VV.UU.RR-BB.distro.arch.rpm
Unless you want to view information through HPE RS, you must enable OPEN-WSMan through hp-smx-EnableWsman. Otherwise, OPEN-WSMan
is not required for WBEM providers.
Note
In the Linux WBEM Provider releases, VV.UU.FF, VV is the major version number, UU is the minor version/update number, RR is the release/fix
number and BB is build number; distro is the OS distribution (e.g. rhel6, rhel7, sles11, sles12); “arch” is x86_64 only and “noarch” indicates there is
no architecture-specific dependencies
The current packages are available at downloads.linux.hpe.com/SDR/repo/bl920-wbem/
Note
The Software Delivery Repository on hpe.com provides a resource compatible with apt-get, yum and zipper. See
downloads.linux.hpe.com/SDR/getting_started.html for more information on how to configure access to the SDR.
You can also find more support information at hpe.com/info/support. The HPE Support page allows you to drill down to specific information with
product support pages such as hpe.com/portal/site/hpsc/public/psi/home/?sp4ts.oid=7161269
Technical white paper
Page 5
Linux WBEM provider details
Be sure to install the current version of Linux WBEM providers for SLES and RHEL OS from the HPE Software Delivery Repository (SDR).
Note
Linux WBEM providers are not compatible with:
KVM host and KVM guests—As an example of known problems, the libvirt-cim providers from a KVM installation has a conflict with the Linux
WBEM providers. Do not install Linux WBEM providers on an HPE SD-X server setup as a KVM host.
Standards Based Linux Instrumentation for Manageability Performance Data Gatherer Base (SBLIM-Gather)—SBLIM-Gather packages
are intended to implement the DMTF CIM Metrics Model for Linux, making it available via a CIMOM supporting/supported by the CMPI provider
interface.
You can read more about potential conflicts in the HPE Integrity SD-X Linux WBEM providers release notes here: hpe.com/SDR/repo/bl920wbem/Integrity%20Superdome%20X%20Linux%20WBEM%20providers%20release%20notes.pdf
HP Management Base
HP Management Base (hpmgmtbase) is a software collection that includes driver modules, daemons, shared libraries, lookup files, and featured
utilities for Linux WBEM providers. Examples of the shared libraries include:
• Libezbmc
– Open Intelligent Platform Management Interface (IPMI) driver binaries (ipmi_devintf, ipmi_si, ipmi_msghandler)
– Get/Set data via IPMI driver
– FPL, SEL etc.
• Libezpci
– Read data from SMBIOS, /sys/ analysis, lspci
– Slot, Chassis, and Cabinet location for every card
• Libcpqchif
– A non-blocking, concurrent, user mode accessible channels for messaging between the HPE BladeSystem Onboard Administrator (OA) and
the host.
Technical white paper
Page 6
Server Manageability eXtensions
HP-SMX is a set of providers that monitor and provide reporting for HPE Integrity SD-X hardware. The information generated by these providers
is based on industry standards and covers server CPUs, memory, network, and attached storage. Figure 2 shows an overview of the HP-SMX
architecture and the types of providers included.
Figure 2.
Common Manageability Provider Interface Layer
The Common Manageability Provider Interface (CMPI) layer is an industry standard defining how providers can be developed to allow
interoperability across CIMOMs application programming interfaces (APIs) and application binary interfaces (ABIs). SMX requires that CMPI be
the CIMOM interface for all providers. Because using CMPI can be error prone, SMX utilizes a CMPI Adapter layer (Cmp.Cpp) to make this
interaction more trouble-free.
Common Manageability Provider Interface to C++ Adapter Layer
Cmp.Cpp is the C++ framework for provider development, which hides all ‘raw’ CMPI interfaces. It greatly reduces and simplifies provider
development through object orientation and reuse.
Cmp.Cpp is associated with these provider types:
Technical white paper
Page 7
• Instance provider
• Association provider
• Method provider
• Indication provider
Cmp.Cpp also works with all Common Information Model (CIM) data types.
Providers
Providers handle the interaction between the Linux WBEM server (using the standardized CMP interface), and the system hardware or software.
The following providers are used in the HPE SD-X environment.
• Base Server Provider
– Provides computational information and capabilities and serve as an aggregation point to associate one or more elements that make up a
base server, such as fans, power supplies, processor, and memory.
– Reports the partition OS boot status to the OA.
• Blade System Lite Provider—Extends the management capability for referencing profiles by adding the capability of the Distributed
Management Task Force (DMTF) Modular System Profile. While this profile is based on the DMTF Modular System Profile, it does not conform
to that profile. This provider is intended only for the blades within an enclosure as a means for tying the blade to an enclosure. This profile is
not intended to be implemented at the enclosure level. The HPE OA manages the shared enclosure resources at the enclosure level.
• Management Processor Lite Provider—Extends the management capability for referencing profiles by adding the capability to represent HPE
Management Processor on HPE servers
• CPU Provider—Implements and extends the HPE CPU Profile, HPE CPU Consolidated Status Profile, and HPE CPU Physical Asset Profile to
model the system processors
• Memory Provider—Implements the HPE Memory Profile and HPE Memory Physical Asset Profile to represent system memory on HPE servers
• PCI Device Provider—Implements the profiles intended for PCI devices installed on HPE servers
• Ethernet Port provider—Implements and extends the Ethernet Port Profile, Host LAN Network Port Profile, IP Protocol Profile (with IPv6
implementation), and HPE Ethernet Teaming Profile to model the Ethernet port. These classes reside in the local host OS CIM Object Manager
(CIM OM) on each monitored system and describe the Ethernet ports, associated controllers, and logical Ethernet interfaces that are available
in the system. These classes do not describe iLO Management Processor-related information.
• Host File System Provider—Extends HPE Base Server Physical Asset Profile to model the file systems hosted by a managed node. These
classes provide computational information and capabilities that serve as an aggregation point to associate one or more elements that make up
hosted file systems and logical disks.
• Fibre Channel Host Bus Adapter (FCHBA) Provider—Describes the behavior of Fibre Channel host adapters featuring the SCSI (Fibre Channel
Protocol) command set
• IPMI Record Log provider
– Compatible with system logs available on HPE servers
– Detects events using the WBEM definition System Event Log (SEL) and records them in the Linux system logs
• SMX Executive Provider—Collects provider class properties, methods, and values that represent product configuration information for HP
Integrity Superdome X systems.
– Executive Provider
– Calls each provider through CIMOM, using a round robin algorithm
– Default loop every 30 seconds
Technical white paper
Page 8
Managed Resource Adapter Layer
The Managed Resource Adapter (MRA) Layer (each provider has its own MRA Layer) abstracts the managed resource so that provider code can
run on any platform without changes. The MRA layer provides system-related information that includes components such as CPU and memory.
The MRA interface is platform-independent and does not include CIM-related functions. MRA interfaces allow provider core code to implement a
standard profile, and allows the user to get/ set system information and state. It is important to know that some MRA Layers require platformdependent implementation.
Managed Resource Interface Layer
The Managed Resource Interface (MRI) Layer provides system manageability interfaces used by MRA Layers. MRIs are platform specific and
allow getting and setting a variety of information.
Examples of MRI interfaces include:
• SMBIOS
• IPMI
• Compaq ROM Utility (CRU)
• SNIA HBA APIs
System Health Daemon
The HP System Health Daemon (HPSHD) receives Linux WBEM provider event indications and retains that data in the system event database
(SED). HPSHD (Figure 3) analyzes WBEM event indication data stored in the SED and sends warnings to the OA. These warnings are
categorized as “minor, major, critical, and fatal” events. In addition, the HPSHD analyzes Linux WBEM Provider system startup/shutdown
indications that include “started, OS boot, and OS graceful shutdown” events. The HPSHD also monitors FC HBA status when the port status
changes to “unknown”. Although the port status change event is only informational, it can also be sent to the OA.
Figure 3.
Technical white paper
Page 9
You can read more about provider indications, including SMX providers, in the Linux WBEM provider indications section of this document.
Server Manageability eXtensions WEBAPP
HPSMX-WEBAPP is a web application, which is deployed in HPESMH. It can collect and send HPSMX provider data and HPSHD indication data
to HPSMH (Figure 4).
Figure 4.
HPSMX-WEBAPP also performs these functions:
• Collects HPSMX data and saves it in a cache system
• Refreshes the cache system periodically
• Retrieves the data directly from HPSMX if a connection failure occurs in the cache system
The “cache system” entity is memcached-XX process running on each OS. XX indicates on what OS version the process is running. For instance:
• On RHEL6 → memcached-rhel6
• On RHEL7 → memcached-rhel7
• On SUSE11 → memcached-sles11sp3
• On SUSE12 → memcached-sles12
WBEM 56 or later refreshes the cache system 300 seconds after the previous refresh completes.
WBEM 55 or earlier refreshes the cache system hourly.
Technical white paper
Page 10
Linux WBEM provider indications
Linux WBEM indications are asynchronous alerts that provide users real-time status of hardware components. Linux WBEM provider indications
include Base Server, Blade System Lite, Management Processor Lite, CPU, Memory, PCI Device, Ethernet, FCHBA, and IPMI Record Log.
View from System Management Homepage
The HPSMX-WEBAPP retrieves indication information from HPSHD and displays it in HPSMH pages (Figure 5). To view indication information
on the HPSMH pages, you must install HPSMX-WEBAPP and HPSHD. The pathway to the HPSMH pages is: Home→Indications→WBEM
indication.
Figure 5.
Technical white paper
Page 11
View from HPE BladeSystem Onboard Administrator
HPE OA receives indication information from HPESHD that can be viewed from OA web pages, or through OA command line. You must first
install HPSHD.
Viewing from Onboard Administrator web pages
Figure 6 shows that you can access the OA web pages by selecting the enclosure and system log to view indication Information (highlighted).
Figure 6.
Note
HPSHD sends indications to OA only when event alert levels are exceeded for events such as: Linux WBEM Providers Started, OS boot, OS
graceful shutdown events, and FC HBA Port Status Changed to Unknown.
Viewing from command line
You can view HPSHD indication information through secure shell (SSH) to OA. Use command ‘SHOW CAE -L’ to display a summary list of
indications (shown in Figure 7).
Figure 7.
Technical white paper
Page 12
For more detail, please go to OA user guide at: hpe.com/hpsc/doc/public/display?sp4ts.oid=7161269&docId=emr_nac04389088&docLocale=en_US
Viewing information through HPE Insight Remote Support
Insight RS discovers the partitions in which Linux WBEM Providers and OpenWSMAN are installed, and displays Linux WBEM provider
information through the WSMAN protocol.
OpenWSMAN
Web Services for Management (WS-Management, WS-MAN) is a specification for managing computer systems using web services standards.
WS-MAN features a common set of operations that are central to all systems. OpenWSMAN is an open source implementation of WSManagement enabling the in-band management of Linux and Windows platforms. The featured operations include:
• Get, put, create and delete—to handle individual managed resources
• Enumerate—To enumerate all the instances of a managed resource
• Subscribe, Unsubscribe—Capture the events sent by a managed resource
• Discover—For discovering the managed resources and navigating between them
• Invoke—To Invoke a method on a managed resource with defined parameters and gather the output
Test events
Some monitored device types allow you to send a test event to Insight RS. After configuring the monitored device and sending a test event, use
the following process to verify the test event arrived.
• Log on to the Insight RS Console (Figure 8).
• In the main menu, select Service Events. If the monitored device is properly configured, the event will appear in the Service Events Information
pane.
.
Figure 8. Insight RS Console
Technical white paper
Page 13
Appendix: Troubleshooting
HPSMX–WEBAPP shows no items/timeout
HPSMX –WEBAPP takes a few minutes to load provider data after installation; it depends on how many blades are involved. Enter the command:
/opt/hp/hpsmh/data/cgi-bin/HPWBEM/saveCache.sh
All the information is shown upon completion.
Restart service
If Linux WBEM provider does not work, try to restart all the services. The solution is different for each OS.
1. RHEL 6.X
HP-Management-Base: /etc/init.d/hpmgmtbase restart
HP-SMX: /etc/init.d/tog-pegasus restart
HPSHD: /etc/init.d/hpshd restart
HPSMH: /etc/init.d/hpsmhd restart
WSMAN: /etc/init.d/openwsmand restart
2. RHEL 7.X
HP-Management-Base: systemctl restart hpmgmtbase.service
HP-SMX: systemctl restart tog-pegasus.service
HPSHD: systemctl restart hpshd.service
HPSMH: systemctl restart hpsmhd.service
WSMAN: systemctl restart openwsmand.service
3. SLES11 SP3
HP-Management-Base: /etc/init.d/hpmgmtbase restart
HP-SMX: /etc/init.d/sfcb restart
HPSHD: /etc/init.d/hpshd restart
HPSMH: /etc/init.d/hpsmhd restart
WSMAN: /etc/init.d/openwsmand restart
4. SLES 12
HP-Management-Base: systemctl restart hpmgmtbase.service
HP-SMX: systemctl restart sfcb.service
HPSHD: systemctl restart hpshd.service
HPSMH: systemctl restart hpsmhd.service
WSMAN: systemctl restart openwsmand.service
View logs
The solution is different for each OS.
RHEL
HP-SMX:
touch /tmp/SMXLogAll.text
restart the tog-pegasus service
cat/var/lib/Pegasus/cache/trace/SMX*.log
HPSHD:
cat /var/log/hp/hpshd
Technical white paper
SLES:
HP-SMX:
touch /tmp/SMXLogAll.text
restart the sfcb service
cat /SMX*.log
HPSHD:
cat /var/log/hp/hpshd
Page 14
Technical white paper
Page 15
Resources
HPE Integrity Superdome X QuickSpecs
hp.com/h20195/v2/GetDocument.aspx?docname=c04383189
Running Linux on HPE Integrity Superdome X White Paper
hp.com/v2/GetDocument.aspx?docname=4AA5-4775ENW&doctype=Technical white paper&doclang=EN_US&searchquery=&cc=us&lc=en
HPE Insight Remote Support
hpe.com/info/insightremotesupport
Tog-pegasus (OpenPegasus WBEM Services for Linux)
centos.org/docs/5/html/5.5/Technical_Notes/tog-pegasus.html
Small-Footprint CIM Broker (SFCB)
novell.com/support/kb/doc.php?id=7010296
OPENWSMAN
openwsman.github.io/
HPE Support Center
hpe.com/info/support
Industry Standard Server Technology Papers
hpe.com/docs/servertechnology
Sign up for updates
Rate this document
© Copyright 2015, 2016 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without
notice. The only warranties for HPE products and services are set forth in the express warranty statements accompanying such products
and services. Nothing herein should be construed as constituting an additional warranty. HPE shall not be liable for technical or editorial
errors or omissions contained herein.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Windows is a trademark of the Microsoft group of
companies.
4AA6-2641ENW, May 2016, Rev. 2