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
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 15
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 55.
v Read Service Processor Error Logs
Displays the service processor error logs. For an example, refer to “Service
Processor Error Logs” on page 54.
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.
16 Eserver pSeries 670 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 17
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 19 for more information.
v System Power Control Menu
See “System Power Control Menu” on page 25 for more information.
v System Information Menu
See “System Information Menu” on page 30 for more information.
v Language Selection Menu
See “Language Selection Menu” on page 35 for more information.
v Call-In/Call-Out Setup Menu
See “Call-In/Call-Out Setup Menu” on page 36 for more information.
v Set System Name
Allows setting of the system name.
18 Eserver pSeries 670 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 19
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 59). 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.
20 Eserver pSeries 670 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 53.
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 21
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 50 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
22 Eserver pSeries 670 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 23
– 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.
24 Eserver pSeries 670 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 43.
Chapter 3. Using the Service Processor 25
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 36 for information on
configuring modems.
Option 2 is used to set the number of rings.
26 Eserver pSeries 670 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 Yes
3. Enable supplemental restart policy?
Currently No
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 - Allows the service processor whether 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 defined, depending on the
operating system or its version/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 YES.
Note: For partitioned systems, this policy applies to errors at the system (or
global
) level, not at the partition level.
Chapter 3. Using the Service Processor 27
– Enable supplemental restart policy - The default setting is NO. If set to YES,
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.
– 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.
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.
28 Eserver pSeries 670 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 29
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
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 55.
v Read Service Processor Error Logs
Displays error conditions detected by the service processor. Refer to “Service
Processor Error Logs” on page 54 for an example of this error log.
v Read System POST Errors
30 Eserver pSeries 670 User’s Guide
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
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 a
processor, and then reconfigure the processor at a later time. An example of this
menu follows:
PROCESSOR CONFIGURATION/DECONFIGURATION MENU
77. Enable/Disable CPU Repeat Gard: 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 table:
1. Bring-up failure
Chapter 3. Using the Service Processor 31
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. CPU repeat gard is
enabled by default.
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. Consult the AIX documentation
before configuring or deconfiguring a processor to ensure that the correct
processor is selected.
Note: The number of processors available to AIX can be determined by issuing the
following command on the AIX command line: bindprocessor -q
v Memory Configuration/Deconfiguration Menu
These menus allow the user to change the system memory configuration. If it is
necessary to take one of the memory books offline, this menu allows you to
deconfigure a book, and then reconfigure the book at a later time.
When this option is selected, a menu displays. The following is an example of this
menu:
MEMORY CONFIGURATION/DECONFIGURATION MENU
77. Enable/Disable Memory 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.
32 Eserver pSeries 670 User’s Guide
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) Configured 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 status
The error status of the each memory book is indicated by AB, where B indicates the
number of errors and A indicates the type of error according to the following table:
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.
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.
In the previous example menu, each line shows two books and indicates whether
they are configured.
To enable or disable Memory Repeat Gard, use menu option 77 of the Processor
Configuration/Deconfiguration Menu.
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.
Chapter 3. Using the Service Processor 33
The four inner memory books, if present, are listed first, if present. The memory
books are shown in the following order of physical location code:
1 U1.18-P1-M2
2 U1.18-P1-M3
3 U1.18-P1-M7
4 U1.18-P1-M6
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
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:
1. For the I/O drawer address, type 1.
2. 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 Indicator Menu
This menu displays the state of the processor subsystem disturbance/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. An example of this
menu follows:
34 Eserver pSeries 670 User’s Guide
LED Indicator
1. CEC LED at location U1.18 Currently in IDENTIFY state
2. Drawer LED at location U1.9 Currently in OFF state
3. Drawer LED at location U1.5 Currently in IDENTIFY state
4. Drawer LED at location U1.1 Currently in OFF state
98. Return to Previous Menu
Enter LED index
0>
The processor subsystem disturbance/system attention LED is 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.
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.
LANGUAGE SELECTION MENU
1. English
2. Francais
3. Deutsch
4. Italiano
5. Espanol
6. Svenska
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 35
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 running application 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 37.
v Serial Port Selection Menu, see “Serial Port Selection Menu” on page 38.
v Serial Port Speed Setup Menu, see “Serial Port Speed Setup Menu” on page 39.
v Telephone Number Setup Menu, see “Telephone Number Setup Menu” on page 40.
v Call-Out Policy Setup Menu, see “Call-Out Policy Setup Menu” on page 42.
v Customer Account Setup Menu, see “Customer Account Setup Menu” on page 43.
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.
36 Eserver pSeries 670 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 143 and “Transfer of a Modem Session” on page 149.
Chapter 3. Using the Service Processor 37
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.
38 Eserver pSeries 670 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
Chapter 3. Using the Service Processor
39
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 running on the
HMC.
Use this menu to set or change the telephone numbers for reporting a system failure.
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>
40 Eserver pSeries 670 User’s Guide
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
52).
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.
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-in
phone number.
Chapter 3. Using the Service Processor 41
Call-Out Policy Setup Menu
Note: Call-out is disabled in partitoned 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>
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.
42 Eserver pSeries 670 User’s Guide
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
Chapter 3. Using the Service Processor 43
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
25.
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.
44 Eserver pSeries 670 User’s Guide
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 45
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 running in a full system partition. Operating system
surveillance is disabled in partitioned systems.
If you are using the AIX operating system, the menu item under SMIT for setting the
restart policy is Automatically Reboot After Crash (True/False). 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.
46 Eserver pSeries 670 User’s Guide
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 yes. 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).
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.
Enable supplemental restart policy - The default setting is no. If set to yes, 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.
Refer to “Service Processor Reboot/Restart Recovery” on page 46.
Chapter 3. Using the Service Processor 47
The following table describes the relationship among the operating system and service
processor restart controls:
OS Automatic
reboot/restart
after crash setting
None No No
Service processor to
use OS-Defined
restart policy?
Service Processor
Enable supplemental
restart policy?
1
System response
None No Yes Restarts
None Yes
None Yes
2
False
2
False
2
False
2
False
1
1
No No
No Yes Restarts
1
Yes
1
Yes
True No No
1
No
Yes Restarts
1
1
No
Yes
1
True No Yes Restarts
True Yes
True Yes
1
Service processor default
2
AIX default
1
1
1
No
Restarts
Yes Restarts
48 Eserver pSeries 670 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 31. For information on
configuring or deconfiguring a memory book, see the Memory
Configuration/Deconfiguration Menu on page 32. 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, which is a submenu under the System
Information 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 49
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 in 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.
50 Eserver pSeries 670 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 46.
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 51
Call-Out (Call-Home)
Note: Call-out is disabled in 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.
52 Eserver pSeries 670 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 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 53
Service Processor Error Logs
The service processor error logs, an example of which is shown below, 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.
54 Eserver pSeries 670 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
Chapter 3. Using the Service Processor 55
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
56 Eserver pSeries 670 User’s Guide
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 by LPAR
on the operator panel. At this point, the server is capable of starting multiple logical
partitions which would be activated via through HMC graphical user interface.
The bring-up phase components are as follows:
v Retry Request Check
v Dial Out
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.
Chapter 3. Using the Service Processor 57
v Update Operator Panel
v Environmental Monitoring
v System Firmware Surveillance (Heartbeat Monitoring)
v Responding to System Processor Commands
Runtime 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.
58 Eserver pSeries 670 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.
Note: On some of the system management services (or service processor) screens,
you will see the term
system
or simply
Note: In a partitioned system, only those devices that are assigned to the partition that
is being booted display in the SMS menus. In a full system partition, all devices
in the system display in the SMS menus.
To start the system management services, do the following:
1. For a partitioned system, use the Hardware Management Console for pSeries
(HMC) to restart the partition.
For a full system partition, restart the system.
2. For a partitioned system, watch the virtual terminal window on the HMC.
For a full system partition, watch the firmware console.
3. Look for the POST indicators memory, keyboard, network, scsi, speaker, which
appear across the bottom of the screen.
Press the numeric 1 key after the word keyboard appears, and before the word
speaker appears.
For more information on the POST indicator words, refer to “Understanding the
Power-On Self-Test (POST)” on page 10.
LPAR
, which is equivalent to the term
partitioned system
.
logically partitioned
After the system management services starts, the following screen displays:
Utilities
1 Password Utilities...NOT available in LPAR mode.
2 Display Error Log
3 Remote Initial Program Load Setup
4 SCSI Utilities
5 Select Console...NOT available in LPAR mode.
6 MultiBoot
7 Select Language
8 OK Prompt
.------.
|X=Exit|
===>
`------’
Each option on the system management services utilities menu is described in this
section.
59
Password Utilities
Note: This utility is disabled in partitioned systems.
Entering this selection permits access to the options shown on the following screen:
Password Utilities
1 Set Privileged-Access Password
2 Remove Privileged-Access Password
3 Unattended Start Mode <ON>
===>
Set Privileged-Access Password: The privileged-access password protects against
the unauthorized starting of the system programs. When this option is selected, another
screen displays that allows the setting of a password.
You can set the password from either the service processor or system management
services menus. After the password is set, both the service processor and system
management services automatically use the same password. The password is limited to
eight characters.
.------.
|X=Exit|
`------’
Remove Privileged-Access Password: If you previously had set a privileged-access
password and want to remove it, select Remove Privileged-Access Password.
Unattended Start Mode <ON>: This selection is used to enable or 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, which is necessary on servers that require
automatic power-on after a power failure. The default setting is on.
60 Eserver pSeries 670 User’s Guide
Display Error Log
A screen similar to the following displays when you select this option. You can view or
clear your system error log.
.-----------------. .-----------.
|C=Clear Error Log| |X=Exit Log |
`-----------------’ `-----------’
Note: The time stamp in this error log is coordinated universal time (UTC), which is
.--------------------------------------------------------.
| Error Log |
||
||
| Date Time ErrorCode Location |
| Entry 1. 01/06/30 02:15:35 25a80011 U1.18-P1-H2/Q1 |
| Entry 2. 01/07/01 03:18:36 20300026 U1.18-p1-H2/Q1 |
`--------------------------------------------------------’
also referred to as Greenwich mean time (GMT). AIX error logs have more
information available and can time stamp with your local time.
Chapter 4. Using System Management Services 61
Remote Initial Program Load Setup
This option allows you to enable and set up the remote startup of your system or
partition. You must first specify the network parameters as shown in the following
screen:
Network Parameters
1. IP Parameters
2. Adapter Parameters
3. Ping
===>
Note: Some applications may require that IP addresses contain leading zeroes for
numbers less than 100. For example, 129.132.4.20 may need to be entered as
129.132.004.020.
.------.
|X=Exit|
`------’
62 Eserver pSeries 670 User’s Guide
IP Parameters
Select the IP Parameters option from the Network Parameters menu to display a
screen similar to the following:
IP Parameters
1. Client IP Address [9.3.146.162]
2. Server IP Address [9.3.146.171]
3. Gateway IP Address [0.0.0.0]
4. Subnet Mask [255.255.255.0]
.------.
|X=Exit|
===>
`------’
To set an address using this menu, do the following:
1. Type the number of the selection (1, 2, 3, or 4).
2. Enter the address on the next screen.
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 63
Adapter Parameters
Note: In a partitioned system, only those network adapters that have been assigned to
Select the Adapter Parameters option from the Network Parameters menu to view an
adapter’s hardware address, as well as configure network adapters that require setup. A
screen similar to the following displays when you make this selection:
Adapter Parameters
1. Gigabit Ethernet 4: U1.9-P1-I4/E1 0004ac7c0135
2. token-ring 5: U1.9-P1-I5/T1 0020357a9105
3. ethernet 8: U1.9-P1-I8/E1 0060949d7ac5
4. ethernet 2: U1.9-P2-I2/E1 0004ac5e692b
5. token-ring 3: U1.5-P1-I3/T1 0004ac634e38
(PRESS ENTER AFTER MAKING A SELECTION) ===>
Select an adapter on this screen to display configuration menus for that adapter. If
Ethernet is selected, you can set parameters that control how the Ethernet adapter
communicates with the network. For example, the following screen shows the menu for
the Ethernet adapter configuration:
the partition being booted display in the IP Parameters menu. In a full system
partition, all network adapters in the system are listed in the Adapter Parameters
menu.
Device Slot Hardware Address
.------.
|X=Exit|
`------’
1. Data Rate [Auto]
2. Full Duplex [No]
64 Eserver pSeries 670 User’s Guide
Ping
Select Ping from the Network Parameters menu to test a connection to a remote
system unit. After selecting the Ping option, you must first choose an adapter to
communicate with the remote system.
Adapter Parameters
Device Slot Hardware Address
1. Gigabit Ethernet 4: U1.9-P1-I4/E1 0004ac7c0135
2. token-ring 5: U1.9-P1-I5/T1 0020357a9105
3. ethernet 8: U1.9-P1-I8/E1 0060949d7ac5
4. ethernet 2: U1.9-P2-I2/E1 0004ac5e692b
5. token-ring 3: U1.5-P1-I3/T1 0004ac634e38
.------.
|X=Exit|
(PRESS ENTER AFTER MAKING A SELECTION) ===>
`------’
After determining which adapter to use to ping the remote system, you must provide the
addresses needed to communicate with the remote system. Select the appropriate
device from the Ping menu to display a screen similar to the following:
PING IP Address
1. Client IP Address [9.3.146.162]
2. Server IP Address [9.3.146.171]
3. Gateway IP Address [0.0.0.0]
4. Subnet Mask [0.0.0.0]
.---------. .------.
|E=Execute| |X=Exit|
`---------’ `------’
===>
Chapter 4. Using System Management Services 65
SCSI Utilities
SCSI Utilities allow you to set delay times for the SCSI hard disk spin-up and to set
SCSI IDs for SCSI controllers installed in the system.
SCSI Utilities
1. Harddrive Spin Up Delay
2. Change SCSI Id
.--------.
| X=Exit |
===>
`--------’
Using the Harddrive Spin Up Delay option allows you to change the spin up delay
time for SCSI hard disk drives attached to your system. Spin up delay values can be
entered manually, or you can use a default setting (two seconds). All values are
measured in seconds.
Attention: Setting the value lower than the default can prevent successful booting
because the system power handling capabilities might be exceeded. If the system no
longer boots after setting this value, access this utility again and increase the value. It is
also possible that adding disk drives can cause similar symptoms. Changing this value
changes the surge current requirements on the system. As you increase the value, the
surge current requirements on the system are decreased.
Select Console
Note: This option is not available in partitioned systems. A virtual terminal window on
the HMC is the default firmware console for a partitioned system. The following
screen displays only if the system is running in a full system partition.
Select this option to define which display is used by the system for system
management. If no console is selected, the console defaults to serial port 1 on the
primary I/O book.
Press 0 to select this console
66 Eserver pSeries 670 User’s Guide
as the active console
Multiboot
Multiboot allows you to select a method for booting the system.
Select Software
If this option is supported by the operating system, the names of the operating system
installed are shown. This option might not be supported by all operating systems.
If you are running AIX, and you receive the following message:
No Operating System Installed
this indicates that information in nonvolatile storage could have been lost, as would
happen if the battery had been removed. To re-create this value, run the bootlist
command under AIX with the appropriate parameters. See the bootlist command in
your AIX documentation.
Multiboot
1 Select Software
2 Software Default
3 Select Install Device
4 Select Boot Devices
5 OK Prompt
6 Multiboot Startup <OFF>
===>
.------.
|X=Exit|
`------’
The AIX Documentation library is available at the following Web address:
http//www.ibm.com/servers/aix/library/. Select Technical Publications. AIX
documentation is also contained on the AIX Documentation CD. This documentation is
made accessible by loading the documentation CD onto the hard disk or by mounting
the CD in the CD-ROM drive.
Chapter 4. Using System Management Services 67
Software Default
If this option is supported by the operating system, you can select the default operating
system to start the system.
Select Install Device
Attention: In a partitioned system, only those devices from which an operating
system can be installed that are assigned to the partition being booted display on the
Select Install Device menu. In a full system partition, all devices from which an
operating system can be installed display on the Select Install Device menu.
Select this option to produce a list of devices, such as the CD-ROM, from which the
operating system may be installed. Select a device, and the system searches that
device for an operating system to install. If the device supported by the operating
system is that device, the name of the operating system displays.
Select Boot Devices
Attention: In a partitioned system, only those devices from which an operating
system can be booted that are assigned to the partition being booted display on the
select boot devices menu. In a full system partition, devices from which an operating
system can be booted display on the select boot devices menu.
Select this option to view and change the customized boot list, which is the sequence of
devices that the system searches when booting an operating system. The boot device
list can contain up to five devices. The following is an example of this screen.
Select Boot Devices
1 Display Current Settings
2 Restore Default Settings
3 Configure 1st Boot Device
4 Configure 2nd Boot Device
5 Configure 3rd Boot Device
6 Configure 4th Boot Device
7 Configure 5th Boot Device
====>
68 Eserver pSeries 670 User’s Guide
.------.
|X=Exit|
`------’
Display Current Settings
Lists the current order of devices in the boot list. The following is an example of this
screen.
Current Boot Sequence
1. Diskette
2. SCSI CD-ROM id=1 ( loc=U1.9-P1-I1/Z1-A1 )
3. SCSI 9100 MB Harddisk id=5 ( loc=U1.9-P1-I1/Z1-A5 )
4. Ethernet ( loc=U1.9-P1-I2/E1 )
5. None
.------.
|X=Exit|
`------’
===>
Chapter 4. Using System Management Services 69
Restore Default Settings
Restores the boot device list to the following default sequence:
v Primary diskette drive
v CD-ROM drive
v Tape (if installed)
v Hard disk drive
v Network device
Selecting any of the Configure Boot Device options displays a screen similar to the
following.
Configure Nth Boot Device
Device Current Device
Number Position Name
1 1 Diskette
2 4 Ethernet ( loc=U1.9-P1-I4/E1 )
3 - Token-Ring ( loc=U1.9-P2-I4/T1 )
4 2 SCSI CD-ROM id=1 ( loc=U1.9-P1-I1/Z1-A1 )
5 3 SCSI 18200 MB Harddisk id=5 ( loc=U1.9-P1/Z1-A5 )
===>
70 Eserver pSeries 670 User’s Guide
.------.
|X=Exit|
`------’
Multiboot Startup <OFF>
Toggles between off and on to select whether Multiboot menu starts automatically on
startup.
Select Language
Select this option to change the language used by the system management services
screens and the service processor menus.
Select Language
1. English
2. Francais
3. Deutsch
4. Italiano
5. Espanol
6. Svenska
===> .------.
Note: To correctly display languages other than English, your system or your virtual
terminal window must support the ISO-8859 character set.
OK Prompt
This option is for service personnel only to obtain additional debug information. It
provides access to the open firmware command prompt. If it is necessary to exit from
the open firmware command prompt, type:
reset-all
Exiting System Management Services
After you have finished using the system management services, type x (for exit) at the
Utilities screen to boot your system or partition. On all other screens, typing x returns
you to the previous screen.
|X=Exit|
`------’
Chapter 4. Using System Management Services 71
72 Eserver pSeries 670 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, they 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 78.
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.
73
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. These difficulties can be bypassed 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.
74 Eserver pSeries 670 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 (refer to Full System
Management Tasks in the
, order number SA38-0603, for more information on full system partitions).
Guide
10. Make sure that there are no media in the devices in the media subsystem.
11. Enter any passwords, if requested.
Hardware Management Console for pSeries Operations
Chapter 5. Using the Online and Standalone Diagnostics 75
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 118.
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.
76 Eserver pSeries 670 User’s Guide
4. When testing is complete, use the F3 key to return to the DIAGNOSTIC
OPERATING INSTRUCTIONS. Press the F3 key again to return to the AIX
operating system prompt. Be sure to vary on any resource that you had varied to
off.
5. Press the Ctrl-D key sequence to log off from root user or CE Login.
Maintenance Mode
Maintenance mode runs the online diagnostics using the customer’s version of the AIX
operating system. This mode requires that all activity on the partition running the AIX
operating system be stopped so that the online diagnostics have most of the resources
available to check. All of the system resources, except the SCSI adapters, memory,
processor, and the disk drive used for paging, can be checked.
Error log analysis is done in maintenance mode when you select the Problem
Determination option on the DIAGNOSTIC MODE SELECTION menu.
Use the shutdown -m command to stop all activity on the AIX operating system and
put the AIX operating system into maintenance mode. The diag command is then used
to invoke the diagnostic controller so you can run the diagnostics. After the diagnostic
controller is loaded, follow the normal diagnostic instructions.
The AIX Documentation library is available at the following Web address:
http//www.ibm.com/servers/aix/library/. Select Technical Publications. AIX
documentation is also contained on the AIX Documentation CD. This documentation is
made accessible by loading the documentation CD onto the hard disk or by mounting
the CD in the CD-ROM drive.
Running the Online Diagnostics in Maintenance Mode
To run the online diagnostics in maintenance mode, do the following:
1. Stop all programs running on the partition except the AIX operating system (if help
is needed, see the system operator).
2. Log in to the AIX operating system as root user or use CE Login.
3. Type the shutdown -m command.
4. When a message indicates the system is in maintenance mode, enter the diag
command.
TERM
Note: It might be necessary to set
5. When DIAGNOSTIC OPERATING INSTRUCTIONS screen displays, follow the
displayed instructions to check out the desired resources.
6. When testing is complete, use the F3 key to return to DIAGNOSTIC OPERATING
INSTRUCTIONS. Press the F3 key again to return to the AIX operating system
prompt.
7. Press Ctrl-D to log off from root user or CE Login.
Chapter 5. Using the Online and Standalone Diagnostics 77
type again.
Standalone Diagnostic Operation
Use standalone diagnostics to test the system when the online diagnostics are not
installed and as a method of testing the disk drives that cannot be tested by the online
diagnostics.
Note: No error log analysis is done by the standalone diagnostics. The CD-ROM drive
and the SCSI controller that controls it cannot be tested by the standalone
diagnostics. Standalone diagnostics:
v Are resident on CD-ROM or a Network Installation Management (NIM) server
v Provide a method to test the system when the online diagnostics are not
installed or cannot be loaded from the disk drive
v Allow testing of the disk drives and other resources that cannot be tested by
the online diagnostics
v Do not have access to the AIX configuration data
v Do not have access to the AIX error log
v Do not allow for running of error log analysis
Performing Slow Boot
To fully analyze all of the available information, perform the following steps before doing
a hardware repair or replacement:
1. Record the 8-character error code (and location code if present) in the operator
panel or that was reported by the customer.
2. Do a slow-mode boot in service mode. This boot can be specified using the System
Power Control Menu on the service processor main menu. (A fast-mode boot skips
much of the built-in diagnostic testing.) A slow-mode boot may yield a new
8-character error code on the operator panel and new errors in the service
processor error log. If a new error code is reported, use this code to continue
problem analysis.
Partitioned System Considerations for Standalone Diagnostics
To run standalone diagnostics on a full system partition, you must reboot the entire
system. However, for a partition in a partitioned system, you can boot standalone
diagnostics either in a given partition or on the entire system (which is the same
procedure as a full system partition). For a partitioned system, before running
standalone diagnostics on a given partition, the user must move the device from the
existing location where standalone diagnostics is booted (the CD-ROM drive or the
network adapter connected to the NIM server, in the case of NIM boot of standalone
diagnostics), to the partition that will run standalone diagnostics. Devices on a
partitioned system are moved on an I/O-slot basis.
If the CD-ROM drive is moved from one partition to another, all SCSI devices on the
same SCSI adapter card which the CD-ROM drive is attached must be moved to the
same partition. It is recommended that you attach few SCSI devices to the same SCSI
controller card to prevent moving them, along with the CD-ROM drive, between
78 Eserver pSeries 670 User’s Guide
partitions. A reboot is required on the partition containing this device and on the moved
device, but the system itself is
in a logical partitioned system partition.
not
powered off in order to boot standalone diagnostics
Considerations for Running Standalone Diagnostics from CD-ROM
Consider the following when you run standalone diagnostics:
v The diagnostic CD must remain in the CD-ROM drive for the entire time that
diagnostics are running.
v The diagnostic CD cannot be ejected from the CD-ROM drive after the diagnostics
have loaded. The CD can only be ejected after the system has been turned off and
then turned on (standalone mode) or after the diagnostics program has terminated
(online concurrent mode).
v The CD-ROM drive from which diagnostics were loaded cannot be tested.
v The SCSI adapter (or circuitry) controlling the CD-ROM drive from which diagnostics
were loaded cannot be tested.
Loading the Standalone Diagnostics from CD-ROM
To run standalone diagnostics in service mode from CD-ROM, do the following:
1. Stop all programs including the AIX operating system (get help if needed).
2. Remove all tapes, diskettes, and CD-ROMs.
3. Power off the Eserver pSeries 670 (refer to Full System Management Tasks in the
Hardware Management Console for pSeries Operations Guide
SA38-0603, for more information on full system partitions).
4. Right-click the mouse and select Open Terminal Window.
5. From the service processor menu on the VTERM, select option 2, System Power
Control Menu.
6. Select option 6. Verify that the state changes to currently disabled. Disabling fast
system boot automatically enables slow boot.
7. Select option 98 to exit the system power control menu.
8. Use the HMC to power on the managed server in a full system partition. Select
thePower on Diagnostic Default Boot List (refer to Full System Management
Tasks in the
number SA38-0603, for more information on full system partitions).
9. Insert the CD-ROM into the CD-ROM drive in the media subsystem in the Eserver
pSeries 670 (not into the HMC’s CD-ROM drive).
Hardware Management Console for pSeries Operations Guide
, order number
, order
Running Standalone Diagnostics from a Network Installation Management (NIM) Server
A client system connected to a network with a Network Installation Management (NIM)
server can boot standalone diagnostics from the NIM server if the client-specific settings
on both the NIM server and client are correct.
Notes:
1. All operations to configure the NIM server require root user authority.
Chapter 5. Using the Online and Standalone Diagnostics 79
2. If you replace the network adapter in the client, the network adapter hardware
address settings for the client must be updated on the NIM server.
3. The Cstate for each standalone diagnostics client on the NIM server should be kept
in the
diagnostic boot has been enabled
4. On the client system, the NIM server network adapter should be put in the bootlist
after the boot hardfile. This allows the system to boot in standalone diagnostics from
the NIM server if there is a problem booting from the hard file. Refer to the
Multiboot section under “SMS” in the client system’s service guide for information
on setting the bootlist.
NIM Server Configuration
Refer to the “Advanced NIM Configuration Tasks” chapter of the
Management Guide and Reference
the following:
v Registering a client on the NIM server
v Enabling a client to run diagnostics from the NIM server
To verify that the client system is registered on the NIM server and the diagnostic boot
is enabled, run the command lsnim -a Cstate -Z
on the NIM server. Refer to the following table for system responses.
state.
Network Installation
, order number SC23-4385, for information on doing
ClientName
from the command line
Note: The
ClientName
is the name of the system on which you want to run standalone
diagnostics.
System Response Client Status
#name:Cstate:
ClientName:diagnostic boot has been
enabled:
#name:Cstate:
ClientName:ready for a NIM operation:
or
#name:Cstate:
ClientName:BOS installation has been
enabled:
0042-053 lsnim: there is no NIM object
named "ClientName"
The client system is registered on the NIM
server and enabled to run diagnostics from the
NIM server.
The client is registered on the NIM server but
not enabled to run diagnostics from the NIM
server.
Note: If the client system is registered on the
NIM server but Cstate has not been set, no
data will be returned.
The client is not registered on the NIM server.
80 Eserver pSeries 670 User’s Guide
Client Configuration and Booting Standalone Diagnostics from the NIM Server
To run standalone diagnostics on a client from the NIM server, do the following:
1. Remove any removable media (tape or CD-ROM disc).
2. Stop all programs including the AIX operating system (get help if needed).
3. If you are running standalone diagnostics in a full system partition, verify with the
system administrator and system users that the system unit can shut down. Stop
all programs, including the AIX operating system. Refer to the AIX operating
system documentation for shutdown command information.
In a partitioned system, make the CD-ROM drive available to the partition used to
run standalone diagnostics (refer to the
pSeries Operations Guide
administrator and system users using that partition that all applications on that
partition must be stopped, and that the partition will be rebooted. Stop all programs
on that partition, including the operating system.
4. If you are in a full system partition, power on the system unit to run standalone
diagnostics. In a partitioned system, reboot the partition to run standalone
diagnostics.
5. When the keyboard indicator is displayed (the word keyboard on a HMC virtual
terminal window or the keyboard icon on a graphical display), press the number 1
key on the keyboard to display the SMS menu.
6. Enter any requested passwords.
7. Select Utilities.
8. Depending on the console type, select RIPL or Remote Initial Program Load
Setup.
9. Enter the client address, server address, gateway address (if applicable), and
subnet mask. If you are using a graphical interface Click Save. Exit to the SMS
Utilities screen.
10. If the NIM server is set up to allow pinging from the client system, use the ping
utility in the RIPL utility to verify that the client system can ping the NIM server.
Under the ping utility, choose the network adapter that provides the attachment to
the NIM server to do the ping operation. If the ping returns with an OK prompt, the
client is prepared to boot from the NIM server. If ping returns with a FAILED prompt,
the client cannot proceed with the NIM boot.
for more information). Verify with the system
Hardware Management Console for
Note: If the ping fails, refer to the
Eserver
problems.
To temporarily change the system bootlist so that the network adapter attached to the
NIM server network is first in the bootlist, do the following:
1. Exit to the SMS Main screen.
2. Depending on the console type, select Multiboot or Select Boot Devices.
3. Depending on the console type, select Boot Sequence or Select Boot Devices.
4. Record the current bootlist settings. (You must set the bootlist back to the original
settings after running diagnostics from the NIM server.)
pSeries 670 Service Guide
Chapter 5. Using the Online and Standalone Diagnostics 81
Boot Problems and Concerns
and follow the steps for network boot
section of the
5. Change the bootlist so the network adapter attached to the NIM server is first in the
bootlist.
6. Exit completely from SMS.
The system starts loading packets while doing a bootp from the network.
Follow the instructions on the screen to select the system console.
If Diagnostics Operating Instructions Version x.x.x is displayed, standalone
diagnostics have loaded successfully.
If the AIX login prompt is displayed, standalone diagnostics did not load. Check the
following items:
v The bootlist on the client may be incorrect.
v Cstate on the NIM server may be incorrect.
v There may be network problems preventing you from connecting to the NIM server.
Verify the settings and the status of the network. If you continue to have problems, refer
to the
Boot Problems and Concerns
and follow the steps for network boot problems.
After running diagnostics, reboot the system and use SMS to change the bootlist
sequence back to the original settings.
section of the Eserver
pSeries 670 Service Guide
82 Eserver pSeries 670 User’s Guide
Chapter 6. Introducing Tasks and Service Aids
The AIX diagnostic package contains programs that are called
thought of as performing a specific function on a resource; for example running
diagnostics, or performing a service aid on a resource.
Note: Many of these programs work on all system model architectures. Some
programs are only accessible from online diagnostics in service or concurrent
mode, while others might be accessible only from standalone diagnostics. Still
other programs may only be supported on a particular system architecture, such
as CHRP (Common Hardware Reference Platform).
Note: In a logical partitioned system, the following tasks may only be executed in a
partition with service authority:
v Configure Reboot Policy
v Configure Remote Maintenance Policy
v Configure Ring Indicate Power On
v Configure Ring Indicate Power-On Policy
v Configure Surveillance Policy
v Update System or Service Processor Flash
v Save or Restore Hardware Management Policies
For more information, refer to the
Operations Guide
To perform one of these tasks, use the Task Selection option from the FUNCTION
SELECTION menu.
.
Hardware Management Console for pSeries
tasks
. Tasks can be
After a task is selected, a resource menu may be presented showing all resources
supported by the task.
A fast path method is also available to perform a task by using the diag command and
the -T flag. By using the fast path, the user can bypass most of the introductory menus
to access a particular task. The user is presented with a list of resources available to
support the specified task. The fast path tasks are as follows:
v Certify – Certifies media
v Chkspares – Checks for the availability of spare sectors
v Download – Downloads microcode to an adapter or device
v Disp_mcode – Displays current level of microcode
v Format – Formats media
v Identify – Identifies the PCI RAID physical disks
v IdentifyRemove – Identifies and removes devices (Hot Plug)
83
Tasks
To run these tasks directly from the command line, specify the resource and other
task-unique flags. Use the descriptions in this chapter to understand which flags are
needed for a given task.
The following tasks are described in this chapter:
v Add Resource to Resource List
v AIX Shell Prompt
v Analyze Adapter Internal Log
v Backup and Restore Media
v Certify Media
v Change Hardware Vital Product Data
v Configure Dials and LPF Keys
v Configure Reboot Policy
v Configure Remote Maintenance Policy
v Configure Ring Indicate Power On Policy
v Configure Surveillance Policy
v Create Customized Configuration Diskette
v Delete Resource from Resource List
v Disk Maintenance
v Display Configuration and Resource List
v Display Firmware Device Node Information
v Display Hardware Error Report
v Display Hardware Vital Product Data
v Display Machine Check Error Log
v Display Microcode Level
v Display or Change Bootlist
v Display or Change Diagnostic Run-Time Options
v Display Previous Diagnostic Results
v Display Resource Attributes
v Display Service Hints
v Display Software Product Data
v Display System Environmental Sensors
v Display Test Patterns
v Download Microcode
v Fibre Channel RAID Service Aids
v Flash SK-NET FDDI Firmware
v Format Media
v Generic Microcode Download
v Hot Plug Task
84 Eserver pSeries 670 User’s Guide
Loading...