HP-UX HB v13.00 Ch-16 - iCAP

HP-UX Handbook – Rev 13.00 Page 17 (of 24)
Chapter 16 Instant Capacity (iCAP)
October 29, 2013
TiCAP for GiCAP systems:
Temporary capacity can be shared across servers for better efficiency and ease of use.
Temporary capacity within a GiCAP group is always available to all members of a group without
the need to purchase temporary capacity for each server. You can exercise some control over
how “willing” each GiCAP member system is to share temporary capacity by setting its
“temporary capacity warning period”.
Initially, only 30 minutes of temporary capacity are transferred per core activated with temporary
capacity. Every 30 minutes the daemon determines whether temporary capacity is depleted and
acquires more from the group as needed.
iCAP In a Virtual Partition Environment
The minimum required versions of vPars software for HP-UX systems are as follows:
 HP-UX 11i v1: vPars version A.03.05
 -UX 11i v2: vPars version A.04.01
 -UX 11i v3: vPars version A.05.01
Each of these versions provides a virtual partition environment which is tightly integrated with
Instant Capacity, making it less likely for a complex to be misconfigured or to violate contractual
compliance.
The Instant Capacity software must be installed on all virtual partitions in an Instant Capacity
system.
Cores that are not assigned to any virtual partition are considered inactive. Unassigned cores can
be assigned (activated) or deassigned (deactivated) using either the icapmodify command or the
vparmodify command:
 When usage rights freed by deactivating cores are to be used in a different nPartition, use
the icapmodify command.
 When usage rights freed by deactivating cores are to be used by another virtual partition
within the same nPartition, use the vparmodify command.
The vparmodify command does not change the value for the number of intended active
cores for the nPartition.
Deferred activations and deactivations are not supported in any vPar environment.