Technical data

HP Instant Capacity on Demand (iCOD) for nPartitions
iCOD Requirements for nPartition Servers
HP System Partitions Guide: Administration for nPartitions—rp7410
EMSP—[e-mail]
314
iCOD Requirements for nPartition Servers
HP’s iCOD software has the following requirements and restrictions for
using and managing iCOD processors in an nPartition server complex.
• Each nPartition server complex can optionally be under either an
iCOD Purchase contract or a pay per use (iCOD Utility) contract.
In a server complex that is under one of these contracts, the
appropriate software must be installed in the complex’s nPars to
support the contract.
HP does not support mixing iCOD Purchase and iCOD Utility
nPartitions in the same server complex.
• nPartition servers that are under an iCOD Utility contract (a pay per
use “PPU” contract) are required to have iCOD Utility software
installed and running on every HP-UX instance in the complex.
In other words, each nPartition in the complex must have the iCOD
Utility software installed on all potential boot disks for the nPar.
NOTE Where multiple devices are configured for an nPar (for example, the
PRI, HAA, and ALT boot paths), each device must have iCOD Utility
software installed.
• Each nPartition that is under an iCOD Purchase contract must have
iCOD Purchase software installed to enable additional processors to
be activated (or to deactivate processors).
In an iCOD Purchase complex, you do not have to install iCOD
Purchase software on the nPars that are not under an iCOD Purchase
contract. However, in this situation HP recommends that all nPars
have iCOD Purchase software installed to allow administrators to
perform “load balancing” across nPars should the need to do so arise.
NOTE All potential boot disks for nPars with iCOD processors must have the
iCOD Purchase software installed, including any alternate boot
devices.
HP Restricted / DRAFT
DRAFT NOV 2001