IBM eserver pSeries 690 User manual

pSeries 690
User’s Guide
SA38-0588-02
ER ser ver
IBM

Third Edition (October 2002)
Before using this information and the product it supports, read the information in “Safety Notices” on page ix,
Appendix A, “Environmental Notices” on page 155, and Appendix B, “Notices” on page 157.
A reader’s comment form is provided at the back of this publication. If the form has been removed, address comments
to Information Development, Department H6DS-905-6C006, 11501 Burnet Road, Austin, Texas 78758-3493. To send
comments electronically, use this commercial internet address: [email protected]. Any information that you
supply may be used without incurring any obligation to you.
©International Business Machines Corporation, 2001, 2002. All rights reserved. Note to U.S. Government Users
-- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth is GSA
ADP Schedule Contract with IBM Corp.

Contents
Safety Notices ........................ix
Electrical Safety........................ix
Laser Safety Information .....................x
Laser Compliance ......................x
Data Integrity and Verification ..................xi
About This Book ......................xiii
Highlighting .........................xiii
ISO 9000 .........................xiii
Online Publications ......................xiii
Related Publications ......................xiii
Trademarks.........................xiv
Chapter 1. Introducing the Eserver pSeries 690 ............1
System Configurations......................2
Partitioned System Overview ...................3
Partition Profiles.......................3
System Profiles .......................4
Types of Partitions ......................4
Processor on Demand......................5
Processor on Demand Features .................5
Processor on Demand Activation Features ..............6
Capacity Planning ......................6
Software Licenses and Processor on Demand .............8
Activating Process for Processor on Demand .............8
Chapter 2. Using the Eserver pSeries 690 ..............9
Hardware Management Console (HMC) Overview and Setup .........9
System Power-on Methods ....................9
Powering the Server On and Off ..................9
Powering On the Processor Subsystem using the HMC .........10
Powering Off the Processor Subsystem Using the HMC .........10
Graphics Console Support ....................10
Reading the Operator Panel Display.................11
Checkpoints........................11
Disturbance or System Attention LED ...............11
Understanding the Power-On Self-Test (POST) .............13
POST Indicators ......................13
POST Keys ........................13
Chapter 3. Using the Service Processor...............15
Service Processor Menus ....................15
Accessing the Service Processor Menus Locally............16
Accessing the Service Processor Menus Remotely ...........16
Saving and Restoring Service Processor Settings ...........16
Menu Inactivity .......................16
iii

General User Menu ......................17
Privileged User Menus .....................19
Main Menu ........................19
Service Processor Setup Menu .................21
Passwords ........................22
System Power Control Menu ..................27
System Information Menu ...................32
Language Selection Menu ...................42
Call-In/Call-Out Setup Menu ..................44
Modem Configuration Menu ..................45
Serial Port Selection Menu ...................46
Serial Port Speed Setup Menu .................47
Telephone Number Setup Menu .................47
Call-Out Policy Setup Menu ..................49
Customer Account Setup Menu .................50
Call-out Test........................50
Service Processor Parameters in Service Mode (Full System Partition) .....50
System Power-On Methods ...................50
Service Processor Reboot/Restart Recovery ..............52
Boot (IPL) Speed ......................52
Failure During Boot Process ..................52
Failure During Normal System Operation ..............52
Service Processor Reboot/Restart Policy Controls ...........52
Configuring and Deconfiguring Processors or Memory...........55
Run-Time CPU Deconfiguration (CPU Gard) .............55
Service Processor System Monitoring - Surveillance ...........56
System Firmware Surveillance..................56
Operating System Surveillance .................57
Call-Out (Call-Home) ......................58
Console Mirroring .......................59
System Configuration ....................59
Service Processor Error Logs ...................60
LCD Progress Indicator Log ...................61
Resetting the Service Processor ..................61
Service Processor Operational Phases ................63
Pre-Standby Phase .....................63
Standby Phase.......................64
Bring-Up Phase ......................64
Run-Time Phase ......................65
Chapter 4. Using System Management Services............67
Select Language .......................68
Password Utilities .......................69
Set Privileged-Access Password .................69
View Error Log ........................69
Setup Remote IPL (Initial Program Load) ...............71
Change SCSI Settings .....................75
Select Console........................76
Select Boot Options ......................76
Select Boot Devices ......................79
iv Eserver pSeries 690 User’s Guide

Display Current Settings.....................81
Restore Default Settings ....................81
Multiboot Startup .......................82
Exiting System Management Services ................82
Chapter 5. Using the Online and Standalone Diagnostics ........83
Online and Standalone Diagnostics Operating Considerations ........83
Identifying the Terminal Type to the Diagnostics ............84
Undefined Terminal Types ...................84
Resetting the Terminal ....................84
Running Online Diagnostics ..................84
Online Diagnostics Modes of Operation ...............85
Service Mode .......................85
Running Online Diagnostics in Service Mode .............85
Concurrent Mode ......................86
Running the Online Diagnostics in Concurrent Mode ..........86
Maintenance Mode .....................87
Running the Online Diagnostics in Maintenance Mode..........87
Standalone Diagnostic Operation..................88
Performing Slow Boot ....................88
Partitioned System Considerations for Standalone Diagnostics .......88
Considerations for Running Standalone Diagnostics from CD-ROM .....89
Loading the Standalone Diagnostics from CD-ROM...........89
Running Standalone Diagnostics from a Network Installation Management (NIM)
Server .........................89
NIM Server Configuration ...................90
Client Configuration and Booting Standalone Diagnostics from the NIM Server 91
Chapter 6. Introduction to Tasks and Service Aids ...........93
Tasks ...........................94
Add Resource to Resource List ..................95
AIX Shell Prompt .......................95
Analyze Adapter Internal Log ...................95
Backup and Restore Media....................96
Certify Media ........................97
Change Hardware Vital Product Data ................100
Configure Dials and LPF Keys ..................100
Configure ISA Adapter .....................100
Configure Reboot Policy ....................101
Configure Remote Maintenance Policy ...............102
Configure Ring Indicate Power-On Policy...............104
Configure Scan Dump Policy...................105
Configure Surveillance Policy ..................106
Create Customized Configuration Diskette ..............106
Delete Resource from Resource List ................107
Disk Maintenance ......................107
Disk to Disk Copy .....................107
Display/Alter Sector .....................108
Display Configuration and Resource List ...............108
Display Firmware Device Node Information ..............108
Contents v

Display Hardware Error Report ..................108
Display Hardware Vital Product Data ................109
Display Machine Check Error Log .................109
Display Microcode Level ....................109
Display or Change Bootlist ...................109
Display or Change Diagnostic Run-Time Options ............110
Display Previous Diagnostic Results ................112
Display Resource Attributes ...................112
Display Service Hints .....................112
Display Software Product Data ..................113
Display System Environmental Sensors ...............113
Examples ........................114
Display Test Patterns .....................115
Display USB Devices .....................115
Download Microcode .....................115
Download Microcode to PCI SCSI RAID Adapter ...........115
Download Microcode to a PCI-X Dual Channel Adapter .........115
Download Microcode to Disk Drive Attached to a PCI SCSI RAID Adapter 116
Download Microcode to a Fiber Channel Adapter ...........116
Download Microcode to DVD-RAM Attached to a PCI SCSI Adapter.....117
Download Microcode to Disk Attached to PCI SCSI Adapter .......117
Download Microcode to Other Devices ..............118
Fault Indicators .......................118
Fibre Channel RAID Service Aids .................119
Flash SK-NET FDDI Firmware ..................119
Format Media........................120
Hardfile Attached to SCSI Adapter (non-RAID) ............120
Hardfile Attached to PCI SCSI RAID Adapter ............121
Optical Media .......................121
Diskette Format ......................122
Gather System Information ...................122
Generic Microcode Download ..................122
Hot Plug Task........................122
PCI Hot Plug Manager ....................123
SCSI Hot Swap Manager ...................125
RAID Hot Plug Devices ...................126
Identify Indicators ......................126
Identify and System Attention Indicators ...............126
Local Area Network Analyzer...................127
Log Repair Action ......................127
Periodic Diagnostics .....................128
PCI RAID Physical Disk Identify..................128
Process Supplemental Media ..................128
Run Diagnostics .......................129
Run Error Log Analysis ....................129
Run Exercisers .......................129
Exerciser Commands (CMD)..................130
Abbreviations .......................130
Memory Exerciser .....................131
Tape Exerciser ......................131
vi Eserver pSeries 690 User’s Guide

Diskette Exerciser .....................131
CD-ROM Exerciser .....................131
Floating Point Exerciser ...................131
SCSI Bus Analyzer ......................133
SCSD Tape Drive Service Aid ..................134
Spare Sector Availability ....................135
SSA Service Aid .......................135
System Fault Indicator .....................135
System Identify Indicator ....................135
Update Disk-Based Diagnostics ..................135
Update System or Service Processor Flash ..............136
7135 RAIDiant Array Service Aid .................137
Command Examples ....................139
7318 Serial Communications Network Server Service Aid .........139
Chapter 7. Verifying the Hardware Operation ............141
Step 1. Considerations Before Running This Procedure ..........141
Step 2. Loading the Online Diagnostics in Service Mode .........141
Step 2.5 Loading the Standalone Diagnostics from CD-ROM ........142
Step 3. Running System Verification ................142
Step 4. Performing Additional System Verification ............143
Step 5. Stopping the Diagnostics .................143
Chapter 8. Hardware Problem Determination ............145
Problem Determination Using the Standalone or Online Diagnostics......145
Problem Determination When Unable to Load Diagnostics .........151
Appendix A. Environmental Notices................155
Product Recycling and Disposal..................155
Environmental Design .....................155
Acoustical Noise Emissions ...................156
Declared Acoustical Noise Emissions ...............156
Appendix B. Notices .....................157
Appendix C. Service Processor Setup and Test ...........159
Service Processor Setup Checklist .................159
Testing the Setup ......................160
Testing Call-In ......................160
Testing Call-Out ......................161
Serial Port Configuration ...................161
Appendix D. Modem Configurations ...............163
Sample Modem Configuration Files ................163
Generic Modem Configuration Files ...............163
Specific Modem Configuration Files ...............163
Configuration File Selection ...................164
Examples for Using the Generic Sample Modem Configuration Files ....165
Customizing the Modem Configuration Files.............166
IBM 7852-400 DIP Switch Settings................166
Contents vii

Xon/Xoff Modems .....................167
Ring Detection ......................167
Terminal Emulators .....................167
Recovery Procedures ....................168
Transfer of a Modem Session ..................169
Recovery Strategy .....................170
Prevention Strategy .....................170
Modem Configuration Sample Files ................171
Sample File modem_m0.cfg ..................171
Sample File modem_m1.cfg ..................173
Sample File modem_z.cfg...................175
Sample File modem_z0.cfg ..................177
Sample File modem_f.cfg ...................179
Sample File modem_f0.cfg ..................182
Sample File modem_f1.cfg ..................185
Index ..........................189
viii Eserver pSeries 690 User’s Guide

Safety Notices
A danger notice indicates the presence of a hazard that has the potential of causing
death or serious personal injury.
Danger notices appear on the following pages:
vix
A
caution notice indicates the presence of a hazard that has the potential of causing
moderate or minor personal injury.
Caution notices appear on the following pages:
vix
vx
For a translation of the safety notices contained in this book, see the
System Unit
Safety Information
, order number SA23-2652.
Electrical Safety
Observe the following safety instructions any time you are connecting or disconnecting
devices attached to the system.
DANGER
An electrical outlet that is not correctly wired could place hazardous voltage
on metal parts of the system or the devices that attach to the system. It is the
responsibility of the customer to ensure that the outlet is correctly wired and
grounded to prevent an electrical shock.
Use one hand, when possible, to connect or disconnect signal cables to
prevent a possible shock from touching two surfaces with different electrical
potentials.
During an electrical storm, do not connect cables for display stations, printers,
telephones, or station protectors for communications lines.
D06
CAUTION:
This product is equipped with a four-wire (three-phase and ground) power cable
for the user’s safety. Use this power cable with a properly grounded electrical
outlet to avoid electrical shock.
C27
DANGER
To prevent electrical shock hazard, disconnect all power cables from the
electrical outlet before relocating the system.
D01
ix

Laser Safety Information
CAUTION:
This product may contain a CD-ROM, DVD-ROM, or laser module on a PCI card,
which are class 1 laser products.
C30
Laser Compliance
All lasers are certified in the U.S. to conform to the requirements of DHHS 21 CFR
Subchapter J for class 1 laser products. Outside the U.S., they are certified to be in
compliance with the IEC 825 (first edition 1984) as a class 1 laser product. Consult the
label on each part for laser certification numbers and approval information.
CAUTION:
All IBM laser modules are designed so that there is never any human access to
laser radiation above a class 1 level during normal operation, user maintenance,
or prescribed service conditions. Data processing environments can contain
equipment transmitting on system links with laser modules that operate at
greater than class 1 power levels. For this reason, never look into the end of an
optical fiber cable or open receptacle. Only trained service personnel should
perform the inspection or repair of optical fiber cable assemblies and receptacles.
C25, C26
xEserver pSeries 690 User’s Guide

Data Integrity and Verification
IBM computer systems contain mechanisms designed to reduce the possibility of
undetected data corruption or loss. This risk, however, cannot be eliminated. Users who
experience unplanned outages, system failures, power fluctuations or outages, or
component failures must verify the accuracy of operations performed and data saved or
transmitted by the system at or near the time of the outage or failure. In addition, users
must establish procedures to ensure that there is independent data verification before
relying on such data in sensitive or critical operations. Users should periodically check
the IBM support websites for updated information and fixes applicable to the system and
related software.
xi

xii Eserver pSeries 690 User’s Guide

About This Book
This book provides information on how to use the server, use diagnostics, use service
aids, and verify server operation. This book also provides information to help you solve
some of the simpler problems that might occur.
Highlighting
The following highlighting conventions are used in this book:
Bold Identifies commands, subroutines, keywords, files, structures, directories, and
other items whose names are predefined by the system. Also identifies
graphical objects such as buttons, labels, and icons that the user selects.
Italics Identifies parameters whose actual names or values are to be supplied by the
user.
Monospace Identifies examples of specific data values, examples of text similar to what
you might see displayed, examples of portions of program code similar to
what you might write as a programmer, messages from the system, or
information you should actually type.
ISO 9000
ISO 9000 registered quality systems were used in the development and manufacturing
of this product.
Online Publications
IBM Eserver pSeries publications are available online. To access the online books,
visit our IBM Eserver pSeries Information Center at
http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base. Click Hardware
documentation.
Related Publications
The following publications provide related information:
vThe
System Unit Safety Information , order number SA23-2652, contains translations
of safety information used throughout this book.
vThe
Site and Hardware Planning Information , order number SA38-0508, contains
information to help you plan your installation.
vThe Eserver
pSeries 690 Service Guide , SA38-0589, contains reference
information, maintenance analysis procedures (MAPs), error codes, removal and
replacement procedures, and a parts catalog.
vThe Eserver
pSeries 690 Installation Guide , SA23-1285, contains information on
how to set up and cable the server and verify server operation.
xiii

vThe IBM Hardware Management Console for pSeries Installation and Operations
Guide
, SA38-0590, provides information to system administrators on how to install
and use a Hardware Management Console (HMC) to manage a system.
vThe
IBM Hardware Management Console for pSeries Maintenance Guide ,
SA38-0603, provides information on how to service a Hardware Management
Console (HMC).
vThe
RS/6000 and Eserver Diagnostic Information for Multiple Bus Systems ,
SA38-0509, contains diagnostic information, service request numbers (SRNs), and
failing function codes (FFCs).
vThe RS/6000 and Eserver Adapters, Devices and Cable Information for Multiple
Bus Systems
, SA38-0516, contains information about adapters, devices, and cables
for your server. This manual is intended to supplement the service information found
in the Diagnostic Information for Multiple Bus Systems.
vThe
PCI Adapter Placement Reference , SA23-2504, contains information regarding
slot restrictions for adapters that can be used in this system.
Trademarks
The following terms are trademarks of International Business Machines Corporation in
the United States, other countries, or both:
vAIX
vRS/6000
vEserver
vIBM
vpSeries
Other company, product, and service names may be trademarks or service marks of
others.
xiv Eserver pSeries 690 User’s Guide

Chapter 1. Introducing the Eserver pSeries 690
The Eserver pSeries 690 system is a shared multiprocessor server.
The system can be configured (or partitioned) to be used as multiple separate systems.
This configuration is known as a
logically partitioned system .
The following illustration shows an Eserver pSeries 690 containing two Integrated
Battery Feature drawers.
1
2
4
3
5
6
7
8
9
1Hardware Management Console for
pSeries 77040 Model 61D I/O Subsystem
27040 Model 61R Bulk Power Subsystem
Redundant 7040 Model 61R Bulk Power
Subsystem is placed in the rear.
87040 Model 61D I/O
Subsystem (Optional)
37040 Model 681 Processor Subsystem 97040 Model 61D I/O
Subsystem (Optional)
47040 Model 681 Media Drawer
5*,6* Primary 7040 Model 61R Integrated
Battery Feature (IBF) (Optional) for the
Primary Power Subsystem.
Redundant 7040 Model 61R Integrated
Battery Feature (IBF) (Optional) is placed
in the rear.
*7040 Model 61D I/O Subsystem (Optional, if features 5 and 6 are not installed).
1

A pSeries 690 system can have up to two racks, which support up to eight I/O drawer
subsystems.
The Hardware Management Console for pSeries (HMC) is used to manage the
resources in the system. The system can be configured as a full system partition, which
means that all resources of the system are used as a single system.
The system can also be configured into multiple (or logical) partitioned systems. With a
logically partitioned system, system resources can be divided into a number of systems
each running in its own partition.
Numerous configurations of pSeries 690 systems can be managed from one Hardware
Management Console. A second Hardware Management Console can be used for
redundancy.
System Configurations
The system configuration may vary. Possible configurations include:
vMultiple pSeries 690s attached to one Hardware Management Console (HMC)
vTwo HMCs attached to one pSeries 690
vTwo HMCs jointly managing up to eight pSeries 690s
The following components make up the base configuration of the pSeries 690:
vRack and Bulk Power Subsystem (BPA) The BPA is the main power control unit for
the pSeries 690. This redundant bulk power assembly distributes power at 350 V to
each drawer where conversion is made to the required chip level.
vProcessor Subsystem The processor subsystem is a 17 EIA-unit-high drawer. The
processor subsystem contains the backplane, up to four processor modules, up to 16
L3 cache modules, up to four I/O books, up to eight memory books, and cooling
blowers. The processor subsystem drawer also contains the power subsystem
components used in the conversion of 350 V bulk power to the supply voltages
required by the various internal components.
Several memory book sizes are available. The minimum memory requirement to
operate this system is 8 GB, and the maximum amount of memory is 256 GB.
vMedia Drawer The media drawer is a 1 EIA-unit high drawer containing an operator
panel, 1.44 MB floppy diskette drive, one SCSI optical drive (either a CD-ROM or a
DVD-RAM), signal cables, power cables, a 1 EIA-unit-high 24-inch rack-mountable
sheet metal enclosure, and miscellaneous mechanical hardware. Three additional
SCSI bays are available to add optional CD-ROMs, DVD-RAMs, or 4-mm tape
drives:
– Variable Speed SCSI-2 CD-ROM Drive
– SCSI DVD-RAM Drive
– 4-mm Internal Tape Drive
vIntegrated Battery Feature (IBF) (optional) The IBF is a 2 EIA-unit-high drawer that
can be added to your system. The IBF provides backup electric power in case of a
power outage. You can install up to two IBFs in the base rack configuration. One
additional IBF can be installed in an expansion rack.
2Eserver pSeries 690 User’s Guide

vI/O Drawers The I/O drawer is a 4 EIA-unit-high drawer containing up to two I/O
boards, up to 16 disk drives, four DASD backplanes, a midplane card, four cooling
fans and two power supplies (which are independent of the bulk power assembly).
The base rack configuration can have up to four I/O drawers with each drawer
having 20 PCI card slots, and more than 500 GB of storage. An expansion rack can
be connected to the base system and contain additional I/O drawers and IBFs.
Note: If your base rack configuration contains an IBF, the space in the rack for the
fourth I/O drawer in that rack is not available.However, an expansion rack
allows you to add additional I/O drawers and an additional IBF.
vHardware Management Console (HMC) - The HMC consists of a display,
independent processor, keyboard, and mouse. The HMC is mandatory for all
systems. For more information on the use of logical partitioned systems, see the
“Partitioned System Overview”.
Partitioned System Overview
Partitioning enables users to configure a single computer into several independent
systems. Each of these systems, called
logical partitions , is capable of running
applications in its own independent environment. This independent environment
contains its own operating system, its own set of system processors, its own set of
system memory, and its own I/O adapters.
An
affinity partition is a special type of logical partition in which processors and system
memory are allocated in a predefined way that may increase performance when running
some types of applications (memory is assigned to a processor that is in close physical
proximity to it).
The HMC allows you to perform many hardware management tasks for your managed
system, including configuring logical partitions. You can choose to operate your
managed system as a single server (called
full system partitions ), or you can choose to
run multiple partitions.
Partition Profiles
A profile defines a configuration setup for a managed system or partition. The HMC
allows you to create multiple profiles for each managed system or partition. You can
then use the profiles you created to start a managed system or partition in a particular
configuration.
A partition does not actually own any resources until it is activated; resource
specifications are stored within partition profiles. The same partition can operate using
different resources at different times, depending on the profile you activate.
When you activate a partition, you enable the system to create a partition using the set
of resources in a profile created for that partition. For example, a logical partition profile
might indicate to the managed system that its partition requires three processors, 2
gigabytes of memory, and I/O slots 6, 11, and 12 when activated.
Chapter 1. Introducing the Eserver pSeries 690 3

You can have more than one profile for a partition. However, you can only activate a
partition with one profile at a time. Additionally, affinity partitions and logical partitions
cannot be active at the same time.
When you create a partition profile, the HMC shows you all the resources available on
your system. The HMC does not, however, verify if another partition profile is currently
using a portion of these resources. For example, the HMC might show 16 processors
on your system, but does not notify you that other partitions are using nine of them. You
can create two partition profiles, each using a majority of system resources. If you
attempt to activate both of these partitions at the same time, the second partition in the
activation list fails.
System Profiles
Using the HMC, you can create and activate often-used collections of predefined
partition profiles. A collection of predefined partition profiles is called a system profile.
The system profile is an ordered list of partitions and the profile that is to be activated
for each partition. The first profile in the list is activated first, followed by the second
profile in the list, followed by the third, and so on.
The system profile helps you change the managed systems from one complete set of
partitions configurations to another. For example, a company might want to switch from
using 12 partitions to using only four, every day. To do this, the system administrator
deactivates the 12 partitions and activates a different system profile, one specifying four
partitions.
When you create a group of affinity partitions, the HMC automatically creates a system
profile that includes all of the affinity partitions that you created.
Types of Partitions
The HMC allows you to use two types of partitions: logical partitions and the full system
partition.
Logical Partitions
Logical partitions are user-defined system resource divisions. Users determine the
number of processors, memory, and I/O that a logical partition can have when active.
Affinity Partitions: An affinity partition is a special type of logical partition in which
processors and system memory are allocated in a predefined way that may increase
performance when running some types of applications (memory is assigned to a
processor that is in close physical proximity to it).
Affinity partitions can be created with either four or eight processors. The user
determines the allocation of I/O resources in a server with affinity partitions; only the
allocation of processors and memory is predefined.
Reassigning Partition Resources Dynamically: You can logically attach and detach
a managed system’s resources to and from a logical partition’s operating system
4Eserver pSeries 690 User’s Guide

without rebooting. In addition, failing resources can be dynamically released from the
owning partition, serviced and reattached, or replaced with an acceptable replacement
without disturbing the partition’s activities.
Full System Partition
A special partition called the full system partition assigns all of your managed system’s
resources to one large partition. The full system partition is similar to the traditional,
non-partition method of operating a system. Because all resources are assigned to this
partition, no other partitions can be started when the full system partition is running.
Likewise, the full system partition cannot be started while other partitions are running.
The HMC allows you to easily switch from the full system partition to logical partitions.
The actual setup of the operating system in a partition may require some careful
planning to ensure that no conflicts exist between the two environments.
For more detail on partitions, see the
IBM Hardware Management Console for pSeries
Installation and Operations Guide
, order number SA38-0590.
Processor on Demand
The Processor On Demand (POD) feature of some IBM servers allows the server to be
manufactured with extra processor capacity built in, ready to be activated when you
need it. If your system is ordered with processor on demand features, you can activate
the features and pay for the increased processing power as your needs grow.
The processor on demand feature enables you to start small, and then increase your
processing capacity without disrupting any of your current operations.
For information about how to activate processor on demand features on your server,
refer to “Activating Process for Processor on Demand” on page 8, or refer to the
IBM
Hardware Management Console for pSeries Installation and Operations Guide
, order
number SA38-0590 that was delivered with your hardware management console.
The processor on demand feature offers the capability to non-disruptively activate two
or more processors on a server that was ordered and installed with inactive processor
on demand features. The processor on demand feature adds capacity in increments of
two processors, up to the maximum number of standby processors. The processor on
demand feature adds significant value if you want to upgrade without disruption, handle
business peaks, or add new workloads. The processor on demand feature adds
permanent capacity growth with no requirement to reboot the server.
Processor on Demand Features
If your system was ordered with processor on demand features, your managed system
has a set of processors that are ″active″and a set of standby processors that are ″not
active.″In the event that an active processor fails, the inactive processors are then
available to be used by the system until the failing processor is replaced.
Chapter 1. Introducing the Eserver pSeries 690 5

Processor on Demand Activation Features
Standby processors (two or more) can be permanently activated by ordering a quantity
of permanent processor on demand activation features. This order is filled when your
service provider receives your request, generates an activation code, and delivers it to
you. Activation codes can be delivered to you through postal mail and they are posted
on the Web.
Capacity Planning
If you are doing capacity planning for models offering processor on demand, plan
ahead for any potentially disruptive actions that might inhibit your using fully the
capacity of the activated processors. Some actions you may want to take prior to
activating any processor on demand features are as follows:
vPerform any I/O updates, such as adding adapters necessary to increase system
capacity
vPerform memory upgrades
vPrepare LPAR partitions
By planning ahead, you can accommodate the growth of existing workloads, as well as
handle new workloads without requiring a server outage. Other components of a server
such as memory and I/O affect performance and overall throughput of workloads. By
planning ahead and taking into account the complete server configuration, you can help
ensure that you get the full benefit of processor on demand activations.
Note: If you have questions about capacity-planning topics not covered here, contact
your sales representative for assistance.
Processor on Demand Ordering
Permanent processor-on-demand capacity can be activated in either of the following
scenarios. The description of each of the following scenarios highlights if and when it is
necessary to send vital product data (VPD) to IBM.
vNew system order (new footprint): An order can contain a number of processor on
demand activation features. The manufacturing facility fills orders directly at the plant
of manufacture, before the server is delivered to the customer.
vOrdering activation features for an installed server: After you have determined
that you want to permanently activate some or all of your standby processors,
contact your business partner or sales representative to place an order.
When the order record and the VPD are both available to the manufacturing facility, a
processor on demand activation code unique to your server is generated. The
activation code is mailed to you and posted at a public Web site for quick access:
http://www.ibm.com/servers/eserver/pseries/cuod/index.html
As part of the order process, VPD collected from the installed server is combined
with information from the actual order records for processor on demand activation
features. This combined information is used to generate a processor on demand
activation code specifically for your server, enabling the activation of the desired
number of standby processors. Allow some time for the order processing and posting
6Eserver pSeries 690 User’s Guide