HP Instant Capacity Version 10.x User Guide (762794-001, March 2014)

There must be no intervening blanks within a hostlist, and
if both add and remove lists are specified, the entire string
must be contiguous.
-i Install a grouping rules file on a Group Manager system.
-m
<member_name>:<host>[,<host>]...
Add a member (a partitionable complex) to a group, with
name member_name. Specify an OS instance (host) for
each nPartition or virtual partition of the complex (do not
specify virtual machine or guest OS instances).
A member of a group must encompass all nPar and vPar
OS instances of a complex, and each OS instance specified
as a host must be accessible, (ping-able) for the command
to succeed. When you first add a member to a group, you
are prompted for the root password for each specified host.
The password is used for initial communication only and is
not saved or stored.
If you are using the HP Virtual Server Environment (VSE), it
may be helpful to define the member_name to be the same
as the VSE complex name (which includes the serial number).
A member complex can be added to a group if it is not in
an exception state, if there are enough GiCAP sharing rights
available to match the number of cores without usage rights
on that complex, and if the complex's hardware is
compatible with the grouping rules and with the other
members of the group.
-m <member_name> Specify the member name when removing a member from
a GiCAP group.
-n Prevents icapmanage -Q from attempting to exchange
SSL keys with member hosts which the new active Group
Manager cannot contact. This option allows icapmanage
-Q to be issued from a script without the script having to
deal with the possibility of root password prompts. If -n is
specified and there are member hosts which the active group
manager cannot contact, the active manager is not able to
use those hosts for GiCAP operations. If a GiCAP group
member is not a host, which the active manager can contact
then that member is not allowed to participate in the GiCAP
group.
-r Remove a member from a group, remove a GiCAP group,
or remove a system from use as a standby Group Manager.
When used with the -m option to specify the member name,
removes that member from a GiCAP group. To remove a
member, at least one host defined for the member must be
up and the Group Manager must be able to contact it. (To
avoid potential problems, the Group Manager should also
be able to contact any standby manager that is defined.)
Note that a member cannot be removed from a group until
any borrowed usage rights are returned to the group and
any loaned usage rights are returned to the member.
Removal of a member from a group releases sharing rights
and makes them available for future use.
154