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

Table 7 Use Case 2 — Initial Configuration
Total Active CoresTotal CoresPartition
1016nPar3
88nPar4
Core migration from complex2 to complex1 may be done as follows:
Choose a partition(s) in complex2 where you would like to reduce the active core count. In this
use case, we have chosen nPar4.
In nPar4:
# icapmodify –d 3
5 cores are intended to be active and are currently active.
The usage rights obtained from complex2 can be distributed among the partition(s) of complex1.
In this use case, we distribute it among nPar1 and nPar2.
In nPar1:
# icapmodify –a 2
14 cores are intended to be active and are currently active.
In nPar2:
# icapmodify –a 1
11 cores are intended to be active and are currently active.
Core migration between the complexes is complete.
IMPORTANT: To remain in compliance, you must perform the deactivation operation first.
Table 8 Configuration of Complex1 post core migration
Total Active CoresTotal CoresPartition
1416nPar1
1116nPar2
Table 9 Configuration of Complex2 post core migration
Total Active CoresTotal CoresPartition
1016nPar3
58nPar4
IMPORTANT: The sum of total number of active cores in the complexes involved in core migration
must not change at the end of this operation. In the above example, the sum of the total active
cores in the complexes is 40 (22 in complex1 and 18 in complex2). It must remain same after the
core migration.
Temporary Capacity (TiCAP)
The Instant Capacity (iCAP) software for HP Integrity Superdome 2 maintains temporary Capacity
(TiCAP) balance for each partition in the complex separately. Therefore, the temporary capacity
balance bought from the portal needs to be distributed among the partitions of a complex as
required .
Sample Scenario
Consider a complex with 2 partitions npar1 and npar2 . If 30 days (43200 minutes) of TiCAP is
bought from the portal, it can be distributed among the partitions in the complex as shown in the
example below:
Temporary Capacity (TiCAP) 95