Implement high-availability solutions with HP Instant Capacity - easily and effectively
9
Figure 4. HP TiCAP example before failure
Now, imagine that a failure on Sys1 incapacitates the server, forcing a move of existing workloads to Sys2. To handle the
new workload requirements in the partition 2 on Sys2, you activate the 12 inactive processor cores using TiCAP by
specifying the -t option to icapmodify:
Sys2> icapmodify -a 12 -t
OR
OA> icapmodify –p 2 –a 12 –t
You can also preconfigure iCAP to use TiCAP if necessary by running icapmodify –T on the HP Onboard Administrator
(OA). You can run icapmodify –a without the –t operation, and iCAP will use temporary capacity if required.
These cores remain active until they are deactivated. As three units of TiCAP were originally purchased, this is sufficient
for 7.5 days of operation with all 12 cores active. You can also purchase and apply additional TiCAP for Sys2 if needed. (If
the TiCAP balance goes negative and the cores remain active, the server is out of compliance with the iCAP contract.)
The iCAP software decrements the available TiCAP balance every 30 minutes, based on the number of cores using TiCAP.
Figure 5 shows the state after running it for one day in failover mode.
2 blades, 4 active
cores (12 iCAP), 3
units of TiCAP
2 blades, 16 active
cores
SD2 – Sys1 SD2 – Sys2
A A
A A
A A
A A
A A
A
A
A A
A A
A A
A A
90 days
A
Active core
Inactive (iCAP) core