HP Instant Capacity Release Notes for Version 9.x

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. The problem
only occurred if the Group Manager had intermittent contact with the member donating
the usage rights.
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).
Negative "cores without usage rights" fixed
If simultaneous activations were requested on multiple partitions of a GiCAP group member
that was authorized to use temporary capacity, then the update by the Group Manager might
have resulted in a very large value for "cores without usage rights" on the group member, such
that the value exceeded the field size and displayed as a negative number.
Changes in Version 9.0 from Version 8.03.01 (HP-UX)
High Availability support for group manager
Instant Capacity version 9.0 includes the ability to create a standby Group Manager to be available
for use as an active Group Manager if the currently active Group Manager is unavailable.
To enable this new feature, several new options have been added to the icapmanage command.
The icapmanage -a -S and icapmanage -r -S commands allow users to set up and remove
a standby Group Manager respectively. The icapmanage -Q command allows users to make
a standby Group Manager the active Group Manager. The icapmanage -t command allows
users to manually replicate the GiCAP database from an active Group Manager to a standby
Group Manager.
WBEM 2.05 required for all versions
WBEM Version A.02.05 or higher is now required for all versions of HP-UX.
Changes to GiCAP Communication Protocol
The communication protocol used by GiCAP when making remote connections has changed
with this release. Secure Shell (SSH) is no longer required. iCAP version 9.0 uses SSL certificates
for WBEM security authorization. Communication between the managers and members of groups
is established using SSL certificates which are supplied by the GiCAP software. This change
prohibits GiCAP 9.0 from supporting iCAP versions 8.x on the GiCAP Group Manager or on
any OS instance on any member system. Furthermore, the GiCAP Group Manager, the standby
Group Manager, and all OS instances of all member systems must have the CIM Server property
sslClientVerificationMode set to a value of “optional”.
GiCAP and iCAP do not use any network ports directly. However, version 9.0 GiCAP uses
WBEM/SSL for the communication protocol, requiring use of the CIM HTTPS port 5989. GiCAP
also uses ping (which uses port 7 for the echo protocol) and host lookup services (getaddrinfo
and getnameinfo) which may use the Domain Name System (DNS), Network Information
Service (NIS), or a local host file to provide the lookup function.
Summary of New Features and Changes 19