HP Instant Capacity Version 10.x User Guide (762794-001, March 2014)

Table 4 Use case 1 — Initial configuration
Total Active CoresTotal CoresPartition
1216nPar1
28nPar2
Core migration from nPar1 to nPar2 can be done as follows:
In nPar1:
# icapmodify –d 2
10 cores are intended to be active and are currently active.
In nPar2:
# icapmodify –a 2
4 cores are intended to be active and are currently active.
IMPORTANT: To remain in compliance, you must perform the deactivation operation first.
Core migration between the partitions is now complete.
Configuration of Complex after core migration:
Table 5 Use case 1 — Configuration of complex after core migration
Total Active CoresTotal CoresPartition
1016nPar1
48nPar2
IMPORTANT: The total number of active cores in the complex must not change at the end of this
operation.
Core migration across complexes (GiCAP)
Consider two complexes, complex1 and complex2 each with 2 partitions. The partitions nPar1
and nPar2 are contained in complex1; nPar3 and nPar4 are contained in complex2.
Table 6 contains initial configuration of Complex1.
Table 6 Use case 2 — Initial configuration
Total Active CoresTotal CoresPartition
1216nPar1
1016nPar2
Table 7 contains Initial configuration of Complex2.
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 want to reduce the active core count. In this use case,
we have chosen nPar4.
In nPar4:
92 Using iCAP on HP Integrity Superdome 2