HP Management Base Installation and Users Guide for Linux HP Integrity Servers HP Part Number: 5991-7630 Published: May 2009 Edition: 4
© Copyright 2007–2009 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About This Document.........................................................................................................4 Intended Audience.................................................................................................................................4 Typographic Conventions......................................................................................................................4 Publishing History...........................................................
About This Document This document provides installation and user information for the HP Management Base (hpmgmtbase). Intended Audience This document is intended for system administrators who have experience installing and managing Linux systems. This document is intended to be used with the operations and maintenance guides for any HP Integrity servers on which HP Management Base is installed.
http://docs.hp.com/en/ linuxredhat.html#HP%20Integrity%20Essentials%20Foundation%20Pack%20for%20Linux Manufacturing Part Number Supported Operating Systems Supported Versions Edition Number Publication Date 5991–5421 SUSE Linux (SLES) SLES 8, SLES 9 1 May 2006 Red Hat Enterprise Linux (RHEL) RHEL 3, RHEL 4 SLES SLES 8, SLES 9 2 September 2006 RHEL RHEL 3, RHEL 4 SLES SLES 8, SLES 9, SLES 3 10 5991–7426 5991–7630 RHEL April 2007 RHEL 3, RHEL 4 5991–7630 SLES RHEL SLES 8, SLES 9.
HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to: docsfeedback@hp.com Include the document title, manufacturing part number, and any comment, error found, or suggestion for improvement you have concerning this document.
1 Overview of HP Management Base HP Management Base is a collection of software that includes driver modules, daemons, shared libraries, lookup files, and utility support for other HP manageability software (such as SNMP Agents or WBEM providers). All HP Integrity servers provide their platform manageability information using hardware that follows the Intelligent Platform Management Initiative (IPMI) specification. A key component of IPMI is the Baseboard Management Controller (BMC).
• • 8 hprasd, a daemon that collects and analyzes events to enhance Reliability, Availability, and Serviceability (RAS). This daemon is only available on SLES11 and RHEL5.4 and later.
2 Installing HP Management Base This chapter describes the installation procedures for HP Management Base. Installation Requirements A typical server installation usually includes the following items, and these items are required to successfully install HP Management Base: • An officially supported version, update, or errata kernel for: — RHEL Advanced Server (AS) 2.1 — RHEL AS 3.0 — RHEL AS 4.0 — RHEL 5.0 — SLES 8.0 — SLES 9.0 — SLES 10.0 — SLES 11 RHEL AS 2.
3 Using HP Management Base Utilities This chapter describes how to use the HP Management Base command-line utilities. All utilities have manpages. See Appendix B (page 20). NOTE: For all the HP Management Base manpages, you can display a synopsis of options and directives by entering the following: command -? where command is the name of the command.
-v Verbose (only on cellular systems). For status checks, prints out the components and connectivity of the running partition. hpuid—Reports Unique Identifier (UID) Syntax /sbin/hpuid [-d] [-e] [-s] [-v] The Unique Identifier (UID) is a flashing LED on the chassis used to identify a box. This identifier can be a great aid when you are confronted with a server farm of hundreds of boxes. On entry-level systems, the UID is a blue LED that is present on both front and rear panels.
All IPMI commands use a command/response message protocol with a requestor and a responder. In most cases on HP hardware using HP software, programs running under Linux are the requestor, and the system's BMC is the responder. The BMC hardware is exposed through a system interface, as described in the IPMI specification. This channel requires a device driver and device file to exchange commands and responses.
The final complexity in addressing an IPMI responder or target device is the IPMI Bus, or IPMB. IPMB is an address-based I2C bus that passes IPMI commands back and forth between intelligent controllers. Some HP Integrity Servers do have IPMB, but its use is hidden by hpbmc and not directly exposed. However, on the HP ATCA platform, this functionality is of immense interest. Consult ATCA documentation for details.
the key bytes from a SEL entry. These triplets are described in the operations and maintenance guide of each server. This triplet can be used as input for EventLookup. Finally, the entire event dictionary can be dumped with either EventLookup LIST (a very verbose form) or EventLookup TABLE ( | -separated fields suitable for further parsing or importing into a spreadsheet).
4 Troubleshooting In the discussion that follows, all programs (and drivers) attempt to communicate with the local system BMC. No RMCP is used, no -d argument is used, and the shell environment variable EZBMC_DEVICE is not set. Proper Function In a properly functioning system the following should be observed: • No errors occur during installation of hpmgmtbase. • Three IPMI kernel modules are visible from lsmod.
Improper Function Almost all problems with HP Management Base are related to the version and loading of the three kernel modules that make up the Open IPMI driver. Specifically, it is the System Interface (SI) module that causes the problems. Kernel Distributions SI Module Name 2.4 (old) RHEL 2.1, SLES 8 ipmi_kcs_drv.o 2.4 (recent) RHEL 3 ipmi_si_drv.o 2.6 RHEL 4, RHEL 5, SLES 9, SLES 10, SLES 11 ipmi_si.ko The other two modules are always named impi_msghandler and ipmi_devintf.
5 Rebuilding the Kernel The HP Management Base scripts examine the running kernel version to assist in the selection of the appropriate binaries for the HP-supplied Open IPMI modules. If the kernel version is changed, the selection process will probably need to be executed again. This situation might not be apparent until a reboot of the new kernel when hpmgmtbase fails to initialize or when other programs that are dependent on the Open IPMI driver fail to start.
5. For all kernels, enter: # modprobe ipmi_devintf . 6. Reconfigure HP Management Base: # /etc/init.d/hpmgmtbase reconfigure. The reconfiguration should recognize that modules are loaded from some other source and ignore any HP-supplied binaries.
A Frequently Asked Questions This section addresses frequently asked questions concerning HP Management Base. 1. I have a custom kernel, and none of the IPMI modules work. See Chapter 5 for instructions on rebuilding the kernel. 2. Can I use the Open IPMI driver directly from my own programs? Yes. There are several open source tools that use direct access to the Open IPMI driver device interface. One of these is the Open IPMI Library, which can be found at the SourceForge Open IPMI website: http://www.sf.
B HP Management Base Manpages This appendix contains the HP Management Base manpages. NOTE: For all the HP Management Base manpages, you can display a synopsis of options and directives by entering the following: command -? where command is the name of the command.
hpbmc(8) NAME hpbmc -- Manage the IPMI BMC on HP Servers . Synopsis /sbin/hpbmc [-b busaddr ] [-d path] [directive] Description hpbmc is a utility for performing action(s) on a Baseboard Management Controller (BMC). hpbmc was originally designed for HP Integrity Servers using the Open IPMI driver. hpbmc may work against other platforms if a BMC is available via a network connection (RMCP). If the optional directive is missing, the Summary output is printed.
Trap: SNMP enterprise-specific trap (if any) Platform: All, Entry-level, Mid-range, High-end An E0 event may occur on multiple platforms with slightly different fields (event ID 98 is a good example). A set of attributes will be printed for each platform that supports the event. If the argument is LIST, all registered events for the running platform will be printed as described above. There will not be any multiple events printed in this list.
IPMIraw NetFn/LUN Cmd [data1 data2 ...] Takes the hexadecimal bytes and sends them directly to the target device. Output is printed as a block of hexadecimal bytes, although no length information is explicitly given. The user must know how to interpret the bytes. For example, hpbmc IPMIraw 18 1 is the Get Device ID command. IPMBgetaddr Returns the apparent bus address of the Open IPMI device; cannot be used with the -b option.
F Sensor Full sensor that can return analog readings FRU Field Replaceable Unit Ent Assoc Entity association, a logical grouping of lower-level entities A Prop Association property, an HP-proprietary type (cellular only) D Prop Data property, an HP-proprietary type (cellular only) C Prop Control property, an HP-proprietary type (cellular only) SDRprintraw Like SDRprint, along with the raw data bytes of the entry, starting at the Record Type. SELappend Adds a new event to the System Event Log.
Sensors [number ] Lists all sensors and the current reading of each. If number is given, list only that sensor (which can be obtained from SDRprint). Note that sensor number may not be a truly unique reference if multiple LUNs are available. SetSystemInfoParameter {parameter} The IPMI 2.0 spec allows information strings to be set with this command. Commonly used parameters are shown under the GetSystemInfoParameter directive.
hpia64info(8) NAME hpia64info -- Report IPMI information for HP Integrity Servers Synopsis hpia64info [-v] Description hpia64info is a utility that lists information obtained from the IPMI Baseboard Management Controller (BMC) on HP Integrity Servers. This information is a fixed set in a fixed format and is used primarily by other HP tools. In general, more useful functionality can be found with hpbmc. See Also hpbmc(8) Author Hewlett-Packard Company.http://www.hp.com/linux.
hpipmid(8) NAME hpipmid -- HP IPMI Daemon Synopsis hpipmid [-d device ] [-f ] [-h] [-s LOG] [-v] Description hpipmid is started by /etc/init.d/hpmgmtbase. An attempt to start another copy will fail (with the exception of the -s option). hpipmid talks directly to the system BMC and performs several tasks: • Caches the content of the IPMI SEL (System Event Log) and FPL (Forward Progress Log). Signals are emitted on the System DBus when SEL events are added.
Use hpipmid -s SELto see the current status of the cache. The state will be "filling" right after installation of hpmgmtbase, and will switch to "watching" when the backfill is complete. See Also hpbmc(8)hprasd(8) Author Hewlett-Packard Company .http://www.hp.com/linux. Copyright Copyright 2009 Hewlett-Packard Technologies Group, L.P.
hpmodel(8) NAME hpmodel -- Report Hardware Model Information Synopsis /sbin/hpmodel [-a] [-imprsuw] Description hpmodel reads the system firmware's SMBIOS table in order to obtain information on HP Integrity servers. This utility offers some additional options to report system UUID, product model name, version, wake up type, serial number, manufacturer and platform type. -a Displays all system information obtained from the system table in SMBIOS.
hpuid(8) NAME hpuid -- hp Unique IDentifer (UID) utility Synopsis /sbin/hpuid [-d] [-e] [-s] [-v] Description hpuid interacts with the "Unique IDentifier" (UID) LED on HP Integrity servers, turning it on and off or reporting its current status. Entry-level servers have a blue LED on the front and back panels; this redundant pair of LEDs is the UID. For midrange and high-end servers, each major component of the complex (cabinets, cells, and IO chassis) has its own LED.
Author Hewlett-Packard Company.http://www.hp.com/linux, based on a similar command originally available on Compaq Proliants. Copyright Copyright 2006 Hewlett-Packard Technologies Group, L.P.
Glossary BMC Baseboard Management Controller. The IPMI spec describes the BMC as the "heart of IPMI." It is an embedded microcontroller surrounded by memory, interfaces, and sensors. The entire collection can provide the various functions described in the specification. BT Block Transfer. One of the System Interfaces used to connect a BMC to a system CPU. BT is used in HP Integrity midrange and high-end systems. It transfers data in blocks and is much faster than KCS or SMIC. FPL Forward Progress Log.
RMCP Remote Management Control Protocol. A network IP-based protocol that provides authentication, access, and session management for management utilities. It can carry embedded IPMI commands and responses between network entities. SDRR Sensor Data Record Repository. A required feature of a BMC, this is the material list for IPMI. It starts with the list of sensors, their conversion and units, thresholds, and scanning information.
Index B S Baseboard Management Controller (see BMC) BMC, 7 SDRR, 7, 12 SEL, 7 Sensor Data Record Repository (see SDRR) start-up scripts, 7 System Event Log (see SEL) C cell assignment monitored by hpbmc, 7 E troubleshooting, 15 events decoding, 13 F Forward Progress Log (see FPL) FPL, 7 frequently asked questions, 19 H hpbmc, 11 hpia64info, 10 hpipmid, 7, 11 hpmgmtbase components, 7 installing, 9 overview, 7 using, 10 utilities, 11 hpmodel, 10 hprasd, 8 hpuid, 11 I installation prerequisites, 9 pr
*5991-7630* Printed in the US
