HP Instant Capacity release notes for Version 10.x (5900-1258, October 2010)

Changes to icapstatus output
The icapstatus command has been changed so that the Actual Active cores count now includes
the total number of cores assigned to the vPar database, including any cores used by an
inaccessible virtual partition.
The GiCAP section of the icapstatus output has been expanded and now includes information
about the active Group Manager and the standby Group Manager.
The icapstatus output now displays the full iCAP version string and a date and time have
been added to the local nPartition status.
Internal Representation of the Group Manager
In previous releases, the internal representation of the Group Manager was maintained as an IP
address. It is now maintained by its host name. This enables the use of a GiCAP Group Manager
using DHCP for dynamic IP addresses.
New GiCAP Configuration File for Group Members
In versions 9.0 and later, the file /etc/opt/iCAP/GiCAP.configFile is created on every
host of a GiCAP group member. It contains information needed by the iCAP software when
contacting the Group Manager for the host.
GiCAP Activation Time
In iCAP versions prior to 9.0, the GiCAP Group Manager would do an iCAP compliance check
of every group member whenever the GiCAP Group Manager was restarted. This could occur
quite frequently due to the automatic shutdown of the GiCAP Group Manager WBEM provider
by the local CIM server. The CIM server shuts down WBEM providers, such as the GiCAP
Provider, whenever it has been idle for a period of time. This means that GiCAP Group Manager
restarts could happen multiple times during the day, depending on how frequently the GiCAP
Group Manager was accessed by icapmanage or icapmodify commands.
With this release, the GiCAP Group Manager does an iCAP compliance check on a group member
only once a day or any time a host on that member reboots. The once a day compliance checks
are done at different times for each group member, thereby diffusing the performance impact
of starting up the GiCAP Group Manager.
The impact of this performance improvement depends on the size of your group, and the number
and timing of your GiCAP-related commands.
New log file entries
When asset reports cannot be sent, new entries are added to the iCAP log file (/var/adm/
icap.log). New GiCAP log file (/var/adm/GiCAP.log) entries have been added to reflect
high availability operations.
Changes in Version 8.03.01 from Version 8.03 (HP-UX)
Changes to icapmodify in a virtual partition environment
In previous releases, running the command icapmodify -d in a virtual partition environment
incorrectly issued an error message stating that cores could not be deactivated when cores were
available for deactivation. This command now counts unused capacity as a part of the number
of cores that can be deactivated.
Changes to icapmodify on GiCAP group members
In previous releases, running concurrent icapmodify –a commands that required the borrowing
of core usage rights on two or more virtual partitions in a vPar database on a GiCAP group
member resulted in an unbootable vPar database. This problem has been fixed.
Summary of New Features and Changes 23