Instant Capacity (iCAP) Glossary (May 2010)

• iCAP Cell Board with Memory iCAP Cell Boards contain processors and memory modules, all of
which are iCAP. When the Cell Board is activated, all memory on the Cell Board must also be
activated. Each active cell must also have at least one active core, so Usage Rights for one
processor core may need to be purchased if there are not enough existing core Usage Rights to
balance across all of the active cells in the system.
• Temporary Instant Capacity (TiCAP) An optional product layered on top of iCAP Processor
Cores. Allows you to turn iCAP processor cores on active cells on and off for 30 days until the
TiCAP Balance is consumed. How quickly TiCAP is consumed depends on how many cores are
activated and for how long: 1 core can be turned on for 30 days, 2 cores for 15 days, etc.
Accounting is in increments of 30 minutes. TiCAP includes temporary HP-UX Operation
Environment LTUs and HW/SW support. TiCAP can be likened to a prepaid phone card – and,
just as you need a phone to use a phone card, you need iCAP Processors before you can use
TiCAP.
• TiCAP Balance The amount of unused TiCAP time on a server. iCAP Processor Cores can be
activated as long as the TiCAP Balance is above zero. Once the TiCAP Balance is consumed, the
Customer is obligated to either apply more TiCAP to the system or shut the offending processor
cores off. If the cores are not shut off, the system will accrue a negative balance and the
offending cores will be deactivated at the next reboot. The Customer is then responsible for
clearing the negative balance either by purchasing the required amount of TiCAP.
• Instant Access Capacity (IAC) 5 processor core days of Temporary Capacity included with each
iCAP core sold after July 2006. For example, if a system was purchased with 10 iCAP cores, it
would include 50 days of IAC. IAC must be retrieved from the iCAP Portal and applied to the
system to be available for use.
• Global Instant Capacity (GiCAP) Allows Usage Rights to be borrowed from Active Hardware and
lent to iCAP Hardware within a group of servers. This equates to deactivating Active Hardware in
one server and then activating iCAP Hardware in another server. The total number of active
components always remains the same; it is simply the location of those components that
changes. For example, the Usage Rights for processors in a failed partition can be moved to a
backup partition in another server and used to activate iCAP cores. The application can then be
migrated using Serviceguard. GiCAP has excellent applications for disaster recovery, high
availability and load balancing and also offers the ability to pool TiCAP as a way of easily
managing one TiCAP balance for an entire group of servers.
• GiCAP Group Manager This HP-UX server creates and manages GiCAP Groups, and controls the
borrowing and lending of Usage Rights between Group Members.
• GiCAP Grouping Rules Downloaded from the Utility Pricing Solutions Portal and applied to the
GiCAP Group Manager, these rules dictate which servers can be grouped together and share
Usage Rights.