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

All the commands continue to work from OA command line interface. For more information about
commands, see Chapter titled iCAP HP-UX Manpages for HP Integrity Superdome 2 with Dynamic
Cores in the HP Instant Capacity Version 10.x User Guide
TiCAP
For more information about TiCAP, see Section titled HP Integrity Superdome 2 with Dynamic Cores
in the Chapter titled Using iCAP on HP Integrity Superdome 2 in the HP Instant Capacity Version
10.x User Guide
GiCAP
NOTE: In legacy machines, TiCAP usage information used to be logged in the partition but in
HP Integrity Superdome 2 system this TiCAP usage information is logged in the OA syslog, which
is not normally accessible by the user.
Setting up GiCAP environment
For more information about GiCAP, see Section titled HP Integrity Superdome 2 with Dynamic
Cores in the Chapter titled Using iCAP on HP Integrity Superdome 2 in the HP Instant Capacity
Version 10.x User Guide
NOTE:
• GM(Group Manager) and OA of the member complexes in GiCAP group must be able to
establish a TCP connection initiated by either of them when necessary.
• Communication occurs only between GM and OA through SSL certificates, and the partition
details are hidden from Group Manager.
• Communication occurs through Port 5989, 80, and 7, so these ports must be open on any
firewalls between the GM and OA.
• Communication occurs between OA and DNS if OA is configured to resolve the IP addresses
for GMs.
• The CIM Server configuration property sslClientVerificationMode must be set to optional
and enableHttpsConnection must be set to true on all GiCAP Group Managers and OS
instances of all the member systems.
• While adding HP Integrity Superdome 2 systems (member systems) to a GiCAP group, the
host name of both the Active Onboard Administrator and Standby Onboard Administrator
can be given in same order shown in the following command:
icapmanage -a -m member_name:active_OA,standby_OA -g group_name
NOTE: Here Standby Onboard Administrator is optional.
• When dual OA is configured with GM and the Active OA fails to respond, but standby OA
is reachable, icapmanage -x might fail. Since active OA is not actually down, but its network
is not reachable, standby OA will not takeover automatically. To recover from this situation
user has to execute “force takeover ”on standby OA.
8 Instant Capacity support for HP Integrity Superdome 2 with dynamic cores release notes