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: [e-mail]. 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

General User Menu

The menu options presented to the general user are a subset of the options available to
the privileged user. The user must know the general-access password, if one is set, to
access this menu.

1. Power-on System

2. Power-off System

3. Read VPD Image from Last System Boot

4. Read Progress Indicators from Last System Boot

5. Read Service Processor Error Logs

6. Read System POST Errors

99. Exit from Menus

0>

v Power-on System

Allows the user to start the system using the current virtual terminal window as the
active console.

v Power-off System

This option is not available on this system.

v Read VPD Image from Last System Boot

Displays manufacturer vital product data, such as serial numbers, part numbers, and
so on, that were stored from the system boot prior to the one in progress now, for the
entire system.

GENERAL USER MENU

Chapter 3. Using the Service Processor 17

v Read Progress Indicators from Last System Boot

Displays a number of the boot progress indicators, which may include service
processor checkpoints, IPL checkpoints, or AIX configuration codes, from the
previous system boot. This information can be useful in diagnosing system faults.

Note: If you are running one or more logical partitions, enter the partition ID (0-15)

to display progress indicators for that partition since the last system boot. If
your system is running in full system partition mode, this option automatically
displays details from partition 0.

The progress indicator codes are listed from top (latest) to bottom (oldest).

This information is not stored in nonvolatile storage. If the system is powered off
using the power-on button on the operator panel, this information is retained. If the
ac power is disconnected from the system, this information will be lost. For an
example, refer to “LCD Progress Indicator Log” on page 61.

v Read Service Processor Error Logs

Displays the service processor error logs. For an example, refer to “Service
Processor Error Logs” on page 60.

v Read System POST Errors

Displays additional error log information (this option is only for service personnel).

v Exit from Menus

Selecting this option will exit the service processor menus. You can re-enter the
menus by pressing any key on the console.

18 Eserver pSeries 690 User’s Guide

Privileged User Menus

The following menus are available to privileged users only. The user must know the
privileged-access password, if one is set, to access these menus.

Main Menu

A listing at the top of the main menu contains the following:

v Your system’s current firmware version
v The firmware copyright notice
v The system name given to your server during setup

You need the firmware version for reference when you either update or repair the
functions of your service processor.

The system name, an optional field, is the name that your server reports in problem
messages. This name helps your support team (for example, your system administrator,
network administrator, or service representative) to more quickly identify the location,
configuration, and history of your server. Set the system name, from the main menu,
using option 6.

Chapter 3. Using the Service Processor 19

Note: The information under the Service Processor Firmware heading in the following

Main Menu illustration is example information only.

Service Processor Firmware
VERSION: RH011007
Copyright 2001 IBM Corporation

SYSTEM NAME

MAIN MENU

1. Service Processor Setup Menu

2. System Power Control Menu

3. System Information Menu

4. Language Selection Menu

5. Call-In/Call-Out Setup Menu

6. Set System Name

99. Exit from Menus

0>

v Service Processor Setup Menu

See “Service Processor Setup Menu” on page 21 for more information.

v System Power Control Menu

See “System Power Control Menu” on page 27 for more information.

v System Information Menu

See “System Information Menu” on page 32 for more information.

v Language Selection Menu

See “Language Selection Menu” on page 42 for more information.

v Call-In/Call-Out Setup Menu

See “Call-In/Call-Out Setup Menu” on page 44 for more information.

v Set System Name

Allows setting of the system name.

20 Eserver pSeries 690 User’s Guide

Service Processor Setup Menu

The following Service Processor Setup Menu is accessed from the Main Menu:

SERVICE PROCESSOR SETUP MENU

1. Change Privileged Access Password

2. Change General Access Password

3. Enable/Disable Console Mirroring:
Currently Enabled

4. Start Talk Mode

5. OS Surveillance Setup Menu

NOT supported in LPAR mode.

6. Reset Service Processor

7. Reprogram Flash EPROM Menu

8. Serial Port Snoop Setup Menu

NOT supported in LPAR mode.

9. Scan Log Dump Policy:

Currently Never

98. Return to Previous Menu

99. Exit from Menus

0>

Note: Unless otherwise stated in menu responses, settings become effective when a

menu is exited using option 98 or 99.

Chapter 3. Using the Service Processor 21

Passwords

Passwords can be any combination of up to eight alphanumeric characters. You can
enter longer passwords, but the entries are truncated to include only the first eight
characters. The privileged-access password can be set from service processor menus
or from System Management Services (SMS) utilities (see Chapter 4, “Using System
Management Services” on page 67). The general-access password can be set only
from service processor menus.

For security purposes, the service processor counts the number of attempts to enter
passwords. The results of not recognizing a password within this error threshold are
different, depending on whether the attempts are being made locally (at the server) or
remotely (through a modem). The error threshold is three attempts.

If the error threshold is reached by someone entering passwords at the server, the
service processor commands the server to resume the initial program load (IPL). This
action is taken based on the assumption that the server is in an adequately secure
location with only authorized users having access. Such users must still successfully
enter a login password to access AIX.

If the error threshold is reached by someone entering passwords remotely, the service
processor commands the server to power off to prevent potential security attacks on the
server by unauthorized remote users. The following table lists what you can access with
the privileged-access password and the general-access password.

Privileged

Access

Password

None None Service processor MAIN MENU displays.

Set None Users with the password see the service processor

Set Set Users see menus associated with the entered

General

Access

Password

Resulting Menu

MAIN MENU. Users without password cannot log in.

password.

22 Eserver pSeries 690 User’s Guide

v Change Privileged-Access Password

Set or change the privileged-access password. It provides the user with the capability
to access all service processor functions. This password is usually used by the
system administrator or root user.

v Change General-Access Password

Set or change the general-access password. It provides limited access to service
processor menus, and is usually available to all users who are allowed to power on
the server, especially remotely.

Note: The general-access password can only be set or changed after the privileged

access password is set.

v Enable/Disable Console Mirroring

Note: Console mirroring is disabled in partitioned systems.

Console mirroring is supported on serial port 1 (S1) and serial port 2 (S2). When
console mirroring is enabled, the service processor sends information to all serial
ports. The serial port from which console mirroring is enabled is referred to as the

active port

. The

mirror port

is determined when keyboard input is detected from one
of the other ports. From this point on, the service processor sends information only to
the active port and the mirror port. This capability can be enabled by local or remote
users, providing local users with the capability to monitor remote sessions. Console
mirroring can be enabled for the current session only. For more information, see
“Console Mirroring” on page 59.

v Start Talk Mode

In a console-mirroring session, it is useful for those who are monitoring the session
to be able to communicate with each other. Selecting Start Talk Mode activates the
keyboards and displays for such communications while console mirroring is
established. This is a full duplex link, so message interference is possible. Alternating
messages between users works best.

Chapter 3. Using the Service Processor 23

v OS Surveillance Setup Menu

Note: This option is disabled in partitioned systems.

This menu can be used to set up operating system (OS) surveillance.

OS Surveillance Setup Menu

1. Surveillance:

Currently Enabled

2. Surveillance Time Interval:

2 minutes

3. Surveillance Delay:

2 minutes

98. Return to Previous Menu

0>

– Surveillance

Can be set to Enabled or Disabled.

– Surveillance Time Interval

Can be set to any number from 2 through 255.

– Surveillance Delay

Can be set to any number from 0 through 255.

Refer to “Service Processor System Monitoring - Surveillance” on page 56 for more
information about surveillance.

v Reset Service Processor

If this option is selected, entering Y causes the service processor to reboot.

v Reprogram Flash EPROM Menu

This option updates the system EPROMs. After entering Y to indicate that you want
to continue, you are prompted to enter the update diskettes. Follow the instructions
on the screen. When the update is complete, the service processor reboots.

All system EPROMs that can be reprogrammed are updated at the same time and
are as follows:

– System power control network programming
– Service processor programming
– System firmware programming
– Run-Time Abstraction Services

24 Eserver pSeries 690 User’s Guide

v Serial Port Snoop Setup Menu

Note: This option is disabled in partitioned systems.

This menu can be used to set up serial port snooping, in which the user can
configure serial port 1 as a ″catch-all″ reset device.

From the service processor main menu, select option 1, service processor setup
menu, then select option 8 (Serial Port Snoop Setup Menu).

SERIAL PORT SNOOP SETUP MENU

1. System reset string:
Currently Unassigned

2. Snoop Serial Port:

Currently Unassigned

98. Return to Previous Menu

1>

Use the Snoop Serial Port option to select the serial port to snoop.

Note: Only serial port 1 is supported.

Use the system reset string option to enter the system reset string, which resets the
machine when it is detected on the main console on Serial Port 1.

After serial port snooping is correctly configured, at any point after the system is
booted to AIX, whenever the reset string is typed on the main console, the system
uses the service processor reboot policy to restart.

Because pressing Enter after the reset string is not required, make sure that the
string is not common or trivial. A mixed-case string is recommended.

v Scan Log Dump Policy

A scan dump is the collection of chip data that the service processor gathers after a
system malfunction, such as a checkstop or hang. The scan dump data may contain
chip scan rings, chip trace arrays, and SCOM contents.

The scan dump data are stored in the system control store. The size of the scan
dump area is approximately 4 MB.

During the scan log dump, A8xx (in the range A810 to A8FF) displays in the operator
panel. The xx characters will change as the scan log dump progresses. If the xx
characters do not change after several minutes, the service processor is hung and
must be reset.

When the scan log dump is complete, depending on how the reboot policy is set, the
system will either:

Chapter 3. Using the Service Processor 25

– Go to the standby state (and the service processor menus will be available),

indicated by OK or STBY in the operator panel

OR
– Attempt to reboot.

Scan Log Dump Policy Menu

1. Scan Log Dump Policy:
Currently Never

2. Scan Log Dump Content:

Not Applicable

98. Return to Previous Menu

0>

Option 1 displays the following screen:

Select from the following options:

(As needed=1, Never=2, Always=3, Immediate=4)

Enter new option:

0>

The scan log dump policy can be set to the following:

1 = As needed

The processor run-time diagnostics record the dump data based on the
error type. Selecting this option will set the scan log dump policy to ″Not
Applicable″. This is the default value.

2 = Never

Selecting this option will set the scan log dump policy to ″Not Applicable″.

3 = Always

Selecting this option will set the scan log dump policy to ″Currently
Checkstop Hardware Abbreviated″; this is the default. However, if the dump
policy is set to always, the scan log dump content can be changed, by
selecting option 2, to either ″abbreviated″ or ″complete″. Selecting
″complete″ will result in more data being stored in a larger scan dump, but
the scan dump operation will take longer.

4 = Immediately

This option can only be used when the system is in the standby state with
power on. It is used to dump the system data after a checkstop or machine
check occurs when the system firmware is running, or when the operating
system is booting or running.

The scan log dump policy can also be set from the Tasks menu in the AIX service
aids.

26 Eserver pSeries 690 User’s Guide

System Power Control Menu

This menu is used to set power control options. Other menus that control boot options
are available from this menu.

SYSTEM POWER CONTROL MENU

1. Enable/Disable Unattended Start Mode:
Currently Enabled

2. Ring Indicate Power-On Menu

3. Reboot/Restart Policy Setup Menu

4. Power-On System

5. Power-Off System

6. Enable/Disable Fast System Boot
Currently Enabled

7. Boot Mode Menu

98. Return to Previous Menu

99. Exit from Menus

0>

v Enable/Disable Unattended Start Mode

Use this option to instruct the service processor to restore the power state of the
server after a temporary power failure. Unattended start mode can also be set
through the System Management Services (SMS) menus. This option is intended to
be used on servers that require automatic power-on after a power failure. For more
information, see “System Power-On Methods” on page 50.

Chapter 3. Using the Service Processor 27

v Ring Indicate Power-On Menu

RING INDICATE POWER-ON MENU

1. Ring indicate power-on :
Currently Enabled

2. Number of rings:
Currently 3

30. Refresh Modem Settings

98. Return to Previous Menu

Ring indicate power-on is enabled by default on both serial port 1 (S1) and serial port
2 (S2). When ring indicate power-on is enabled, call-in is disabled.

If ring indicate power-on is enabled and call-in is already enabled, you will be asked
to confirm your choice. Refer to the message displayed on your screen.

If the ring indicate power-on setting is changed, you must select option 30, Refresh
Modem Settings to update the modem settings. If Refresh Modem Settings is
selected, and the modem(s) have not been configured, you will be asked to configure
the modems first. See “Call-In/Call-Out Setup Menu” on page 44 for information on
configuring modems.

Option 2 is used to set the number of rings.

28 Eserver pSeries 690 User’s Guide

v Reboot/Restart Policy Setup Menu

The following menu controls the Reboot/Restart Policy:

Reboot/Restart Policy Setup Menu

1. Number of reboot attempts:
Currently 1

2. Use OS-Defined restart policy?
Currently No

3. Enable supplemental restart policy?
Currently Yes

4. Call-Out before restart:
Currently Disabled

98. Return to Previous Menu

0>

Reboot

system reset or power on.

is the process of bringing up the system hardware; for example, from a

Restart

is activating the operating system after the system

hardware is reinitialized. Restart must follow a successful reboot.
– Number of reboot attempts - If the server fails to successfully complete the boot

process, it attempts to reboot the number of times specified. Entry values equal to
or greater than 0 are valid. Only successive failed reboot/restart attempts are
counted.

– Use OS-Defined restart policy - In a full system partition, this allows the service

processor to react in the same way that the operating system does to major
system faults by reading the setting of the operating system parameter
Automatically Restart/Reboot After a System Crash. This parameter might
already be defined, depending on the operating system or its version (or level). If
the operating system automatic restart setting is defined, it can be set to respond
to a major fault by restarting or by not restarting. See your operating system
documentation for details on setting up operating system automatic restarts. The
default value is No.

On a partitioned system, this setting is ignored.

Chapter 3. Using the Service Processor 29

– Enable supplemental restart policy - The default setting is Yes. When set to

Yes in a full system partition, the service processor restarts the system when the
system loses control as detected by service processor surveillance, and either:

The Use OS-Defined restart policy is set to No.
OR
The Use OS-Defined restart policy is set to Yes and the operating system has

no automatic restart policy.
If set to Yes on a partitioned system, the service processor restarts the system

when the system loses control and it is detected by service processor
surveillance.

– Call-Out before restart (Enabled/Disabled) - If a restart is necessary due to a

system fault, and you are running a full system partition, you can enable the
service processor to call out and report the event. This option can be valuable if
the number of these events becomes excessive, which might signal a bigger
problem.

This setting is ignored on a partitioned system.

v Power-On System

Allows immediate power-on of the system.

v Power-Off System

This option is not available on this system.

v Enable/Disable Fast System Boot

Allows the user to select the IPL type, mode, and speed of the system boot.
Attention: Selecting the fast IPL results in several diagnostic tests being skipped

and a shorter memory test being run.

30 Eserver pSeries 690 User’s Guide

v Boot Mode Menu

Note: This option is disabled in partitioned systems.

The Boot Mode Menu allows you to select a boot mode.

Boot Mode Menu

1. Boot to SMS Menu:
Currently Disabled

2. Service Mode Boot from Saved List:
Currently Disabled

3. Service Mode Boot from Default List:
Currently Disabled

4. Boot to Open Firmware Prompt:
Currently Disabled

98. Return to Previous Menu

0>

To select a boot mode, select a number and press Enter. The item corresponding to
the selected number toggles between Disabled to Enabled. If a boot mode is
Enabled, the boot mode selected is performed, and the Disabled/Enabled selection is
reset to Disabled. The following describes each boot mode:

– Boot to SMS Menu

When this selection is enabled, the system boots to the System Management
Services (SMS) Menu.

– Service Mode Boot from Saved List

This selection causes the system to perform a service mode boot using the
service mode boot list saved in NVRAM. If the system boots AIX from the disk
drive and AIX diagnostics are loaded on the disk drive, AIX boots to the
diagnostics menu.

Using this option to boot the system is the preferred way to run online diagnostics.

– Service Mode Boot from Default List

This selection is similar to

Service Mode Boot from Saved List

, except the system
boots using the default boot list that is stored in the system firmware. This is
normally used to try to boot customer diagnostics from the CD-ROM drive.

Using this option to boot the system is the preferred way to run standalone
diagnostics.

– Boot to Open Firmware

This option should only be used by service personnel to obtain additional debug
information. When this selection is enabled, the system boots to the open
firmware prompt.

Chapter 3. Using the Service Processor 31

System Information Menu

This menu provides access to system configuration information, error logs, system
resources, and processor configuration.

SYSTEM INFORMATION MENU

1. Read VPD Image from Last System Boot

2. Read Progress Indicators from Last System Boot

3. Read Service Processor Error Logs

4. Read System POST Errors

5. Read NVRAM

6. Read Service Processor Configuration

7. Processor Configuration/Deconfiguration Menu

8. Memory Configuration/Deconfiguration Menu

9. Power Control Network Utilities Menu

10. LED Control Menu

11. MCM/L3 Interposer Plug Count Menu

12. Performance Mode Setup Menu

98. Return to Previous Menu

99. Exit from Menus

0>

v Read VPD Image from Last System Boot

Displays manufacturer’s vital product data (VPD), such as serial numbers, part
numbers, and so on, that was stored from the system boot prior to the one in
progress now. VPD from all devices in the system is displayed.

v Read Progress Indicators from Last System Boot

Displays a number of the boot progress indicators, which may include service
processor checkpoints, IPL checkpoints, or AIX configuration codes, from the
previous system boot. This information can be useful in diagnosing system faults.

Note: If you are running from a partitioned system, enter the partition ID (0-15) to

display progress indicators for that partition since the last system boot. In a
full system partition, this option automatically displays details from partition 0.

The progress indicator codes are listed from top (latest) to bottom (oldest).

This information is not stored in nonvolatile storage. If the system is powered off
using the power-on button on the operator panel, this information is retained. If the
ac power is disconnected from the system, this information will be lost. For an
example, refer to “LCD Progress Indicator Log” on page 61.

v Read Service Processor Error Logs

32 Eserver pSeries 690 User’s Guide

Displays error conditions detected by the service processor. Refer to “Service
Processor Error Logs” on page 60 for an example of this error log.

v Read System POST Errors

This option should only be used by service personnel to obtain additional debug
information.

v Read NVRAM

Displays Non Volatile Random Access Memory (NVRAM) content.

v Read Service Processor Configuration

Displays current service processor configuration.

v Processor Configuration/Deconfiguration Menu

Enable/Disable CPU Repeat Gard

CPU repeat gard automatically deconfigures a CPU during a system boot if
a processor has failed BIST POST, caused a machine check or check stop,
or has reached a threshold of recoverable errors. The processor will remain
deconfigured until repeat gard is disabled or the processor is replaced.

Repeat gard is enabled by default.
For more information, see “Configuring and Deconfiguring Processors or

Memory” on page 55.

Enable/Disable Dynamic Processor Sparing

This option is part of the Capacity Upgrade on Demand (CUoD) function.
Dynamic Processor Sparing is the capability of the system to deconfigure a
failing (or potentially failing) processor and then configure a replacement
processor from the unlicensed CUoD processor pool.

If the system is running logical partitions, the hot sparing operation takes
place while the system is running. If the system is booted in a full system
partition, the system must be rebooted for the processor sparing operation
to take place.

Processor hot sparing is enabled by default.

Note: The memory affinity of the failing processor is not taken into account

when the replacement processor is assigned; the replacement
processor is the next processor that is available.

This menu allows the user to change the system processor configuration. If it is
necessary to take one of the processors offline, use this menu to deconfigure the
processor, and then reconfigure the processor at a later time. An example of this
menu follows:

Chapter 3. Using the Service Processor 33

PROCESSOR CONFIGURATION/DECONFIGURATION MENU

77. Enable/Disable CPU Repeat Gard: Currently Enabled

78. Enable/Disable Processor Hot Sparing (if available): Currently Enabled

1. 0 3.0 (00) Configured by system 2. 1 3.1 (00) Deconfigured by system

3. 2 3.2 (00) Configured by system 4. 3 3.3 (00) Configured by system

5. 4 3.4 (00) Configured by system 6. 5 3.5 (00) Deconfigured by system

7. 6 3.6 (00) Configured by system 8. 7 3.7 (00) Configured by system

98. Return to Previous Menu

0>

Note: This table is built from vital product data collected during the last boot

sequence. The first time the system is powered on, or after the system’s
nonvolatile RAM (NVRAM) has been erased, this table may be empty. The
table is rebuilt during the next boot into AIX.

The fields of the previous table represent the following:

Column 1

(1.) Menu selection index.

Column 2

(0) Logical processor device number assigned by AIX. You can display
these logical device numbers by issuing the following command on the AIX
command line:

lsdev -C | grep proc

Column 3

(3.0) Processor address list used by the service processor.

Column 4

(00) Error status of the processors.

The error status of each processor is indicated by AB, where B indicates the number
of errors and A indicates the type of error according to the following:

1. Bring-up failure

2. Run-time non-recoverable failure

3. Run-time recoverable failure

4. Group integrity failure

5. Non-repeat-gardable error. The resource may be reconfigured on the next boot.
A status of 00 indicates that the CPU has not had any errors logged against it by the

service processor.
To enable or disable CPU repeat gard, use menu option 77. The default is enabled.
To enable or disable processor hot sparing, use option 78. The default is enabled.

34 Eserver pSeries 690 User’s Guide

If CPU repeat gard is disabled, processors that are in the ″deconfigured by system″
state will be reconfigured. These reconfigured processors are then tested during the
boot process, and if they pass, they remain online. If they fail the boot testing, they
are deconfigured even though CPU repeat gard is disabled.

The failure history of each CPU is retained. If a processor with a history of failures is
brought back online by disabling repeat gard, it remains online if it passes testing
during the boot process. However, if repeat gard is enabled, the processor is taken
offline again because of its history of failures.

Note: The processor numbering scheme used by the service processor is different

from the numbering scheme used by AIX. To ensure that the correct processor
is selected, consult the AIX documentation before configuring or deconfiguring
a processor.

Note: To determine the number of processors available to AIX, run the following

command on the AIX command line: bindprocessor -q

v Memory Configuration/Deconfiguration Menu

Enable/Disable Memory Repeat Gard

Memory repeat gard partially or fully deconfigures a memory book
automatically during a system boot if a memory book has failed BIST POST,
caused a machine check or checkstop, or has reached a threshold of
recoverable errors. The memory will remain deconfigured until repeat gard is
disabled or the memory book is replaced.

Memory repeat gard is enabled by default.
For more information, see “Configuring and Deconfiguring Processors or

Memory” on page 55.

Runtime Recoverable Error Repeat Gard

Runtime recoverable error repeat gard controls the deallocation of the
memory if a recoverable error occurs during runtime. If a recoverable
memory error occurs, and runtime recoverable error repeat gard is disabled,
the system will continue running with no change in the memory
configuration. If a recoverable memory error occurs, and runtime
recoverable error repeat gard is enabled, the memory half-book or book in
which the error occurred will be taken offline.

Runtime Recoverabe Error Repeat Gard is disabled by default.

These menus allow the user to change the system memory configuration. If it is
necessary to take one of the memory books partially or completely offline, this menu
allows you to deconfigure a book, and then reconfigure the book at a later time. This
menu also allows you to see if the repeat gard function has partially or completely
deconfigured a memory book.

When this option is selected, a menu displays. The following is an example of this
menu:

Chapter 3. Using the Service Processor 35

MEMORY CONFIGURATION/DECONFIGURATION MENU

77. Enable/Disable Memory Repeat Gard: Currently Enabled

78. Runtime Recoverable Error Repeat Gard: Currently Enabled

1. Memory card

98. Return to Previous Menu

After you select the memory card option by entering 1, a menu displays, allowing the
selection of a memory book. The following is an example of this menu.

MEMORY CONFIGURATION/DECONFIGURATION MENU

1: 16.16(00, -) Configured by system 2: 17.17(00, -) Configured by system
3: 18.18(00, -) Configured by system 4: 19.19(00, 1) Partially deconfigured by system

98. Return to Previous Menu

Note: This table is built from vital product data collected during the last boot

sequence. The first time the system is powered on, or after the system’s
nonvolatile RAM (NVRAM) has been erased, this table may be empty. The
table is rebuilt during the next boot into AIX.

The fields in the previous table represent the following:

Column 1

1. Menu selection index/book number

Column 2

xx.xx : Book address used by service processor

Column 3

(00, -) Error/deconfiguration status

The error status of the each memory book is indicated by (AB, -1) where B indicates
the number of errors and A indicates the type of error according to the following:

1. Bring-up failure

2. Run-time non-recoverable failure

3. Run-time recoverable failure

4. Group integrity failure

5. Non-repeat-gardable error. The resource may be reconfigured on the next boot.

An error status of (00, -) (for example, 11.16(00, -)) indicates that the memory book
has not had any errors logged against it by the service processor, and it is fully
configured.

The field after the error status will be a “-”, “0”, or “1”. The dash indicates that the
memory book is fully configured. A zero or a one indicates that memory repeat gard

36 Eserver pSeries 690 User’s Guide

has deconfigured half of the memory book. If this occurs, the status of the book in
the menu is shown as “Partially deconfigured by system.”

To change the memory configuration, select the number of the memory book. The
memory book state will change from configured to deconfigured or from
deconfigured to configured.

This menu only allows the deconfiguration of an entire book; it does not allow the
manual deconfiguration of half a book. If half a book has been configured by the
sytem (“Partially deconfigured”), it can be manually reconfigured using this menu.

In the previous example menu, each line shows two books and indicates whether
they are configured, deconfigured, or partially deconfigured.

To enable or disable Memory Repeat Gard, use menu option 77 of the Memory
Configuration/Deconfiguration Menu. The default is enabled.

To enable or disable runtime recoverable error repeat gard, use option 78 of the
Memory Configuration/Deconfiguration Menu. The default is enabled.

The failure history of each book is retained. If a book with a history of failures is
brought back online by disabling Repeat Gard, it remains online if it passes testing
during the boot process. However, if Repeat Gard is enabled, the book is taken
offline again because of its history of failures.

The four inner memory books, if present, are listed first, followed by the four outer
books, if present. The memory books are shown in the following order of physical
location code:

1 U1.18-P1-M2 5 U1.18-P1-M4
2 U1.18-P1-M3 6 U1.18-P1-M8
3 U1.18-P1-M7 7 U1.18-P1-M5
4 U1.18-P1-M6 8 U1.18-P1-M1

v Power Control Network Utilities Menu

POWER CONTROL NETWORK UTILITIES MENU

1. Lamp Test for all Operator Panels

2. Display I/O Type
Not Supported

3. Change I/O Type

98. Return to Previous Menu

0>

– Lamp Test for All Operator Panels

Selecting this option tests the media drawer operator panel’s indicators by causing
them to blink on and off for approximately 30 seconds.

– Change I/O Type

Chapter 3. Using the Service Processor 37

Use this option to change the I/O type of the primary I/O book after a service
action or configuration change if the I/O type is incorrect. If this option is chosen,
you will be asked to make the following entries:

- For the I/O drawer address, type 1.

- For the I/O type, type 98.

If either value is not valid, a failure message displays on the console. Press Enter
to return to the Power Control Network Utilities Menu.

v LED Control Menu

This menu displays the state of the processor subsystem disturbance or system
attention LED and the fault/identify LED on the I/O subsystem(s). Use this menu to
toggle the attention/fault LEDs between identify (blinking) and off. Option 1 is
available only when the system is in the error state (the CEC is powered on and the
service processor menus are available). Option 1 is not available when the system is
in standby.

An example of this menu follows:

LED Control Menu

1. Set/Reset Identify LED state

2. Clear System Attention Indicator

98. Return to Previous Menu

0>

The processor subsystem disturbance or system attention LED is located on the
operator panel in the media drawer. The I/O drawer fault/identify LED is located on
the front of each I/O subsystem.

If option 1 is selected, a list of location codes of the I/O subsystems and the CEC
drawer displays. The screen will be similar to the following:

38 Eserver pSeries 690 User’s Guide

1. U1.9-P1

2. U1.9-P2

3. U1.5-P1

4. U1.5-P2

5. U1.1-P1

6. U1.1-P2

7. U2.1-P1

8. U2.1-P2

9. U2.5-P1

10. U2.5-P2

Enter number corresponding to the location code, or
press Return to continue, or ’x’ to return to the menu.
0>4

If one of the devices is selected using the index number, the present state of its LED
will be displayed, and you are given the option to toggle it, as shown in the following
screen. The final state of the LED will then be displayed, whether or not it was
changed.

U1.5-P2 is currently in the OFF state

Select from the following (1=IDENTIFY ON, 2=IDENTIFY OFF)
0>2
Please wait...

U1.5-P2 is currently in the OFF state

(Press Return to continue)

Option 2, Clear System Attention Indicator, will clear the attention indicator on the
operator panel in the media drawer.

v MCM/L3 Interposer Plug Count Menu

Attention: Do not power on the system when in this menu. Fully eixt this menu

before powering on the system.
This menu tracks the number of times that the MCM(s) and L3 cache modules have

been plugged into the system backplane.
If an MCM or L3 cache module is replaced the plug count for tha module must be

incremented by 1. If the plug count exceeds the limit of 10 (reaches 11 or greater), a
450x yyyy or 4B2x yyyy error with a detail value of CFF0 that calls out an MCM or
L3 cache module will be posted in the service processor error log. The FRU should
be replaced during a deferred service call.

If an MCM or L3 cache module is replaced, or installed during an MES upgrade, the
plug count must be set using the interposer plug count menu. If the plug count
information is not inclueded with the new or replacement module, enter the default

Chapter 3. Using the Service Processor 39

value of 7. If the plug count is not entered, a B1xx 4698 error code, with a detail
value of E10B or E10C, will be posted in the service processor error log.

If the primary I/O book is replaced, the plug counts are retained. However the plug
count menu must be accessed and option 50, ″Commit the values and write to the
VPD,″ must be executed so that the plug counts are revalidated If the counts are not
revalidated, a B1xx 4698 error code, with a detail value of E10B or E10C, will be
posted in the service processor error log.

Notes:

1. The plug count will be zero for those positions in which L3 cache modules and
MCMs have never been installed.

2. If MCM and L3 modules are removed from the system and not replaced, those
plug counts are retained until they are manually changed.

A screen similar to the following will be displayed. In this example, all four MCMs and
all 16 L3 modules are shown.

MCM/L3 Interposer Plug Count Menu

1. L3_13:7 2. L3_0:7 3. MCM_0:7 4. L3_1:7 5. L3_4:7

6. L3_14:7 7. L3_3:7 8. L3_2:7 9. L3_7:7

10. MCM_3:1 11. MCM_2:1

12. L3_15:7 13. L3_10:7 14. MCM_1:7 15. L3_11:7 16. L3_6:7

17. L3_12:7 18. L3_9:7 19. L3_8:7 20. L3_5:7

50. Commit the values and write to the VPD

98. Return to Previous Menu

The format of the preceding menu entries is the menu index number, followed by
L3_xx, followed by the plug count after the colon. The following table correlates the
preceding information with the physical location codes.

Menu Index Number Physical Location Code

1. L3_13 U1.18-P1-C5

2. L3_0 U1.18-P1-C6

3. MCM_0 U1.18-P1-C1

4. L3_1 U1.18-P1-C7

5. L3_4 U1.18-P1-C8

6. L3_14 U1.18-P1-C9

7. L3_3 U1.18-P1-C10

8. L3_2 U1.18-P1-C11

9. L3_7 U1.18-P1-C12

40 Eserver pSeries 690 User’s Guide

10. MCM_3 U1.18-P1-C2

11. MCM_2 U1.18-P1-C3

12. L3_15 U1.18-P1-C13

13. L3_10 U1.18-P1-C14

14. MCM_1 U1.18-P1-C4

15. L3_11 U1.18-P1-C15

16. L3_6 U1.18-P1-C16

17. L3_12 U1.18-P1-C17

18. L3_9 U1.18-P1-C18

19. L3_8 U1.18-P1-C19

20. L3_5 U1.18-P1-C20

To change the plug count for a particular module, enter a menu index number. For
example, to change the plug count of the L3 module that is physically in the
upper-right corner (U1.18-P1-C8), type 5, then enter the new plug count.

When all of the new plug counts have been entered, select 50, Commit the values
and write to the VPD. This action stores the new values in NVRAM.

v Performance Mode Setup Menu

If certain types of processor cards are installed in the system, this menu is ″not
applicable.″ For other types of processor cards, this menu will be active after the first
boot as noted below.

Note: The first time the system is booted after NVRAM is cleared, ″Not Applicable″

will display under ″Performance Mode Setup Menu″ on the screen. This may
also happen if the service processor is replaced, or the processor MCMs are
upgraded.

If option 12 is selected when ″Not Applicable″ is on the screen, the system will
respond with ″Not Applicable″ and redisplay the system information menu.
The setup menu can be displayed after the performance mode is set, which
happens the first time the system is booted.

The default performance mode is set by the firmware during IPL. The default mode
provides the optimum performance for the hardware configuration of the system. The
performance mode is systemwide; it cannot be set on a per-partition basis.

You can override the default setting by using the performance mode setup menu.
The performance mode setup menu will be similar to the following:

Chapter 3. Using the Service Processor 41

Default Performance Mode: Large Commercial System optimization

1. Current Performance Mode:
Large Commercial System optimization

98. Return to Previous Menu

0>1

Selecting option 1 displays the following performance modes:

Select from the following options:

1. Large Commercial System optimization

2. Standard Operation

3. Turbo Database Mode

0>

Notes:

1. Some MCM configuration changes, such as going from an 8-way to a 24-way
system, will cause the default performance mode to change. This new setting will
not be reflected in the menu until after the system is rebooted with the new
configuration.

2. If the NVRAM has been cleared, the default performance mode and the current
performance mode will indicate uninitialized.

To override the default setting, a brief description of each performance mode follows:
– Large commercial system optimization is the setting for systems that do not fall

into the other two categories, standard operation and turbo database mode. This
setting provides the best performance for most applications.

– Standard operation optimizes the system for large memory bandwidth applications

where minimal sharing of data occurs and the likelihood of significant hardware
data-prefetching exists.

– Turbo database mode optimizes system operation for environments where there is

a large amount of data sharing among processes running concurrently on the
system.

Language Selection Menu

The service processor menus and messages are available in various languages. This
menu allows selecting languages in which the service processor and system firmware
menus and messages are displayed.

42 Eserver pSeries 690 User’s Guide

LANGUAGE SELECTION MENU

1. English

2. Francais

3. Deutsch

4. Italiano

5. Espanol

98. Return to Previous Menu

99. Exit from Menus

0>

Note: Your virtual terminal window must support the ISO-8859 character set to

correctly display languages other than English.

Chapter 3. Using the Service Processor 43

Call-In/Call-Out Setup Menu

Note: The information in this section 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). These serial ports are
normally used for call-in and call-out.

Call-out is disabled in partitioned systems. The call-out function is normally
handled by the Service Focal Point application running on the HMC.

None of these menus are applicable to the serial ports, or modems attached to
those serial ports, on the hardware management console (HMC).

CALL-IN/CALL-OUT SETUP MENU

1. Modem Configuration Menu

2. Serial Port Selection Menu

3. Serial Port Speed Setup Menu

4. Telephone Number Setup Menu

5. Call-Out Policy Setup Menu

6. Customer Account Setup Menu

7. Call-Out Test
NOT supported in LPAR mode.

98. Return to Previous Menu

99. Exit from Menus

0>

v Modem Configuration Menu, see “Modem Configuration Menu” on page 45.
v Serial Port Selection Menu, see “Serial Port Selection Menu” on page 46.
v Serial Port Speed Setup Menu, see “Serial Port Speed Setup Menu” on page 47.
v Telephone Number Setup Menu, see “Telephone Number Setup Menu” on page 47.
v Call-Out Policy Setup Menu, see “Call-Out Policy Setup Menu” on page 49.
v Customer Account Setup Menu, see “Customer Account Setup Menu” on page 50.
v Call-Out Test tests the configuration after the modem is installed and configured

correctly.

Note: If the system is running in partition mode, the call-out option is disabled.

44 Eserver pSeries 690 User’s Guide

Modem Configuration Menu

Note: This option applies only to a modem attached to serial port 1 (S1) or serial port 2

(S2) on the primary I/O book.

The first two lines of the Modem Configuration Menu contain status of the current
selections. Selections are made in the sections labeled Modem Ports and Modem
Configuration File Name. Select the serial port that you want to activate and then select
the modem configuration file for the modem on the port. If you want to set up all of the
serial ports with modems, make your selections one port at a time.

Modem Configuration Menu

Port 1 Modem Configuration File Name:
Port 2 Modem Configuration File Name:

To make changes, First select the port and then the configuration file
name

Modem Ports:

1. Serial port 1

2. Serial port 2

Modem Configuration File Name:

5. none9. modem_z_sp

6. modem_f_sp 10. modem_m1_sp

7. modem_f0_sp 11. modem_m0_sp

8. modem_f1_sp 12. modem_m1_sp

30. Save configuration to NVRAM and Configure modem

98. Return to Previous Menu

0>

For information on choosing a modem configuration file, see “Sample Modem
Configuration Files” on page 163 and “Transfer of a Modem Session” on page 169.

Chapter 3. Using the Service Processor 45

Serial Port Selection Menu

This menu allows you to enable or disable the call-in and call-out functions of each
serial port in any combination.

Note: If the system is running in partition mode, call-out is disabled.

Serial Port Selection Menu

1. Serial Port 1 Call-Out:
Currently Disabled

NOT supported in LPAR mode.

2. Serial Port 2 Call-Out:

Currently Disabled

NOT supported in LPAR mode.

3. Serial Port 1 Call-In:

Currently Disabled

4. Serial Port 2 Call-In:
Currently Disabled

98. Return to Previous Menu

0>

Call-in and ring indicate power-on cannot be enabled at the same time. If ring-indicate
power-on is already enabled and you try to enable call-in, a message prompts you for
confirmation. Refer to the message displayed on the screen.

46 Eserver pSeries 690 User’s Guide

Serial Port Speed Setup Menu

This menu allows you to set serial port speed to enhance terminal performance or to
accommodate modem capabilities.

Serial Port Speed Setup Menu

1. Serial Port 1 Speed:

Currently 9600

2. Serial Port 2 Speed:

Currently 9600

98. Return to Previous Menu

0>

A serial port speed of 9600 baud or higher is recommended. The following are valid
serial port speeds:

50 600 4800
75 1200 7200
110 1800 9600
134 2000 19200
150 2400 38000
300 3600 57600

115200

Telephone Number Setup Menu

Note: These menus are available, however, the function of calling out to report a

system failure is normally handled by the Service Focal Point application running
on the HMC.

Use this menu to set or change the telephone numbers for reporting a system failure.

Chapter 3. Using the Service Processor 47

Telephone Number Setup Menu

1. Service Center Telephone Number:
Currently Unassigned

2. Customer Administration Center Telephone Number:
Currently Unassigned

3. Digital Pager Telephone Number:
Currently Unassigned

4. Customer Voice Telephone Number:
Currently Unassigned

5. Customer System Telephone Number:
Currently Unassigned

98. Return to Previous Menu

0>

v Service Center Telephone Number is the number of the service center computer.

The service center usually includes a computer that takes calls from servers with
call-out capability. This computer is referred to as the ″catcher.″ The catcher expects
messages in a specific format to which the service processor conforms.

For more information about the format and catcher computers, refer to the README
file in the AIX /usr/samples/syscatch directory. Contact your service provider for the
correct service center telephone number to enter. Until you have that number, leave
this field unassigned.

v Customer Administration Center Telephone Number is the number of the System

Administration Center computer (catcher) that receives problem calls from servers.
Contact your system administrator for the correct telephone number to enter here.
Until you have that number, leave this field unassigned.

v Digital Pager Telephone Number is the number for a numeric pager carried by

someone who responds to problem calls from your server. Contact your
administration center representative for the correct telephone number to enter. For
test purposes, use a test number, which you can change later (see the note on page

58).

Note: If the system is running in partition mode, call-out is disabled. However, if the

system is booted in full system partition mode, at least one of the preceding
three telephone numbers must be assigned in order for the call-out test to
complete successfully.

48 Eserver pSeries 690 User’s Guide

v Customer Voice Telephone Number is the telephone number of a phone near the

server or answered by someone responsible for the server. This is the telephone
number left on the pager for callback. For test purposes, use a test number, which
you can change later.

v Customer System Telephone Number is the telephone number to which your

server’s modem is connected. The service or administrative center representatives
need this number to make direct contact with your server for problem investigation.
This is also referred to as the

Call-Out Policy Setup Menu

Note: Call-out is disabled in partitioned systems.

Call out settings can be set using the following menu:

CALL-OUT POLICY SETUP MENU

1. Call-Out policy (First/All):
Currently First

2. Remote timeout, (in seconds):
Currently 120

3. Remote latency, (in seconds):
Currently 2

4. Number of retries:
Currently 2

98. Return to Previous Menu

0>

call-in

phone number.

v Call-Out policy can be set to first or all. If call-out policy is set to first, the

service processor stops at the first successful call-out to one of the following
numbers in the order listed:

1. Service Center

2. Customer Administrative Center

3. Pager
If call-out policy is set to all, the service processor attempts a call-out to all of the

following numbers in the order listed:

1. Service Center

2. Customer Administrative Center

3. Pager

v Remote timeout and remote latency are functions of your service provider’s catcher

computer. Either use the defaults or contact your service provider for recommended
settings.

v Number of retries is the number of times you want the server to retry calls that

failed to complete.

Chapter 3. Using the Service Processor 49

Customer Account Setup Menu

This menu allows users to enter information that is specific to their account.

Customer Account Setup Menu

1. Customer Account Number:
Currently Unassigned

2. Customer RETAIN Login userid:
Currently Unassigned

3. Customer RETAIN login password:
Currently Unassigned

98. Return to Previous Menu

0>

v Customer Account Number is assigned by your service provider for record-keeping

and billing. If you have an account number, enter it. Otherwise, leave this field
unassigned.

v Customer RETAIN Login User ID and Customer RETAIN Login Password apply

to a service function to which your service provider might have access. Leave these
fields unassigned if your service provider does not use RETAIN.

Call-out Test

Call-out test is disabled in partitioned systems.

Service Processor Parameters in Service Mode (Full System Partition)

When the system is in service mode, the following service processor functions are
suspended:

v Unattended Start Mode
v Reboot/Restart Policy
v Call-Out
v Surveillance

When service mode is exited, the service processor functions are re-activated.

System Power-On Methods

This section discusses the following system power-on methods:

v Power-on Switch
v Service Processor Menus

Privileged users can power on the system by selecting the System Control Power
Menu option from the main menu and then selecting the Power-on System option
from the System Power Control Menu. General users should select Power-on
System on the General User Menu.

v Remote Power-on via Ring-Indicate Signal

50 Eserver pSeries 690 User’s Guide

The server automatically powers on when it detects a ″ring indicate″ signal from a
modem attached to serial port 1 (S1) or serial port 2 (S2).

A remote user can call the server to activate ring detection by the modem. Listen for
a few more rings than the threshold number for starting the system. The system
powers on without answering the call.

v Unattended start mode - refer to Enable/Disable Unattended Start Mode on page

27.
The service processor can be enabled to recover from the loss of ac power (see

Enable/Disable Unattended Power-On Mode in the SYSTEM POWER CONTROL
MENU). When ac power is restored, the system returns to the power state at the
time ac loss occurred. For example, if the system was powered on when ac loss
occurred, it reboots/restarts when power is restored. If the system was powered off
when ac loss occurred, it remains off when power is restored.

v Timed power-on - refer to the shutdown -t command on servers using AIX.

Working in conjunction with AIX, the Service Processor in your server can operate a
timer, much like the wake-up timer on your clock radio. You can set the timer so that
your server powers on at a certain time after shutting down. The timer is
battery-operated, so power interruptions that occur while the server is off do not
affect its accuracy. Refer to the AIX shutdown -t command for details on setting the
timer.

Note: If an ac power loss (exceeding the hold-up time of any optional IBFs) is in

progress when the timed power-on attempt occurs, the server cannot power
on when ac power is restored.

v Follow-up to a Failed Boot Attempt

The service processor initiates a power-on sequence if a failed boot attempt is
detected (due to a hardware or software failure).

v Fast or Slow Boot (IPL)

Using the service processor menus, you can select the IPL type, mode, and speed of
your system.

Attention: Selecting fast IPL results in several diagnostic tests being skipped and a
shorter memory test being run.

Chapter 3. Using the Service Processor 51

Service Processor Reboot/Restart Recovery

Reboot

reset or power-on. The boot process ends when control passes to the operating system
process.

describes bringing the system hardware back up; for example, from a system

Restart

reinitialized. Restart must follow a successful reboot.

describes activating the operating system after the system hardware is

Boot (IPL) Speed

When the server enters reboot recovery, slow IPL is automatically started, which gives
the POST an opportunity to locate and report any problems that might otherwise be
unreported.

Failure During Boot Process

During the boot process, either initially after system power-on or upon reboot after a
system failure, the service processor monitors the boot progress. If progress stops, the
service processor can reinitiate the boot process (reboot) if enabled to do so. The
service processor can re-attempt this process according to the number of retries
selected in the Reboot/Restart Policy Setup Menu.

Failure During Normal System Operation

When the boot process completes and control transfers to the operating system (OS),
the service processor can monitor operating system activity (see the Set Surveillance
Parameters option in the SERVICE PROCESSOR SETUP MENU). If OS activity stops
due to a hardware- or software-induced failure, the service processor can initiate a
reboot/restart process based on the settings in the Service Processor Reboot/Restart
Policy Setup Menu and the OS automatic restart settings (see the operating system
documentation).

If you are using the AIX operating system, the menu item under SMIT for setting the
restart policy is Automatically Reboot After Crash. The default is false. When the
setting is true, and if the service processor parameter ″Use OS-Defined Restart Policy″
is yes (the default), the service processor takes over for AIX to reboot/restart after a
hardware or surveillance failure.

Service Processor Reboot/Restart Policy Controls

The operating system’s automatic restart policy (see operating system documentation)
indicates the operating system response to a system crash. The service processor can
be instructed to refer to that policy by the Use OS-Defined Restart Policy setup menu.

If the operating system has no automatic restart policy, or if it is disabled, then the
service processor-restart policy can be controlled from the service processor menus.
Use the Enable Supplemental Restart Policy selection.

Use OS-Defined restart policy - The default setting is no. If set to yes on a full system
partition, this causes the service processor to refer to the OS Automatic Restart Policy
setting and take action (the same action the operating system would take if it could
have responded to the problem causing the restart).

52 Eserver pSeries 690 User’s Guide

When this setting is no, or if the operating system did not set a policy, the service
processor refers to enable supplemental restart policy for its action.

This setting is ignored on a partitioned system.

Enable supplemental restart policy - The default setting is yes. When set to yes on a
full system partition, the service processor restarts the server when the operating
system loses control and either:

The Use OS-Defined restart policy is set to No.

OR

The Use OS-Defined restart policy is set to Yes and the operating system has no
automatic restart policy.

If set to Yes on a partitioned system, the service processor restarts the system when
the system loses control and it is detected by service processor surveillance.

Refer to “Service Processor Reboot/Restart Recovery” on page 52.

The following table describes the relationship among the operating system and service
processor restart controls in a full system partition.

OS Automatic
reboot/restart
after crash setting

None No
None No

Service processor to
use OS-Defined
restart policy?

1

1

Service Processor
Enable supplemental
restart policy?

No

1

Yes

System response

Restarts

None Yes No

No
Yes

No
Yes

1

1

1

1

Restarts

Restarts

Restarts

None Yes Yes

2

False

2

False

2

False

2

False
True No
True No

1

No

1

No
Yes No
Yes Yes

1

1

True Yes No Restarts
True Yes Yes

1

Service processor default

2

AIX default

1

Restarts

In a partitioned system, the service processor’s supplemental restart policy is the only
setting that is used, as shown in the following table:

Chapter 3. Using the Service Processor 53

Service Processor enable supplemental

restart policy

No
Yes (default) Restarts

System Response

54 Eserver pSeries 690 User’s Guide

Configuring and Deconfiguring Processors or Memory

All failures that crash the system with a machine check or check stop, even if
intermittent, are reported as a diagnostic callout for service repair. To prevent the
recurrence of intermittent problems and improve the availability of the system until a
scheduled maintenance window, processors and memory books with a failure history
are marked ″bad″ to prevent their being configured on subsequent boots.

A processor or memory book is marked ″bad″ under the following circumstances:
v A processor or memory book fails built-in self-test (BIST) or power-on self-test

(POST) testing during boot (as determined by the service processor).

v A processor or memory book causes a machine check or check stop during runtime,

and the failure can be isolated specifically to that processor or memory book (as
determined by the processor runtime diagnostics in the service processor).

v A processor or memory book reaches a threshold of recovered failures that results in

a predictive callout (as determined by the processor run-time diagnostics in the
service processor).

During boot time, the service processor does not configure processors or memory
books that are marked “bad.”

If a processor or memory book is deconfigured, the processor or memory book remains
offline for subsequent reboots until it is replaced or repeat gard is disabled. The repeat
gard function also provides the user with the option of manually deconfiguring a
processor or memory book, or re-enabling a previously deconfigured processor or
memory book. For information on configuring or deconfiguring a processor, see the
Processor Configuration/Deconfiguration Menu on page 33.

For information on configuring or deconfiguring a memory book, see the Memory
Configuration/Deconfiguration Menu on page 35. Both of these menus are submenus
under the System Information Menu.

You can enable or disable CPU Repeat Gard or Memory Repeat Gard using the
Processor Configuration/Deconfiguration Menu.

Run-Time CPU Deconfiguration (CPU Gard)

L1 instruction cache recoverable errors, L1 data cache correctable errors, and L2 cache
correctable errors are monitored by the processor runtime diagnostics (PRD) code
running in the service processor. When a predefined error threshold is met, an error log
with warning severity and threshold exceeded status is returned to AIX. At the same
time, PRD marks the CPU for deconfiguration at the next boot. AIX will attempt to
migrate all resources associated with that processor to another processor and then stop
the defective processor.

Chapter 3. Using the Service Processor 55

Service Processor System Monitoring - Surveillance

Surveillance is a function in which the service processor monitors the system, and the
system monitors the service processor. This monitoring is accomplished by periodic
samplings called

Surveillance is available during two phases:

v System firmware bringup (automatic)
v Operating system runtime (optional)

Note: Operating system surveillance is disabled on partitioned systems.

heartbeats

.

System Firmware Surveillance

System firmware surveillance is automatically enabled during system power-on. It
cannot be disabled by the user, and the surveillance interval and surveillance delay
cannot be changed by the user.

If the service processor detects no heartbeats during system IPL (for a set period of
time), it cycles the system power to attempt a reboot. The maximum number of retries
is set from the service processor menus. If the fail condition persists, the service
processor leaves the machine powered on, logs an error, and displays menus to the
user. If Call-out is enabled, the service processor calls to report the failure and displays
the operating-system surveillance failure code on the operator panel.

56 Eserver pSeries 690 User’s Guide

Operating System Surveillance

Note: Operating system surveillance is disabled in partitioned systems.

Operating system surveillance provides the service processor with a means to detect
hang conditions, as well as hardware or software failures, while the operating system is
running. It also provides the operating system with a means to detect a service
processor failure caused by the lack of a return heartbeat.

Operating system surveillance is not enabled by default, allowing you to run operating
systems that do not support this service processor option.

You can also use service processor menus and AIX service aids to enable or disable
operating system surveillance.

For operating system surveillance to work correctly, you must set these parameters:

v Surveillance enable/disable
v Surveillance interval

The maximum time the service processor should wait for a heartbeat from the
operating system before timeout.

v Surveillance delay

The length of time to wait from the time the operating system is started to when the
first heartbeat is expected.

Surveillance does not take effect until the next time the operating system is started after
the parameters have been set.

If desired, you can initiate surveillance mode immediately from service aids. In addition
to the three options above, a fourth option allows you to select immediate surveillance,
and rebooting of the system is not necessarily required.

If operating system surveillance is enabled (and system firmware has passed control to
the operating system), and the service processor does not detect any heartbeats from
the operating system, the service processor assumes the system is hung and takes
action according to the reboot/restart policy settings. See “Service Processor
Reboot/Restart Recovery” on page 52.

If surveillance is selected from the service processor menus which are only available at
bootup, then surveillance is enabled by default as soon as the system boots. From
service aids, the selection is optional.

Chapter 3. Using the Service Processor 57

Call-Out (Call-Home)

Note: Call-out is disabled on partitioned systems. The call-out function is handled by

the Service Focal Point application on the Hardware Management Console
(HMC).

The service processor can call out (call-home) when it detects one of the following
conditions:

v System firmware surveillance failure
v Operating system surveillance failure (if supported by operating system)
v Restarts
v Critical hardware failure
v Abnormal operating system termination

To enable the call-out feature, do the following:

1. Connect a modem to any serial port.

2. Set up the following using the service processor menus or diagnostic service aids:

v Enable call-out for the serial port where the modem is connected.
v Enter the modem configuration file name.
v Set up site-specific parameters (phone numbers for call-out, call-out policy,

number of call-out retries, and so on).

3. To call out before restart, set Call-out before restart to ENABLED from the
Reboot/Restart Policy Setup menu.

Note: Some modems, such as IBM 7857-017, are not designed for the paging function.

Although they can be used for paging, they will return an error message when
they do not get the expected response from another modem. Therefore, even
though the paging was successful, the error message will cause the service
processor to retry, continuing to place pager calls for the number of retries
specified in the call-out policy setup menu. These retries result in redundant
pages.

58 Eserver pSeries 690 User’s Guide

Console Mirroring

Console mirroring allows a user on one serial port to monitor the service processor
activities on another serial port. This can be done on the locally attached HMC virtual
terminal window or windows remotely attached through modems. Console mirroring is
supported on any combination of locally or remotely attached monitors.

The serial port from which console mirroring is enabled is called the
mirror port is determined when keyboard input is detected from one of the other two
serial ports. From this point forward, the service processor sends information to the
active port and the mirror port only. Console mirroring ends when the service processor
releases control of the serial ports to the system firmware.

Console mirroring is supported on serial port 1 (S1), serial port 2 (S2), and serial port 3
(S3). Remote attachment through a modem is supported on serial port 1 (S1) and serial
port 2 (S2).

System Configuration

The following describes the configuration for console mirroring:

v Service processor
v Modem connected to one serial port and enabled for incoming calls
v Local HMC virtual terminal window connected to the other serial port. This local

terminal can be connected directly to your server or connected through another
modem.

Console mirroring can be started by either of the following methods:
v Remote session first, then local session added:

1. Remote session is already in progress.

2. Remote user uses service processor menus to enable console mirroring, allowing
both consoles to be active.

v Local session first, then remote session added:

1. Local session is already in progress.

2. The service processor receives a call from the remote user.

3. The local user selects the option to enable console mirroring. The service
processor immediately begins mirroring service processor menus.

primary port

. The

Chapter 3. Using the Service Processor 59

Service Processor Error Logs

The service processor error logs, an example of which follows, contain error conditions
detected by the service processor.

1. 11/30/99 19:41:56 Service Processor Firmware Failure
B1004999

Enter error number for more details.
Press Return to continue, or ’x’ to return to menu.

Press "C" to clear error log, any other key to continue. >

Note: The time stamp in this error log is coordinated universal time (UTC), which is

also referred to as Greenwich mean time (GMT). AIX error logs have additional
information available and can time stamp with local time.

Entering an error number provides nine words of system reference code (SRC) data; an
example screen is shown below.

Detail: 6005

SRC

-----------------------------------

word11:B1004999 word12:0110005D word13:00000000
word14:00000000 word15:00001111 word16:00000000
word17:B1004AAA word18:0114005D word19:A4F1E909

B1004999

Press Return to continue, or ’x’ to return to menu.

Error Log

If Return is pressed, the contents of NVRAM will be dumped 320 bytes at a time,
starting at address 0000.

60 Eserver pSeries 690 User’s Guide

LCD Progress Indicator Log

The following is an example of the LCD progress indicator log. It shows the types of
entries that may appear in the log, and is for example purposes only.

The progress indicator codes are listed from top (latest) to bottom (oldest).

B0FF

0539..17

0538..17

0539..17

0538..17

0539..17
0581

0538..17

0539..12

0538..12

0539..

0821..01-K1-00

0539..

0728..01-R1-00-00

0539..

0664..40-60-00-1,0

0539..

0777..U1.5-P1-I14/E1

0539..

0742..U1.5-P1-I12/E1

0539..

0776..U1.5-P1-I10/T1
E139
E1FB
E139

Press Return to continue, or ’x’ to return to menu. >

E183

EAA1..U1.9-P1-I14
E172..U1.9-P1
E172..U1.9-P1-I14
E172..U1.9-P1
94BB
9109
9380
9108
9107
9106
9105
9118
9104
9103
9102
90FD

LCD Progress Indicator Log

Resetting the Service Processor

Some error conditions might cause the service processor to hang. The service
processor must be reset to recover from a hung condition. If the system is powered on,
resetting the service processor will cause the system to shut down. When the service
processor is reset, it carries out its power-on sequence, including self-tests. Successful
completion of the reset sequence is indicated by OK in the operator panel in the media
drawer.

Chapter 3. Using the Service Processor 61

Before resetting the service processor, if the managed system is powered on and
running AIX, shut down all partitions, or the full system partition. This action causes the
system to shut down and the system power is turned off.

To reset the service processor when the managed system is powered off, perform either
of the following:

v If the service processor is responding to input from the HMC (or ASCII terminal),

select Service Processor Setup Menu from the main menu, then select Reset
Service Processor. This can only be done by a privileged user.

v Put the UEPO switch in the off position, then back to the on position.

Note: Do

not

use the pinhole reset switch to reset the service processor.

62 Eserver pSeries 690 User’s Guide

Service Processor Operational Phases

This section provides a high-level flow of the phases of the service processor.

SP Power Applied

Standby Phase SP Menus Available

Bring-Up Phase SMS Menus Available

Run-time Phase AIX Login Prompt Available

Pre-Standby Phase

This phase is entered when the server is connected to a power source. The server may
or may not be fully powered on. This phase is exited when the power-on self-tests
(POSTs) and configurations tasks are completed.

The pre-standby phase components are:
v Service Processor Initialization - service processor performs any necessary hardware

and software initialization.

v Service Processor POST - service processor conducts power-on self-tests on its

various work and code areas.

v Service Processor Unattended Start Mode Checks - To assist fault recovery. If

unattended start mode is set, the service processor automatically reboots the server.
The service processor does not wait for user input or power-on command, but moves
through the phase and into the bring-up phase. Access the SMS menus or the
service processor menus to reset the unattended start mode.

Pre-Standby Phase

Chapter 3. Using the Service Processor 63

Standby Phase

The standby phase can be reached in either of two ways:
v With the server off and power connected (the normal path), recognized by OK in the

LCD display.
OR

v With the server on after an operating system fault, recognized by an 8-digit code in

the LCD display.

In the standby phase, the service processor takes care of some automatic duties and is
available for menus operation. The service processor remains in the standby phase
until a power-on request is detected.

The standby phase components are as follows:
v Modem Configuration

The service processor configures the modem (if installed) so that incoming calls can
be received, or outgoing calls can be placed.

v Dial In

Monitor incoming phone line to answer calls, prompt for a password, verify the
password, and remotely display the standby menu. The remote session can be
mirrored on the local HMC virtual terminal window if the server is so equipped and if
the user enables this function.

v Menus

The service processor menus are password-protected. Before you can access them,
you need either the general user-password or privileged-user password.

Service processor menus are available on ASCII terminals attached to the serial
ports on the primary I/O book, and on terminal emulators. On HMC-managed
systems, service processor menus are also available on the HMC graphical user
interface.

Bring-Up Phase

On a system that is powered-on to full system partition, this phase is entered upon
power-on, and exited upon loading of the operating system.

On a system that is powered-on to partition standby, this phase is entered upon
power-on, and exited when the partition manager and hypervisor have been loaded and
become fully operational in system memory. The end of this phase is indicated when
LPAR displays on the operator panel. At this point, the server can start multiple logical
partitions which would be activated through the HMC graphical user interface.

The bring-up phase components are as follows:
v Retry Request Check

The service processor checks to see if the previous boot attempt failed. If the
specified number of failures are detected, the service processor displays an error
code and places an outgoing call to notify an external party if the user has enabled
this option.

v Dial Out

64 Eserver pSeries 690 User’s Guide

v Update Operator Panel

v Environmental Monitoring

v System Firmware Surveillance (Heartbeat Monitoring)

v Responding to System Processor Commands

Run-Time Phase

This phase includes the tasks that the service processor performs during steady-state
execution of the operating system.

v Environmental Monitoring

v Responding to System Processor Commands

v Run-Time Surveillance (not supported on partitioned systems)

v HMC surveillance

The service processor can dial a preprogrammed telephone number in the event of
an IPL failure. The service processor issues an error report with the last reported IPL
status indicated and any other available error information.

The service processor displays operator panel data on the HMC virtual terminal
window if a remote connection is active.

The service processor provides expanded error recording and reporting.

The service processor monitors and times the interval between system firmware
heartbeats.

The service processor responds to any command issued by the system processor.

The service processor monitors voltages, temperatures, and fan speeds (on some
servers).

The service processor responds to any command issued by the system processor.

If the device driver is installed and surveillance enabled, the service processor
monitors the system heartbeat. If the heartbeat times out, the service processor
places an outgoing call. This is different from the bring-up phase scenario, where the
specified number of reboot attempts are made before placing an outgoing call.

On an HMC-managed system, the service processor monitors the communication link
between the managed system and the HMC. If the service processor detects that this
communication link has been broken, it will post an error to the operating system
running on the managed system.

Chapter 3. Using the Service Processor 65

66 Eserver pSeries 690 User’s Guide

Chapter 4. Using System Management Services

Use the system management services menus to view information about your system or
partition, and to perform tasks such as setting a password, changing the boot list, and
setting the network parameters.

To start the text-based System Management Services, press the number 1 key on the
terminal or in the virtual terminal window on the HMC after the word keyboard appears
and before the word speaker appears. After the text-based System Management
Services starts, the following screen displays.

Main Menu

1 Select Language
2 Change Password Options (NOT available in LPAR mode)
3 View Error Log
4 Setup Remote IPL (Initial Program Load)
5 Change SCSI Settings
6 Select Console (NOT available in LPAR mode)
7 Select Boot Options

-------------------------------------------------------------------------------------------------­Navigation keys:

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

Note: The System Management Services menus can also be started using the Service

Processor Boot Mode Menu. See page 31.

X = eXit System Management Services

On all menus except the Main Menu, there are several navigation keys:

M Return to the main menu.
ESC Return to the previous menu.
X Exit the System Management Services and start the operating system.

If X is entered, you are asked to confirm your choice to exit the SMS menus
and start the operating system.

67

When there is more than one page of information to display, the following additional
navigation keys display:

N Display the next page of the list.
P Display the next page of the list.

Note: The lowercase navigation key has the same effect as the uppercase key that is

On each menu screen, you can choose either a menu item and press Enter (if
applicable), or select a navigation key.

Select Language

Note: Your TTY must support the ISO-8859 character set to properly display languages

This option allows you to change the language used by the text-based System
Management Services menus.

shown on the screen. For example, either
menu.

other than English.

SELECT LANGUAGE

1. English

2. Francais

3. Deutsch

4. Italiano

5. Espanol

morM

takes you back to the main

--------------------------------------------------------------------------------------------------

Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

--------------------------------------------------------------------------------------------------

Type the number of the menu item and press Enter or Select a Navigation key: _

68 Eserver pSeries 690 User’s Guide

Password Utilities

Note: This option is disabled in partitioned systems.

The Password Utilities menu enables you to select from password utilities.

Password Utilities

1 Set Privileged-Access Password
2 Remove Privileged-Access Password

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

Set Privileged-Access Password

The privileged-access password protects against the unauthorized starting of the
system programs.

Note: If the privileged-access password has been enabled, you are asked for the

privileged-access password at startup every time you boot your system.

View Error Log

If you previously had set a privileged-access password and want to remove it, select
Remove Privileged-Access Password.

Use this option to view or clear your system’s error log. A menu similar to the following
displays when you select this option.

Error Log

Entry 1. 01/04/96 12:13:22 25A80011 00-00
Entry 2. no error logged

1. Clear error log

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

Date Time Error Code Location

Chapter 4. Using System Management Services 69

Note: The time stamp in this error log is coordinated universal time (UTC), which is

also referred to as Greenwich mean time (GMT). AIX error logs have more
information available and can time stamp with your local time.

70 Eserver pSeries 690 User’s Guide

Setup Remote IPL (Initial Program Load)

This option allows you to enable and set up the remote startup capability of your
system unit. You must first specify the network parameters.

Network Parameters

1. IP Parameters

2. Adapter Parameters

3. Ping Test

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

Selecting the IP Parameters option displays the following menu.

IP Parameters

1. Client IP Address [000.000.000.000]

2. Server IP Address [000.000.000.000]

3. Gateway IP Address [000.000.000.000]

4. Subnet Mask [255.255.255.000]

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

To change IP (Internet Protocol) parameters, type the number of the parameters for
which you want to change the value.

Attention: If the client system and the server are on the same subnet, set the
gateway IP address to [0.0.0.0].

Chapter 4. Using System Management Services 71

Selecting the Adapter Parameters option allows you to view an adapter’s hardware
address, as well as configure network adapters that require setup. A menu similar to the
following displays.

Device Slot Hardware Address

1. 10/100 Ethernet Adapter U1.9-P1-I4/E1 000629aca72d

2. 10/100 Ethernet Adapter U1.5-P2-I3/E1 0020357A0530

3. High Speed Token-Ring Adapter U1.5-P1-I3/T1 000629be04e1

4. Gigabit Ethernet PCI Adapter U1.1-P2-I3/T1 0004ac7c9ec7

--------------------------------------------------------------------------------------------------

Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

--------------------------------------------------------------------------------------------------

Type the number of the menu item and press Enter or Select a Navigation key: _

Entering adapter parameters on these screens will automatically update the parameters
on the ping test screen.

Selecting an adapter on this menu displays configuration menus for that adapter:

10/100 Ethernet TP PCI Adapter

1. Data Rate [Auto]

2. Full Duplex [Yes]

--------------------------------------------------------------------------------------------------

Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

--------------------------------------------------------------------------------------------------

Type the number of the menu item and press Enter or Select a Navigation key: _

72 Eserver pSeries 690 User’s Guide

Selecting the Data Rate option allows you the change the media usedd by the Ethernet
adapter:

Data Rate

1. 10 Mbps

2. 100 Mbps

3. Auto

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

Selecting the Full Duplex option allows you to change how the Ethernet adapter
communicates with the network:

Full Duplex

1. Yes

2. No

3. Auto

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

From the Network Parameters Menu, select Ping to test a connection to a remote
system unit. After selecting the Ping option, you must choose which adapter
communicates with the remote system.

Chapter 4. Using System Management Services 73

Adapter Parameters

Device Slot Hardware Address

1. 10/100 Ethernet Adapter U1.9-P1-I4/E1 000629aca72d

2. 10/100 Ethernet Adapter U1.5-P2-I3/E1 0020357A0530

3. High Speed Token-Ring Adapter U1.5-P1-I3/T1 000629be04e1

4. Gigabit Ethernet PCI Adapter U1.1-P2-I3/T1 0004ac7c9ec7

--------------------------------------------------------------------------------------------------

Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

--------------------------------------------------------------------------------------------------

Type the number of the menu item and press Enter or Select a Navigation key: _

After selecting an adapter, you will be asked to set the parameters for the adapter; a
menu similar to the following displays:

Adapter Parameters
10/100 Ethernet Adapter

1. Data Rate [Auto]

2. Full Duplex [Auto]

3. Continue with Ping

--------------------------------------------------------------------------------------------------

Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

--------------------------------------------------------------------------------------------------

Type the number of the menu item and press Enter or Select a Navigation key: _

74 Eserver pSeries 690 User’s Guide

After choosing which adapter to use to ping the remote system, and setting its
parameters, you must provide the addresses needed to communicate with the remote
system.

Ping Test

1. Client IP Address [129.132.4.20]

2. Server IP Address [129.132.4.10]

3. Gateway IP Address [129.132.4.30]

4. Subnet Mask [255.255.255.0]

5. Execute Ping Test

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

If changes to the adapter parameters must be made in this screen, entering those
changes will not automatically update the Adapter Parameters screen. Go back to the
adapter parameters menu to make any changes.

Notes:

1. After the ping test is initiated, it might take up to 60 seconds to return a result.

2. When the ping test completes, the firmware stops and waits for a key to be pressed

before continuing.

Change SCSI Settings

This option allow you to view and change the addresses of the SCSI controllers
attached to your system.

SCSI Utilities

1. Hardware Spin Up Delay

2. Change SCSI Id

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

Chapter 4. Using System Management Services 75

Select Console

Note: This option is disabled in partitioned systems.

The Select Console option allows the user to select the console to use to display the
SMS menus. This selection is valid only for the SMS menus and does not affect the
display used by the AIX operating system.

Follow the instructions that display on the screen. The firmware automatically returns to
the SMS main menu.

Select Boot Options

Use this menu to view and set various options regarding the installation devices and
boot devices.

1. Select Install or Boot a Device

2. Select Boot Devices

3. Multiboot Startup

--------------------------------------------------------------------------------------------------

Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

--------------------------------------------------------------------------------------------------

Type the number of the menu item and press Enter or Select a Navigation key: _

The following options are explained as follows:

1. Select Install or Boot a Device allows you to select a device to boot from or to
install the operating system from. This selection is for the current boot only.

2. Select Boot Devices allows you to set the boot list.

3. Multiboot Startup toggles the multiboot startup flag, which controls whether the
multiboot menu is invoked automatically on startup.

76 Eserver pSeries 690 User’s Guide

If Diskette is selected, the following menu is displayed:

Select Device Type

1. Diskette

2. Tape

3. CD/DVD

4. IDE

5. Hard Drive

6. Network

7. None

8. List All Devices

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

If a device is selected that does not reside in the system, a menu with the following
message displays:

.---------------------------------------------------------.
| THE SELECTED DEVICES WERE NOT DETECTED IN THE SYSTEM ! |
| Press any key to continue. |
`---------------------------------------------------------’

If Hard Drive is selected, the following menu displays:

Select Hard Drive Type

1. SCSI

2. SSA

3. SAN

4. None

5. List All Devices

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

Chapter 4. Using System Management Services 77

If List All Devices is selected, a menu similar to the following displays, depending on
the devices that are installed in the system:

Select Device
Device Current Device
Number Position Name

1. 1 SCSI 18200 MB Harddisk (loc=U1.9-P2/Z1-A8,O)

2. - SCSI 18200 MB Harddisk (loc=U1.9-P2/Z1-A9,0)

3. - SCSI 18200 MB Harddisk (loc=U1.9-P2/Z1-Aa,0)

4. None

5. List all devices

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

The appropriate device can then be selected for this boot or installation.

When a device is selected for installing the operating system, or to boot from, the
Select Task menu allows you to get more information about the device, or to boot from
that device in normal mode or service mode. The following is an example of this menu.

Select Task

SCSI 18200 MB Harddisk (loc=U1.9-P2/Z1-A8,0)

1. Information

2. Normal Mode Boot

3. Service Mode Boot

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

If either Normal Mode Boot or Service Mode Boot is selected, the next screen
requests confirmation. If you answer yes, the device will be booted in the appropriate
mode. If you answer no, the firmware will return to the Select Task menu.

78 Eserver pSeries 690 User’s Guide

Select Boot Devices

Select this option to view and change the customized boot list, which is the sequence of
devices read at startup.

Configure Boot Device Order

1. Select 1st Boot Device

2. Select 2nd Boot Device

3. Select 3rd Boot Device

4. Select 4th Boot Device

5. Select 5th Boot Device

6. Display Current Setting

7. Restore Default Setting

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

When any of the Boot Device options are selected, the Select Device Type screen
displays, which will be similar to the following.

Select Device Type

1. Diskette

2. Tape

3. CD/DVD

4. IDE

5. Hard Drive

6. Network

7. None

8. List All Devices

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

Chapter 4. Using System Management Services 79

When a device type is selected, Select Task menu displays, similar to the following:

Select Task

SCSI 18200 MB Harddisk (loc=U1.9-P2/Z1-A8,0)

1. Information

2. Set Boot Sequence: Configure as 1st Boot Device

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

Selecting Information displays a menu similar to the following for a hard disk.

Device Information

/pci@3fffdf0a000/pci@2,4/scsi@1/sd@8,0

DEVICE : SCSI 18200 MB Harddisk (U1.9-P2/Z1-A8,0)
NAME : sd
DEVICE-TYPE : block

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

: (Integrated) (Bootable)

The Set Boot Sequence option allows you to set the location of the device in the boot
list.

80 Eserver pSeries 690 User’s Guide

Display Current Settings

This option displays the current setting of the customized boot list. An example of this
menu, with one device in the boot list, follows.

Current Boot Sequence

1. SCSI 18200 MB Harddisk (loc=U1.9-P2/Z1-A8,0)

2. None

3. None

4. None

5. None

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

Restore Default Settings

This option restores the boot list to the default boot list. The default boot list will vary,
depending on the devices that are installed in the system.

The default boot list is:

1. Primary diskette drive (if installed)

2. CD-ROM drive (if installed)

3. Tape drive (in installed)

4. Hard disk drive (if installed)

5. Network adapter

-------------------------------------------------------------------------------------------------­Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services

-------------------------------------------------------------------------------------------------­Type the number of the menu item and press Enter or Select a Navigation key: _

Chapter 4. Using System Management Services 81

Multiboot Startup

The Multiboot Startup option controls whether the multiboot menu is invoked
automatically on startup.

Exiting System Management Services

After you have finished using the system management services, type x (for exit) at the
Utilities menu to boot your system or partition. On all other screens, typing x returns
you to the previous screen.

82 Eserver pSeries 690 User’s Guide

Chapter 5. Using the Online and Standalone Diagnostics

The diagnostics consist of online diagnostics and standalone diagnostics.

Attention: The AIX operating system must be installed in a partition in order to run
online diagnostics on that partition. If the AIX operating system is not installed, use the
standalone diagnostic procedures.

Online diagnostics, when they are installed, reside with AIX in the file system. They can
be booted:

v In single user mode (referred to as
v To run in maintenance mode (referred to as
v To run concurrently with other applications (referred to as

Standalone diagnostics must be booted before they can be run. If booted, the
diagnostics have no access to the AIX error log or the AIX configuration data.

Online and Standalone Diagnostics Operating Considerations

Note: When possible, run online diagnostics in service mode. Online diagnostics

perform additional functions compared to standalone diagnostics. Running online
diagnostics in service mode ensures that the error state of the system that has
been captured in NVRAM is available for your use in analyzing the problem. The
AIX error log and certain SMIT functions are only available when diagnostics are
run from the disk drive.

service mode

maintenance mode

)

)

concurrent mode

)

Consider the following items before using the diagnostics:
v Standalone diagnostics can run on systems configured for either a full (or single)

system partition or a multiple partitioned system. When running in a partitioned
system, the device from which you are booting standalone diagnostics must be made
available to the partition dedicated to running standalone diagnostics. This may
require moving the device from the partition that currently contains the boot device
(for example, the CD-ROM or network adapter connected to the NIM server that has
a standalone diagnostic image) to the partition used to run standalone diagnostics. If
you move devices, reboot both partitions. For more information, see “Standalone
Diagnostic Operation” on page 88.

v When diagnostics are installed, the device support for some devices might not get

installed. If this is the case, that device does not display in the diagnostic test list
when running disk-based diagnostics.

v When running diagnostics in a partitioned system, diagnostics will work only with the

resources that were assigned to that partition. You must run diagnostics in the
partition containing the resource that you want to test.

83

Identifying the Terminal Type to the Diagnostics

When you run diagnostics, you must identify which type of terminal you are using. If the
terminal type is not known when the FUNCTION SELECTION menu is displayed, the
diagnostics do not allow you to continue until a terminal is selected from the DEFINE
TERMINAL option menu.

Undefined Terminal Types

If you specify an undefined terminal type from the DEFINE TERMINAL option menu, the
menu prompts the user to enter a valid terminal type. The menu redisplays until either a
valid type is entered or you exit the DEFINE TERMINAL option.

Resetting the Terminal

If you enter a terminal type that is valid (according to the DEFINE TERMINAL option
menu) but is not the correct type for the Hardware Management Console for pSeries
(HMC) virtual terminal window being used, you may be unable to read the screen, use
the function keys, or use the Enter key. Bypass these difficulties by pressing Ctrl-C to
reset the terminal. The screen display that results from this reset depends on the mode
in which the system is being run:

v Online Normal or Maintenance Mode - The command prompt displays.
v Standalone Mode or Online Service Mode - The terminal type is reset to dumb, the

Diagnostic Operating Instruction panel displays, and you are required to go through
the DEFINE TERMINAL process again.

Running Online Diagnostics

Consider the following when you run the online diagnostics from a server or a disk:
v The diagnostics cannot be loaded and run from a disk until the AIX operating system

has been installed and configured.

v The diagnostics cannot be loaded on a system (client) from a server if that system is

not set up to boot from a server over a network. When the system is set up to boot
from a server, the diagnostics are run in the same manner as they are from disk.

v On full system partitions, if the diagnostics are loaded from disk or a server, you

must shut down the AIX operating system before turning off the system unit to
prevent possible damage to disk data. Do this in either of the following ways:

– If the diagnostics were loaded in standalone mode, press the F3 key until

DIAGNOSTIC OPERATING INSTRUCTIONS displays. Then press the F3 key once again
to shut down the AIX operating system.

– If the diagnostics were loaded in maintenance or concurrent mode, type the

shutdown -F command.

v Under some conditions, the system might stop, with instructions displayed on

attached displays and terminals. Follow the instructions to select a console display.

84 Eserver pSeries 690 User’s Guide

Online Diagnostics Modes of Operation

Note: When running online diagnostics on a partition in a partitioned system,

diagnostics can be run only on resources that are allocated to that partition.

The online diagnostics can be run in the following modes:

v Service Mode
v Concurrent Mode
v Maintenance Mode

Service Mode

Service mode provides the most complete checkout of the system resources. This
mode also requires that no other programs be running on the partition or system on a
full system partition. All partition or system on a full system partition resources, except
the SCSI adapter and the disk drives used for paging, can be tested. However, note
that the memory and processor are only tested during POST, and the results of the
POST tests are reported by diagnostics.

Error-log analysis is done in service mode when you select the Problem Determination
option on the DIAGNOSTIC MODE SELECTION menu.

Running Online Diagnostics in Service Mode

To run the online diagnostics in service mode from the boot hard disk, do the following:

1. From the HMC, select the Partition Manager.

2. Right-click on the mouse and select Open Terminal Window.

3. From the Service Processor Menu on the VTERM, select Option 2 System Power
Control.

4. Select option 6. Verify that the state changes to currently disabled. Disabling
fast system boot automatically enables slow boot.

5. Select Option 98 to exit the system power control menu.

6. Use the HMC to power on the managed system in a full system partition by
selecting the managed system in the Contents area.

7. Right-click or select the desired system in the Contents area. Next, on the menu,
choose Selected.

8. Select Power On.

9. Select the Power on Diagnostic Stored Boot list option see the

Management Console for pSeries Installation and Operations Guide

SA38-0590, for more information about full system partitions).

10. Make sure that there are no media in the devices in the media subsystem.

11. Enter any passwords, if requested.

IBM Hardware

, order number

Chapter 5. Using the Online and Standalone Diagnostics 85

Concurrent Mode

Use concurrent mode to run online diagnostics on some of the system resources while
the system is running normal activity.

Because the system is running in normal operation, the following resources cannot be
tested in concurrent mode:

v SCSI adapters connected to paging devices
v Disk drive used for paging
v Some display adapters and graphics related devices
v Memory (tested during POST)
v Processor (tested during POST)

The following levels of testing exist in concurrent mode:
v The share-test level tests a resource while the resource is being shared by

programs running in the normal operation. This testing is mostly limited to normal
commands that test for the presence of a device or adapter.

v The sub-test level tests a portion of a resource while the remaining part of the

resource is being used in normal operation. For example, this test could test one port
of a multiport device while the other ports are being used in normal operation.

v The full-test level requires the device not be assigned to or used by any other

operation. This level of testing on a disk drive might require the use of the varyoff
command. The diagnostics display menus to allow you to vary off the needed
resource.

Note: If you are unable to load the diagnostics to the point when the DIAGNOSTIC

OPERATING INSTRUCTIONS display, go to “Step 2.5 Loading the Standalone

Diagnostics from CD-ROM” on page 142.

Error-log analysis is done in concurrent mode when you select the Problem
Determination option on the DIAGNOSTIC MODE SELECTION menu.

To run the online diagnostics in concurrent mode, you must be logged in to the AIX
operating system and have proper authority to issue the commands (if help is needed,
see the system operator).

The diag command loads the diagnostic controller and displays the online diagnostic
menus.

Running the Online Diagnostics in Concurrent Mode

To run online diagnostics in concurrent mode, do the following:

1. Log in to the AIX operating system as root user or use CE Login.

2. Enter the diag command.

3. When the DIAGNOSTIC OPERATING INSTRUCTIONS display, follow the
instructions to check out the desired resources.

86 Eserver pSeries 690 User’s Guide