HP WBEM Providers for Linux

Transcription

1 HP WBEM s for Linux Installation Guide and Release Notes HP Part Number: Published: April 2008 Edition: 6

2 Copyright Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , 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. The only warranties for HP 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. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments RED HAT READY Logo and RED HAT CERTIFIED PARTNER Logo are trademarks of Red Hat, Inc.

3 About This Document This document provides instructions for downloading and configuring HP Web-Based Enterprise Management (WBEM) s for Linux. As of this publication, the HP WBEM s for Linux agents operate with Red Hat Enterprise Linux and SUSE Linux Enterprise Server. IMPORTANT: HP recommends that you review the Release Notes (page 14) chapter of this document prior to installing and configuring HP WBEM s for Linux. The release notes contain important information pertaining to the current release of the providers and the product. Intended Audience This document is intended for use by system administrators responsible for installing, configuring, and managing Linux systems. Administrators are expected to have knowledge of Linux operating system concepts, commands, and configuration. Typographic Conventions This document uses the following typographical conventions. Command A command name or qualified command phrase. ComputerOut Text displayed by the computer. Ctrl-x A key sequence. A sequence such as Ctrl-x indicates that you must hold down the key labeled Ctrl while you press another key or button. ENVIRONVAR The name of an environment variable, for example, PATH. [ERRORNAME] The name of an error, usually returned in the errno variable. Key The name of a keyboard key. Return and Enter both refer to the same key. Term The defined use of an important word or phrase. UserInput Commands and other text that you type. Variable The name of a placeholder in a command, function, or other syntax display that you replace with an actual value. [ ] The contents are optional in formats and command descriptions. If the contents are a list separated by, you must choose one of the items. { } The contents are required in formats and command descriptions. If the contents are a list separated by, you must choose one of the items.... The preceding element can be repeated an arbitrary number of times. Separates items in a list of choices. Intended Audience 3

4 Publishing History The document publishing date and part number indicate the current edition of the document. The publishing date changes when a new edition is printed. Minor changes might be made at reprint without changing the publishing date. The document part number changes when extensive changes are made. Document updates might be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, subscribe to the appropriate product support service. See your HP sales representative for details. For the latest version of this document online, see the HP Technical Documentation Web site at: Manufacturing Part Number Supported OS Supported Versions Edition Number Publication Date Red Hat Enterprise Linux (RHEL) SUSE Linux Enterprise Server (SLES) RHEL4U4 and later updates, and RHEL5 and later updates SLES9SP3, and SLES10 and later service packs Red Hat Enterprise Linux (RHEL) SUSE Linux Enterprise Server (SLES) RHEL4U4 and later updates, and RHEL5 and later updates SLES9SP3, and SLES10 and later service packs Red Hat Enterprise Linux (RHEL) RHEL4U4 and later SUSE Linux Enterprise Server (SLES) updates, and RHEL5 SLES9SP3 and SLES Red Hat Enterprise Linux (RHEL) RHEL3U8, RHEL4U4 and SUSE Linux Enterprise Server (SLES) earlier, and RHEL5 SLES9SP3 and SLES Red Hat Enterprise Linux (RHEL) RHEL3U8 and RHEL4U4 SUSE Linux Enterprise Server (SLES) and earlier SLES9SP Red Hat Enterprise Linux (RHEL) RHEL3U8 and RHEL4U4 SUSE Linux Enterprise Server (SLES) and earlier SLES9SP April 2008 December 2007 August 2007 March 2007 November 2006 September 2006 Related Information The HP WBEM s for Linux product Web site, which contains additional product information, is located at: The HP WBEM s for Linux product documentation is located at: HP Integrity Essentials Foundation Pack for Linux Web site is located at: The HP Systems Insight Manager Web site is located at: The Distributed Management Task Force (DMTF) Web site, which contains details on the WBEM protocol, is located at: 4

5 The Open Group's OpenPegasus Web site is located at: The HP Integrity server technical support information is located at: For additional information on HP products and services, visit: For the location of the nearest sales office, call: In the United States: In Canada: In Japan: In Latin America: In Australia/New Zealand: In Asia Pacific: In Europe/Africa/Middle East: For product information, contact any of the HP worldwide sales offices or HP Channel Partners (in the United States, call ). HP Encourages Your Comments HP encourages your comments concerning this document. We are truly committed to providing documentation that meets your needs. Send your comments to HP at: Include the document title, manufacturing part number, and any comment, error found, or suggestion for improvement you have concerning this document. Also, include what we did right so we can incorporate it into other documents. HP Encourages Your Comments 5

6 1 Overview 6 Overview HP WBEM s for Linux is based on the OpenPegasus Web-Based Enterprise Management (WBEM) protocol, and it allows you to remotely monitor configuration information and system status on your HP Integrity server from any WBEM client. A management application such as HP Systems Insight Manager (SIM) gathers and organizes the raw provider information from the browser for display in reports, allowing you to monitor system use and troubleshoot problems. For additional details regarding OpenPegasus WBEM, see the OpenPegasus Administrator s Guide installed in the /usr/share/doc/tog-pegasus-2.#.# directory on your system. The HP WBEM s for Linux package is composed of groups of WBEM providers that monitor various aspects of system health and inventory. The components and their functions are as follows: A base package containing common utilities and class definitions s that implement and extend profiles developed by the Distributed Management Task Force (DMTF): the DMTF Profile Registration Profile 1.0.0a and DMTF Record Log Profile s that implement event logging, system health, inventory and monitoring for HP SIM The following HP WBEM s for Linux are included: Disk Partition HP Software Inventory HP Fibre Channel Host Bus Adapter HP Forward Progress Log HP Profile Registration Profile HP System Event Log HP Processor HP Computer System The Disk Partition provider models virtual, logical, or physical disk partitions and supports the creation and modification of partition tables. The HP Software Inventory returns information about installed RPMs on the system, based on the information in the RPM database for both RHEL and SLES. This provider returns information on the Fibre Channel host bus adapters (FC HBAs) that support the SCSI-FCP (Small Computer System Interface-Fibre Channel Protocol) command set. The HP Forward Progress Log exposes the Forward Progress Log (FPL) that is part of the HP Integrity platform. The FPL is used to store detailed information about the booting process, as the system discovers memory, CPU, and I/O resources. Memory and Extensible Firmware Interface (EFI) POST test progress and information is also stored in the FPL. The HP Profile Registration implements the DMTF Profile Registration Profile as documented in the DMTF standard DSP1033. This profile allows providers to register their conformance with other well-known standard DMTF profiles. WBEM clients can use this information to determine whether a server supports a particular set of CIM classes and operations. The System Event Log provider exposes the System Event Log (SEL) that is part of the HP Integrity platform. The SEL is used to store sensor events such as over temperature, fan failures and other sensors attached to the chassis. The Processor provider represents processors, processor chips, processor slots, and the relationships between them. It offers detailed information about the processors, such as speeds, versions and firmware information. The Computer System provider produces a single instance of the HP_ComputerSystem class which represents the managed node running WBEM. Useful inventory information such as the

7 HP SCSI Protocol Controller HP IPMI Sensors Logical Disk Disk Drive HP Network Adapter HP PCI Devices and Locations Physical Media Physical Memory Physical Memory Statistical Information Power Supply RPM Database SMART State Sensor UUID and chassis serial number is provided in the instance properties. The SCSI Protocol Controller provider The SCSI controller provider makes available information about any SCSI controller found in the managed node. It offers information on controller capabilities like such as data protection, max data width, max transfer rate, signal capabilities and specifications on the number of controlled devices. The IPMI Sensors provider represents IPMI sensors that measure numeric, threshold and presence sensors in a managed node. Typically there are numeric and threshold sensors for power supply voltages and cooling fans, and hot-pluggable power supply units appear as presence sensors. The Logical Disk provider makes available information about logical disks (file systems) currently mounted on the machine. It encompasses HD partitions, RAM disks, CD-ROMs, floppies, etc. The disk drive provider makes available information about the capabilities and management of SCSI hard disks. This provider exposes information about media blocksize, adapter, channel and target numbers as well as capability descriptions. The Network Adapter provider returns information on the capabilities and management of Ethernet network cards, ports and endpoints. The PCI Device provider makes available information about the capabilities and management of PCI devices on internal and external SCSI buses. Information such as base address, subsystem id, subsystem vendor id, and min grant time are offered by instances of this class. The Physical Media provider makes available inventory information about SCSI hard disks such as capacity, model, and manufacturer. The physical memory provider represents the physical memory hardware, memory slots, and the relationships between them. It offers detailed information about the memory, such as bank labels, types, speeds, and capacities. The Physical Memory Statistical Information provider represents the physical memory hardware, memory slots, and the relationships between them. It offers detailed information about the memory, such as bank labels, types, speeds, and capacities. The Power Supply provider makes available information about power supply bays in the managed node and includes the existence of a power supply, its status and availability. The RPM Package Manager (RPM) Database provider supplies access to a single database of installed packages on a system. It contains all of the meta information of the installed RPMs and multiple databases used for indexing purposes. The provider is used to keep track of all files that are changed and created when a program is installed, thus allowing RPM to remove packages. The SMART State Sensor provider models the Self-Monitoring, Analysis and Reporting Technology System (SMART) for hard disks installed on the managed node. This can provide advanced warning of disk degradation and failure. 7

8 HP System Firmware Inventory The HP System Firmware Inventory returns information about the system's firmware, which is returned by the system firmware for both RHEL and SLES. HP WBEM s for Linux is provided in the HP Integrity Essentials Foundation Pack for Linux Support Pack, which is available for download at: Supported Operating Systems HP WBEM s for Linux is supported on the following Linux distributions: Red Hat Enterprise Linux (RHEL) RHEL4U4 (OpenPegasus V2.5) and later RHEL5 (OpenPegasus V2.5) and later SUSE Linux Enterprise Server (SLES) SLES 9 SP3 (OpenPegasus V2.4) SLES) 10 (OpenPegasus V2.5) and later service packs Supported Hardware HP WBEM s for Linux have been installed, tested, and are supported on servers supported by the HP Integrity Essentials Foundation Pack for Linux. For a list of supported servers, see the HP Integrity Essentials Foundation Pack for Linux User's Guide at: Integration Software The primary method of integrating the HP WBEM s for Linux product into your system is through HP SIM V5.0. In addition, the providers also operate with any client that can initiate requests using WBEM. For more information, see the HP Systems Insight Manager website: Coexistence with other HP Products HP WBEM s for Linux can coexist with existing installations of HP Insight Management Agents (SNMP agents). Updating HP WBEM s for Linux Updates to HP WBEM s for Linux are provided through the HP Integrity Essentials Foundation Pack for Linux Support Pack, which is available for download at: WBEM Versus SNMP Nomenclature WBEM is a set of standards defining manageability protocols and schema for modelling systems, networks, applications and services. It is intended to be a significant improvement on the SNMP standard especially in the areas of modeling and security. 8 Overview

9 The following WBEM related documents may be of interest: Specification for CIM Operations over HTTP Describes the interface used to fetch and modify managed objects found at: The CIM Document Type Definition Describes the XML format used by the WBEM protocol found at: Web-Based Enterprise Management Describes how to use WBEM found at: The following table provides a brief list of commonly used WBEM terms and their corresponding SNMP terms. WBEM Term OpenPegasus Common Information Model Object Manager (CIMOM) Property Common Information Model (CIM) schema Indication CIM class SNMP Term SNMP Master Agent SNMP subagent SNMP Object Management Information Base (MIB) Trap SNMP Object definition SNMP sends messages over unencrypted UDP datagrams on ports 161 and 162; WBEM sends messages over HTTP encrypted using SSL on TCP port WBEM Versus SNMP Nomenclature 9

10 2 Installing and Configuring You can install the HP WBEM s using HP Integrity Essentials Foundation Pack for Linux Support Pack or from the command line. Either method requires the use of the HP Integrity Essentials Foundation Pack for Linux Support Pack. Installing using the Command Line Use the following steps to install HP WBEM s for Linux on your system: 1. Uninstall any previous releases of HP WBEM s for Linux. To determine if there are any providers installed, enter: # rpm -qa grep hp.com-wbem-providers If the command produces any output, uninstall the old providers using the following command: # rpm -e hp.com-wbem-providers Due to problems in previous releases of the HP Integrity Foundation Pack for Linux, the upgrade option of the RPM package manager does not operate correctly so the rpm -U upgrade command cannot be used. You must completely remove previous versions of the providers before installing new versions using the following steps: a. Determine which RPMs are installed, enter: # rpm -qa grep ^hpwbem hpwbem-firmwarelogs rhel4 hpwbem-legacy rhel4 hpwbem rhel4 hpwbem-base-server rhel4 The installed providers are displayed by RPM name. b. You must remove each RPM displayed in the following order as follows: # rpm -e hpwbem-legacy # rpm -e hpwbem-firmwarelogs # rpm -e hpwbem-base-server # rpm -e hpwbem c. Use the rpm -e <RPM name> to remove all remaining installed providers/rpms. 2. Install the tog-pegasus RPM from your distribution media for RHEL distributions, or for SLES9 from the HP Integrity Essentials Foundation Pack for Linux Support Pack, enter: # rpm -i tog-pegasus*.rpm 3. Start the WBEM server by entering the following command: # /etc/init.d/tog-pegasus start 4. Ensure that the installation and startup of OpenPegasus was successful using the following command: # osinfo If relevant information about your system is displayed, similar to the following, then installation was successful. OperatingSystem Information Host: test.cao.cpqcorp.net Name: Red Hat Enterprise Linux AS ( EL #1 SMP Fri Feb 24 16:49:08 EST 2006 ) Version: EL UserLicense: Unlimited user license Number of Users: 1 users Number of Processes: 69 processes 10 Installing and Configuring

11 OSCapability: 64 bit LastBootTime: Jul 21, :54:12 (01000) LocalDateTime: Aug 11, :13:13 (01000) SystemUpTime: seconds = 21 days, 0 hrs, 19 mins, 1 sec 5. Ensure that the media containing the HP Integrity Essentials Foundation Pack for Linux Support Pack is mounted, and then change to the hpwbem directory. 6. Install all the HP WBEM s for Linux RPMs from the media by entering the following command: # rpm -i hpwbem*.rpm NOTE: OpenPegasus must be running for the providers to be installed; the installation process cannot complete otherwise. 7. Edit the PAM configuration file (/etc/pegasus/access.conf) so that OpenPegasus is allowed network access. By default the OpenPegasus server does not allow access by users over the network. Only the root and pegasus users can access information provided by the WBEM server locally. Modifying the access rules in the PAM configuration file is necessary so that HP SIM can manage the system; the format of these access rules is described in the comments at the head of this file. NOTE: If additional users are allowed local or remote access to OpenPegasus, they must also be added to the Unix group pegasus. The first access rule, which is also called the remote host user access rule, is implemented with the following line. This rule specifies that only the pegasus user is allowed to access WBEM remotely. -: ALL EXCEPT pegasus:wbemnetwork Edit the remote host user access rule to allow HP WBEM s for Linux access by adding root to the line, as follows: -: ALL EXCEPT pegasus root:wbemnetwork NOTE: It is not necessary to restart the WBEM server after the PAM configuration file is modified. 8. Test the installation and configuration of OpenPegasus by accessing your server through HP SIM. For details, see the HP Systems Insight Manager Installation and Configuration Guide for Linux at: Installing using HP Integrity Essentials Foundation Pack for Linux To install HP WBEM s for Linux using HP Integrity Essentials Foundation Pack for Linux, follow the installation procedure in Chapter 5, of the HP Integrity Essentials Foundation Pack for Linux User's Guide: Configuring HP WBEM s for Linux No additional configuration is required for HP WBEM s for Linux to operate. Installing using HP Integrity Essentials Foundation Pack for Linux 11

12 3 Troubleshooting This section provides instructions for troubleshooting basic installation issues. The following assumptions were made when developing this information: The providers are not responding to inquiries from HP SIM. You are a Linux system administrator with root privilege. No errors were issued during provider installation and initial configuration. Commands and options are capitalized correctly. You have access to several terminal windows and you have multiple command lines available. You understand that shutting down the firewall to troubleshoot creates a security breach, and you assume all risks inherent with that procedure. Important Information About Firewalls and Troubleshooting Some Linux distributions automatically configure firewall software during installation, usually using iptables, which is the standard Linux kernel s method of providing firewall support. Such a firewall configuration might block remote management stations from contacting the OpenPegasus server, making it difficult to troubleshoot HP WBEM s for Linux. To execute the troubleshooting steps in this document, you must shut down firewall software on the managed server using the following steps. The information in the Diagnosing Problems (page 12) section applies only when you have the standard Linux firewall capabilities of iptables. Consult your network administrator to determine if this situation exists. Shutting Down iptables WARNING! Inform your network administrator before you stop a running firewall, even momentarily. Disabling the firewall creates a potential security breach, and you must weigh this threat against the benefits of live troubleshooting. 1. Enter /etc/init.d/iptables status to see if the firewall software is installed and running. If you see the message No such file or directory, then standard firewall software is not installed and you can proceed to Diagnosing Problems (page 12). Or If you see the message Firewall is stopped, proceed to Diagnosing Problems (page 12). Or If you see output indicating the firewall is running, proceed to the next step. 2. If the firewall is running, enter /etc/init.d/iptables stop to stop the firewall. You can then proceed to Diagnosing Problems (page 12). Diagnosing Problems If your system is not visible to HP SIM, you should begin your troubleshooting from the host itself, and then move on to the network toward the host running HP SIM. Follow these steps to start diagnosing problems with HP WBEM s for Linux on your system: 1. Log on to the system and check that the cimserver process is running by entering the following command: 12 Troubleshooting # ps auxww grep cimserver Ensure that a /usr/sbin/cimserver process is running similar to the following: root ? Ssl 13:30 0:00 /usr/sbin/cimserver

13 2. If the cimserver is not running, start it using the following command: # /etc/init.d/tog-pegasus start 3. Check to see if OpenPegasus is installed and running, enter: # osinfo If relevant information about your system is displayed, similar to the following, then OpenPegasus is running: OperatingSystem Information Host: test.cao.cpqcorp.net Name: Red Hat Enterprise Linux AS ( EL #1 SMP Fri Feb 24 16:49:08 EST 2006 ) Version: EL UserLicense: Unlimited user license Number of Users: 1 users Number of Processes: 69 processes OSCapability: 64 bit LastBootTime: Jul 21, :54:12 (01000) LocalDateTime: Aug 11, :13:13 (01000) SystemUpTime: seconds = 21 days, 0 hrs, 19 mins, 1 sec Otherwise, it is not running and you must check the installation of OpenPegasus. It might be necessary to uninstall and reinstall the tog-pegasus RPM that comes with your distribution; for SLES9, reinstall the tog-pegasus RPM from the HP Integrity Essentials Foundation Pack for Linux Support Pack. 4. Check that appropriate changes have been made to the PAM configuration file (/etc/pegasus/access.conf) to allow remote access as described in the Installing and Configuring (page 10). NOTE: The default configuration of OpenPegasus does not allow access to the WBEM server over the network. 5. Test network connectivity between the management station and your system. If your management station is named hpsim.your.domain, run the command ping hpsim.your.domain to test network connectivity. If the command fails, there is a problem with your network configuration, which you must investigate and repair before continuing with troubleshooting. 6. Ensure that the user name and password credentials used by HP SIM are correct. When HP SIM discovers a new system and probes it for WBEM support, you might see errors similar to the following in /var/log/messages: Aug 11 08:47:46 deckchair wbem(pam_unix)[9827]: check pass; user unknown Aug 11 08:47:46 deckchair wbem(pam_unix)[9827]: authentication failure; logname= uid=0 euid=0 tty=wbemnetwork ruser= rhost= Aug 11 08:47:48 deckchair cimserver[9827]: pam_authenticate failed: Authentication failure Aug 11 08:47:48 deckchair cimserver[9827]: PAM authentication failed for remote user: Administrator A set of messages similar to the previous appears for each user name and password combination attempted by HP SIM during the discovery process. If this does not occur, the most likely cause is HP SIM is unable to connect to the server due to a network connectivity problem is in need of resolution. Diagnosing Problems 13

14 4 Release Notes New, Changed, and Deprecated Features This section contains important information about new, changed, and deprecated features in each release of HP WBEM s for Linux. December 2007 Release New Features Changed Features Deprecated Features August 2007 Release New Features Changed Features Deprecated Features March 2007 Release New Features Changed Features Deprecated Features November 2006 Release New Features Changed Features Deprecated Features The System Firmware Inventory is introduced in this release. The Fibre Channel Host Bus Adapter is updated to indicate the changes in the reporting of driver and firmware versions. There are no deprecated features in this release. The HP System Inventory and Disk Partition are introduced in this release. There are no changed features in this release. The HP Disk Partition is deprecated and is replaced by the Disk Partition. The Fibre Channel Host Bus Adapter is introduced in this release. All provider datasheets are updated to indicate support for RHEL5 and SLES10. There are no deprecated features in this release. There are no new features in this release. The following features have changed from the previous release of HP WBEM s for Linux: The Forward Progress Log is enhanced to include the HP_FPLIndication class. The HP Processor is enhanced to include the LoadPercentage and SpuId properties in the HP_Processor class. Renamed the HP_ComputerSystem class to the PG_ComputerSystem in HP Computer System. All provider datasheets are updated to indicate the supported namespaces. There are no deprecated features in this release. 14 Release Notes

15 September 2006 Release New Features Changed Features Deprecated Features The following features are new with this release of HP WBEM s for Linux: The Forward Progress Log is introduced. The System Event Log is introduced. The Profile Registration Profile is introduced. The following features have changed from the previous release of HP WBEM s for Linux: Updated the HP SCSI Protocol Controller to include newly supported controller cards. Fixed crash bug in HP IPMI Sensors when debugging enabled Renamed the incorrectly named HP_RealizesPCIDevice class to the HP_RealizesPCIController class generated by the HP PCI Devices and Locations. Renamed the incorrectly named HP_SystemController class to the HP_ComputerSystemPCIController in HP Computer System. The following features are deprecated with this release of HP WBEM s for Linux: The CIM Network is deprecated and is replaced by the HP Network. The CIM SCSI Controller is deprecated and is replaced by the HP SCSI Protocol Controller. Known Problems and Limitations Due to problems in previous releases of the HP Integrity Foundation Pack for Linux, the upgrade option of the RPM package manager does not operate correctly so the rpm -U upgrade command cannot be used when installing the HP WBEM s from the command line. You must completely remove each individual previous version (or RPM) of the providers before installing new versions as described in Step 1 of the Installing using the Command Line (page 10) section. This does not affect installing the providers using the HP Integrity Essentials Foundation Pack for Linux installer as described in Chapter 5, of the HP Integrity Essentials Foundation Pack for Linux User's Guide: Known Problems and Limitations 15

16