HP Instant Capacity Version 10.x User Guide (5900-2170, January 2012)

The enforcement methods used by the software include:
• Not allowing activations that cause the system to be out of compliance
• Deactivating cores at boot time:
Automatically deactivate cores at boot time if temporary capacity is exceeded and the
number of active cores continues to exceed the number of core usage rights for the
complex (see “TiCAP expiration and compliance enforcement” (page 61)).
◦
◦ Prevents a virtual partition from booting if the number of assigned cores is greater than
the number of intended active cores for the nPartition (see “Boot time compliance”
(page 48)).
• For GiCAP members in a running (booted) virtual partition environment, if the number of
assigned cores is greater than the number of intended active cores, the icapmodify command
may be disallowed. In this case, to bring the vPar database into compliance, deactivate cores
using the vparmodify command.
• On OpenVMS systems, the ICAP_SERVER process dynamically deactivates active cores that
exceed the number of core usage rights for the complex.
Configuration change notification
Specifying an increase or decrease in the number of active cores (using the icapmodify command)
causes a core configuration change. An email notification is sent to the system contact when a
change occurs that affects the configuration of cores.
If you do not want an email notification to be sent when configuration changes are made, disable
this feature by using the following command on HP-UX systems:
/usr/sbin/icapnotify -n off
Example 1 shows a configuration change email notification the iCAP software sends to the system
contact. Note that if the operation is a deferred configuration change, “previous” and “current”
show equal values; only the value for “Number of cores to be active after reboot” reflects the
requested change.
Configuration change notification 29