Instant Capacity On Demand (iCOD) User's Guide For Versions B.05.x

Instant Capacity on Demand (iCOD)
User’s Guide for versions B.05.x

Fourth Edition
Manufacturing Part Number: B9073-90040

December 2003
United States
© Copyright 2003 Hewlett-Packard Development Company, L.P. All rights reserved.
Legal Notices
The information in this document is subject to change without notice.
Hewlett-Packard makes no warranty of any kind with regard to this
manual, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. Hewlett-Packard
shall not be held liable for errors contained herein or direct, indirect,
special, incidental or consequential damages in connection with the
furnishing, performance, or use of this material.
Warranty
A copy of the specific warranty terms applicable to your Hewlett-Packard
product and replacement parts can be obtained from your local Sales and
Service Office.
Restricted Rights Legend

Use, duplication or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in
Technical Data and Computer Software clause at DFARS 252.227-7013
for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the
Commercial Computer Software Restricted Rights clause at FAR
52.227-19 for other agencies.
Hewlett-Packard Development Company, L.P.
3000 Hanover Street
Palo Alto, California 94304 U.S.A.
Use of this manual and supplied CDs is restricted to this product only.
Additional copies of the programs may be made for security and back-up
purposes only. Resale of the programs, in their present form or with
alterations, is expressly prohibited.
Copyright Notices
Copyright  2003 Hewlett-Packard Development Company, L.P. All
rights reserved. Reproduction, adaptation, or translation of this
document without prior written permission is prohibited, except as
allowed under the copyright laws.
iCOD Software is a product of the Hewlett-Packard Development
Company, L.P. and is protected by copyright.
2
Copyright  1979, 1980, 1983, 1985-93 Regents of the University of
California. This software is based in part on the Fourth Berkeley
Software Distribution under license from the Regents of the University
of California.
Copyright  1988 Carnegie Mellon University
Copyright  1990-1995 Cornell University
Copyright  1986 Digital Equipment Corporation.
Copyright  1997 Isogon Corporation
Copyright  1985, 1986, 1988 Massachusetts Institute of Technology.
Copyright  1991-1997 Mentat, Inc.
Copyright  1996 Morning Star Technologies, Inc.
Copyright  1990 Motorola, Inc.
Copyright  1980, 1984, 1986 Novell, Inc.
Copyright  1989-1993 The Open Software Foundation, Inc.
Copyright  1996 Progressive Systems, Inc.
Copyright  1989-1991 The University of Maryland
Copyright  1986-1992 Sun Microsystems, Inc.
Trademark Notices
UNIX is a registered trademark in the United States and other
countries, licensed exclusively through The Open Group.
3
Publication History
The manual publication date and part number indicate its current
edition. The publication date will change when a new edition is released.
The manual part number will change when extensive changes are made.
To ensure that you receive the new editions, you should subscribe to the
appropriate product support service. See your HP sales representative
for details.
• First Edition: July 2002, 5990-2943,

(iCOD version B.05.00 on HP-UX 11.0 and 11i v1)
web only
• Second Edition: September 2002, 5990-2943,
web, print, and Instant Information CD
• Third Edition: December 2002, 5990-4343,
• Fourth Edition: December 2003, B9073-90040,
(iCOD versions B.05.x on HP-UX 11.0 and 11i v1)
web, print, and Instant Information CD
IMPORTANT New information may have been developed after the time of this
printing. For the most current information, visit the following HP
documentation web site:
docs.hp.com
4
Contents
1. About this guide
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
HP On Demand Solutions Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Software Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Most Recent iCOD Product Version and Supported Platforms . . . . . . . . . . . . . . . . . 14
Past iCOD Versions and Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
iCOD Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
iCOD User’s Guide History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Locating the iCOD User’s Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Locating the iCOD Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Manpages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2. Understanding iCOD Requirements

iCOD Program Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
HP-UX 11.0 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
HP-UX 11i v1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
cron Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
E-Mail Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
E-Mail Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Steps to Confirm or Diagnose E-mail Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 28
Configuring iCOD’s FROM E-mail Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Configuring Your Server to Send but Not Receive E-Mail . . . . . . . . . . . . . . . . . . . . . 30
iCOD System Configuration Information Reported to HP . . . . . . . . . . . . . . . . . . . . . 31
Testing E-Mail Transmission of the Asset Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Roles Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
License Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
iCOD System Move Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
When iCOD Program Requirements End. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3. Installing and Uninstalling iCOD Software

Updating/Installing iCOD Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
How To Find The Latest Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
For HP-UX 11.0 - Installing from the Support Plus CD . . . . . . . . . . . . . . . . . . . . . . . 43
5
Contents
For HP-UX 11i v1 - Installing from the Support Plus CD . . . . . . . . . . . . . . . . . . . . . 44
For HP-UX 11.0 - Installing from the HP Software Depot . . . . . . . . . . . . . . . . . . . . . 44
For HP-UX 11i v1 - Installing from the HP Software Depot . . . . . . . . . . . . . . . . . . . 45
For All Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Reinstalling iCOD Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Preserving current iCOD information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Installing “Golden Images” on a non-iCOD System . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Uninstalling iCOD Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4. Using iCOD to Manage your Processors

Understanding Configuration Change Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Licensing Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Setting Your System Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Checking the Status of your iCOD System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Increasing Processor Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
iCOD Activation Example Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Decreasing Processor Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Deactivation Example Session for Hardware-partitionable Systems . . . . . . . . . . . . 60
Load-balancing Active Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Overriding Deferred Processor Activations and Deactivations . . . . . . . . . . . . . . . . . . . 62
Moving a Cell from one Partition to Another . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Software Application Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Understanding Online vs. Offline Activation Methods . . . . . . . . . . . . . . . . . . . . . . . . . 66
Advantages and Disadvantages of Online Activation. . . . . . . . . . . . . . . . . . . . . . . . . 68
Advantages and Disadvantages of Offline Activation . . . . . . . . . . . . . . . . . . . . . . . . 68
Processor Test Activation on iCOD Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Replacement of Failed Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
In Online Activation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Failed Monarch Processors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
In Offline Activation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Processor Activation or Deactivation Delay with vPars . . . . . . . . . . . . . . . . . . . . . . . . 72
5. Troubleshooting
Correcting Activation Mistakes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Too Many Processors Activated on iCOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Troubleshooting the iCOD Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6
Contents
6. Frequently Asked Questions
iCOD Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Superdome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
7. Temporary Capacity for iCOD Processors

Utilizing Temporary Capacity for iCOD Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Overview of Temporary Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Ordering Temporary Capacity for New iCOD Processors . . . . . . . . . . . . . . . . . . . . . 85
Ordering Temporary Capacity for Existing Systems . . . . . . . . . . . . . . . . . . . . . . . . . 85
Licensing and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Tracking the Purchase and Use of Temporary Capacity . . . . . . . . . . . . . . . . . . . . . . 86
8. iCOD Compatibility with vPars and Psets

iCOD Compatibility with Virtual Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
iCOD Software Compatibility with vPars — Supported Hardware Platforms . . . . . 91
Activation and Deactivation of Processors in a vPar . . . . . . . . . . . . . . . . . . . . . . . . . 92
icod_stat Output Differences in a vPar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Licensing and vPars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Static vPars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
LPMC Deactivations in vPars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
LPMC and icod_stat Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Removal of the iCOD Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
iCOD Compatibility with Processor Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
iCOD Software Compatibility with Psets — Supported Hardware Platforms . . . . . 98
Scope of the iCOD Software Interacting with Psets . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Activation and Deactivation of Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Psets on vPars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
9. iCOD Cell Board

iCOD Cell Board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
iCOD Cell Board — Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Ordering a New System Containing iCOD Cell Board. . . . . . . . . . . . . . . . . . . . . . . 103
HP-UX License and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
iCOD Cell Board Activation Fees. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Activation of an iCOD Cell Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
7
Contents
Accidental Activation of an iCOD Cell Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
A. Offline Configuration and Activation of Processors

Operating in Offline Activation Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Converting Your System From the Default Online Activation Mode to Offline
Activation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Activating a Deconfigured Processor in Offline Activation Mode . . . . . . . . . . . . . . 111
Converting from Offline Activation Mode to Online Activation Mode. . . . . . . . . . . 111
Receiving a System Alert on L-Class and N-Class on Hard Reset . . . . . . . . . . . . . . . 113
Configuring and Activating Processors for the L-Class and N-Class Servers . . . . . . 114
Configuring and Activating Processors for the V-Class Server . . . . . . . . . . . . . . . . . . 120
Configuring and Activating Processors for Hardware-partitionable Systems . . . . . . 126
B. Special Considerations
iCOD and pstat, pstat_getdynamic, and mpctl System Calls . . . . . . . . . . . . . . . . . . . 128
pstat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
mpctl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Affected HP-UX Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Measurement Software on iCOD Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
OpenView Measurement Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Other Measurement Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Differences Between Supported Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
L-, N-, and V-Class Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Hardware-partitionable Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Firmware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
V-Class Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Superdome Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Dynamic Processor Resilience (DPR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Requested Active Processors Below Minimum Required . . . . . . . . . . . . . . . . . . . . . . 135
C. Glossary
iCOD Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
D. iCOD Manpages
iCOD (5) Manpage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
icod_modify (1M) Manpage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
8
Contents
icod_notify (1M) Manpage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
icod_stat (1M) Manpage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
9
Contents
10
1 About this guide
This chapter covers the following topics:
• “Introduction” on page 12
• “Overview” on page 14
• “iCOD Information” on page 16
• “Conventions” on page 18
For more in-depth information, see the manpage icod (5).
Chapter 1 11
About this guide
Introduction
Introduction
Welcome
Welcome to the Instant Capacity on Demand (iCOD) User’s Guide for
versions B.05.x. Hewlett-Packard’s instant Capacity on Demand (iCOD)
software product provides the ability to increase or decrease processor
capacity instantly on (specified) HP enterprise servers. The iCOD
software product is a part of HP’s On Demand Solutions program.
This user’s guide provides you with the most recent information on using
the iCOD versions B.05.x software (versions B.05.00 and B.05.01) to
manage processor capacity in your HP enterprise server.
NOTE All personnel with system administrator access (that is, root login
privileges) to an iCOD system should read and understand the contents
of this document and the implications of activating inactive processors.
HP On Demand Solutions Program
iCOD With iCOD versions B.05.x, you initially purchase a specified number of
activated processors, and pay a right to access fee for a specified number
of deactivated processors. Whenever you activate an additional processor
you are charged an enablement fee.
iCOD versions B.05.x are available for Superdome, rp7410, rp8400, L-,
N-, and V-Class servers.
iCOD Audit HP utilizes an iCOD audit application to track enablement fee payment
Application for any newly activated iCOD processor. The iCOD software monitors all
processors on the system, active and inactive, and sends an encrypted
e-mail message to the iCOD audit application at HP. The iCOD audit
application compares the iCOD system’s processor information against
iCOD shipment and purchase information. The audit application and
iCOD software are capable of auditing the processor configuration for
both on-line and off-line activation modes.
12 Chapter 1
About this guide
Introduction
Pay Per Use Pay per use (PPU) is a pricing model in which you are charged for actual
processor usage. You acquire a specific hardware platform and number of
processors, and are charged for the actual usage, based on the number of
active processors in the complex.
The billing amounts vary as your processor usage needs increase or
decrease. This is different than the traditional financing approaches that
are based on fixed payment amounts for a specified period.
Pay per use is currently available for Superdome, rp7410, and rp8400
servers. It will be available on other HP enterprise servers in the future.
Terminology
icod-purchase The iCOD software and manpages refer to the term icod-purchase. Your
iCOD system displays icod-purchase as the Contract type in the output
from the icod_stat command. The manpages icod(5), icod_modify(1M),
and icod_stat(1M) also make references to icod-purchase.
Throughout the remainder of this document, icod-purchase is referred
to as “iCOD”.
See “iCOD Terminology” on page 138 for commonly used terms with the
HP On Demand Solutions program.
Chapter 1 13
About this guide
Overview
Overview
Software Product Overview

There are two software products associated with HP’s On Demand
Solutions program:
• iCOD: product number B9073AA

• PPU: product number T1322AA
You will find only iCOD versions B.05.x information in this user’s guide.
For information on PPU, see the appropriate Pay Per Use User’s Guide.
The iCOD product has been available on the HP Support Plus media
since March 2000 (version B.01.00).
The iCOD version B.05.01 software can be obtained from the following
HP web site (search for “iCOD”): software.hp.com
Most Recent iCOD Product Version and Supported

Platforms
Table 1-1 Most Recent iCOD Version and Supported Platforms
Operating Supported
Software and
System Hardware Notes
Version
Version Platforms
iCOD HP-UX 11.0 L-, N-, and Available on:

B.05.01 V-Class servers
(B9073AA) • http://software.hp.com
• December 2003 Support Plus
media for HP-UX 11.0
iCOD HP-UX 11i L-, N-, V-Class, Available on:

B.05.01 v1 Superdome,
(B9073AA) rp7410, and • http://software.hp.com
rp8400 servers • December 2003 Support Plus
media for HP-UX 11i v1
14 Chapter 1
About this guide
Overview
iCOD Supported Hardware Platforms

Currently, the iCOD versions B.05.x software is supported on the
following HP servers:
• N-Class: N4000
• L-Class: L2000 and L3000
• V-Class: V2500 and V2600
— V-Class firmware upgrade - V2500/V2600 Test Station Software

Release 3.1 or greater
— only dual processor boards are supported
• Superdome: SD16000, SD32000, and SD64000
• rp7410
• rp8400
Past iCOD Versions and Supported Platforms
iCOD Versions
The iCOD version B.05.01 software supersedes these previous iCOD
software versions:
• B.01.00 (on HP-UX 11.0)
• B.02.x (on HP-UX 11.0 and 11i v1)
• B.03.x (on HP-UX 11i v1)
• B.04.x (on HP-UX 11.0 and 11i v1)
Chapter 1 15
About this guide
iCOD Information
iCOD Information
iCOD User’s Guide History

This is the fourth edition of the iCOD User’s Guide for versions B.05.x.
For versions previous to iCOD B.05.x, the information is contained in the
iCOD/PPU User’s Guide for versions B.04.x.
Locating the iCOD User’s Guide

You can find the iCOD User’s Guide for versions B.05.x in the following
locations:
• For the most recent version of the user’s guide, visit the following HP
documentation web site (search for “B9073-90040”):
docs.hp.com
• Printed (part number B9073-90040) — order from the following HP
Web site:
www.hp.com/products1/unixservers/solutions/icod/index.html
• December 2003 Instant Information CD

• In the iCOD B.05.01 software product, located in:
/usr/share/doc/icodUserGuide.pdf
Note, this is an early version of this document. For more current
information see the documents listed above.
Locating the iCOD Release Notes

You can find the iCOD Release Notes for version B.05.00 in the following
locations/media:
• For the most recent version of the release notes, visit the following
HP documentation web site (search for “B9073-90020”):
docs.hp.com
16 Chapter 1
About this guide
iCOD Information
• Printed (part number B9073-90020) — order from the following HP

web site:
www.hp.com/products1/unixservers/solutions/icod/index.html
• December 2003 Instant Information CD

• In the iCOD B.05.x software product located in:
/usr/share/doc/icodRelNotes.pdf
Note, this is an early version of this document. For the most recent
information see the documents listed above.
Manpages
See Appendix D, “iCOD Manpages,” on page 143 for details of the
following manpages:
• icod (5): an overview of the iCOD commands and their usage
• icod_modify (1M): how to manage processor activity in your iCOD

system, change system contact information, and apply a software
license to use
• icod_notify (1M): how to manage asset notification to HP
• icod_stat (1M): how to display processor status, usage information,

and system information
Chapter 1 17
About this guide
Conventions
Conventions
This guide uses these typographic conventions:
Boldface Words defined for the first time appear in boldface.
Computer Computer font indicates system commands, file
names, and literal items — which may be displayed by
the computer. For example: file not found
User input Bold, computer text indicates literal items that you
type. For example, to change to your HP-UX account’s
home directory, enter:
cd
Italics Manual titles, variable in commands and emphasized
words appear in italics. For example, you would
substitute an actual directory name for
directory_name in this command:
cd directory_name
[ ]and | Brackets [] enclose optional items in command syntax.
The vertical bar | separates syntax items in a list of
choices. For example, you can enter any of these three
items in this syntax:
ls [-a | -i | -x]
Enter Text in this bold, sans-serif font denotes keyboard keys
and on-screen menu items. A notation like Ctrl-Q
indicates that you should hold the Ctrl key down and
press Q.
18 Chapter 1
2 Understanding iCOD
Requirements
• “iCOD Program Requirements” on page 20

• “Software Requirements” on page 21
• “E-Mail Requirements” on page 24
• “Roles Requirement” on page 36
• “License Requirement” on page 37
• “iCOD System Move Requirements” on page 39
• “When iCOD Program Requirements End” on page 40
For more in-depth information, see the manpage icod (5).
Chapter 2 19
Understanding iCOD Requirements
iCOD Program Requirements
iCOD Program Requirements

You must comply with the following HP On Demand Solutions conditions
to participate in the iCOD program:
• Configure iCOD systems/partitions with the capability to send
internet e-mail to the “hp.com” domain (see “E-Mail Requirements”
on page 24 for more information)
• Maintain the HP iCOD software — a non-intrusive and low overhead
software module that resides on the iCOD system
• Migrate to later iCOD software versions as they become available
For the specific details on your individual iCOD program requirements,
refer to your On Demand Solutions contract from HP or your authorized
channel partner. Participants of the On Demand Solutions program who
do not meet these requirements may be in breach of contract. This
results in unnecessary expense for both the iCOD program participant
and HP.
20 Chapter 2
Software Requirements
iCOD systems are required to run the iCOD software which e-mails asset
report information to an audit system located at HP. Your system must
continue to send asset reports, via e-mail to HP, until all program
requirements are fulfilled. Refer to “When iCOD Program Requirements
End” on page 40 for details.
IMPORTANT This document lists the patches required to install and run iCOD
versions B.05.x known at the time of publication. To find the most
current patches, see “How To Find The Latest Patches” on page 42 for
detailed instructions.
HP-UX 11.0 Requirements
For iCOD Versions The following software is required for iCOD versions B.05.x on HP-UX
B.05.x on 11.0:
HP-UX 11.0
❏ iCOD software bundle B9073AA (version B.05.01) located at the
following HP web site:
software.hp.com
❏ HP-UX 11.0 (Extension Pack 9905)
❏ kernel driver diag2
Your iCOD system is shipped with the correct version of HP-UX, the
iCOD software bundle, and the kernel driver diag2. In the event your
system’s operating system is re-installed or installed with Ignite-UX,
ensure that the above software requirements are satisfied. The kernel
driver diag2 is part of standard HP-UX. Since diag2 is an iCOD
software dependency, this driver must not be removed from the kernel.
Chapter 2 21
Required Patches for HP-UX 11.0

The following patches (or superseded patches) are required for HP-UX
11.0 (at the time of publication). All of these patches are available on the
Support Plus media:
• PHKL_22986: S700_800 11.00 pstat() patch
• PHKL_23001: S700_800 11.00 thread_creat() patch
• PHKL_23180: S700_800 11.00 PM patch
• PHKL_25999: S700_800 11.00 umask cumulative patch
• PHCO_22686: S700_800 11.00 top patch
• PHCO_22733: S700_800 11.00 sar patch
• PHCO_21894: S700_800 11.00 vmstat patch
• PHCO_21927: S700_800 11.00 iostat patch
• PHCO_21928: S700_800 11.00 uptime patch
HP-UX 11i v1 Requirements
For iCOD Versions The following software is required for iCOD versions B.05.x on HP-UX
B.05.x on 11i v1:
HP-UX 11i v1
❏ iCOD software bundle B9073AA (version B.05.01) located on the
following HP web site:
software.hp.com
❏ HP-UX 11i v1
IMPORTANT For hardware-partitionable systems (for example, Superdome): The

Utility subsystem firmware must be 6.40 or greater. iCOD is not
supported on versions prior to 6.40. The Utility firmware revision is
displayed in two places by the Management Processor (MP). To
determine your version, check the main menu when you first log into the
MP, or type CM at the main menu to display the command menu, then HE
for help.
Your iCOD system is shipped with the correct version of HP-UX and the
iCOD software bundle. In the event your system’s operating system is
re-installed or installed with Ignite-UX, ensure that the correct version
of HP-UX is used.
22 Chapter 2
Required Patches for HP-UX 11i v1

The following patches (or superseded patches) are required for HP-UX
11i v1:
• PHKL_23154: S700_800 11.11 dflush() patch

• PHKL_25218: S700_800 11.11 PDC Call retry,
PDC_SCSI_PARMS, iCOD hang fix
• PHKL_26232: S700_800 11.11 Psets Enablement patch,
FSS iCOD patch
• PHCO_24477: S700_800 11.11 sar(1M) patch
IMPORTANT If your system runs MeasureWare software, then the following patch is
also required: PHKL_22987: S700_800 11.11 pstat() patch.
cron Configuration Requirements

The iCOD software utilizes the cron job scheduler to send an asset
report, via e-mail, to HP on a daily basis. For details of the asset report,
see “iCOD System Configuration Information Reported to HP” on
page 31. Upon installation of the iCOD software, the following cron
entry is made in the system’s root crontab file:
0 12 * * * /usr/sbin/icod_notify -c </dev/null >/dev/null 2>&1
This entry runs the iCOD icod_notify -c command at 12:00 noon

daily. To verify the cron entry, log in as root and enter the following
command:
/usr/bin/crontab -l
IMPORTANT As a part of the On Demand Solutions program requirements, HP must

receive the iCOD system’s asset report daily, via e-mail. Therefore, the
cron daemon should always be executing. For further information on
cron, see the cron(1M) manpage.
Chapter 2 23
E-Mail Requirements
E-Mail Requirements
The iCOD software sends an encrypted e-mail message, which contains
the iCOD system’s asset report, to an audit system located at HP. See
“iCOD System Configuration Information Reported to HP” on page 31 for
details of the information reported to HP. The e-mail requirements are:
• The iCOD system/partition is required to have sendmail installed

and configured such that it has the ability to send e-mail to the
hp.com domain.
• The domain name in the iCOD FROM e-mail address, for the e-mail
sent from the iCOD system to HP, must be DNS resolvable by HP.
See “Configuring iCOD’s FROM E-mail Address” on page 29 for
details.
IMPORTANT The e-mail is bounced/rejected by the mail servers at HP if the domain

name in the FROM address, for the e-mail sent from the iCOD system to
HP, is not DNS resolvable by HP.
Note that the sendmail configuration and routing may vary, but the
iCOD system must have the ability to send e-mail to the hp.com domain.
The ability to receive e-mail from HP is optional, but you may find it
useful for testing the capability of sending e-mail to HP. For more
information see “Configuring Your Server to Send but Not Receive
E-Mail” on page 30. Refer to the sendmail(1M) manpage for more
information on sendmail.
sendmail is part of the HP-UX core and is installed with the HP-UX
operating system. However, a sendmail configuration process needs to
be followed to complete its installation. For information, refer to the
chapter titled Installing and Administering sendmail, in the appropriate
documentation:
• For HP-UX 11.0: Installing and Administering Internet Services

(B2355-90147)
• For HP-UX 11i v1: Installing and Administering Internet Services
(B2355-90685)
24 Chapter 2
E-Mail Requirements
You can retrieve the above documentation from the HP web site:
docs.hp.com
Select:
Networking and Communications -> Internet Services
to access either of the documents.
On Superdome For Superdome systems all iCOD partitions must be configured to send
Systems e-mail to HP. This is because each iCOD partition reports the processor
information for itself. It is recommended that the e-mail capability be
configured and the iCOD software be installed on the non-iCOD
partitions, as well. This makes it easier for you to later redistribute
processors across partitions (that is, load balance). See “Load-balancing
Active Processors” on page 61 for details.
E-Mail Configuration
Before you Start

Your iCOD system must be network accessible to HP mail servers that
are outside your company's firewalls. If your iCOD system is on an
isolated network, e-mail from the iCOD system does not reach HP. This
causes your iCOD system to be out of compliance with HP’s On Demand
Solutions program.
Sendmail
sendmail is the application used by the iCOD software to send encrypted
mail messages from your system to HP. The sendmail daemon, if
running, can also be used to receive e-mail. For the purposes of this
e-mail configuration, only the ability to send e-mail is required.
Mail applications invoke sendmail to send e-mail. The configuration file,
/etc/mail/sendmail.cf, offers tremendous flexibility.
Chapter 2 25
E-Mail Requirements
Overview of E-mail Routing Across the Internet

When sendmail is invoked, by the iCOD software, to send e-mail to HP,
sendmail determines where it should initially send the e-mail (the first
hop). Mail often goes through multiple systems (hops) before it reaches
the final destination. To determine the first hop for the e-mail, sendmail
uses one of the following:
• The e-mail is routed to a mail relay host if it is configured in the
/etc/mail/sendmail.cf configuration file. This is the easiest
implementation and can be done with just a one line change (DS) to
the default /etc/mail/sendmail.cf file.
Note that the relay host must be configured to properly route
(forward) the mail to the final destination.
• DNS MX records - this method requires that the iCOD system be in
an environment (network) where DNS (Domain Name Server) is
operating and properly configured. sendmail on the system queries a
DNS server for the name of the mail server to forward the e-mail to
(for the first hop) in order for the e-mail to reach the final destination
(hp.com).
In all cases, the following requirements must be met:
• HP’s mail servers receiving mail expect the host (the mail server in
the last hop before reaching HP) to be properly registered in DNS.
Otherwise the HP mail server rejects or “bounces” the e-mail.
• The 'From' field (e-mail address), in the e-mail message, must be
known by the receiving mail server (that is, the hostname is
registered in DNS and advertised on the internet). Otherwise the
receiving mail server at HP rejects the mail. This field in the e-mail
can be configured with a simple one line modification (DM) to the
/etc/mail/sendmail.cf file.
In some DNS environments no changes to the default
/etc/mail/sendmail.cf file may be needed to properly route e-mail
from the iCOD system to HP.
26 Chapter 2
E-Mail Requirements
• In some environments, configuring your iCOD system to properly

send e-mail from the system to HP can require as little as a two line
edit (or none) to the /etc/mail/sendmail.cf file. Configuring mail,
including sendmail and DNS configurations, is usually handled by
the IT team in most organizations.
Example 2-1 Example Edit to Sendmail Configuration (/etc/mail/sendmail.cf)

DMmy_company.com
DSmailhub.my_company.com
This example assumes the following:
• the iCOD system’s hostname is:

myICODsystem.my_site.my_company.com
• the From field of the e-mail is set to my_company.com rather than the
exact hostname of the iCOD system. This is because most
organizations do not advertise the names of their internal servers to
the internet; however, they do advertise a few (select) high level
domain names to the internet.
• the iCOD system is not advertised to the internet but hostname
mycompany.com is advertised and reachable from the internet
• e-mail is forwarded from the iCOD system to a mail relay host called
mailhub. The mail server called mailhub may either be directly
connected to the internet and send the e-mail directly to HP, or it
may forward the e-mail to another mail server on its way to HP.
NOTE Any bounced iCOD e-mail messages are in the adm mailbox.
Chapter 2 27
E-Mail Requirements
Steps to Confirm or Diagnose E-mail Configuration

After you have configured your iCOD system to send e-mail over the
internet you can use the following steps to confirm the e-mail
configuration or to aid in debugging the configuration:
1. Send an e-mail message from your iCOD system to an e-mail address

in the same domain (intranet) and confirm receipt of the e-mail
message.
2. Send an e-mail message from your iCOD system to an e-mail address
outside of your domain (to the internet, for example, to a yahoo or
hotmail e-mail address) and confirm receipt of the e-mail message.
3. Send an e-mail message from your iCOD system to someone at HP
(for example, a HP representative in a local account team) and
confirm the person at HP received the e-mail message.
4. As root, execute the command:
/usr/sbin/icod_notify
This command sends an e-mail message to HP’s audit application.
HP sends a confirmation e-mail message to the iCOD system contact
that is configured for your iCOD system. Receipt of the confirmation
e-mail message confirms successful iCOD e-mail configuration.
28 Chapter 2
E-Mail Requirements
Configuring iCOD’s FROM E-mail Address

One of the e-mail requirements of the iCOD program is that the FROM
e-mail address, on e-mail messages sent by the iCOD software from your
iCOD system to HP, must be DNS resolvable.
The iCOD software uses adm@localhost.domain as the default FROM
e-mail address (where localhost is the hostname of your iCOD system
and domain is its DNS domain). If the default FROM e-mail address is
undesirable, you can configure the iCOD B.05.x software to use a FROM
address you specify.
Configuring a To configure your specified iCOD FROM e-mail address, execute the
Specified FROM following command:
Address /usr/sbin/icod_modify -f from_address
You can verify the configured iCOD FROM e-mail address by using the
/usr/sbin/icod_stat command.
After you have configured a specified FROM e-mail address, the iCOD
software uses it on all subsequent e-mail messages sent from your iCOD
system to HP.
Reverting to the If you have specified an iCOD FROM e-mail address and you want to
Default FROM revert to the default iCOD FROM e-mail address
Address (adm@localhost.domain), execute the following command:
/usr/sbin/icod_modify -f ““
Chapter 2 29
E-Mail Requirements
Configuring Your Server to Send but Not Receive

E-Mail
For security reasons, some organizations do not wish to allow incoming
mail. If you want your iCOD system to be capable of only sending e-mail,
and not receiving e-mail, complete the following configuration procedure:
Step 1. To prevent the sendmail daemon from starting up again when your
system reboots, edit the /etc/rc.config.d/mailservs file, changing
the value of SENDMAIL_SERVER to 0:
vi /etc/rc.config.d/mailservs
#########################################
# Mail configuration. See sendmail(1m) #
#########################################
#
# BSD’s popular message handling system
#
# SENDMAIL_SERVER: Set to 1 if this is a mail server
# and should run the sendmail deamon.
# SENDMAIL_SERVER_NAME: If this is not a mail server, but a
# client being served by another
# system, then set this variable to
# the name of the mail server system
# name so that site hiding can be
# performed.
#
export SENDMAIL_SERVER=0
export SENDMAIL_SERVER_NAME=
Step 2. To immediately stop the server from receiving e-mail, kill the active
sendmail daemon by executing the following command:
/sbin/init.d/sendmail stop
30 Chapter 2
E-Mail Requirements
iCOD System Configuration Information Reported to

HP
The iCOD software sends an asset report, via encrypted internet e-mail,
to HP’s audit application when one of the following events occur:
• the periodic iCOD cron task is triggered

• the iCOD system is booted
• the iCOD system is shut down
• the number of requested active processors is changed
The asset report contains iCOD system configuration information. The
following data is reported to HP:
iCOD Version The version number of the asset
report (formatting)
Client Type The type of contract, either
iCOD-purchase or iCOD-utility
Date The date and time in UTC
(Coordinated Universal Time)
Local Date The local date and time, including the
time zone
Event Type The type of event that caused an
asset report to be sent to HP
Serial Number The serial number of the system
Software ID The software identifier of the system
Hostname The system host name
NIS Domain Name The NIS domain name
Domain Name The fully qualified domain name
Model The model number of the system
Uname Output The HP-UX system information
Total CPUs The total number of physically
installed processors
Active CPUs The number of active processors
Chapter 2 31
E-Mail Requirements
Reply to Contact Status of System Contact’s request

for reply e-mail — if set to “true” (1)
causes HP to return an
acknowledgment e-mail, if set to
“false” (0) causes HP to not return an
acknowledgment e-mail
System Contact Name The name of the person who is the
System Contact (responsible for the
system)
System Contact Phone The phone number of the person who
is the System Contact
System Contact E-mail The e-mail address of the person who
is the System Contact
Configuration If the iCOD system configuration has changed, by the activation or

Change deactivation of processors, the following information is reported as well:
Authorizing Manager Name The name of the manager who is
authorizing the change to the number
of requested active processors
Authorizing Manager Phone The phone number of the authorizing
manager
Authorizing Manager E-mail The e-mail address of the authorizing
manager
System Administrator Name The name of the system
administrator (person) activating or
deactivating the processors
Change Description Text that describes the reason for the
system configuration change
32 Chapter 2
E-Mail Requirements
On Hardware- In addition to the above information, hardware-partitionable systems

Partitionable also report the following to HP (note that all partitions should be
Systems: configured to send e-mail to HP):
Local Partition ID The identifier of the iCOD partition,
that the information in the above
section applies, and through which
the complex information was
obtained
Total Reporting Partitions The total number of reporting
partitions in the complex
Reporting Partition IDs The identifiers of reporting partitions
defined in the complex
Total Inactive Partitions The total number of inactive
partitions in the complex
Inactive Partition IDs The identifiers of inactive partitions
in the complex
Total CPUs in Complex The total number of processors in the
complex including active and inactive
processors
Total Free CPUs The total number of processors in free
cells in the entire complex
Total Partitions The total number of partitions in the
entire complex
Partition The partition identifier, followed by
the total number of processors in the
partition including active and
inactive processors (repeated for each
partition in the entire complex)
Total Cells The total number of cells in the entire
complex
Cell The cell number, partition ID,
Active|Inactive, number of
processors, and gigabytes of memory
(repeated for each cell in the entire
complex)
Chapter 2 33
E-Mail Requirements
HP receives an asset report from your iCOD system. Here is an example

of an asset report sent from a hardware-partitionable iCOD system:
Example 2-2 iCOD B.05.x Asset Report

iCOD Version:5.0
Client Type:iCOD-purchase
Date:01/01/2002 08:00
Local Date:01/01/2002 02:00 MST
Event Type:PERIODIC_SYSTEM_AUDIT
Serial number:USR0000000
Software ID:abcdef
Hostname:par2
NIS Domain name:.
Domain name:par2.corp.com
Model:9000/800/SD32000
Uname Output:HP-UX par2 B.11.11 U 9000/800
unlimited-user
Total CPUs:4
Active CPUs:4
Reply to Contact:1
System Contact Name:A.Contact
System Contact Phone:Number:970-888-9999
System Contact Email:acontact@corp.com
Local Partition ID:0
Total Reporting Partitions:1
Reporting Partition IDs:0
Total Inactive Partitions:1
Inactive Partition IDs:1
Total CPUs in Complex:16
Total Free CPUs:4
Total Partitions:3
Partition:0,4
Partition:1,0
Partition:2,8
Total Cells:4
Cell:0,0,Active,4,16.0
Cell:4,-1,Inactive,4,16.0
34 Chapter 2
E-Mail Requirements
Testing E-Mail Transmission of the Asset Report
NOTE The following procedure assumes your iCOD system is capable of

sending internet e-mail and your system contact information is
configured.
Execute the following command to send your asset report, via e-mail, to
HP:
You should receive an acknowledgment e-mail message from HP
confirming the receipt of your asset report. Use an e-mail client to verify
the acknowledgement e-mail message from HP to the system contact.
The reply should look like the following (note that only
hardware-partionable systems have Local Partition information):
Subject: Asset Report Acknowledgement & License Key
HP has received your iCOD information
System: super
Serial Number: USR99USR99
Software Id #: Zabc339dkfj
System TimeStamp: 09/01/2001 18:00
Local Partition: 0
If you have not already done so, you may now apply the
license to use iCOD software on the specified system. The
license can be applied by executing the following command on
the specified system:
/usr/sbin/icod_modify -l 123abcde123abce123
For more information, see the icod(5) manpage or iCOD

documentation at http://docs.hp.com
Chapter 2 35
Roles Requirement
Roles Requirement
Your organization needs to designate people to fill certain roles for the
successful management of iCOD systems. There are two main roles to be
filled and they are:
• System Contact: This person is usually a system administrator and
must have root login privileges on the iCOD system. The system
contact controls the number of activated and deactivated processors
by use of the icod_modify command. iCOD system management
information is sent to the system contact via e-mail.
• Authorizing Manager: This person has financial authorization to
approve payment for additional processor capacity. That is, when the
number of active processors is increased, there is an additional
charge from HP for the use of the newly activated processors. The
authorizing manager approves the additional expense.
36 Chapter 2
License Requirement
License Requirement
iCOD systems require the iCOD software (versions B.04.x and B.05.x) to
be licensed. The required license is free and ensures communication
between your iCOD system and HP.
New for versions B.05.x is that once any vPar or hard partition is valid
and licensed on an iCOD system, the following are automatically valid
and licensed:
• other vPars — within the same complex

• other hard partitions — within the same complex
IMPORTANT A license must be applied before activation or deactivation of processors

can be performed with the icod_modify command. An unlicensed iCOD
system is incapable of activating or deactivating processors. iCOD
systems must have the license applied at the customer’s site. HP does
not apply the license prior to shipping iCOD systems to customers.
The method to apply the license is:
Step 1. Configure your iCOD system to send internet e-mail (configuration for
receiving e-mail is not required)
Step 2. Set the system contact information by entering the following command:
/usr/sbin/icod_modify -c name:e-mail:phone
Example 2-3 Setting system contact information for Mary Jones:
/usr/sbin/icod_modify -c “Mary Jones:mjones@corp.com:(970) 888-9999”
Step 3. Request a license-key from HP, via e-mail, by entering the following
command (This command sends an asset report, via e-mail, to: HP, the
system contact, and root):
Chapter 2 37
License Requirement
Step 4. After HP receives the asset report, a confirmation e-mail containing the
license-key, is sent to the system contact (the system contact was set in
Step 2, above). See “Testing E-Mail Transmission of the Asset Report” on
page 35 for an example of the acknowledgement e-mail message sent by
HP. Retrieve the license-key from the system contact’s e-mail.
Step 5. Apply the license by entering the following command (note that the
license-key in the following command is the string of letters and
numbers contained in the e-mail from HP):
/usr/sbin/icod_modify -l license-key
IMPORTANT Failure to license your system causes an e-mail message to be sent, on a

daily basis, to the system contact (if system contact information is
configured) or to root (if system contact information is not configured).
38 Chapter 2
iCOD System Move Requirements
iCOD System Move Requirements

If you are planning to move your iCOD system from its current street
address you must notify HP for authorization before the system is
moved. A move within a building or site, that does not change the street
address, does not require notification to HP.
HP generally authorizes any change of address for an iCOD system as
long as the move does not involve crossing national borders.
Before moving the iCOD system, contact the HP iCOD administrator to
get an “iCOD Move Authorization Number.” HP has the right to refuse
authorization in certain situations. Allow for at least one week for HP to
process the authorization. To request authorization for the move, send
an e-mail message to the iCOD administrator at icod_admin@hp.com
and include the following information:
• customer name
• customer contact e-mail address
• customer contact phone number
• system serial number or Software ID of the system to be moved
• date that the system will be moved
The iCOD administrator replies to the system contact, via e-mail, with
an authorization number for the specific system move. E-mail or some
other form of written authorization from HP must be received before
moving the iCOD system.
Chapter 2 39
When iCOD Program Requirements End
When iCOD Program Requirements End
IMPORTANT Refer to your contract from HP or the authorized channel partner for
details of all On Demand Solutions program requirements.
iCOD program requirements end after all of the following requirements

have been met:
1. all of the processors in the iCOD system are activated

2. all of the processors in the iCOD system are purchased from HP or
the authorized channel partner by paying the required enablement
fee
3. the requested number of active processors equals the total number of
processors
At this point the system is no longer an iCOD system and:
• The iCOD software can be un-installed (see “Uninstalling iCOD

Software” on page 49) to prevent asset reports being sent to HP daily,
via e-mail.
• The capability of sending e-mail to HP is no longer required.
40 Chapter 2
3 Installing and Uninstalling
iCOD Software
• “Updating/Installing iCOD Software” on page 42 below

• “Reinstalling iCOD Software” on page 48
• “Uninstalling iCOD Software” on page 49
Chapter 3 41
Installing and Uninstalling iCOD Software
Updating/Installing iCOD Software

Factory Integrated You do not need to install the iCOD software if your processors and
Systems software were ordered with your HP enterprise server. The iCOD
software was already installed by HP prior to delivery. You can use the
following command to verify that the iCOD software is installed and
configured:
/usr/sbin/icod_stat
IMPORTANT OpenView measure products (such as MeasureWare and GlancePlus)

must be updated to version C.02.60 or later before installing or updating
the iCOD software. For details see “Measurement Software on iCOD
Systems” on page 130.
If you currently have an iCOD software version installed that is prior to

version B.04.x (for example: B.01.00, B.02.x, or B.03.x) you need to
update your system to iCOD version B.05.01. It is recommended to
update to iCOD version B.05.01 if you currently have version B.04.x
installed. You can contact your HP service representative to update and
reconfigure your system to version B.05.01. However, below are
instructions for installing version B.05.01 (for HP-UX 11.0 and 11i v1)
from the Support Plus CD-ROM and Software Depot
(software.hp.com). These instructions can be used to upgrade an
existing iCOD system to version B.05.01, or to install version B.05.01 on
a newly configured iCOD system.
How To Find The Latest Patches

This document lists the patches required to install and run iCOD B.05.x
known at the time of publication. To find the most current patches, go to
the HP Software Depot at software.hp.com and perform the following
steps:
Step 1. Click on Search, enter the iCOD software product number B9073AA, then
click on the Search button
Step 2. Click on the link that appears as a result of your search

Step 3. Click on the installation link
42 Chapter 3
The required patches for iCOD B.05.01 are listed. You can then retrieve
the necessary patches from the HP web site:
ITresourcecenter.hp.com
For HP-UX 11.0 - Installing from the Support Plus CD

Follow this procedure to install or upgrade your HP-UX 11.0 iCOD
system to version B.05.01:
Step 1. Log in as root.
Step 2. Determine the CD drive device file by entering the following command:
ioscan -fnC disk
Step 3. Insert the Support Plus CD into the CD drive.
Step 4. Mount the CD drive to the desired directory. The following example uses
the /dev/dsk/c1t2d0 device file (from Step 2, above) and the /cdrom
directory. To mount the CD drive, enter a similar command as:
Mount Example:
mount -r /dev/dsk/c1t2d0 /cdrom
Step 5. Install the iCOD B.05.01 bundle from the Support Plus CD by entering
the following command:
swinstall -s /cdrom/DIAGNOSTICS/B.11.00 B9073AA
Step 6. Install the required patches from the HWE1100 bundle on the Support
Plus CD. Note that these patches require an automatic reboot. To install
the required patches, enter the following command:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /cdrom/HWE1100 ’*’
Step 7. Continue with “For All Installations” on page 46.
Chapter 3 43
For HP-UX 11i v1 - Installing from the Support Plus

CD
Follow this procedure to install or upgrade your HP-UX 11i v1 iCOD
system to version B.05.01:
Step 1. Log in as root.
Step 2. Determine the CD drive device file by entering the following command:
ioscan -fnC disk
Step 3. Insert the Support Plus CD into the CD drive.
Step 4. Mount the CD drive to the desired directory. The following example uses
the /dev/dsk/c1t2d0 device file (from Step 2, above) and the /cdrom
directory. To mount the CD drive, enter a similar command as:
Mount Example:
mount -r /dev/dsk/c1t2d0 /cdrom
Step 5. Install the iCOD B.05.01 bundle B9073AA from the CD:
swinstall -s /cdrom/DIAGNOSTICS/B.11.11 B9073AA
Step 6. Install the required patches from the HWEnable11i bundle on the
Support Plus CD. Note that these patches require an automatic reboot.
To install the required patches, enter the following command:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /cdrom/HWEnable11i ’*’
For HP-UX 11.0 - Installing from the HP Software

Depot
Step 1. Do a search for “B9073AA” at HP’s Software Depot web site:
software.hp.com
Step 2. Select the link, that appeared as a result of your search, and read the
Overview page.
Step 3. On the Overview page, click on the Receive for Free button.
Step 4. Fill in the registration information, select the HP-UX 11.00 operating
system, and then click on the Next button.
44 Chapter 3
Step 5. Select the link: B9073AA HP-UX 11.00.depot
under software download and download the depot file to the following
directory: /var/tmp
Note that you can name the download anything but by default it is:
/var/tmp/B9073AA_B.05.01_HP-UX_B.11.00_32+64.depot
Step 6. On the iCOD system log in as root.

Step 7. Install the iCOD bundle by entering the following command:
swinstall -s \
/var/tmp/B9073AA_B.05.01_HP-UX_B.11.00_32+64.depot ’*’
The interactive swinstall can also be used to install the depot file by
setting the target to /var/tmp/<package_name>. The iCOD B.05.x
software is low overhead and non-intrusive. The file system size will
increase by approximately 2 MB and a reboot is not required.
For HP-UX 11i v1 - Installing from the HP Software

Depot
Step 1. Do a search for the iCOD product number B9073AA at HP’s Software
Depot web site: software.hp.com
Step 2. Select the link, which appeared as a result of your search, and read the
Overview page.
Step 3. On the Overview page, click on the Receive for Free button.
Step 4. Fill in the registration information, select the HP-UX 11.11 operating
system, and then click on the Next button.
Step 5. Select the link: B9073AA HP-UX 11.11.depot
under software download and download the depot file to the following
directory: /var/tmp
Note that you can name the download anything but by default it is:
/var/tmp/B9073AA_B.05.01_HP-UX_B.11.11_32+64.depot
Step 6. On the iCOD system log in as root.
Chapter 3 45
Step 7. Install the iCOD bundle:

swinstall -s \
/var/tmp/B9073AA_B.05.01_HP-UX_B.11.11_32+64.depot ’*’
The interactive swinstall can also be used to install the depot file by
setting the target to /var/tmp/<package_name>. The iCOD B.05.x
software is low overhead and non-intrusive. The file system size will
increase by approximately 2 MB and a reboot is not required.
For All Installations

After you have successfully installed the iCOD B.05.x software using the
swinstall command, perform the following procedure to complete your
iCOD installation:
Step 1. Log in as root
Step 2. Note, this step is required only on new installations and upgrades from
iCOD version 1.0 software. Set the system contact information by
entering the following command:
/usr/sbin/icod_modify -c name:e-mail:phone
If you need details on setting system contact information, see “Setting

Your System Contact Information” on page 55.
Step 3. Ensure that outgoing mail can be sent to HP mail servers from your
iCOD system, even if the system is behind a firewall. If you need details
on configuring e-mail, see “E-Mail Configuration” on page 25.
Step 4. Acquire and apply a license to your iCOD system. See “License
Requirement” on page 37 for details of this procedure.
Step 5. If this is an update from an earlier version of iCOD, do the following:

a. Verify that the number of active processors is correct for this iCOD
system by executing the following command:
/usr/sbin/icod_stat
b. If the number of active processors is not correct, use the following
command to set the correct number of active processors (refer to the
manpage icod_modify(1M) for details of the icod_modify command):
/usr/sbin/icod_modify -s number-of-active-processors \
[desc]:user-name:mgr-name:mgr-e-mail:mgr-phone
46 Chapter 3
Step 6. Note, this step is necessary only for add-on systems and it must be
performed by a HP service representative (SR). An add-on system
is a non-iCOD system that has been converted to an iCOD system. If
your system is an add-on, then have your HP SR do the following:
a. Set the number of active processors equal to the number of existing

processors in the system by executing the following command:
/usr/sbin/icod_modify -s number-of-active-processors \
[desc]:user-name:mgr-name:mgr-e-mail:mgr-phone
b. Shut down the iCOD system.
c. Physically install the new processors.
d. If you want to configure iCOD for online activation of processors,
simply reboot the system. If you want to configure iCOD for offline
activation, reboot the system and deconfigure the appropriate
number of iCOD processors from BCH.
Step 7. Verify the correct number of requested active processors, and the
number of activated and deactivated processors, by executing the
following command:
/usr/sbin/icod_stat
Step 8. Test the transmission of your asset report, via e-mail to HP, by entering
Step 9. An e-mail reply is sent to the system contact after performing the
icod_notify command in Step 8. Use an e-mail client to verify the
return e-mail from HP to the system contact e-mail address.
Chapter 3 47
Reinstalling iCOD Software
Reinstalling iCOD Software
Preserving current iCOD information

If you reinstall HP-UX on an iCOD system (for example, installing
HP-UX by either cold-installing or installing from a “golden image”), all
information in the iCOD configuration file disappears unless you do the
following:
1. Before the reinstall, manually save your iCOD data and processor
allocation history by backing up the following files:
a. /etc/.iCOD_data
b. /var/adm/.iCOD_log
c. /var/adm/.iCOD_log.back
These files will be restored in Step 3 below.
2. Reinstall the iCOD B.05.x software bundle B9073AA from the
Support Plus media or the HP Software Depot (software.hp.com).
3. Restore your iCOD data and processor allocation history files:
a. /etc/.iCOD_data
b. /var/adm/.iCOD_log
c. /var/adm/.iCOD_log.back
If this is not done, you will lose all of the iCOD change history and
contact information.
Installing “Golden Images” on a non-iCOD System

If you attempt to install a golden image of an iCOD B.05.x system onto
another (non-iCOD) HP enterprise server, the result on the target
system is an invalid installation. That is, the iCOD B.05.x software will
be in a non-operational state. You can successfully remove the iCOD
software when the system is in this state by entering the following
command:
/usr/sbin/swremove B9073AA
48 Chapter 3
Uninstalling iCOD Software

If you have fulfilled all of the iCOD program requirements, see “When
iCOD Program Requirements End” on page 40, the system is no longer
considered an iCOD system. Therefore, the iCOD software is no longer
necessary and can be removed.
On iCOD When running the iCOD software on hardware-partitionable systems,

Hardware- the number of iCOD processors is audited for your complex as a whole,
Partitionable not an individual partition. You may find it necessary to redistribute
Systems: active processors from one partition to another, and at times remove the
iCOD software from a partition. It is important not to remove the iCOD
software from all partitions in your complex unless you have activated
and purchased all iCOD processors.
On All Systems: Remove the iCOD software bundle:

/usr/sbin/swremove B9073AA
For hardware-partitionable systems, you need to run this command on
each iCOD partition in the complex.
NOTE This command fails if any of the following conditions are true:
• all processors are not activated

• the requested number of active processors does not equal the total
number of processors
Chapter 3 49
50 Chapter 3
4 Using iCOD to Manage your
Processors
• “Understanding Configuration Change Notification” on page 52

• “Licensing Considerations” on page 54
• “Setting Your System Contact Information” on page 55
• “Checking the Status of your iCOD System” on page 56
• “Increasing Processor Capacity” on page 58
• “Decreasing Processor Capacity” on page 60
• “Overriding Deferred Processor Activations and Deactivations” on
page 62
• “Load-balancing Active Processors” on page 61
• “Moving a Cell from one Partition to Another” on page 64
• “Software Application Considerations” on page 65
• “Understanding Online vs. Offline Activation Methods” on page 66
• “Processor Test Activation on iCOD Systems” on page 69
• “Replacement of Failed Processors” on page 70
• “Processor Activation or Deactivation Delay with vPars” on page 72
For information on activating processors offline, see Appendix ,
“Operating in Offline Activation Mode,” on page 110.
Chapter 4 51
Using iCOD to Manage your Processors
Understanding Configuration Change Notification
Understanding Configuration Change

Notification
When you specify an increase or decrease in the number of active
processors — using the icod_modify command — this causes a
configuration change. When a configuration change occurs an asset
report e-mail is sent to the HP audit application.
Additionally, a notification e-mail is sent to the system contact and
authorizing manager when a configuration change occurs. If you do not
desire a notification e-mail to be sent whenever a configuration change is
made, then disable this feature by using the following command:
/usr/sbin/icod_notify -n off
52 Chapter 4
Understanding Configuration Change Notification
Example 4-1 Configuration Change Notification E-Mail for (non-vPar) iCOD

System
Subject: iCOD Configuration Change Notification
A configuration change has been made to the following system:

super.corp.com
NOTICE: This system is under an iCOD program contract. As per the

terms and conditions of the iCOD contract, when iCOD processors are
activated, you must either:
a) pay an enablement/activation fee for a permanent activation, or;
b) have processing time remaining under a special temporary
activation program.
If an activation is permanent or beyond your temporary activation

agreement, please issue a purchase order to HP or your authorized
channel partner for the required enablement fee. Failure to do so
constitutes a breach of contract.
One or more processors were activated.
Details of the change include:
Time of change: 11/01/02 11:00:00
Previous number of active processors: 1

Current number of active processors: 2
Number of processors to be active after reboot: 2
Description of change: new fiscal year increase

Person making the change: Tim Admin
Authorizing manager: Mr. Smith
Authorizing manager e-mail: wsmith@corp.com
Authorizing manager phone: (970) 888-1111
System contact: Mary Jones

System contact e-mail: mjones@corp.com
System contact phone: (970) 888-9999
If you are the system contact or authorizing manager and do not

want to receive this type of notification in the future, it can
be disabled by executing the following command on the system in
question:
/usr/sbin/icod_notify -n off
To turn notification on, execute:
/usr/sbin/icod_notify -n on
Chapter 4 53
Licensing Considerations
Licensing Considerations
License is Required
Licensing is required for the iCOD versions B.05.x software. The
required license is free and ensures communication between your iCOD
system and HP.
IMPORTANT You must apply a valid license prior to activating or deactivating

processors. An unlicensed iCOD system is incapable of activating and
deactivating processors.
You can verify if your iCOD system has a valid license applied by
entering the following command:
/usr/sbin/icod_stat
You should see the following if your system is licensed:
License applied: yes
See “License Requirement” on page 37 for details of applying a license to
your iCOD system.
54 Chapter 4
Setting Your System Contact Information
Setting Your System Contact Information

If you need to set the system contact information, use the icod_modify
command with the -c option. Note that you must specify a valid internet
e-mail address.
Here is an example session of icod_modify -c:
icod_modify -c “Mary Jones:mjones@corp.com:(970)888-9999“

Contact name: Mary Jones
Contact e-mail: mjones@corp.com
Contact phone: (970) 888-9999
NOTE: The system contact e-mail address shown above

will be used to send asset report acknowledgments,
software licenses for this software, and configuration
change notifications. Ensure that the e-mail address is
correct and the individual specified is the correct
person to receive this information.
Chapter 4 55
Checking the Status of your iCOD System

The icod_stat command lists the status of the processors in the iCOD
system. icod_stat provides the following information:
• the version number of the iCOD software
• the contract type (icod-purchase)
• whether or not the system is licensed
• hostname and network information
• model, serial number, and software ID of the system
• system contact information
• iCOD FROM e-mail address
• processor information, including the number of active and inactive
processors
• the local partition status (for hardware-partitionable systems)
• the number of physically present processors (active and inactive)
• a record of processor configuration changes and processor usage
See the icod_stat(1M) manpage for details.
See “icod_stat Output Differences in a vPar” on page 93 for details, and
an example, of icod_stat in a vPar environment.
56 Chapter 4
Sample Session of /usr/sbin/icod_stat -v

icod_stat -v on
iCOD Superdome Version: 5.0
Contract type: iCOD-purchase
System: License applied: yes
Hostname: supericod
DNS domain name: supericod.corp.com
IP address: 11.22.33.55
NIS domain name: .
System model: 9000/800/SD32000
Serial number: 1234567890
Software ID: abcdef

Contact phone: 970-888-9999
From e-mail: mjones@corp.com
Total processors: 4
Active processors: 1
Inactive processors that can be activated: 3
Inactive processors that cannot be activated: 0
Deconfigured processors: 0
Requested active processors: 1
Requested active processors specified for all partitions:
Requested
Active Total
Processors Processors Partition
========== ========== =========
1 4 supericod (par0) (local)
1 4 supericod (par1)
n/a 12 Unassigned cells
---------------------------------------------------------
2 total requested active processors specified for complex
Date: 09/01/01 11:00:00

Log type: Usage
Total processors: 4
Active processors: 1
Requested active processors: 1
Description: Application demand
Changed by: Tim Admin
Manager: W. Smith
E-mail address: wsmith@corp.com
Phone number: (970) 888-1111
Chapter 4 57
Increasing Processor Capacity

You have the ability to increase processor capacity instantly on
(specified) HP enterprise servers with HP’s On Demand Solutions
products. At any time, any number of inactive processors can be
activated. An inactive processor under warranty or support
automatically replaces a failed processor. HP will also service and
replace any failed processor.
Benefit of Deferred A benefit of using the icod_modify command’s deferred option (-D), for
Activation processor activation, is that the activation does not take place until a
reboot of the system occurs. The scheduled timing of the reboot (and the
processor activation) can take place at a planned time. For example, you
can activate processors in deferred activation mode and schedule a
system reboot to occur on the first day of the next month, which is a new
fiscal quarter for your organization.
Activating iCOD A nominal right-to-access fee is paid to HP for each iCOD processor in the
Processors in iCOD system. After an iCOD processor is activated, a purchase order
iCOD Systems should be submitted to HP or the authorized channel partner, for
payment of the enablement fee. Therefore, exercise caution to ensure that
an iCOD processor is activated purposefully and with financial approval.
Factory Integrated If your iCOD processors and software were ordered with your server,
Systems then they were already installed by HP before delivery and can be
activated at any time.
To activate one or more inactive processors, use the icod_modify
command as root. The following examples show you how to activate
inactive processors. Refer to the manpage icod_modify(1M) for details.
NOTE If you accidentally activate an iCOD processor, deactivate it as soon as

possible to avoid being charged the enablement fee. You can use the
icod_modify -s command/option to set the number of active processors.
If you have temporary capacity, the activation duration is debited from
your temporary capacity credits.
58 Chapter 4
iCOD Activation Example Session
IMPORTANT V-Class processors can only be activated in pairs.
In the following example session, there are a total of 4 processors in the

iCOD system; 2 processors are activated and 2 are inactive processors. In
this example, 1 additional processor is activated, leaving the iCOD
system with 3 active processors (and 1 inactive processor):
icod_modify -a 1 “app. demand:mjones:Bill Price:bprice@corp.com:(970)111-2222“
3 processors are now active.
NOTE: Verify that HP and 3rd party software licenses are upgraded
to take into account the number of active processors.
NOTE In the above activation example, the processor activation is instant (that
is, not require a reboot). To defer the activation (until the next reboot)
add the -D option to the command. See the manpage icod_modify(1M) for
details.
The icod_modify command allows you to activate processors with the -a
option, or set the total number of active processors with the -s option.
See “Software Application Considerations” on page 65 for details of

software application implications when activating additional processors.
Chapter 4 59
Decreasing Processor Capacity
Decreasing Processor Capacity

You have the ability to decrease processor capacity instantly on HP
enterprise servers with the iCOD software. At any time, any number of
active processors can be deactivated. Processor deactivation can be
useful for load balancing processors in hardware-partitionable iCOD
systems.
Benefit of Deferred A benefit of using the icod_modify command’s deferred option (-D), for
Deactivation processor deactivation, is that the deactivation does not take place until
a reboot of the system occurs. The scheduled timing of the reboot (and
the processor deactivation) can take place at a planned time.
To deactivate one or more active processors, use the icod_modify
command as root. The following example shows you how to deactivate
processors. Refer to the manpage icod_modify(1M) for details.
Deactivation Example Session for

Hardware-partitionable Systems
In the following session, there are a total of 4 processors in the
Superdome local partition; 3 processors are activated and 1 is an inactive
processor. In this example, 1 active processor is deactivated, leaving the
partition with 2 active processors and 2 inactive processors.
icod_modify -d 1 “load balance:mjones:Bill Price:bprice@corp.com:(970)111-2222“
NOTE In the above deactivation example, the processor deactivation is instant

(that is, not require a reboot). To defer the deactivation (until the next
reboot) add the -D option to the command. See the manpage
icod_modify(1M) for details.
The icod_modify command allows you to deactivate processors with the
-d option, or set the total number of active processors with the -s option.
60 Chapter 4
Load-balancing Active Processors
Load-balancing Active Processors
NOTE This section also applies to virtual partitions (vPars).
iCOD offers dynamic resizing of partitions on hardware-partitionable

systems (for example, Superdome). Specifically, active processors can be
redistributed across any or all partitions of a hardware-partitionable
system if those partitions contain iCOD processors.
For example, consider a Superdome system with two partitions:
Partition 1 has 5 active processors and 3 inactive processors

Partition 2 has 8 active processors and 0 inactive processors
You need to add processing power to Partition 1 because of application
demand and you notice that the active processors in Partition 2 are
under utilized.
Deactivating an active processor in Partition 2 decreases the number
of active processors in that partition, and activating one of the processors
in Partition 1 increases the number of active processors in that
partition. The total number of active processors in the Superdome
complex is the same at the end of this operation.
IMPORTANT To avoid any billing consequences, it is important to perform the

deactivation operation first.
This leaves the following:
Partition 1 now has 6 active processors and 2 inactive processors

Partition 2 now has 7 active processors and 1 inactive processor
Does the redistribution of active processors cost you anything?

No, because you did not change the overall number of active processors
in the Superdome complex, there is no charge.
Chapter 4 61
Overriding Deferred Processor Activations and Deactivations
Overriding Deferred Processor Activations

and Deactivations
NOTE Only activation of processors is discussed in this section, but deactivation

of processors also applies.
If you have performed a deferred processor activation, using the -D

option in the icod_modify command, and the requested number of
active processors specified is no longer desirable, you can override the
(pending) deferred activation by performing another deferred or instant
icod_modify operation, which overrides the first activation.
You may experience one of the following deferred activation scenarios:
• The specified number of active processors was incorrect and you

want to correct it, and apply the change, when the system reboots
• The entire operation was accidental and you want to undo it
Two examples are used to explain how to override these situations.
Example 4-2 Correcting an Incorrect Number of Deferred Active Processors
1. On your system or partition you currently have 2 processors

activated and 2 processors inactive. You decide 4 active processors
are needed, so you perform a deferred activation for 2 additional
active processors by entering the following command:
icod_modify -D -a 2 [desc]:user-name:mgr-name:mgr-email:mgr-phone
2. Later, and prior to a system reboot, you realize that you need only 3
active processors (not 4). You can override the initial deferred
activation in Step 1 by entering the following command:
icod_modify -D -s 3 [desc]:user-name:mgr-name:mgr-email:mgr-phone
The -s option in Step 2 (above) sets the number of active processors. The
activation takes place after the next system reboot due to the -D option.
You could also perform Step 2 without the -D option for the icod_modify
operation to be instant.
62 Chapter 4
Overriding Deferred Processor Activations and Deactivations
Example 4-3 Undoing an Accidental Deferred Processor Activation
1. On your system or partition you currently have 2 processors

activated and 2 processors inactive. You accidentally perform a
deferred activation for 1 additional active processor by entering the
following command:
icod_modify -D -a 1 [desc]:user-name:mgr-name:mgr-email:mgr-phone
2. Later, and prior to a system reboot, you realize that you didn’t want
to activate the additional processor — which would give you 3 active
processors — and you want your number of active processors to be 2.
You can override the initial deferred activation in Step 1 by entering
icod_modify -a 0 [desc]:user-name:mgr-name:mgr-email:mgr-phone
The -a 0 option in Step 2 (above) overrides the previous (deferred)

icod_modify command, which was executed in Step 1.
Chapter 4 63
Moving a Cell from one Partition to Another
Moving a Cell from one Partition to Another

When moving a cell from one partition to another partition, in an iCOD
system, the number of requested active processors for each partition does
not automatically change. The following example illustrates this:
Table 4-1 Pre-modification state:
Assigned Total Requested

Partition
Cells Processors Active #
par0 1,2 8 6
par1 3,4 8 6
Table 4-2 Post-modification state:
Assigned Total Requested

Partition
Cells Processors Active #
par0 1 4 6
par1 2,3,4 12 6
While the total number of processors changed in each partition, par0 is

left with a requested active number that can’t be satisfied, and par1 by
default does not automatically have an increase in the number of
requested active processors. Be sure to use icod_modify to adjust the
number of requested active processors for each partition affected by a
complex re-configuration.
NOTE Cell boards are dedicated to specific partitions and cannot be shared
between partitions. All processors on a cell board are only accessible by a
maximum of one partition. Processors on one cell board cannot be shared
across multiple partitions.
64 Chapter 4
Software Application Considerations
Software Application Considerations

Some software applications size themselves based on the number of
available processors when the application is started. Therefore, it may be
necessary to do one of the following for optimal performance with this
type of application:
• restart the application in order for it to recognize the presence of

newly activated processors
• reconfigure the application, prior to it being restarted, for maximum
performance benefits of the newly activated processor
• use the deferred activation option when activating processors so that
processors are only activated in conjunction with system reboots - see
the manpage icod_modify(1M) for details
• use the offline activation method when activating processors - see
“Understanding Online vs. Offline Activation Methods” on page 66
for details
IMPORTANT When you activate a processor, the number of active processors in the
system increases. Consequently this may require a license upgrade for
some of the software on your system. A license may be required for
HP-UX, HP-supplied software, or software from other application
providers.
Chapter 4 65
Understanding Online vs. Offline Activation Methods
Understanding Online vs. Offline Activation

Methods
Online Activation Online (dynamic) activation occurs when you activate processors, using
Mode the icod_modify command in either instant or deferred mode, while
HP-UX is running. Online activation is the standard method used to
activate processors.
Offline Activation Offline (manual) activation consists of deconfiguring processors that

Mode would otherwise be deactivated and available for online activation.
Offline activation occurs when you activate processors using the
following process:
1. using the icod_modify command to activate processors in deferred
mode
2. shutting down HP-UX on your iCOD system
3. configuring processors from the Boot Console Handler (BCH)
4. reset and boot the system
A reboot is required for offline activation.
Most software applications work fine with the online activation method.
However, some applications erroneously regard inactive processors to be
active processors. These types of applications may exhibit functional or
performance problems. Offline (manual) activation may be necessary for
these types of applications.
You may want to test your application for proper operation in online
activation mode. For information on testing your application, see
“Processor Test Activation on iCOD Systems” on page 69.
If you are not satisfied with your application behavior in the (dynamic)
online activation mode, you may want to switch the iCOD system to
offline (manual) activation mode. For information on configuring your
system in offline activation mode see Appendix A, “Offline Configuration
and Activation of Processors,” on page 109.
66 Chapter 4
NOTE Booting a system to the HP-UX prompt can be time consuming,

depending on your software and hardware configuration.
For information on how to dynamically activate processors, see

“Increasing Processor Capacity” on page 58.
For information on how to manually configure processors, see
Appendix A, “Offline Configuration and Activation of Processors,” on
page 109.
Chapter 4 67
Advantages and Disadvantages of Online Activation
Advantages: • no reboot required

• immediate additional processing power
• one simple command to activate
• automatic replacement of failed processors
Disadvantages: • some applications may not take advantage of the additional

processing power and experience functional or performance problems
• some applications may erroneously regard the inactive processors as
active processors and experience licensing problems
Advantages and Disadvantages of Offline Activation
Advantages: • applications should not experience functional or performance

problems
• applications should not experience licensing problems
Disadvantages: • requires a reboot to activate a processor

• complex, multi-step process
• no automatic replacement of failed processors
• the HP application, Predictive, reports the deconfigured processors
• L- and N-Class systems show system alerts for deconfigured
processors
68 Chapter 4
Processor Test Activation on iCOD Systems
Processor Test Activation on iCOD Systems

You may desire to test your iCOD system for improved performance by
activating an additional processor. The use of temporary capacity
(TiCOD) is required for processor test activations. E-mail connectivity to
HP is required for the use of TiCOD.
See Chapter 7, “Temporary Capacity for iCOD Processors,” on page 83
for details of TiCOD.
The following testing guidelines are meant to be an aid to your test plan.
You may need to get consulting help to develop a detailed test plan.
1. Test your applications for proper functionality and performance with
all of the iCOD processors inactive. Be sure to check measurement
tools that monitor processor usage.
2. Acquire TiCOD for the amount of processor test activation necessary.
3. Use TiCOD for activation of an iCOD processor while your
applications are running.
4. Confirm that measurement tools, which monitor processor usage,
account for the newly activated processor.
5. Verify that applications are benefiting from the performance of the
extra processors (as per your expectations for your applications).
Note that some applications may need to be restarted or reconfigured
to take advantage of the newly activated processors.
6. When you are finished with your testing, use icod_modify to
deactivate a processor that was activated with TiCOD.
Chapter 4 69
Replacement of Failed Processors
In Online Activation Mode

If an active processor fails with a Low Priority Machine Check (LPMC),
in your iCOD system, its processor capacity is replaced instantly by an
inactive processor, if any are available on the system/partition. The
failing processor is marked for deconfiguration during the next system
reboot.
If an active processor fails with a High Priority Machine Check (HPMC),
then upon reboot, the failed processor is deconfigured and its processor
capacity is instantly replaced by an inactive processor, if any are
available on the system/partition.
NOTE In both of the above scenarios the failed processor should be replaced in a
timely manner using your normal hardware support process.
Failed Monarch Processors

Monarch processors (see “monarch processor” on page 140 for a
definition) that are failing with a LPMC are not instantly replaced.
When a monarch processor experiences a LPMC, the LPMC monitor
marks the processor for deconfiguration; however, the LPMC monitor is
not be able to deactivate the processor, unless the system is re-booted.
Deactivation of a monarch processor is not possible because it is the
controlling processor of the operating system (CPU 0). Therefore, an
iCOD processor cannot replace a (failing) monarch processor.
If your iCOD system has only one active processor, it is considered a
monarch processor, and it cannot be replaced online. A reboot of the
system is required to replace the failing monarch processor.
If there are multiple active processors in your iCOD system, one of them
is designated as the monarch processor, and the other (non-monarch)
processors can be replaced online. If the monarch processor fails, it
cannot be replaced without a reboot.
70 Chapter 4
In Offline Activation Mode

An inactive processor, if available in the system/partition, needs to be
manually configured before the processor capacity of the failed processor
can be replaced.
Chapter 4 71
Processor Activation or Deactivation Delay with vPars
Processor Activation or Deactivation Delay

with vPars
You may experience a delay with processor activation or deactivation in
a vPar environment. For example, if you currently have two active
processors in your vPar, and you activate an additional processor, by
executing the following command:
icod_modify -a 1 “app demand:mjones:Bill Price:bprice@corp.com:(970)111-2222“
You should immediately receive a message indicating the number of
active processors in the vPar:
However, if your iCOD system is experiencing a delay with the processor
activation, you will not receive the message above (indicating the
additional processor is activated). After five seconds have elapsed, and
the additional processor is not activated, you will receive the following
message:
NOTE: This request may take one or more minutes to complete.
If you receive the above message, wait for the command to complete.
Though the above example is for a processor activation, the same
scenario may occur for a processor deactivation in a vPar environment.
72 Chapter 4
5 Troubleshooting
• “Correcting Activation Mistakes” on page 74

• “Troubleshooting the iCOD Software” on page 75
Chapter 5 73
Troubleshooting
Correcting Activation Mistakes
Correcting Activation Mistakes
Too Many Processors Activated on iCOD
iCOD On For hardware-partitionable systems under an iCOD contract,

Hardware- deactivating processors in one partition and activating the same number
Partitionable of iCOD processors in another, does not require the payment of an
Systems enablement fee as long as the two events occur within the grace period
specified in the iCOD agreement. The total number of iCOD processors
does not change, so HP does not require that the activated processors be
purchased. See “Load-balancing Active Processors” on page 61 for
details.
74 Chapter 5
Troubleshooting
Troubleshooting the iCOD Software

In the event the iCOD software is not functioning, perform the following
steps:
NOTE The following procedure assumes you have entered your system contact
information and you can send e-mail over the internet to the hp.com
domain. See “E-Mail Requirements” on page 24 for details on configuring
e-mail.
1. Verify that HP is able to receive the e-mail message from the iCOD
software:
a. execute the command:

b. verify that HP replies with a confirmation message, via e-mail, to
the system contact
2. Verify that your iCOD system has a valid license applied by entering
/usr/sbin/icod_stat
You should see the following if your system is licensed:

License applied: yes
If your system is not licensed, see “License Requirement” on page 37

for details on applying the license.
3. Verify that the cron entry for the iCOD software has been set
correctly by logging in as root and executing:
/usr/bin/crontab -l
You should see the following:

0 12 * * * /usr/sbin/icod_notify -c </dev/null >/dev/null 2>&1
4. Verify that the cron daemon is up and running.
Chapter 5 75
Troubleshooting
5. Verify that the executables and configuration files have not been
deleted and the permissions are set correctly:
• /usr/sbin/icod_stat
• /usr/sbin/icod_modify
• /usr/sbin/icod_notify
• /usr/lib/libicod.sl
• /etc/.iCOD_data
6. If any of the files in Step 5 (above) are missing or corrupted then
re-install the iCOD software. Refer to “Reinstalling iCOD Software”
on page 48 for details.
7. Ensure that the kernel driver diag2 is built into the kernel.
8. For V-Class enterprise servers, verify V2500/V2600 Test Station
Software Release 3.1, or higher, is loaded on the system.
9. If HP-UX 11.0 is installed on your iCOD system, verify that the
required 11.00 kernel and command patches are installed. See
“HP-UX 11.0 Requirements” on page 21 for details.
10. If HP-UX 11i v1 is installed on your iCOD system, verify that
the required 11i v1 kernel patches are installed. See “HP-UX 11i v1
Requirements” on page 22 for details.
NOTE See “Steps to Confirm or Diagnose E-mail Configuration” on page 28 for

details of ensuring your e-mail is configured correctly.
76 Chapter 5
6 Frequently Asked Questions
This chapter covers frequently asked questions on the following topics:
• “iCOD Software” on page 78

• “Superdome” on page 82
Chapter 6 77
Frequently Asked Questions
iCOD Software
iCOD Software
What software product is required for iCOD on Superdome servers?
There are separate HP software bundles for iCOD and pay per use
(PPU). For iCOD, you should install the iCOD software, product number
B9073AA. Do not install the PPU software, product number T1322AA, on
iCOD systems.
Can I run both the pay per use software and the iCOD software on a L-,
N-, or V-Class server that is running HP-UX 11.0?
The pay per use and iCOD software bundles are mutually exclusive. That
is, they cannot coexist on the same HP enterprise server.
What patches are required for running iCOD B.05.x software, on a HP

enterprise server, that is running HP-UX 11i v1?
At the initial release of the iCOD B.05.00 software, the following patches
are required:
• PHKL_23154 dflush() patch
• PHKL_25218 PDC Call retry, PDC_SCSI_PARMS, iCOD hang fix
• PHKL_26232: S700_800 11.11 Psets Enablement patch, FSS
iCOD patch
• PHCO_24477: S700_800 11.11 sar(1M) patch
• PHKL_22987: 11i pstat() patch — only if your system runs
MeasureWare software
How can I get the iCOD B.05.01 software bundle?

The iCOD B.05.01 software bundle B9073AA is installed at the factory for
new systems. The B9073AA software bundle must be installed by a HP
service representative for existing (non-iCOD) systems. The B9073AA
bundle is available on the HP web site: software.hp.com. It is not
available on the HP-UX 11i v1 Operating Environment (OE) media.
See “Updating/Installing iCOD Software” on page 42 for details of

installing the iCOD B.05.01 software bundle B9073AA.
78 Chapter 6
iCOD Software
One of my HP-UX 11i v1 applications has compatibility issues with the

iCOD software. How do I correct the problem?
The application may have a problem when processors are activated or
deactivated online. Some applications size themselves at startup based
on the number of active processors and they don’t adjust for processor
increases or decreases. You may try offline activation mode for these
types of applications. See “Operating in Offline Activation Mode” on
page 110 for details.
We received an e-mail message indicating the system/partition did not

report system configuration data. What is the problem and how do I
correct it?
Make sure that e-mail is properly configured for the system/partition. On
hardware-partitionable systems, such as Superdome, all partitions must
be configured to send e-mail to HP. See “E-Mail Configuration” on
page 25 for details. Use the icod_notify command to test e-mail
connectivity to HP. This command sends an e-mail message to HP, and if
the message is received by HP, a reply message is sent to the system
contact.
How much history is retained in the iCOD log files?

The iCOD log files retain (approximately) the latest 3000 iCOD events.
An iCOD event occurs, and is written to the log files, when one of the
following happen:
• the iCOD system sends an asset report to HP (scheduled in cron to

occur daily at noon)
• the iCOD system is shut down
• the iCOD system is started
• the iCOD system has a configuration change (that is, a processor is
activated or deactivated)
You can view all events in the iCOD log files by executing the following
command:
/usr/sbin/icod_stat -u
Chapter 6 79
iCOD Software
Is the iCOD software license applied by HP, before the iCOD system is
shipped to the customer?
No. HP does not apply the license prior to shipping iCOD systems to
customers. The license for the iCOD software must be applied at the
customer’s site. This is because the e-mail connectivity to HP is a crucial
part of the iCOD software. See “License Requirement” on page 37 for
details on licensing your iCOD system.
The resulting configuration of my iCOD system does not agree with

what I ordered from HP. How did this configuration change occur?
The iCOD software is able to control the granularity of processor
activation/deactivation to the single processor level. The iCOD ordering
and manufacturing rules often do not allow such fine granularity.
The iCOD ordering rules dictate the quantity of active processors and
iCOD processors in the cell boards. Because the iCOD software
distributes the active processors and iCOD processors (for a given
partition) in a manner that optimizes loads across all cells, the end
configuration may be different than the original order — but the number
of active and icod processors is the same (that is, they match what was
ordered).
For example, if you order a rp8400 server with two cell boards, in which
cell board #1 contains 4 active processors and cell board #2 contains 2
active processors and 2 iCOD processors (total of 6 active and 2 iCOD
processors), at run time, the iCOD software balances the distribution of
active processors across the cell boards so that each cell has 3 active
processors and 1 iCOD processor.
80 Chapter 6
iCOD Software
What e-mail is sent by the iCOD software?

The following table lists the e-mail messages sent to the iCOD system
from the iCOD software:
Table 6-1 E-mail sent by the iCOD software
Triggered By E-mail Message
icod_notify An asset report is sent to the system

contact, root, and HP (the asset report sent
to HP is encrypted).
icod_notify -c (daily from An encrypted asset report is sent to HP.

cron, system startup,
system shutdown, and
configuration change)
icod_modify (if Information about the configuration change

configuration change is sent to the system contact and the
notification is turned on) authorizing manager.
icod_notify -c (daily from If the system is unlicensed, instructions on

cron - if unlicensed system) how to license the system are sent to the
system contact. If the system contact is not
set, then instructions on how to set the
system contact and license the system are
sent to root.
system boot Information about the number of requested

active processors being below the minimum
number of active processors is sent to the
system contact, if set, or to root if the
system contact is not set.
Chapter 6 81
Superdome
Superdome
What is the difference between iCOD and pay per use on Superdome?
Under iCOD: When iCOD processors are activated, you must pay an
enablement fee. iCOD processors cannot be deactivated, unless you are
load balancing between partitions in a Superdome complex, and not
changing the total number of active processors.
Under pay per use: You can activate and deactivate processors as your
needs change. The number of active processors is reported automatically
to HP (via e-mail) and you are billed each month based on your usage.
What Superdome configurations are required for iCOD?

The Superdome configuration requirements for iCOD are:
• For 32 processor systems, a minimum of 32GB of main memory
• For 64 processor systems, a minimum of 64 GB of main memory
• The HP-UX 11i v1 OE operating system must be installed
• The iCOD B.05.x software bundle B9073AA must be installed
82 Chapter 6
7 Temporary Capacity for iCOD
Processors
• “Overview of Temporary Capacity” on page 84

• “Ordering Temporary Capacity for New iCOD Processors” on page 85
• “Ordering Temporary Capacity for Existing Systems” on page 85
• “Licensing and Support” on page 85
• “Tracking the Purchase and Use of Temporary Capacity” on page 86
Chapter 7 83
Temporary Capacity for iCOD Processors
Utilizing Temporary Capacity for iCOD Processors
Utilizing Temporary Capacity for iCOD

Processors
Overview of Temporary Capacity

New for iCOD versions B.05.x is temporary capacity. Temporary
capacity is a HP software product that enables iCOD customers to
purchase (prepaid) processor activation rights, for their iCOD processors,
for a limited duration of time. Temporary capacity can be purchased in
units of 30 processor-days (43,200 processor-minutes).
NOTE Temporary capacity is supported on HP-UX 11i v1 only and is not

available on HP-UX 11.0.
You can activate and deactivate iCOD processors as you wish until the
activation time equals your prepaid temporary capacity duration. For
example, with one unit of temporary capacity, you can activate one
iCOD processor for 30 days or four iCOD processors for one hour a day
for 180 days (or any combination that totals 43,200 processor-minutes).
Processor activation time is managed in units of minutes; therefore, you
can use iCOD processors in units of minutes. For example, if you activate
an iCOD processor for only five minutes, and then deactivate it, you are
charged for only five minutes of activation time (out of your total of 30
processor-days). There can be a deviation of up to one minute in usage
tracking for each instance of activation and deactivation. This is because
the licensing clock runs in units of minutes.
If you activate processors beyond the prepaid temporary capacity
duration, then the activated iCOD processors are considered purchased,
as in today's iCOD model.
NOTE Temporary capacity credits are not transferable from one iCOD system
to another.
84 Chapter 7
Ordering Temporary Capacity for New iCOD

Processors
iCOD processors do not automatically include temporary capacity
rights. To utilize temporary capacity on newly ordered iCOD
processors, you first order iCOD processors as you normally do. In
addition, order temporary capacity rights separately, in units of 30
processor-days. There is one temporary capacity product per class of
HP server.
For example, to add two new iCOD 750MHz processors to your rp8400
server, and two 30 processor-day units of temporary capacity:
1. Order the two iCOD processors with the HP product number A6718A
2. Order the two 30 processor-day units of temporary capacity
The two units of temporary capacity provide you with 60
processor-days of temporary capacity. A processor-day is the usage of one
iCOD processor for one 24-hour period. The processor-days can be used
among any of the iCOD processors installed in your iCOD system.
Ordering Temporary Capacity for Existing Systems

To add temporary capacity credits to your existing iCOD system, that
contains iCOD processors, just order the desired quantity of the
temporary capacity product for your type of server. Be sure to specify
the system serial number, which is required for orders of iCOD
processors and temporary capacity, for installed base systems.
Licensing and Support

When you purchase temporary capacity, included are the temporary
HP-UX license to use and support for the iCOD processors. Your iCOD
system must be properly licensed for the HP-UX Operating Environment
(OE), before activating iCOD processors under temporary capacity.
Software licenses for 3rd party software may also be needed. Check with
your application software vendor for licensing requirements.
Chapter 7 85
Tracking the Purchase and Use of Temporary

Capacity
NOTE The reply e-mail message, sent from HP in response to the icod_notify
command, includes information on your remaining credits of temporary
capacity.
The HP audit application tracks temporary capacity usage in increments

of minutes. The initial purchase is converted from the number of
processor-days, to processor-minutes, and usage debits take place as the
audit application becomes aware of iCOD processor activations
The audit application sends the system contact an e-mail when the
available credit remaining for processor-days falls below five. This e-mail
notifies you to deactivate the iCOD processor, or submit a purchase order
to continue usage.
IMPORTANT If you leave an iCOD processor activated beyond the purchased

temporary capacity duration, the iCOD software does not
automatically deactivate the processor. You are responsible to either
purchase an additional unit of temporary capacity or purchase the
iCOD processor.
Continuation of After an activated iCOD processor has exhausted its temporary

Temporary capacity duration, you may wish to leave the processor activated, and
Capacity initiate the purchase of an additional unit of temporary capacity.
Because the purchase of an additional temporary capacity unit is not
instantaneous, the processor usage (after the initial temporary
capacity duration has expired, but before your new unit of temporary
capacity is purchased and entered into the HP audit application) is
deducted from the amount of processor-days credited. For example, if you
submit a temporary capacity order ten days after running out of initial
temporary capacity processor-days, but keep the iCOD processor
activated, the ten processor-days are deducted from your available
processor-days, which you have just purchased.
86 Chapter 7
It is mandatory for your iCOD system to be able to send e-mail to the HP

audit application on a daily basis. This is necessary for HP to monitor
usage of your iCOD system so that temporary capacity usage can be
tracked. If the audit application stops receiving your iCOD system’s
e-mail, then HP makes assumptions on processor usage, specifically:
1. For the first five days of missing e-mail, the iCOD processor usage is
assumed to be identical to the processor usage as configured in the
last system report. If the last system report demonstrated no iCOD
processors are activated, then HP assumes this to be the state of the
system. If the last system usage indicates two iCOD processors are
activated, then two processor-days are deducted for each of the five
days.
2. After the fifth day of missing e-mail, HP assumes all iCOD
processors on the system are active. If the system has five iCOD
processors, HP deducts five processor-days, each day for the iCOD
system thereafter.
Auditing of temporary capacity is done at the system level on iCOD
systems that support partitioning. Therefore, although temporary
capacity may have been purchased for use by a specific partition, it is
available to all partitions in the system.
Temporary capacity credits are not transferable across iCOD systems.
All credits for processor-days for a system are considered lost when all
iCOD processors on that system are purchased, or when the iCOD
contract term expires for that system.
Buying all iCOD processors on the system, at the current list price,
clears out any previous violation of temporary capacity.
Chapter 7 87
88 Chapter 7
8 iCOD Compatibility with vPars
and Psets
• “iCOD Compatibility with Virtual Partitions” on page 90

• “iCOD Compatibility with Processor Sets” on page 97
Chapter 8 89
iCOD Compatibility with vPars and Psets
iCOD Compatibility with Virtual Partitions
Overview
The iCOD version B.05.x software co-exists with virtual partitions
(vPars) version A.02.00 or greater.
To co-exist with vPars, the iCOD software modifies processor capacity
using the vparmodify command. Assigning a processor to a vPar is
equivalent to activation and removing a processor from a vPar is
equivalent to deactivation.
The iCOD software must be installed on all vPars with iCOD processors.
In addition, all vPars with iCOD processors must be configured to send
e-mail to HP.
Once one vPar or hard partition is licensed, all other vPars, or hard
partitions, are automatically licensed. This is similar to licensing on
hard partitions.
Only unbound processors can be added or removed from a vPar.
NOTE See the Installing and Managing HP-UX Virtual Partitions manual for
details of vPars. This manual can be found on the HP web site:
docs.hp.com
90 Chapter 8
iCOD Software Compatibility with vPars —

Supported Hardware Platforms
Table 8-1 iCOD Compatibility with vPars — Supported Hardware
Platforms
Operating Supported
Software and
Version
Version Platforms
iCOD HP-UX 11i L-Class, vPar software version A.02.00 or

B.05.x v1 N-Class, and greater is required
(B9073AA) Superdome
servers
iCOD Compatibility with vPars — Supported Hardware Platforms

The iCOD B.05.x software is compatible with vPars (version A.02.00 or
greater) and is supported on the following HP servers:
• L-Class: L3000
• N-Class: All Models
Chapter 8 91
Activation and Deactivation of Processors in a vPar

The iCOD software uses the vparmodify command to instantly activate
and deactivate processors. The activations and deactivations are
accomplished by adding and removing unbound processors from a vPar.
NOTE Deferred activations and deactivations are not supported in a vPar

environment.
When you execute the icod_modify command to deactivate a processor,

it determines how many processors in the local vPar are unbound. If
enough unbound processors exist to satisfy the request, the appropriate
vparmodify command is executed, and the proper number of unbound
processors are removed from the local vPar.
When you execute the icod_modify command to activate a processor, it
determines how many processors are available for activation. If enough
processors are available to meet the request, the appropriate
vparmodify command is executed, and the proper number of unbound
processors are added to the local vPar.
Whether you are activating or deactivating processors, the (appropriate)
vparmodify command adjusts only the number of unbound processors,
and it does not explicitly specify certain processors, or affect the number
of bound processors. Any error messages that are output by the
vparmodify command are displayed by the icod_modify command.
Activation or deactivation of processors in a vPar may take one or more
minutes to complete, but is usually no slower than in a non-vPar. See
“Processor Activation or Deactivation Delay with vPars” on page 72 for
details.
92 Chapter 8
icod_stat Output Differences in a vPar

The following table outlines the differences between a vPar environment
and a non-vPar environment for the icod_stat command’s output:
Table 8-2 icod_stat Output Differences in vPars
icod_stat Meaning in a non-vPar Meaning in a vPar

Option Environment Environment
-i Displays the number of Displays the number of

inactive processors available inactive processors available
for immediate activation for immediate activation in
the local vPar
-I Displays the total number of Displays the total number of

inactive processors. This inactive processors in the
number includes any hard partition. This number
deconfigured processors and includes any deconfigured
inactive processors that processors and inactive
cannot be instantly activated. processors that cannot be
This is basically the reported instantly activated. This is
number of iCOD processors. basically the reported number
of iCOD processors for the
hard partition.
-a Displays total number of Displays total number of

active CPUs on the system active CPUs in the local vPar
-t Displays total number of Displays total number of

CPUs assigned to (physically processors assigned to the
present on) the system local vPar
-p Displays requested active and Displays number of CPUs

total processors for all hard assigned to each vPar AND
partitions in a partitionable the requested active and total
system CPUs for all hard partitions
in a partitionable system
NOTE In a vPar environment, the usage log information displayed by the

icod_stat -u command reflects the status of the entire hard partition,
rather than the status of the local vPar. Also, the Requested active
processors are the total number of processors assigned to all vPars.
Chapter 8 93
Example Output of /usr/sbin/icod_stat -p

icod_stat -p on a
Partitionable Version: 5.0
System Contract type: iCOD-purchase
Containing vPars License applied: yes
Hostname: zooVpar0
DNS domain name: zooVpar0.com
IP address: 11.22.33.55
NIS domain name: .
System model: 9000/800/N4000-44
Serial number: 1234567890
Software ID: abcdef

Contact phone: 970-888-9999
From e-mail: mjones@corp.com
Processor Information for Local Virtual Partition

-------------------------------------------------
Assigned processors: 4
Active assigned processors: 3
Inactive assigned processors: 1
Unassigned processors that can be assigned: 1
Unassigned processors that cannot be assigned: 2
Virtual Partition Information for Hard Partition:

zooVpar0
-------------------------------------------------
Assigned Virtual
Processors Partition
========== =========
4 zooVpar0 (local)
1 zooVpar1
3 Unassigned processors
94 Chapter 8
Licensing and vPars

Once any vPar or hard partition is valid and licensed, the following are
valid and automatically licensed (assuming the iCOD software is
installed):
• other vPars, within the same complex

• other hard partitions, within the same complex
Static vPars
If a vPar is static (that is, the resources cannot be migrated, added,
deleted, or modified) and you attempt to activate or deactivate
processors, the iCOD software displays a message indicating that the
configuration of the processor resources cannot be modified.
NOTE The icod_stat command’s output indicates that the number of

unassigned processors that can be assigned (to the local vPar) is
zero if the static resource attribute for the local vPar is set.
LPMC Deactivations in vPars

In a vPar environment, if the Low Priority Machine Check (LPMC)
monitor deactivates a processor, it does not automatically replace the
failing processor with an iCOD processor. The processor replacement
must be performed manually by using the icod_modify command to
assign a replacement processor, if one exists. The failing processor
remains in the vPar until the vPar is rebooted.
Chapter 8 95
LPMC and icod_stat Reporting

In a vPar environment, the icod_stat command does not report the
correct number of “Unassigned processors that can be assigned” if the
following conditions occur:
1. the LPMC monitor marks a failing processor for deconfiguration

2. the vPar with the failed processor is rebooted
If the above two conditions occur, the failed processor is erroneously
included in the count of “Unassigned processors that can be assigned” as
reported by the icod_stat command.
Removal of the iCOD Software

In a vPar environment, you cannot remove the iCOD software, unless the
following conditions are true:
• the total number of activated processors on the hard partition = total

processors
• the total number of processors assigned to all vPars for the hard
partition = total processors
96 Chapter 8
iCOD Compatibility with Processor Sets
Overview
The iCOD version B.05.x software successfully co-exists with processor
sets (Psets).
To co-exist with Psets, the iCOD software only activates and deactivates
processors in the default processor set. Processors in non-default
processor sets are not activated or deactivated.
NOTE There must be at least one processor in the default processor set. The
last remaining processor in the default processor set is unavailable for
deactivation.
Chapter 8 97
iCOD Software Compatibility with Psets — Supported

Hardware Platforms
Table 8-3 iCOD Compatibility with Psets — Supported Hardware
Platforms
Operating Supported
Software and
Version
Version Platforms
iCOD HP-UX 11i L-, N-, V-Class,

B.05.x v1 rp7410, rp8400,
(B9073AA) and Superdome
servers
iCOD Compatibility with Psets — Supported Hardware Platforms

The iCOD B.05.x software is compatible with Psets and is supported on
the following HP servers:
• L-Class: L2000 and L3000

• N-Class: All Models
• V-Class: V2500 and V2600
• rp7410
• rp8400
98 Chapter 8
Scope of the iCOD Software Interacting with Psets

The iCOD software does not provide any additional functionality to
specifically support adding or removing processors from a specific Pset,
and it does not interfere with any Psets on the system. Processor
activations and deactivations are limited to the default Pset.
Activation and Deactivation of Processors

In a non-vPar environment where Psets are present, the iCOD software
only activates and deactivates processors in the default Pset.
Processors can be migrated to the default Pset for purposes of
deactivation, or from the default Pset to other Psets after activation.
Psets on vPars
In a vPar environment, the iCOD software passes the request for a
processor activation or deactivation to the vparmodify command. No
special consideration is given to Psets from the vparmodify command’s
perspective. Therefore, when using vPars, processors in non-default
Psets must be bound processors. Otherwise, a processor designated for
deactivation by vparmodify may be selected from an unexpected Pset.
Chapter 8 99
100 Chapter 8
9 iCOD Cell Board
• “Overview” on page 102

• “iCOD Cell Board — Supported Platforms” on page 102
• “Ordering a New System Containing iCOD Cell Board” on page 103
• “HP-UX License and Support” on page 103
• “iCOD Cell Board Activation Fees” on page 104
• “Activation of an iCOD Cell Board” on page 107
• “Accidental Activation of an iCOD Cell Board” on page 108
Chapter 9 101
iCOD Cell Board
iCOD Cell Board
iCOD Cell Board
Overview
iCOD Cell Board offers you a way to have additional (inactive) cell board
capacity in your iCOD system for growing business needs. When the
need arises, these iCOD cell boards, which contain memory and
processors, are then available for instant activation and use.
Similar to the iCOD CPU program, there is an initial right to access fee
for an iCOD cell board. Once activated, a cell board and its memory are
considered purchased and you must pay the enablement fee to purchase
the cell board.
After an iCOD cell board has been activated, all of the iCOD processors
on the cell board are available for purchase accordingly. That is, you can
activate an iCOD processor and purchase it by paying the enablement
fee.
As part of the activation process, you should submit a Purchase Order to
HP to purchase the cell board, memory, and any activated processor(s).
IMPORTANT An active cell board must have a minimum of one active processor.
iCOD Cell Board — Supported Platforms

Table 9-1 iCOD Cell Board — Supported Platforms
Operating Supported
Software and
Version
Version Platforms
iCOD HP-UX 11i rp7410 and Check with your HP sales

B.05.x v1 rp8400 servers representative for availability of the
(B9073AA) iCOD Cell Board product
102 Chapter 9
iCOD Cell Board
iCOD Cell Board
Ordering a New System Containing iCOD Cell Board

Initially, you have the right to access an iCOD cell board by ordering the
appropriate HP product number, for your specific class of HP server.
Additionally, the memory on the iCOD cell board has a separate HP
product number for the right to access.
NOTE It is highly recommended to have the same number of processors and

amount of memory on all cell boards in a given hard partition
(nPartition). For optimum performance, each nPartition should have cell
boards with identical numbers of processors and amounts of memory
(otherwise, the system performance can be unpredictable).
When you decide to activate the iCOD cell board and memory, you order
the corresponding HP product numbers, and pay the enablement fee.
If the cell board activation results in any iCOD processors being
activated, those activated processors need to be purchased using the
existing HP iCOD CPU product numbers.
Rules for ordering memory ensure that the iCOD cell board matches the
amount of memory in the non-iCOD cell boards, in a given nPartition.
HP-UX License and Support

You do not initially pay for HP-UX license and support fees on an iCOD
cell board.
When you activate an iCOD cell board, and pay for the enablement fee,
you must additionally pay for the incremental HP-UX license and
support costs for each iCOD processor that is activated. That is, the
HP-UX license and support costs are based on a “per active processor”
basis and not included in the enablement fee for the iCOD cell board.
If activation of an iCOD cell board does not increase the number of active
processors, then you do not have to pay any incremental HP-UX license
and support fees.
Your iCOD system must be properly licensed for the HP-UX Operating
Environment (OE) when activating the iCOD cell board. Software
licenses for 3rd party software may also be needed. Check with your
application software vendor for licensing requirements.
Chapter 9 103
iCOD Cell Board
iCOD Cell Board
iCOD Cell Board Activation Fees

Additional fees are payable to HP when you activate an iCOD cell board.
Contact your HP sales representative for details.
Activating an iCOD cell board causes at least one processor to become
active on that cell board. However, this does not necessarily mean an
iCOD processor has been activated or that the total number of active
processors increases — unless the requirement of a minimum of one
active processor per active cell board could not be met without activating
a new processor. In summary, if the number of activated (and purchased)
processors in a nPartition equals (or exceeds) the number of active cell
boards, then the iCOD software does not automatically activate
additional iCOD processors.
NOTE The following examples assume that the number of requested active
processors has not been increased just prior to the iCOD cell board
activation.
104 Chapter 9
iCOD Cell Board
iCOD Cell Board
Example 9-1 Activating an iCOD Cell Board without increasing the number of
total active processors
For example, if you have a two cell board nPartition with four active
processors on one cell board, and an inactive (iCOD) cell board with four
iCOD processors, activating the iCOD cell board results in two active
processors per cell board. That is, the iCOD software distributes the
number of active processors across the two cell boards. The total number
of active processors has not changed, so no payment for processors is due.
Table 9-2 Activation Fees — No Increase in Active Processors
Non-iCOD iCOD Cell

State Cell Board Board HP Activation Fees
Processors Processors
Before iCOD 4 active, 4 iCOD N/A

Cell Board 0 iCOD
Activation
After iCOD 2 active, 2 active, • Enablement fee for activated

Cell Board 2 iCOD 2 iCOD iCOD cell board
Activation
(No processor activation charges
because the number of total active
processors did not increase)
Chapter 9 105
iCOD Cell Board
iCOD Cell Board
Example 9-2 Activating an iCOD Cell Board and increasing the number of
total active processors
In a different scenario, activation of an iCOD cell board can cause the
number of requested active processors to be below the minimum required
(one active processor per cell board) and necessitate the purchase of the
newly activated iCOD processor. For example, if you have a two cell
board nPartition with one active processor on one cell board and three
iCOD processors, and an inactive (iCOD) cell board with four iCOD
processors, activating the iCOD cell board results in one active processor
per cell board. That is, the iCOD software distributes the number of
active processors across the two cell boards. The total number of active
processors has increased by one and payment for the processor
enablement fee is due.
Table 9-3 Activation Fees — Increase in Active Processors
Non-iCOD iCOD Cell

State Cell Board Board HP Activation Fees
Processors Processors
Before iCOD 1 active, 4 iCOD N/A

Cell Board 3 iCOD
Activation
After iCOD 1 active, 1 active, • Enablement fee for activated

Cell Board 3 iCOD 3 iCOD iCOD cell board
Activation
• Enablement fee for activated
iCOD processor
• HP-UX license and support fees
for activated iCOD processor
106 Chapter 9
iCOD Cell Board
iCOD Cell Board
Activation of an iCOD Cell Board

An iCOD cell board is configured so that it is assigned to a nPartition;
however, it does not participate in the boot of the nPartition. Activating
an iCOD cell board is a two step process:
Step 1. Set the iCOD cell board’s use-on-next-boot flag to “y”
Step 2. Perform a reboot of the nPartition
Example 9-3 Activating an iCOD cell board in cabinet 0, slot 5, nPartition 3

For example, changing the use-on-next-boot flag to “y” on the iCOD
cell board in cabinet 0, slot 5, in nPartition 3 can be accomplished via the
following command:
/usr/sbin/parmodify -p 3 -m 0/5::y:
See the HP System Partitions Guide for details about adding and
configuring cells in nPartitions.
After you have set the iCOD cell board’s use-on-next-boot flag to “y”,
and performed the reboot, you can use the icod_modify command to
activate iCOD processors that are listed as inactive processors that
can be activated (as reported by the icod_stat command).
The number of active processors in the nPartition remain the same after
the iCOD cell board is made active — unless prior to the iCOD cell
board’s activation the number of requested active processors is
greater than the number of active processors (as reported by the
icod_stat command).
Activating an iCOD cell board causes at least one processor to become
active on that cell board. However, this does not necessarily mean an
iCOD processor has been activated or that the total number of active
processors increases — unless the requirement of a minimum of one
active processor per active cell board could not be met without activating
a new processor. In summary, if the number of activated (and purchased)
processors in a nPartition equals (or exceeds) the number of active cell
boards, then the iCOD software does not automatically activate
additional iCOD processors.
See “iCOD Cell Board Activation Fees” on page 104 for more details on
activating an iCOD cell board.
Chapter 9 107
iCOD Cell Board
iCOD Cell Board
Accidental Activation of an iCOD Cell Board

If you inadvertently activate an iCOD cell board, you can de-activate it
by following this two step procedure:
Step 1. Set the iCOD cell board’s use-on-next-boot flag to “n”
Step 2. Perform a reboot of the nPartition
IMPORTANT You must deactivate the inadvertently activated cell board within five
days or the cell board is considered to be purchased from HP.
Example 9-4 Deactivating an iCOD cell board in cabinet 0, slot 5, nPartition 3

For example, changing the use-on-next-boot flag to “n” on the iCOD
cell board in cabinet 0, slot 5, in nPartition 3 can be accomplished via the
following command:
/usr/sbin/parmodify -p 3 -m 0/5::n:
The “n” in the above command line sets the cell board’s
use-on-next-boot flag to “no” and causes the cell board to not
participate in the nPartition when it is booted.
See the HP System Partitions Guide for details about adding and
configuring cells in nPartitions.
108 Chapter 9
A Offline Configuration and
Activation of Processors
This appendix describes managing your processors in offline activation
mode. If you are dynamically activating your inactive processors using
the online activation mode, you do not need to read this appendix.
This appendix includes:
• “Operating in Offline Activation Mode” on page 110 including a

summary of the basic steps when operating in offline activation
mode:
— “Converting Your System From the Default Online Activation

Mode to Offline Activation Mode” on page 110
— “Activating a Deconfigured Processor in Offline Activation Mode”
on page 111
— “Converting from Offline Activation Mode to Online Activation
Mode” on page 111
• “Receiving a System Alert on L-Class and N-Class on Hard Reset” on
page 113
• “Configuring and Activating Processors for the L-Class and N-Class
Servers” on page 114
• “Configuring and Activating Processors for the V-Class Server” on
page 120
• “Configuring and Activating Processors for Hardware-partitionable
Systems” on page 126
Refer to your hardware operating guide for additional information on
adding and configuring processors to your system or call your HP SR.
Appendix A 109
Offline Configuration and Activation of Processors
Operating in Offline Activation Mode

This section outlines the basic steps to take when operating in offline
activation mode in several situations.
Most software applications work fine with the online activation method.
However, some applications erroneously regard inactive processors to be
active processors. These types of applications may exhibit functional or
performance problems. Offline (manual) activation may be necessary for
these types of applications. In offline activation mode, the deactivated
processors are converted to deconfigured processors. iCOD software can
activate processors that are deactivated (inactive). However, iCOD
software cannot activate processors that are deconfigured.
NOTE The iCOD software deactivates processors by use of the icod_modify

command. The boot console handler (BCH) deconfigures processors.
Deconfigured processors cannot be activated by iCOD software.
Converting Your System From the Default Online

Activation Mode to Offline Activation Mode
The following steps outline what needs to be done if you are converting
your system from the default online activation mode to offline activation
mode. Following this procedure ensures that the application never runs
in an environment where deactivated processors may exist. The changes
in system state information is consistent with a non-iCOD system and
does not affect application operation:
System state:
• The system is booted
• One or more processors are deactivated by iCOD software
Procedure:
Step 1. Reboot the system and stop the boot process at BCH
Step 2. At BCH, deconfigure the (iCOD) deactivated processors per configuration

rules
110 Appendix A
Step 3. Boot the system
Activating a Deconfigured Processor in Offline

Activation Mode
At some time after you have deconfigured processors, you may desire to
activate the deconfigured processors. To accomplish this, you must first
convert the deconfigured processors into deactivated processors, and
then activate the processor.
The following steps outline what needs to be done if you want to activate
a deconfigured processor:
System state:

• One or more processors are deconfigured
• No processors are deactivated by iCOD software
Procedure:
Step 2. At BCH, configure processors per configuration rules
Step 3. Boot the system (iCOD software deactivates the previously deconfigured
processors — assuming you have not increased the number of requested
active processors)
Step 4. Execute icod_modify -a to instantly activate the newly configured

processors
Converting from Offline Activation Mode to Online

Activation Mode
Your iCOD system may currently be in offline activation mode and you
desire to return the system to online activation mode. To do this, you
need to make the deconfigured processors available for activation by the
iCOD software. That is, this procedure converts deconfigured processors
into deactivated processors.
The following steps outline what needs to be done to change your iCOD
system to online activation mode. In online activation mode, you can
instantly activate your inactive processors:
Appendix A 111
System state:

• One or more processors are deconfigured
• No processors are deactivated by iCOD software
Procedure:
Step 2. At BCH, configure processors per configuration rules

Step 3. Boot the system (iCOD software deactivates the previously deconfigured
processors)
Step 4. At any time after this, you can use icod_modify -a to instantly activate
the newly configured processors
NOTE Following this procedure results in the application running in an

environment with deactivated processors. System state information
reflects the deactivated processors, but is different than that reported by
a non-iCOD system. Some applications may notice the difference, but
most do not. This approach provides the intended level of flexibility for
those customers and applications that have been verified to work with
deactivated processors present on a system.
112 Appendix A
Receiving a System Alert on L-Class and N-Class on Hard Reset
Receiving a System Alert on L-Class and

N-Class on Hard Reset
When L-Class and N-Class iCOD systems undergo a hard reset, the PDC
firmware displays a level 6 system alert for each deconfigured processor.
A hard reset is accomplished by either cycling the power, or by entering
the RS (reset) command on the Management Processor (MP) interface.
Typing a CTRL-B on the system console displays the MP interface if it is
not already displayed. Situations requiring a hard reset are infrequent,
such as system hangs and during the boot process.
The system alert displays on the console during the selftest screens
before HP-UX begins to boot. After a deconfigured processor is activated
(configured), the system alert for that processor no longer appears.
These system alert messages identify processors disabled by Online
Diagnostics as a result of exceeding the threshold of Low-Priority
Machine Checks (LPMC). However, these system alert messages can be
ignored for deactivated processors, but should be acknowledged as per
the following example:
Example N-Class ***** EARLY BOOT VFP : SYSTEM ALERT ***** SYSTEM NAME:
System Alert for uninitialized
CPU number 6 DATE: 01/28/2000 TIME: 00:48:32
ALERT LEVEL: 6 = Boot possible, pending failure - action required
REASON FOR ALERT
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 6 PROBLEM DETAIL:

3 = functional failure
LEDs: RUN ATTENTION FAULT REMOTE POWER

FLASH FLASH OFF OFF ON
0x0000006311061620 F0000000 00000006 - type 0 = Data Field Unused

0x5800086311061620 00006400 1C003020 - type 11 = Timestamp
01/28/2000 00:48:32
A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display
Anything else redisplay the log entry
->Choice:a
Appendix A 113
Configuring and Activating Processors for the L-Class and N-Class Servers
Configuring and Activating Processors for the

L-Class and N-Class Servers
This section illustrates the procedure for configuring a processor on both
the L-Class and N-Class servers. The BCH interface is practically
identical for both classes of servers.
For additional information on the L- and N-Class boot sequence, and
other operating instructions, please consult the Server Boot Up section
in the Operating Instructions at: docs.hp.com/hpux/hw (for the
appropriate class of server — for example, N-Class).
NOTE Booting a system to the HP-UX prompt from the BCH main menu can be
time consuming, depending on your software and hardware
configuration.
An N-Class system can contain up to 8 processors. Configure these

processors in the following order:
• 1
• 3
• 5
• 7
• 0
• 2
• 4
• 6
Always deconfigure processors in the reverse order.
114 Appendix A
An L-Class system can contain up to 4 processors. Configure these

processors in the following order:
• 0
• 3
• 1
• 2
Always deconfigure processors in the reverse order.
Step 1. Reboot the system from the system console.
Step 2. Access the BCH interface. If autoboot is disabled, the system accesses
the BCH by default; otherwise, interrupt the boot process when
prompted by pressing any key.
---- Main Menu -------------------------------------------------------------

Command Description
------- -----------
BOot [PRI|ALT|<path>] Boot from specified path
PAth [PRI|ALT|CON|KEY] [<path>] Display or modify a path
SEArch [DIsplay|IPL] [<path>] Search for boot devices
COnfiguration menu Displays or sets boot values

INformation menu Displays hardware information
SERvice menu Displays service commands
DeBug menu Displays debug commands
MFG menu Displays manufacturing commands
DIsplay Redisplay the current menu

HElp [<menu>|<command>] Display help for menu or command
RESET Restart the system
----
Main Menu: Enter command or menu >
Appendix A 115
Step 3. Enter the IN PR command to display the processor information:
Main Menu: Enter command or menu > IN PR
Model: 9000/800/L2000-44
PROCESSOR INFORMATION
HVERSION SVERSION Processor

Processor Speed Model Model/Op CVERSION State
--------- -------- -------- -------- -------- -------------
0 440 MHz 0x05c4 0x0491 2. 0 Active
3 440 MHz 0x05c4 0x0491 2. 0 Stopped:Deconfigured
Central Bus Speed (in MHz) : 82

Software ID (dec) : 0
Software ID (hex) : 0x00000000
Software Capability : 0x01100000f0
---- Main Menu -------------------------------------------------------------

Command Description
------- -----------
PAth [PRI|ALT|CON|KEY] [<path>] Display or modify a path
COnfiguration menu Displays or sets boot values

INformation menu Displays hardware information
SERvice menu Displays service commands
DeBug menu Displays debug commands
MFG menu Displays manufacturing commands

HElp [<menu>|<command>] Display help for menu or command
----
In the above example two processors are on the system. Processor 0 is

configured and processor 3 is deconfigured.
116 Appendix A
Step 4. Enter the CO command to enter the configuration menu:
Main Menu: Enter command or menu > CO
---- Configuration Menu ------------------------------------------------------
Command Description
------- -----------
AUto [BOot|SEArch|STart] [ON|OFF] Display or set specified flag
BootID [<proc>] [<bootid>] Display or set Boot Identifier
BootINfo Display boot-related information
BootTimer [0 - 200] Seconds allowed for boot attempt
CPUconfig [<proc>] [ON|OFF] Config/Deconfig processor
DEfault Set the system to predefined values
FAn [HI|NORmal] Display or change fan speed
FastBoot [ON|OFF] Display or set boot tests execution
PAth [PRI|ALT] [<path>] Display or modify a path
TIme [c:y:m:d:h:m:[s]] Read or set the real time clock in GMT

HElp [<command>] Display help for specified command
MAin Return to Main Menu
----
Configuration Menu: Enter command >
Step 5. Use the CPU <processor number> ON command to configure the

processor. Repeat this step until all processors that are targeted for
activation are configured:
Configuration Menu: Enter command > CPU 3 ON
Changes will not take effect until next hard boot
PROCESSOR CONFIGURATION INFORMATION
Processor hpa Configuration Status

--------- ------------------ ----------------------------------------
3 0xfffffffffffa6000 Deconfigured, flagged to be reconfigured
Appendix A 117
Step 6. Use the CPU command to display processor information and verify that
the processors that are targeted for activation are flagged to be
configured:
Configuration Menu: Enter command > CPU
PROCESSOR CONFIGURATION INFORMATION
Processor hpa Configuration Status

--------- ------------------ ----------------------------------------
0 0xfffffffffffa0000 Configured, not flagged to be deconfigured
3 0xfffffffffffa6000 Deconfigured, flagged to be reconfigured
Step 7. Reset the system to configure the processors. Enter the command RESET
and boot the system to the HP-UX prompt:
Configuration Menu: Enter command > RESET
Step 8. At the system prompt, activate the configured processors with the
icod_modify command (see “Increasing Processor Capacity” on
page 58).
118 Appendix A
Step 9. Verify from HP-UX that the processors are available with the ioscan
HP-UX command. Note the information provided by ioscan on the
number of active processors is different from that reported during
configuration.
root@guinness> ioscan -fk|grep -i proc

processor 0 160 processor CLAIMED PROCESSOR Processor
root@guinness>
This completes the processor offline configuration and activation process

for the HP-UX N- and L-Class servers.
NOTE Deconfiguring Processors

Deconfiguring a processor is similar to configuring a processor, except
the deconfiguration order is the reverse of the configuration order. Also,
the command CPU # OFF is used for deconfiguring processors.
Appendix A 119
Configuring and Activating Processors for the V-Class Server
Configuring and Activating Processors for the

V-Class Server
This section illustrates the procedure for configuring or activating a
processor for the V-Class.
For additional information on the V-Class boot sequence and other
operating instructions please consult the V2500 Server Operator’s Guide
at: docs.hp.com/hpux/hw under V-Class.
Step 1. Reboot the system from the system console either remotely or from the
V-Class test station.
Step 2. Access the V-Class boot menu interface. If autoboot is disabled the
system displays the boot menu by default; otherwise, interrupt the boot
process when prompted by pressing any key.
Command Description
------- -----------
AUto [BOot|SEArch|Force ON|OFF] Display or set the specified flag
BOot [PRI|ALT|<path> <args>] Boot from a specified path
BootTimer [time] Display or set boot delay time
CLEARPIM Clear PIM storage
CPUconfig [<cpu>] [ON|OFF|SHOW] (De)Configure/Show Processor
DEfault Set the system to defined values
DIsplay Display this menu
ForthMode Switch to the Forth OBP interface
IO List the I/O devices in the system
LS [<path>|flash] List the boot or flash volume
PASSword Set the Forth password
PAth [PRI|ALT|CON] [<path>] Display or modify a path
PDT [CLEAR|DEBUG] Display/clear Non-Volatile PDT state
PIM_info [cpu#] [HPMC|TOC|LPMC] Display PIM of current or any CPU
RemoteCommand node# command Execute command on a remote node
RESET [hard|debug] Force a reset of the system
RESTrict [ON|OFF] Display/Select restricted access to Forth
SCSI [INIT|RATE] [bus slot val] List/Set SCSI controller parms
SEArch [<path>] Search for boot devices
SECure [ON|OFF] Display or set secure boot mode
TIme [cn:yr:mo:dy:hr:mn[:ss]] Display or set the real-time clock
VErsion Display the firmware versions
[0] Command:
120 Appendix A
Step 3. Enter the CPU command to display the processor information:
[0] Command: CPU
Processor Configuration Status

--------- --------------------
0 Processor configured, not flagged to be deconfigured
1 Processor not installed
10 Processor deconfigured : by user.
26 Processor deconfigured : by user.
Processor not installed
[0] Command:
Appendix A 121
Step 4. Determine if the V-Class has Single or Dual Processor Boards.
Determining if the V-Class has Single or Dual Processor Boards
If there are a pair processors numbered n and n+16 then the system uses dual
processor boards. In the example below there are two processors numbered 0
and 16; therefore, the system uses dual processor boards and the two
processors reside on one processor board. Otherwise, the system uses single
processor boards. In this example, there are a pair of deconfigured processors
10 and 26 that reside on a dual processor board.
If the V-Class uses dual processor boards, then the two processors residing on
the dual processor board must be configured as a pair. Additionally, each pair
of processors must be configured in the sequence illustrated in the following
table under “Dual Processor Board Configuration Sequence.”
In the dual processor board example being outlined, processors 10 and 26
reside on one dual processor board and must be configured after the processor
pair 2 and 18. Processors 10 and 26 are configured as a pair as illustrated
below.
The CPU processor number ON command configures the deconfigured
processors. Repeat the command until all processors that are targeted for
activation are configured.
Always deconfigure processors (CPU processor number OFF> in the reverse
order.
122 Appendix A
Dual Processor Board

Configuration Sequence
0 and 16
8 and 24
2 and 18
10 and 26
5 and 21
13 and 29
7 and 23
15 and 31
1 and 17
9 and 25
3 and 19
11 and 27
4 and 20
12 and 28
6 and 22
14 and 30
Step 5. Configure the processor with the following command (in this example,
we are configuring processors 10 and 26):
[0] Command: CPU 10 ON
[0] Command: CPU 26 ON
Step 6. Use the CPU command to verify that the processors have been properly
configured:
[0] Command: CPU
Processor Configuration Status

--------- --------------------
Appendix A 123

[0] Command:
Step 7. Reset the system to configure the processors. Enter the command RESET.
Boot the system to the HP-UX prompt.
[0] Command: RESET
Step 8. At the system prompt, activate the configured processors with the
icod_modify command (see “Increasing Processor Capacity” on
page 58).
Step 9. Verify that the processors are available with the ioscan
HP-UX command. Note the information provided by ioscan on the
number of active processors is different from that reported during
configuration.
/> ioscan -fk|grep -i proc

124 Appendix A

/>
This completes the processor offline configuration and activation process

for the HP-UX V-Class server.
NOTE Deconfiguring Processors

To deconfigure a processor, refer to the Table on page 123 and use the
reverse order of the configuration sequence.
Appendix A 125
Configuring and Activating Processors for Hardware-partitionable Systems
Configuring and Activating Processors for

Activation of processors in offline activation mode on
hardware-partitionable systems is not a user executable operation. If you
use the offline activation method, and you wish to activate a processor,
you need to contact your HP service representative.
126 Appendix A
B Special Considerations
This appendix describes special considerations for iCOD systems.

This appendix includes:
• “iCOD and pstat, pstat_getdynamic, and mpctl System Calls” on

page 128 including a summary of the basic steps when operating in
offline activation mode:
— “pstat” on page 128

— “mpctl” on page 129
— “Affected HP-UX Commands” on page 129
• “Measurement Software on iCOD Systems” on page 130
• “Differences Between Supported Platforms” on page 131
• “Firmware Requirements” on page 133
• “Dynamic Processor Resilience (DPR)” on page 134
• “Requested Active Processors Below Minimum Required” on
page 135
Refer to your hardware operating guide for additional information on
adding and configuring processors to your system or call your HP service
representative.
Appendix B 127
Special Considerations
iCOD and pstat, pstat_getdynamic, and mpctl System Calls
iCOD and pstat, pstat_getdynamic, and mpctl

System Calls
Applications that are dependent on the number of active processors most
likely depend on the system calls pstat and mpctl.
pstat
pstat_getdynamic now returns the number of active processors in
pst_dynamic.psd_proc_cnt. In the original release of HP-UX 11.00, it
was always the same as pst_dynamic.psd_max_proc_cnt. That field
now includes deactivated processors.
In the past, a call to pstat_getdynamic returned fields psd_proc_cnt
(number of active processors) and psd_max_proc_cnt (maximum
number of active processors), and they usually had the same value. This
is because all processors in the system were usually active.
Consequently, these fields could be used interchangeably even though
they had different meanings. With iCOD systems, these fields are no
longer interchangeable.
Four other fields are adjusted in pst_dynamic structure. They are
psd_avg_1_min, psd_avg_5_min, psd_avg_15_min, and
psd_cpu_time[].
psd_avg_1_min is calculated by summing up the corresponding entries
in psd_mp_avg_1_min[] and dividing by psd_max_proc_cnt. In effect,
psd_avg_1_min reflects the average values of psd_mp_avg_1_min[]. The
change is made to exclude the values of the deactivated processors when
summing up entries in psd_mp_avg_1_min[]. The sum is then divided
by psd_proc_cnt. Thus, values of deactivated processors are not taken
into account for each load average value. psd_avg_5_min and
psd_avg_15_min is adjusted in a similar way.
Similarly, psd_cpu_time[i] reflects the average values in
psd_mp_cpu_time[][i]. Again, the adjustment is to exclude the values
of deactivated processors in psd_mp_cpu_time[][i] and the sum is then
divided by psd_proc_cnt. Thus, values of deactivated processors are not
taken into account for each load average value.
128 Appendix B
iCOD and pstat, pstat_getdynamic, and mpctl System Calls
Note that even though these average fields are adjusted, no information
is lost because psd_mp_avg_*_min and psd_mp_cpu_time[] still contain
deactivated processor values.
mpctl
MPC_GETNUMSPUS now returns the number of activated processors.
Earlier versions of this command reported activated and deactivated
processors in this field.
MPC_GETFIRSTSPU now returns the first activated processor.
MPC_GETNEXTSPU now returns the next activated processor and skips
deactivated ones.
MPC_GETNUMSPUS, MPC_GETFIRSTSPU and MPC_GETNEXTSPU now take
into account deactivated processors. MPC_GETNUMSPUS does not count
deactivated processors and the other two options do not return
deactivated processors’ indices.
Affected HP-UX Commands

pstat() and mpctl() required changes to the following HP-UX
commands in order to work properly on HP-UX systems:
• top
• sar
• vmstat
• iostat
• uptime
Patches for these commands are required before installing iCOD B.05.x
on HP-UX 11.0. No commands patches are required on HP-UX 11i v1.
Appendix B 129
Measurement Software on iCOD Systems
Measurement Software on iCOD Systems

iCOD systems inherently have fewer active processors than the total
number of processors in the system. This fundamental difference
between the number of active processors and the total number of
processors can cause some processor measurement products and utilities
to report incorrect information. Additionally, when a processor is
dynamically activated, some software products must recognize the
change in the number of active processors in order to report correct
processor related information.
The iCOD system behavior described above along with the associated
system call changes described in the previous section (“iCOD and pstat,
pstat_getdynamic, and mpctl System Calls” on page 128) requires close
examination of and possible changes to measurement related software to
ensure they work properly on iCOD systems. Some non-measurement
applications may also be impacted.
HP’s OpenView measurement software and some HP-UX commands
were modified to work properly on iCOD systems. For example, the
HP-UX commands top and sar were modified in order to report correct
information on iCOD systems.
OpenView Measurement Products

OpenView measurement products, such as MeasureWare and
GlancePlus, must be version C.02.60 or later to provide correct processor
measurements. OpenView measurement products, version C.02.60 or
later, behave correctly on iCOD systems. Earlier versions of the
OpenView measurement products do not work correctly on iCOD
systems.
On Superdome On Superdome systems HP recommends updating to the GlancePlus Pak

Systems version C.03.20 or later.
Other Measurement Software

Please check with your measurement software vendor to ensure their
software works properly on iCOD systems and update the measurement
software versions as needed.
130 Appendix B
Differences Between Supported Platforms

With the iCOD software, HP enterprise servers that are single partition
machines — for example: L-, N-, and V-Class servers — have a few
differences with multi partition machines, such as Superdome. The
differences are summarized as follows.
L-, N-, and V-Class Systems

System alerts are handled differently on L- and N-Class systems. See
“Receiving a System Alert on L-Class and N-Class on Hard Reset” on
In offline configuration mode, processor configurations are performed
differently on L- and N-Class systems than on V-Class systems. For L-
and N-Class systems, see “Configuring and Activating Processors for the
L-Class and N-Class Servers” on page 114 for details. For V-Class
systems, see “Configuring and Activating Processors for the V-Class
Server” on page 120 for details.
Activation of processors in offline activation mode on
hardware-partitionable systems (for example: rp7410, rp8400, and
Superdome) is not a user executable operation. If you use the offline
activation method and you wish to activate a processor, you need to
contact your HP service representative.
Load balancing capability can be accomplished by redistributing
processors across partitions. See “Load-balancing Active Processors” on
NOTE The Utility subsystem firmware version must be 6.40 or greater on

Superdome. The iCOD software is not supported on firmware versions
prior to 6.40.
Appendix B 131
On iCOD When running the iCOD software on hardware-partitionable systems,

Superdome the number of iCOD processors is audited for your complex as a whole,
Systems: not an individual partition. iCOD software must be installed and
configured on all partitions that contain iCOD processors. It is important
not to remove the iCOD software from all partitions in your complex
unless you have activated and purchased all iCOD processors.
Activation of processors in offline activation mode on Superdome systems
is not a user executable operation. If you use the offline activation
method and you wish to activate a processor, you need to contact your
HP service representative.
If you are running OpenView measurement products, such as the
GlancePlus Pak, HP recommends that you update to version C.03.20 or
later.
Also, see the information on “Too Many Processors Activated on iCOD”
on page 74, in the Frequently Asked Questions chapter.
132 Appendix B
Firmware Requirements
Firmware Requirements
V-Class Systems
On V-Class iCOD systems, V-Class firmware upgrade V2500/V2600
Test Station Software Release 3.1 or greater is required.
Superdome Systems
The Utility subsystem firmware version must be 6.40 or greater. The
iCOD software is not supported on firmware versions prior to 6.40.
Appendix B 133
Dynamic Processor Resilience (DPR)
Dynamic Processor Resilience (DPR)

The LPMC monitor, within the Support Tools Manager (STM)
diagnostics, generates Information events for all cache errors that are
detected. After three errors (Threshold) have been detected on a
processor in 1440 minutes, or a 24-hour period of time (Period), the
monitor deactivates that particular processor, mark it for
deconfiguration on the next system reboot, and generate a SERIOUS
event. After the failed processor is deactivated, the LPMC monitor
attempts to activate one of the inactive iCOD processors, if any are
available. This method ensures the processing power of the system is
unchanged.
A default value of “three” is assigned to Threshold, except for the
PCX-W+ family of processors, which has a value of “five” assigned. The
default value assigned to a Period is 1440 minutes, or 24 hours, in all
possible processor configurations.
NOTE Dynamic processor resilience is supported only if the inactive iCOD

processors are configured for on-line activation.
V-Class Systems A V-Class system has a slight variation from: L-2000, N-Class,
Superdome, rp7410, and rp8400. This is because the V2500 and V2600
systems have dual processor boards. As a result, only the failing
processor is deactivated, and after the system reboots, the pair of
processors are deconfigured.
vPars In a vPar environment, processors deactivated by the LPMC monitor

must be manually replaced. See “LPMC Deactivations in vPars” on
Monarch See “Failed Monarch Processors” on page 70 for details on replacing

Processors failed monarch processors.
134 Appendix B
Requested Active Processors Below Minimum Required
Requested Active Processors Below Minimum

Required
For Partitionable Your iCOD system has a minimum number of processors that are
iCOD Systems required to be activated. The minimum number of active processors in a
partition is one per cell board.
If the requested number of active processors is less than the required
minimum number of active processors, the system contact for your iCOD
system receives a notification e-mail message.
This can happen if a new cell board was activated on your iCOD system,
which increased the required minimum number of active processors.
For example, an iCOD partition has two requested active processors and
two active cell boards. If two additional cell boards are added to the
partition, the required minimum number of active processors becomes
four. Because the number of requested active processors (two) is less
than the required minimum number of active processors (four), a
notification e-mail message is sent to the system contact.
Example B-1 E-mail: Requested Active Processors Below Minimum Required

Subject: iCOD: Requested Active Processors Below Minimum Required
This mail is being automatically sent from system zooVpar0,

which is under an iCOD contract.
Upon boot, it was detected that the number of requested active

processors (2) was less than the minimum number of required active
processors (4). As a result, there are more active processors
on this system than requested. One way that this can happen is if
a new cell board was activated, which increased the minimum
number of processors required to be active on the system.
Having more active processors than requested usually means that

one or more iCOD processors have been activated and must be paid
for.
Appendix B 135
Requested Active Processors Below Minimum Required
136 Appendix B
C Glossary
Appendix C 137
Glossary
iCOD Terminology
iCOD Terminology
The following terms are commonly used in conjunction with iCOD:
activated processors
Processors that have been turned on by the iCOD
software or during installation. Processors are
activated with the icod_modify command while
HP-UX is running.
add-on system
A non-iCOD system that has been converted to an
iCOD system. This process is performed by a HP
service representative.
bound processor
Bound processors have I/O interrupts assigned to
them. Because HP-UX cannot migrate I/O interrupts to
or from a processor, you cannot dynamically add or
remove bound processors to or from a vPar.
configured processors
Processors that have been configured at the boot
interface and are now available for activation.
deactivated processors
Processors that either have not yet been activated or
that have been turned off by the iCOD software and
returned to the pool of inactive processors. These
processors are available for activation.
Note that new HP-UX processes are not assigned to a

deactivated processor and all processes running on the
deactivated processor are migrated to other processors
(with the exception that interrupt handlers may not be
migrated from deactivated processors).
138 Appendix C
Glossary
iCOD Terminology
deconfigured processors
Processors that have not yet been configured at the
boot console interface (BCH). The iCOD software
cannot activate a processor that is deconfigured.
enablement fee
The fee a customer pays to activate and use an iCOD
processor. This fee pertains to only the iCOD program.
hard partition
A physical partitioning of a computer that divides the
computer into groups of cell boards where each group
operates independently of the other groups. A hard
partition can run a single instance of HP-UX or be
further divided into virtual partitions. Hard partitions
are also referred to as “nPartitions”.
icod processors
Processors that are physically installed in an iCOD
system, but are not activated. iCOD processors can be
turned on by the iCOD software or during installation.
iCOD processors are activated with the icod_modify
command while HP-UX is running.
icod-purchase
The HP product name of the iCOD software. The HP
product number for icod-purchase is B9073AA.
icod-utility
The HP product name of the pay per use (PPU)
software. The HP product number for icod-utility is
T1322AA.
inactive cell
On a hardware-partitionable system, a cell that is
either powered off, or in a state prior to BCH, defined
as “waiting on SINC_BIB”.
inactive partition
A partition where all of the cells in the partition are
inactive.
Appendix C 139
Glossary
iCOD Terminology
inactive processor
A processor in an iCOD system that is currently
inactive, but is capable of activation by use of the
icod_modify command. An inactive processor is also
referred to as a “deactivated processor”.
migrating processors
The process of activating and deactivating processors
across partitions for load-balancing. See
“Load-balancing Active Processors” on page 61 for more
information.
monarch processor
This is the main controlling processor from the
perspective of the operating system. This processor is
designated as CPU 0. The LPMC monitor does not
deactivate/replace a failing monarch processor.
online activation
The ability to activate a deactivated processor while
HP-UX is running. No reboot is required. This is done
by using the icod_modify command. This is the
default behavior of iCOD.
offline configuration and activation
To manually configure a processor for activation from
the boot interface, boot to the system prompt, and then
use the icod_modify command to activate the
processor as you would in the online activation mode (a
two step process). A reboot is required for offline
configuration.
pay per use
The HP On Demand Solutions program that is a
pricing model in which you are charged for actual
processor usage. You acquire a specific hardware
platform, and number of processors, and are charged
for the actual usage, based on the number of active
processors in the complex.
140 Appendix C
Glossary
iCOD Terminology
right to access
The initial fee a customer pays to enter the iCOD
program and physically acquire possession of an iCOD
(inactive) processor.
temporary capacity
An HP product that enables customers to purchase
prepaid processor activation rights, for a specified
(temporary) period of time. Temporary capacity is sold
in 30 processor-day increments. Temporary capacity is
available on HP-UX 11i v1 only.
unbound processor
Unbound processors do not have I/O interrupts
assigned to them and can dynamically migrate from
one vPar to another.
virtual partition
A software partitioning of a computer or hard partition
where each virtual partition contains an instance of an
operating system. Though a hard partition can contain
multiple virtual partitions, the inverse is not true (that
is, a virtual partition cannot span hard partition
boundaries). Virtual partitions are also referred to as
“vPars”.
Appendix C 141
Glossary
iCOD Terminology
142 Appendix C
D iCOD Manpages
This appendix contains the manpages for iCOD commands.

The manpages are:
• “iCOD (5) Manpage” on page 144 — an overview of iCOD commands

and their usage
• “icod_modify (1M) Manpage” on page 148 — how to activate and
deactivate processors in your iCOD system, change system contact
information, and apply a software license to use
• “icod_notify (1M) Manpage” on page 151 — how to manage asset
notification to HP
• “icod_stat (1M) Manpage” on page 154 — how to display processor
status, usage information, and system information
NOTE The information contained in the following manpages is current at the

time of publication for this manual.
Appendix D 143
iCOD Manpages
iCOD (5) Manpage
iCOD (5) Manpage
iCOD (5)
NAME
iCOD – instant Capacity on Demand software for HP-UX
DESCRIPTION
iCOD provides services for instantly increasing processing capacity on
supported HP servers to respond to increasing system demands. When
the processing demand significantly changes, the user executes the
icod_modify (see icod_modify (1M)) command to instantly activate or
deactivate processors, or defer an activation or deactivation until the
next reboot.
Initializing an iCOD Server

iCOD is typically installed by HP manufacturing on instantly ignited
systems or can be installed by an HP support representative on existing
supported servers as an add-on. After iCOD has been installed on a
system, a system contact must be specified and a free license applied.
Complete the configuration as follows:
1) Use the icod_modify -c command (see icod_modify
(1M)) to configure contact information (name, phone,
e-mail address). This information is used by HP to send
licensing instructions to the system contact.
2) Use the icod_stat (see icod_stat (1M)) command to
check the current status of the iCOD processors and
verify that the contact information is set properly.
144 Appendix D
iCOD Manpages
iCOD (5) Manpage
3) Execute the icod_notify command (see icod_notify

(1M)) to send an asset report to both HP and to the
system contact e-mail address. HP will respond to this
asset report by sending a second e-mail to the system
contact address. This verifies that e-mail
communication with HP has been established. E-mail
communication is required between the iCOD server
and HP because iCOD servers are required to send
asset reports to HP to report iCOD processor usage.
The reply e-mail, which is sent from HP to the contact
e-mail address will contain a confirmation message and
a license to use the iCOD software to activate or
deactivate processors (see Software Licensing).
Increasing Capacity
Once the free iCOD software license has been applied, iCOD processors
can be activated as needs dictate by use of the icod_modify command
(see icod_modify (1M)). An enablement fee must be paid to HP for every
iCOD processor that is permanently activated.
Software Licensing
Before iCOD software can be used to activate and deactivate processors,
a free license to use must be applied via the icod_modify command.
This license is obtained by executing the icod_notify command which
initiates a response from HP to the system contact e-mail address. This
e-mail contains the free license to use required for processor
activation and deactivation, and instructions for how to apply it.
Appendix D 145
iCOD Manpages
iCOD (5) Manpage
Software Removal
After all contractual obligations have been satisfied, the iCOD software
bundle can be uninstalled from the system using the swremove command
(see swremove (1M)).
NOTE: iCOD software cannot be removed from a system until all
processors in the system have been activated.
Hardware-Partitionable Systems (e.g. Superdome)

Hardware-partitionable systems support more than one instance of an
operating system by partitioning the system into separate systems.
When iCOD is running on this type of system, special consideration must
be taken when creating partitions, removing partitions, and moving cells
between partitions.
For more details about these special considerations, please read the
iCOD User's Guide available at /usr/share/doc/icodUserGuide.pdf.
Contractual Status Of iCOD Processors

Information about the number of iCOD processors (inactive processors
for which an enablement fee has not been paid) remaining on a system
can be obtained by executing the icod_notify command, which will
cause HP to respond via e-mail to the system contact e-mail address.
This response will contain, among other things, the number of iCOD
processors remaining on this system.
Virtual Partitions
iCOD processors may be present in systems or partitions where virtual
partition technology is employed. In a virtual partition environment,
processors which are not assigned to any virtual partition are considered
inactive (in addition to other classes of inactive processors). Unassigned
processors can be assigned by either the icod_modify command or the
vparmodify command (see vparmodify (1M)). Assignment via the
vparmodify command does not result in logging of the activation, e-mail
change notification, or transmission of an asset report to HP (although
the daily report will contain this information). HP recommends using the
icod_modify command when activating or deactivating processors in a
virtual partition where iCOD processors are present.
See vparmodify (1M) for more information on virtual partitions.
146 Appendix D
iCOD Manpages
iCOD (5) Manpage
Processor Sets
In an environment where processor sets are being used, icod_modify
will activate iCOD processors into the default processor set and will
deactivate processors only from the default processor set. Activation or
deactivation of processors in non-default processor sets is a two step
operation, where one step is the migration of processors into or out of the
default processor set and the other step is the activation or deactivation
of those processors.
See psrset (1M) for more information on processors sets.
Temporary Capacity Program

NOTE: Support for this program starts with HP-UX 11.11.
iCOD processors may include an amount of temporary capacity time.
This temporary capacity allows an iCOD processor to be activated for the
specified period of time without requiring the payment of an enablement
fee to HP for the permanent activation of the processor.
The temporary capacity associated with each iCOD processor is pooled.
Thus, the period of time that an iCOD processor is active will be
subtracted from the pool of temporary capacity time associated with all
iCOD processors.
Information about the amount of temporary capacity time remaining on
a system can be obtained from HP by executing the icod_notify
command, which will cause HP to respond via e-mail to the system
contact e-mail address. This response will contain, among other things,
the amount of temporary capacity time remaining for this system.
SEE ALSO
icod_modify (1M), icod_notify (1M), icod_stat (1M).
Appendix D 147
iCOD Manpages
icod_modify (1M) Manpage
icod_modify (1M)
NAME
icod_modify – activate and deactivate instant Capacity on Demand (iCOD)
processors, change system contact information, and apply a software license to
use
SYNOPSIS
/usr/sbin/icod_modify -c <name:e-mail:phone>
/usr/sbin/icod_modify -l <license>
/usr/sbin/icod_modify -f <from_address>
icod_modify [-D] -a <n>
<[desc]:usr_name:mgr_name:mgr_e-mail:mgr_phone>
icod_modify [-D] -d <n>
icod_modify [-D] -s <n>
DESCRIPTION
Use icod_modify to activate or deactivate iCOD processors, apply a
software license to use as well as set system contact information.
Changes to the number of active processors using this command are
persistent (survive system reboot).
For detailed information on the use of this command and interactions it
has with other aspects of the system, view the iCOD User's Guide located
at /usr/share/doc/icodUserGuide.pdf.
148 Appendix D
iCOD Manpages
Options and Arguments

icod_modify recognizes the following options and arguments:
-c <name:e-mail:phone> Changes the system contact information,
where name is the system contact name, e-mail is the
system contact e-mail address, and phone is the system
contact phone number. This information is used by HP
so that information requested via the icod_notify
command can be returned via e-mail.
-l <license> Applies a software license to use to the system.
Before the iCOD software allows activation and
deactivation of processors, a license to use (provided
by HP) must be applied.
-f <from_address> Causes all e-mail correspondence from this system
to be sent from from_address. Specifying a null string
will return to default behavior, which is to send from
the adm user on the local system.
-a <n> Activates n processors.
-d <n> Deactivates n processors.
-s <n> Sets the number of active processors to n.
-D Defers a processor activation or deactivation until the
next reboot. By default, activation or deactivation is
instant. NOTE: this option is not supported within a
virtual partition.
desc Optional description to help customers identify this
change. This description becomes part of the change
record for this activation/deactivation which can be
viewed by executing icod_stat -u.
usr_name Name of the user performing the processor activation
or deactivation.
mgr_name Name of the manager authorizing the processor
activation or deactivation.
mgr_e-mail E-mail address of the authorizing manager.
mgr_phone Phone number of the authorizing manager.
Appendix D 149
iCOD Manpages
EXTERNAL INFLUENCES
Environment Variables
• LANG determines the locale to use for the locale categories when both
LC_ALL and the corresponding environment variable (beginning with
LC_) do not specify a locale. If LANG is not set or is set to the empty
string, a default of “C” is used (see lang (5)).
• LC_CTYPE determines the interpretation of single- and multi-byte
characters.
• LC_TIME determines the date and time strings output.
• LC_MESSAGES determines the language in which messages are
displayed.
If any internationalization variable contains an invalid setting,
icod_modify behaves as if all internationalization variables are set
to “C” (see environ (5)).
International Code Set Support

Single- and multi-byte character code sets are supported. However, input
to the command must be entered using ASCII characters only.
RETURN VALUE
icod_modify exits with one of these values:
0 Command succeeded.
>0 Command failed; error message sent to STDERR.
AUTHOR
icod_modify was developed by HP.
SEE ALSO
icod_notify (1M), icod_stat (1M), icod (5).
150 Appendix D
iCOD Manpages
icod_notify (1M) Manpage
icod_notify (1M)
NAME
icod_notify – send asset reports to HP for instant Capacity on Demand (iCOD). Turn
change notification on or off. Request response e-mail from HP.
SYNOPSIS
/usr/sbin/icod_notify -c
/usr/sbin/icod_notify -n on|off
DESCRIPTION
If no options are specified to icod_notify, an asset report e-mail is sent
to HP, root and the system contact e-mail address (see icod_stat (1M)).
Confirmation e-mail is sent from HP to the system contact e-mail
address indicating that HP received the asset report e-mail.
The confirmation e-mail contains the free license to use required for
processor activation and deactivation, and instructions for how to apply
it. In addition, this e-mail will contain information about the status of
iCOD components in the system. This information may include: the
number of remaining iCOD processors, the remaining temporary
capacity time, and other information relevant to the state of the system.
Appendix D 151
iCOD Manpages
Options
icod_notify recognizes these options:
-c Sends asset report e-mail only to HP. Asset report
e-mail will not be sent to root and the system contact
e-mail address, and a confirmation e-mail will not be
sent to the system contact e-mail address from HP.
However, if a license to use hasn't been applied to
this system, licensing instructions will be sent to the
system contact e-mail address (or root if not specified).
-n on|off Turns change notification on or off. If specified on and
executing icod_modify results in a processor
configuration change, notification e-mail is sent to the
system contact and authorizing manager summarizing
the processor configuration change. This notification
e-mail can be turned off by specifying off.
icod_notify does not accept multiple command-line options.
EXTERNAL INFLUENCES
• LC_CTYPE determines the interpretation of single- and multi-byte
characters.
• LC_MESSAGES determines the language in which messages are
displayed.
icod_notify behaves as if all internationalization variables are set
to “C” (see environ (5)).
152 Appendix D
iCOD Manpages
International Code Set Support

Single- and multi-byte character code sets are supported.
RETURN VALUE
icod_notify exits with one of these values:
>0 Command failed; error message sent to STDERR.
AUTHOR
icod_notify was developed by HP.
SEE ALSO
icod_modify (1M), icod_stat (1M), icod (5).
Appendix D 153
iCOD Manpages
icod_stat (1M) Manpage
icod_stat (1M)
NAME
icod_stat – display instant Capacity on Demand (iCOD) processor status, usage
information, and system information
SYNOPSIS
/usr/sbin/icod_stat [-pv]
/usr/sbin/icod_stat -a|i|I|t|r
/usr/sbin/icod_stat -u
DESCRIPTION
The icod_stat command displays the processor status, usage
information, and system information on a system equipped with iCOD
processors. If no options are specified icod_stat displays:
Version: This field displays the version of the iCOD client
software.
Contract type: This field displays iCOD-purchase identifying that this
system is under an iCOD contract.
Licensed applied: This field indicates whether the license to use the
iCOD software has been applied.
Hostname: This field displays the system hostname as returned by
the hostname command (see hostname (1)).
DNS domain name: This field displays the system's fully qualified
domain name, for example: system.corp.com.
IP address: This field displays the Internet Protocol address
associated with the system's fully qualified domain
name.
NIS domain name: This field displays the Network Information Service
domain (if any) for the system.
154 Appendix D
iCOD Manpages
System model: This field displays the model of the system as returned
by the model command (see model (1)).
Serial number: This field displays the system's serial number.
Software ID: This field displays a unique identifier for the system as
returned by the getconf command (see getconf (1)).
Contact name: This field displays the system contact name for this
system, as specified by the user via the icod_modify
command.
Contact e-mail: This field displays the internet e-mail address for the
system contact. This may be an e-mail alias. This
address is used for sending copies of asset reports,
acknowledgements & licensing instructions from HP,
and change notifications from the icod_modify
command.
Contact phone: This field displays the phone number for the system
contact.
From e-mail: This field displays the e-mail address that will be
specified as the sender of all iCOD initiated
correspondence. This field is set via the icod_modify
command. If not set, e-mail will be sent from the adm
user on the local system.
Appendix D 155
iCOD Manpages
Information displayed for non-virtual partitions

The following status is displayed when icod_stat is run on a
non-partitionable system or on a hardware partition where virtual
partitions are not being used:
Total processors: This field displays the total number of processors
physically present in the system.
Active processors: This field displays the number of processors being
used by the operating system.
Inactive processors that can be activated: This field displays the number
of inactive processors immediately available for
activation.
Inactive processors that cannot be activated: This field displays the
number of processors deactivated by other software.
This may include processors deactivated due to LPMCs
(Low Priority Machine Checks). These processors are
not available for instant activation.
Deconfigured processors: This field displays the number of processors
deconfigured at the firmware level and not visible to
the operating system. These processors are not
available for instant activation.
Requested active processors: This field displays the number of processors
requested to be active for this system.
156 Appendix D
iCOD Manpages
Information displayed for virtual partitions

The following status is displayed when icod_stat is run on a virtual
partition:
Assigned processors: This field displays the number of processors
assigned to the local virtual partition.
Active assigned processors: This field displays the number of assigned
processors in the local virtual partition that are active.
Inactive assigned processors: This field displays the number of assigned
processors in the local virtual partition that are not
active.
Unassigned processors that can be assigned: This field displays the
number of unassigned processors in the
non-partitionable system or hardware partition that
are not assigned to the local virtual partition and can
be instantly assigned.
Unassigned processors that cannot be assigned: This field displays the
number of unassigned processors in the
non-partitionable system or hardware partition that
are not assigned to the local virtual partition and
cannot be instantly assigned. Bound processors at the
time the local virtual partition booted, if unbound later,
cannot be instantly assigned to the local virtual
partition without an intervening reboot.
Appendix D 157
iCOD Manpages
Options
icod_stat recognizes these options:
-a Displays the number of active processors on the
system.
-i Displays the number of inactive processors available
for instant activation. For virtual partitions, displays
the number of unassigned processors that can be
instantly assigned to the local virtual partition.
-I Displays the total number of inactive processors. This
number includes any deconfigured processors and
inactive processors that cannot be activated.
-p If running in a partitionable system (in a hardware
partition or a virtual partition), displays the status of
the local partition as well as a table showing
information about other partitions.
-r Displays the revision of the iCOD client software.
-t Displays the total number of processors physically
present on the system. For virtual partitions, this is
the number of assigned processors in the virtual
partition.
-u Displays a record of changes to processor configuration
and processor usage. Information displayed includes
(oldest to newest):
Date: The date and time that the change
took place.
Log type: The type of event that caused this log
entry; either system startup, system
shutdown, configuration change or
periodic usage.
Total processors: The total number of processors
physically present in the system.
Active processors: The number of processors being used
by the operating system at the time
the log entry was written.
158 Appendix D
iCOD Manpages
Requested active processors: The number of processors

the user requested to be active.
Description: A user specified description
documenting why processors were
activated or deactivated.
Changed by: The name of the individual
performing the change to the
configuration.
Manager: The name of the manager or the
individual granting approval for the
change.
E-mail address: The e-mail address of the authorizing
manager.
Phone number: The phone number of the authorizing
manager.
-v Displays verbose output. Displays the same output

available when specifying the -p and -u options.
Appendix D 159
iCOD Manpages
EXTERNAL INFLUENCES
• LC_TIME determines the date and time strings output.
• LC_MESSAGES determines the language in which messages (other
than the date and time strings) are displayed.

icod_stat behaves as if all internationalization variables are set to
“C” (see environ (5)).
RETURN VALUE
icod_stat exits with one of these values:
2 Command succeeded; system is not an iCOD system.
>0,!=2 Command failed; error message sent to STDERR.
AUTHOR
icod_stat was developed by HP.
SEE ALSO
icod_modify (1M), icod_notify (1M), icod (5).
160 Appendix D
Index
A applying license, 37
activated processors, defined, 138 checking system status, 57
activation modes, online and offline, 66 icod_stat on iCOD Superdome, 57, 94
add-on system, defined, 138 processor activation, 59
asset report processor deactivation on Superdome, 60
e-mail example, 34 setting system contact information, 55
information sent to HP, 31
testing e-mail transmission, 35 F
authorizing manager, role requirement, 36
failed processor replacement, 70
firmware requirements
B Superdome, 133
bound processor, defined, 138 V-Class, 133
frequently asked questions
C iCOD software, 78
cell,moving, 64 PPU software, 78
configuration change notification, 52 Superdome, 82
configured processors, defined, 138
configuring processors G
L- and N-Class, 114 golden image installation, 48
Superdome, 126
V-Class, 120 H
conventions, User’s Guide, 18
cron configuration requirements, 23 hard partition, defined, 139
D I
deactivated processors, defined, 138 iCOD
deconfigured processors, defined, 139 affected HP-UX commands, 129
deconfiguring processors compatibility with Psets, 97
L- and N-Class, 119 compatibility with vPars, 90
V-Class, 125 enablement fee for activation, 58
deferred activation HP-UX 11.0 requirements, 21
benefit, 58 HP-UX 11i requirements, 22
overriding, 62 icod_stat example on Superdome, 57, 94
deferred deactivation install from HP software depot on HP-UX
benefit, 60 11.0, 44
overriding, 62 install from HP software depot on HP-UX
differences in supported platforms, 131 11i, 45
dynamic processor resilience, 134, 135 install from Support Plus CD on HP-UX
11.0, 43
E install from Support Plus CD on HP-UX
e-mail configuration, 25 11i, 44
e-mail example measurement software, 130
acknowledgement of asset report, 35 mpctl system call, 129
asset report, 34 pstat system call, 128
configuration change notification, 52 required patches for HP-UX 11.0, 21
e-mail requirements, 24 required patches for HP-UX 11i, 22
e-mail sent by iCOD software, 81 software product, 14
enablement fee, defined, 139 supported platforms, 14, 91, 98
example test activation policy, 69
161
Index
too many processors activated, 74 mpctl system call, special considerations, 129
troubleshooting software, 75
uninstalling software, 49 O
iCOD audit application, 12 offline activation mode
iCOD Cell Board activating processor, 111
accidental activation, 108 advantage/disadvantage, 68
activating, 107 converting from online, 110
activation fees, 104 converting to online, 111
supported platforms, 102 defined, 140
iCOD processors, defined, 139 described, 66
iCOD software
replace failed processor, 70
frequently asked questions, 78
iCOD software requirements system alert, L-and N-Class, 113
HP-UX 11.0, 21 On Demand Solutions
HP-UX 11i, 22 program requirements, 20
software requirements, 21
icod(5) Manpage, 144
icod_modify (1M) Manpage, 148 On Demand Solutions Program, 12
icod_notify (1M) Manpage, 151 online activation mode
icod_stat (1M) Manpage, 154 advantage/disadvantage, 68
icod_stat differences with vPars, 93 converting from offline, 111
icod_stat reporting and LPMC, 96 converting to offline, 110
icod-purchase defined, 140
defined, 139 described, 66
described, 13 replace failed processor, 70
icod-utility Openview measurement software, 130
defined, 139 override deferred activation/deactivation, 62
described, 13
inactive cell, defined, 139 P
inactive partition, defined, 139 patches
inactive processor, defined, 140 how to find the latest, 42
installing iCOD, 42
required for HP-UX 11.0, 22
required for HP-UX 11i, 23
L pay per use, defined, 140
license requirement, applying license, 37 PPU
licensing on vPars, 95 defined, 140
load-balancing active processors on software product, 14
Superdome, 61 PPU software
log file history, 79 frequently asked questions, 78
LPMC and icod_stat reporting, 96 processors
activated, defined, 138
M activating in offline activation mode, 111
Manpage bound, defined, 138
icod (5), 144 configured, defined, 138
icod_modify (1M), 148 configuring on L- and N-Class, 114
icod_notify (1M), 151 configuring on Superdome, 126
icod_stat (1M), 154 configuring on V-Class, 120
manpages, iCOD, 17 deactivated, defined, 138
measurement software on iCOD, 130 deconfigured, defined, 139
migrating processors, defined, 140 deconfiguring on L- and N-Class, 119
monarch processor, defined, 140 deconfiguring on V-Class, 125
moving a system, requirement, 39
162
Index
iCOD, defined, 139 User’s Guide
inactive, defined, 140 conventions, 18
migrating, defined, 140 obtaining, 16
monarch, defined, 140
too many activated on iCOD, 74 V
unbound, defined, 141 V-Class, firmware requirements, 133
program requirements, On Demand virtual partition, defined, 141
Solutions, 20 vPars
Psets compatibility with iCOD, 90
compatibility with iCOD, 97 icod_stat differences, 93
pstat system call, special considerations, 128
R
reinstall, preserving iCOD information, 48
Release Notes, obtaining, 16
required patches, for HP-UX 11.0, 22
required patches, for HP-UX 11i, 23
right to access, defined, 141
roles requirement, 36
S
software application considerations, 65
software products, iCOD and PPU, 14
software requirements, On Demand
Solutions, 21
Superdome
example of icod_stat on iCOD, 57, 94
firmware requirements, 133
frequently asked questions, 82
load-balancing active processors, 61
supported platforms
differences, 131
iCOD, 14, 91, 98
iCOD Cell Board, 102
system alert on L- and N-Class, 113
system contact
role requirement, 36
setting information, 55
system status, checking, 56
T
temporary capacity, 84
temporary capacity, defined, 141
test activation policy, 69
troubleshooting, iCOD software, 75
U
unbound processor, defined, 141
uninstalling iCOD software, 49
usage history, 79
163

Instant Capacity On Demand (iCOD) User's Guide For Versions B.05.x

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Instant Capacity On Demand (iCOD) User's Guide For Versions B.05.x

Încărcat de

Drepturi de autor:

Formate disponibile

Instant Capacity on Demand (iCOD)

User’s Guide for versions B.05.x

Manufacturing Part Number: B9073-90040

Restricted Rights Legend

• First Edition: July 2002, 5990-2943,

2. Understanding iCOD Requirements

3. Installing and Uninstalling iCOD Software

4. Using iCOD to Manage your Processors

7. Temporary Capacity for iCOD Processors

8. iCOD Compatibility with vPars and Psets

9. iCOD Cell Board

A. Offline Configuration and Activation of Processors

This chapter covers the following topics:

HP On Demand Solutions Program

Software Product Overview

• iCOD: product number B9073AA

Most Recent iCOD Product Version and Supported

iCOD HP-UX 11.0 L-, N-, and Available on:

iCOD HP-UX 11i L-, N-, V-Class, Available on:

iCOD Supported Hardware Platforms

— V-Class firmware upgrade - V2500/V2600 Test Station Software

Past iCOD Versions and Supported Platforms

iCOD User’s Guide History

Locating the iCOD User’s Guide

• December 2003 Instant Information CD

Locating the iCOD Release Notes

• Printed (part number B9073-90020) — order from the following HP

• December 2003 Instant Information CD

• icod (5): an overview of the iCOD commands and their usage

• icod_modify (1M): how to manage processor activity in your iCOD

• icod_notify (1M): how to manage asset notification to HP

• icod_stat (1M): how to display processor status, usage information,

• “iCOD Program Requirements” on page 20

iCOD Program Requirements

HP-UX 11.0 Requirements

Required Patches for HP-UX 11.0

HP-UX 11i v1 Requirements

IMPORTANT For hardware-partitionable systems (for example, Superdome): The

Required Patches for HP-UX 11i v1

• PHKL_23154: S700_800 11.11 dflush() patch

cron Configuration Requirements

This entry runs the iCOD icod_notify -c command at 12:00 noon

IMPORTANT As a part of the On Demand Solutions program requirements, HP must

• The iCOD system/partition is required to have sendmail installed

IMPORTANT The e-mail is bounced/rejected by the mail servers at HP if the domain

• For HP-UX 11.0: Installing and Administering Internet Services

Before you Start

Overview of E-mail Routing Across the Internet

• In some environments, configuring your iCOD system to properly

Example 2-1 Example Edit to Sendmail Configuration (/etc/mail/sendmail.cf)

• the iCOD system’s hostname is:

Steps to Confirm or Diagnose E-mail Configuration

1. Send an e-mail message from your iCOD system to an e-mail address

Configuring iCOD’s FROM E-mail Address

Configuring Your Server to Send but Not Receive

iCOD System Configuration Information Reported to

• the periodic iCOD cron task is triggered

Reply to Contact Status of System Contact’s request

Configuration If the iCOD system configuration has changed, by the activation or

On Hardware- In addition to the above information, hardware-partitionable systems

HP receives an asset report from your iCOD system. Here is an example

Example 2-2 iCOD B.05.x Asset Report

Testing E-Mail Transmission of the Asset Report