Insight Control for Linux 7.0 Installation Guide Abstract This document describes how to install HP Insight Control for Linux and how to configure it to interoperate with HP Systems Insight Manager. This document is intended for anyone who is responsible for installing and configuring Insight Control for Linux. It is helpful to have previous experience as a Linux system administrator and to have some knowledge of Systems Insight Manager.
© Copyright 2008, 2010, 2011, 2012 Hewlett-Packard 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 Product overview........................................................................................6 1.1 Product description..............................................................................................................6 1.2 Insight Control for Linux tools and features..............................................................................6 1.3 Licensing.......................................................................................................................
5 Installing Systems Insight Manager and Insight Control for Linux......................37 5.1 Insight Control for Linux installation overview.........................................................................37 5.2 Preparing for Insight Control for Linux installation questions....................................................37 5.2.1 DHCP server configuration questions............................................................................40 5.3 Validating RPM signatures (optional).............
10.5 Documentation feedback..................................................................................................64 10.6 New and changed information in this edition.....................................................................64 10.7 Related information.........................................................................................................64 10.7.1 Documents..............................................................................................................64 10.
1 Product overview This chapter provides an overview of HP Insight Control for Linux , its features, and its licensing requirements. 1.1 Product description Insight Control for Linux is a Linux-hosted management product for HP ProLiant servers in enterprise environments and high performance workgroups. Insight Control for Linux is designed as a plug-in to Systems Insight Manager (Systems Insight Manager).
• Total control monitoring with integrated industry-proven open source monitoring tools The following open source monitoring tools have been integrated into Insight Control for Linux: • ◦ Nagios, a system and network monitoring application that provides monitoring capabilities for Insight Control for Linux. Nagios watches specified hosts and services and issues alerts when problems occur and when problems are resolved. ◦ RRDtool, a round robin database tool and graphing system.
Insight Control for Linux enables you to reboot, power on, and power off a managed system through its management processor (MP) directly from the Tools→Server Controls menu. Remote power control operations are documented in the HP Insight Control for Linux User Guide.
HP provides script templates in the /opt/repository/script directory for you to review for suggested uses. The directories and scripts are named: postdeploy_example.sh, predeploy_example.sh, postcapture_example.sh, and precapture_example.sh. You are free to use your own script names. • Microsoft Windows interactive installation using generic ISO mounting You can install a generic ISO- or Microsoft Windows to iLO-based servers.
1.3 Licensing Insight Control for Linux uses the Systems Insight Manager License Manager as its licensing model. When you purchase Insight Control for Linux, you receive a license entitlement package that describes how to retrieve your Insight Control for Linux license keys. The license redemption process generates the license keys for Insight Control for Linux and the license keys for the HP Lights-Out 100i Advanced Pack, another product in the HP Insight Control family of core products.
2 Installation and configuration checklist The checklist shown in Table 1 provides a summary of the steps that are required to install and configure Insight Control for Linux. Table 1 Insight Control for Linux installation and configuration checklist Task Documented in Prepare for the Insight Control for Linux installation process: 1. Read the HP Insight Control for Linux Release Notes. 2. Verify installation requirements and ensure that you have all the items you need to begin the installation process.
3 Preparing for the Insight Control for Linux installation This chapter describes Insight Control for Linux preinstallation tasks. It is especially important that you prepare the server you have chosen to be the CMS to meet all requirements for Systems Insight Manager and Insight Control for Linux according to the instructions in this chapter. 3.
• Remote repository Using a remote repository can save on virtualized I/O and storage needs. This is an opportunity to distribute the work load, allowing a file server to provide the OS install repository. NOTE: Distributing the repository is not an advantage when installing ESXi hosts because the entire distribution resides in the /opt/repository/boot directory, unlike RHEL, SLES, or ESX installations.
Table 2 Installation requirements (continued) Item Requirement Minimum firmware versions All components of the CMS and all ProLiant servers you want to manage with Insight Control for Linux must meet the minimum firmware requirements listed in the HP Insight Control for Linux Support Matrix. ProLiant Support Pack You must have downloaded a copy of the PSP that has been tested with this version of Insight Control for Linux and is appropriate for your hardware.
3.4.1.2 Verify that required OS RPMs are installed Verify that all RPM package dependencies are installed on the CMS. The Insight Control for Linux installation process verifies RPM dependencies and alerts you if an RPM is missing on the CMS.
Table 4 RHEL version 4 RPM requirements Platform Required RPMs RPM requirements common to all RHEL 4 apr apr-util compat-libstdc++-296-2.96 dhcp distcache e2fsprogs-devel gd glib httpd krb5-devel libart_lgpl libtool-libs1 lm_sensors mkisofs mod_ssl net-snmp net-snmp-utils openssh openssl-devel perl-Compress-Zlib perl-HTML-Parser perl-HTML-Tagset perl-libwww-perl perl-Time-HiRes perl-URI php redhat-lsb tftp-server zlib zlib-devel RPM requirements specific to audit-libs.i386 compat-libstdc++-296.
Table 5 RHEL version 5 RPM requirements (continued) Platform Required RPMs krb5-devel krb5-devel ksh libart_lgpl libselinux-devel lm_sensors mkisofs mod_ssl net-snmp net-snmp-utils openssh openssl-devel perl-Compress-Zlib perl-HTML-Parser perl-HTML-Tagset perl-libwww-perl perl-URI postgresql-libs php redhat-lsb tftp-server zlib zlib-devel RPM requirements specific to audit-libs.i386 compat-libstdc++-296.i386 RHEL 5 X64 compat-libstdc++-33.i386 cracklib.i386 gd.x86_64 glib2.i386 ksh libgcc.i386 libselinux.
Table 6 RHEL version 6 RPM requirements (continued) Platform Required RPMs perl-HTML-Tagset perl-Time-HiRes perl-URI perl-libwww-perl php postgresql-libs RPM requirements specific to audit-libs compat-libstdc++-296 RHEL 6 X64 compat-libstdc++-33 cracklib e2fsprogs-devel glib2 keyutils-libs-devel krb5 krb5-devel libgcc libselinux libselinux-devel libsepol-devel net-snmp openssh pam sqlite zlib zlib-devel RPM requirements specific to audit-libs compat-libstdc++-296 RHEL 6 i386 compat-libstdc++-33 cracklib d
Table 7 SLES version 10 RPM requirements (continued) Platform Required RPMs libart_lgpl lsb mm net-snmp openssh openssl-devel perl-HTML-Parser perl-HTML-Tagset perl-libwww-perl php5 php5-timezonedb plotutils sensors zlib RPM requirements specific to audit-libs-32bit compat-32bit SLES 10 X64 compat-32bit-2006.1.25-11.2.x86_64.rpm compat-openssl097g-32bit-0.9.7g-13.9.
Table 8 SLES version 11 RPM requirements (continued) Platform Required RPMs perl-HTML-Tagset perl-libwww-perl php5 plotutils sensors zlib RPM requirements specific to audit-libs-32bit cracklib-32bit SLES 11 X64 ksh libdb-4_5-32bit libstdc++33-32bit libxcrypt-32bit pam-32bit pam-modules-32bit zlib-32bit RPM requirements specific to audit-libs cracklib SLES 11 i386 ksh libstdc++33 libdb-4_5 libstdc++43 libxcrypt pam pam-modules 1 2 2 TFTP is also supported, but HP recommends installing ATFTP.
NOTE: You can skip the PSP installation step in the following circumstances: • When the CMS is an http://www.hp.com/servers/dl DL100 series server (such as the DL160, DL165, DL180, and DL185). PSPs are not available for those hardware models. • When you are installing Insight Control for Linux in a virtual machine guest. See the HP Insight Control for Linux Support Matrix for the PSP version that has been tested and qualified for this release.
# /sbin/hpsnmpconfig For a sample of the SNMP configuration questions and how to respond, see the related appendix in the HP Insight Control for Linux User Guide. Typically, you can accept the default responses to most questions. 3.4.2.3 Modify the CMS entry in the /etc/hosts file View the CMS information in the /etc/hosts file to ensure that the real host name of the CMS is not equated to localhost. Example 1 provides an example of the contents of this file.
Table 9 Network ports on the CMS that must be open to inbound traffic (continued) Port number Service Protocol 280 Systems Insight Manager web server TCP 443 https TCP/UDP 514 syslog-ng UDP 873 rsync TCP 2301 and 2381 HP System Management Homepage TCP 2709 mond TCP 2710 supermon TCP nrpe TCP 5667 nsca TCP 6500 cmfd TCP 50000 Systems Insight Manager secure web server TCP 50001 Systems Insight Manager SOAP TCP 50002 Database communication with management hubs TCP 60000
If your company policy prevents you from using NFS, you can manually export the /hptc_cluster file system using a different mechanism. Procedure 1 Opening ports on RHEL operating systems 1. Use a text editor to create a /etc/sysconfig/nfs file on a RHEL Version 4 OS or modify the /etc/sysconfig/nfs on a RHEL Version 5 OS with content similar to the following to lock most of the NFS services to specific port numbers. You can use any available port number above 1024.
# MOUNTD_PORT="33777" . . . Save your changes and exit the text editor. 2. Use a text editor to modify the /etc/services file to lock down the quota daemon: rquotad rquotad 14900/udp 14900/tcp Save your changes and exit the text editor. 3. Stop NFS with the following command: # /etc/init.d/nfsserver stop 4. Use a text editor either to create the /etc/modprobe.
HP recommends leaving at least 10 GB of free space available for the repository. Although the size varies by what you are storing, 10 GB is enough space to store the following: • Two Linux operating systems • Two captured Linux images • Two PSPs • Several script files • Several Kickstart and AutoYaST installation configuration files If you expect to be storing a lot of data in the repository, HP recommends mounting a separate file system at /opt/repository to ensure sufficient disk space.
4 Configuring the network This chapter describes Insight Control for Linux networking requirements, including how to properly configure DHCP, which is a requirement for Insight Control for Linux if you are not using virtual media to boot managed systems. When you are finished configuring the network, proceed to Chapter 5 (page 37) to install Systems Insight Manager and Insight Control for Linux. 4.
• Pre-execution Environment (PXE) for booting1 • HTTP/HTTPS • rsync • Simple Network Management Protocol (SNMP) • Trivial File Transfer Protocol (TFTP) All systems, routers, and firewalls involved in Insight Control for Linux communication must be configured not to block this traffic. Table 9 (page 22) lists the inbound network ports on the CMS that must be open on a firewall.
HP recommends the following network configurations for Insight Control for Linux: • “Two-tier network topology” (page 29) • “Flat single network topology” (page 29) 4.2.
4.3 Configuring a DHCP server This section describes the requirements and best practices for configuring a DHCP server for Insight Control for Linux if you do not elect to configure a DHCP server on the CMS during the Insight Control for Linux installation process. 4.3.1 DHCP minimum requirements Serving managed systems with DHCP is an absolute requirement to use the Insight Control for Linux deployment features, unless you plan on using virtual media to boot managed systems.
# Insight Control for Linux settings option option-140 code 140 = text; option option-140 "172.1.1.1"; next-server 172.1.1.1; filename "pxelinux.bin"; # log-servers option log-servers 172.1.1.1; subnet 172.1.1.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; range dynamic-bootp 172.1.1.100 172.1.1.200; default-lease-time 1209600; max-lease-time 1814400; } 1 1 The range means that this DHCP server assigns IP addresses at random from the pool of specified addresses.
• IP address to assign to the NIC • Host name to assign to the server. The host-name field is data that is passed to the managed server to set its default host name. NOTE: In Example 3, the settings required by Insight Control for Linux are shown in bold font. If you need more information about the required settings, see Table 10 (page 30). Example 3 Insight Control for Linux best practices in the /etc/dhcpd.
# iLO2 console port from server 2 host server002-cp { hardware ethernet 00:1E:0B:76:54:9C; fixed-address 192.0.2.22; option host-name "server002-cp"; } } 1 2 3 HP recommends running NTP or similar utility to maintain synchronization among the CMS and managed systems. Specify the NTP servers as list of fully qualified host names or IP addresses. This host name must agree with the DNS look up name or the host name entry if it exists in the /etc/hosts file.
4.4 Other network services The successful operation of Insight Control for Linux also requires the proper operation of the following network services, and these services are configured automatically. • “ATFTP/ TFTP configuration” (page 34) • “rsync configuration” (page 35) • “SNMP configuration” (page 35) • “NTP configuration” (page 36) 4.4.
Example 6 /etc/xinetd.d/tftp file for SLES and RHEL # default: off # description: The tftp server serves files using the trivial file # transfer protocol. The tftp protocol is often used to boot diskless # workstations, download configuration files to network-aware printers, # and to start the installation process for some operating systems. service tftp { disable = no socket_type = dgram protocol = udp wait = yes user = root server = /usr/sbin/in.
• trapsink sets the destination for any traps the system generates. This value must be the IP address or the name of the CMS. 4.4.4 NTP configuration HP recommends that you run NTP or another such utility on the CMS and managed nodes to synchronize their system clocks. See your Linux documentation for specifics on installing and configuring NTP.
5 Installing Systems Insight Manager and Insight Control for Linux This chapter describes how to install Systems Insight Manager and Insight Control for Linux. IMPORTANT: Use the instructions in this chapter if you are performing a new installation of Insight Control for Linux on a CMS. If you want to upgrade a previous version of Insight Control for Linux to this release, see Chapter 8 (page 54). 5.
Table 11 Insight Control for Linux installation questions Question Description and user action Oracle or default database You have the option to use an existing instance of a supported version of an Oracle database if you want to override the default Systems Insight Manager database.
Table 11 Insight Control for Linux installation questions (continued) Question Description and user action If the user name already exists, the existing password is overwritten by the password specified here. After Insight Control for Linux is installed and configured, you can change this default user name and password on all or individual managed systems from the Configure→Management Processor→Credentials... menu item.
Table 11 Insight Control for Linux installation questions (continued) Question Description and user action The HP Insight Control for Linux User Guide describes how to manually add the host names of the servers you want to act as management hubs to the Management_Hubs subcollection at the appropriate time. You do not have to do that before or during the installation process. The /hptc_cluster file system stores monitoring data collected by the management hubs.
Table 12 DHCP server configuration questions (continued) Item Description Default lease time (in seconds) Long lease times are very important to Insight Control for Linux. See Table 10 (page 30) for more information. The default value is 1209600 seconds (two weeks). Maximum lease time (in seconds) The maximum lease time is the longest time that a DHCP client considers an IP address lease as valid. If a client has not been able to update its address lease in that time frame, it will stop using it.
Validating the signature on an RPM Use the rpm –-checksig command to validate and verify the digital signature of an RPM. The output from the command indicates whether or not the RPM is correctly signed, as shown in these examples: NOTE: All RPMs can be found under /mnt/dirname/HP/RPMS/*. # rpm -checksig pdsh-hp-2.10-4.6.i386.rpm pdsh-hp-2.10-4.6.i386.rpm: (sha1) dsa sha1 md5 gpg OK # rpm –checksig gwt-1.4.60-1ct.src.rpm gwt-1.4.60-1ct.src.
Do you want to proceed? (y/n) [y] y NOTE: Default responses to all questions are enclosed in square brackets ([ ]). Press Enter to accept a default response. 5. Indicate whether or not you have read and accept the license agreement. If you have not read the agreement, enter n to display and read the agreement now. Have you read the license agreement? (y/n) [n] Do you accept this license agreement? (y/n) [n] The installation process does not start until you read and accept the license agreement. 6.
2 3 4 6 5 7 8 Select the device name that corresponds to the CMS management interface. The CMS management interface is the Ethernet adapter that is used for communication between the CMS and the managed systems. Enter the number of the TCP port that you want to use for the Insight Control for Linux repository web server; the default is port 60000. If another service is already using that port, you are prompted for another entry.
5.7 Logging in to Systems Insight Manager and using Insight Control for Linux To log in to Systems Insight Manager and begin using Insight Control for Linux, see Chapter 6 (page 46), specifically Section 6.2 (page 47). 5.
6 Logging in and configuring Systems Insight Manager If you installed Systems Insight Manager from the Insight Control for Linux distribution medium, follow the procedures in this chapter to log in to Systems Insight Manager and configure it for use with Insight Control for Linux. When you log in to Systems Insight Manager for the first time, a First Time Wizard is launched, and you will answer basic configuration questions.
For more information about command line options, see the mxuser(1M) manpage. 6.2 Logging in to Systems Insight Manager To log in and launch Systems Insight Manager and Insight Control for Linux, follow these steps: 1. Open a recent version of a supported web browser (Mozilla Firefox and Microsoft Internet Explorer are supported). NOTE: Supported web browser versions are listed in the HP Insight Control for Linux Support Matrix. 2. Enter the following web address.
Figure 3 Systems Insight Manager registration screen NOTE: Be aware that pop-ups might be blocked by some browsers. If pop-ups are blocked, do one of the following: 2. 48 • Close the browser and log in to Systems Insight Manager again after you reset the browser pop-up blocker. • Open the Registration window and the First Time Wizard from the Systems Insight Manager GUI: ◦ Options→Registration... ◦ Options→First Time Wizard...
Figure 4 Systems Insight Manager First Time Wizard Introduction Screen Table 13 Responses to the First Time Wizard First Time Wizard screen Required, not required, or optional User response Introduction Required Click Next. Managed Environment Required At a minimum, select Linux if it is not already preselected for you. You can make other selections as well. GlancePlus is a performance management tool that is not used by Insight Control for Linux, and you are not required to select it. Click Next.
Table 13 Responses to the First Time Wizard (continued) First Time Wizard screen Required, not required, or optional User response Configure Managed Systems Optional Configure managed systems. Privilege Elevation Optional Insight Control for Linux does not support privilege elevation. E-mail Optional Supply an SMTP host name and email address if you want Systems Insight Manager to send event notifications by email. Then, click Next. Summary Required Click Finish, then click Close.
4. Scroll to the bottom of the page, and click OK to apply the settings. 6.5 Discovering the management processor on the CMS (optional) This task is optional, and you can skip this task if the CMS is running in a virtual machine guest. If the CMS has an MP and you want to monitor the CMS with Insight Control for Linux, create a new discovery task to discover its MP: NOTE: Before you begin this procedure, make sure you have configured SNMP on the CMS, as described in Section 3.4.2.2 (page 21). 1.
1. Select the following menu item from the Systems Insight Manager GUI: Deploy→License Manager... 2. 3. 4. 5. 6. 7. Click Add Licenses.... Enter the Insight Control for Linux license key (the license key consists of five sets of five characters). Before continuing to the next step, verify that you typed the license key characters exactly as shown on your license agreement. Click Process.... Click Add Licenses Now.... Click OK. 6.7 Adding an iLO Advanced Pack license key This task is required.
7 Next steps When Systems Insight Manager and Insight Control for Linux are fully installed on the CMS, use the instructions in the HP Insight Control for Linux User Guide to perform the following tasks: 1. Discover your managed systems, switches, and enclosures to make them known to Systems Insight Manager and Insight Control for Linux. 2.
8 Upgrading Insight Control for Linux This chapter describes how to upgrade a previously-installed version of Insight Control for Linux to the latest release of Insight Control for Linux. 8.1 Upgrade overview The Insight Control for Linux install.sh installation script upgrades a CMS that is already running a previous version of Insight Control for Linux to this version of Insight Control for Linux.
# mkdir /mnt # mount –o loop Insight Control for Linux_image_name.iso /mnt NOTE: Use the following mount command if you are mounting a DVD: # mount -r /dev/cdrom /mnt 7. Navigate to the mount point and to the location of the installation script: # cd /mnt/HP 8. Run the Insight Control for Linux installation script to start the upgrade process: # ./install.
The Insight Control for Linux upgrade process saves user customizations to Insight Control for Linux configuration files by renaming the files with a .rpmnew or .rpmsave file extension. The list of .rpmnew or .rpmsave files is stored in the /opt/hp/icelx/logs/install_log file. To retain your customizations to Insight Control for Linux configuration files by manually merging the customizations into the newly delivered version of the file (which might have changed), follow these steps: 1.
9 Troubleshooting This chapter addresses troubleshooting topics for new installations and upgrades. 9.1 New installations 9.1.1 Skipped HP VCRM installation If HP SMH is not installed on your CMS, HP SIM cannot automatically install the Version Control Repository Manager (VCRM) for you.
NOTE: The error messages were displayed on multiple lines for clarity. warning: ../RPMS/nodist/nover/noarch/systemimager-i386boot-standard4.0.2-1.icelx15894.noarch.rpm: Header V3 DSA signature: NOKEY, key ID 2689b887 warning: ../RPMS/suse/sles11/noarch/hp-cms-1-75.noarch.rpm: Header V3 DSA signature: NOKEY, key ID 2689b887 warning: ../RPMS/nodist/nover/i386/hpvmm-6.0.0.1123-1.i386.rpm: Header V3 DSA signature: NOKEY, key ID 2689b887 warning: ../RPMS/nodist/nover/noarch/hpipm-6.0.0-1.noarch.
9.1.9 What to do if you see install.sh authentication errors This section describes what to do if you see the following message generated by the install.sh script: Logging in Proxy = https://172.17.91.6:50001/mxsoap/services/MxpiMain5_2 java.lang.Exception: Authentication failed. ERROR: create_MxpiMainService returned 2304 Error: /opt/hptc/cms/bin/setup_cms returned: 1 Error: post install failure Install error: 10_mgmt_postinstall.
• /var/opt/mx/logs/initconfig.log 9.1.11 Apache service does not start if you did not create a self-signed certificate The Apache service does not start if you did not create a self-signed Apache certificate. • SLES: Look in the /var/log/apache2/error_log log file for service errors. You might see an error similar to this: Init: Unable to read server certificate from file /etc/apache2/ssl.crt/server.crt • RHEL Version 4: Look in the /var/log/httpd/error_log log file for service errors.
error: Failed dependencies: ksh is needed by sys_check-x-y.arch date and time stamp: 10_mgmt_install.sh An error occurred during the RPM installation. 9.1.15 HP SIM might not start on SLES11 CMS during installation The installation of Insight Control for Linux on a CMS running SLES 11 sometimes fails with the following HP SIM startup error because HP SIM startup delays are affecting the installation: ... HP Systems Insight Manager Initialization Starts at: Monday, datestamp ...........
# su hpsmdb 2. Start the postmaster command: # /opt/hpsmdb/bin/postmaster –D /var/opt/hpsmdb/data & NOTE: 3. This command must run in the background. Return to the root shell: # exit 4. When the root prompt returns, stop the hpsmdb service if it is already running: # /etc/init.d/hpsmdb stop 5. Start the hpsmdb service. # /etc/init.d/hpsmdb start 6. Restart HP SIM: # mxstart 7. Rerun the Insight Control for Linux installation script with the --upgrade option: # install.
10 Support and other resources 10.1 Information to collect before contacting HP 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) 10.2 How to contact HP Use the following methods to contact HP technical support: • See the Contact HP worldwide website: http://www.hp.
10.3.2 Warranty information HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty applies to all Insight Management products. 10.4 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 website: http://www.hp.com/service_locator • In other locations, see the Contact HP worldwide website: http://www.hp.com/go/assistance 10.
Download from the Insight Control Information Library website For your convenience, the documentation set for this release of Insight Control for Linux is available from the Insight Control Information Library website. To view or download the documentation from this website, follow these steps: 1. Open a web browser to the following web address: http://www.hp.com/go/insightcontrol/docs 2. 3. Locate the Product Documentation section. Click the Insight Control for Linux tab.
10.7.2 Websites • HP ProLiant Support Pack To find and download the HP ProLiant Support Pack (PSP) that is appropriate for your ProLiant server and Linux OS, follow these steps: 1. Open a browser to the HP Support Center website: http://www.hp.com/go/hpsc 2. 3. 4. Select the Support & Drivers tab near the top of the page. Select Drivers & Software. Enter your server model (for example, DL360 G7) in the Enter a product name/number text box, then click Search.
• Third-party open source software products The following are useful links to third-party open source software products that were integrated into Insight Control for Linux. The location of each website or link to a particular topic is subject to change without notice by the site provider. ◦ http://www.nagios.org Home page for Nagios, a system and network monitoring application that provides monitoring capabilities for Insight Control for Linux.
ENVIRONMENT VARIABLE The name of an environment variable, for example, PATH. Key The name of a keyboard key. Return and Enter both refer to the same key. Term A term or phrase that is defined in the body text of the document, not in a glossary. User input Indicates commands and text that you type exactly as shown. Replaceable The name of a placeholder that you replace with an actual value. [] In command syntax statements, these characters enclose optional content.
A Alternative network configurations This appendix provides optional, alternative network configurations that are supported for use with Insight Control for Linux in addition to the network configurations described in Chapter 4 (page 27).
Figure 7 Microsoft DHCP graphical utility: set predefined options 3. 70 A dialog box displays all standard DHCP options. Select Add to add a new option.
Figure 8 Microsoft DHCP graphical utility: Add options 4. In the Option Type dialog box, enter the values shown in Figure 9. You must set the Data type field to Binary. A.
Figure 9 Microsoft DHCP graphical utility: Option type dialog box 5. 72 Select OK and then select OK again. You have successfully added the System Imager option 140 to the DHCP Snap-in.
Figure 10 Microsoft DHCP graphical utility: Successful addition of option 140 Next, follow this procedure to configure the Scope Options: 1. Expand the server, right-click on Scope Options, and select Configure Options... 2. In the Scope Options dialog box, scroll to and select the 066 Boot Server Host Name option. As shown in Figure 11, enter the IP address of the management NIC of the CMS in the String value: field. A.
Figure 11 Microsoft DHCP graphical utility: Scope options dialog box (boot server host) 3. 74 Also in the Scope Options dialog box, select the 067 Bootfile Name option. As shown in Figure 12, enter pxelinux.bin in the String value: field.
Figure 12 Microsoft DHCP Graphical utility: Scope options dialog box (Bootfile name) 4. In the same Scope Options dialog box, scroll down and select option 140 System Imager to configure it for your scope. Click in the dialog box underneath the ASCII column. Press the Backspace key to remove the extraneous period (.) in that column. A.
Figure 13 Microsoft DHCP Graphical utility: Scope options dialog box 5. 76 Enter the IP address of the management NIC of the CMS under the ASCII column. As you type, the Binary and Data columns are automatically filled out for you. When you are done, select OK.
Figure 14 Microsoft DHCP graphical utility: Scope options dialog box (2) Your Microsoft DHCP server is now configured to provide the options required for Insight Control for Linux. A.3 Configuring a static IP Address using DNSMASQ Example 11 demonstrates how to configure two hosts with static IP addresses. You must assign IP addresses that are outside of the pool of addresses configured in the range option.
# Static Address Assignment #dhcp-host=11:22:33:44:55:66,mercury,192.168.0.60,45m dhcp-host=aa:bb:cc:dd:ee:ff,mystatichost,172.1.1.201,24h dhcp-host=00:11:12:13:14:15,myotherhost,172.1.1.202,24h A.4 Configuring a static IP address using ISC DHCP Example 12 provides an example of how to configure two hosts with static addresses. You must assign IP addresses that are outside of the pool of addresses configured in the range option.
Figure 15 Multiple network architecture In this configuration, static routes must be added to the (and to the external DHCP, if used) to set the gateway to the remote subnets. If the same router that provides connectivity to the remote subnets also provides connectivity to the larger public network, a simple default gateway may suffice. It is just required that the CMS have the ability to reach the remote network.
# log-servers option log-servers 172.1.1.1; subnet 172.1.1.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; range dynamic-bootp 172.1.1.100 172.1.1.200; default-lease-time 50000; max-lease-time 100000; } subnet 172.1.2.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; option routers 172.1.2.254; range dynamic-bootp 172.1.2.100 172.1.2.200; default-lease-time 50000; max-lease-time 100000; } subnet 172.1.3.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; option routers 172.1.3.
B Sample output from a new Insight Control for Linux installation Example 15 provides a sample of the output you can expect to see after you respond to the Insight Control for Linux install.sh installation script configuration questions. Example 15 Sample Insight Control for Linux installation # ./install.sh This will install HP Insight Control for Linux (IC-Linux) including HP Systems Insight Manager (SIM).
vacuuming database template1 ... ok copying template1 to template0 ... ok copying template1 to postgres ... ok WARNING: enabling "trust" authentication for local connections You can change this by editing pg_hba.conf or using the -A option the next time you run initdb. Success. You can now start the database server using: /opt/hpsmdb/bin/postgres -D /var/opt/hpsmdb/data or /opt/hpsmdb/bin/pg_ctl -D /var/opt/hpsmdb/data -l logfile start The directory '/var/opt/hpsmdb/data' exists but is not empty.
9. Database Content ..Done 10. Web Server ..Done 11. Setup Property File ..Done 12. JBoss Setup ..Done 13. Agent Configuration ..Done 14. Management Services ..Done 15. Initialization and Database Population .... ............Completed all tasks successfully. Details can be found in the log files at: /var/opt/mx/logs HP Systems Insight Manager initialization completed successfully. * Stopping HPSIM...done * Registering IC-Linux Deploy database tables...done * Initializing the IC-Linux Deploy repository...
5.INFO : Loading PLP details into LM system : /etc/opt/mx/config/preload-plugins/60/ILO/addfiles/plp-1-1.xml 6.INFO : ** PlpKeeper.parseXml- plp-1-1.xml, completed! 7.INFO : 8.INFO : Loading PLP details into LM system : /etc/opt/mx/config/preload-plugins/60/ILO/addfiles/plp-29-1.xml 9.INFO : ** PlpKeeper.parseXml- plp-29-1.xml, completed! 10.INFO : 11.INFO : Loading PLP details into LM system : /etc/opt/mx/config/preload-plugins/60/ILO/addfiles/plp-24-1.xml 12.INFO : ** PlpKeeper.parseXml- plp-24-1.
C Sample output from an Insight Control for Linux upgrade Example 16 provides a sample of the output you can expect to see during a successful upgrade to the new release of Insight Control for Linux. Example 16 Sample Insight Control for Linux upgrade # ./install.sh This will install HP Insight Control for Linux (IC-Linux) including HP Systems Insight Manager (SIM). IC-Linux Version n.n was found on this system. Would you like to upgrade from this version to 7.0.
HP Systems Insight Manager installed successfully. * * * * * * * * * * Stopping HPSIM...done Registering IC-Linux Deploy database tables...done Initializing the IC-Linux Deploy repository...done Starting HP SIM... Please be patient - it may take a while for HP Systems Insight Manager to start. If HP Systems Insight Manager does not start within 15 minutes, the install.sh script stops the installation process and exits. HP SIM started Updating IC-Linux Deploy tools in HPSIM...
Glossary A AutoYaST file A configuration file used to effect an unattended installation of SLES operating systems. B bare-metal Describes a server that is not currently booted with a running operating system. This could be a brand new server with no OS installed on it, or it could be a server with an OS that is not booted. C central management server See CMS. certificate An electronic document that contains a subject's public key and identifying information about the subject.
I iLO Integrated Lights Out. A self-contained hardware technology available on various hardware models that enables remote management of any node within a system. Subsequent generations of this technology are iLO 2 and iLO3. For information on which servers offer iLO MPs, see the HP Insight Control for Linux Support Matrix. Integrated Lights Out See iLO. Internet address A unique 32-bit number that identifies a host's connection to an Internet network.
PXE Preboot Execution Environment. A standard client/server interface that enables networked computers that are not yet installed with an operating system to be configured and booted remotely. PXE booting is configured at the BIOS level. R RAM disk A portion of RAM memory treated as a disk drive. remote repository A remote file system mounted on a CMS, that contains the repository contents.
Index bare metal defined, 6 best practice DHCP, 31 booting managed system, 27 documentation ESX, 67 ESXi, 67 HP Insight Control, 65 Insight Control for Linux, 64 KVM, 67 Linux, 66 Nagios, 67 pdsh, 67 ProLiant servers, 65 providing feedback, 64 PSP User Guide, 66 reporting errors in, 64 RRDtool, 67 Supermon, 67 syslog-ng, 67 Systems Insight Manager, 65 Xen, 67 C E CMF, 9 CMS, 6 configuration requirements, 14, 21 installation requirements, 14 installing PSP, 20 management interface defined, 38 open inbou
hp-health RPM, 21 hp-ilo RPM, 21 hp-snmp-agent RPM, 21 /hptc_cluster file system , 26 /hptc_cluster file system exporting to management hubs, 39 HTTP/HTTPS, 27 I iLO Advanced Pack adding license key, 51 retrieving license key, 10 image deployment large environments, 9 Insight Control for Linux adding license key, 51 documentation, 64 launching, 47 starting, 47 white papers, 64 Insight Control for Linux installation checklist, 11 CMS requirements, 14 DHCP requirements, 30 preinstallation tasks, 12 preparing
network port opening inbound on the CMS, 22 network services configuring, 34 network topology, 28 networking protocols, 27 O /opt/repository, 25 Oracle database configuring, 38 P parallel distributed command see pdsh password for administrator users, 46 root, 39 pdsh, 9 documentation, 67 performance dashboard utility, 6 port opening inbound on the CMS, 22 postinstallation failure, 59 postinstallation phase error, 58 power consumption monitoring, 7 power control remote, 7 power management, 7 product licens
monitoring, 7 troubleshooting, 57 typographic conventions, 67 U upgrade install.
