IBM Eserver pSeries 670 User Manual
ERserver
IBM
pSeries 670
User’s Guide
SA38-0614-00
ER ser ver
IBM
pSeries 670
User’s Guide
SA38-0614-00
First Edition (April 2002)
Before using this information and the product it supports, read the information in “Safety Notices” on page ix,
Appendix B, “Environmental Notices” on page 135, and Appendix C, “Notices” on page 137.
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, 11400 Burnet Road, Austin, Texas 78758-3493. To send
comments electronically, use this commercial internet address: aix6kpub@austin.ibm.com. Any information that you
supply may be used without incurring any obligation to you.
© International Business Machines Corporation, 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 pSeries 670 ...............1
System Configurations......................2
Partitioned System Overview ...................3
Partition Profiles.......................3
System Profiles .......................4
Types of Partitions ......................4
Chapter 2. Using the Eserver pSeries 670 ..............7
Hardware Management Console (HMC) Overview and Setup .........7
System Power-on Methods ....................7
Powering the Server On and Off ..................7
Powering On the Processor Subsystem using the HMC..........8
Powering Off the Processor Subsystem Using the HMC .........8
Graphics Console Support ....................8
Reading the Operator Panel Display .................9
Checkpoints ........................9
Understanding the Power-On Self-Test (POST) .............10
POST Indicators ......................10
POST Keys ........................10
Chapter 3. Using the Service Processor...............13
Service Processor Menus ....................13
Accessing the Service Processor Menus Locally............14
Accessing the Service Processor Menus Remotely ...........14
Saving and Restoring Service Processor Settings ...........14
Menu Inactivity.......................14
General User Menu ......................15
Privileged User Menus .....................17
Main Menu ........................17
Service Processor Setup Menu .................19
Passwords ........................20
System Power Control Menu ..................25
System Information Menu ...................30
iii
Language Selection Menu ...................35
Call-In/Call-Out Setup Menu ..................36
Modem Configuration Menu ..................37
Serial Port Selection Menu ...................38
Serial Port Speed Setup Menu .................39
Telephone Number Setup Menu .................40
Call-Out Policy Setup Menu ..................42
Customer Account Setup Menu .................43
Call-out Test........................43
Service Processor Parameters in Service Mode (Full System Partition) .....43
System Power-On Methods ...................43
Service Processor Reboot/Restart Recovery ..............46
Boot (IPL) Speed ......................46
Failure During Boot Process ..................46
Failure During Normal System Operation ..............46
Service Processor Reboot/Restart Policy Controls ...........47
Configuring and Deconfiguring Processors or Memory...........49
Run-Time CPU Deconfiguration (CPU Gard) .............49
Service Processor System Monitoring - Surveillance ...........50
System Firmware Surveillance..................50
Operating System Surveillance .................51
Call-Out (Call-Home)......................52
Console Mirroring .......................53
System Configuration ....................53
Service Processor Error Logs ...................54
LCD Progress Indicator Log ...................55
Service Processor Operational Phases ................56
Pre-Standby Phase .....................56
Standby Phase.......................57
Bring-Up Phase ......................57
Runtime Phase.......................58
Chapter 4. Using System Management Services ............59
Password Utilities .......................60
Display Error Log .......................61
Remote Initial Program Load Setup .................62
IP Parameters .......................63
Adapter Parameters .....................64
Ping ..........................65
SCSI Utilities........................66
Select Console........................66
Multiboot ..........................67
Select Software ......................67
Software Default ......................68
Select Install Device .....................68
Select Boot Devices .....................68
Multiboot Startup <OFF> ...................71
Select Language .......................71
OK Prompt .........................71
Exiting System Management Services ................71
iv Eserver pSeries 670 User’s Guide
Chapter 5. Using the Online and Standalone Diagnostics ........73
Online and Standalone Diagnostics Operating Considerations ........73
Identifying the Terminal Type to the Diagnostics ............74
Undefined Terminal Types ...................74
Running Online Diagnostics ..................74
Online Diagnostics Modes of Operation ...............75
Service Mode .......................75
Running Online Diagnostics in Service Mode .............75
Concurrent Mode ......................76
Running the Online Diagnostics in Concurrent Mode ..........76
Maintenance Mode .....................77
Running the Online Diagnostics in Maintenance Mode..........77
Standalone Diagnostic Operation ..................78
Performing Slow Boot ....................78
Partitioned System Considerations for Standalone Diagnostics .......78
Considerations for Running Standalone Diagnostics from CD-ROM .....79
Loading the Standalone Diagnostics from CD-ROM...........79
Running Standalone Diagnostics from a Network Installation Management (NIM)
Server .........................79
NIM Server Configuration ...................80
Client Configuration and Booting Standalone Diagnostics from the NIM Server 81
Chapter 6. Introducing Tasks and Service Aids ............83
Tasks ...........................84
Add Resource to Resource List ..................85
AIX Shell Prompt .......................85
Analyze Adapter Internal Log ...................86
Backup and Restore Media....................86
Certify Media ........................86
Change Hardware Vital Product Data ................87
Configure Dials and LPF Keys...................87
Configure Reboot Policy.....................87
Configure Remote Maintenance Policy ................88
Configure Ring Indicate Power-On Policy ...............90
Configure Surveillance Policy ...................91
Create Customized Configuration Diskette...............91
Delete Resource from Resource List ................91
Disk Maintenance .......................92
Disk to Disk Copy ......................92
Display/Alter Sector .....................93
Display Configuration and Resource List ...............93
Display Firmware Device Node Information ..............93
Display Hardware Error Report ..................93
Display Hardware Vital Product Data ................93
Display Machine Check Error Log .................94
Display Microcode Level.....................94
Display or Change Bootlist ....................94
Display or Change Diagnostic Run-Time Options ............94
Display Previous Diagnostic Results.................95
Display Resource Attributes ...................96
Contents v
Display Service Hints......................96
Display Software Product Data ..................96
Display System Environmental Sensors ...............96
Examples ........................98
Display Test Patterns......................98
Download Microcode......................98
Download Microcode to PCI SCSI RAID Adapter ...........99
Download Microcode to Disk Drive Attached to a PCI SCSI RAID Adapter . . . 99
Download Microcode to a PCI FC-AL Adapter ............99
Download Microcode to DVD-RAM Attached to a PCI SCSI Adapter .....99
Download Microcode to Disk attached to PCI SCSI adapter .......100
Download Microcode to Other Devices ..............100
Fibre Channel RAID Service Aid .................101
Flash SK-NET FDDI Firmware ..................102
Format Media........................102
Hardfile Attached to SCSI Adapter (non-RAID) ............102
Hardfile Attached to PCI SCSI RAID Adapter ............103
Optical Media.......................104
Diskette Format ......................104
Generic Microcode Download ..................104
Hot-Plug Task........................105
PCI Hot Plug Manager ....................105
SCSI Hot Swap Manager ...................107
RAID Hot Plug Devices ...................108
Local Area Network Analyzer...................108
Log Repair Action ......................109
Periodic Diagnostics .....................109
PCI RAID Physical Disk Identify..................109
Process Supplemental Media ..................109
Run Diagnostics .......................110
Run Error Log Analysis.....................110
Run Exercisers .......................110
Exerciser Commands (CMD) ..................110
Abbreviations .......................111
Memory Exerciser .....................111
Save or Restore Hardware Management Policies ............112
SCSI Bus Analyzer ......................112
SCSI Tape Drive Service Aid ...................113
Spare Sector Availability ....................114
SSA Service Aid .......................114
Update Disk-Based Diagnostics ..................114
Update System or Service Processor Flash ..............115
Partitions ........................115
7318 Serial Communications Network Server Service Aid .........116
Chapter 7. Verifying the Hardware Operation ............117
Step 1. Considerations Before Running This Procedure ..........117
Step 2. Loading the Online Diagnostics in Service Mode .........117
Step 2.5 Loading the Standalone Diagnostics from CD-ROM ........118
Step 3. Running System Verification ................118
vi Eserver pSeries 670 User’s Guide
Step 4. Performing Additional System Verification ............119
Step 5. Stopping the Diagnostics .................119
Chapter 8. Hardware Problem Determination ............121
Problem Determination Using the Standalone or Online Diagnostics ......121
Problem Determination When Unable to Load Diagnostics .........127
Appendix A. Communications Statements .............131
Federal Communications Commission (FCC) Statement..........131
European Union (EU) Statement .................131
International Electrotechnical Commission (IEC) Statement.........132
United Kingdom Telecommunications Safety Requirements.........132
Avis de conformité aux normes du ministère des Communications du Canada 132
Canadian Department of Communications Compliance Statement ......132
VCCI Statement .......................132
Electromagnetic Interference (EMI) Statement - Taiwan ..........133
Radio Protection for Germany ..................133
Appendix B. Environmental Notices................135
Product Recycling and Disposal..................135
Environmental Design .....................135
Acoustical Noise Emissions ...................136
Declared Acoustical Noise Emissions ...............136
Appendix C. Notices .....................137
Appendix D. Service Processor Setup and Test ...........139
Service Processor Setup Checklist .................139
Testing the Setup ......................140
Testing Call-In ......................140
Testing Call-Out ......................141
Serial Port Configuration ...................141
Appendix E. Modem Configurations................143
Sample Modem Configuration Files ................143
Generic Modem Configuration Files ...............143
Specific Modem Configuration Files ...............143
Configuration File Selection ...................144
Examples for Using the Generic Sample Modem Configuration Files ....145
Customizing the Modem Configuration Files.............146
IBM 7852-400 DIP Switch Settings................146
Xon/Xoff Modems .....................147
Ring Detection ......................148
Terminal Emulators .....................148
Recovery Procedures ....................148
Transfer of a Modem Session ..................149
Recovery Strategy .....................150
Prevention Strategy.....................150
Modem Configuration Sample Files ................151
Sample File modem_m0.cfg ..................151
Contents vii
Sample File modem_m1.cfg ..................154
Sample File modem_z.cfg...................157
Sample File modem_z0.cfg ..................160
Sample File modem_f.cfg ...................163
Sample File modem_f0.cfg ..................166
Sample File modem_f1.cfg ..................169
Index ..........................173
viii Eserver pSeries 670 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.
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.
DANGER
To prevent electrical shock hazard, disconnect all power cables from the
electrical outlet before relocating the system.
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.
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.
x Eserver pSeries 670 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 670 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 Web site at: http://www.ibm.com/servers/eserver/pseries/library/hardware_docs/
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 on how to set up and cable the server and verify server operation.
v The Eserver
reference information, maintenance analysis procedures (MAPs), error codes,
removal and replacement procedures, and a parts catalog.
v The
SA38-0603, provides information to system administrators on how to install and use
a Hardware Management Console (HMC) to manage a system.
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
Site and Hardware Planning Information
pSeries 670 Installation Guide
pSeries 670 Service Guide
, order number SA23-2652, contains translations
, order number SA38-0508, contains
, order number SA38-0613, contains
, order number SA38-0615, contains
Hardware Management Console for pSeries Operations Guide
, order number
xiii
Trademarks
v The
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
number SA38-0509, contains diagnostic information, service request numbers
(SRNs), and failing function codes (FFCs).
v The
RS/6000 and
Bus Systems
devices, and cables for your server. This manual is intended to supplement the
service information found in the
PCI Adapter Placement Reference
v The
information regarding 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 e (logo)
v IBM
v pSeries
Other company, product, and service names may be trademarks or service marks of
others.
Eserver
Eserver
, order number SA38-0516, contains information about adapters,
Diagnostic Information for Multiple Bus Systems
Adapters, Devices and Cable Information for Multiple
Diagnostic Information for Multiple Bus Systems
, order number SA38-0538, contains
, order number
, order
.
xiv Eserver pSeries 670 User’s Guide
Chapter 1. Introducing the pSeries 670
The Eserver pSeries 670 system is a shared multiprocessor server.
The system can be configured (or partitioned) to be used as multiple separate systems.
This configuration is known as a logically partitioned system.
The following illustration shows an Eserver pSeries 670 containing two Internal Battery
Feature drawers.
2
3
4
5
6
7
8
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 671 Processor
Subsystem
4 7040 Model 671 Media Drawer
5 7040 Model 61R Integrated Battery
Feature (IBF) (Optional) for the
Power Subsystem.
Redundant 7040 Model 61R
Integrated Battery Feature (IBF)
(Optional) is placed in the rear.
1
6 7040 Model 61D I/O Subsystem
7 7040 Model 61D I/O Subsystem
(Optional)
8 7040 Model 61D I/O Subsystem
(Optional)
1
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 670 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 670s attached to one Hardware Management Console (HMC)
The following components make up the base configuration of the pSeries 670:
v Rack and Bulk Power Subsystem (BPA) The BPA is the main power control unit for
the Eserver pSeries 670. 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 two processor modules, up to 8
L3 cache modules, up to 2 I/O books, up to 4 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 4 GB, and the maximum amount of memory is 128 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 Internal 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.
v I/O Drawers The I/O drawer is a 4 EIA-unit drawer containing up to 16 disk drives, 4
DASD backplanes, a midplane card, 4 cooling fans and 2 power supplies (which are
independent of the bulk power assembly). The rack configuration can have up to 3
I/O drawers.
2 Eserver pSeries 670 User’s Guide
Note: For configurations only using 1 I/O board with no additional I/O drawers, only
the two DASD backplanes (allowing the installation of up to 8 disk drives) are
available.
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 is a special type of logical partition in which processors and system
memory are allocated in a pre-defined way that may increase performance when
running some types of applications (memory is assigned to a processor that is in close
physical proximity to it).
The HMC allows you to perform many hardware management tasks for your managed
system, including configuring logical partitions. You can choose to operate your
managed system as a single server (called full system partitions), or you can choose to
run multiple partitions.
logical partitions
, is capable of running
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 3 processors, 2
gigabytes of memory, and I/O slots 6, 11, and 12 when activated.
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
Chapter 1. Introducing the Eserver pSeries 670 3
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 pre-defined 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 pre-defined.
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 no conflicts exist between the two environments.
4 Eserver pSeries 670 User’s Guide
An affinity partition is a special type of logical partition in which
For more detail on partitions, see the
Operations Guide
, order number SA38-0603.
Hardware Management Console for pSeries
Chapter 1. Introducing the Eserver pSeries 670 5
6 Eserver pSeries 670 User’s Guide
Chapter 2. Using the Eserver pSeries 670
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 Eserver pSeries 670 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 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.
Hardware Management Console for
.
checkpoints
, are visible on the media subsystem
7
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 Operations Guide
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 selected 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 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 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.
Hardware
for more information on HMC
Note: Only logic power will be removed; 350V dc power will still be present within the
system.
Graphics Console Support
The Eserver pSeries 670 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.
8 Eserver pSeries 670 User’s Guide
Reading the Operator Panel Display
The operator panel display is located in the media drawer of the Eserver pSeries 670
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 use only)
3 Operator panel display 6 Disturbance or system attention LED
R
Chapter 2. Using the Eserver pSeries 670
9
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.
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.
10 Eserver pSeries 670 User’s Guide
after
the keyboard POST indicator displays and
before
the
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
Chapter 2. Using the Eserver pSeries 670 11
12 Eserver pSeries 670 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
13
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 vice versa.
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 37), the service processor menus
can be accessed 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.
14 Eserver pSeries 670 User’s Guide
Loading...