HP Virtual Server Environment Management for Integrity Version 4.
© Copyright 2007–2009 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 About This Document.........................................................................................................5 Intended Audience.................................................................................................................................5 Document Organization.........................................................................................................................5 Typographic Conventions.....................................................
Installation of HP-UX Patches and Agent Software.............................................................................20 Licenses.................................................................................................................................................21 Additional Software Dependencies......................................................................................................21 4 Known Issues............................................................................
About This Document Intended Audience This document is intended for use by system administrators, application administrators, capacity planners, and other technical professionals who are involved with data center operations, administration, and planning. Document Organization This document is organized as follows: Chapter 1 (page 9) This chapter highlights the major new capabilities in this release, then lists all the new capabilities, organized by product area.
| Separates items in a list of choices. WARNING A warning calls attention to important information that if not understood or followed will result in personal injury or nonrecoverable system problems. CAUTION A caution calls attention to important information that if not understood or followed will result in data loss, data corruption, or damage to hardware or software. IMPORTANT This alert provides essential information to explain a concept or to complete a task.
HP Encourages Your Comments Your comments and suggestions regarding product features will help us develop future versions of the Virtual Server Environment Management Software. Use the following email address to send feedback directly to the VSE Management Software development team: vse@hpuxweb.fc.hp.com. NOTE: HP cannot provide product support through this e-mail address. To obtain product support, contact your HP Support Representative, your HP Services Representative, or your authorized HP reseller.
1 New Capabilities These release notes include coverage of the VSE Management Software Version 4.0 October 2008 Update Release. For details on the October 2008 Update Release, see “VSE Management Software Version 4.0 October 2008 Update Release” (page 19). Highlights VSE Management Software Version 4.
New Capabilities by Product Area The following sections list all of the new capabilities available in this release, organized by VSE product or functional area.
• • Network and disk I/O are now viewable within scenarios and used throughout Capacity Advisor. The user is allowed to specify maximum expected data rates for network and disk I/O, or default to maximum observed values. The HP Smart Solver allows system administrators to generate capacity planning information in an automated fashion, thus saving the time and effort required to manually plan the placement of workloads on systems.
• • • • • • • • • SRD. Also, you can use Temporary Instant Capacity (TiCAP) within an SRD based on a GiCAP group. New type of conditional policy based on time. New type of conditional policy based on the existence of a file (useful during system or application start-up). New type of custom policy that scales a metric (you provide through gwlmsend) to produce a CPU request. New default Min Size value for gWLM-provided OwnBorrow policies. The default Min Size is now 0.0.
HP Integrity VM Manager • • • • Compatibility with HP Integrity Virtual Machines version 3.5 (A.03.50). Support for creating HP-UX 11i v3 and Linux virtual machines, using the Create Virtual Machine wizard. For more information, see the VM Manager online help. Support of Accelerated Virtual Input/Output (AVIO) network and storage devices. AVIO storage devices can be added to a new virtual machine by using the Create Virtual Machine wizard.
• • • From the Virtualization Manager Visualization tab, click the iCAP technology link associated with any managed system that has iCAP components, TiCAP capacity, or is a member of a GiCAP group. Select Tools→Instant Capacity Manager from the VSE Management menu. Select Tools→Instant Capacity Manager from the HP SIM menu. Partition Manager This release of Partition Manager includes support for cell online activation and cell online deactivation.
2 Documentation Corrections and Additions The following items are late corrections and additions to the VSE Management Software documentation. General Even though the product documentation states OpenSSH is required, Insight Dynamics - VSE supports Microsoft Windows environments not running OpenSSH. For details about limitations when using Microsoft Windows systems without OpenSSH, see “Managing Microsoft Windows Severs without OpenSSH Installed” (page 20).
Changes to Capacity Advisor Profile Viewer Changes to the Profile Viewer are not documented in the Capacity Advisor Help Reference. Consult the Capacity Advisor Version 4.0 User Guide at http://docs.hp.com/en/vse.html for the most recent information on how to use this feature.
VM Manager “Create Virtual Machine” Summary Help Page Displays Misleading Information The Summary screen is displayed by the Create Virtual Machine wizard after you have specified all the parameters and devices for the virtual machine being created. The Summary help page incorrectly describes how the commands and error checking are executed when creating a virtual machine with the wizard. As documented correctly in the HP Integrity Virtual Machines Manager Version 3.
By selecting appropriate sizes for the fixed policies, the GiCAP requirement to clear the loaned/borrowed usage rights can be satisfied. For more information, see the section “Global Instant Capacity Member Removal” in the HP Instant Capacity User's Guide.
3 Installation, Configuration, and Licensing For system requirements and installation instructions on a CMS running HP-UX, see VSE Management Software Version 4.0 Installation and Update Guide for HP-UX. For HP ProLiant servers running Microsoft Windows, see HP Insight Control Management Quick Setup Poster. See “Additional Software Dependencies” (page 21) for additional software not included with this release that might be required in your configuration.
Downloading HP-UX Patches To download patches for HP-UX, use the HP IT Resource Center website (http://itrc.hp.com). 1. Go to the HP IT Resource Center (http://itrc.hp.com) and select the “Patch database” link under the Downloads section. 2. Login or create an account if this is the first time visiting the site. 3. Search for the various patch IDs and download the patches by following the instructions on the patch page. See the following section for details on installing and removing HP-UX patches.
PHKL_33752 Intel® Itanium® 2 processor speed reporting patch for Integrity systems running HP-UX 11i v2. Required by VSE so that Capacity Advisor can get the correct clock speed for the system. Requires reboot. PHKL_35174 Partition ID, PCI EH, PCIe patch for HP-UX 11i v2 Integrity systems. Required by VSE in order to discover and manage nPartitions or virtual partitions. Requires reboot. PHSS_33349 Linker + fdp cumulative patch for HP-UX 11i v2 Integrity systems. Corrects a WBEM memory leak.
4 Known Issues Known issues and limitations of this release are listed below, organized by VSE product or functional area.
Workaround Cancel the VSE Uninstall process and then proceed with the installation of the others ICM components. When the ICM installation finishes, be sure that HP SIM is running, then run the following command to install/configure VSE: vseinitconfig -a -x restart_sim=true • Database Error on Windows Installation Installing HP Insight Dynamics - VSE on Windows may produce the following message in C:\Program Files\HP\Virtual Server Environment\logs\gwlminitconfig.log.
• • Perl version 5.6.1 is not supported on an HP-UX CMS. You must update Perl to version 5.8.2 or later. By default, HP SIM automatically performs a daily identify operation at 4:05 PM local time. This can be disruptive to normal use of HP SIM because many tasks may be deferred while the identify operation completes.
Minor Issues • Adding Licenses Via VSE Management for Integrity Licenses... Screens When incrementing the number of licenses for a given system, if licenses have been assigned to that system in the same day, the system will end up licensed with only the difference between the original and new assignments. For example, after assigning one license to a system and, that same day, returning to the license screen and changing it to four licenses, the result is the system has only three licenses assigned.
• If you see a noticeable decrease in performance, including slower response times and long durations of “barber poles”, check the mxdomainmgr process (using the Task Manager on Windows and the top command on HP-UX). If the memory in use by the mxdomainmgr process is more than about 1.2 GB on a Windows CMS and 1.5 GB on an HP-UX CMS, this may be causing the performance decline and, in rarer cases, out of memory errors in the user interfaces or HP SIM logs.
SEVERE [20] Error retrieving the last configuration: java.lang.NullPointerException. SEVERE [21] Error starting CMS daemon. Make sure C:\Program Files\HP\vsevseinitconfig has been run after gWLM installation or upgrade. SEVERE [22] java.lang.NullPointerException caused by java.lang.NullPointerException caused by java.lang.NullPointerException at com.hp.gwlm.storage.DataManager.buildConfig(DataManager.java:1651) at com.hp.gwlm.storage.DataManager.getConfig(DataManager.java:1523) ... Caused by: java.lang.
• Performing name changes on already licensed systems can cause them to disappear from Virtualization Manager. Workaround • • In order to perform operations on active logical servers such as an SMP migration, you must select the physical blade or VM system from the Physical and Virtual perspective. Selecting items on the Logical Servers perspective and invoking tools from the HP SIM tools menu will not function properly in this release.
— the license from the old node name to the new one. Do this by selecting the Show All Licensed Systems option. Change the preferred name of the re-added node to its original name using the Edit System Properties dialog in HP SIM. Virtualization Manager Limitations • On the Visualization tab, the Virtual Machine perspective does not show VMware Virtual Center data centers, clusters, or resource pools. Workaround To see this information, go the HP SIM System Properties page for the virtual machine.
• • • Monitored workloads are not supported on any Windows or Linux systems except for Linux running on Integrity 64-bit architectures. When you create workload definitions on the “Create Monitored Workload Definition” page, Virtualization Manager presents a list of systems from which you can deploy the workload. This list can contain systems on which monitored workloads are not allowed. Further, the Tools→Update System Workloads menu might be available on systems that do not support monitored workloads.
• Using illegal characters when creating a regular expression in an AD template will crash the Application Discovery user interface. Application Discovery recognizes regular expressions constructed using Perl 5 or POSIX syntax and semantics. If you use characters or syntax not recognized by these conventions (shell syntax, for example), the AD user interface will crash. Workaround See “PCRE - Perl Compatible Regular Expressions” at http://www.pcre.
Discovery agent can be stopped by running /opt/amgr/bin/agent_stop as root on the HP-UX– or Linux-managed system. • • If the clock on managed systems are off by more than a few minutes to the current time on the CMS, then the Application Discovery agent communication with the CMS may be delayed by the clock differential. Application Discovery user interface screens display OS version number “SLES0” for SLES10 Linux managed nodes.
ip-address: The system "hostname.hp.com" has no workload defined. Make sure to select Tools->VSE Management... in HP-SIM before running this command for the first time. • • • • and the stated fix fails to correct the problem, you must ensure that the DNS lookup returns the host name of the system rather than its IP. For the IPM power history of a managed node, the Refresh Data button may appear not to work and a javascript error may be displayed in the lower left corner of the page.
• • The JS and CSS directories are not created when running the capreport command. This only occurs for the English Windows CMS localized to Japanese. Parked/Reassigned Workload Shows Incorrect Utilization If you select a workload in a scenario and choose What-if Action→Park Workloads... then later select the same workload and choose What-if Action→Move Workloads...
Workaround You will need to re-identify the VM Host and its virtual machines to correct this issue. You may then want to click the “Refresh Data” link on the Virtualization Manager Workload tab to ensure the information is also up-to-date for Capacity Advisor. If this problem persists, you may need to run vseassist on the VM Host to determine why HP SIM is not correctly identifying the VM Host and its constituents. • • • • • For VMware hosts/guests, Capacity Advisor requires use of VMM 3.
— — • The properties files for gwlmagent and gwlmcmsd are parsed as English, regardless of the locale setting. So, be careful of using commas where English would use periods. Some items are always in English: ◦ Start-up messages from gwlmagent and gwlmcmsd ◦ Log files ◦ Messages from initial configuration Unable to Manage Partitions with Inactive Cells or Deconfigured Cores gWLM does not support management of partitions with either inactive cells or deconfigured cores.
with entitlements specified in percentages. (That is, do not manage virtual machines with entitlements specified in CPU cycles.) To obtain older versions of the gWLM agent, and for assistance with this configuration, contact HP at the following email address: gwlmfeedback@rsn.hp.com. • Compatibility with PRM and WLM You cannot use gWLM with either Process Resource Manager (PRM) or Workload Manager (WLM) to manage the same system at the same time.
— Ensure that the mode attribute for the sharedResourceDomain element is set to the desired value (Managed or Advisory): mode="Managed" — Ensure that the interval attribute for the sharedResourceDomain element is set to the desired value: interval="x" — Ensure that the ticapMode attribute for the sharedResourceDomain element is set to all if you want gWLM to allocate TiCAP when needed: ticapMode="all" — 3.
Workaround Update the CMS version. This update also installs the corresponding agent. (Because gWLM requires all managed nodes in an SRD to have the same agent version, you must update the agents on any other managed nodes that could be in an SRD that includes the CMS. For information about performing this update, see the VSE Management Software Installation and Update Guide. • gWLM Fails to Start with Certain Time Zone Settings gwlmcmsd and gwlmagent can fail to start with certain time zone settings.
Workaround You can manage the workloads using compartments based on fss groups (which have a smaller minimum size) or add resources to the partition or SRD to enable the pset minimum size requirements to be met. • Constant Use of TiCAP Global Workload Manager can activate TiCAP if needed to satisfy SRD policies. To avoid unnecessary consumption of TiCAP, you must have a sufficient number of CPUs with permanent licenses available.
1. 2. In the file /etc/opt/gwlm/conf/gwlmcms.properties (HP-UX) or install-path\VirtualServerEnvironment\conf\gwlmcms.properties (Windows), increase the CMS database cache size by increasing the value of the com.hp.gwlm.cms.cachesize property by 25%. (The cache is more memory efficient if the size is near a power of 2. If your target cache size is close to a power of 2, round it up to the next power. For example, if your target cache size is 60,000, round it up to 66,000.
• Configurations with Psets Nested in Virtual Partitions Rejected With vPars version < 4.0 gWLM does not support nesting psets in virtual partitions when the vPars version is earlier than vPars A.04.00. However, it has not always rejected such configurations. gWLM 4.0 does reject these configurations though. So, configurations you used with gWLM 2.x or gWLM 3.x can be rejected when you begin using gWLM 4.0 agents.
— — A corporate LAN/WAN via one network interface card and IP address A second, private internal network and private IP address for communicating with a certain other set of hosts (such as cluster members) Global Workload Manager attempts to detect and report network configuration issues that can cause undesirable behavior, but in some cases this detection occurs in a context that can be reported only into a log file.
[mysystem#3] > grep 15.11.100.17 /etc/hosts 15.11.100.17 mysystem.mydomain.com mysystem d. Verify that the reverse lookup of the IP address returns the same fully qualified domain name as configured in /etc/hosts. [mysystem#4] > nslookup 15.11.100.17 Trying DNS Name: mysystem.mydomain.com Address: 15.11.100.17 Fix any issues by editing /etc/hosts or for additional information, see: — The HP-UX IP Address and Client Management Administrator's Guide, available online at http://docs.hp.com.
Using the HP SIM interface: Select the menus Configure → Configure VSE Agents → Start gWLM Agent • Configuration of Agent and CMS Not Synchronized Occasionally, a gWLM agent and the gWLM CMS disagree on whether an SRD is actually deployed. This can occur when you use Ctrl-C to interrupt a gwlm deploy or undeploy command. It can also occur if there are errors saving a gWLM configuration: The configuration is deployed and then saved to the gWLM configuration repository.
state where the agent on each of its managed nodes must be restarted. It can also be caused by a managed node being down, having its gwlmagent not running, or being hung. If the managed node is down or gwlmagent is not running, you will see the following message: The gWLM agent process on the host is not running -- start the agent and retry.
ERROR: Task 'Secure gWLM Communications' terminating. This message is displayed when a communications certificate file hostname-certificate-file has been corrupted or is not valid. Workaround 1.
• Only One SRD is Allowed to be Deployed You might see a message similar to the following: Error trying to deploy SRD, mysystem.vpar.000 to mysystem2.mydomain.com. SRD, mysystem2.fss.000 is already deployed. Only one SRD is allowed to be deployed. Workaround Undeploy the SRD using the --force option with the gwlm undeploy command, and restart gwlmagent on the managed node.
explained in the online help topic "pset / fss group tips" in the section "Precedence of placement techniques." If you use the psrset command to place processes in psets, gWLM is likely to move the processes to the default pset. Workaround To maintain the placement of a process, use gWLM's application records or user records when creating or editing your workload definitions in gWLM. If using records is not practical, use the gwlmplace command.
— — • Adjust the entitlements of those virtual machines that are on so that the CPUs are not oversubscribed. Stop one or more virtual machines until those still on do not oversubscribe the CPUs. Unmanaging a Virtual Machine That Is On Leaves SRD Undeployed When attempting to unmanage a virtual machine that is started, the SRD can be undeployed, even though the following message is displayed: The virtual machine VM_name on host hostname is on but does not have an associated gWLM policy.
Manager version 3.5 does not fully support them. A nested APA device is a grouping of other APA devices. For example, if lan900 is an APA device composed of physical network interface cards (NICs) lan1 and lan2, and lan901 is an APA device composed of physical NICs lan3 and lan4, the HP network configuration utilities allow you to define a nested APA lan902 device that is composed of lan900 and lan901.
version 3.0 or later. If HP WBEM Services version 2.5 or later is required on a VM Host, upgrade Integrity VM to version 3.0 or later. Minor Issues • A Virtual Machine Deleted Soon After Being Created Might Appear in Virtualization Manager When using VM Manager from HP SIM with VSE, if you create a virtual machine and then delete it before the new virtual machine has been identified by HP SIM, the virtual machine might appear in Virtualization Manager as though it had not been deleted.
• Negative TiCAP values are not included in the total. Workaround • • Do not let the TiCAP balance for a complex drop below zero. When a system becomes a GiCAP group manager, the system must be reidentified in HP SIM for the GiCAP group manager to be visible in iCAP Manager. nPartitions that are not running HP-UX will not appear on the Complex page in iCAP Manager. Partition Manager Minor Issues • The Partition Manager Help menu and context-sensitive Help buttons do not work.
• The vseassist command checks that use the Win32 API are not logging API and exit code details to the logfile. The status (PASS, FAIL, or WARN) of these checks is still logged. And if the check fails, vseassist logs the Issue and Resolution messages for the failure. However, vseassist does not log the details of the APIs that were called and their results.
