IBM K5400 User Manual
ER ser ver
IBM
pSeries 690
User’s Guide
SA38-0588-02
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: aix6kpub@austin.ibm.com. 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 ISAAdapter .....................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
death or serious personal injury.
v ix
notice indicates the presence of a hazard that has the potential of causing
Danger
notices appear on the following pages:
A
moderate or minor personal injury.
v ix
v x
For a translation of the safety notices contained in this book, see the
Safety Information
Electrical Safety
Observe the following safety instructions any time you are connecting or disconnecting
devices attached to the system.
DANGER
caution
notice indicates the presence of a hazard that has the potential of causing
Caution
notices appear on the following pages:
System Unit
, order number SA23-2652.
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
x Eserver 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
Italics
Monospace Identifies examples of specific data values, examples of text similar to what
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:
v The
of safety information used throughout this book.
v The
information to help you plan your installation.
v The Eserver
information, maintenance analysis procedures (MAPs), error codes, removal and
replacement procedures, and a parts catalog.
v The Eserver
how to set up and cable the server and verify server operation.
other items whose names are predefined by the system. Also identifies
graphical objects such as buttons, labels, and icons that the user selects.
Identifies parameters whose actual names or values are to be supplied by the
user.
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.
System Unit Safety Information
, order number SA23-2652, contains translations
Site and Hardware Planning Information
pSeries 690 Service Guide
, SA38-0589, contains reference
pSeries 690 Installation Guide
, order number SA38-0508, contains
, SA23-1285, contains information on
xiii
Trademarks
v The
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.
v The
IBM Hardware Management Console for pSeries Maintenance Guide
SA38-0603, provides information on how to service a Hardware Management
Console (HMC).
v The
RS/6000 and
SA38-0509, contains diagnostic information, service request numbers (SRNs), and
failing function codes (FFCs).
v The
RS/6000 and
Bus Systems
for your server. This manual is intended to supplement the service information found
in the Diagnostic Information for Multiple Bus Systems.
v The
PCI Adapter Placement Reference
slot restrictions for adapters that can be used in this system.
The following terms are trademarks of International Business Machines Corporation in
the United States, other countries, or both:
v AIX
v RS/6000
v Eserver
v IBM
v pSeries
Eserver
Eserver
, SA38-0516, contains information about adapters, devices, and cables
Diagnostic Information for Multiple Bus Systems
Adapters, Devices and Cable Information for Multiple
, SA23-2504, contains information regarding
,
,
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
The following illustration shows an Eserver pSeries 690 containing two Integrated
Battery Feature drawers.
2
3
4
5
6
7
8
9
logically partitioned system
.
1
1 Hardware Management Console for
pSeries
2 7040 Model 61R Bulk Power Subsystem
Redundant 7040 Model 61R Bulk Power
Subsystem is placed in the rear.
3 7040 Model 681 Processor Subsystem 9 7040 Model 61D I/O
4 7040 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).
7 7040 Model 61D I/O
Subsystem
8 7040 Model 61D I/O
Subsystem (Optional)
Subsystem (Optional)
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:
v Multiple pSeries 690s attached to one Hardware Management Console (HMC)
v Two HMCs attached to one pSeries 690
v Two HMCs jointly managing up to eight pSeries 690s
The following components make up the base configuration of the pSeries 690:
v Rack 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.
v Processor 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.
v Media 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
v Integrated 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.
2 Eserver pSeries 690 User’s Guide
v I/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.
v Hardware 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
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
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).
logical partitions
is a special type of logical partition in which processors and system
, is capable of running
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
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.
full system partitions
Chapter 1. Introducing the Eserver pSeries 690 3
), or you can choose to
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:
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:
a managed system’s resources to and from a logical partition’s operating system
4 Eserver pSeries 690 User’s Guide
An affinity partition is a special type of logical partition in which
You can logically attach and detach
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
Installation and Operations Guide
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
Hardware Management Console for pSeries Installation and Operations Guide
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.
IBM Hardware Management Console for pSeries
, order number SA38-0590.
IBM
, order
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:
v Perform any I/O updates, such as adding adapters necessary to increase system
capacity
v Perform memory upgrades
v Prepare 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.
v New 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.
v Ordering 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
6 Eserver pSeries 690 User’s Guide
of the processor on demand activation code to take place. Then use the code to
activate the processor on demand features directly on your server.
Processor on demand activation features will not be fulfilled until you submit the VPD
through the Electronic Service Agent or manually to the following Web site:
http://www.ibm.com/servers/eserver/pseries/cuod/index.html
When you enter a processor on demand activation code, standby processors will
immediately become activated for use. After their status changes from Standby to
Active, the processors can be dynamically moved to the partition where they are
needed.
Electronic Service Agent and Processor on Demand
When Electronic Service Agent is used to electronically report VPD on a regular basis,
you can eliminate potential delays in the order process for processor on demand
activation features (no manual reporting of VPD is necessary prior to the fulfillment of a
feature upgrade order). To best utilize Electronic Service Agent and to be prepared to
activate processor on demand features conveniently, make sure that Electronic Service
Agent and related communications requirements are up and running. If this is done
before the processor on demand activation features are ordered, the VPD for the
system will already be up to date, and the manual process of updating the VPD is not
needed.
After Electronic Service Agent is installed, follow the procedures under “Activating
Process for Processor on Demand” on page 8 to enable the system to collect and
transfer the required VPD for processor on demand.
If a processor on demand activation feature is ordered and then canceled, an action by
the service representative is required to cancel the order. After the activation code is
posted on the Web or mailed, the order for processor on demand activation features is
considered fulfilled, and the downstream billing process is started.
Dynamic Processor Sparing
In environments with CUoD, Dynamic Processor Sparing allows inactive processors to
act as “dynamic spares”. An inactive processor is transparently activated if a failing
processor reaches a predetermined error threshold, thus helping to maintain
performance and improve system availability. Starting with AIX 5L V5.2, this capability is
offered on pSeries servers with CUoD to help minimize the impact to server
performance caused by a failed processor. This will happen dynamically and
automatically when using DLPAR and the failing processor is detected prior to failure. If
not detected prior to failure or not using DLPAR, a reboot of the system will bring
onboard an alternate processor from the inactive spares. The user can then re-establish
required performance levels without waiting for parts to arrive on-site. Dynamic
Processor Sparing does not require the purchase of an Activation Code, it only requires
the system have inactive CUoD processors available.
Chapter 1. Introducing the Eserver pSeries 690 7
Software Licenses and Processor on Demand
Activating a processor may change the terms and conditions for applications that you
use on your server. Consult the application documentation to determine if the license
terms and conditions requirements change based on hardware configuration.
Activating Process for Processor on Demand
The processor on demand process begins when you determine a potential need for
more processing capability in the future and want to have the hardware installed on the
server now. If processor on demand features are ordered for your server, they are
included in the server when it is delivered. When additional processors become a
necessity, use the following steps to activate them:
1. Determine the number of standby processors you want to activate.
2. Contact your sales representative or business partner to place an order for
particular processor on demand activation features.
3. The sales representative places an order to the system coordinator or feature
coordinator for the specific number of processor on demand activation features. The
order specifies the number of additional processors you have requested to add.
4. To process the order, you must send the system Vital Product Data (VPD) to IBM in
either of the following ways:
v Electronic process (Electronic Service Agent)
v Web-based VPD entry:
For details on how to submit the VPD either through the Electronic Service Agent or
using the Web system go to the following Web site and locate the document
Planning Guide for Capacity Upgrade on Demand
detailed procedures.
http://www.ibm.com/servers/eserver/pseries/cuod/index.html
5. After the Activation Code is received (either from the Web or the mailed copy), enter
the Activation Code using the HMC. Detailed procedures are available in the
document
6. Once you have finished the acivation process, you can assign the activated
processors to a partition. If you are using dynamic partitioning (DLPAR), you need
not reboot the system to use the processors. If you are not using DLPAR, you must
reboot the managed system before the newly activated processors can be used.
Before adding processors to a partition that is running Linux, you must stop Linux
partitions and then restart them after you have assigned the processors.
Planning Guide for Capacity Upgrade on Demand
. The planning guide provides
.
Begin using the new processor capacity. If you encountered any problems using the
preceding process, see the following Web site:
http://www.ibm.com/servers/eserver/pseries/cuod/index.html
8 Eserver pSeries 690 User’s Guide
Chapter 2. Using the Eserver pSeries 690
This chapter discusses the Hardware Management Console for pSeries (HMC), system
power control, and drives supported by the server.
Hardware Management Console (HMC) Overview and Setup
The Hardware Management Console (HMC) uses its connection to the processor
subsystem to perform various functions. The main functions of the HMC include:
v Creating and maintaining a multiple partition environment
v Detecting, reporting, and storing changes in hardware conditions
v Acting as a service focal point for service representatives to determine an
appropriate service strategy
Note: The HMC is shipped with the pSeries 690 and is the main interface for
configuring and managing resources on this system through the HMC virtual
terminal window.
on a particular window. You can have up to 16 virtual terminal windows.
All the tasks you need to maintain the interface, the underlying operating system, and
the HMC application code are available by using the HMC’s management applications.
Virtual terminal window
refers to the operating system session
For more information on the HMC, refer to the
pSeries Installation and Operations Guide
System Power-on Methods
Using the HMC to power on the managed system is recommended. However, the white
power button on the media subsystem operator panel can be used to power on the
managed system. The managed system will reboot in the same mode in which it was
previously booted. (If the managed system was previously booted in partitioned system
mode, all partitions will automatically start and run.)
Powering the Server On and Off
This section provides procedures for powering the server on and off.
Progress indicators, also referred to as
operator panel display. The power LED on the media subsystem stops blinking and
stays on, indicating the system power is on.
IBM Hardware Management Console for
.
checkpoints
, are visible on the media subsystem
9
Powering On the Processor Subsystem using the HMC
To power on the processor subsystem using the HMC, do the following:
1. Log in to the HMC with your user ID and password. Refer to the
Management Console for pSeries Installation and Operations Guide
information on HMC user IDs and passwords.
2. Click on the Partition Management icon under the HMC hostname to select your
preferred partition environment. The Contents area now lists the processor
subsystem as available as a managed system. If you have only one processor
subsystem, the Contents area lists the processor subsystem as System A
3. Select the appropriate managed system.
4. To power on the managed system, select the desired system in the Contents area.
Next, on the menu, choose Selected.
5. Select Power On.
Powering Off the Processor Subsystem Using the HMC
Attention: Shut down the partitions before powering off the processor subsystem.
To power off the processor subsystem using the HMC, do the following:
1. Click on the Partition Management icon under the HMC host name to select your
preferred partition environment. The Contents area now lists the processor
subsystem as available as a managed system. If you have only one processor
subsystem, the Contents area lists the processor subsytem as System A.
2. Select the appropriate managed system.
3. To power off the managed system, select the desired system in the Contents area.
Next, on the menu, choose Selected.
4. Select Power Off.
5. A screen displays to verify that you want to power off. Select Yes.
IBM Hardware
for more
Note: Only logical power will be removed; 350V dc power will still be present within the
system.
Graphics Console Support
The pSeries 690 supports graphics consoles. Graphics console support requires the
following adapters:
v Graphics adapter with a graphics display attached
v Universal Serial Bus (USB) adapter with a keyboard and mouse attached
Only one graphics console is supported per system partition. If the system is running
partitions, up to eight partitions can have graphics consoles.
The graphics console is functional only when AIX is running. For any installation or
service processor functions, you must use the HMC.
10 Eserver pSeries 690 User’s Guide
Reading the Operator Panel Display
The operator panel display is located in the media drawer of the pSeries 690 and is
used to:
v Track the progress of the system unit self tests and configuration program
v Display codes when the operating system comes to an abnormal end
v Display system messages
Checkpoints
During power-on self-test (POST), four-digit checkpoints display, indicating the progress
of the testing. If an error is detected that requires attention, the server halts with an
eight-digit error code displayed in the upper row of the operator panel display, starting
in the leftmost position. This eight-digit error code identifies the error. For a listing of the
error codes, see the Eserver
The four-digit checkpoints are in the form of nnnn, where n is an alphabetic or numeric
character.
The following diagram shows the locations of the operator panel display and
components of the operator panel.
1
2
!
pSeries 690 Service Guide
3
.
6
5
4
1 Power on/off button 4 Reset button
2 Power on/off LED 5 Service processor reset button (Service
3 Operator panel display 6 Disturbance or system attention LED
R
Disturbance or System Attention LED
The system attention LED on the operator panel is turned on when an entry is made in
the service processor error log that gets transmitted to the system-level error logs (the
AIX error log and the service action event log in service focal point). When the attention
light comes on, examine these error logs to see if user intervention is required.
If a hardware problem is indicated, call service support. If no intervention is required,
the system attention LED can be turned off by either of the following methods:
v On the HMC’s graphical interface, as follows:
1. Click on the Service Applications icon.
use only)
Chapter 2. Using the Eserver pSeries 690 11
2. Double-click the Service Focal Point icon.
3. In the Contents area, select
Management window opens.
4. In the LED Management window, select one of more managed systems from the
table.
5. Select Deactivate LED. The associated system attention LED is turned off.
Hardware Service Functions
. The LED
For more information about the operator panel as it relates to the HMC, see the
Hardware Management Console for pSeries Installation and Operations Guide
number SA38-0590.
v As a user with root authority, enter diag on an AIX command line and do the
following:
1. Select Task Selection.
2. On the task selection menu, select Identify and Attention Indicators.
3. When the list of LEDs displays, use the cursor to highlight Set System Attention
Indicator to Normal.
4. Press Enter, and then press F7 to commit. This action turns off the LED.
v If the system is powered off, access the service processor menus and from the main
menu do the following:
1. Select System Information Menu.
2. Select LED Control Menu.
3. Select Clear System Attention Indicator. This will turn the LED off.
For more information regarding the LED, refer to Chapter 3, “Using the Service
Processor” on page 15.
IBM
, order
12 Eserver pSeries 690 User’s Guide
Understanding the Power-On Self-Test (POST)
After power is turned on and before the operating system is loaded, the partition does a
power-on self-test (POST). This test performs checks to ensure that the hardware is
functioning correctly before the operating system is loaded. During the POST, a POST
screen displays, and POST indicators appear on the virtual terminal window. The next
section describes the POST indicators and functions that can be accessed during the
POST.
POST Indicators
POST indicators indicate tests that are being performed as the partition is preparing to
load the operating system. The POST indicators are words that display on the virtual
terminal window. Each time that the firmware starts another different step in the POST,
a POST indicator word appears on the console. Each word is an indicator of the tests
that are being performed.
The POST screen displays the following words:
Memory
Memory test
Keyboard
Initialize the keyboard and mouse. The time period for pressing a key to
access the System Management Services, or to initiate a service mode boot is
now open. See “POST Keys” for more information.
Network
Self-test on network adapters
SCSI
Adapters are being initialized
Speaker
Sounds an audible tone at the end of POST
POST Keys
The POST keys, if pressed
last (speaker) POST indicator displays, cause the system to start services or to initiate
service mode boots used for configuring the system and diagnosing problems. The keys
are described below:
Note: The program function keys (F1-F12) on a keyboard attached to the HMC or USB
card are not used and will be ignored. After the keyboard POST indicator
displays, you must use the numeric number keys to enter input.
after
the keyboard POST indicator displays and
before
the
1 Key
The numeric 1 key, when pressed during POST, starts the System Management
Services (SMS) interface.
5 Key
The numeric 5 key, when pressed during POST, initiates a system boot in service mode
using the default service mode boot list.
Chapter 2. Using the Eserver pSeries 690 13
6 Key
The numeric 6 key works like the numeric 5 key, except that the firmware uses the
customized service mode bootlist.
8 Key
This option is used by service personnel. To enter the open firmware command line,
press the numeric 8 key
speaker displays during startup. After you press the 8 key, the remaining POST
indicators display until initialization completes.
When initialization and POST are complete, the open firmware command line (an OK
prompt) displays.
This option should only be used by service personnel to obtain additional debug
information.
To exit from the open firmware command prompt, type reset-all or power off the
system and reboot.
after
the word keyboard displays and
before
the last word
14 Eserver pSeries 690 User’s Guide
Chapter 3. Using the Service Processor
Note: The information in this chapter regarding the configuring of serial ports, and
modems attached to those serial ports, applies only to the serial ports (S1 and
S2) on the primary I/O book (location U1.18-P1-H2). None of this information is
applicable to the serial ports, or modems attached to those serial ports, on the
Hardware Management Console for pSeries (HMC).
Note: On some of the system management services (or service processor) screens,
you will see the term
The service processor runs on its own power boundary and continually monitors
hardware attributes and the environmental conditions within the system. The service
processor is controlled by firmware and does not require the AIX operating system to be
operational to perform its tasks.
The service processor menus allow you to configure service processor options, as well
as enable and disable functions.
Service processor menus are available using an HMC virtual terminal window when OK
is displayed on the operator panel or when the service processor has detected a server
problem (such as a surveillance failure).
Service Processor Menus
The service processor menus are divided into the following groups:
v General user menu - the user must know the general-access password.
v Privileged user menus - the user must know the privileged-access password.
LPAR
, which is equivalent to the term
partitioned system
.
If the server is powered off, the service processor menus can be accessed locally or
remotely on the following:
v Serial port 1 (S1)
v Serial port 2 (S2)
v The HMC
15
Accessing the Service Processor Menus Locally
Service processor menus can be accessed by opening a virtual terminal window on the
HMC, or by attaching an ASCII terminal to serial port 1 (S1) or serial port 2 (S2). After
OK displays in the operator panel, press any key on the keyboard to signal the service.
Note: The service processor menus cannot be accessed simultaneously on a virtual
terminal window on the HMC and on an ASCII terminal. Accessing the menus on
the HMC locks out access to the ASCII terminals and the other way around.
When you gain access, the service processor prompts you for a password (if one is
set), and when verified, displays the service processor menus.
The service processor menu prompt, represented by 0> or 1>, indicates the serial port
to which the terminal is connected.
v An ASCII terminal can have the following prompts:
– 0> indicates serial port 1 (S1)
– 1> indicates serial port 2 (S2)
v The HMC always indicates 0>
Accessing the Service Processor Menus Remotely
If your system has a modem connected to serial port 1 or serial port 2 and is configured
for call-in (see “Modem Configuration Menu” on page 45), access the service processor
menus remotely as follows:
1. With the system powered off, call in from a remote terminal.
2. The service processor detects ring-indicate and prompts you for a password (if one
is set). When verified, the service processor menus display remotely.
Saving and Restoring Service Processor Settings
All the settings that you make (except language) from the service processor menus can
be backed up either for recovering from a fault that may corrupt these settings, or for
replicating these settings to other servers that include a service processor.
The service aid, Save or Restore Hardware Management Policies, can be used to save
your settings after initial setup or whenever the settings must be changed for system
operation purposes.
It is strongly recommended that you use this service aid for backing up service
processor settings to protect the usefulness of the service processor and the availability
of the server. Refer to “Save or Restore Hardware Management Policies,” in
“Introduction to Tasks and Service Aids” for information about this service aid.
Menu Inactivity
The service processor exits menu mode after ten minutes of inactivity and displays a
message indicating that it has done so. Pressing any key on the virtual terminal window
causes the main menu to display.
16 Eserver pSeries 690 User’s Guide
Loading...