Maintaining iCAP Compliance on HP Integrity & HP 9000 Mid-range & Superdome Servers

5
required on nPar 1 to bring Complex 1 as close to compliance as possible (minimum of 1 core
per cell). In this case only 1 core will be activated in nPar 1 (the minimum required for a single
cell nPar). In this condition the vPar on nPar 1 will not be able to boot up as the minimum
required 4 cores are not available. Note that TiCAP will continue to be consumed for 1 core
as the number of Inactive Cores in the complex is 7 which is one less than the number of
Cores without Usage Rights of 8. This state is shown in the figure below
Best Practices To Ensure Compliance, Manage TiCAP
Balance, and Create nPARS on an iCAP System
• If there are any iCAP cores on the complex, make sure that the number of Inactive Cores in the
HP-UX/OpenVMS partitions is greater than or equal to the number of iCAP cores in the
complex.
• Ensure that partitions in an iCAP system are shutdown correctly by using the -R -H option.
• For the first 12 hours that a partition is at any of the conditions (as defined in the section titled
“iCAP boot time compliance enforcement with respect to iCAP cores”) where all cores can be
counted as active there is no decrementing of TiCAP balance. As soon as the 12 hours are
over and if the partition is still in any of the conditions above, TiCAP balance may
subsequently be deducted while the situation remains unresolved. Make sure that the situation
is rectified within 12 hours.
• Ensure that cimserver and icapd daemons are running on all nPars and vPars in an iCAP
system.
• By default the iCAP software will send expiration reminder when the temporary capacity
balance is projected to expire within 15 days or less. The icapmodify command with the -w
option can be used to adjust the warning period for more advance notice of TiCAP
consumption.
• Hardware failures are uncommon. In the event of a cell board hardware failure the best
option is to replace the failed cell board as soon as possible and return the system to a
compliant state.
• When removing hardware from an iCAP system, ensure that there are enough Inactive cores
on the remaining hardware to cover the expected iCAP inventory for the system. Replace the
removed hardware as soon as possible.
• In the event of vPar database lock, boot into nPar mode and use vparmodify/vpardelete
as appropriate to repair the vPar database so that the total assigned core count "fits" within
nPar 1
1 Active Cores
7 Inactive Cores
vPar unable to boot
nPar 2
(at EFI or BCH
prompt)
8 Active cores
Complex 1
Total # of cores in Complex 1 = 16
# of Cores with Permanent Usage Rights = 8
# of Cores without Usage Rights (CWuR) = 8
# of Inactive Cores = 7
# of Active Cores = 1 + 8 (assumed) = 9