HP Instant Capacity Version 10.x User Guide HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3 (5900-3361, December 2013)

Adding members to GiCAP groups
After the GiCAP group is created, you can use the following command to add the HP Integrity
Superdome 2 systems to the group:
icapmanage -a -m <member_name>:<oa_hostname> -g <group_name>
You can specify the host name of both the Active Onboard Administrator and Standby Onboard
Administrator to improve the high availability:
icapmanage -a -m <member_name>:<active_OA_hostname>,
<standby_OA_hostname>, -g group_name
In this case, the ENCLOSURE_IP_MODE value needs to be disabled on the member Onboard
Administrator.
NOTE:
1. The group must already exist.
2. While adding legacy systems, hostnames of all partitions must be specified in the hostlist.
But, while adding HP Integrity Superdome 2 systems, only the hostname of the Onboard
Administrator has to be specified.
3. The group name and member name must have a maximum of 127 characters. And these
names must not contain any special characters except hypen (-), underscore (_), dot (.), and
space ( ).
After you run the command, you are prompted to enter the password for users Administrator and
active_gm on the OA. You must provide a password for active_gm user which will be set on the
OA, as this user is specifically created on OA by the group manager for communication.
IMPORTANT: After the member is added to the group, the user active_gm or the certificate
associated with the user MUST NOT be removed. If the active_gm user or the associate certificate
is removed, communication between the group manager and the group member fails.
The following example shows the addition of an HP Integrity Superdome 2 system to a GiCAP
group.
# icapmanage -a -m complex_abc:complex-oa.yourdomain.com -g sd2
Enter the password for Administrator on complex-oa.yourdomain.com: ******
Enter the password for active_gm on complex-oa.yourdomain.com: ******
Member complex_abc added to group sd2.
If you encounter the error “Could not install member certificate”, you need to remove the member
OA user certificate from the trust store. See the topic Handling errors while re-adding GiCAP
member in chapter 9 for more detail information.
GiCAP resource sharing
Resource sharing within a group containing HP Integrity Superdome 2 systems is same as what is
explained in “GiCAP resource sharing” (page 72) with the following exceptions:
• Cell blade rights are absent.
• Memory usage rights cannot be shared.
Removing a GiCAP group member
The procedure to remove an HP Integrity Superdome 2 system from a group is the same as the
procedure given in “Removing a GiCAP group member” (page 76).
The following example shows how to remove an HP Integrity Superdome 2 system from the group:
# icapmanage -r -m complex_abc
Member complex_abc removed.
HP Integrity Superdome 2 with dynamic cores 113