Special Considerations
Implications of Removing a Cell from an Instant Capacity System
Table | Removing a Cell — Decrease Inactive Processors | |||
|
|
|
| |
State | Partition | Partition | Notes | |
(Cell) 0 | (Cell) 1 | |||
|
| |||
|
|
|
| |
Before Cell 0 is | 2 active | 2 active | 4 inactive processors expected (in | |
Removed | 2 inactive | 2 inactive | compliance) | |
|
|
|
| |
After Cell 0 is | 0 active | 2 active, | 4 inactive processors expected (out of | |
Removed | 0 inactive | 2 inactive | compliance) | |
|
|
|
|
In the above example, because the removed cell causes the complex to be out of compliance, temporary capacity begins to be debited at the rate of two
Temporary Instant Capacity (TiCAP) allows for increased capacity, even in the presence of a cell hardware failure, which necessitates the removal and repair of a cell. Removal of a cell, followed by a reboot of the partition it was assigned to, results in a maximal number of active processors in the partition (subject to the configured intended number of active processors), while the maximum number of unlicensed processors are relegated to the removed cell. During the period when the cell is absent, temporary capacity is consumed for each (newly missing) unlicensed processor that was shifted to the removed cell. Having additional Temporary Instant Capacity allows for increased capacity during rare hardware failures that would otherwise not have been possible.
128 | Appendix A |