HP Instant Capacity Release Notes for Versions 8.x

became “Additional cores that can be assigned with current usage rights” and “Number of
cores that could be assigned with additional usage rights”.
• A problem with the configuration change notification e-mail was fixed. Previously when a
deferred configuration change was requested, sometimes the e-mail incorrectly stated that
deactivation occurred when it was really a deferred activation.
• A problem was fixed with the icapstatus (icod_stat) display of the “actual inactive”
value when LANG = ko.KR.eucKR .
• When determining whether or not to allow activation of a cell, the Instant Capacity software
now properly accounts for whether or not the cell is currently active when determining if
the result of the operation is in compliance. Previously, if parmodify was used to set the
UONB (Use On Next Boot) flag of an active cell to false on a system that was in compliance,
immediately trying to reset the UONB flag back to true (while the cell was still active, before
any reboot) would incorrectly produce an out-of-compliance error.
• A problem where a system was out of compliance because too many cells were active was
fixed. Previously, attempts to bring the system into compliance by setting the UONB flag
on some cells via the parmodify command would fail.
• A problem was fixed relating to the system product number. Previously, if a system was
upgraded from one hardware version to another (for example, from an rp7410 to an rp7420),
then icod_stat (icapstatus) still displayed the original product number instead of the
upgraded product number. This was inconsistent with the behavior of other commands
such as the ID command at the MP, and the output from the parstatus command. This
problem has been fixed and now the upgraded product number will be displayed by
icapstatus.
• A problem with the icod_notify (icapnotify) command was fixed. In certain situations,
a reboot was causing a core dump on shutdown on HP-UX 11.11 systems. A modified
icod_notify script fixes this problem.
• A problem was fixed where an attempt to modify remote complexes would fail with a
message “@117:Error: Operation not approved due to the following
low-level error: index out of range”.
• When a cell in a complex is powered down, iCAP may have reported the following error
message in the /var/adm/syslog/syslog.log file:
icapd: ERROR: The following low-level error occurred:
ERROR: Failure reading detailed cell information
for unknown cell.
ERROR: Required property (CPUSpeed) missing from
WBEM read.
This problem was fixed.
24 Major Changes, New Features and Requirements of Instant Capacity 8.x