Implement high-availability solutions with HP Instant Capacity - easily and effectively

30
Appendix
Command reference
The following table provides a reference for various commands used in this paper.
Command Description
icapmodify -d <n>
Deactivate <n> cores and free core usage rights to make them available to another
partition. (Note that even on systems with full usage rights, and thus no inactive
components, you can deactivate cores.)
If the server is currently using TiCAP, using the -d option stops (or reduces)
TiCAP consumption before releasing core usage rights.
icapmodify -a <n> [-t]
Activate <n> cores.
Use the -t option if you want to allow the use of TiCAP in the event core usage rights
are not available.
icapstatus Show iCAP-related details about the current system.
vparmodify -d cpu::<n> -p
<vpar>
Delete <n> cores from the virtual partition <vpar>.
vparmodify -a cpu::<n> -p
<vpar>
Add <n> cores to the virtual partition <vpar>.
icapmanage –s On any Group Manager: show GiCAP-related details about the current system.
icapmanage -x <host>
On an active Group Manager: acquire (seize) core usage rights from the nPartition
containing <host> to make available to other GiCAP group members.
icapmanage -z <host>
On an active Group Manager: restore previously seized core usage rights to the
nPartition containing <host>.
icapmanage -a -S <host>
On an active Group Manager: add a standby Group Manager on <host>.
icapmanage -Q [-n]
On any Group Manager: make (or confirm) this Group Manager as the active Group
Manager for all group members. Use the -n option to suppress attempts to prompt
for passwords in order to exchange SSL keys with members not previously contacted
by the standby Group Manager.
icapmanage –t
Transfer a copy of the GiCAP database from the active Group Manager to a standby
Group Manager.
Summary of usage rights seizure
The following list summarizes various facts about usage rights seizure:
• iCAP OS version 10.05 or later and firmware version 2.51.102 or later can seize usage rights from an unavailable
server and can be used for usage rights seizure even in full disaster recovery—you can seize rights from a group
member even if the entire server is unavailable. In this case, the usage rights seizure expires after 30 days, and the
usage rights will revert to the original partition.
• Only core usage rights can be seized—While GiCAP enables migration of all types of usage rights between member
servers (cores, memory), seizure from a failed server is only for core usage rights. Note that if memory usage rights
are needed, partitioning tools such as the parmodify command can be used either remotely or on an accessible
partition to remove one or more blades from the downed partition, making usage rights available.