HP Instant Capacity release notes for Version 10.x, August 2010 (T1428-90081)

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.
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 <member> 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. In addition, error and status
messages have been improved for these situations: when no groups are defined, when a group
is locked for compliance reasons, when icapmanage is run by a non-root user, and when
erroneously attempting to add virtual machines (“guests”) as group member host systems.
Summary of New Features and Changes 21