HP Instant Capacity Release Notes for Versions 8.x

added to a non-iCAP partition, icapmodify operations were required in order to activate the
newly added cores. With this release, the icapmodify operation is no longer needed.
Running icapstatus on a non-iCAP system
For a complex which does not include any Instant Capacity components, the Intended Active
output of the icapstatus command was changed. icapstatus reports a value of the total
number of activated configured cores for Intended Active.
Error in applying GiCAP codewords
A problem was fixed where attempting to apply a GiCAP sharing rights codeword intended for
another system would prevent future application of a good GiCAP sharing rights codeword on
the system.
Displaying vPar code on a non-partitionable system
In previous releases, icapmanage would show the vPar code only if the command was run on
a partitionable system. icapmanage will display the vPar code on all systems when one is
present.
Error modifying partitions on a remote iCAP complex
In previous releases, attempts to modify partitions on a remote iCAP complex using the complex’s
service processor’s LAN port could fail with the message “Error: Operation not approved
due to the following low-level error: ERROR: Unable to execute command:
/opt/wbem/bin/wbemexec -t”. This problem has been fixed.
Error creating partitions on a remote iCAP complex
In previous releases, attempts to create partitions on a remote iCAP complex using the complex’s
service processor’s LAN port could create an error. This problem has been fixed.
Error in submitting audit snapshots
In iCAP version 8.00, memory units were standardized; however, the Audit Snapshot code was
not changed to reflect the new standardized memory units and audit snapshots were not
compatible with the changes implemented at the portal. This problem has been fixed and audit
snapshots produced by iCAP 8.01.x are compatible with portal operations.
Change in icapstatus output
The icapstatus field “Number of cores that are deconfigured or attached to inactive cells” in
the Virtual Partition section of the output was changed to “Number of cores currently unavailable
for assignment”.
Changes in GiCAP grouping rules
The iCAP installation depot no longer includes a default GiCAP grouping rules file; it now must
be downloaded from the portal. The format of the grouping rules file was changed with this
release; previous versions of the grouping rules files are no longer valid.
Processor Frequencies Recognized by GiCAP
The iCAP software uses rounded processor frequency values which match the rounded values
reported by the HP-UX machinfo command. For example, a processor with a true frequency
value of 1.398 Ghz is rounded to a value of 1.4 Ghz. The GiCAP rules file contains these rounded
frequency values.
20 Major Changes, New Features and Requirements of Instant Capacity 8.x