HP AlphaServer Systems instant Capacity on Demand (iCAP) Notes for Installation and Use

Installation and Use with the Tru64Unix Operating System 1-1
Chapter 1
Installation and Use with the Tru64 Unix
Operating System
1.0 Introduction
iCAP systems contain two types of CPUs, those that are purchased initially
with the system, and those that can be made available as processing
requirements grow. This document provides information about installing iCAP,
bringing additional iCAP CPUs on line, designating CPUs as spares, loaning
iCAP CPUs to the system, and purchasing iCAP CPUs for full use. You must be
root or have the appropriate privileges to perform these tasks.
Please note the following restrictions:
• iCAP runs on Tru64 UNIX Version 5.1B* + PK4 or later.
• iCAP software and the associated SMP licenses must be installed on all
systems that have iCAP CPUs.
1.1 Configuration
When you install the iCAP software, all the CPUs on the system are in the
online state. This includes the CPUs that are purchased initially with the
system, as well as the additional CPUs that are reserved for future demand.
Use the iCAP software to configure the system by designating the iCAP CPUs
and setting them to the offline state.
You must include as active CPUs the primary CPU, and either the CPUs
responsible for managing hardware interrupts, or the CPUs being used by one
or more applications, or both when configuring iCAP.
For ES47, ES80 and GS1280, an inactive iCAP CPU cannot be connected to
either internal I/O (ES47 & ES80) or an external I/O Building Block Drawer.
1. ES47 & ES80: One CPU on the iCAP Dual CPU Building Block Module
must remain active, and the active CPU must be the one connected to the