HP Instant Capacity Release Notes for Versions 8.x

Changes in Version 8.00.01 from Version 8.00 (HP-UX only)
Modifications of Remote Complexes
A problem was fixed where an attempt to modify remote complexes would fail with a message
“@117:Error: Operation not approved due to the following low-level
error: index out of range”.
Error When Cells are Powered Down
When a cell in a complex is powered down, iCAP reported the following error message in the
/var/adm/syslog/syslog.log file:
icapd: ERROR: The following low-level error occurred:
ERROR: Failure reading detailed cell information
for unknown cell.
ERROR: Required property (CPUSpeed) missing from
WBEM read.
This problem has been fixed.
Changes in Version 8.0 (OpenVMS only)
iCAP version 8.0 included support for HP Integrity Servers running OpenVMS Industry Standard
64 Operating System V8.3.
Changes in Version 8.00 from Versions 7.x (HP-UX only)
Support for Global Instant Capacity (GiCAP)
Global Instant Capacity, or GiCAP, provides HP customers with the flexibility to move usage
rights (RTUs) for Instant Capacity components within a group of servers. It also provides “pooled”
temporary capacity across the group. This provides more cost-effective and higher availability,
more adaptable load balancing, and more efficient and easier use of temporary capacity.
Global Instant Capacity is built on the concept of a server group, or GiCAP Group. This is a list
of servers that are allowed to share iCAP usage rights. In addition, at least one HP-UX system
running iCAP must be designated as the Global Instant Capacity Group Manager. The Group
Manager hosts the GiCAP software that maintains a database of information about the group
and about group resources (usage rights and temporary capacity).
The Group Manager must be an HP-UX system running Instant Capacity version 8 or later
software. The system running the Group Manager does not need to have any Instant Capacity
components, nor does it need to be a partitionable system. A Group Manager cannot be run on
a virtual machine (also known as a “guest”). A GiCAP group is managed using the new command
icapmanage on the Group Manager system.
While GiCAP is part of Instant Capacity and is installed at the same time as iCAP, it is not enabled
during installation. In order to share resources across groups, you must purchase a GiCAP
Sharing Rights codeword from the iCAP portal. Application of the Sharing Rights codeword to
the Group Manager system enables the creation of a GiCAP Group containing members that
have Instant Capacity components without usage rights. All GiCAP group members must run
Instant Capacity version 8.x.
Instant Capacity now allows deactivations of cores on non-Instant Capacity systems (those
without any Instant Capacity components), allowing such systems to participate in a GiCAP
group and loan usage rights to Instant Capacity systems. Temporary capacity codewords can be
applied to non-Instant Capacity systems, allowing them to share temporary capacity with other
members of a GiCAP group.
Additional information on GiCAP Groups and Sharing Rights can be found in the Instant Capacity
User’s Guide for versions 8.x.
Summary of New Features and Changes 21