HP Insight Control for Linux V6.
© Copyright 2009, 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 Overview and description.............................................................................................7 1.1 Insight Control for Linux overview..................................................................................................7 1.2 Release overview...............................................................................................................................7 1.2.1 How to obtain the ISO image.....................................................
2.6 Management and monitoring notes................................................................................................16 2.6.1 Metrics for HP ProLiant DL100 series servers might not be individually reported...............16 2.6.2 Configure Insight Control for Linux management services or install agents might fail .......17 2.6.3 Configure or Repair Agents failure for managed systems running Red Hat 4.8...................17 2.6.
3.3.7 Correction to Chapter 17, Remote server controls..................................................................30 3.3.8 Addition to Chapter 21, Miscellaneous tasks..........................................................................30 3.3.9 Correction to Chapter 22, Advanced topics............................................................................31 3.3.10 Additions to Chapter 23, Troubleshooting............................................................................31 3.3.
1 Overview and description 1.1 Insight Control for Linux overview 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 (SIM).
See the HP Insight Control for Linux Support Matrix for the full list of supported hardware platforms. 1.3.3 Support for new operating systems • Support for the following operating systems: — Red Hat Enterprise Linux 4 Update 8 — Red Hat Enterprise Linux 5 Update 4 — SUSE Enterprise Linux 10 SP3 • Support for the following virtualization operating systems: — VMware ESX (3.03, 3.5, 3.5 U4, 3.5 U5, 4.0, and 4.0 U1) — VMware ESXi (3.5, 3.5 U4, 3.5 U5, 4.0, and 4.
1.3.7.2 New Define networks and Network Configuration Editor tools By defining a network with the Define Networks tool, you specify the common network parameters, such as net mask, gateway, and so on, under a common name, called a “network”. Later, you apply a network name to a server instead of entering all the network configuration, thus saving time and effort.
1.3.12 Insight Control virtual machine management New features were added to HP Insight Control virtual machine management Version 6.0. For more information, see the HP Insight Control Release Notes located at the following web address: www.hp.com/go/insightcontrol/docs 1.4 Deprecated features of Insight Control for Linux The following operating systems are no longer officially supported on the CMS. However, Insight Control for Linux OS installation tools still support them on managed systems.
1.8 Security bulletin and alert policy for non-HP owned software components Open source software (such as OpenSSL) or third-party software (such as Java) are sometimes included in HP products. HP discloses that the non-HP owned software components listed in the Insight Control for Linux end user license agreement (EULA) are included with Insight Control for Linux.
2 Notes and corrective actions 2.1 General operation 2.1.1 SSH delays on SLES managed systems on networks without name resolution You might encounter extended delays when trying to use SSH to access a SLES managed system on a network that does not have DNS name resolution configured or does not have a well populated /etc/hosts file. Such a configuration might exist if your managed nodes are on an internal private network, which is typical for many high performance computing applications.
2.2.1 Bare metal discovery fails on ProLiant DL100 G5 series servers with BMC firmware <3.11 NOTE: This release note applies only to DL100 G5 series servers with baseboard management controller (BMC) firmware earlier than version 3.11. DL100 G5 series servers with BMC firmware 3.11 and later do not exhibit this behavior. Older versions of the baseboard management controller (BMC) firmware (versions than Version 3.
2.2.2 Maintaining the association between the BMC and ProLiant DL100 G5 series server in SIM (BMC firmware <3.11) NOTE: This release note applies only to DL100 G5 series servers with BMC firmware earlier than version 3.11. DL100 G5 series servers with BMC firmware 3.11 and later do not exhibit this behavior.
option gpxe.priority 1; See the following website for more information: http://etherboot.org 2.4.2 Bare metal discovery complains there is no DOS partition on the disk During a bare-metal discovery on a new system with new disks, when the RAM disk loaded onto the system, it reported that there was no valid DOS partition on the disk and subsequently failed to complete the discovery process. Corrective action: Remove the disk or disks temporarily and rerun the bare-metal discovery, then replace the disks.
2.6.2 Configure Insight Control for Linux management services or install agents might fail An intermittent SIM SSH delay by Configure→Configure or Repair Agents might cause Options→Configure Insight Control for Linux Management Services and Deploy→Deploy Drivers, Firmware and Agents→Insight Control for Linux Management→Install Agents... to fail. Corrective action: 1. 2. Select Tasks & Logs→View Task Results...
2.6.6 Nagios nrpe daemon might fail to start on the CMS The nrpe daemon might fail to start on the CMS. Every time you run Options→Configure Insight Control for Linux Management Services, verify that the nrpe daemon is running on the CMS: # ps auxww | grep nrpe If nrpe is not running, enter the following command to start it: # /etc/init.d/nagios start_nrpe 2.6.
Corrective action: Follow this procedure on your CMS to move the RRD directory aside and rerun the Configure Management Services task, which re-creates the /hptc_cluster/rrd directory and reconfigures the Insight Control for Linux management services: 1. Move the /hptc_cluster/rrd directory to another file name: # mv -Rf /hptc_cluster/rrd /hptc_cluster/rrd-save You may choose to delete this directory instead. 2.
the mdadm and mcleog commands are missing from the /etc/sudoers file on the CMS. As a result, these commands are not executed properly. Corrective action: Edit /etc/sudoers on the CMS: • • Add the mdadm and mcleog commands as shown in the first two lines of the example. Add MDADM and MCELOG to the end of the nagios ALL entry as shown in this example.
2.8.1 Manage repository: Updating the kernel name and RAM disk name for a custom OS When you select Options→Manage Repository... and edit a custom OS, the Kernel name and RAM disk name fields display the values you entered when you added the custom OS. If you want to edit either of these values, you must: 1. 2. Edit the /opt/repository/.icle/nameBoot.xml file, where name is the name of the custom OS. Change the values contained in the Kernel or Ramdisk elements. 2.8.
2.11.1.1 SLES 11 image deployment fails with GRUB error In some situations, a SLES 11 image deployment will complete, but the node does not boot. A GRUB error similar to the following appears on the console: GRUB Loading stage1.5. GRUB loading, please wait.. Error 21 In most cases, the deployment failure is actually a capture failure and requires a new image to be captured. Corrective action: Before capturing the image, examine the /etc/fstab and /boot/grub/ menu.
Corrective action: HP suggests that you do not create the swap partition in an LVM volume, and that you do not use the Partition Wizard for creating or renaming the swap partition. 2.12 Console management note 2.12.1 The CMF console command not working due to expired SSL certificate The /etc/init.d/cmfd script creates the SSL certificates that are used when the console or cmfmgr command want to communicate with cmfd. The certificate files are: /opt/hptc/cmf/certs/cert.pem and /opt/hptc/cmf/.key/ privkey.
a. Run the following command to display the status of the currently active interfaces: # ifconfig | more . . . vmnicA Link encap:Ethernet . . . vmnicB Link encap:Ethernet . . . b. 6. HWaddr MAC_ADDRESS HWaddr MAC_ADDRESS_BOOT Locate the MAC address that matches the MAC address of boot NIC (from step 4). In this example, the interface name that is assigned to the boot NIC is vmnicB. This is the vmnic that should be assigned to the vSwitch.
Unable to immediately obtain a dynamic address for this interface. ESX 4.x uses a generated MAC address for the installation service console. The ESX 4.x installation was unable to obtain an IP address from the DHCP server for the generated MAC address. For a successful installation using PXE, the DHCP server must be configured to assign at least a limited number of IP addresses to arbitrary MAC addresses. An ESX 4.
3 Documentation notes This chapter contains notes that affect the Insight Control for Linux user documentation and online help. 3.1 HP Insight Control for Linux Support Matrix The notes in this section apply to the HP Insight Control for Linux Support Matrix. 3.1.
date and time stamp: 10_mgmt_install.sh An error occurred during the RPM installation. 3.3 HP Insight Control for Linux User Guide and online help The notes in this section apply to the HP Insight Control for Linux User Guide. An HTML version of the HP Insight Control for Linux User Guide is used as the Insight Control for Linux online help. 3.3.1 Addition to Chapter 1, Using HP Insight Control for Linux The following item is missing in the bullet list in Section 1.14.
3.3.4 Additions to Chapter 6, Managing the Insight Control for Linux repository The following items should be added to Chapter 6 in the specified locations: • Section 6.2.2 is missing the following NOTE. It should be positioned after step 3 of the procedure to register an OS in the repository. NOTE: The VMware ESX and ESXi operating systems use revision numbers that have multiple sub-versions, for example ESX3.0.3U4, that are not matched exactly when registering the operating system into the repository.
• Ensure that the selected boot partition matches the boot partition in captured image. If you use the Partition Wizard to specify a different disk partitioning scheme, the bootable partition (typically /boot or /) must be the same partition as in the captured image. This is typically the first partition (partition 0) for RHEL distributions, but the second partition (partition 1) for SLES distributions.
HP advises you to upgrade the firmware of DL1xx servers to the most recent version. 3.3.9 Correction to Chapter 22, Advanced topics In section 22.2, Deploying WBEM provider components using Configure or Repair Agents task, the topics that apply to RHEL 5.3 also apply to RHEL 5.4. Likewise, topics that apply to SLES 10 SP2 also apply to SLES 10 SP3. 3.3.10 Additions to Chapter 23, Troubleshooting • The following items are missing from Section 23.
• The following items are missing from Section 23.15.1, RHEL and SLES installations: Cause/Symptom Corrective actions cciss: fifo full error on ProLiant ML350 G6 console Install the cpq-cciss driver option from the latest This error appears on the console of a ProLiant ML350 supported PSP. G6 installed with RHEL 4 Update 7 or RHEL 5 Update 2.
• The following items are missing from Section 23.18, Troubleshooting server power control problems Cause/Symptom Corrective actions Power cycle after SIM discovery starts bare metal discovery Powering on the server a second time causes it to boot normally, and this problem will not reoccur. A server that is set to PXE boot all the time might not boot properly after it is discovered with the Options→Discovery... tool.
• The following items are missing from Section 23.26, Troubleshooting virtual machine installation and setup problems: Cause/Symptom Corrective actions Virtual machine management might fail to start on the CMS Follow this procedure: 1. Verify that virtual machine management has started: In some cases, particularly for the RHEL 4.n release stream, HP Insight Control virtual machine management does not start properly after a reboot. # /etc/init.d/hpvmm status 2.
Index automatic firmware update (see firmware update) (see also ProLiant) supported in this release, 7 hardware requirements, 10 B I bare metal discovery iLO to server association lost, 33 power cycle starts , 33 starts after power cycle, 33 iLO to server association lost, 33 image deployment, 21 (see also Linux image deployment) installation custom OS, 21 PSP, 21 supported operating systems, 21 with multiple storage media, 32 installation guide notes for, 27 installation requirements, 10 ISO image obt
intermittent failures, 33 power management, 20 ProLiant new models supported in this release, 7 ProLiant DL100 G5 bare metal discovery fails , 14 ProLiant DL100 series server metrics reporting, 16 ProLiant DL180 G5 cannot deploy SLES 10 SP2 image, 22 PSP hpsmh and hponcfg components, 21 installing, 21 PXE booting, 15 R Red Hat Enterprise Linux (see RHEL) repository management, 20 incorrect rename for captured image, 21 RHEL, 7 RHEL 5 Update 2 deprecated, 10 S security bulletins and alerts, 11 sensor metri
