HP Instant Capacity support for HP Integrity Superdome 2 with Dynamic Cores - Release Notes (5900-3370, December 2013)

Strictly correct email address must be set with icapmodify -c
From the complex firmware bundle 3.6.48, an email address with an FQDN needs to be specified
using the format icapmodify -c <contact_email_address>. If you manage to remove the
configured email address and do not want to disable the alert mail functionality, then press the
OA reset button.
Re-adding members may fail after GM OS SSL certificates are renewed
If SSL certificates are renewed with GiCAP_OA_keygen on GMs after removing members for any
reason, you must restart the member OAs before re-adding the members. If multiple OAs are
specified for a member, both OAs must be restarted, without which the member additions will not
work.
Performance improvement in 10.08.01.07 release
The performance changes that are a part of the 10.08.01.07 release are targeted at GMs running
on HP Integrity servers. As of the 10.08.01.07 release, they are partially beneficial to users who
have GM on HP 9000 servers. It is recommended that users upgrade their GM to HP Integrity
systems or wait till the same is available for HP 9000 servers too.
Known problems
Error generated during partition reboot
In HP Integrity Superdome 2 with Dynamic Cores, when partitions are managed with TiCAP turned
ON, and if one or more of the partitions goes down, the RTUs associated with the partitions are
freed up by iCAP and are available for use in other partitions. This may lead to errors while booting
the partitions that are down.
This problem can be solved by using TiCAP to boot up the partition. Use the command icapmodify
–T on to turn on the TiCAP pre-authorization flag on OA. See the TiCAP pre-authorization usage
matrix, in the HP Integrity Superdome 2 with dynamic cores chapter in HP Instant Capacity 10.x
User Guide.
Command timeout
When a command timeout occurs while executing icapmodify -a or -d,
nl
there can be a mismatch between Intended Active and Actual Active values. You must execute
icapmodify -s to correct this mismatch.
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:
Known problems 11