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

IMPORTANT: 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. For information about the shutdown command, see
shutdown(1M).
On OpenVMS systems, always use the sys$system:shutdown.com command procedure when
shutting down or rebooting an Instant Capacity partition.
Although a deferred activation does not immediately change the number of active cores, the
intended active value is changed. This change does affect compliance checking, even before the
partition reboot occurs. In particular, compliance checking is calculated as if the activation had
not been deferred.
IMPORTANT: On OpenVMS Instant Capacity systems, HP strongly recommends that you activate
cores using the icapmodify or the ICAP SET command. The use of the START CPU command
on an Instant Capacity system can result in unintended consequences, such as a reduction of
available temporary capacity. Another unintended side effect might be the adjustment in core
usage across the complex, depending on the intended core settings on the partition where the
START CPU command was issued.
To activate one or more inactive cores, use the icapmodify command as root. For more
information about this command, see icapmodify((1M)).
Constraints
The Instant Capacity software does not activate cores that are marked for deconfiguration. Also,
you cannot use Instant Capacity to activate more cores than are configured in the current nPartition.
If you want more cores, you must modify the nPartition with the parmodify command. You can
use Instant Capacity to activate more cores than are configured into the current virtual partition,
but only if the associated nPartition contains enough unassigned cores and the virtual partition
allows enough additional cores to fulfill the request . Otherwise, use the parmodify command
to reconfigure the nPartitions, or use the vparmodify command to remove cores from other virtual
partitions within the same nPartition (essentially adding to the unassigned pool).
Example Core Activation Session
Example 4 shows how to activate an additional core in an nPartition environment. At the beginning
of this activation session, there are a total of 4 cores in the partition; 2 cores are activated and 2
are inactive, but usage rights have been acquired to activate at least one inactive core. In this
example, 1 additional core is activated, leaving the partition with 3 active cores and 1 inactive
core.
Example 4 Activating an Additional Core (HP-UX)
> /usr/sbin/icapmodify -a 1 "Add CPU for new FY: Bill P."
3 cores are intended to be active and are currently active.
In this example, note the following:
• The core activation is instant (that is, a reboot is not required).
• The double-quoted text serves as an audit trail of why the activation was done and who
performed it. This information is optional and is written to the Instant Capacity log file (var/
adm/icap.log) if provided.
42 Using Instant Capacity to Manage Processing Capacity