HP Instant Capacity Version 10.x Release Notes (5900-1580, March 2011)

To support Disaster Recovery, the icapmanage -x option was expanded to allow the transfer of
usage rights not just from single unreachable partitions, but also from members which are completely
unreachable. In the case of unavailable group members, the transfer is limited to a specific time
period of 10 days.
A new option, icapmanage -z, was added to allow users to restore previously seized core usage
rights to a specified host. See the descriptions of the -x and -z options on the icapmanage
manpage for complete details.
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.01 (HP-UX 11i v1, 11i v2 and 11i v3)
Changes Relating to System Compliance
The iCAP software uses the debiting of Temporary Capacity to track the noncompliance of a system,
such as when there are more cores active than there are core usage rights on the system, even if
the system has had no Temporary Capacity applied to it. So, temporary capacity can be negative
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. This enforcement now applies to all systems, whether
or not temporary capacity has been applied.
Changes in the Application of RTU Codewords
A negative TiCAP balance is no longer cleared when applying an RTU codeword.
Also, improvements were made to the application of RTU codewords on GiCAP group members.
With this release, the amount of core usage rights on a member cannot be more than the sum of
the “number of cores without usage rights” and “borrowed core usage rights.”
Improvements in TiCAP Transfer Between GiCAP Group Members
Improvements were made to the transfer of TiCAP between GiCAP group members. The flow of
TiCAP between group members was improved so that all TiCAP-consuming GiCAP members enter
their TiCAP warning period at approximately the same time and all TiCAP-consuming group
members will run out of TiCAP at the same time.
Reboot error with GiCAP members
When GiCAP members were rebooted, under some circumstances there was a startup error message
indicating that the complex was not a member of any GiCAP group. This problem is fixed.
Changes to icapmanage
The icapmanage -s -v option was modified to show additional information including resources
held by the Group Manager, borrow/loan values for group members, and unassigned usage rights
available across the group.
A new option, icapmanage —u -m <member name> —h <hostlist>, was added to provide
host-level operations to icapmanage allowing hosts to be added to or removed from an existing
GiCAP group.
Summary of New Features and Changes 17