HP Insight Control for Linux V6.
© Copyright 2008, 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents 1 Product overview.............................................................................................................7 1.1 Product description...........................................................................................................................7 1.2 Insight Control for Linux tools and features.....................................................................................7 1.3 Licensing.....................................................................
.4 Other network services....................................................................................................................36 4.4.1 ATFTP/ TFTP configuration....................................................................................................36 4.4.2 rsync configuration.................................................................................................................37 4.4.3 SNMP configuration....................................................................
9.2.1 Linux OS RPM dependencies are missing on SLES 11 CMS..................................................66 10 Support and other resources.....................................................................................67 10.1 Contacting HP...............................................................................................................................67 10.1.1 Information to collect before contacting HP.........................................................................67 10.1.
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 HP Systems Insight Manager (Systems Insight Manager).
— — — — 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 uses RRDtool with Nagios to provide a graphical view of system status.
• Remote installation of Linux OSs to managed systems Insight Control for Linux enables you to launch the following types of remote network installations to install a Linux OS on one or more managed systems: — — — — Interactive or unattended installations of RHEL. Unattended installations of RHEL are run with user-customized Kickstart configuration files that have been registered in the repository. Interactive or unattended installations of SLES.
you to manually enter the network information for each server through the Options→IC-LinuxNetwork Configuration Editor on the CMS. See the HP Insight Control for Linux User Guide for information about configuring and using virtual media. • ProLiant Support Pack (PSP) installation Insight Control for Linux enables you to download and copy PSPs to the Insight Control for Linux repository and deploy the PSPs to managed systems.
At the appropriate point in this document, you will follow a procedure to add the trial license key to Systems Insight Manager, which enables you to use Insight Control for Linux and its integrated HP products. After the evaluation period expires, you must purchase additional Insight Control for Linux licenses from HP if you want to continue using the product. 1.3.
2 Installation and configuration checklist The checklist shown in Table 2-1 provides a summary of the steps that are required to install and configure Insight Control for Linux. Table 2-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.
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 3-1 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.
IMPORTANT: HP recommends that you install a new instance of a Linux OS on the CMS because Systems Insight Manager and Insight Control for Linux have requirements on certain RPM Package Manager (RPM) software packages. To get the best experience with Insight Control for Linux, HP recommends that you include the required RPMs during a new installation. Required RPMs are listed in Section 3.4.1.2 (page 18).
Table 3-3 RHEL version 4 RPM requirements RPM requirements common to all RHEL RPM requirements specific to RHEL 4 4 X64 RPM requirements specific to RHEL 4 i386 apr apr-util compat-libstdc++-296-2.
Table 3-4 RHEL version 5 RPM requirements 20 RPM requirements common to all RHEL RPM requirements specific to RHEL 5 5 X64 RPM requirements specific to RHEL 5 i386 apr apr-util dhcp distcache e2fsprogs-devel freetype freetype2 glib httpd keyutils-libs-devel krb5-devel krb5-devel 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
Table 3-5 SLES version 10 RPM requirements RPM requirements common to all SLES RPM requirements specific to SLES 10 10 X64 RPM requirements specific to SLES 10 i386 apache2 apache2-mod_php5 apache2-prefork atftp1 compat-libstdc++ dhcp-server freetype gd glib gnuplot krb5 libapr1 libapr-util1 libart_lgpl lsb mm net-snmp openssh openssl-devel perl-HTML-Parser perl-HTML-Tagset perl-libwww-perl php5 php5-timezonedb plotutils sensors zlib audit-libs compat cracklib db libstdc++332 libxcrypt pam pam-modules zl
Table 3-6 SLES version 11 RPM requirements RPM requirements common to all SLES RPM requirements specific to SLES 11 11 X64 RPM requirements specific to SLES 11 i386 apache2 apache2-mod_php5 apache2-prefork atftp 1 dhcp-server freetype gd genisoimage libmm14 libsensors4 lsb gnuplot krb5 libapr1 libapr-util1 libart_lgpl net-snmp openssh perl-HTML-Parser perl-HTML-Tagset perl-libwww-perl php5 plotutils sensors zlib audit-libs cracklib compat compat-libstdc++-296-2.
release. A PSP contains essential operating specific optimized drivers, utilities, and management agents that are required for ProLiant hardware platforms. NOTE: You can skip the PSP installation step in the following circumstances: • When the CMS is an HP ProLiant 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.
3.4.2.2 Configure SNMP When the CMS is an HP ProLiant server with an Integrated Lights Out (iLO or iLO2) management processor, Section 3.4.1.5 (page 22) instructed you to install the PSP on it. Now, enter the following command to configure SNMP on the CMS: NOTE: Do not configure SNMP if the CMS is a Xen virtual guest. # /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.
Table 3-7 Network ports on the CMS that must be open to inbound traffic Port number Service Protocol 22 ssh TCP 69 tftp UDP 161 SNMP TCP/UDP 162 SNMP trap listener UDP 214 syslog-ng TCP 280 Systems Insight Manager web server TCP 443 https TCP/UDP 514 syslog-ng UDP 873 rsync TCP 2301 and 2381 HP System Management home page TCP 2709 mond TCP 2710 supermon TCP 5666 nrpe TCP 56671 nsca TCP 6500 cmfd TCP 50000 Systems Insight Manager secure web server TCP 50001
NOTE: The port numbers used in the procedure are intended as examples; you can elect to use different values than are used in the procedures. NOTE: See Table 5-1 (page 40) if you want to learn more about exporting the /hptc_cluster file system and management hubs. If your company policy prevents you from using NFS, you can manually export the /hptc_cluster file system using a different mechanism. Procedure 3-1 Opening ports on RHEL OSs 1.
# # Only set this if you want to start mountd on a fixed # port instead of the port assigned by rpc. Only for use # to export nfs-filesystems through firewalls. # MOUNTD_PORT="33777" . . . 2. 3. Save your changes and exit the text editor. Use a text editor to modify the /etc/services file to lock down the quota daemon: rquotad rquotad 4. 5. Save your changes and exit the text editor. Set the lockd lock manager port and start NFS: # # # # 6. 14900/udp 14900/tcp /etc/init.
3.4.2.8 Ensure at least 12 GB of disk space is available for the /hptc_cluster file system The /hptc_cluster directory on the CMS is required by the Insight Control for Linux monitoring software, and it is automatically created when you install Insight Control for Linux. This directory can grow very large with various log files, and in some cases, /hptc_cluster consumes the / (root) file system.
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 39) 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 3-7 (page 25) 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 31) “Flat single network topology” (page 31) 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.
deny duplicates; # 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.
This server only responds to systems whose MAC address appears in this dhcpd.confconfiguration file. Each entry in this sample /etc/dhcpd.conf configuration file has three pieces of data: • • • MAC address of the NIC 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 4-2, the settings required by Insight Control for Linux are shown in bold font.
fixed-address 192.0.2.27; option host-name "server001-cp"; } # 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 This host name must agree with the DNS look up name or the host name entry if it exists in the /etc/hosts file. If this server is the CMS, this value must match the output of the hostname --fqdn command. -cp means this is the "console port".
192.0.2.21 192.0.2.22 server001-cp server002-cp 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 36) “rsync configuration” (page 37) “SNMP configuration” (page 37) 4.4.
Example 4-5 /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 proce ss for some operating systems. service tftp { disable = no socket_type = dgram protocol = udp wait = yes user = root server = /usr/sbin/in.
• 38 requests from that location. Not including an IP address or system name accepts requests from any system. trapsink sets the destination for any traps the system generates. This value must be the IP address or the name of the CMS.
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 59). 5.
Table 5-1 Insight Control for Linux installation questions Question Description and user action Oracle or default database You have the option to use a pre-existing instance of a supported version of an Oracle database if you want to override the default Systems Insight Manager database.
Table 5-1 Insight Control for Linux installation questions (continued) Question Description and user action Default management processor user credentials Supply the user name and password that Insight Control for Linux will use to access and manage the MP on the servers that it will manage. The default setting on an iLO management processor accepts passwords equal to or greater than eight characters in length.
Table 5-1 Insight Control for Linux installation questions (continued) Question Description and user action Systems Insight Manager user You must enter root as the Systems Insight Manager user name. This root user is name and password the same as the root user on the Linux system. This user name and its password are used to import an SSL certificate into the Systems Insight Manager trusted certificate pool.
NOTE: See Chapter 4 (page 29) for more information about configuring DHCP for use with Insight Control for Linux. Table 5-2 DHCP server configuration questions Item Description IP network to assign DHCP addresses The subnet identifier to use in the DHCP configuration. For example, if you have a class-C network, identified as 192.0.2.0/24, enter 192.0.2.0. IP network netmask to assign DHCP address The netmask used to identify the network and host components of an IP address.
# rpm -q gpg-pubkey Where gpg-pubkey is the public key. Alternatively, you can use the rpm -qi command to show more details about the certificates. Installing the public key To install the public key from an Insight Control for Linux ISO image, follow these steps: 1. 2. Log in to the CMS with the superuser account (root). Create a temporary mount point: # mkdir /mnt/dirname 3. Mount the ISO image for HP Insight Control for Linux: # mount -o loop IC-LX_release.iso /mnt/dirname Where IC-LX_release.
This creates a temporary directory for the Systems Insight Manager RPMs (for example, makeself-32350-20091024210345). Use the rpm -–checksig command to verify the HP signature of the RPMs. 5.4 Running the Insight Control for Linux install.sh installation script This section describes how to install Systems Insight Manager and Insight Control for Linux on the server you have prepared to be the CMS.
Gathering configuration data... For more information about how to answer a configuration question, enter a question mark(?). Press enter to continue. Enter Would you like to use an existing Oracle database as the HP SIM database? (y/n) [n] 1 Device IP ------- ----------------------eth0 192.0.2.
5.5 Synchronizing the insight management MIB update kit and PSP versions (optional) This task is optional. The Insight Management MIB (Management Information Block) update kit for Systems Insight Manager for Linux contains all the necessary MIB files to update Systems Insight Manager or any other MIB tool to have the current support for ProLiant servers. TIP: A best practice is to keep the MIB and PSP versions synchronized for all components and tools that use them.
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 6-1 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: • 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... 2.
Figure 6-2 Systems Insight Manager First Time Wizard Introduction Screen Table 6-1 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.
Table 6-1 Responses to the First Time Wizard (continued) First Time Wizard screen Required, not required, or optional User response Privilege Elevation Optional Some tools in Systems Insight Manager are defined to run as root on Linux and VMware ESX managed systems. However, root logins are not allowed in many customer environments. Instead, administrators might be required to use an individual login that is authorized to acquire root permissions as needed (for example, using su or sudo).
Figure 6-3 General Settings For All Discoveries 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.
Figure 6-4 Discovering the CMS MP 3. 4. 5. 6. 7. 8. Under New Discovery, select Discover a single system. Enter a unique name for the new discovery task, perhaps Discover CMS MP. You are free to choose any name for this task. Unselect the box next to Schedule; you do not want to schedule this task. Enter the IP Address of the CMS management processor. Click Save. Click Run Now... to start the discovery task.
4. 5. 6. 7. 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. The Integrated Lights Out (iLO) Advanced license key activates iLO Advanced features. The license key activation instructions assume the network client has a network connection to the iLO or to the iLO 2 management processor.
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. 2. 3. 4. 5. Discover your managed systems, switches, and enclosures to make them known to Systems Insight Manager and Insight Control for Linux.
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.
NOTE: Use the following mount command if you are mounting a DVD: # mount -r /dev/cdrom /mnt 6. Navigate to the mount point and to the location of the installation script: # cd /mnt/HP 7. Run the Insight Control for Linux installation script to start the upgrade process: # ./install.sh This will install HP Insight Control for Linux (Insight Control for Linux) including HP Systems Insight Manager (Systems Insight Manager) NOTE: Default responses to all questions are enclosed in square brackets ([ ]).
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.
HP Graph graphs only the metric data since the time the upgrade procedure completed. Therefore, you must follow the procedure in this section to convert the old archive to the new format if you want to display and graph data before the upgrade. The migrate_rrds utility converts the old archive files in the /hptc_cluster/ rrd.preupgrade directory and stores the newly converted archive files in a new /hptc_cluster/rrd.upgrade directory.
9 Troubleshooting This chapter addresses troubleshooting topics for new installations and upgrades. 9.1 New installations 9.1.1 Benign insserv messages when running install.sh script on a SLES 11 CMS The following insserv messages are displayed by the install.sh script on a CMS that is running SLES 11. These messages are benign and you can ignore them.
9.1.5 Installation hangs if *_proxy environment variables are defined The installation process will hang at "Starting Systems Insight Manager" when the wget command determines when Systems Insight Manager has finished loading. The hang occurs if a *_proxy environmental variable is defined (for example, http_proxy) because wget tries to use the defined proxy to access the local host. Corrective action: Unset the proxy environment variables before running the install.sh script.
Example 9-1 and Example 9-2 show examples of correct and incorrect /etc/hosts file contents, respectively. Example 9-1 Correct /etc/hosts file content # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 192.0.2.1 earth.example.
9.1.11 Reinitializing Systems Insight Manager requires you to reinstall Insight Control for Linux If you reinitialize Systems Insight Manager by running the mxinitconfig –r command, and then run the mxinitconfig –a command, you must reinstall Insight Control for Linux. Corrective action: Use the installation procedure in to re-run the install.sh installation script and reinstall Insight Control for Linux. It is not necessary to uninstall Insight Control for Linux first. 9.1.
10 Support and other resources 10.1 Contacting HP 10.1.1 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) 10.1.
10.1.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 at: http://www.hp.com/service_locator • In other locations, see the Contact HP worldwide website at: http://welcome.hp.com/country/us/en/wwcontact.html 10.1.5 Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to: docsfeedback@hp.
— HP Insight Control for Linux User Guide Describes how to set up and use Insight Control for Linux to discover, monitor, and manage HP ProLiant servers that have been licensed for Insight Control for Linux. The Insight Control for Linux product website contains links to the Insight Control for Linux Documentation Set and white papers, a link to the HP Insight Control for Linux QuickSpecs, license information, product registration information, and many other related topics.
NOTE: If more than one server model matches the value you entered in the For product text box, select the appropriate server model from the search results. 5. 6. 7. 8. Select the appropriate Linux OS and version from the list of available operating systems. Scroll down the page until you see the table labeled Software - Support Pack. Select the PSP link in the Description column. To download the PSP, select the Download>> button associated with the *.tar.gz (gzipped) file.
• http://supermon.sourceforge.net Home page for Supermon, a high-speed cluster monitoring system that emphasizes low perturbation, high sampling rates, and an extensible data protocol and programming interface. Supermon works in conjunction with Nagios to provide system monitoring data. • https://computing.llnl.gov/linux/pdsh.html Home page for the parallel distributed shell (pdsh), which executes commands across managed systems in parallel. • http://www.balabit.
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 29).
1. 2. To add Option 140 to Microsoft DHCP, start by opening the DHCP Snap-In tool. Right-click on your server entry, and select the Set Predefined Options... menu item. Figure A-1 Microsoft DHCP graphical utility: set predefined options 3. 74 A dialog box displays all standard DHCP options. Select Add to add a new option.
Figure A-2 Microsoft DHCP graphical utility: Add options 4. In the Option Type dialog box, enter the values shown in Figure A-3. You must set the Data type field to Binary. A.
Figure A-3 Microsoft DHCP graphical utility: Option type dialog box 5. 76 Select OK and then select OK again. You have successfully added the System Imager option 140 to the DHCP Snap-in.
Figure A-4 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 A-5, enter the IP address of the management NIC of the CMS in the String value: field. A.
Figure A-5 Microsoft DHCP graphical utility: Scope options dialog box (boot server host) 3. 78 Also in the Scope Options dialog box, select the 067 Bootfile Name option. As shown in Figure A-6, enter pxelinux.bin in the String value: field.
Figure A-6 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 A-7 Microsoft DHCP Graphical utility: Scope options dialog box 5. 80 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 A-8 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 A-2 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 A-3 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 A-9 Multiple network architecture In this configuration, static routes must be added to the CMS (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 B-1 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 B-1 Sample Insight Control for Linux installation Installing IC-Linux ... Installing HP Systems Insight Manager ... Verifying archive integrity... All good. Uncompressing Hewlett-Packard Development Company, L.P. HP Systems Insight Manager C.06.00.00.00.r60qa21....
11. Setup Property File ..OK Status : Unconfigured 12. JBoss Setup ..OK Status : Unconfigured 13. Agent Configuration ..OK Status : Unconfigured 14. Management Services ..OK Status : Unconfigured 15. Initialization and Database Population ..OK Status : Unconfigured Completed all tasks successfully. Details can be found in the log files at: /var/opt/mx/logs Checking Requisites (15): 1. Check Kernel Parameters ..OK 2. Node Security File ..OK 3. Server Property File ..OK 4. Server Authentication Keys ..OK 5.
Settings: Configuration file: Temporary file: Private key file: Certificate file: Perl module: /opt/hptc/database/etc/ssl/openssl_config /opt/hptc/database/etc/ssl/tmp_keyfile.pem /opt/hptc/database/etc/ssl/keyfile.pem /opt/hptc/database/etc/ssl/certfile.pem /opt/hptc/database/lib/sim/MxpiMainService.pm Creating certificate Generating a 1024 bit RSA private key ..............++++++ .............................................++++++ writing new private key to '/opt/hptc/database/etc/ssl/tmp_keyfile.
/etc/opt/mx/config/preload-plugins/60/vmm/addfiles/plp-14-1.xml 21.INFO : *** LmPlpKeeper.parseXml.registerForAssignWARNING: plp-14-1.xml specifies non-existent tool "VMM Licensing" (i.e. no filtering tool) *** 22.INFO : ** PlpKeeper.parseXml- plp-14-1.xml, completed! 23.INFO : 24.INFO : Loading PLP details into LM system : /etc/opt/mx/config/preload-plugins/60/icelinux/addfiles/plp-50-1.xml 25.INFO : ** PlpKeeper.parseXml- plp-50-1.xml, completed! 26.
C Sample output from an Insight Control for Linux upgrade Example C-1 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 C-1 Sample Insight Control for Linux upgrade [root]# ./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 n.
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 ok HP Systems Insight Manager installed successfully. Set new product name and title - wait up to 5 minutes for SIM to be ready ... New product name and title cannot be set - SIM not ready * Stopping HPSIM...done * Registering IC-Linux Deploy database tables...done * Initializing the IC-Linux Deploy repository.
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 management processors, 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.
contains driver components, agent components, and application and utility components. All these are verified to install together. PSP dependency script An optional user-provided script that runs during a PSP deployment to a managed system. 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.
Index Symbols 06_vmm_dependency.
I iLO Advanced Pack adding license key, 55 retrieving license key, 10 image deployment large environments, 9 Insight Control for Linux adding license key, 55 documentation, 68 launching, 50 starting, 50 white papers, 68 Insight Control for Linux installation checklist, 13 CMS requirements, 17 DHCP requirements, 32 preinstallation tasks, 15 preparing for installation questions, 39 RPM dependencies, 18 insserve messages during installation, 63 install.
P parallel distributed command (see pdsh) password for administrator users, 49 root, 42 pdsh, 10 documentation, 71 performance dashboard utility, 7 port opening inbound on the CMS, 24 postinstallation failure, 64 postinstallation phase error, 63 power consumption monitoring, 8 power control remote, 8 power management, 8 product license iLO Advanced Pack, 10 Insight Control for Linux, 10 product overview, 7 ProLiant servers documentation, 69 ProLiant Support Pack (see PSP) _proxy environment variable, 64 PSP
running, 59 to next release, 59 troubleshooting, 66 user account Linux, 49 Nagios/Apache web, 49 Systems Insight Manager, 49 user name CMS, 42 V virtual machine, 8 virtual machine guest running CMS in, 8 virtual media, 9, 29 virtualization, 8 W websites HP authorized resellers, 68 HP technical support, 67 Linux vendors, 70 MIB, 47 ProLiant servers, 69 ProLiant Support Pack, 69 PSP, 17 white papers for enabling SElinux, 22 Insight Control for Linux, 68 98 Index
