HP Instant Capacity support 10.x Release Notes (762795-002, June 2014)

Expiration time for TiCAP in warning message in OA syslog is not correct
If the warning period message appears in the OA syslog, the complex is in warning period. If the
expiration time for TiCAP is not logged correctly in this message, refer to the icapstatus command
output for TiCAP expiration time.
NOTE: If firmware version 3.6.48 or later is installed on HP Integrity Superdome 2, the expiration
date appears both in the OA syslog and the email message, but the actual expiration time doesn't
appear.
Low-level WBEM errors (HP-UX)
Occasionally, on a busy system, especially one with many partitions, you may see errors, such as
the following:
ERROR: The following low-level WBEM error occurred:
Empty HTTP response message.
or:
ERROR: The following low-level WBEM error occurred:
Locking or unlocking the target failed.
These errors result from contention for system resources from the various partitions in the complex.
If you see these messages, retry the Instant Capacity operation.
Restarting OA updates old audit snapshot information
Active OA continues to have the old hardware resource information even after the memory and
processors are replaced or repaired. In this case, restarting OA is necessary to update the audit
snapshot information.
Creating a codeword for upgrading Superdome 2 from 16-socket to 32-socket
You need to execute icapstatus -s either from OA or HP-UX on the 16-socket system prior to
the hardware upgrade and create an upgrade codeword on the iCAP portal http://www.hp.com/
go/icap/portal. By clicking Upgrade Codeword, you can launch the Create Superdome 2
codeword for 16-socket to 32-socket Upgrade wizard.
You need to apply the upgrade codeword after the physical upgrade task.
GiCAP Known problems (HP-UX)
Resolving errors during addition of a standby GM
While adding a standby GM there is a possibility of certificate exchange failure
nl
for the Superdome 2 members. This can be resolved by re-adding the member to the GM.
Negative sharing rights value in icapmanage -s output
If icapmanage -s reports sharing rights value after a seize operation is performed on one of
the members or otherwise, execute icapmanage -s on the GM.
Inconsistent values reported by icapmanage during rapid updating
If the command icapmanage -s is executed while the group is being rapidly updated (for
example, during gWLM load balancing), the number of loans and borrows assigned to each
member may not add up in a consistent manner. This is because the status reporting checks with
each member in turn, and if resources are simultaneously being reassigned between group members,
the reporting may reflect an intermediate state. If this occurs, reissue the status command when the
group is in a quiescent state.
12 HP Instant Capacity support 10.x Release Notes