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

HP-UX Handbook – Rev 13.00 Page 13 (of 24)
Chapter 16 Instant Capacity (iCAP)
October 29, 2013
the newly activated core as available for processing. It is recommended to restart the application
in this case.
Temporary capacity activations are persistent. You need to deactivate cores to stop consumption
of temporary capacity. The core deactivation does not need to be on the same partition as the one
where they have been activated. If temporary capacity is depleted and still more cores are active
than usage rights are applied, during the next reboot of any partition in the complex software will
automatically deactivate cores in order to bring the system into a state closer to compliance. If
there is a negative balance of TiCAP the exception information is also written to the
/var/adm/syslog/syslog.log file.
To get a notification before TiCAP is deleted, a warning period may be specified with the
command:
# icapmodify -w <warning period in days>
By default an expiration reminder is send 15 days before TiCAP is projected to expire.
If the TiCAP balance should be listed on the iCAP portal, e-mail connectivity to HP needs to be
configured. The listed amount of available TiCAP time is decreased in amount of 30 minutes per
activated core – after the time is consumed.
If you shut down a partition for 12 hours or more, it should be powered off or deactivated to
avoid additional charges. To power off the partition, execute the PE command from the system
MP.
On HP-UX systems, always use the shutdown -R -H command when shutting down or rebooting
an Instant Capacity partition. If the partition is already shut down, use the “rr” command from
the system MP to reset cells for reconfiguring.
Global Instant Capacity – GiCAP
With GiCAP capacity can be shared not only within a complex but within a group of servers. It
also provides pooled TiCAP time across the group. A Global Instant Capacity (GiCAP) group
consists of a list of server and/or complexes that are allowed to share Instant Capacity usage
rights (for cores, cell boards, and memory) and temporary capacity.
For each group, an HP-UX system must be designated as the Global Instant Capacity Group
Manager, which is the system that maintains information about the group, group resources and
the grouping rules. A GiCAP Group is managed using the icapmanage command. The system
running the Group Manager does not need to have any iCAP components nor does it need to be a
partitionable system. A Group Manager cannot run on a virtual machine guest. The system must