HP Instant Capacity release notes for Version 10.
© Copyright 2000, 2011 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.
Contents About this Guide...........................................................................................5 Intended Audience....................................................................................................................5 Typographic Conventions...........................................................................................................5 Publishing History.............................................................................................................
GiCAP Requirements...............................................................................................................30 Software and System Requirements.......................................................................................30 Codeword Requirements.....................................................................................................30 Upgrading Version 8.x Groups to Version 9.x or Later............................................................
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.
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. Document updates may be issued between editions to correct errors or document product changes.
HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to: docsfeedback@hp.com Include the document title, manufacturing part number, and any comment, error found, or suggestion for improvement you have concerning this document.
1 Instant Capacity 10.x release notes This chapter covers the following topics: • “Instant Capacity Product Overview” (page 9) • “Location of Instant Capacity Information” (page 9) • “Most Recent Instant Capacity Product Versions and Supported Platforms” (page 11) • “Past Versions and Supported Operating Systems” (page 12) For details about the changes to Instant Capacity version 10.x software, see Chapter 2.
• In the Instant Capacity 10.x HP-UX software product: /usr/share/doc/icapRelNotes.pdf • On the OpenVMS Version 8.4 Documentation CD (English only) Instant Capacity user’s guide for Version 10.x You can find the HP Instant Capacity user’s guide for Version 10.x in the following locations: • On the BSC website: www.hp.com/go/hp-icap-docs These are the most current localized versions.
Most Recent Instant Capacity Product Versions and Supported Platforms Table 1 lists the current versions of Instant Capacity and the platforms supported for each version. Table 1 Most Recent Instant Capacity Versions and Supported Platforms Software and Version Operating System Supported Hardware Platform Version — HP Integrity iCAP HP-UX 11i v3 Supported Hardware Platform — HP 9000 • HP Integrity Superdome 2 • Superdome B.11.31.10.03.00.
Table 1 Most Recent Instant Capacity Versions and Supported Platforms (continued) Software and Version Operating System Supported Hardware Platform Version — HP Integrity Supported Hardware Platform — HP 9000 iCAP HP-UX 11i v1 • Superdome Not supported. B.11.11.09.02.00 • rp8440 (B9073BA) • rp8420 Available on: • rp8400 • http://www.hp.com/go/ softwaredepot • rp7440 • September 2009 HP-UX 11i v1 Applications Software media • rp7410 iCAP 9.x (BA484AA) • rp7420 HP OpenVMS Version 8.
• 9.02 (on HP-UX 11i v1, 11i v2, and 11i v3) • 9.
2 Major Changes, New Features, and Requirements of Instant Capacity Version 10.x This chapter covers the following topics: • “Program Requirements” (page 15) • “Summary of New Features and Changes” (page 15) • “Known Problems” (page 22) • “Software Requirements” (page 27) • “Usage Rights Requirement” (page 29) • “GiCAP Requirements” (page 30) The following sections provide only a summary of the Instant Capacity Version 10.x major changes and features.
TiCAP debit fix A problem was fixed where the temporary capacity balance was erroneously debited in a GiCAP group. The problem occurred only under unusual timing circumstances. Changes in Version 10.02 from Version 10.01 (HP-UX) A problem was fixed where after a reboot of a partition on HP Integrity Superdome 2, the number of actual active cores was not matching the number of intended active cores for that partition. Changes in Version 10.01 from Version 10.
iCAP 9.01 and partner functionality iCAP 9.01 is the version required for use with VSE 4.1. While iCAP Manager 4.1 is able to monitor iCAP systems with earlier versions of iCAP, it requires 9.01 in order to configure iCAP systems. gWLM 4.1 requires iCAP 9.01 for GiCAP integration support (single-system management is supported with earlier iCAP versions).
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. The command now fails with an error message stating that the member cannot be found in any group.
Changes to icapstatus output The icapstatus command has been changed so that the Actual Active cores count now includes the total number of cores assigned to the vPar database, including any cores used by an inaccessible virtual partition. The GiCAP section of the icapstatus output has been expanded and now includes information about the active Group Manager and the standby Group Manager.
Changes in Version 8.03 from Version 8.02.01 (HP-UX) Support for vPars A.03.05 on HP-UX 11.11 iCAP version 8.03 included support for vPars A.03.05, and support for the “integrated virtual partition environment” on HP-UX 11.11, previously available only on HP-UX 11.23 and 11.31 systems. With this release, vPars A.03.05 became the minimum required version. Support for vPars version A.03.05 integration on HP-UX 11.11 systems allows users to manage 11.11 and 11.23 vPars with the same vparmonitor.
even if temporary capacity has never been purchased or applied; it means that the system has gone out of compliance. Also, if Temporary Capacity is negative and the number of active cores exceeds the number of core usage rights for the complex, at boot time automatic deactivation of cores may occur. This “boottime enforcement” to maintain compliance is not new, although previously there were gaps in enforcement which have now been fixed.
Improvements in Usage Rights Transfers Improvements were made to usage rights transfers in a noncompliant GiCAP group. With this improvement, users can reclaim loaned usage rights even when the group is noncompliant. Changes in Asset Reporting Asset reporting is disabled by default on new installations of Instant Capacity. Asset reporting will remain at the previous setting for reinstalls and upgrades. Asset reporting can be enabled with the command icapnotify -a on.
This problem can be solved by running the icapmodify -w number_of_days command to set the warning period to the required value. If this command is not executed, the temporary capacity expiration warning mails will not be sent to the contact address specified. 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.
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.
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. 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.
• PHCO_24477: S700_800 11.11 sar (1M) patch • PHCO_29832: S700_800 11.11 reboot(1M) patch • PHCO_29833: S700_800 11.11 killall(1M) patch 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 10.
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 v3 Requirements and Dependent Products The following software is required for Instant Capacity version 10.x on HP-UX 11i v3: • HP-UX 11i v3 • iCAP software bundle B9073BA (version10.
HP sends you a letter informing you how to retrieve the RTU codeword from the HP Utility Pricing Solutions website: http://www.hp.com/go/icap/portal After the RTU codeword is retrieved from the Utility Pricing Solutions portal, the RTU codeword is applied to your server by the use of the icapmodify -C command. When the codeword is applied, component-specific usage rights on the system are increased, allowing you to activate one or more additional components.
1. 2. 3. Install iCAP version 9.x (or later) on the Group Manager, any planned standby Group Manager, and each OS instance (host) of each group member. The installations may be done in any order. Set up a CIM Server configuration property (described below) on the Group Manager, any planned standby Group Manager, and each OS instance of each group member. Re-add each group member to the group it already belongs to.
• When a standby manager is added (icapmanage -a -S) certificates are exchanged between the active group manager and the standby manager, and between the standby manager and every host of every member of every managed group. • When a standby manager takes over a group (icapmanage -Q) certificates are exchanged between the new active manager and any member hosts which have not already exchanged certificates with this manager.
Member xyz in GiCAP group One ------------------------------------------------Active Group Manager: gm1.oa.ff.com Standby Group Manager: gm2.ba.ff.com ERROR: Unexpected error HTTP Error (401 Unauthorized). To complete the repair you must either re-add the member to the group using a command on the active group manager similar to: 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.
