HP Instant Capacity Release Notes for Version 9.
© Copyright 2000–2010 Hewlett-Packard Development Company, L.P Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About this Guide................................................................................................................7 Intended Audience.................................................................................................................................7 Typographic Conventions......................................................................................................................7 Publishing History.......................................................
Status Considerations.................................................................................................................37 Lost Certificates..........................................................................................................................37 Manual Regeneration of Certificates and Time Skew................................................................
List of Tables 1-1 Most Recent Instant Capacity Versions and Supported Platforms...............................................
About this Guide Intended Audience All personnel with system administrator access (that is, with root login privileges on HP-UX systems, or Administrators on OpenVMS systems) to an Instant Capacity system should read and understand the contents of this document and the implications of managing an Instant Capacity system. Administrators are expected to have knowledge of HP-UX, or OpenVMS Integrity operating system concepts, commands, and configuration. This document is not a tutorial.
IMPORTANT This alert provides essential information to explain a concept or to complete a task NOTE A note contains additional information to emphasize or supplement important points of the main text. Publishing History The document printing date and part number indicate the document’s current edition. The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The document part number will change when extensive changes are made.
1 Instant Capacity 9.x Release Notes This chapter covers the following topics: • “Instant Capacity Product Overview” (page 10) • “Location of Instant Capacity Information” (page 11) • “Most Recent Instant Capacity Product Versions and Supported Platforms” (page 14) • “Past Versions and Supported Operating Systems” (page 15) For details about the changes to Instant Capacity version 9.x software, see Chapter 2.
Instant Capacity Product Overview HP Instant Capacity software provides the ability to instantly increase or decrease processing capacity on specified HP enterprise servers. With Instant Capacity, you initially purchase an HP enterprise server with a specified amount of active processing capacity, and a specified amount of inactive processing capacity (Instant Capacity components). These release notes provide the most recent information about new features and changes for version 9.
Location of Instant Capacity Information Instant Capacity Release Notes for Version 9.x You can find the HP Instant Capacity Release Notes for Version 9.x in the following locations: • On the HP Documentation website: http://docs.hp.com These are the most current release notes and the most current localized versions.
Instant Capacity User’s Guide for Version 9.x You can find the HP Instant Capacity User’s Guide for Version 9.x in the following locations: • On the HP Documentation website: http://docs.hp.com These are the most current localized versions.
Manpages NOTE: The information in this section applies only to HP-UX systems. It does not apply to Integrity servers running OpenVMS.
Most Recent Instant Capacity Product Versions and Supported Platforms Table 1-1 lists the current versions of Instant Capacity and the platforms supported for each version. Table 1-1 Most Recent Instant Capacity Versions and Supported Platforms Software and Version Operating System Version Supported Hardware Platforms Notes iCOD HP-UX 11i v3 HP Integrity servers: • Superdome • rx8640 • rx8620 • rx7640 • rx7620 Available on: • http://www.hp.
Past Versions and Supported Operating Systems Previous versions of the Instant Capacity software are as follows: • B.01.00 (on HP-UX 11.00) • B.02.x (on HP-UX 11.00 and 11i v1) • B.03.x (on HP-UX 11i v1) • B.04.x (on HP-UX 11.00 and 11i v1) • B.05.00 (on HP-UX 11.00 and 11i v1) • B.06.x (on HP-UX 11i v1 and 11i v2) • B.07.x (on HP-UX 11i v1 and 11i v2) • B.08.00 (on HP-UX 11i v1 and 11i v2) • B.08.00.01 (on HP-UX 11i v1 and 11i v2) • B.08.01.00 (on HP-UX 11i v1 and 11i v2) • B.08.01.
2 Major Changes, New Features, and Requirements of Instant Capacity Version 9.x This chapter covers the following topics: • “Program Requirements” (page 17) • “Summary of New Features and Changes” (page 18) • “Known Problems” (page 26) • “Software Requirements” (page 31) • “Usage Rights Requirement” (page 34) • “GiCAP Requirements” (page 35) The following sections provide only a summary of the Instant Capacity Version 9.x major changes and features.
Summary of New Features and Changes This section summarizes the new features and changes of the Instant Capacity product. Changes in Version 9.0.3 from Version 9.0.2 (HP-UX) icapd daemon fix Resolved an issue where the icapd daemon woke up earlier than expected to perform the routine Instant Capacity software tasks. System contact email address fix In previous releases, if the system contact email address was more than 128 characters, it corrupted the GiCAP database.
GiCAP database problems fixed The following two problems were fixed in iCAP version 9.01 that could have resulted in corruption of the GiCAP database: • • Simultaneous operations involving the borrowing or loaning of core usage rights in a GiCAP group could result in a corrupt database. The problem only occurred under unusual timing circumstances. Transferring usage rights from a group member to prevent the consumption of temporary capacity on another group member could result in a corrupt GiCAP database.
Compatibility with gWLM iCAP version 9.0 is not compatible with gWLM version 4.0 or earlier. gWLM version 4.1 or later is required. Changes to icapmanage output The icapmanage –s command has been changed to show the current date and time, the full iCAP version string, and information about the standby Group Manager. Improvements in icapmanage error and status messages In previous releases, running the icapmanage –r –m command on a member not defined in any group produced an unclear error message.
TiCAP debit fixes Two race conditions that might have caused incorrect TiCAP debiting have been fixed. One was identified as a potential problem during an ignite installation of one partition, while another partition was active (and running the iCAP daemon). Another potential problem involved a very small and unusual timing window when concurrent activations and deactivations were done on different partitions of the same server.
available for deactivation. This command now counts unused capacity as a part of the number of cores that can be deactivated. Changes to icapmodify on GiCAP group members In previous releases, running concurrent icapmodify –a commands that required the borrowing of core usage rights on two or more virtual partitions in a vPar database on a GiCAP group member resulted in an unbootable vPar database. This problem has been fixed. Changes in Version 8.03 from Version 8.02.01 (HP-UX) Support for vPars A.03.
NOTE: The Group Manager must be running iCAP version 8.02.01 or later, and all known hosts on the complex containing a failed group member must be running iCAP version 8.02 or later, in order to enable full Disaster Recovery features. Changes in Version 8.02 from Version 8.01.
Additional improvements were made to the error handling on GiCAP database write errors. Previously, a write error may have resulted in incorrect gain or loss of usage rights within the group. Improved GiCAP Logging GiCAP logging was improved with this release. The GiCAP log file /var/adm/GiCAP.log includes logging for events such as usage rights transfers, TiCAP transfers, usage rights releases and compliance events.
Changes in Version 8.1 (OpenVMS) Implementation of Global Instant Capacity (GiCAP) GiCAP is fully functional in iCAP version 8.1 on OpenVMS systems. The Group Manager must be an HP-UX system running Instant Capacity software version 8.01.01 or later.
Known Problems Codependency between vPars and iCAP (HP-UX) If you are installing iCAP on an HP-UX 11i v1 vPars system, and want to update to vPars version A.03.05, or configure mixed 11i v1 vPars A.03.05, and 11i v2 vPars A.04.05 or 11i v3 vPars A.05.03, you must install iCAP version 8.03 or later on each 11i v1 virtual partition. This also installs the required versions of WBEM and nParProvider and necessary patches. Installing iCAP version 8.
GiCAP Known Problems (HP-UX) Network-related problems when re-adding members to groups Some users upgrading to iCAP Version 9 have encountered messages like the following, when re-adding existing members to a GiCAP group: icapmanage -a -g Group1 -m xyzmember:abc.hp.com,def.hp.com,ghi.hp.com icapmanage command failed. Attempt to re-add xyzmember to Group1 failed due to a match in the list of OSAddresses.
• least one core per configured cell in the newly booted partition. This can result in the number of active cores being large enough to incur temporary capacity charges. Contact HP for additional methods. Inconsistent values reported by icapmanage during rapid updating If the command icapmanage -s is issued while the group is being rapidly updated ( for example, during gWLM load balancing), the number of loans and borrows assigned to each member may not add up in a consistent manner.
Split GiCAP groups If the active Group Manager system becomes unavailable, an administrator can have a standby Group Manager take control of group operations at any time using the icapmanage -Q command. While this can be done routinely (for example, to allow shutting down a functioning, active Group Manager for maintenance), normally this command is issued either when the active Group Manager has failed, or when a network outage prevents it from communicating with group members.
At this point the member can be removed using the icapmanage -r command. 30 Major Changes, New Features, and Requirements of Instant Capacity Version 9.
Software Requirements Every HP-UX and OpenVMS partition in an Instant Capacity system is required to have the Instant Capacity software installed and the icapd daemon running (on HP-UX systems), or the ICAP_SERVER process running (on OpenVMS systems). You must maintain the Instant Capacity software until all program requirements are fulfilled and until the system is no longer considered an Instant Capacity system. If you are using GiCAP, all systems must be running Instant Capacity version 9.x.
IMPORTANT: For the most recent required patches, see the Instant Capacity Installation page on the HP Software Depot (search for “B9073BA”): http://www.hp.com/go/softwaredepot HP-UX 11i v2 Requirements and Dependent Products The following software is required for Instant Capacity version 9.x on HP-UX 11i v2: • • • • • • • HP-UX 11i v2 iCOD software bundle B9073BA (version 9.x) — On the 11i v2 Applications Software media, or download the most recent version from the HP Software Depot at http://www.hp.
• • If you have a virtual partitioned environment, the Virtual Partitions (vPars) software (bundle T1335BC) must be version A.05.01 or higher. vPars is available separately and is not included with the OE. (GiCAP only) The CIM Server configuration property sslClientVerificationMode must be set to a value of “optional” on all GiCAP Group Managers and on all OS instances of all member systems. (The CIM Server may need to be restarted if the property was not previously set to this value.
Usage Rights Requirement A system managed under the Instant Capacity program can include one or more components (core, cell, or memory) that are without usage rights. Before you can use these components, you must obtain additional usage rights. Usage rights can either be purchased from HP, or, if the system is a member of a GiCAP group, borrowed temporarily from another member of the group, as described in the HP Instant Capacity User’s Guide for Version 9.x.
GiCAP Requirements Software and System Requirements To use Global Instant Capacity, all partitions on all servers in the group must be running Instant Capacity version 9.0 or later. The Group Manager must be an HP-UX system running Instant Capacity version 9.0 or later. GiCAP now uses SSL certificates when making remote connections, rather than SSH as in previous releases.
member OS instances, the GiCAP manager, and any planned standby GiCAP manager. This configuration attribute is not dynamic and must be set using the -p option. You must restart the cimserver to set the value. For details, see cimconfig(1M).
exchange SSL certificates it will remove any existing certificates with the same “Issuer” and “Subject” attributes as the certificates the GiCAP software wishes to install. WBEM does not allow the installation of certificates with the same Issuer and Subject as previously installed certificates. The GiCAP software uses private certificates with an Issuer and Subject that should not conflict with other certificates.
icapmanage -a -m xyz:x,y,z -g One Or use: icapmanage -Q The icapmanage -Q command will not reestablish communication between the member host and any standby manager. If a standby manager is being used, you must specify the standby manager again with a command such as: icapmanage -a -S gm2.ba.ff.com The icapmanage -Q command is particularly useful if you should accidentally delete certificates on a group manager or reignite it.
