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

• Core usage rights are always seized from the nPartition, even when the specified host is a
virtual partition.
• Usage rights can be seized from an nPartition only when:
The nPartition is down.◦
◦ Assuming the nPartition is hosting virtual partitions, all the virtual partitions are down.
In either of these cases, rights seizure is the only technique available for migrating core usage
rights from the nPartition.
• Because rights are seized at the nPartition level, when an entire server is unavailable, to seize
all rights from the server, the icapmanage -x command must be run for each nPartition in
the server.
• An nPartition must be unavailable for usage rights to be seized.
Usage rights can be seized only if the partition is unavailable as determined by the ping
command.
• Partial server failure
If, at the time of rights seizure at least one nPartition of the server is still running, iCAP can
make an immediate adjustment to the available core usage rights, and the seized core usage
rights do not have an expiration date. However, because there are other nPartitions running
iCAP software, the unreachable partition might be assumed to be using all cores on cells
configured for that partition, resulting in possible noncompliance or temporary capacity usage.
To avoid this, cells in partitions from which usage rights have been seized should be made
inactive within 12 hours.
• When seizing usage rights from an nPartition that contains virtual partitions:
All the virtual partitions must be down before rights seizure is allowed.◦
◦ Usage rights cannot restored to the virtual partitions before they boot. Otherwise, you
may not be able to reboot certain virtual partitions, depending on the vPars database
definition and the allocation of usage rights among the virtual partitions. Run the restoration
command icapmanage -z specifying any virtual partition of the nPartition from which
rights were seized. Failure to restore usage rights to the virtual partition before connecting
to the Group Manager can leave the virtual partition in a nonbootable state, requiring
additional steps to fix the vPars database before the virtual partitions can be booted.
• If there are multiple VM guests for the hard partition, they will be affected by the reduction of
usage rights. In an HP Integrity VM environment, specify rights seizure only for the VM host,
not the guests.
• The Group Manager must have network connectivity.
If the Group Manager is also unavailable, and a standby Group Manager is not defined, it
is not possible to transfer usage rights to a standby server.
For additional information about rights seizure, see the Implement high-availability solutions—easily
and effectively on HP-UX white paper available at:
www.hp.com/go/hp-icap-docs
Considerations for multiple groups
You can create multiple GiCAP groups, and they can be managed by the same Group Manager
or by different Group Manager systems. Note that if a Group Manager has an associated standby
Group Manager, the standby Group Manager functions as a standby for all the groups managed
by that Group Manager.
84 GiCAP