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

The vparmodify and vparcreate commands are now bound by the containing nPar's intended
active core count. Also note that in an integrated virtual partition environment, a boot time
compliance check is performed whenever a virtual partition is booted. If the total number of
cores assigned to all virtual partitions in the current vPar database exceeds the nPartition's
intended active core count, the Instant Capacity software notifies the vPar monitor, and the
monitor prevents any virtual partition from booting. See “Instant Capacity Integration with
Virtual Partitions” in the Instant Capacity user's guide for more details. With this release of
Instant Capacity, the compliance checking will now be performed on HP-UX 11.11 vPar systems,
as well as 11.23 and 11.31 systems.
Changes in icapstatus output
The format of the date displayed by the icapstatus command was changed to facilitate
translation. Also, the format of the iCAP version number has been changed to provide more
information.
Improvements in translated messages
Several corrections were made to the Italian and Spanish message catalogs.
Changes in Version 8.02.01 from Version 8.02 (HP-UX)
GiCAP Disaster Recovery
iCAP version 8.02.01 included implementation of GiCAP Disaster Recovery, which enables the
distribution of core usage rights from a GiCAP member which is offline due to some disaster,
to other members of the group, and the restoration of usage rights to the member once contact
has been restored.
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)
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.
24 Major Changes, New Features, and Requirements of Instant Capacity Version 10.x