HP Instant Capacity Version 10.x User Guide (5900-1581, March 2011)

Amount of inactive memory: 16.0 GB
Number of cores without usage rights: 8
Number of inactive cores: 8
The output of the icapstatus command on member2 shows that memory and cell usage rights
are available, along with 1 core usage right:
Instant Capacity Resource Summary
---------------------------------
Number of cells without usage rights: 1
Number of inactive cells: 2
Amount of memory without usage rights: 16.0 GB
Amount of inactive memory: 32.0 GB
Number of cores without usage rights: 7
Number of inactive cores: 8
In this situation, it is not necessary to deactivate components on member2 because the system is
underutilized and usage rights are available. The usage rights from member2 are available to
member1, and the cell can be activated:
member1> parmodify -p 0 -m 2::y:
After a reboot or (on HP-UX 11.31 OEUR 0709 or later) a Cell Online Activation, all of the cell
and memory components on member1 are active.
Global Instant Capacity and Temporary Capacity
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”. No member's temporary capacity balance is decreased below the member's
warning period until all members of the group are within their warning period.
Example: Activation Using Pooled Temporary Capacity
In this scenario, member1 of mygroup has 2 active cores and needs to activate 6 more cores,
but only 5 usage rights are available in the group. There is no temporary capacity available on
member1. Other members of mygroup have a sufficient amount of temporary capacity, so you
can activate the cores using temporary capacity:
member1> icapmodify -a 6 -t
8 cores are intended to be active and are currently active.
Number of cores using temporary capacity: 1
Projected temporary capacity expiration: Less than 30 minutes
Notice that 5 additional cores are permanently activated with the available usage rights, and only
the last core is activated with TiCAP. Initially, only 30 minutes of temporary capacity are transferred
to member1, since 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.
Temporary Capacity and Freed Usage Rights
When a complex consumes temporary capacity, the Instant Capacity daemon periodically
decrements a complex’s temporary capacity balance. Before doing so it contacts the Group
Manager to determine whether there are core usage rights available on other group members. If
not, temporary capacity continues to be consumed. If usage rights are available anywhere in the
group, they are transferred to the complex using temporary capacity in order to stop temporary
capacity consumption on that complex.
80 Global Instant Capacity