User's Manual

Table 8-2 Use Case 1 — Configuration of Complex After Core Migration
Total Active CoresTotal CoresPartition
1016nPar3
48nPar4
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 8-3 contains initial configuration of Complex1.
Table 8-3 Use Case 2 — Initial Configuration
Total Active CoresTotal CoresPartition
1216nPar1
1016nPar2
Table 8-4 contains Initial configuration of Complex2.
Table 8-4 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-5 Configuration of Complex1 post core migration
Total Active CoresTotal CoresPartition
1416nPar1
1116nPar2
134 Using Instant Capacity on HP Integrity Superdome 2