HP Instant Capacity User's Guide for Versions 8.x
includes cores in inactive cells and deconfigured cores.
When using versions of vPars before A.03.05, bound
processors at the time the local virtual partition booted, if
unbound later, cannot be instantly assigned to the local
virtual partition without an intervening reboot (and
assuming usage rights are available).
Information displayed for the local nPartition
The following status is displayed when icapstatus is run on a hard partition. Much of this
information is also displayed when icapstatus is run on a virtual partition, except as otherwise
specified. Note that some of the displayed information pertains specifically and only to the local
hard partition (such as the “number of active cores” or “number of inactive cores”). However,
because usage rights and temporary capacity are always calculated globally across the entire
complex, other local values involving these items (such as “can be activated” or “could be
activated” values) are the result of calculations using count values across all the partitions. The
heading for this section includes a datestamp showing the date and time the icapstatus
command was issued.
Total number of configured cores: This field displays the number of cores physically present
in the hard partition.
Number of Intended Active cores: This field displays the number of cores requested to be
active for this hard partition; this is the number of cores
that will be activated during a boot operation. Typically,
this is the number that results from the execution of an
icapmodify command. Other commands such as
parmodify and parcreate can also affect this value.
vparmodify does not affect this value.
Number of active cores: This field displays the current number of cores active in
the hard partition.
Number of inactive cores: This field displays the current number of inactive cores in
the hard partition.
Additional cores that can be
activated with current usage rights:
This field displays the number of cores that are
immediately available for activation using existing core
usage rights on the complex. This information is not
displayed on a virtual partition.
Number of cores that could be
activated with additional usage
rights:
This field displays the number of cores that are available
for activation if additional core usage rights were
purchased or additional usage rights were borrowed from
a GiCAP group. These cores are also available for
temporary activation if temporary capacity is available.
This information is not displayed on a virtual partition.
Number of cores that can be
activated with temporary capacity:
This field displays the number of additional cores (beyond
the number allowed by the purchased usage rights or
currently borrowed GiCAP usage rights) that can be
activated using temporary capacity currently available on
the complex. When activating a core using temporary
capacity, icapmodify assumes the core will be active for
at least 30 minutes. Thus, if a complex has a small
temporary capacity balance, it may not be possible to
activate all the inactive cores in a partition using temporary
capacity. Also note that temporary capacity will not be
used as long as there are available core usage rights on the
complex, even if the -t option is used with icapmodify
for an activation. This information is not displayed on a
virtual partition.
164