HP Systems Insight Manager 6.3 Installation and Configuration Guide for Linux Abstract This document describes the installation and configuration of HP Systems Insight Manager. This document is intended for system administrators who plan to install and use Systems Insight Manager. It is helpful to have previous experience with HP Systems Insight Manager and a Linux operating system. HP Part Number: 418811-008 Published: April 2011 Edition: 6.
© Copyright 2003, 2011 Hewlett-Packard Development Company, L.P. Legal Notices 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.
Contents 1 Installation overview and requirements..........................................................5 First time install process overview................................................................................................5 Upgrade overview....................................................................................................................5 System requirements..................................................................................................................
8 Troubleshooting........................................................................................43 9 Support and other resources......................................................................46 Information to collect before contacting HP.................................................................................46 How to contact HP..................................................................................................................
1 Installation overview and requirements This chapter provides an overview of the HP Systems Insight Manager installation process, and it identifies the system requirements for a Linux CMS, a managed system, and a network client. First time install process overview Perform these steps for a first time install of HP Systems Insight Manager on your CMS: 1. Install and configure the CMS. For details, see “Installing Systems Insight Manager on the CMS for the first time” (page 20). 2.
• SUSE Linux Enterprise Server 10 x86, SP2 • SUSE Linux Enterprise Server 10 AMD64/EM64T, SP2 Installation overview and requirements
NOTE: Systems Insight Manager can run on a Linux Virtual Machine (VM) provided the following requirements are met. The VM must be hosted on an ESX 3.0.1 or later server and the VM configuration must meet Systems Insight Manager hardware requirements and the CPU and Memory resources allocated to this VM must be always available to this VM (by reserving CPU and Memory resources). NOTE: Installing a Systems Insight Manager CMS on Linux Itanium Processor Family (IPF) is not supported.
• General: ◦ OpenSSH version 1.0 or later ◦ ProLiant Support Pack for Linux 7.00 or later ◦ (Optional) Oracle 9i release 2 ◦ Oracle 10g R2 (10.2.0.3) or later NOTE: Oracle supports up to 5,000 systems and 50,000 events. NOTE: You must install the Oracle JDBC driver, version 10.2.0.4. You can download this driver from the Oracle website at http://www.oracle.com/technology/software/ tech/java/sqlj_jdbc/index.html.
• Windows managed systems ◦ Windows Server 2008 R2 Standard, SP1 ◦ Windows Server 2008 R2 Enterprise, SP1 ◦ Windows Server 2008 R2 Data Center, SP1 ◦ Windows Server 2008 R2 Web Server, SP1 ◦ Windows HPC Server 2008 R2 ◦ Windows Server 2008 R2 Standard ◦ Windows Server 2008 R2 Enterprise ◦ Windows Server 2008 R2 Data Center ◦ Windows Server 2008 R2 Small Business Server ◦ Windows Server 2008 R2 Web Server ◦ Windows Server 2008 R2 Itanium ◦ Windows Server 2008 Standard, SP2 ◦ Windows
• • 10 ◦ Windows 2003 Enterprise (IA64) SP1 ◦ Windows 2003 Enterprise, SP2 ◦ Windows 2003 Enterprise (x64), SP2 ◦ Windows 2003 Enterprise (IA64) SP2 ◦ Windows 2003 Data Center, SP1 ◦ Windows 2003 Data Center (x64), SP1 ◦ Windows 2003 Data Center (IA64), SP1 ◦ Windows 2003 Data Center, SP2 ◦ Windows 2003 Data Center (x64), SP2 ◦ Windows 2003 Data Center (IA64), SP2 ◦ Windows 2003 Web Edition SP1 ◦ Windows 2003 Web Edition SP2 ◦ Windows 2003 Small Business SP1 ◦ Windows 2003 Smal
• ◦ Red Hat Enterprise Linux 5 AMD64/EM64T, Update 4 ◦ Red Hat Enterprise Linux 5 IPF, Update 3 ◦ Red Hat Enterprise Linux 5 x86, Update 3 ◦ Red Hat Enterprise Linux 5 AMD64/EM64T, Update 3 ◦ Red Hat Enterprise Linux 6 IPF ◦ Red Hat Enterprise Linux 6 x86 ◦ Red Hat Enterprise Linux 6 AMD64/EM64T ◦ Red Hat Enterprise Linux 5 IPF, Update 6 ◦ Red Hat Enterprise Linux 5 x86, Update 6 ◦ Red Hat Enterprise Linux 5 AMD64/EM63T, Update 6 ◦ Red Hat Enterprise Linux 4 IPF, Update 8 ◦ Red Hat E
• • • ◦ VMWare ESX/ESXi 4.1 Update1 ◦ VMWare ESX 4.0 Update3 ◦ VMWare ESX 3.5 Update 5 ◦ VMWare ESX 3i Update 5 ◦ VMWare ESX 4.0 Update 2 ◦ VMWare ESX 4.0 Update 1 ◦ VMWare ESX 4i Update 1 ◦ VMWare ESX 4.
◦ • • Any HP Itanium-based system For HP-UX: ◦ Any HP PA-RISC system ◦ Any HP Itanium®-based system For Linux: ◦ Any HP ProLiant system ◦ Any HP Itanium-based system Software This software is not required, but if you want improved management capabilities, HP recommends that you install these components. For Windows: • OpenSSH Services 5.1p1 • ProLiant Support Pack 6.30 or later • WBEM/WMI • SNMP (recommended as an alternative to WBEM) For Linux: • SSH • ProLiant Support Pack for Linux 7.
Required web browsers • For Windows: ◦ Microsoft Internet Explorer 8 ◦ Microsoft Internet Explorer 7 ◦ Mozilla Firefox 3.5 (3.5.09.00) ◦ Mozilla Firefox 3.6 NOTE: 768. • • For optimum performance, the minimum resolution for the browser must be 1024 x For HP-UX: ◦ Mozilla Firefox 3.5 (3.5.09.00) ◦ Mozilla Firefox 3.6 For Linux: ◦ Mozilla Firefox 3.5 (3.5.09.00) ◦ Mozilla Firefox 3.6 NOTE: For all Internet Explorer browsers, you must have the SSL 3.0 or TLS 1.
blades and desktops, enclosure infrastructures, racks, and integrated switches, through hierarchical tree views/picture views. Users are able to conveniently manage individual or groups of blade systems. System support BladeSystem Integrated Manager manages blade infrastructures. For an updated list of supported systems, see http://h18002.www1.hp.com/products/servers/management/bsme/index.html. On the right side of the screen, select Support & Documents.
Table 4 Supported c-Class Servers (continued) Product Models Minimum BIOS — System ROM required Minimum Integrated Lights-Out (iLO) / iLO 2 / firmware version required Operating Systems Supported1 Minimum ProLiant Support Pack (PSP) required Windows PCI expansion blades NA NA NA ProLiant BL260c G6 NA 1.75 or later Windows, Linux, 8.20 Solaris, and NetWare ProLiant BL260c G5 l20 02/14/2008 1.50 or later Windows and Linux 8.00 ProLiant BL280c G6 I22 3/11/09 1.75 Windows and Linux 8.
Table 5 Supported Servers HP Consolidated Client Infrastructure (CCI) (continued) Product Models Minimum BIOS — System ROM required Minimum Integrated Lights-Out (iLO) / iLO 2 / firmware version required Operating Systems Supported1 Minimum ProLiant Support Pack (PSP) required Windows Windows ProLiant BL1000 2.04 A 4.01 Rev. A2 Windows XP NA Windows XP or Vista NA Windows XP or Vista NA Windows XP or Vista NA 15 Jan 2008 ProLiant BL1500 1.02 Rev. AÂ 4.01 Rev.
Table 7 Supported p-Class Servers (continued) Product Models Minimum BIOS — System ROM required Minimum Integrated Lights-Out (iLO) / iLO 2 / firmware version required Operating Systems Supported1 Minimum ProLiant Support Pack (PSP) required Windows (17 Jan 2008) ProLiant BL25p ProLiant BL25p G2 2007.09.23 (A) 1.70 or later Windows and Linux 7.20 or later 1.24 or later Windows and Linux 7.60 or later 1.88 or later Windows and Linux 1.70 or later Windows and Linux 7.10 or later 1.
Table 8 Supported c-Class Interconnects/Switches (continued) Product Models Minimum Software Management firmware version HP GbE2c Layer 2/3 Ethernet Blade Switch 2.0.4 HP Virtual Connect Flex-10 10Gb Ethernet Module for BladeSystem c-Class 2.25 HP Virtual Connect 8Gb Fibre Channel Module (24-port) NA Brocade 8Gb SAN Switch for HP BladeSystem c-Class NA HP NC382m Dual Port 1GbE BL-c Adapter Boot code version 4.4.14 and MBA version 4.4.16 QMH2562 8Gb FC for HP BladeSystem c-Class 4.04.
2 Installing Systems Insight Manager on the CMS for the first time Preparing the system Perform step 1 for a first time install of Systems Insight Manager on your CMS. 1. Install and configure the CMS. 2. Install and configure the required management software on the systems that will be managed by the CMS. For details, see “Setting up managed systems” (page 28). 3. Configure Systems Insight Manager for your environment. For more information, see “Configuring Systems Insight Manager” (page 30).
5. In the directory where you downloaded or copied the files, change user permissions to add execute permissions to the bin file: chmod +x *.bin or chmod +x HPSIM*.bin 6. Verify that the following required software dependencies are available on your system, and install any that are not already installed. a. Verify that SSH is installed by executing the following command: rpm -qa | grep ssh If SSH is not installed, the previous command does not return any results.
NOTE: For information on setting permissions, see Step 5. The HPSIM-Linux*.bin file will extract the RPM Package Manager (RPM) files, install hpsmdb, and then continue with the Systems Insight Manager installation. NOTE: After installation is complete, log out of the operating system and then log back in to set all the correct file permissions and system environments. To complete the initial set up of Systems Insight Manager refer to “After installing Systems Insight Manager” (page 23).
a. View the status by executing the following command: /etc/init.d/postgresql status b. Configure hpsmdb to run during startup by executing the following command: chkconfig hpsmdb 345 c. If the status is unused in any version of Red Hat Linux or SUSE Linux, start the daemon by executing the following command: ◦ For SUSE Linux Enterprise Server 10 SP2 or later: /etc/init.d/hpsmdb start ◦ For Red Hat Enterprise Linux (all versions) /etc/rc.d/init.d/hpsmdb start Or /etc/init.
mxoracleconfig -h hostname [-n port number] -d database name -u username -p password [-j driver jar file location] [-f ] -h Hostname Full DNS name or IP address of the Oracle server. -n Port number Port number to be used to connect to the oracle instance. Default port is 1521. -d Database name Name of database instance. -u Username Database user name. -p Password Database password for the corresponding user name. -j Driver file location Full path to thin driver .jar file. This is not required if the .
If they are not running, start them by executing the following command: /opt/mx/bin/mxstart Installing and configuring the software 25
6. Optional: Configure the system to send SNMP traps. NOTE: These steps might vary slightly, depending on your version of Linux. Refer to your Linux provider for details if these file paths and file names do not exist on your system. a. Verify that SNMP is installed by executing the following command: rpm -qa | grep snmp If SNMP is not installed, the previous command does not return a components list. Refer to your Linux provider for information on installing SNMP. b.
If the line is not present, enter the CMS to the read-only community manually by adding the line: rocommunity CommunityName IPaddress where CommunityName is the SNMP community string used by the CMS and IPaddress is the IP address of the CMS. iii. Save the changes to the file. To save and close this file using the vi editor, press the Esc key, enter :wq!, and press the Enter key. f. Start the SNMP daemon by executing the following command: /etc/init.d/snmpd start g.
3 Setting up managed systems Perform step 2 to install and configure the required management software. 1. Install and configure the CMS. For more information, see “Installing Systems Insight Manager on the CMS for the first time” (page 20). 2. Install and configure the required Insight Management Agents on the systems that will be managed by the CMS. 3. Configure Systems Insight Manager for your environment. For more information, see “Configuring Systems Insight Manager” (page 30).
Configuring SMI-S providers Occasionally, it might be necessary to modify an SMI-S provider's port number or password. Use the provider documentation to perform these modifications. For example, if two CIMOMs exist on the same host, you must configure them to use different ports to communicate with the CMS.
4 Configuring Systems Insight Manager Perform step 3 to configure Systems Insight Manager for your environment. 1. Install and configure the CMS. For more information, see “Installing Systems Insight Manager on the CMS for the first time” (page 20). 2. Install and configure the required Insight Management Agents on the systems that will be managed by the CMS. For more information, see “Setting up managed systems” (page 28). 3. Configure Systems Insight Manager for your environment.
• Configure Managed Systems Configure managed systems as they are discovered, by configuring WBEM and WMI, SNMP, SSH access, and trust relationship. • WBEM/WMI Mapper Proxy To retrieve managed system information on Windows systems, enter the mapper proxy system host name and port number. NOTE: • This page only appears if you selected to manage a Windows operating system.
It is important that you plan which systems each user is going to manage and which specific set of tools the users are authorized to execute against the managed systems. A user with no toolbox authorizations on a system cannot view or manage that system. Authorizations are additive. If a user is authorized on Toolbox1 on a system and is also authorized for Toolbox2 on the same system, the user is authorized for all tools in both Toolbox1 and Toolbox2 on that system.
Procedure 3 1. Install and configure SSH. a. Verify that SSH is installed on the managed system: rpm -qa | grep ssh If it is not installed, see your Linux provider for information on installing SSH. b. On the CMS, copy the SSH generated public key from the CMS to the managed system, and place it in the authorized keys file of the execute-as user (root or administrator).
2. Optional: Configure the system to send SNMP traps. NOTE: These steps might vary slightly, depending on your version of Linux. See your Linux provider for details if these file paths and file names do not exist on your system. a. Verify that SNMP is installed: rpm -qa | grep snmp If it is not installed, see your Linux provider for information on installing SNMP. b.
5 Upgrading from Systems Insight Manager This chapter provides the steps to upgrade Systems Insight Manager 5.3.1 and later. Before beginning the Systems Insight Manager upgrade, verify that your user name and password to access to the database are valid.
c. d. Select the checkbox, save the changes, and then start the service. To start hpsmdb by using the command line, execute the following command: /etc/rc.d/init.d/hpsmdb start Or /etc/init.d/hpsmdb start • For SUSE Linux Enterprise Server 10 SP2 or later: a. View the status by executing the following command: /etc/init.d/postgresql status b. Configure hpsmdb to run during startup by executing the following command: chkconfig hpsmdb 345 c.
7. Complete the upgrade by restarting the Systems Insight Manager daemons using mxstop and mxstart. Systems Insight Manager is now installed and initialized on the CMS. To browse to Systems Insight Manager, start the Systems Insight Manager graphical user interface (GUI) using Firefox, or Internet Explorer at http://:280/. 8. After upgrading to Systems Insight Manager 5.
6 Uninstalling Systems Insight Manager Uninstalling Systems Insight Manager from a Linux system CAUTION: Removing Systems Insight Manager permanently deletes the information in the database unless you back it up before removing the software. Procedure 6 Removing Systems Insight Manager 1. Stop the Systems Insight Manager daemons: /opt/mx/bin/mxstop 2.
7 Configuration options Several configurable parameters in Systems Insight Manager that are not available from the GUI. These parameters can only be configured by editing a configuration file on the CMS. NOTE: All Systems Insight Manager parameters have been set to predefined values that are appropriate for most situations. These parameters should only be changed if you are experiencing issues with the default values. There are two main default locations where configuration files are stored.
Monitor time-out policy The monitor time-out policy keeps sessions alive, provided the user has a web browser window open displaying the HP Systems Insight Manager GUI. Closing the browser or navigating to another web page starts the timer for the time-out period. The default time-out period is 20 minutes. Users must use some other means to protect an unattended session from illegal use, such as password-protected screen savers.
Implementation Changes made to the log.properties file do not take effect until the log manager daemon or service is restarted. Restart the HP Systems Insight Manager service. CAUTION: The queue size should be changed only with extreme care. If the queue is set too high, the log manager consumes too much system memory. NOTE: When the Audit Log file reaches the maximum file size, the log is renamed with MX_LOGROLLFILEEXT extension and a new file is started.
Frequently scheduled tasks Task results can also be removed from the Task Results Page if a certain number of task results for a scheduled task accumulate. This setting defaults to 10 instances of a single task. If more than 10 accumulate on the results page, then the oldest task result for this scheduled task is removed. Last result tasks A task result is kept indefinitely if it is the last result for a scheduled task.
8 Troubleshooting Q Q Q Q Q & & & & & A A A A A 8.1 “Browser issues” 8.2 “GUI issues” 8.3 “Installation issues” 8.4 “Sign in issues” 8.5 “GUI issues” 8.1 Browser issues 8.8.1.1 Accessing some of the menu items on a Linux CMS causes the page to go blank. Solution: If using Firefox and this happens, click back on the displayed page, and the menus will be refreshed. 8.2 GUI issues 8.8.2.1 8.8.2.
When you examine the contents of PgSQL_Config.log, the following lines are displayed: Starting PostgreSQLpg_ctl: postmaster does not start...failed No PostgreSQL RPM Solution: Manually start the PostgreSQL service by performing the following steps: Procedure 9 Manually starting the PostgreSQL service 1. Navigate to the /etc/init.d directory and execute the following command: ./postgresql stop 2. 3. Log in as user postgres (su postgres).
the browser Internet Zone. From the browser menu, select Tools→Internet Options, and click the Connections tab. Click LAN Settings, and if you are configured to use a proxy server, click Advanced. In the Exceptions list, you can specify a list of addresses that should bypass the proxy server. These addresses are no longer in the Internet Zone and are not affected by the privacy settings policy. Solution 2B: (Not Recommended) Change the browser privacy security policy setting.
9 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support: • In the United States, see the Customer Service / Contact HP U
HP authorized resellers For the name of the nearest HP authorized reseller, see the following sources: • In the United States, see the HP U.S. service locator web site: http://www.hp.com/service_locator • In other locations, see the Contact HP worldwide web site: http://welcome.hp.com/country/us/en/wwcontact.html Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to:docsfeedback@hp.
computer output Text displayed by the computer. Enter The name of a keyboard key. Note that Return and Enter both refer to the same key. A sequence such as Ctrl+A indicates that you must hold down the key labeled Ctrl while pressing the A key. term Defined use of an important word or phrase. variable The name of an environment variable, for example PATH or errno. value A value that you may replace in a command or function, or information in a display that represents several possible values.
Glossary A administrative rights user A user who is authorized for the All Tools toolbox on all systems, including the Central Management Server. This type of user has been given special privileges to administer the HP Systems Insight Manager software. administrator A user who manages users, resource pools, and self-service requests through HP Insight Orchestration console. agent A program that regularly gathers information or performs some other service without the user's immediate presence.
certificate An electronic document that contains a subject's public key and identifying information about the subject. The certificate is signed by a certificate authority (CA) to bind the key and subject identification together. See also certificate authority. certificate authority A trusted third-party organization or company that issues digital certificates used to create digital signatures and public-private key pairs.
custom tools Custom tools are tools that can be created by the user to run on the Central Management Server or on target systems. For example: • Remote tool A tool that runs on selected target systems. It might copy files to the target systems or run specific X-Window applications on the target systems. You can schedule this tool. • CMS tool A tool that runs on the CMS. It is usually a script or batch file and can pass in environment variables.
enclosure A physical container for a set of server blades. It consists of a backplane that routes power and communication signals and additional hardware for cabling and thermal issues. It also hosts the CPU or server power supplies. event Information sent to certain users that something in the managed environment has changed. Events are generated from SNMP traps. HP Systems Insight Manager receives a trap when an important event occurs. Events are defined as: • Warning.
HP Insight Control database The database that stores vital information about HP Systems Insight Manager, including users, systems, and toolboxes. HP Insight Control power management An integrated power monitoring and management application that provides centralized control of server power consumption and thermal output at the datacenter level. It extends the capacity of datacenters by enabling the user to control the amount of power and cooling required for ProLiant servers.
M Major status Status information collected from the system that indicates one or more of the monitored subsystems are not operating properly which is impacting the system. Action should be taken immediately. managed systems Any system managed by HP Systems Insight Manager, such as servers, desktops, storage systems, and Remote Insight Boards (RIBs). management agent A daemon or process running on a managed system.
O Onboard Administrator The Onboard Administrator is the central point for controlling an entire c-Class enclosure. It offers configuration, power, and administrative control over the rack, and its associated blades (Compute Servers), blade management processors (iLOs), network switches (depending on the models of switches used) and storage components (such as SAN or SATA). The Onboard Administrator is a single management processor, with shared resources to an optional backup twin processor for failover.
information through your firewall and/or Web proxy to the HP Support Center for reactive support. Additionally, based on your support agreement, system information can be collected for proactive analysis and services. rack A set of components cabled together to communicate between themselves. A rack is a container for an enclosure.
server, so clients can be assured they are communicating with the server it claims to be. It is application protocol independent. secure task execution A feature of HP Systems Insight Manager that securely executes a task from a managed system. STE ensures that the user requesting the task has the appropriate rights to perform the task, and encrypts the request to protect data from snooping.
SMI-S provider An industry-standard WBEM provider that implements a well defined interface for storage management. The manufacturers of host bus adapters (HBAs), switches, tape libraries, and storage arrays can integrate SMI-S providers with their systems, or provide them as separate software packages. See also Web Based Enterprise Management. SNMP communication setting Default SNMP community string used when communicating with systems supporting SNMP communications.
system health status This is aggregate status all of the status sources (which can be SNMP, WBEM, and HTTP) that are supported on a target system, with the most critical status being displayed. The following are the different system health statuses that can be displayed: • Critical HP Systems Insight Manager can no longer communicate with the system. The system was previously discovered but cannot be pinged.
system properties properties can be set for a single system or for multiple systems at the same time and include options such as system name, system type, system sub-type, operating system version, asset number, contact information, and whether or not the system properties can be changed or updated by the discovery process. system search Logical grouping of systems into a collection based on information in the HP Systems Insight Manager database.
U uncleared event status Events that have a Critical, Major, Minor, Normal, or Informational severity and have not been cleared or deleted from the database. Events can be cleared without being deleted from the database by using the Clear events menu option. • Critical. A failure has occurred, and immediate attention is required. • Major. A failure is impending. • Minor. A warning condition exists that can escalate into a more serious problem. • Normal. These events are not a problem.
Web-Based Enterprise Services A tool suite that is aimed at preventing or reducing the downtime of a system. Web-launch aware A run type for tools that are launched in a web browser using a web server. WLA tools can be designed to deal with multiple systems. Windows Management Instrumentation An API in the Windows operating system that enables you to manage and control systems in a network. workspace The section of the GUI where tools appear.
Index A active time-out, 39 audit log configure, 40 C Central Management Server Linux system preparation, 20 central management server installing Systems Insight Manager on Linux, 21 requirements, 5 configuration audit log, 40 data collection CPU utilization, 39 lifetimes for Task Result entries, 41 managed system, 28 time-out policy, 39 configuration options, 39 configuring first time wizard, 30 HP Systems Insight Manager, 30 managed systems, 30 CPU utilization, 39 customization options, 39 D data collec
U Uninstall Central Management Server removing Systems Insight Manager on Linux, 38 upgrading Systems Insight Manager overview, 35 process, 35 64 Index
