Page 1 ERserver pSeries 650 Service Guide SA38-0612-02...
Page 3 ERserver pSeries 650 Service Guide SA38-0612-02...
Page 4 A reader’s comment form is provided at the back of this publication. If the form has been removed, address comments to Information Development, Department H6DS-905-6C006, 11501 Burnet Road, Austin, Texas 78758-3493. To send comments electronically, use this commercial internet address: aix6kpub@austin.ibm.com. Any information that you supply may be used without incurring any obligation to you.
Page 5: Table Of Contents
RIO Cabling ....... . . 14 IBM Hardware Management Console for pSeries (HMC) to the HMC Connector ..18 pSeries 650 Data Flow .
Page 6 pSeries 650 Physical Specifications and Loads ....60 Service Inspection Guide ......62 Chapter 2.
Page 7 MAP 154A: I2C Bus Problem Isolation ..... . . 177 MAP 154B: Insufficient Hardware Resources Problem Isolation ....181 MAP 154C: SPCN Cable Problem Isolation .
Page 8 Running Standalone Diagnostics from a Network Installation Management (NIM) Server with an HMC Attached to the System ......473 NIM Server Configuration .
Page 9 Standby Phase ....... . 523 Bring-Up Phase ....... 523 Runtime Phase .
Page 10 Processor Subsystem Procedures ......614 Processor Card ....... . 614 Processor Bus Connector .
Page 11 Customizing the Modem Configuration Files ..... 700 IBM 7852-400 DIP Switch Settings ......700 Xon/Xoff Modems .
Page 12 EserverpSeries 650 Service Guide...
Page 13: Safety Notices
Safety Notices A danger notice indicates the presence of a hazard that has the potential of causing death or serious personal injury. Danger notices appear on the following pages: v xi v 118 v 543 A caution notice indicates the presence of a hazard that has the potential of causing moderate or minor personal injury.
Page 14 CAUTION: This unit has more than one power supply cord. Follow procedures for removal of power from the system when directed. CAUTION: Energy hazard, remove power before servicing. CAUTION: Energy hazard, remove all jewelry before servicing. EserverpSeries 650 Service Guide...
Page 15: Laser Safety 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.
Page 16 EserverpSeries 650 Service Guide...
Page 17: Data Integrity And Verification
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.
Page 18 EserverpSeries 650 Service Guide...
Page 19: About This Book
If you are using another operating system, consult the appropriate documentation for that operating system regarding support for those features and functions. Accessing Information Documentation for the IBM Eserver pSeries is available online. Visit the IBM Eserver pSeries Information Center at http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base. v To access the pSeries publications, click Hardware documentation.
Page 20: Related Publications
The System Unit Safety Information, order number SA23-2652, contains translations of safety information used throughout this book. v The IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590, contains information on how to set up and cable the hardware system console and verify system operation.
Page 21: Chapter 1. Reference Information
Chapter 1. Reference Information This chapter provides an overview of the Eserver pSeries 650, including a logical description and a physical overview of the system. Additional details pertaining to the 7311 Model D10 I/O Subsystem and 7311 Model D20 I/O Subsystem are also provided. They include the following: v Memory overview and ordering rules v General description of the operator panel v Cabling rules...
Page 22: Internal Disk Drives
The HMC is not required if the system resources are not to be divided among multiple logical partitions. When booted in the traditional ″full system partition″, the system console may be a serially attached TTY terminal or a display attached to the system. Even if the HMC is attached, you may choose to boot a ″full system partition″.
Page 23 The following illustration shows the SCSI bus path for the split disk drive backplane. Disk Drives Disk Drives Media System Backplane External cables that connect the SCSI cables Internal SCSI cables that connect from the SCSI to the bulkhead cable passthrough cassette in repeater card to the split disk drive backplane.
Page 24: Service Processor/Pci Backplane Connectors
Service Processor/PCI Backplane Connectors Top View Flex Cable Connector CEC Backplane Power Connector J1070 Rack Indicator port J112 RJ-45 Operator Panel Connector Fault LED Connector J570 Not used Slot 7 Battery J1071 Slot 6 J1074 J117 Slot 5 J1075 Slot 4 J630 J670 Power Connectors...
Page 25: Capacity Upgrade On Demand
Capacity Upgrade on Demand Capacity Upgrade on Demand, CUoD, of processors and memory is supported on the Eserver pSeries 650 system. These resources can be added during runtime without the need to reboot the system. pSeries 650 System Locations The pSeries 650 consists of one base processor subsystem in a rack. Up to eight additional I/O subsystems may be added in the same rack.
Page 26: 7038 Model 6M2 Processor Subsystem Locations
7038 Model 6M2 Processor Subsystem Locations This section provides a front view and a rear view of the processor subsystem with descriptions and locations for each part of the processor subsystem. 7038 Model 6M2 Processor Subsystem Front View Fan 3 Operator Panel Fan 4 Media Bay 1...
Page 27 The left and right power supplies are hot-pluggable and may be changed one at a time while the system is operational. Each power supply provides 5V dc, 3.3V dc, -12V dc, and 5V dc standby. The following table describes power-related LED indicators that are available on a processor subsystem with an I/O subsystem attached.
Page 28: I/O Subsystem Locations
I/O Subsystem Locations Either the 7311 Model D10 I/O Subsystem or the 7311 Model D20 I/O Subsystem can be used to extend the capabilities of the 7038 Model 6M2. This section shows the locations for I/O subsystems. A front view, a rear view, descriptions, and locations for each part of the subsystem is shown.
Page 29 The green and amber LEDs (viewed on the rear of the PCI adapter cassette when installed) are used to indicate the state of the PCI slot during removal and replacement of an adapter. The following table describes the LED states and their definitions. Green PCI Slot LED Amber PCI Slot LED PCI Slot Power/Status...
Page 30 I/O Subsystem Power 7311 Model D10 I/O Subsystems have two redundant power supplies. One of these power supplies is capable of providing the necessary voltages and currents independent of the other power supply. The left and right power supply output voltages are connected and monitored by the I/O backplane contained in the I/O subsystem.
Page 31: Subsystem Positioning And Cabling
Subsystem Positioning and Cabling I/O subsystems can be installed in a standard 19-inch EIA rack in any location. The cables that connect the subsystems allow some flexibility in drawer placement, but the I/O subsystems should be located above the processor subsystem to which they are connected in the same rack. Up to eight I/O subsystems can be connected to a processor subsystem.
Page 32 Processor Subsystem Connected to One or Two Model D20 I/O Subsystems: 1 Processor Subsystem 2 I/O Subsystem EserverpSeries 650 Service Guide...
Page 33 Four I/O Subsystems, Eight I/O Subsystems The illustration on the left shows four I/O subsystems connected to the processor subsystem using one SPCN loop. The illustration on the right shows eight I/O subsystems connected to the processor subsystem using one SPCN loop. Processor Subsystem Connected to Four or Eight Model D10 I/O Subsystems: 1 Processor Subsystem 2 I/O Subsystem...
Page 34: Rio Cabling
RIO Cabling I/O subsystems are connected to the processor subsystem through remote I/O (RIO) cable loops. The cable loops are connected to ports that are on the rear of the processor subsystem. The RIO cables are connected in loops so that the system has two paths to each I/O subsystem when more than one I/O drawer is in a loop.
Page 35 One I/O Subsystem or Two I/O Subsystems The illustration on the left shows one I/O subsystem drawer connected to the processor subsystem. The illustration on the right shows two I/O subsystem drawers connected to the system unit using one RIO loop.
Page 36 Processor Subsystem Connected to Three or Four Model D10 I/O Subsystems: 1 Processor Subsystem 2 I/O Subsystem Processor Subsystem Connected to Three or Four Model D20 I/O Subsystems: 1 Processor Subsystem 2 I/O Subsystem Eight I/O Subsystems with Two RIO Loops The following illustrations show eight I/O subsystem drawers connected to the processor subsystem unit using two RIO loops.
Page 37 Processor Subsystem Connected to Eight Model D10 I/O Subsystems: 1 Processor Subsystem 2 I/O Subsystem Processor Subsystem Connected to Eight Model D20 I/O Subsystems: 1 Processor Subsystem 2 I/O Subsystem Chapter 1. Reference Information...
Page 38: Ibm Hardware Management Console For Pseries (Hmc) To The Hmc Connector
IBM Hardware Management Console for pSeries (HMC) to the HMC Connector To connect your HMC to the pSeries 650, connect a serial cable into a serial port on the HMC. The port can be either a serial port on the back of the HMC or a serial port on an 8-port or 128-port async adapter.
Page 39: Pseries 650 Data Flow
pSeries 650 Data Flow The following figure shows the data flow for the system. DIMM DIMM DIMM DIMM DIMM DIMM DIMM DIMM DIMM DIMM DIMM DIMM DIMM DIMM DIMM DIMM Memory Memory Memory Memory Controller Controller Controller Controller 32 MB 32 MB 32 MB 32 MB...
Page 40: System Memory
System Memory The main memory for the pSeries 650 consists of memory DIMMs plugged into the processor cards. Each processor card has eight DDR memory DIMM slots for system memory. The memory DIMMs must be installed in quads. DIMM quads are available in 2 GB (4x512 MB), 4GB (4x1 GB), and 8 GB (4x2 GB) sizes.
Page 41 Two Processor Cards Three Processor Cards Four Processor Cards Total Processor Memory Card 6 GB 8 GB 10 GB 12 GB 16 GB 18 GB 20 GB Chapter 1. Reference Information...
Page 42 Two Processor Cards Three Processor Cards Four Processor Cards Total Processor Memory Card 24 GB 30 GB 32 GB 36 GB 40 GB 48 GB 64 GB EserverpSeries 650 Service Guide...
Page 43: Hardware Management Console (Hmc)
Hardware Management Console (HMC) The Hardware Management Console (HMC) provides the tools that are needed to manage the configuration and operation of partitions in a system, as well as add and remove hardware without interrupting system operation. In this book, a system that is managed by the HMC is referred to as the managed system. The HMC uses its serial connection to the managed system to perform various functions.
Page 44: Partition Requirements
In a full system partition, the operating system uses all of the installed memory; the system does not set aside contiguous memory for its own use. For more information about how to allocate memory to partitions, refer to the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590.
Page 45 Available System Memory Firmware Overhead usage 18 GB to 32 GB 1 to 1.25 GB 34 GB to 48 GB 1.25 to 1.75 GB 50 GB to 64 GB 1.5 to 2 GB Before calculating the memory that is available for partitions, the appropriate memory overhead must be subtracted from the system memory.
Page 46: Powering The System On And Off
2. Memory sizes for systems running partitions with AIX 5.1, if the firmware and HMC release levels are at the 10/2002 release level (or later). Do not select the HMC partition profile option for Small Real Mode Address Region for AIX 5.1 partitions. These numbers reflect the maximum when running only AIX 5.1 partitions, but AIX 5.1 and AIX 5.2 partitions can be mixed, and can allow for additional partitions to be run (up to the maximum of eight).
Page 47: Key
5 Key The numeric 5 key, when pressed during POST, initiates a partition boot in service mode using the default service mode, boot list. This mode attempts to boot from the first device of each type found in the list. It does not search for other bootable devices of that type if the first device is not bootable.
Page 48: Logical And Physical Locations
Logical and Physical Locations The pSeries 650 system uses physical location codes in conjunction with AIX location codes to provide mapping of the failing field replaceable units (FRUs). The location codes are produced by the system’s firmware and the AIX operating system. When the operating system is Linux, there are no Linux location codes, but physical location codes may appear in the Linux error logs.
Page 49: Multiple Fru Callout Instructions
Multiple FRU Callout Instructions If an eight-digit error code appears in the operator panel display or in Chapter 5, “Error Code to FRU Index,” on page 241, a location code for a failing part may also be specified. If the location code includes a blank space followed by a lowercase x followed by a number, this is an error code with multiple FRU callouts.
Page 50: Aix Location Codes
″Service Focal Point″ chapter of the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590, for instructions on activating and deactivating a FRU identify LED. AIX Location Codes Attention: When the operating system is Linux, there are no Linux location codes, but physical location codes may appear in the Linux error logs.
Page 51: Scsi Devices
SCSI Devices For SCSI devices, the location code is defined as follows: AB-CD-EF-G,H | | | | | | | | | Logical Unit address of the SCSI Device | | | Control Unit Address of the SCSI Device | | Connector ID | devfunc Number, Adapter Number or Physical Location Bus Type or PCI Parent Bus Where:...
Page 52: Aix And Physical Location Code Reference Tables
AIX and Physical Location Code Reference Tables Attention: When the operating system is Linux, there are no Linux location codes, but physical location codes may appear in the Linux error logs. The following illustrations show the location codes that are used to identify the major functional units in the pSeries 650.
Page 53 Processor Subsystem Rear PCI adapter slot 1, RIO connector card 1 Location: U0.1-P2/I1 Location: U0.1-P1-H1 RIO connector extender card 1 Location: U0.1-P1-H1.1 PCI Adapter Slot 7, RIO connector card 2 Location: U0.1-P2/I7 Location: U0.1-P1-H2 RIO connector extender card 2 Location: U0.1-P1-H2.1 Mouse Port (upper), Power Supply 2, Location: U0.1-V2 Location: U0.1-P2/O1...
Page 54 Processor Subsystem I/O Ports UPS I2C Port, (HMC) HSC Port 1, Location: U0.1-P2/Q9 Location: U0.1-P2/S5 EPO Op PNL I2C Port, (HMC) HSC Port 2, Location: U0.1-P2/Q10 Location: U0.1-P2/S6 Reserved Serial Port 3, Location: U0.1-P2/S3 Mouse Port, Serial Port 4, Location: U0.1-P2/O1 Location: U0.1-P2/S4 Serial Port 2 Keyboard Port,...
Page 55 Processor Subsystem From the Top RIO connector card Processor/Memory Card Location: U0.1-P1-H1 Location: U0.1-P1-C2 RIO connector extender card Location: U0.1-P1-H1.1 RIO connector card Processor/Memory Card Location: U0.1-P1-H2 Location: U0.1-P1-C3 RIO connector extender card Location: U0.1-P1-H2.1 PCI Adapter Slot 1-7, Location: U0.1-P2/1-7 Processor/Memory Card Location: U0.1-P1-C4 Processor/Memory Card...
Page 56 7311 Model D10 I/O Subsystem Rear Locations 1 PCI adapter slot 1 7 RIO bus adapter card U0.dd-P1-I1 U0.dd-P1.1 2 PCI-X adapter slot 2 8 SPCN connector card U0.dd-P1-I2 U0.dd-P1 (part of the I/O backplane FRU) 3 PCI-X adapter slot 3 9 SPCN Connector 2/J16 U0.dd-P1-I3 U0.dd-P1/Q5...
Page 57 Model D20 Front View 1 Serial Number 3 Model D20 Front Bezel 2 Operator Panel 4 Disk Drives (maximum quantity 12 ) Model D20 Rear View 1 PCI-X Expansion Slot 1 9 Primary Power Supply 2 PCI-X Expansion Slot 2 10 Model D20 I/O Drawer 3 PCI-X Expansion Slot 3 11 Connector J11 (Not Used)
Page 58 Model D20 Power Supply Locations 1 Power Supplies 4 Green AC Power LED 2 Amber Fault/Identify LED 5 Power Supply Filler 3 Green DC Good LED 6 Model D20 I/O Drawer EserverpSeries 650 Service Guide...
Page 59 Model D20 Blower Locations The following illustration identifies the I/O subsystem cooling blowers. Each blower has a green power LED and an amber identify LED located on the front blower housing. The green LED indicates that a blower has power and is operating correctly. The amber LED is in the identify state when blinking. 1 Green LED 4 Blower Connector 2 Amber LED...
Page 60 Model D20 I/O Backplane Locations The following illustration of the I/O backplane identifies the primary connectors used in your subsystem. Note: Before replacing the I/O backplane, note the position of pin 1 on the VPD module. 1 PCI-X Adapter Connector 1 11 Disk Drive Power Connector 2 PCI-X Adapter Connector 2 12 Cooling Blower Connector...
Page 61 Model D20 SCSI IDs and Bay Locations Index Bay Location Drive Name SCSI Bus ID 8 DB1 Hot-Plug Disk Drive 8 - DB1 9 DB1 Hot-Plug Disk Drive 9 - DB1 A DB1 Hot-Plug Disk Drive A - DB1 B DB1 Hot-Plug Disk Drive B - DB1 C DB1...
Page 62 FRU identify LED to be flashed. See the ″Hardware Service Functions″ section of the ″Service Focal Point″ chapter of the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590, for instructions on activating and deactivating a FRU identify LED.
Page 63 Attention: When the operating system is Linux, there are no Linux location codes, but physical location codes might appear in the Linux error logs. Location Physical Logical FRU Name Code Location Connection Connection Code Rack Frame (MT/M Serial#) U0 Location Physical Logical FRU Name...
Page 64 Location Physical Logical FRU Name Code Location Connection Connection Code Memory DIMM 2 - U0.1-P1-C2-M2 Processor card 2 Memory DIMM 3 - U0.1-P1-C2-M3 Processor card 2 Memory DIMM 4 - U0.1-P1-C2-M4 Processor card 2 Memory DIMM 5 - U0.1-P1-C2-M5 Processor card 2 Memory DIMM 6 - U0.1-P1-C2-M6 Processor card 2...
Page 65 Location Physical Logical FRU Name Code Location Connection Connection Code RIO connector card 1 U0.1-P1-H1 RIO connector card 1, U0.1-P1-H1/Q1 upper connector RIO connector card 1, U0.1-P1-H1/Q1# upper cable RIO connector card 1, U0.1-P1-H1/Q2 lower connector RIO connector card 1, U0.1-P1-H1/Q2# lower cable RIO connector extender...
Page 66 Location Physical Logical FRU Name Code Location Connection Connection Code Diskette Drive U0.1-P2-D1 01-D1-00-00 Integrated Ethernet U0.1-P2/E1 1c-08 Controller Ent PHB0 on service U0.1-P2 processor/PCI backplane EADS controller under U0.1-P2 10-10, 10-12, 10-14, PHB0 on service 10-16 processor/PCI backplane PCI Slot 1 U0.1-P2/I1 PCI Slot 1 Card U0.1-P2-I1...
Page 67 Location Physical Logical FRU Name Code Location Connection Connection Code Battery U0.1-P2-V3 Platform Firmware U0.1-P2/Y1 SCSI Controller internal U0.1-P2/Z1 1Z-08 connector Z1 DVD Drive U0.1-P2/Z1-A0 1Z-08-00-0,0 Tape Drive U0.1-P2/Z1-A1 1Z-08-00-1,0 Internal DASD 1 U0.1-P2/Z1-A8 1Z-08-00-8,0 Internal DASD 2 U0.1-P2/Z1-A9 1Z-08-00-9,0 Internal DASD 3 U0.1-P2/Z1-AA 1Z-08-00-10,0...
Page 68 Ux.dd-xx-yy | | | | | | | | | | | yy This code is used for the next component (yy, yy, yy, ...) | | xx This code is used for the next component (Px, Fx, Vx, ...) | dd This code is the drawer number for the I/O drawer (2 to 63) Ux This code normally identifies the rack in which a drawer is installed.
Page 69 Location Physical Logical FRU Name Code Location Connection Connection Code PCI slot 4 adapter U0.dd-P1-I4 2R-08 PCI slot 5 U0.dd-P1/I5 PCI slot 5 adapter U0.dd-P1-I5 2U-08 PCI slot 6 U0.dd-P1/I6 PCI slot 6 adapter U0.dd-P1-I6 2d-08 Power supply 1 (with 2 U0.dd-V1 fans) Power supply 2 (with 2...
Page 70 Location Physical Logical FRU Name Code Location Connection Connection Code PCI slot 5 U0.dd-P1/I5 PCI slot 5 adapter U0.dd-P1-I5 3L-08 PCI slot 6 U0.dd-P1/I6 PCI slot 6 adapter U0.dd-P1-I6 3V-08 Power supply 1 (with 2 U0.dd-V1 fans) Power supply 2 (with 2 U0.dd-V2 fans) Cooling blower fan 5...
Page 71 Location Physical Logical FRU Name Code Location Connection Connection Code PCI slot 5 adapter U0.dd-P1-I5 4C-08 PCI slot 6 U0.dd-P1/I6 PCI slot 6 adapter U0.dd-P1-I6 4M-08 Power supply 1 (with 2 U0.dd-V1 fans) Power supply 2 (with 2 U0.dd-V2 fans) Cooling blower fan 5 U0.dd-F5 Rack indicator connector...
Page 72 Location Physical Logical FRU Name Code Location Connection Connection Code PCI slot 6 U0.dd-P1/I6 PCI slot 6 adapter U0.dd-P1-I6 5D-08 Power supply 1 (with 2 U0.dd-V1 fans) Power supply 2 (with 2 U0.dd-V2 fans) Cooling blower fan 5 U0.dd-F5 Rack indicator connector U0.dd-P1/Q3 (4 pins) SPCN connector 1...
Page 73 Location Physical Logical FRU Name Code Location Connection Connection Code PCI slot 6 adapter U0.dd-P1-I6 65-08 Power supply 1 (with 2 U0.dd-V1 fans) Power supply 2 (with 2 U0.dd-V2 fans) Cooling blower fan 5 U0.dd-F5 Rack indicator connector U0.dd-P1/Q3 (4 pins) SPCN connector 1 U0.dd-P1/Q4 SPCN connector 2...
Page 74 Location Physical Logical FRU Name Code Location Connection Connection Code Power supply 1 (with 2 U0.dd-V1 fans) Power supply 2 (with 2 U0.dd-V2 fans) Cooling blower fan 5 U0.dd-F5 Rack indicator connector U0.dd-P1/Q3 (4 pins) SPCN connector 1 U0.dd-P1/Q4 SPCN connector 2 U0.dd-P1/Q5 VPD drawer U0.dd...
Page 75 Location Physical Logical FRU Name Code Location Connection Connection Code Power supply 1 (with 2 U0.dd-V1 fans) Power supply 2 (with 2 U0.dd-V2 fans) Cooling blower fan 5 U0.dd-F5 Rack indicator connector U0.dd-P1/Q3 (4 pins) SPCN connector 1 U0.dd-P1/Q4 SPCN connector 2 U0.dd-P1/Q5 VPD drawer U0.dd...
Page 76 Location Physical Logical FRU Name Code Location Connection Connection Code Power supply 1 (with 2 U0.dd-V1 fans) Power supply 2 (with 2 U0.dd-V2 fans) Cooling blower fan 5 U0.dd-F5 Rack indicator connector U0.dd-P1/Q3 (4 pins) SPCN connector 1 U0.dd-P1/Q4 SPCN connector 2 U0.dd-P1/Q5 VPD drawer U0.dd...
Page 77 FRU Name Physical Location Code AIX Location Code PCI slot 6 U0.dd-P1/I6 PCI card in slot 6 U0.dd-P1/I6 1v-08 PCI slot 7 U0.dd-P1/I7 PCI card in slot 7 U0.dd-P1/I7 25–08 Power Supply Power supply 1 (no internal blower) U0.dd-V1 Power supply 2 (no internal blower) U0.dd-V2 Cooling Blowers Cooling blower 1...
Page 78 FRU Name Physical Location Code AIX Location Code SCSI SES0 U0.dd-P1-Ix/Zn-AF Dependent on Ix SES1 U0.dd-P1-Iy/Zn-AF Dependent on Iy FRU Name Physical Location Code AIX Location Code Model D20 I/O Drawer U0.dd (dd = any number from 2 through 63) Second I/O Subsystem Location Codes Rack frame I/O drawer backplane...
Page 79 FRU Name Physical Location Code AIX Location Code Cooling blower 1 U0.dd-F1 Cooling blower 2 U0.dd-F2 Cooling blower 3 U0.dd-F3 Cooling blower 4 U0.dd-F4 SPCN Connectors Reserved U0.dd-P1/Q3 Reserved U0.dd-P1/Q4 SPCN3 connector U0.dd-P1/Q5 SPCN4 connector U0.dd-P1/Q6 Rack Indicator Rack beacon (4-pin) U0.dd-P1/Q7 Operator Panel Operator panel...
Page 80: Specifications
Specifications This section contains specifications for the Eserver pSeries 650 system. pSeries 650 Physical Specifications and Loads The following tables illustrate the physical, electrical and thermal, acoustical, and environmental characteristics of various pSeries 650 system configurations. Power and Electrical Requirements Redundant power line cords are standard on the pSeries 650.
Page 81 __ 8. Turn on the branch circuit CB. Measure for appropriate voltages between phases. If no voltage is present on the receptacle case or grounded pin, the receptacle is safe to touch. __ 9. With an appropriate meter, verify that the voltage at the outlet is correct. __ 10.
Page 82: Service Inspection Guide
1. See “Declared Acoustical Noise Emissions” on page 690 for definitions of noise emissions positions. See noise emissions note 4. 2. Inrush currents occur only at initial application of power, no inrush occurs during normal power off-on cycle. 3. The upper limit of the dry bulb temperature must be derated 1°C per 137 m (450 ft.) above 915 m (3000 ft.). 4.
Page 83: Chapter 2. Diagnostics Overview
Chapter 2. Diagnostics Overview pSeries 650 servers use an integrated set of software diagnostic procedures to facilitate system maintenance. This book and the Eserver pSeries Diagnostic Information for Multiple Bus Systems are the basis of the diagnostic procedures for pSeries 650 systems. In particular, chapters 3, 4, 5, and 10 in this book are important for the trained service representative to understand and use when isolating a failure on the system.
Page 84: Checkpoints
v The operating system error log v The service action event log (such as loss of surveillance from the HMC to a logical partition) in the Service Focal Point application If the system attention LED is turned on, you can access the system logs to determine the reason. The method used to access your system logs depends on how your system is set up.
Page 85: Fru Isolation
0xxx 2xxx 0xxx codes are AIX progress codes and configuration codes. Location codes may also be shown on the operator panel display during this time. AIX progress codes do not appear when the operating system is Linux. Error Codes If a fault is detected, an 8-digit error code is displayed in the operator panel display. A location code may be displayed at the same time on the second line.
Page 86: Fru Identify Leds
FRU identify LED to be flashed. See the ″Hardware Service Functions″ section of the ″Service Focal Point″ chapter of the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590, for instructions on activating and deactivating a FRU identify LED.
Page 87: Service Focal Point
Verify that the HMC host names are defined. For more information about using fully qualified and short host names, see the IBM Hardware Management Console Operations Guide for pSeries, order number SA38-0590. v If you need to add or change a partition name, see the IBM Hardware Management Console Operations Guide for pSeries. Testing Error Reporting To ensure that Service Focal Point is configured correctly, generate a test error by doing the following: 1.
Page 88: Service Focal Point Settings
5. Type F3 to exit diagnostics. 6. Wait for one minute while the managed system sends the error to Service Focal Point. 7. Check the Serviceable Event window to ensure that the error was sent to Service Focal Point and that Service Focal Point reported the error.
Page 89: Working With Serviceable Events
Enabling this notification causes errors to be passed to the Service Agent application for notification. Note: You must further configure Service Agent to handle notifications sent by Service Focal Point. For more information about Service Agent, refer to the IBM Hardware Management Console Operations Guide for pSeries, order number SA38-0590...
Page 90 event. On this window, designate the set of serviceable events you want to view by specifying your search criteria (such as event status or error class). Note: Only events that match all of the criteria that you specify are shown. 6.
Page 91 1. Perform the steps in “Viewing Serviceable Event Details” on page 70. 2. Select the error to which you want to add comments to and click Comments. If you want to close the event and add comments, click Close Event from this window. The Serviceable Event Comments window opens.
Page 92: Activating And Deactivating Fru Leds
2. Click Add New FRU. 3. Type the FRU’s location code and its part number in the appropriate fields. 4. Click Add to List. The Update FRU Information window opens and displays the newly added FRU in the lower table. 5.
Page 93: Accessing Errors When A System Is Attached To An Hmc
v “Accessing Errors when a System is Running Linux and the Console is Not an HMC.” Accessing Errors when a System is Attached to an HMC If the system attention LED comes on and the system is attached to an HMC for its console, do the following to access the error logs: 1.
Page 94: Resetting The Led When A System Is Attached To An Hmc
4. In the LED Management window, select one or more managed systems from the table. 5. Select Deactivate LED. The associated system attention LED is turned off. For more information about the virtual operator panel on the HMC, see the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590.
Page 95: Chapter 3. Maintenance Analysis Procedures (Maps)
Chapter 3. Maintenance Analysis Procedures (MAPs) This chapter contains Maintenance Analysis Procedures (MAPs) for the Eserver pSeries 650. Entry MAP When possible, run online diagnostics in service mode. Online diagnostics perform additional functions compared to standalone diagnostics. This ensures that the error state of the system that was captured in NVRAM is available for your use in fixing the problem.
Page 96 Symptom Starting Point Go to the Fast Path MAP in the Eserver pSeries You have a problem that does not prevent the system from booting and the media subsystem operator panel is Diagnostic Information for Multiple Bus Systems. functional. Go to MAP 0020 in the Eserver pSeries Diagnostic You do not have a symptom.
Page 97: Quick Entry Map
Quick Entry MAP Quick Entry MAP Table of Contents Problem Description Page No. Service actions The rack indicator LED does not operate as described on “FRU Identify LEDs” on page 119. The system attention LED on the operator panel is on. OK does not appear in the operator panel display before pressing the power-on button.
Page 98 Symptom Action Service Actions You have an open service event in the service action Go to “Service Focal Point” on page 67. event log. You have parts to exchange or a corrective action to 1. Go to Chapter 9, “Removal and Replacement perform.
Page 99 Symptom Action You have a blank display on the operator panel. Other 1. Ensure that the processor subsystem to operator LEDs on the operator panel appear to behave normally. panel cable is connected properly. 2. Replace the operator panel assembly, Location: U0.1-L1.
Page 100 Navigation area of the HMC Management Environment, then the HMC or the connection to the managed system might be failing. 3. Go to the Entry MAP in the IBM Hardware Management Console for pSeries Maintenance Guide, order number SA38-0603. 4. If you cannot fix the problem using the HMC tests in...
Page 101 Symptom Action All display problems. 1. If using the Hardware Management Console, go to the IBM Hardware Management Console for pSeries Maintenance Guide, order number SA38-0603. 2. If using a graphics display: a. Go to the problem determination procedures for the display.
Page 102 The system does not respond to the password being 1. If the password is being entered from the Hardware entered or the system login prompt is displayed when Management Console (HMC), go to the IBM booting in service mode. Hardware Management Console for pSeries Maintenance Guide.
Page 103 Symptom Action The System Management Services menu is displayed. The device or media you are attempting to boot from may be faulty. 1. Check the SMS error log for any errors. To check the error log: v Choose error log v If an error is logged, check the time stamp.
Page 104: Map 1020: Problem Determination
MAP 1020: Problem Determination Purpose of This MAP Use this MAP to get an error code if you were not provided one by the customer or you are unable to load diagnostics. If you are able to load the diagnostics, go to MAP 0020 in the Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 105 Note: Be prepared to answer questions regarding the operator panel display and to perform certain actions based on displayed POST indicators. Please be observant of these conditions. 1. Run diagnostics on any partition. Find your symptom in the following table; then follow the instructions given in the Action column.
Page 106 Symptom Action The system stopped. A POST indicator is displayed on If the POST indicator represents: the system console and an eight-digit error code is not 1. Memory, do a slow boot. If an error code points to displayed. memory, replace that memory book and run slow boot again.
Page 107 Step 1020-2 There is a problem with the keyboard. Find the type of keyboard you are using in the following table; then follow the instructions given in the Action column. Keyboard Type Action Type 101 keyboard (U.S.). Identified by the size of the Record error code M0KB D001;...
Page 108 Step 1020-4 1. Turn off, then turn on the system unit. 2. When the keyboard indicator (the word keyboard) displays, press the 1 key on a directly attached keyboard or the 1 key on an ASCII terminal or 1 key on the HMC. 3.
Page 109: Map 1230: Linux Platform Error Problem Resolution
MAP 1230: Linux Platform Error Problem Resolution Purpose of This MAP Use this MAP to resolve problems reported by SRNs A00-000 to A1F-FFF from a partition running Linux. Step 1230-1 1. The last character of the SRN is bit-encoded as follows: Replace all FRUs listed Hot-swap is supported Software or Firmware could be the cause...
Page 110 Step 1230-4 Were any FRUs or location code reported with the SRN? Go to “Step 1230-5.” Go to “Step 1230-9.” Step 1230-5 Run the diagnostics in problem determination mode on sysplanar0. Were there any FRUs reported with the SRN? Go to “Step 1230-6.” Go to “Step 1230-9.”...
Page 111 3. Refer to the last character in the SRN. A 1, 3, 5, or 7 indicates that all FRUs listed on the Problem Report Screen need to be replaced. For SRNs ending with any other character, exchange one FRU at a time, in the order listed. Note: Use the appropriate procedure in Chapter 9, “Removal and Replacement Procedures,”...
Page 112 Step 1230-13 1. After performing a shutdown of the operating system, turn off power to the system. 2. Remove the new FRU and install the original FRU. 3. Exchange the next FRU in list. 4. Turn on power to the system. 5.
Page 113 Step 1230-15 Is the problem the same as the original problem? The symptom has changed. Check for loose cards, cables, and obvious problems. If you do not find a problem, go to “MAP 1020: Problem Determination” on page 84 and get a new SRN. Go to “Step 1230-16.”...
Page 114: Map 1235: System Array Self-Repair Problem Resolution For Linux
MAP 1235: System Array Self-Repair Problem Resolution for Linux Purpose of This MAP Use this MAP to resolve problems reported by SRNS A11-560 to A11-580. Note: The following steps may require that the system be rebooted to invoke Array bit steering, so you may wish to schedule deferred maintenance with the system administrator to arrange a convenient time to reboot their system.
Page 115: Map 1320: Service Focal Point
MAP 1320: Service Focal Point These procedures define the steps to take when servicing a machine that is equipped with Service Focal Point (SFP). You might also be directed to these procedures if the system is running Linux as its only operating system.
Page 116: Map 1321: Quick Entry Map For Systems With Service Focal Point
MAP 1321: Quick Entry MAP for Systems with Service Focal Point Notes: 1. If you are working on a system that is managed by an HMC, the term service action event is synonymous with serviceable event in this MAP. 2. If you are working on a system that is managed by an HMC, some steps in this MAP may ask you to open the details of the service action event and obtain error codes and FRU location codes.
Page 117 Step 1321-7 Are there any serviceable events with FRU location codes reported in “Step 1321-5” on page 96? Go to “Step 1321-14” on page 98. Go to “Step 1321-8.” Step 1321-8 From the list of open service action events with FRUs reported, examine the details of each service action event and record the error code.
Page 118 Step 1321-14 At the HMC console, open Service Focal Point (SFP) and examine the service action event log for any closed service action events. For SFP operating instructions, refer to “Service Focal Point” on page 67. Step 1321-15 Are there any service action events that are closed? Go to the table in “Entry MAP”...
Page 119 Step 1321-22 Look for and record any additional error information or software messages on the operator panel or the console (serial TTY, Vterm, or HMC). Choose a running Linux partition (preferably the partition with the problem). Step 1321-23 Is Linux usable in any partition with Linux installed? Go to “Step 1321-30”...
Page 120 3. Record that, for this Linux partition, you performed substep 3 of “Step 1321-24” on page 99 for later steps. Use the following command to list diagela messages recorded in the Linux system log: cat /var/log/platform |grep diagela |more Linux run-time diagela error messages are logged in the platform file under /var/log. The following is an example of the Linux system error log diagela messages.
Page 121 4. Also use the following command to list RTAS messages recorded in the Linux system log: cat /var/log/platform |grep RTAS |more Linux RTAS error messages are logged in the platform file under /var/log. The following is an example of the Linux system error log RTAS messages. Aug 27 12:16:33 larry kernel: RTAS: 15 -------- RTAS event begin -------- Aug 27 12:16:33 larry kernel: RTAS 0: 04440040 000003f8 96008508 19155800 Aug 27 12:16:33 larry kernel: RTAS 1: 20030827 00000001 20000000 00000000...
Page 122 Aug 27 12:16:33 larry kernel: RTAS 46: 00000000 00000000 00000000 00000000 Aug 27 12:16:33 larry kernel: RTAS 47: 00000000 00000000 00000000 00000000 Aug 27 12:16:33 larry kernel: RTAS 48: 00000000 00000000 00000000 00000000 Aug 27 12:16:33 larry kernel: RTAS 49: 00000000 00000000 00000000 00000000 Aug 27 12:16:33 larry kernel: RTAS 50: 00000000 00000000 00000000 00000000 Aug 27 12:16:33 larry kernel: RTAS 51: 00000000 00000000 00000000 00000000 Aug 27 12:16:33 larry kernel: RTAS 52: 00000000 00000000 00000000 00000000...
Page 123 Step 1321-26 If you performed substep 3 of “Step 1321-24” on page 99 for the current Linux partition, go to “Step 1321-27,” and when asked in “Step 1321-27,” do not record any RTAS messages from “Step 1321-26” for the current Linux partition. Examine the Linux boot (IPL) log by logging in to the system as the root user and entering the following command: cat /var/log/boot.msg /var/log/dmesg 2>/dev/null | grep RTAS |more...
Page 124 Step 1321-28 If you performed substep 3 of “Step 1321-24” on page 991321-24 for the current Linux partition, go to “Step 1321-29,” and when asked in “Step 1321-29,” do not record any additional extended data from “Step 1321-26” on page 103 for the current Linux partition. Examine the extended data in both logs.
Page 125 Step 1321-31 If no additional error information is available and the problem has not been corrected, shut down the system. If an HMC is not attached, you need a laptop computer (and cable, part number 62H4857) capable of connecting to serial port 1 on the processor subsystem. Note: The Linux login prompt cannot be seen on a laptop computer connected to serial port 1.
Page 126 Step 1321-36 To determine if any device(s) or adapter(s) are missing, compare the list of found resources and partition assignments to the customer’s known configuration. Record the location of any missing devices. Also record any differences in the descriptions or the locations of devices. You may also compare this list of found resources to a prior version of the device tree as follows: Note: Every time that the partition is booted, the update-device-tree command is run and the device tree is stored in the /var/lib/lsvpd/ directory in a file with the file name device-tree-YYYY-MM-DD-...
Page 127 Step 1321-38 Does the system appear to stop or hang before reaching the login prompt or did you record any problems with resources in “Step 1321-36” on page 106? Note: If the system console or VTERM window is always blank, choose NO. If you are sure the console or VTERM is operational and connected correctly, answer the question for this step.
Page 128 Step 1321-42 Was the problem corrected in Step 1321-41? Go to “Step 1321-34” on page 105. Return the system to its original configuration. This ends the procedure. Go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems. Step 1321-43 Were any other symptoms recorded in step 1321-1? Call support.
Page 129: Map 1322: End Of Call Map For Systems With Service Focal Point
MAP 1322: End of Call MAP for Systems with Service Focal Point Note: If you are working on a system that not managed by an HMC go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems Step 1322-1 For future reference, record the SRC or symptom and the location code of the FRU you replaced.
Page 130 Step 1322-9 Is the FRU list identical (same FRUs, same number of FRUs, and same order of FRUs) to the FRU list of the error code recorded in “Step 1322-1” on page 109? Go to “Step 1322-10.” Go to “Step 1322-11.” Step 1322-10 The FRU list is different.
Page 131 Step 1322-16 Remove all entries in the list of all partition(s) you recorded in “Step 1322-11” on page 110. If you are referred to the list of partition(s) obtained in “Step 1322-11” on page 110 in future steps, the list is empty. Go to “Step 1322-17.”...
Page 132 Step 1322-27 Is the error class recorded in “Step 1322-6” on page 109 AIX? Go to “Step 1322-33.” Go to “Step 1322-28.” Step 1322-28 Perform the following steps for each entry in the list of all partition(s) you recorded in “Step 1322-11” on page 110, except the partition you were using to debug the original problem.
Page 133 Step 1322-34 While processing all service action events, were you directed to “Step 1322-14” on page 110? If the system attention LED is still on, use the HMC to turn off the LED as described in “Resetting the LED when a System is Attached To an HMC” on page 74. This completes the repair. Return the system to the customer.
Page 134: Map 1420: Recovery Procedures For Hot-Pluggable Pci Adapters
MAP 1420: Recovery Procedures for Hot-Pluggable PCI Adapters This procedure is used to locate problems that might occur when performing a PCI adapter hot-plug operation. Find the symptom in the following table; then follow the instructions given in the Action column. Recovery Procedures for Hot-Pluggable PCI Adapters Symptom/Reference Code Action...
Page 135: Map 1422: Slot Is Empty Even When Populated
Step 1421-6 Is the PCI slot power LED of the location recorded in “Step 1421-3” on page 114 on? Go to “Step 1421-7.” Go to “Step 1421-12.” Step 1421-7 Are there any empty PCI slots attached to the system that are not assigned to any partitions? Go to “Step 1421-12.”...
Page 136 Step 1422-2 Is the PCI slot power LED of the location recorded in “Step 1422-1” on page 115 on? Go to “Step 1422-3.” Go to “Step 1422-7.” Step 1422-3 Disconnect any external cables from the adapter identified in “Step 1422-1” on page 115. Step 1422-4 Remove the adapter identified in “Step 1422-1”...
Page 137 Step 1422-11 Insert a new adapter of the same type recorded in “Step 1422-1” on page 115 into the slot assigned in “Step 1422-10” on page 116. Step 1422-12 Move any external cabling from the adapter in the slot recorded in “Step 1422-1” on page 115 to the adapter in the slot assigned in “Step 1422-10”...
Page 138: Map 1520: Power
MAP 1520: Power This procedure is used to locate power problems in the CEC drawer, I/O drawer(s) or rack. If a problem is detected, this procedure helps you isolate the problem to a failing unit. Observe the following safety notices during service procedures. DANGER An electrical outlet that is not correctly wired could place hazardous voltage on metal parts of the system or the devices that attach to the system.
Page 139: Fru Identify Leds
FRU identify LED to be flashed. See the ″Hardware Service Functions″ section of the ″Service Focal Point″ chapter of the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590 for instructions on activating and/or deactivating a FRU identify LED.
Page 140: Map 1521: The Base Processor Subsystem Drawer Will Not Power On And No Error Codes Are Available
Map 1521: The Base Processor Subsystem Drawer Will Not Power On and No Error Codes are Available Step 1521-1 Attempt to power on the base system drawer (see “Powering Off and Powering On the System” on page 545) Does the base system drawer power on? Go to “Step 1521-2.”...
Page 141 Go to the beginning of this step and replace the next item. Call service support. The item just replaced was defective. This ends the procedure. Go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems Step 1521-8 Is this machine connected to dc power? Go to “Step 1521-12”...
Page 142 Step 1521-12 Are all circuit breakers reset at the rack power distribution unit(s)? Reset the popped breaker. This ends the procedure. Go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 1521-13.” Step 1521-13 Are all the ac power cables seated firmly and connected correctly from the rack power distribution unit(s) to the rack drawers?
Page 143 Step 1521-16 Reconnect the ac power cable(s) to the power distribution unit. Note: Read the danger and caution notices under “Safety Notices” on page xi before continuing with this procedure. Perform the following: 1. Disconnect the ac power cable from each power supply of the base system drawer. 2.
Page 144 Step 1521-18 Is the ac power cable from the rack power distribution unit to the customer’s ac power outlet connected and seated correctly at both ends? Connect the ac power cable correctly at both ends. This ends the procedure. Go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 145 Step 1521-22 Replace the items in the following list one at a time. Turn the power off before removing the item, and turn the power back on after replacing the item to determine if the drawer will power on. 1. Replace the power supply with the amber fault LED on solid. 2.
Page 146 Go to “Step 1521-28.” Go to “Step 1521-26.” Step 1521-26 Reinsert the following components in the base system drawer, one card at a time, disconnecting the ac power cable (dc power cable in a dc-powered system) to each power supply before reinsertion and reconnecting the ac power cable (dc power cable for a dc-powered system) to each power supply after reinsertion: 1.
Page 147: Map 1522: Cannot Power On The I/O Drawer
Map 1522: Cannot Power On the I/O Drawer Step 1522-1 Attempt to power on the I/O drawer (see “Powering Off and Powering On the System” on page 545) Does the I/O drawer power on? Go to “Step 1522-2.” This ends the procedure. Go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 148 Step 1522-7 Replace the items in the following list one at a time. Turn off the power before removing the item, and turn the power back on after replacing the item to determine if the drawer will power on. 1. Replace the power supply with the green DC good LED off solid. 2.
Page 149 Step 1522-11 Note: Read the danger and caution notices under “Safety Notices” on page xi before continuing with this procedure. Perform the following: 1. Disconnect the dc power cable from each power supply of the I/O drawer. 2. Use a multimeter to measure the dc voltage at the drawer end of each dc power cable. Is the dc voltage from −40 V dc to −60 V dc? There is no power to the drawer.
Page 150 Step 1522-15 Note: Read the danger and caution notices under “Safety Notices” on page xi before continuing with this procedure. Perform the following: 1. Disconnect the ac power cable(s) from the power distribution unit that supplies power to the I/O drawer.
Page 151 Step 1522-16 Reconnect the ac power cable(s) to the power distribution unit. Note: Read the danger and caution notices under “Safety Notices” on page xi before continuing with this procedure. Perform the following: 1. Disconnect the ac power cable from each power supply of the I/O drawer. 2.
Page 152 Step 1522-19 Note: Read the danger and caution notices under “Safety Notices” on page xi before continuing with this procedure. Perform the following: 1. Disconnect the mainline ac power cable from the power distribution unit that supplies power to the I/O drawer.
Page 153 Step 1522-22 Replace the items in the following list one at a time. Turn the power off before removing the item, and turn the power back on after replacing the item to determine if the drawer will power on. 1. Replace the power supply with the amber fault LED on solid. 2.
Page 154 Step 1522- 25 Disconnect the ac power cable (dc power cable for a dc-powered system) to each power supply of the I/O drawer and remove the following components from the I/O drawer, one at a time, in the sequence listed: 1.
Page 155 Step 1522-28 Replace the I/O drawer backplane. Disconnect the power cable to each power supply before replacement and then reconnect the power cable to each power supply after replacement: Does the I/O drawer power on? Call your next level of support for assistance. This ends the procedure. Reinsert the components removed in “Step 1522- 25”...
Page 156: Map 1523: The Spcn Error Codes Table Directed You Here And The Error Code Is 1011 1B0X
Map 1523: The SPCN Error Codes Table Directed You Here and the Error Code is 1011 1B0x A base system power supply is reporting a load fault. Note: Read the danger and caution notices under “Safety Notices” on page xi before continuing with this procedure.
Page 157 Step 1523-3 This ends the procedure. Go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems. Step 1523-4 1. Turn off the power. 2. Remove the new power supply, just installed in base system power supply 2 and restore the original power supply to base system power supply 2.
Page 158 Step 1523-5 1. Turn off the power. 2. Remove base system fan 3. Disregard any error code for the processor subsystem fan if it occurs during this step. 3. Turn on the power. Is the error code 1011 1B0x displayed? Replace base system fan 3, location: U0.1-F3.
Page 159 Step 1523-7 1. Turn off the power. 2. Disconnect the ac power cables (dc power cables in a dc-powered system) from the base system drawer. 3. Reinstall one of the cards that was removed in “Step 1523-1” on page 136, in the sequence listed: a.
Page 160: Map 1540: Problem Isolation Procedures
FRU identify LED to be flashed. See the ″Hardware Service Functions″ section of the ″Service Focal Point″ chapter of the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590, for instructions on activating and/or deactivating a FRU identify LED.
Page 161: Map 1541: Jtag Problem Isolation
Problem Isolation Procedures Symptom/Reference Code/Checkpoint Action 406x 0EB1, 406x 0EB2, 406x 0EB3, 406x 0EB4, Go to “MAP 1549: Attention Problem Isolation” on page 406x 0EB5, 406x 0EB6, 406x 0EB7, 406x 0EB8, 172. 406x 0EB9, 406x 0EBA, 406x 0EBB, 406x 0EBC 406x 0EB0 Go to “MAP 1541: JTAG Problem Isolation.”...
Page 162 Step 1541-7 Turn off the power. Step 1541-8 Attention: Before replacing the processor backplane, call for support. Replace the processor backplane at U0.1-P1. Step 1541-9 Turn on the power. Step 1541-10 Did the system stop with the same error code as recorded in “Step 1541-1” on page 141? The card just replaced was defective.
Page 163 Step 1541-17 Reinsert one of the cards you removed in “Step 1541-13” on page 142. Step 1541-18 Turn on the power. Step 1541-19 Did the system stop with the same error code as recorded in “Step 1541-1” on page 141? Go to “Step 1541-20.”...
Page 164: Map 1542: I/O Problem Isolation
Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 1541-29.” Step 1541-29 Turn off the power. Step 1541-30 Replace all the DIMMs on the processor card at location U0.1-P1-C1. Step 1541-31 Turn on the power.
Page 165 Reboot Policy From the System Power Control Menu, go to the Reboot/Restart Policy Setup Menu and set: 1. Number of reboot attempts to 0 (zero) 2. Use OS-Defined restart policy to No 3. Enable supplemental restart policy to No. Call Out From the Call-In/Call-Out Setup Menu, go to the Serial Port Selection Menu and disable call-out on both serial ports.
Page 166 Step 1542-4 The system stopped with the Please define system console prompt appearing on the system console. Standalone diagnostics can be booted. Perform the following: 1. Follow the instructions on the screen to select the system console. 2. When the DIAGNOSTIC OPERATING INSTRUCTIONS screen is displayed, press Enter. 3.
Page 167 Step 1542-5 Examine the base system RIO port 0 of RIO connector card 1 (U0.1-P1-H1/Q1). Are there any I/O subsystems attached to the base system? Go to “Step 1542-32” on page 167. Go to “Step 1542-6.” Step 1542-6 There may be missing devices associated with one or more I/O subsystems. Attention: The 7311 Model D10 I/O Subsystem and the 7311 Model D20 I/O Subsystem may both be connected to the pSeries 650.
Page 168 is ″looped one″ and record the location of the next I/O subsystem that is connected to I/O port connector 1 of the ″looped one″ I/O subsystem. Go to substep 13. 9. If the RIO cable attached to the I/O port connector 1 (U0.x-P1.1/Q2) of the I/O subsystem recorded in substep 4 on page 147 connects to port 1 of RIO connector card 1 (U0.1-P1-H1/Q2) of the base system, record that the I/O subsystem is ″not looped left.″...
Page 169 substep 18 on page 148 must connect to port 1 of RIO connector card 1 (U0.1-P1-H1/Q2) of the base system, record that the next I/O subsystem is ″looped four.″ A maximum of four I/O subsystems can be looped on a single pair of base system RIO ports. 24.
Page 170 Reconfigure the system to its original condition. Go to “Map 0410: Repair Checkout” in the Eserver pSeries Diagnostic Information for Multiple Bus Systems Step 1542-7 The pSeries 650 Model 6M2 server may have up to four I/O subsystems attached to each of the four pairs of RIO ports of the base system.
Page 171 Step 1542-9 For any I/O subsystem attached to the RIO card of the base system defined in the step that sent you to this step (“Step 1542-9”): If the I/O subsystem was recorded as ″looped one,″ ″not looped left,″ or ″not looped right,″...
Page 172 Step 1542-13 1. If it is not already off, turn off the power. 2. Remove all adapters from slots 1, 2, 3, 4, 5, and 6 (location codes Ux.y-P1-I1 through I6) from the I/O subsystem, or for a 7311 Model D20 I/O Subsystem, slots 1-7 (location codes U0.x-P1-I1 through I7). 3.
Page 173 Step 1542-15 1. If it is not already off, turn off the power. 2. Remove all adapters from slots 1, 2, 3, 4, 5, and 6 (location codes Ux.y-P1-I1 through I6) from the I/O subsystem, or for a 7311 Model D20 I/O Subsystem, slots 1-7 (location codes U0.x-P1-I1 through I7). 3.
Page 174 Step 1542-17 If the Please define the System Console screen does display and all attached devices and adapters are listed, the problem is with one of the adapter cards or devices that was removed or disconnected from the I/O subsystem. 1.
Page 175 Step 1542-19 1. Turn off the power. 2. Disconnect the I/O subsystem power cables. 3. Replace the following parts, one at a time, in the sequence listed: a. I/O subsystem backplane of any ″looped one″, ″not looped right″, or ″not looped left″ I/O subsystem attached to the RIO card of the base system defined in the step that sent you to “Step 1542-9”...
Page 176 Step 1542-20 1. Turn off the power. 2. The item just replaced fixed the problem. 3. If a display adapter with keyboard and mouse were used, reinstall the display adapter card, keyboard, and mouse. 4. Reconnect the diskette drive cable to the diskette drive connector on the base system. 5.
Page 177 Step 1542-22 Reconnect the next I/O subsystem in the configuration that you recorded in earlier in “Step 1542-7” on page 150. Use the following table to determine the next base system RIO card to use to reconnect the I/O subsystem(s). Current Base System RIO Card New Base System RIO Card Go to:...
Page 178 Step 1542-25 Note: Before continuing, check the cabling from the base system to the I/O subsystem(s) to ensure that the system is cabled correctly. Refer to “Subsystem Positioning and Cabling” on page 11 for valid configurations. Record the current cabling configuration and then continue with the following steps: 1.
Page 179 16. At the ″looped two″ I/O subsystem recorded in substep 14 on page 158, disconnect the I/O port connector 1 (U0.x-P1.1/Q2), and reconnect to the I/O port connector 0 (U0.x-P1.1/Q1) of the ″looped one″ I/O subsystem identified in substep 8 on page 158. 17.
Page 180 33. Use the Display Configuration and Resource List to list all attached devices and adapters (refer to the Eserver pSeries Diagnostic Information for Multiple Bus Systems if necessary). 34. Check that all attached devices and adapters are listed. Did the Please define the System Console screen display and are all attached devices and adapters listed? Go to “Step 1542-9”...
Page 181 Go to “Step 1542-27” to isolate I/O problems attached to the base system RIO connector card 2 (U0.1-P1-H2). Go to “Step 1542-22” on page 157. Step 1542-27 Examine the base system RIO port 0 of RIO connector card 2 (U0.1-P1-H2/Q5). Are there any I/O subsystems attached to this connector of the base system? Go to “Step 1542-29”...
Page 182 connects to the I/O port connector 0 of another I/O subsystem, record that the next I/O subsystem identified in substep 8 on page 161 is ″looped two,″ and record the location of the I/O subsystem that is connected to I/O port connector 1 of the ″looped two″ subsystem. Go to substep 18. 14.
Page 183 28. If an I/O subsystem was ″looped three,″ verify that the ″looped two″ I/O subsystem I/O port connector 1 (U0.x-P1.1/Q2) is connected to the ″looped three″ I/O subsystem I/O port connector 0 (U0.x-P1.1/Q1). 29. If an I/O subsystem was ″looped four,″ verify that the ″looped three″ I/O subsystem I/O port connector 1 (U0.x-P1.1/Q2) is connected to the ″looped four″...
Page 184 5. Make sure the I/O subsystem(s) are cabled correctly as shown in “Subsystem Positioning and Cabling” on page 11. 6. Turn on the power to boot standalone diagnostics from CD. 7. If the Please define the System Console screen is displayed, follow directions to select the system console.
Page 185 9. If the RIO cable attached to the I/O port connector 1 (U0.x-P1.1/Q2) of the I/O subsystem recorded in substep 4 on page 164 connects to port 1 of RIO extender card 1 (U0.1-P1-H2.1/Q8) of the base system, record that the I/O subsystem is ″not looped left.″ 10.
Page 186 24. At the base system, disconnect the cable connection at RIO port 1 of RIO extender card 2 (U0.1-P1-H2.1/Q8), and reconnect it to RIO port 0 of RIO extender card 2 (U0.1-P1-H2.1/Q7). 25. At the ″looped four″ I/O subsystem recorded in substep 23 on page 165, disconnect the I/O port connector 1 (U0.x-P1.1/Q2) and reconnect to the I/O port connector 0 (U0.x-P1.1/Q1) of the ″looped one″...
Page 187 Step 1542-32 Are there any adapters in slots 1, 2, 3, 4, 5, 6, or 7 (location codes U0.1-P1-I1 through I7) in the base system? Go to “Step 1542-33.” Go to “Step 1542-35.” Step 1542-33 Replace the service processor/PCI backplane, location U0.1-P2 Step 1542-34 1.
Page 188 2. Reinstall one adapter and device that was removed. Us the original adapter cards in their original slots when reinstalling adapters. 3. Turn on the power to boot standalone diagnostics from CD. 4. If the Please define the System Console screen is displayed, follow directions to select the system console.
Page 189: Map 1547: Rio Adapter Card Problem Isolation
8. Use the Display Configuration and Resource List to list all attached devices and adapters (refer to the Eserver pSeries Diagnostic Information for Multiple Bus Systems, order number SA38-0509, if necessary). 9. Check that all attached devices and adapters are listed. Did the Please define the System Console screen display and are all attached devices and adapters listed? Replace the next part in the list and return to the beginning of this step.
Page 190: Map 1548: Memory And Processor Problem Isolation
Step 1547-8 Attention: Before replacing the processor backplane, call for support. Replace the processor backplane at U0.1-P1. Step 1547-9 Turn on the power. Step 1547-10 Did the system stop with the same error code as recorded in “Step 1547-1” on page 169? The part just replaced was defective.
Page 191 v If the error code recorded in “Step 1548-1” on page 170 is of the form 450x xxxx then replace all memory DIMMS on processor card 4 at location U0.1-P1-C4-Mn (n equals 1 to 8), if not recorded in “Step 1548-1” on page 170. v Service processor/PCI backplane at location U0.1-P2, if not recorded in “Step 1548-1”...
Page 192: Map 1549: Attention Problem Isolation
MAP 1549: Attention Problem Isolation Step 1549-1 Record the error code and the location code(s) that sent you to this MAP. Step 1549-2 Turn off the power. Step 1549-3 Examine the following table and locate the error code that sent you to this MAP to determine your next step.
Page 193 Step 1549-7 Have all the cards listed in “Step 1549-4” on page 172 been replaced? Go to “Step 1549-2” on page 172. Go to “Step 1549-28” on page 175. Step 1549-8 Replace the following cards, if present, one at a time: v First location code item recorded, if any, in “Step 1549-1”...
Page 194 Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 1549-15.” Step 1549-15 Have all the cards listed in “Step 1549-12” on page 173 been replaced? Go to “Step 1549-2”...
Page 195 The card just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 1549-23.” Step 1549-23 Have all the cards listed in “Step 1549-20” on page 174 been replaced? Go to “Step 1549-2”...
Page 196 Step 1549-32 Call for support. This ends the procedure. EserverpSeries 650 Service Guide...
Page 197: Map 154A: I2C Bus Problem Isolation
MAP 154A: I2C Bus Problem Isolation Step 154A-1 Record the error code, location code(s) and word 13 that sent you to this MAP. Step 154A-2 Turn off the power. Step 154A-3 Examine the following table and locate the error code that sent you to this MAP to determine your next step.
Page 198 Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 154A-7.” Step 154A-7 Have all the cards listed in “Step 154A-4” on page 177 been replaced? Go to “Step 154A-2”...
Page 199 The card just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 154A-17.” Step 154A-17 Turn off the power. Step 154A-18 Call for support.
Page 200 Step 154A-29 Turn on the power. Step 154A-30 Did the system stop with the same error code as recorded in “Step 154A-1” on page 177? The card just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 201: Map 154B: Insufficient Hardware Resources Problem Isolation
MAP 154B: Insufficient Hardware Resources Problem Isolation Step 154B-1 Record the error code, location code(s) and word 13 that sent you to this MAP. Step 154B-2 Turn off the power. Step 154B-3 Make sure the power is off on the base system drawer. Step 154B-4 Attention: Before replacing any parts examine the base system drawer for violation of any of the...
Page 202: Map 154C: Spcn Cable Problem Isolation
Go to “Step 154B-8.” Step 154B-8 Turn off the power. Step 154B-9 Ensure that the power is off on the base system drawer. Step 154B-10 Attention: Before replacing the processor backplane, call for support. Replace the processor backplane at U0.1-P1. Step 154B-11 Turn on the power.
Page 203 Word 13 value Action A782 xxxx 1. Trace the SPCN cable attached to U0.1-P2/Q12 of the base system drawer back to an attached I/O drawer connector U0.dd-P1/Q4 (U0.dd-P1/Q5). 2. Trace the SPCN cable attached to connector U0.dd-P1/Q5 (U0.dd-P1/Q6) of this I/O drawer back to an attached I/O drawer connector U0.dd-P1/Q4 (U0.dd-P1/Q5).
Page 204 The SPCN cable just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems. If an I/O drawer will not power on, go to “Map 1522: Cannot Power On the I/O Drawer” on page 127.
Page 205: Chapter 4. Checkpoints
Chapter 4. Checkpoints Checkpoints display on the media subsystem operator panel and the virtual terminal while the system is powering on and going through the initial program load (IPL). This chapter explains the IPL flow of the system and provides a table that lists checkpoints that you might see in the media subsystem operator panel and in a virtual terminal window on the HMC.
Page 206 At phase 3, a system processor takes over control and continues initializing partition resources. During this phase, checkpoints in the form Exxx are displayed. E105, the last checkpoint in this phase, indicates that control is being passed to the operating system boot program. v Phase 4: Operating System Boot When the operating system starts to boot, checkpoints in the form 0xxx and 2xxx are displayed.
Page 207 The following table outlines the IPL phases from power-on to the operating system login prompt, matching the phases to corresponding operator-panel checkpoints for a typical partition boot. Also listed are the approximate boot times for each phase, along with their dependencies for each phase. Note: The following table lists the major checkpoints only.
Page 208 Checkpoints enable users and service personnel to know what the server is doing, with some detail, as it initializes. These checkpoints are not intended to be error indicators, but in some cases a server could hang at one of the checkpoints without displaying an 8-character error code. It is for these hang conditions, only, that any action should be taken with respect to checkpoints.
Page 209: Service Processor Checkpoints
Service Processor Checkpoints Service processor checkpoints are in the range 8xxx to Bxxx. The message OK indicates successful service processor testing and initialization. Firmware checkpoints are listed in “Firmware Checkpoints” on page 196. Note: A spinning (or twirling) slash displays in the upper-right corner of the operator panel display while some checkpoints are being displayed.
Page 210 Table 1. Service Processor Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU 9021 Service processor state set to standby See note 1 on page 194. 9022 Service processor state set to IPL See note 1 on page 194. 9023 Service processor state set to runtime See note 1 on page 194.
Page 211 Table 1. Service Processor Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU 9104 Waiting for SPCN VPD collection to be See note 1 on page 194. completed 9105 Load IPL LIDs See note 1 on page 194. 9106 Initialize MOPs See note 1 on page 194.
Page 212 Table 1. Service Processor Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU 9300 Logic BIST See note 1 on page 194. 9301 Scanned ABIST See note 1 on page 194. 9302 Dedicated ABIST See note 1 on page 194. 9303 Dedicated ABIST array fuse repair See note 1 on page 194.
Page 213 Table 1. Service Processor Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU 99FD Service processor receiving firmware See note 3 on page 194. update module Attention: This checkpoint may stay in the operator panel for some period of time during a firmware update or hypervisor dump with no indication of activity.
Page 214 Table 1. Service Processor Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU A810-A8FF Scan log dump in progress Informational message. (See “Scan Log Dump Policy” on page 484.) The last two characters of the checkpoints will change as the scan log dump progresses.
Page 215 a. Check the modem, modem cable, and serial port for loose or unconnected cables. Reset the service processor using the pinhole reset switch on the system’s operator panel. b. If the hang repeats, check with service support to see if there is a firmware update that fixes the problem.
Page 216: Firmware Checkpoints
Firmware Checkpoints Firmware uses checkpoints (progress codes) in the range of Exxx to EFFF. These checkpoints occur during system startup and can be useful in diagnosing certain problems. Service Processor checkpoints are listed in “Service Processor Checkpoints” on page 189. If you have a checkpoint with no location code associated with it, see “Determining the Location Code”...
Page 217 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E139 Create node aliases and system aliases Go to “MAP 1540: Problem Isolation Procedures” on page 140. E13A Create packages node Go to “MAP 1540: Problem Isolation Procedures” on page 140. E140 Operating system load See “Boot Problems”...
Page 218 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E174 Establishing host connection If the system is not connected to an active network, or if the target server is inaccessible (which can result from incorrect IP parameters being specified), the system still attempts to boot and because time-out durations are necessarily long to accommodate retries, the system...
Page 219 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E1A1 User requested boot to open firmware Go to “MAP 1540: Problem Isolation prompt via keyboard entry Procedures” on page 140. E1A2 User requested boot using default service Go to “MAP 1540: Problem Isolation mode boot list via keyboard entry Procedures”...
Page 220 3. Check the serial connection between the HMC and the managed system. 4. Reboot the HMC. 5. There may be a hardware problem with the HMC. Refer to the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590 6.
Page 221 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E1D3 Create SCSI block device node (SD) Go to “MAP 1540: Problem Isolation Procedures” on page 140. E1D4 Create SCSI byte device node (ST) Go to “MAP 1540: Problem Isolation Procedures”...
Page 222 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E1F4 End self-test sequence on boot devices; Go to “MAP 1542: I/O Problem Isolation” on begin SMS. page 144. E1F5 Build boot device list Go to “MAP 1542: I/O Problem Isolation” on page 144.
Page 223 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E440 Validate NVRAM, initialize partitions as 1. Check for system firmware updates. needed 2. Replace the service processor/PCI backplane, Location: U0.1-P2. 3. Call service support. E441 Generate /options node NVRAM 1.
Page 224 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E507 I/O hub assignment 1. Check for system firmware updates. 2. Replace the RIO adapter specified by the location code. 3. Go to “MAP 1542: I/O Problem Isolation” on page 144. E508 Begin initializing I/O hubs 1.
Page 225 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E522 Set up miscellaneous registers for the 1. Check for system firmware updates. current I/O hub 2. Replace the RIO adapter specified by the location code. 3. Go to “MAP 1542: I/O Problem Isolation”...
Page 226 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E528 Begin search for the next available I/O 1. Check the RIO cable specified by the drawer from a current RIO port location code. If the location code specifies an I/O subsystem or its RIO interface, check the RIO cables going into and out of the I/O subsystem.
Page 227 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E52A Search for the next available I/O drawer 1. Check the RIO cable specified by the from a current RIO port location code. If the location code specifies an I/O subsystem or its RIO interface, check the RIO cables going into and out of the I/O subsystem.
Page 228 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E52D Disable the anynode mode 1. If the location code associated with this checkpoint specifies a PCI adapter card, replace the adapter card. 2. Replace the I/O subsytem backplane to which the RIO cable specified by the location code is attached.
Page 229 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E532 RIO cable detected; enable the I/O hub port 1. Replace the RIO cable specified by the location code. 2. Replace the RIO connector card in the processor subsystem to which the failing I/O subsystem is attached.
Page 230 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E534 Get the node ID of the node on the other 1. This error code may indicate that the end of the RIO cable RIO cables are not properly connected to the I/O subsystems.
Page 231 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E537 Configuring the I/O subsystem 1. Replace the RIO cable specified by the location code. 2. Replace the RIO connector card in the processor subsystem to which the failing I/O subsystem is attached. 3.
Page 232 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E53B End of looking for next node port Check for system firmware updates. 2. Go to “MAP 1542: I/O Problem Isolation” on page 144. E53C End of looking for next RIO hub port Check for system firmware updates.
Page 233 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E544 Enable the I/O ports 1. Replace the RIO cable specified by the location code. 2. Replace the RIO connector card (location: U0.dd-P1.1) in the failing I/O subsystem. This is the I/O subsystem to which the cable replaced in step 1 is attached.
Page 234 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E547 Set up the I/O interface chip routing table 1. Replace the RIO cable specified by the location code. 2. Replace the RIO connector card (location: U0.dd-P1.1) in the failing I/O subsystem.
Page 235 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E54A Configure the I/O drawer 1. Check the RIO cable specified by the location code. If the location code specifies an I/O subsystem or its RIO connector card, check the RIO cables going into and out of the I/O subsystem.
Page 236 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E550 Begin to initialize I/O interface chip If the location code associated with this checkpoint is either U0.1–P2 or U0.1–P1–H1, do the following: 1. Replace the RIO adapter in the processor subsystem.
Page 237 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E553 Set up the I/O interface chip base address If the location code associated with this checkpoint is either U0.1–P2 or U0.1–P1–H1, do the following: 1. Replace the RIO adapter in the processor subsystem.
Page 238 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E556 Set up and initialize I/O interface chips If the location code associated with this under current I/O interface chip checkpoint is either U0.1–P2 or U0.1–P1–H1, do the following: 1.
Page 239 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E562 Set up I/O interface chip registers If the location code associated with this checkpoint is either U0.1–P2 or U0.1–P1–H1, do the following: 1. Replace the RIO adapter in the processor subsystem.
Page 240 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E565 Set up I/O interface chip registers If the location code associated with this checkpoint is either U0.1–P2 or U0.1–P1–H1, do the following: 1. Replace the RIO adapter in the processor subsystem.
Page 241 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E568 Set up the external interrupt vector register If the location code associated with this checkpoint is either U0.1–P2 or U0.1–P1–H1, do the following: 1. Replace the RIO adapter in the processor subsystem.
Page 242 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E56B Set up I/O interface chip registers If the location code associated with this checkpoint is either U0.1–P2 or U0.1–P1–H1, do the following: 1. Replace the RIO adapter in the processor subsystem.
Page 243 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E56E Begin initializing the service processor If the location code associated with this control chip checkpoint is either U0.1–P2 or U0.1–P1–H1, do the following: 1. Replace the RIO adapter in the processor subsystem.
Page 244 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E580 Begin initializing the EADS module 1. Check for system firmware updates. 2. Replace the RIO connector card (location: U0.dd-P1.1) specified by the location code. 3. If the location code associated with this checkpoint specifies a PCI adapter card, replace the adapter card.
Page 245 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E583 Running BIST on the current EADS 1. Check for system firmware updates. 2. Replace the RIO connector card (location: U0.dd-P1.1) in the failing I/O subsystem specified by the location code.
Page 246 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E587 Set up EADS BIST 1. Check for system firmware updates. 2. Replace the RIO connector card (location: U0.dd-P1.1) in the failing I/O subsystem specified by the location code. 3.
Page 247 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E58A Set up EADS function registers 1. Check for system firmware updates. 2. Replace the RIO connector card (location: U0.dd-P1.1) in the failing I/O subsystem specified by the location code.
Page 248 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E58D Set up EADS function registers 1. Check for system firmware updates. 2. Replace the RIO connector card (location: U0.dd-P1.1) in the failing I/O subsystem specified by the location code.
Page 249 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E590 Set up EADS function registers 1. Check for system firmware updates. 2. Replace the RIO connector card (location: U0.dd-P1.1) in the failing I/O subsystem specified by the location code.
Page 250 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E593 Set up EADS function registers 1. Check for system firmware updates. 2. Replace the RIO connector card (location: U0.dd-P1.1) in the failing I/O subsystem specified by the location code.
Page 251 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E59E End of walking bus of current EADS 1. Check for system firmware updates. 2. Replace the RIO connector card (location: U0.dd-P1.1) in the failing I/O subsystem specified by the location code.
Page 252 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E5E4 Activate slave processors 1. Check for system firmware updates. 2. Go to “MAP 1542: I/O Problem Isolation” on page 144. E5E5 Initialize the hypervisor, phase 2 1. Check for system firmware updates. 2.
Page 253 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E605 SSA PCI adapter BIST has completed Replace the adapter. successfully but subsequent POSTS have failed. E60E SSA PCI open firmware about to exit (no Replace the adapter. stack corruption). E60F SSA PCI open firmware has run Replace the adapter.
Page 254 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E7EE Delaying while waiting for power subsystem 1. Check for system firmware updates. VPD collection to be completed; 2. Call service support. informational only E7FF Successful end of VPD creation Informational message.
Page 255 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E854 Start collecting cable IDs 1. Check the SPCN and RIO cabling to the I/O subystems. 2. Remove, then reapply power to the system. 3. Go to “MAP 1542: I/O Problem Isolation”...
Page 256 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E8D1 Initializing interface/special memory access 1. Check for system firmware updates. 2. Call service support. E900 The system firmware is in the recoverable Go to “MAP 1540: Problem Isolation non-maskable interrupt code.
Page 257: Boot Problems
Boot Problems Attention: If the system is running partitions from partition standby (LPAR), the following procedure addresses the problem in which one partition will not boot while other partitions boot successfully and run the operating system successfully. This procedure also addresses the problem in which a system does not boot to a full system partition. All of the system’s resources are available to the diagnostics;...
Page 258 b. If the intended boot device is not correctly listed in the boot sequence, add it to the boot sequence using the SMS menus. If the device can be added to the boot sequence, reboot the partition. If the intended boot device cannot be added to the boot list, ask the customer or system administrator to verify that the device you are trying to boot from is assigned to the correct partition.
Page 259 isolated. When the failing devices is isolated, replace it and then go to ″MAP 410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems. If the CD-ROM is not present, turn off the power and disconnect the CD-ROM. Reconnect one of the SCSI devices on the same bus.
Page 260 EserverpSeries 650 Service Guide...
Page 261: Chapter 5. Error Code To Fru Index
Chapter 5. Error Code to FRU Index The Error Code to FRU Index lists fault symptoms and possible causes. The most likely cause is listed first. Use this index to help you decide which FRUs to replace when servicing the system. Attention: If you replace FRUs or perform an action on an I/O subsystem and the problem is still not corrected, go to “MAP 1542: I/O Problem Isolation”...
Page 262: Confirming Initial Error Code
e. Select option 6. Verify that the state changes to currently disabled. Disabling fast system boot automatically enables slow boot. f. Select Option 98 to exit the system power control menu. g. Use the HMC to power up the system to the SMS menus in a full system partition. 3.
Page 263: Four-Character Checkpoints
error codes (which is forward in time from the earliest time stamp to the latest) until either the problem is fixed, you reach the error code that was first reported, or you are at the top of the list. If there are no hardware error codes in the form 450x yyyy, 460x yyyy, or 4B2x yyyy that occurred just prior to the 406x 0EAy error, look for the last firmware checkpoint of the form Exxx before the 406x 0EAy error.
Page 264 FRU identify LED to be flashed. See the ″Hardware Service Functions″ section of the ″Service Focal Point″ chapter of the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590, for instructions on activating and deactivating a FRU identify LED.
Page 265: Checkpoints And Error Codes Index
Checkpoints and Error Codes Index The table below is an index to the checkpoints or error codes that you may receive to help diagnose a failure. Locate the code you received and follow the instructions to determine your next step. Table 3.
Page 266 Table 3. Checkpoints and Error Codes Index (continued) 8-Digit Error Code What You Should Do 4-Digit Checkpoint 4xxx xxxx Service Processor Error Codes 1. Is the system powered up? Go to step 2 below. Go to step 4 below. 2. Find the error code in the service processor error log and check the value of word 13. Go to 3 below.
Page 267 Table 3. Checkpoints and Error Codes Index (continued) 8-Digit Error Code What You Should Do 4-Digit Checkpoint 8xxx Service Processor Checkpoints 9xxx Go to “Service Processor Checkpoints” on page 189 for more information on these Axxx checkpoints. Bxxx A1FD 000x The system has entered recovery mode.
Page 268: Operator Panel Error Codes
Operator Panel Error Codes Attention: If you replace FRUs or perform an action on an I/O subsystem and the problem is still not corrected, go to “MAP 1542: I/O Problem Isolation” on page 144 unless you were already directed to any MAP 154x by the error code.
Page 269: Spcn Error Codes
SPCN Error Codes Attention: If you replace FRUs or perform an action on an I/O subsystem and the problem is still not corrected, go to “MAP 1542: I/O Problem Isolation” on page 144 unless you were already directed to any MAP 154x by the error code.
Page 270 Table 4. SPCN Error Codes for the processor subsystem (System Unit) (continued) Error Code Description Action/ Possible Failing FRU 1011 1516 Power supply 1 fan missing 1. Processor subsystem power supply fan 1 Location: U0.1-F1 2. Service processor/PCI backplane Location: U0.1-P2 1011 1520 Power supply 2 power source failure 1.
Page 271 Table 4. SPCN Error Codes for the processor subsystem (System Unit) (continued) Error Code Description Action/ Possible Failing FRU 1011 2612 Optical converter fault Service processor/PCI backplane Location: U0.1-P2 1011 2613 100v fault Service processor/PCI backplane Location: U0.1-P2 1011 3100 I2C controller fault Service processor/PCI backplane Location: U0.1-P2 1011 3104 3104 I2C bus 4 failure;...
Page 272 Table 4. SPCN Error Codes for the processor subsystem (System Unit) (continued) Error Code Description Action/ Possible Failing FRU 1011 7630 Power supply V1 fan failure 1. Fan Location: U0.1-F1 2. Power supply V1 Location: U0.1-V1 1011 7631 Power supply V1 fan missing Location: U0.1-F1 1011 7640 Power supply V2 fan missing 1.
Page 273 Table 4. SPCN Error Codes for the processor subsystem (System Unit) (continued) Error Code Description Action/ Possible Failing FRU 1011 840A VPD +5 stuck high Go to “MAP 1540: Problem Isolation Procedures” on page 140. 1011 840B VPD access Go to “MAP 1540: Problem Isolation Procedures”...
Page 274 Table 4. SPCN Error Codes for the processor subsystem (System Unit) (continued) Error Code Description Action/ Possible Failing FRU 1011 9280 SPCN interface failure 1. Check the SPCN cables connected to the processor subsystem drawer. 2. Check for system firmware updates. Apply any available updates.
Page 275 Attention: If you replace FRUs or perform an action on an I/O subsystem and the problem is still not corrected, go to “MAP 1542: I/O Problem Isolation” on page 144 unless you were already directed to any MAP 154x by the error code. Otherwise call support if the action(s) for an error code do not resolve the problem.
Page 276 Table 5. SPCN Error Codes for I/O Subsystems (continued) Error Code Description Action/ Possible Failing FRU 1nn1 1516 Power supply 1 fan missing (7311 Model D10 1. I/O subsystem power supply 1 I/O Subsystem only) Location: U0.dd-V1 2. I/O subsystem backplane Location: U0.dd-P1 See the notices on page 255 for “dd”...
Page 277 Table 5. SPCN Error Codes for I/O Subsystems (continued) Error Code Description Action/ Possible Failing FRU 1nn1 1527 Power supply 2 thermal fault 1. Check for obstructions to the air flow around the I/O subsystem. 2. I/O subsystem power supply 2, Location: U0.dd-V2 3.
Page 278 Table 5. SPCN Error Codes for I/O Subsystems (continued) Error Code Description Action/ Possible Failing FRU 1nn1 2606 Power good 2.5 V fault I/O subsystem backplane, Location: U0.dd-P1 See the notices on page 255 for “dd” values. 1nn1 3100 I2C controller fault I/O subsystem backplane, Location: U0.dd-P1 See the notices on page 255 for “dd”...
Page 279 Table 5. SPCN Error Codes for I/O Subsystems (continued) Error Code Description Action/ Possible Failing FRU 1nn1 7610 Blower 1 fault (7311 Model D20 I/O Subsystem Blower 1, only) Location: U0.dd-F1 See the notices on page 255 for “dd” values. 1nn1 7611 Blower 1 missing (7311 Model D20 I/O Blower 1, Subsystem only)
Page 280 Table 5. SPCN Error Codes for I/O Subsystems (continued) Error Code Description Action/ Possible Failing FRU 1nn1 840E I/O type mismatch 1. Check cabling 2. Set the I/O type. See Power Control Network Utilities Menu on page 493. 3. I/O subsystem backplane Location: U0.dd-P1 See the notices on page 255 for “dd”...
Page 281: Firmware/Post Error Codes
Firmware/POST Error Codes Attention: If you replace FRUs or perform an action on an I/O subsystem and the problem is still not corrected, go to “MAP 1542: I/O Problem Isolation” on page 144 unless you were already directed to any MAP 154x by the error code.
Page 282 Error Code Description Action/ Possible Failing FRU 20D0 0010 Self test failed on device, can’t locate package Contact your next level of support for assistance. 20D0 0011 Firmware RTAS attempt to allocate memory Contact your next level of support for failed.
Page 283 Error Code Description Action/ Possible Failing FRU 20D0 0A07 Error initializing interface/operating system 1. Check for system firmware updates. Apply access update if available. 2. Contact your next level of support for assistance. 20D0 0A08 Error initializing interface/client_interface 1. Check for system firmware updates. Apply access update if available.
Page 284 Error Code Description Action/ Possible Failing FRU 20D0 0A12 Error initializing interface/hot-plug access 1. Check for system firmware updates. Apply update if available. 2. Contact your next level of support for assistance. 20D0 0A13 Error initializing interface/log access 1. Check for system firmware updates. Apply update if available.
Page 285 Error Code Description Action/ Possible Failing FRU 20D0 9003 Subsystem serial number information not found 1. If the location code starts with U0.1, the in VPD problem is in the system VPD module on the operator panel. Replace the operator panel;...
Page 286 Error Code Description Action/ Possible Failing FRU 20D0 9008 Invalid subsystem serial number found in VPD 1. If the location code starts with U0.1, the problem is in the system VPD module on the operator panel. Replace the operator panel; do not swap the old VPD module onto the new operator panel.
Page 287 Error Code Description Action/ Possible Failing FRU 20D1 0009 Missing or invalid subsystem serial number 1. Check for system firmware updates. Apply update if available. 2. If a location code is shown with this error code, replace the part at that location. 3.
Page 288 Error Code Description Action/ Possible Failing FRU 20D1 0011 A recovery operation on an internal I/O control If the system is partitioned, perform a hard chip failed reset on the partition that owns the drawer specified by the location code reported with the error.
Page 289 Error Code Description Action/ Possible Failing FRU 20EE 0007 Keyboard not found 1. Plug in the keyboard. 2. Replace the keyboard. 3. If the keyboard is plugged into the processor subsystem, replace the service processor/PCI backplane. 4. If the keyboard is plugged into a USB card, replace the USB card.
Page 290 Error Code Description Action/ Possible Failing FRU 20EE 000C Pointer to the operating system found in Values normally found in non-volatile storage non-volatile storage. that point to the location of an operating system were not found. This can happen for two reasons: v Either your operating system doesn’t support storing the values...
Page 291 Error Code Description Action/ Possible Failing FRU 20EE 0011 Unable to execute the root-lpar-vpd vpd 1. Verify that the system is in LPAR mode, method and reboot the system. 2. Reflash the system with the latest level of system firmware. 3.
Page 292 20EE 0100 Fcode resident on an I/O adapter is not Informational message. The adapter’s Fcode supported on this system driver is not supported on this system. IBM may produce a compatible driver in the future, but does not guarantee one. Additional information may be available from service support.
Page 293 Error Code Description Action/ Possible Failing FRU 20FF 0022 Invalid VPD (84/90 tag length is more than 2KB Replace the part specified by the location - large resource tag) code. 2. If no location code is shown with the error code, call service support.
Page 294 Error Code Description Action/ Possible Failing FRU 20FF 00B0 Invalid VPD (the FG keyword is not found for a Replace the part specified by the location processor bus connector card) code. 2. If no location code is shown with the error code, call service support.
Page 295 Error Code Description Action/ Possible Failing FRU 21A0 0003 SCSI DASD: send diagnostic failed; sense data Before replacing any system components, refer available to the Action under error code 21A0 0001. Replace the SCSI device. 21A0 0004 SCSI DASD: send diagnostic failed - devofl Before replacing any system components, refer command to the Action under error code...
Page 296 Error Code Description Action/ Possible Failing FRU 21ED 0004 SCSI changer: send diagnostic failed - devofl Before replacing any system components, refer command to the Action under error code 21A0 0001. Replace the SCSI device. 21EE 0001 Undetermined SCSI device: test unit ready Before replacing any system components, refer failed;...
Page 297 Error Code Description Action/ Possible Failing FRU 21F2 0001 SCSI read/write optical device: test unit ready Before replacing any system components, refer failed; hardware error to the Action under error code 21A0 0001. 1. Replace the SCSI device. 2. Replace the SCSI cable. 3.
Page 298 Error Code Description Action/ Possible Failing FRU 25A8 0xxx NVRAM problems Errors reported against NVRAM can be caused by low battery voltage and (more rarely) power outages that occur during normal system usage. With the exception of the 25A8 0000 error, these errors are warnings that the NVRAM data content had to be reestablished and do not require any FRU replacement...
Page 299 Error Code Description Action/ Possible Failing FRU 25A8 0998 NVRAMRC script evaluation error - command line execution error Action: Execution of a command line within the nvram configuration variable “nvramrc” (script) resulted in a “throw” being executed. This script can be modified by the system firmware SMS utilities, the operating system, PCI adapter ROM code or utility, or an operator (via the open firmware script editing command “nvedit”).
Page 300 Error Code Description Action/ Possible Failing FRU 2601 0000 Boot failed because the RIO cables, or the 1. Check both ends of the RIO cable specified power subsystem cables, are not routed in the location code that appears with this correctly to the I/O subsystems error code.
Page 301 Error Code Description Action/ Possible Failing FRU 2602 0002 Invalid PCI adapter device ID 1. Move adapter to another slot (behind a different PCI bus). 2. Check for available firmware updates for adapter. Apply update if available. 3. Run AIX diagnostics on adapter. Replace if indicated.
Page 302 Error Code Description Action/ Possible Failing FRU 2602 0010 Description: PCI probe error, bridge in freeze state Action: If the location code identifies a slot or PCI adapter, do the following: 1. Check for system firmware updates. Apply if available. 2.
Page 303 Error Code Description Action/ Possible Failing FRU 2602 0010 Power down the system. See “Non-Hot-Pluggable PCI Adapter Removal and Replacement” (continued) on page 558 for instructions on reseating the card. If reseating the adapter fixes the problem, go to ″MAP 0410: Repair Checkout″ in the Eserver pSeries Diagnostic Information for Multiple Bus Systems manual.
Page 304 Error Code Description Action/ Possible Failing FRU 2602 0Fxy PCI bridge chip failure Replace the I/O planar specified by the location code. The I/IO planar may be in the CEC or in an external I/O drawer. The problem is associated with bridge ″y″ in 2680 0Axy MX-PCI Bridge BIST Failure I/O subsystem ″x″.
Page 305 Error Code Description Action/ Possible Failing FRU 2803 0004 RTC operating mode parameters (eg. data 1. Set time and date. mode) changed 2. Refer to Action under error code 2803 0001. 2803 0005 RTC battery error Replace the service processor/PCI backplane. Location: U0.1-P2 Note: Passwords, time, and date need to be reset.
Page 306 Error Code Description Action/ Possible Failing FRU 2B20 0042 Unknown processor card Remove the unknown/unsupported processor card. 2B20 8880 Unrecoverable system unit error If Linux is the only operating system on the failing system, call service support. If AIX is available, and the system is powered down, replace the FRU indicated in the service processor error log entry.
Page 307 Error Code Description Action/ Possible Failing FRU 2B2x 00EE An exception error has been reported on a The type of interrupt that caused the exception global processor is specified by the x as follows: Unknown interrupt System reset interrupt (SRI) Machine check interrupt (MCI) Data storage interrupt (DSI) Instruction storage interrupt (ISI)
Page 308 Error Code Description Action/ Possible Failing FRU 2Dmm mhhh A processor’s timebase enable signal is stuck 1. Replace the service processor/PCI disabled backplane, location: U0.1-P2. 2. hhh indicates the failing processor. Replace the processor card that contains the failing processor according to the following table: v hhh = 0 - 7: U0.1-C1 v hhh = 8-15: U0.1-C2 v hhh = 16-23: U0.1-C3...
Page 309: Service Processor Error Codes
Service Processor Error Codes Attention: Follow the procedure defined in “Checkpoints and Error Codes Index” on page 245. If you replace FRUs or perform an action on an I/O subsystem and the problem is still not corrected, go to “MAP 1542: I/O Problem Isolation”...
Page 310 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4064 0010 Memory DIMM J0A, processor card 1 Memory DIMM Location: U0.1-P1-C1.M3 4064 0011 Memory DIMM J1A, processor card 1 Memory DIMM Location: U0.1-P1-C1.M8 4064 0012 Memory DIMM J2A, processor card 1 Memory DIMM Location: U0.1-P1-C1.M1 4064 0013 Memory DIMM J3A, processor card 1...
Page 311 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4064 0027 Memory DIMM J3C, processor card 3 Memory DIMM Location: U0.1-P1-C3.M5 4064 0028 Memory DIMM J0A, processor card 4 Memory DIMM Location: U0.1-P1-C4.M3 4064 0029 Memory DIMM J1A, processor card 4 Memory DIMM Location: U0.1-P1-C4.M8 4064 002A Memory DIMM J2A, processor card 4...
Page 312 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4064 00B7 Insufficient hardware resources were detected Go to “MAP 1540: Problem Isolation to continue IPL of the system after processor Procedures” on page 140. subsystem testing and initialization was completed 4064 00D1 Informational message Informational message...
Page 313 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4064 0A04 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 2 firmware, may be able to correct this problem without replacing hardware.
Page 314 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4064 0A06 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 3 firmware, may be able to correct this problem without replacing hardware.
Page 315 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4064 0B03 Problem with RIO interface (I/O slot 0, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H1 and the I/O subsystems.
Page 316 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4064 0B32 Problem with RIO interface (I/O slot 3, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H2.1 and the I/O subsystems.
Page 317 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4064 0BF3 I/O hub 3, I/O port x (problem outside the 1. Check for system firmware updates. system unit 2. Check the cabling between the RIO interface card at U0.1-P1-H2.1 and the I/O subsystems.
Page 318 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4064 0EB2 Attention line 1 stuck fault Go to “MAP 1540: Problem Isolation Procedures” on page 140. 4064 0EB3 Attention line 2 stuck fault Go to “MAP 1540: Problem Isolation Procedures”...
Page 319 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4065 0002 System backplane fault 1. Ensure processor cards are seated and cables are connected securely. System backplane Location: U0.1-P1 4065 0003 Scan interface basic assurance tests detected 1.
Page 320 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4065 0016 Memory DIMM J2C, processor card 1 Memory DIMM Location: U0.1-P1-C1.M2 4065 0017 Memory DIMM J3C, processor card 1 Memory DIMM Location: U0.1-P1-C1.M5 4065 0018 Memory DIMM J0A, processor card 2 Memory DIMM Location: U0.1-P1-C2.M3 4065 0019 Memory DIMM J1A, processor card 2...
Page 321 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4065 002D Memory DIMM J1C, processor card 4 Memory DIMM Location: U0.1-P1-C4.M7 4065 002E Memory DIMM J2C, processor card 4 Memory DIMM Location: U0.1-P1-C4.M2 4065 002F Memory DIMM J3C, processor card 4 Memory DIMM Location: U0.1-P1-C4.M5 4065 0030 NUMA directory DIMM card 0...
Page 322 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4065 0120 Memory extender 0 on processor card 4 Processor card, Location: U0.1-P1-C4 4065 0121 Memory extender 2 on processor card 4 Processor card, Location: U0.1-P1-C4 4065 0130 Memory extender 0 on processor card 3 Processor card, Location: U0.1-P1-C3...
Page 323 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4065 0A04 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 2 firmware, may be able to correct this problem without replacing hardware.
Page 324 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4065 0A06 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 3 firmware, may be able to correct this problem without replacing hardware.
Page 325 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4065 0B03 Problem with RIO interface (I/O slot 0, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H1 and the I/O subsystems.
Page 326 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4065 0B32 Problem with RIO interface (I/O slot 3, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H2.1 and the I/O subsystems.
Page 327 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4065 0BF3 I/O hub 3, I/O port x (problem outside the 1. Check for system firmware updates. system unit 2. Check the cabling between the RIO interface card at U0.1-P1-H2.1 and the I/O subsystems.
Page 328 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4065 0EB2 Attention line 1 stuck fault Go to “MAP 1540: Problem Isolation Procedures” on page 140. 4065 0EB3 Attention line 2 stuck fault Go to “MAP 1540: Problem Isolation Procedures”...
Page 329 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4066 0002 System backplane fault 1. Ensure processor cards are seated and cables are connected securely. System backplane Location: U0.1-P1 4066 0003 Scan interface basic assurance tests detected 1.
Page 330 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4066 0016 Memory DIMM J2C, processor card 1 Memory DIMM Location: U0.1-P1-C1.M2 4066 0017 Memory DIMM J3C, processor card 1 Memory DIMM Location: U0.1-P1-C1.M5 4066 0018 Memory DIMM J0A, processor card 2 Memory DIMM Location: U0.1-P1-C2.M3 4066 0019 Memory DIMM J1A, processor card 2...
Page 331 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4066 002D Memory DIMM J1C, processor card 4 Memory DIMM Location: U0.1-P1-C4.M7 4066 002E Memory DIMM J2C, processor card 4 Memory DIMM Location: U0.1-P1-C4.M2 4066 002F Memory DIMM J3C, processor card 4 Memory DIMM Location: U0.1-P1-C4.M5 4066 0030 NUMA directory DIMM card 0...
Page 332 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4066 0120 Memory extender 0 on processor card 4 Processor card, Location: U0.1-P1-C4 4066 0121 Memory extender 2 on processor card 4 Processor card, Location: U0.1-P1-C4 4066 0130 Memory extender 0 on processor card 3 Processor card, Location: U0.1-P1-C3...
Page 333 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4066 0A04 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 2 firmware, may be able to correct this problem without replacing hardware.
Page 334 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4066 0A06 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 3 firmware, may be able to correct this problem without replacing hardware.
Page 335 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4066 0B03 Problem with RIO interface (I/O slot 0, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H1 and the I/O subsystems.
Page 336 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4066 0B32 Problem with RIO interface (I/O slot 3, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H2.1 and the I/O subsystems.
Page 337 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4066 0BF3 I/O hub 3, I/O port x (problem outside the 1. Check for system firmware updates. system unit 2. Check the cabling between the RIO interface card at U0.1-P1-H2.1 and the I/O subsystems.
Page 338 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4066 0EB2 Attention line 1 stuck fault Go to “MAP 1540: Problem Isolation Procedures” on page 140. 4066 0EB3 Attention line 2 stuck fault Go to “MAP 1540: Problem Isolation Procedures”...
Page 339 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4067 0002 System backplane fault 1. Ensure processor cards are seated and cables are connected securely. System backplane Location: U0.1-P1 4067 0003 Scan interface basic assurance tests detected 1.
Page 340 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4067 0016 Memory DIMM J2C, processor card 1 Memory DIMM Location: U0.1-P1-C1.M2 4067 0017 Memory DIMM J3C, processor card 1 Memory DIMM Location: U0.1-P1-C1.M5 4067 0018 Memory DIMM J0A, processor card 2 Memory DIMM Location: U0.1-P1-C2.M3 4067 0019 Memory DIMM J1A, processor card 2...
Page 341 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4067 002D Memory DIMM J1C, processor card 4 Memory DIMM Location: U0.1-P1-C4.M7 4067 002E Memory DIMM J2C, processor card 4 Memory DIMM Location: U0.1-P1-C4.M2 4067 002F Memory DIMM J3C, processor card 4 Memory DIMM Location: U0.1-P1-C4.M5 4067 0030 NUMA directory DIMM card 0...
Page 342 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4067 0120 Memory extender 0 on processor card 4 Processor card, Location: U0.1-P1-C4 4067 0121 Memory extender 2 on processor card 4 Processor card, Location: U0.1-P1-C4 4067 0130 Memory extender 0 on processor card 3 Processor card, Location: U0.1-P1-C3...
Page 343 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4067 0A04 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 2 firmware, may be able to correct this problem without replacing hardware.
Page 344 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4067 0A06 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 3 firmware, may be able to correct this problem without replacing hardware.
Page 345 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4067 0B03 Problem with RIO interface (I/O slot 0, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H1 and the I/O subsystems.
Page 346 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4067 0B32 Problem with RIO interface (I/O slot 3, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H2.1 and the I/O subsystems.
Page 347 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4067 0BF3 I/O hub 3, I/O port x (problem outside the 1. Check for system firmware updates. system unit 2. Check the cabling between the RIO interface card at U0.1-P1-H2.1 and the I/O subsystems.
Page 348 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4067 0EB2 Attention line 1 stuck fault Go to “MAP 1540: Problem Isolation Procedures” on page 140. 4067 0EB3 Attention line 2 stuck fault Go to “MAP 1540: Problem Isolation Procedures”...
Page 349 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4068 0006 Scan interface basic assurance tests detected 1. Ensure processor cards are seated and processor fault cables are connected securely. 2. Processor card Location: U0.1-P1-C4 4068 0009 Processor bus connector card 1.
Page 350 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4068 001E Memory DIMM J2C, processor card 2 Memory DIMM Location: U0.1-P1-C2.M2 4068 001F Memory DIMM J3C, processor card 2 Memory DIMM Location: U0.1-P1-C2.M5 4068 0020 Memory DIMM J0A, processor card 3 Memory DIMM Location: U0.1-P1-C3.M3 4068 0021 Memory DIMM J1A, processor card 3...
Page 351 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4068 00B0 Bus controller failure 1. Check for system firmware updates 2. Service processor/PCI backplane Location: U0.1-P2 4068 00B1 Bus controller failure 1. Check for system firmware updates 2.
Page 352 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4068 0A03 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 0 firmware, may be able to correct this problem without replacing hardware.
Page 353 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4068 0A05 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 1 firmware, may be able to correct this problem without replacing hardware.
Page 354 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4068 0B00 Problem with internal RIO interface (I/O slot 0, 1. Check for system firmware updates. I/O port 0) 2. RIO riser card, Location: U0.1-P1-H1 3. Service processor/PCI backplane, Location:U0.1-P2 4.
Page 355 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4068 0B22 Problem with RIO interface (I/O slot 2, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H2 and the I/O subsystems.
Page 356 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4068 0BF1 Problem with RIO interface (I/O slot 1, I/O hub 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H1.1 and the I/O subsystems.
Page 357 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4068 0EA1 Operating system code on main processor 1. Check for operating system code updates. 2. Call service support. 4068 0EA2 PRD code on service processor error. 1.
Page 358 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4068 0EBF Memory error 1. Reboot the system in slow mode to the SMS menus. See “Performing Slow Boot” on page 241. 2. Examine the service processor error log. a.
Page 359 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4069 000A RIO connector card 1 RIO connector card 1 Location: U0.1-P1-H1 4069 000B RIO connector extender card 1 RIO connector extender card 1 Location: U0.1-P1-H1.1 4069 000C RIO connector card 2 RIO connector card 2 Location: U0.1-P1-H2...
Page 360 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4069 0022 Memory DIMM J2A, processor card 3 Memory DIMM Location: U0.1-P1-C3.M1 4069 0023 Memory DIMM J3A, processor card 3 Memory DIMM Location: U0.1-P1-C3.M6 4069 0024 Memory DIMM J0C, processor card 3 Memory DIMM Location: U0.1-P1-C3.M4 4069 0025 Memory DIMM J1C, processor card 3...
Page 361 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4069 00B4 Processor/VPD problem detected 1. Check for system firmware updates 2. Processor card 2 Location: U0.1-P1-C2 4069 00B5 Processor/VPD problem detected 1. Check for system firmware updates 2.
Page 362 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4069 0A03 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 0 firmware, may be able to correct this problem without replacing hardware.
Page 363 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4069 0A05 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 1 firmware, may be able to correct this problem without replacing hardware.
Page 364 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4069 0B00 Problem with internal RIO interface (I/O slot 0, 1. Check for system firmware updates. I/O port 0) 2. RIO riser card, Location: U0.1-P1-H1 3. Service processor/PCI backplane, Location:U0.1-P2 4.
Page 365 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4069 0B22 Problem with RIO interface (I/O slot 2, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H2 and the I/O subsystems.
Page 366 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4069 0BF1 Problem with RIO interface (I/O slot 1, I/O hub 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H1.1 and the I/O subsystems.
Page 367 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4069 0EA1 Operating system code on main processor 1. Check for operating system code updates. 2. Call service support. 4069 0EA2 PRD code on service processor error. 1.
Page 368 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4069 0EB6 Attention line 5 stuck fault Go to “MAP 1540: Problem Isolation Procedures” on page 140. 4069 0EB7 Attention line 6 stuck fault Go to “MAP 1540: Problem Isolation Procedures”...
Page 369 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406A 0004 Scan interface basic assurance tests detected 1. Ensure processor cards are seated and processor fault cables are connected securely. 2. Processor card Location: U0.1-P1-C2 406A 0005 Scan interface basic assurance tests detected 1.
Page 370 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406A 001A Memory DIMM J2A, processor card 2 Memory DIMM Location: U0.1-P1-C2.M1 406A 001B Memory DIMM J3A, processor card 2 Memory DIMM Location: U0.1-P1-C2.M6 406A 001C Memory DIMM J0C, processor card 2 Memory DIMM Location: U0.1-P1-C2.M4 406A 001D Memory DIMM J1C, processor card 2...
Page 371 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406A 0038 NUMA directory DIMM card 1 Memory DIMM Location: U0.1-P1-C2.M9 406A 0040 NUMA directory DIMM card 3 Memory DIMM Location: U0.1-P1-C3.M9 406A 0048 NUMA directory DIMM card 2 Memory DIMM Location: U0.1-P1-C4.M9 406A 00B0 Bus controller failure...
Page 372 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406A 0A03 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 0 firmware, may be able to correct this problem without replacing hardware.
Page 373 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406A 0A05 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 1 firmware, may be able to correct this problem without replacing hardware.
Page 374 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406A 0B00 Problem with internal RIO interface (I/O slot 0, 1. Check for system firmware updates. I/O port 0) 2. RIO riser card, Location: U0.1-P1-H1 3. Service processor/PCI backplane, Location:U0.1-P2 4.
Page 375 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406A 0B22 Problem with RIO interface (I/O slot 2, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H2 and the I/O subsystems.
Page 376 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406A 0BF1 Problem with RIO interface (I/O slot 1, I/O hub 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H1.1 and the I/O subsystems.
Page 377 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406A 0EA1 Operating system code on main processor 1. Check for operating system code updates. 2. Call service support. 406A 0EA2 PRD code on service processor error. 1.
Page 378 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406A 0EBF Memory error 1. Reboot the system in slow mode to the SMS menus. See “Performing Slow Boot” on page 241. 2. Examine the service processor error log. a.
Page 379 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406B 000A RIO connector card 1 RIO connector card 1 Location: U0.1-P1-H1 406B 000B RIO connector extender card 1 RIO connector extender card 1 Location: U0.1-P1-H1.1 406B 000C RIO connector card 2 RIO connector card 2 Location: U0.1-P1-H2...
Page 380 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406B 0022 Memory DIMM J2A, processor card 3 Memory DIMM Location: U0.1-P1-C3.M1 406B 0023 Memory DIMM J3A, processor card 3 Memory DIMM Location: U0.1-P1-C3.M6 406B 0024 Memory DIMM J0C, processor card 3 Memory DIMM Location: U0.1-P1-C3.M4 406B 0025 Memory DIMM J1C, processor card 3...
Page 381 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406B 00B4 Processor/VPD problem detected 1. Check for system firmware updates 2. Processor card 2 Location: U0.1-P1-C2 406B 00B5 Processor/VPD problem detected 1. Check for system firmware updates 2.
Page 382 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406B 0A03 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 0 firmware, may be able to correct this problem without replacing hardware.
Page 383 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406B 0A05 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 1 firmware, may be able to correct this problem without replacing hardware.
Page 384 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406B 0B00 Problem with internal RIO interface (I/O slot 0, 1. Check for system firmware updates. I/O port 0) 2. RIO riser card, Location: U0.1-P1-H1 3. Service processor/PCI backplane, Location:U0.1-P2 4.
Page 385 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406B 0B22 Problem with RIO interface (I/O slot 2, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H2 and the I/O subsystems.
Page 386 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406B 0BF1 Problem with RIO interface (I/O slot 1, I/O hub 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H1.1 and the I/O subsystems.
Page 387 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406B 0EA1 Operating system code on main processor 1. Check for operating system code updates. 2. Call service support. 406B 0EA2 PRD code on service processor error. 1.
Page 388 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406B 0EBF Memory error 1. Reboot the system in slow mode to the SMS menus. See “Performing Slow Boot” on page 241. 2. Examine the service processor error log. a.
Page 389 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406C 000A RIO connector card 1 RIO connector card 1 Location: U0.1-P1-H1 406C 000B RIO connector extender card 1 RIO connector extender card 1 Location: U0.1-P1-H1.1 406C 000C RIO connector card 2 RIO connector card 2 Location: U0.1-P1-H2...
Page 390 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406C 0022 Memory DIMM J2A, processor card 3 Memory DIMM Location: U0.1-P1-C3.M1 406C 0023 Memory DIMM J3A, processor card 3 Memory DIMM Location: U0.1-P1-C3.M6 406C 0024 Memory DIMM J0C, processor card 3 Memory DIMM Location: U0.1-P1-C3.M4 406C 0025 Memory DIMM J1C, processor card 3...
Page 391 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406C 00B4 Processor/VPD problem detected 1. Check for system firmware updates 2. Processor card 2 Location: U0.1-P1-C2 406C 00B5 Processor/VPD problem detected 1. Check for system firmware updates 2.
Page 392 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406C 0A03 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 0 firmware, may be able to correct this problem without replacing hardware.
Page 393 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406C 0A05 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 1 firmware, may be able to correct this problem without replacing hardware.
Page 394 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406C 0B00 Problem with internal RIO interface (I/O slot 0, 1. Check for system firmware updates. I/O port 0) 2. RIO riser card, Location: U0.1-P1-H1 3. Service processor/PCI backplane, Location:U0.1-P2 4.
Page 395 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406C 0B22 Problem with RIO interface (I/O slot 2, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H2 and the I/O subsystems.
Page 396 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406C 0BF1 Problem with RIO interface (I/O slot 1, I/O hub 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H1.1 and the I/O subsystems.
Page 397 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406C 0EA1 Operating system code on main processor 1. Check for operating system code updates. 2. Call service support. 406C 0EA2 PRD code on service processor error. 1.
Page 398 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406C 0EBF Memory error 1. Reboot the system in slow mode to the SMS menus. See “Performing Slow Boot” on page 241. 2. Examine the service processor error log. a.
Page 399 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406D 000A RIO connector card 1 RIO connector card 1 Location: U0.1-P1-H1 406D 000B RIO connector extender card 1 RIO connector extender card 1 Location: U0.1-P1-H1.1 406D 000C RIO connector card 2 RIO connector card 2 Location: U0.1-P1-H2...
Page 400 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406D 0022 Memory DIMM J2A, processor card 3 Memory DIMM Location: U0.1-P1-C3.M1 406D 0023 Memory DIMM J3A, processor card 3 Memory DIMM Location: U0.1-P1-C3.M6 406D 0024 Memory DIMM J0C, processor card 3 Memory DIMM Location: U0.1-P1-C3.M4 406D 0025 Memory DIMM J1C, processor card 3...
Page 401 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406D 00B4 Processor/VPD problem detected 1. Check for system firmware updates 2. Processor card 2 Location: U0.1-P1-C2 406D 00B5 Processor/VPD problem detected 1. Check for system firmware updates 2.
Page 402 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406D 0A03 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 0 firmware, may be able to correct this problem without replacing hardware.
Page 403 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406D 0A05 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 1 firmware, may be able to correct this problem without replacing hardware.
Page 404 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406D 0B00 Problem with internal RIO interface (I/O slot 0, 1. Check for system firmware updates. I/O port 0) 2. RIO riser card, Location: U0.1-P1-H1 3. Service processor/PCI backplane, Location:U0.1-P2 4.
Page 405 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406D 0B22 Problem with RIO interface (I/O slot 2, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H2 and the I/O subsystems.
Page 406 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406D 0BF1 Problem with RIO interface (I/O slot 1, I/O hub 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H1.1 and the I/O subsystems.
Page 407 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406D 0EA1 Operating system code on main processor 1. Check for operating system code updates. 2. Call service support. 406D 0EA2 PRD code on service processor error. 1.
Page 408 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406D 0EBF Memory error 1. Reboot the system in slow mode to the SMS menus. See “Performing Slow Boot” on page 241. 2. Examine the service processor error log. a.
Page 409 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406E 000A RIO connector card 1 RIO connector card 1 Location: U0.1-P1-H1 406E 000B RIO connector extender card 1 RIO connector extender card 1 Location: U0.1-P1-H1.1 406E 000C RIO connector card 2 RIO connector card 2 Location: U0.1-P1-H2...
Page 410 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406E 0022 Memory DIMM J2A, processor card 3 Memory DIMM Location: U0.1-P1-C3.M1 406E 0023 Memory DIMM J3A, processor card 3 Memory DIMM Location: U0.1-P1-C3.M6 406E 0024 Memory DIMM J0C, processor card 3 Memory DIMM Location: U0.1-P1-C3.M4 406E 0025 Memory DIMM J1C, processor card 3...
Page 411 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406E 00B4 Processor/VPD problem detected 1. Check for system firmware updates 2. Processor card 2 Location: U0.1-P1-C2 406E 00B5 Processor/VPD problem detected 1. Check for system firmware updates 2.
Page 412 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406E 0A03 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 0 firmware, may be able to correct this problem without replacing hardware.
Page 413 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406E 0A05 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 1 firmware, may be able to correct this problem without replacing hardware.
Page 414 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406E 0B00 Problem with internal RIO interface (I/O slot 0, 1. Check for system firmware updates. I/O port 0) 2. RIO riser card, Location: U0.1-P1-H1 3. Service processor/PCI backplane, Location:U0.1-P2 4.
Page 415 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406E 0B22 Problem with RIO interface (I/O slot 2, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H2 and the I/O subsystems.
Page 416 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406E 0BF1 Problem with RIO interface (I/O slot 1, I/O hub 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H1.1 and the I/O subsystems.
Page 417 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406E 0EA1 Operating system code on main processor 1. Check for operating system code updates. 2. Call service support. 406E 0EA2 PRD code on service processor error. 1.
Page 418 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406E 0EBF Memory error 1. Reboot the system in slow mode to the SMS menus. See “Performing Slow Boot” on page 241. 2. Examine the service processor error log. a.
Page 419 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406F 000A RIO connector card 1 RIO connector card 1 Location: U0.1-P1-H1 406F 000B RIO connector extender card 1 RIO connector extender card 1 Location: U0.1-P1-H1.1 406F 000C RIO connector card 2 RIO connector card 2 Location: U0.1-P1-H2...
Page 420 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406F 0022 Memory DIMM J2A, processor card 3 Memory DIMM Location: U0.1-P1-C3.M1 406F 0023 Memory DIMM J3A, processor card 3 Memory DIMM Location: U0.1-P1-C3.M6 406F 0024 Memory DIMM J0C, processor card 3 Memory DIMM Location: U0.1-P1-C3.M4 406F 0025 Memory DIMM J1C, processor card 3...
Page 421 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406F 00B4 Processor/VPD problem detected 1. Check for system firmware updates 2. Processor card 2 Location: U0.1-P1-C2 406F 00B5 Processor/VPD problem detected 1. Check for system firmware updates 2.
Page 422 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406F 0A03 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 0 firmware, may be able to correct this problem without replacing hardware.
Page 423 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406F 0A05 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 1 firmware, may be able to correct this problem without replacing hardware.
Page 424 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406F 0B00 Problem with internal RIO interface (I/O slot 0, 1. Check for system firmware updates. I/O port 0) 2. RIO riser card, Location: U0.1-P1-H1 3. Service processor/PCI backplane, Location:U0.1-P2 4.
Page 425 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406F 0B22 Problem with RIO interface (I/O slot 2, I/O port 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H2 and the I/O subsystems.
Page 426 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406F 0BF1 Problem with RIO interface (I/O slot 1, I/O hub 1. Check for system firmware updates. 2. Check the cabling between the RIO interface card at U0.1-P1-H1.1 and the I/O subsystems.
Page 427 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406F 0EA1 Operating system code on main processor 1. Check for operating system code updates. 2. Call service support. 406F 0EA2 PRD code on service processor error. 1.
Page 428 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 406F 0EBF Memory error 1. Reboot the system in slow mode to the SMS menus. See “Performing Slow Boot” on page 241. 2. Examine the service processor error log. a.
Page 429 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4503 25DC This error code indicates that the processor Do the following: repeat gard function has deconfigured a 1. Go to the processor processor. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 430 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4503 25EC This error code indicates that the processor Do the following: repeat gard function has deconfigured a 1. Go to the processor processor. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 431 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4503 25F4 This error code indicates that the processor Do the following: repeat gard function has deconfigured a 1. Go to the processor processor. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 432 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4503 301B This error code indicates that the memory Do the following: repeat gard function has deconfigured a quad 1. Go to the memory of memory. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 433 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4503 301D This error code indicates that the memory Do the following: repeat gard function has deconfigured a quad 1. Go to the memory of memory. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 434 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4503 302E This error code indicates that the memory Do the following: repeat gard function has deconfigured a quad 1. Go to the memory of memory. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 435 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4503 303B This error code indicates that the memory Do the following: repeat gard function has deconfigured a quad 1. Go to the memory of memory. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 436 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4503 303D This error code indicates that the memory Do the following: repeat gard function has deconfigured a quad 1. Go to the memory of memory. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 437 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4503 309B This error code indicates that the memory Do the following: repeat gard function has deconfigured a quad 1. Go to the memory of memory. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 438 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4503 309D This error code indicates that the memory Do the following: repeat gard function has deconfigured a quad 1. Go to the memory of memory. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 439 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4503 309F This error code indicates that the memory Do the following: repeat gard function has deconfigured a quad 1. Go to the memory of memory. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 440 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4504 25EF 0-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 4504 25F4 2 way processor card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 441 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4505 25EF 0-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 4505 25F4 2 way processor card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 442 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4506 25EF 0-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 4506 25F4 2 way processor card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 443 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4507 25EF 0-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 4507 25F4 2 way processor card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 444 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4508 25EF 0-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 4508 25F4 2 way processor card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 445 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4509 25EF 0-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 4509 25F4 2 way processor card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 446 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 450A 25EF 0-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 450A 25F4 2 way processor card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 447 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 450B 25EF 0-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 450B 25F4 2 way processor card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 448 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 450C 25EF 0-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 450C 25F4 2 way processor card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 449 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 450D 25EF 0-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 450D 25F4 2 way processor card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 450 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 450E 25EF 0-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 450E 25F4 2 way processor card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 451 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 450F 25EF 0-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 450F 25F4 2 way processor card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 452 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4605 278C RIO adapter card Replace the part specified by the location code. 4605 278D RIO adapter card Replace the part specified by the location code. 4605 2848 Service processor/PCI backplane Replace the part specified by the location code.
Page 453 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 460D 2784 RIO adapter card Replace the part specified by the location code. 460D 278C RIO adapter card Replace the part specified by the location code. 460D 278D RIO adapter card Replace the part specified by the location code.
Page 454 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4B23 25DC This error code indicates that the processor Do the following: repeat gard function has deconfigured a 1. Go to the processor processor. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 455 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4B23 25EC This error code indicates that the processor Do the following: repeat gard function has deconfigured a 1. Go to the processor processor. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 456 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4B23 25F4 This error code indicates that the processor Do the following: repeat gard function has deconfigured a 1. Go to the processor processor. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 457 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4B25 25EC 1-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 4B25 25EF 0-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 458 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4B27 289C 4-way processor bus connector card fault Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 4B27 289D 6-way processor bus connector card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 459 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4B2A 25DB 2-way processor card fault Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 4B2A 25DC 2-way processor card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 460 Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4B2C 25EC 1-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 4B2C 25EF 0-2 way processor card fault (CuOD) Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 461: Memory Dimm Present Detect Bits (Pd-Bits)
Table 6. Service Processor Error Codes. (continued) Error Code Description Action/ Possible Failing FRU 4B2E 281E System backplane fault Go to “MAP 1548: Memory and Processor Problem Isolation” on page 170. 4B2E 289C 4-way processor bus connector card fault Go to “MAP 1548: Memory and Processor Problem Isolation”...
Page 462: Error Log Utility Procedure
Error Log Utility Procedure When the System Management Services menu appears, check the error log for any errors. Use the location code obtained from the SMS error log utiltity to identify the component the error is reported against. To obtain the location code from the error log utility do the following: 1.
Page 463: System Firmware Update Messages
System Firmware Update Messages Error Code Description Action/ Possible Failing FRU A1FD 0000 Firmware update recovery mode entered Informational message A1FD 0001 Service processor flash recovery Insert Diskette #1 A1FD 0002 Service processor flash recovery Insert Diskette #2 A1FD 0003 Service processor flash recovery Insert Diskette #3 A1FD 0004 Service processor flash recovery Insert Diskette #4...
Page 464: Common Firmware Error Codes
Common Firmware Error Codes Attention: Follow the procedure defined in “Checkpoints and Error Codes Index” on page 245. If you replace FRUs or perform an action on an I/O subsystem and the problem is still not corrected, go to “MAP 1542: I/O Problem Isolation”...
Page 465 Error Code Description Action/ Possible Failing FRU B10F 100F Service processor base flash corrupted Service processor/PCI backplane Location: U0.1-P2 B10F 1300 Service processor failure Service processor/PCI backplane Location: U0.1-P2 B10F 1370 Service processor flash update failure Service processor/PCI backplane Location: U0.1-P2 B10F 1380 Service processor program failure Service processor/PCI backplane Location: U0.1-P2...
Page 466 Error Code Description Action/ Possible Failing FRU B1xx 4602 RIO failure Was this error code logged just after the system crashed? Go to step 3. Go to step 2. 2. Examine the service processor error log. Look for a 4xxx yyyy error that calls out FRU(s) in the CEC whose timestamp just precedes the B1xx 4602 error.
Page 467 Error Code Description Action/ Possible Failing FRU B1xx 4603 Service processor firmware corrupted 1. Reflash system firmware. 2. Service processor/PCI backplane Location: U0.1-P2 B1xx 4606 Firmware failure 1. Check for system firmware updates. 2. Operator panel Location: U0.1-L1 B1xx 4608 Service processor early termination 1.
Page 468 Error Code Description Action/ Possible Failing FRU B1xx 4633 This error code may be informational, or it may indicate a failure in the SPCN firmware update. Before changing any parts, examine word 13 in the service processor error log entry, or bytes 68 and 69 in the AIX error log entry.
Page 469 Error Code Description Action/ Possible Failing FRU B1xx 4643 I2C card/flex cable detection error Go to “MAP 1540: Problem Isolation Procedures” on page 140 B1xx 4644 Processor VPD System Fault Go to “MAP 1540: Problem Isolation Procedures” on page 140 B1xx 4645 I2C (non-processor) VPD system fault Go to “MAP 1540: Problem Isolation Procedures”...
Page 470 Error Code Description Action/ Possible Failing FRU B1xx 4671 Critical temperature in system unit drawer 1. Check ambient temperature. 2. Check air supply to fans. 3. Check fans for proper installation and operation. 4. Check for unsupported cards (which may be too hot) 5.
Page 471 Error Code Description Action/ Possible Failing FRU B1xx 4690 Description: Operating system surveillance interval exceeded (AIX to service processor interface failure) Action: 1. This error code indicates that the operating system terminated early (which usually implies an operating system crash). This error code may appear in the service processor error log by iteself.
Page 472 Error Code Description Action/ Possible Failing FRU B1xx 4696 System firmware interface failure 1. Check for system firmware updates. 2. Call service support. B1xx 4698 Service processor firmware error This usually indicates a mismatch between the number of CUoD processors or memory the system is licensed to have and the number of processors or memory installed in the system.
Page 473 Error Code Description Action/ Possible Failing FRU B1xx 469A System firmware interface 1. Check for system firmware updates. 2. Call service support. B1xx 469B Firmware to I/O interface 1. Check for system firmware updates. 2. Service processor/PCI backplane Location: U0.1-P2 B1xx 469C Firmware to I/O interface 1.
Page 474: Error Code B1Xx 4699
Error Code Description Action/ Possible Failing FRU B1FD 0016 Firmware update diskette read error 1. The firmware diskette may be faulty. Try another diskette. 2. Diskette drive Location: U0.1-D1. 3. Service processor/PCI backplane Location: U0.1-P2. B1FD 001A Service processor recovery mode update fault Reset the service processor by activating the pinhole reset switch on the operator panel.
Page 475 Actions: This is an informational message. No action is required by the customer or service representative. 2306: No processor card is detected in slot one (U0.1-P1-C1); a processor card is required in the first slot for the system to boot. Actions: 1.
Page 476 the load source. Actions: This is an informational message. No action is required by the customer or service representative. 9900: Memory allocation failure during firmware update. Actions: 1. Reset the system using the pin-hole reset button on the operator panel. Retry the operation that caused this error code.
Page 477 9906: Software problem during firmware update from operating system. Actions: 1. Check for a system firmware update that is later than the one that caused this error. Apply if available. 2. Call service support. 9920: Error occurred during model upgrade from a pSeries 670 (7040 model 671) to a pSeries 690 (7040 model 681).
Page 478: Error Code B1Xx 8Ff0
2. From the service processor main menu, enter code 88484 to access the hidden menu. 3. Press enter again at ″IBM Authorized Use Only″ screen. 4. When the CUoD menu appears, the status of ″Test and Run″ should be Available.
Page 479: Cod Transactions
68 and 69 in the AIX error log entry is C1A4, this indicates a capacity on demand (CoD) transaction has taken place. For more detail about CUoD and CoD transactions, see the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590.
Page 480 v Word 17 value (first 2 bytes): The number of processors activated with this transaction. v Word 17 value (second 2 bytes): The total number of activated processors of this type. This includes those previously activated plus those activated with this transaction. v Word 18 value (first 2 bytes): The current value of the processor day counter.
Page 481 2. On/off CoD resources are started or stopped due to a customer request (logically partitioned mode) v Word 16 value (first 2 bytes): 0600 v Word 17 value (first 2 bytes): The number entered on the processor on/off CoD management screen on the HMC (the number itself, not the difference from the previous value).
Page 482: Spcn Informational Codes
v Word 18 value (second 2 bytes): The current value of the hours remaining in the current period counter. Out of compliance due to the expiration of an on/off CoD period An informational log entry is made when the system goes out of compliance due to the expiration of an on/off CoD period (when the processor day counter is fully decremented to zero).
Page 483: Early Service Processor Termination Error Codes
HMC and the partitions, ensure that the short host names are set up correctly according to the instructions in ″Using Network Adapters to Communicate with Partitions″ in the IBM Hardware Management Console for pSeries Installation and Operations Guide. Correct any problems that are found, then verify that you can ping in both directions between the HMC and partitions.
Page 484: Problem Determination-Generated Error Codes
Problem Determination-Generated Error Codes Table 9. Problem Determination-Generated Error Codes Error Code Description Action/ Possible Failing FRU M0BT 0000 The system hung during speaker POST. This Go to “MAP 1542: I/O Problem Isolation” on error code is generated by the customer page 144.
Page 485: Hypervisor Dump Retrieval Procedure
Hypervisor Dump Retrieval Procedure This procedure defines the requirements and methods for retrieving a hypervisor (LPAR) dump file following a system crash. This procedure is only applicable if the managed system had been running as a partitioned system before it crashed. This procedure requires the managed system to be rebooted as a partitioned system.
Page 486 This will result in a file being written into the /tmp directory named dumpMMDDYY where MM is the current month, DD is the current day, and YY is the current year. The file /tmp/dumpMMDDYY should be forwarded to service support. If the following text appears on the AIX console: Retrieving Dump File Error performing dump read...
Page 487: Chapter 6. Using The Online And Standalone Diagnostics
Chapter 6. Using the Online and Standalone Diagnostics Running AIX diagnostics verifies system hardware operation. The AIX 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.
Page 488: Identifying The Terminal Type To The Diagnostics
FUNCTION SELECTION menu is displayed, the diagnostics do not allow you to continue until a terminal is selected from the DEFINE TERMINAL option menu. Choose the ″lft″ selection when running diagnostics from a IBM Hardware Management Console for pSeries (HMC). 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.
Page 489: Service Mode
– 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 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.
Page 490: Concurrent Mode
5. Enter any requested passwords. After any requested passwords have been entered, the system attempts to boot from the first device of each type found on the list. If no bootable image is found on the first device of each type on the list, the system does not search through the other devices of that type for a bootable image;...
Page 491: 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. Documentation for the AIX operating system is available from the IBM Eserver pSeries Information Center at http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base. Select AIX documentation. The AIX Documentation CD contains the base set of publications for the operating system, including system-management and end-user documentation.
Page 492: Standalone Diagnostic Operation With An Hmc Attached To The System
1. Stop all programs including the operating system (get help if needed). 2. Remove all tapes, diskettes, and CD-ROMs. 3. Power off the Eserver pSeries 650 (refer to Full System Management Tasks in the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590, for more information on full system partitions).
Page 493 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.
Page 494 In a partitioned system, make the CD-ROM drive available to the partition used to run standalone diagnostics (refer to the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590 for more information). Verify with the system administrator and system users using a partition that all applications on that partition must be stopped, and that the partition will be rebooted.
Page 495 – Cstate on the NIM server may be incorrect. – Network problems might be 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 refer to “Boot Problems”...
Page 496 EserverpSeries 650 Service Guide...
Page 497 (location U0.1-P2). None of this information is applicable to the serial ports, or modems attached to those serial ports, on the IBM Hardware Management Console for pSeries (HMC). 2. On some of the system management services (or service processor) screens, you will see the term LPAR.
Page 498 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 processor.
Page 499 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. GENERAL USER MENU 1.
Page 500 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.
Page 501 v Set System Name Allows setting of the system name. 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.
Page 502 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 8, “Using System Management Services,”...
Page 503 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.
Page 504 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).
Page 505 Scan Log Dump Setup Menu 1. Scan Log Dump Policy: Currently As Needed 2. Scan Log Dump Content: Currently As Requested 3. Immediate Dump 98. Return to Previous Menu 0>1 Select from the following options: (As Needed=2, Always=3) Enter New Option: 0>1 The scan log dump policy can be set to the following: 2=As Needed...
Page 506 The complete dump will take the longest time to finish; it may take as long as 1.5 hours on a fully configured system. Option 3, Immediate Dump, 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.
Page 507 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.
Page 508 – Enable supplemental restart policy - The default setting is Yes. When set to Yes in a full system partition, the service processor restarts the system when the system loses control as detected by service processor surveillance, and either: The Use OS-Defined restart policy is set to No. The Use OS-Defined restart policy is set to Yes, and the operating system has no automatic restart policy.
Page 509 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.
Page 510 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.
Page 511 v Read NVRAM Displays Nonvolatile Random Access Memory (NVRAM) content. v Read Service Processor Configuration Displays current service processor configuration. v Processor Configuration/Deconfiguration Menu Enable/Disable CPU Repeat Gard: CPU repeat gard automatically deconfigures a CPU during a system boot if a processor fails BIST (built-in self-test), caused a machine check or check stop, or has reached a threshold of recoverable errors.
Page 512 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.
Page 513 MEMORY CONFIGURATION/DECONFIGURATION MENU 77. Enable/Disable Memory Repeat Gard: Currently Enabled 78. Runtime Recoverable Error Repeat Gard: Currently Enabled 1. Memory card 98. Return to Previous Menu After you select the memory card option by entering 1, a menu similar to the following displays, allowing the selection of a memory DIMM.
Page 514 POWER CONTROL NETWORK UTILITIES MENU 1. Lamp test for all operator panels 2. Display I/O type Not Supported 3. Change I/O type 4. Collect & display SPCN trace data 5. Start SPCN Flash Update 6. Display Power Subsystem FRU Code Levels Not Applicable 7.
Page 515 – Collect & display SPCN trace data This option is used by service personnel to dump the SPCN trace data from the system unit or an I/O subsystem to gather additional debug information. To dump the SPCN trace data for the processor subsystem (CEC drawer), enter 0 when prompted for the SPCN drawer number and enter d0 when prompted for the unit address.
Page 516 LED Control Menu 1. Set/Reset Identify LED state 2. Clear System Attention Indicator 98. Return to Previous Menu Enter LED index 0 > If Option 1 is selected, a list of location codes of the I/O subsystems and the system unit drawer is shown, similar to the following: 1.
Page 517 system-wide; it cannot be set on a per-partition basis. Chapter 7. Using the Service Processor...
Page 518 You can override the default setting by using the Default Performance Mode menu, similar to the following: Default Performance Mode: Standard Operation 1. Current Performance Mode: Standard Operation 98. Return to Previous Menu 0>1 Selecting option 1 displays the following performance modes: Select from the following options: 1.
Page 519 This option is used to change the speed of the RIO interface to external drawers. On this system, setting this speed will have no effect on the system. The hardware capability is detected and set by the system firmware during the boot process. If the hardware capability is uninitialized (after NVRAM is cleared), it will be set during the first boot and remain set during subsequent boots.
Page 520 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 service processor/PCI backplane (location U0.1-P2). These serial ports are normally used for call-in and call-out. Call-out is disabled in partitioned systems.
Page 521 Modem Configuration Menu Note: This option applies only to a modem attached to serial port 1 (S1) or serial port 2 (S2) on the service processor/PCI backplane. 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.
Page 522 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.
Page 523 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.
Page 524 Telephone Number Setup Menu Note: These menus are available. However, the function of calling out to report a system failure is usually handled by the Service Focal Point application running on the HMC. Use this menu to set or change the telephone numbers for reporting a system failure. Telephone Number Setup Menu 1.
Page 525 Call-Out Policy Setup Menu Note: Call-out is disabled in logically partitioned systems. Call out settings can be set using the following menu: CALL-OUT POLICY SETUP MENU 1. Call-Out policy (First/All): Currently First 2. Remote timeout, (in seconds): Currently 120 3. Remote latency, (in seconds): Currently 2 4.
Page 526 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.
Page 527 System Power-On Methods This section discusses the following system power-on methods: v Power-on Button on the operator panel 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.
Page 528 Service Processor Reboot/Restart Recovery Reboot describes bringing the system hardware back up; for example, from a system reset or power-on. The boot process ends when control passes to the operating system process. Restart describes activating the operating system after the system hardware is reinitialized. Restart must follow a successful reboot.
Page 529 Enable supplemental restart policy - The default setting is yes. When set to yes in a full system partition, the service processor restarts the server when the operating system loses control and either: The Use OS-Defined restart policy is set to No. The Use OS-Defined restart policy is set to Yes and the operating system has no automatic restart policy.
Page 530 Download the detailed instructions, as well as the latest flash images, from the following Web address: http://www.rs6000.ibm.com/support/micro. Before doing a system firmware update, check the Web site for the latest code and images. Do not attempt a firmware update if you are unsure of the image you have, or of the procedure required for the update.
Page 531 Note: This information may be superseded by the information that is available on the Web site listed below. Always check the Web site for the latest images and instructions for checking the firmware level. The Web address is: http://techsupport.services.ibm.com/server/mdownload2. There are two forms in which the firmware level may be denoted: v RKyymmdd, where RK = the pSeries Eserver pSeries 650’s firmware designation, yy = year, mm =...
Page 532 System Firmware Update in AIX Using a Locally Available Image To update the system firmware using a locally available image, perform the following steps: 1. Log in as root user. 2. If the /tmp/fwupdate directory does not exist, create it by issuing the following command: mkdir /tmp/fwupdate 3.
Page 533 Updating System Firmware From the Service Processor Menus This procedure requires a diskette drive to be installed in the system. This procedure also requires a set of firmware update diskettes in backup format. The service processor menus are available while the system is powered off. As a privileged user, from the service processor main menu, select Service Processor Setup, then select Reprogram Flash EPROM Menu.
Page 534 Recovery Mode If the service processor detects that its programming has been corrupted when it is powering on to standby mode, it will enter recovery mode. In recovery mode, it prompts for the firmware update diskettes by putting eight-digit codes on the operator panel display, as shown in the following table. After the update process is complete, the service processor resets itself and performs a complete reboot.
Page 535 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 DIMMs with a failure history are marked ″bad″...
Page 536 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 heartbeats. 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.
Page 537 processor assumes the system is hung and takes action according to the reboot/restart policy settings. See “Service Processor Reboot/Restart Recovery” on page 508. 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.
Page 538 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.
Page 539 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.
Page 540 Service Processor Error Logs The service processor error logs, an example of which is shown below, contain error conditions detected by the service processor. Error Log 1. 11/30/99 19:41:56 Service Processor Firmware Failure B1004999 Enter error number for more details. Press Return to continue, or ’x’...
Page 541 LCD Progress Indicator Log The following is an example of the LCD progress indicator log. It shows the types of entries that the log can contain, and is for example purposes only. The progress indicator codes are listed from top (latest) to bottom (oldest). LCD Progress Indicator Log B0FF 0539..17...
Page 542 Service Processor Operational Phases This section provides a high-level flow of the phases of the service processor. SP Power Applied Pre-Standby Phase Standby Phase SP Menus Available Bring-Up Phase SMS Menus Available Run-time Phase Operating System Login Prompt Available Pre-Standby Phase This phase is entered when the server is connected to a power source.
Page 543 Standby Phase The standby phase can be reached in either of the following: v With the server off and power connected (the normal path), recognized by OK in the LCD display. 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.
Page 544 v Update Operator Panel The service processor displays operator panel data on the HMC virtual terminal window if a remote connection is active. v Environmental Monitoring The service processor provides expanded error recording and reporting. v System Firmware Surveillance (Heartbeat Monitoring) The service processor monitors and times the interval between system firmware heartbeats.
Page 545 1. At the service processor main menu, enter 11235 2. A the the screen that says IBM AUTHORIZED PERSONNEL ONLY, press Enter to continue. 3. Select option 2, set time-of-day. Enter the date and time using the formats shown on the screen. The time must be Greenwich Mean Time (GMT) and must be in the 24-hour format (1:00:00 PM is 13:00:00, for example).
Page 546 EserverpSeries 650 Service Guide...
Page 547 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 IBM Hardware Management Console for pSeries (HMC) to restart the partition. For a full system partition, restart the system.
Page 548 When there is more than one page of information to display, there are two additional navigation keys: Display the next page of the list. Display the previous page of the list. Note: The lowercase navigation key has the same effect as the uppercase key that is shown on the screen.
Page 549 Select Language Note: Your TTY must support the ISO-8859 character set to properly display languages other than English. This option allows you to change the language used by the text-based System Management Services menus. SELECT LANGUAGE 1. English 2. Francais 3.
Page 550 Change Password Options The Change Password Options menu enables you to select from password utilities. Note: This option is not available when the system is booted in LPAR mode. Password Utilities 1 Set Privileged-Access Password 2 Remove Privileged-Access Password -------------------------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen...
Page 551 NIC Adapters Device Slot Hardware Address 10/100 Mbps Ethernet PCI Adapt Integ: U0.1-P2/E1 00096baeac10 IBM 10/100/1000 Base-TX PCI Integ: U0.1-P2-I3/E1 0009cbce0fde -------------------------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services...
Page 552 Attention: If the client system and the server are on the same subnet, set the gateway IP address to [0.0.0.0]. EserverpSeries 650 Service Guide...
Page 553 Selecting Adapter Configuration allows the setting of the network speed, enabling or disabling spanning tree, and setting the protocol as shown in the example menu below: Attention: In a partitioned system, only those network adapters that have been assigned to the partition being booted display in the IP Parameters menu.
Page 554 Spanning Tree Enabled 10/100 Mbps Ethernet PCI Adapter II: U0.1-P2/E1 1. Yes <=== 2. No -------------------------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _ The Protocol option allows you to set the appropriate protocol for your network as shown below.
Page 555 Select Console Note: This option is not available in a partitioned system. A virtual terminal window on the HMC is the default firmware console for a partitioned system. The Select Console Utility allows the user to select which console the user would like to use to display the SMS menus.
Page 556 If option 1 is selected, the following menu is displayed: Select Device Type 1. Diskette 2. Tape 3. CD/DVD 4. IDE 5. Hard Drive 6. Network 7. None 8. List All Devices -------------------------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services --------------------------------------------------------------------------------------------------...
Page 557 If List All Devices is selected, a menu similar to the following displays, depending on the devices that are installed in the system: Select Device Device Current Device Number Position Name SCSI 18200 MB Harddisk (loc=U0.1-P2/Z1-A8,0) SCSI 18200 MB Harddisk (loc=U0.1-P2/Z1-A9,0) SCSI 18200 MB Harddisk (loc=U0.1-P2/Z1-Aa,0) None 5.
Page 558 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. Note: To keep the search time for bootable devices down, these menus follow a hierarchy of: 1.
Page 559 When a device type is selected, such as item 5, a Select Media Type menu is displayed. The following is an example of that menu. Select Media Type 1. SCSI 2. SSA 3. SAN 4. IDE 5. ISA 7. None 8.
Page 560 -------------------------------------------------------------------------------------------------- THE SELECTED DEVICES WERE NOT DETECTED IN THE SYSTEM Press any key to continue. -------------------------------------------------------------------------------------------------- When a device type is selected, such as item 1, a Select Task menu will be displayed. The following is an example of that menu for a hard disk. Select Task SCSI 18200 MB Harddisk (loc=U0.1-P2/Z1-A8,0) 1.
Page 561 Display Current Settings This option displays the current setting of the customized boot list. An example of this menu, with one device in the boot list, follows. Current Boot Sequence 1. SCSI 18200 MB Harddisk (loc=U0.1-P1/Z1-A8,0) None None None None -------------------------------------------------------------------------------------------------- Navigation keys: M = return to main menu...
Page 562 EserverpSeries 650 Service Guide...
Page 563 Chapter 9. Removal and Replacement Procedures This chapter provides removal and replacement instructions for FRUs that are associated with the 7038 Model 6M2 processor subsystem. For removal and replacement of FRUs associated with the an I/O subsystem, see the pSeries 7311 Model D10 and Model D20 Service Guide, order number, SA38-0627. Before performing any of the removal or replacement procedures in this chapter, read the following notices.
Page 564 the lower left side of the back of the rack. See the following illustration 1 Rack Without Extenders 3 ESD Pad 2 ESD Pad 4 Rack With 4 Inch Extenders EserverpSeries 650 Service Guide...
Page 565 Powering Off and Powering On the System This section provides procedures for powering off and powering on the system. Stopping the System without an HMC Attached Attention: When shutting down your system to install options, shut down all applications first and then shut down the operating system.
Page 566 Attention: Using the power button on the operator panel or commands at the HMC to power off the system can cause unpredictable results in the data files. The next IPL will also take longer to complete if all applications in all partitions are not stopped before hand. Starting the System Without an HMC Attached Power on the system only after all of the following steps are completed: v All I/O drawer cables are connected...
Page 567 After the system is powered on, all logical partitions will be in a standby or powered on state. Each logical partition must then be booted via the HMC. The state of all logical partitions that have been booted will be running.
Page 568 Processor Subsystem Access The processor subsystem is normally installed in the operating position in a standard rack. Access to the rear of the drawer is through the back door of the rack. To access components inside the drawer, it must be placed in the service position and the two top covers removed.
Page 569 Processor Subsystem Top Covers If you plan to remove the covers from the top of the processor subsystem for a service procedure, you can loosen the covers when the processor subsystem is in the operating position, and then remove the covers when the processor subsystem is in the service position.
Page 570 3. Lift the front of the EMC cover straight up. When the rear of the cover is clear of the rear bulkhead, lift the cover out of the processor subsystem. Replacement 1. Pull up on all the push-button snaps to ensure that they are all in the open position. 2.
Page 571 PCI Adapters Attention: The Linux operating system does not support some hot-pluggable procedures. Also, Linux does not support hot-plugging any hot-pluggable PCI adapters or devices. System with Linux installed on one or more partitions must be shutdown and powered off before replacing any PCI adapter or device assigned to a Linux partition.
Page 572 Removing and Replacing a PCI Adapter Cassette Attention: Only perform these procedures with the power turned on if you are directed to by the “Hot-Pluggable PCI Adapter Removal and Replacement” on page 559. Removing a PCI Adapter Cassette Attention: Perform this procedure only when you are instructed to by the removal and replacement procedures for a “Non-Hot-Pluggable PCI Adapter Removal and Replacement”...
Page 573 To remove a PCI adapter cassette, do the following: 1. Determine which PCI adapter cassette you are removing. 2. Disconnect any cables that are connected to the PCI adapter. 3. Press the handle release lever, then push the handle to the down position. See the following illustration.
Page 574 1 Locking Bar 2 PCI Adapter Tailstock Tab 3 Adapter Cassette Pull Tab 5. Position your index finger under the handle and push up the adapter tailstock tab. Grasp the adapter cassette pull tab with the other hand. Pull the PCI adapter cassette from the adapter slot by pulling on the adapter cassette pull tab.
Page 575 Replacing a PCI Adapter Cassette Attention: Perform this procedure only when instructed to by “Non-Hot-Pluggable PCI Adapter Removal and Replacement” on page 558 or “Hot-Pluggable PCI Adapter Removal and Replacement” on page 559. Check the following: v An adapter or blank filler must be installed in each PCI adapter cassette and the top cover for the unit must be installed before installing PCI adapter cassette in the system.
Page 576 3. Examine the PCI adapter slot opening carefully, and note the location of the dovetail rails and the cassette guide rails. A flashlight can be used to enable you to see the dovetail rails and the cassette guide rail slots, as shown in the following illustration. 1 Cassette Left Dovetail Rail 4 Cassette Bottom Guide Rail 2 Cassette Right Dovetail Rail...
Page 577 9. Visually check to ensure that the cassette is parallel with the cassettes to the left or right. If the cassette is not parallel with the neighboring cassettes, the cassette dovetail rails might not be correctly engaged. If the cassette is not correctly aligned, you might need to pull it out so you can see the ends of the dovetail rails.
Page 578 Non-Hot-Pluggable PCI Adapter Removal and Replacement Removing a Non-Hot-Pluggable PCI Adapter To remove a non-hot-pluggable adapter, do the following: 1. Turn off power and remove the power from the system as described in “Stopping the System without an HMC Attached” on page 545. 2.
Page 579 For additional information about taking an adapter offline or removing it from the system configuration, see the AIX System Management Guide: Operating System and Devices. Documentation for the AIX operating system is available from the IBM Eserver pSeries Information Center at http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base. Select AIX documentation.
Page 580 13. Select Replace/Remove a PCI Hot-Plug Adapter and press Enter. The Replace/Remove a PCI Hot-Plug Adapter menu displays. 14. Move the cursor to select the adapter that you are removing and press Enter. 15. Press the Tab key until the entry field displays the replace operation and then press Enter. Follow the instructions that display on the screen until you are instructed to remove the adapter.
Page 581 For additional information about taking an adapter offline or removing it from the system configuration, see the AIX System Management Guide: Operating System and Devices. Documentation for the AIX operating system is available from the IBM Eserver pSeries Information Center at http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base. Select AIX documentation.
Page 582 16. Press the Tab key until the entry field displays the remove operation and then Press the Enter key. Follow the instructions that display on the screen until you are instructed to remove the adapter. 17. When you are instructed to remove the adapter from the adapter slot, disconnect any cables that are connected to the adapter being removed.
Page 583 Installing a Hot-Pluggable PCI Adapter Attention: The Linux operating system does not support some hot-pluggable procedures. Also, Linux does not support hot-plugging any hot-pluggable PCI adapters or devices. The system with Linux installed on one or more partitions must be shutdown and powered off before replacing any PCI adapter or device assigned to a Linux partition.
Page 584 For additional information about taking an adapter offline or removing it from the system configuration, see the AIX System Management Guide: Operating System and Devices. Documentation for the AIX operating system is available from the IBM Eserver pSeries Information Center at http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base. Select AIX documentation.
Page 585 List PCI Hot-Plug Slots Provides a descriptive list of all slots that support PCI hot-plug capability. If the listing for a slot indicates it holds an “Unknown” device, select the Install/Configure Devices Added after IPL to configure the adapter in that slot. Add a PCI Hot-Plug Adapter Allows the user to add a new PCI hot-plug-capable adapter to the slot with the system turned on.
Page 586 Install/Configure Devices Added After IPL The system attempts to configure any new devices and tries to find and install any required software from a user-selected source. The add, remove, and replace functions return information to the user indicating whether the operation was successful.
Page 587 PCI Adapter or Blank Filler Removal from a Cassette Assembly Use this procedure when you are preparing to install or replace an adapter or an adapter blank filler in the system unit or an I/O drawer. Note: An adapter or an adapter blank filler must be installed into the PCI adapter cassette assembly before it is reinstalled in a system unit or an I/O drawer.
Page 588 2. Using two fingers, remove the bushing-lock pin from the bushing. The bushing-lock pin can be removed by pulling it out of the bushing with your fingernails. 1 Bushing 2 Bushing-Lock Pin 1 Bushing-Lock Pin EserverpSeries 650 Service Guide...
Page 589 3. Remove the bushing. The bushing can be removed by pulling it out of the PCI adapter cassette assembly with your fingernails. 1 Bushing 4. Turn over the PCI adapter cassette assembly so that the top is facing away from you. 1 Top of Adapter 2 Handle Chapter 9.
Page 590 5. Remove the bezel, as follows: a. Locate the plastic latch fingers in the top part of the cassette. 1 Top of Cassette 2 Bezel 3 Plastic Latch Fingers b. Using one hand, pinch the plastic latch fingers, and with your other hand, carefully lift the top part of the bezel extension out until the tabs clear the slots in the PCI adapter cassette assembly.
Page 591 c. While holding the bezel extension out, push the plastic cover latch out of the bezel hook, as shown in the following illustration. This action allows the bezel to be removed. 1 Bezel Extension 2 Plastic Cover Latch in Bezel Hook d.
Page 592 e. While holding the bezel extension out, carefully slide the bezel off. You might have to work from both sides to loosen the bezel assembly from the cassette assembly. When the bezel is free, slide it completely off the cassette assembly, and set it aside. 1 Bezel Extension 2 Bezel 1 Bezel...
Page 593 6. Turn over the cassette so that the cover is facing up, as shown in the following illustration. Remove the cover from the cassette as follows: a. Slide the cover until it releases from the cassette assembly. Attention: The cover might be tight and difficult to slide. If you grasp the left end (handle end) of the cassette and the right end of the cover, you can use enough force to pull the cover off the PCI adapter cassette assembly.
Page 594 7. Remove the metal EMC shield from the top of the tailstock. 1 Metal EMC Shield 8. Remove the blank filler or adapter that is installed in the cassette linkage assembly. Note: If there is a blank filler in the cassette linkage assembly, as shipped from the manufacturer, there are two adapter arms.
Page 595 Short Adapter or Blank Filler Removal To remove a short adapter or blank filler, do the following: Slide the long and short adapter arms away from the adapter or blank filler by doing the following: Each adapter arm has a release tab that allows the arm to be moved away from the adapter or blank filler in the cassette assembly.
Page 596 2. Remove the adapter or blank filler from the cassette linkage assembly by rotating the bottom of the tailstock out, as shown in the following illustration. Store the adapter or blank filler in a safe place. 1 Cassette Linkage Assembly 2 Bottom of Tailstock 3 Handle 3.
Page 597 Long Adapter Removal To remove a long adapter, do the following: Each adapter arm has a release tab that allows the arm to be moved away from the adapter in the cassette assembly. Use your fingernail to lift the tab, to allow the arm to be moved away from the adapter.
Page 598 Note: Your PCI adapter cassette linkage might not have the short or long adapter retaining arms installed if you removed them during the removal procedure. In the following illustration, both arms are shown. 1 Handle 2 Cassette Linkage Assembly 3 Arms EserverpSeries 650 Service Guide...
Page 599 5700 IBM Gigabit Ethernet-SX PCI-X Adapter 53P5450 5701 IBM 10/100/1000 Base-TX Ethernet PCI-X Adapter 53P5450 5706 IBM 2-Port 10/100/1000 Base-TX Ethernet PCI-X Adapter 53P5450 5707 IBM 2-Port Gigabit Ethernet-SX PCI-X Adapter 53P5450 6203 PCI Dual Channel Ultra3 SCSI Adapter 44P2661...
Page 600 2. To determine if you are installing a long adapter or a short adapter, use the following steps. If you know the length of your adapter, skip the following steps and proceed to step 3 on page 582. a. Remove the adapter from its protective packaging and, if present, remove the plastic extension handle from the end of the adapter.
Page 601 c. The cassette linkage is marked to show long or short adapters similar to the adapter shown in the following illustration. Check the right end of the adapter to determine if it is long enough to fall into the long area of the cassette linkage. Ensure that the corner on the left end of the adapter is still aligned into the top adapter-retaining clip, and determine the length of the adapter.
Page 602 3. Remove the adapter or blank filler and ensure that the handle is in the up position. If you need to move the handle, ensure that the locking bar is pulled into the unlocked position, and then rotate the adapter handle until the handle is in the up position (the cassette linkage will extend down beyond the cassette top).
Page 603 1. Place the adapter or blank filler into the cassette so that the upper-left corner of the adapter engages the adjustable top adapter-retaining clip as shown in the following illustration. 1 Cassette Linkage Assembly 2 Bottom of Tailstock 3 Retaining Clip 4 Handle Chapter 9.
Page 604 2. Rotate the adapter so that the adapter engages the slot in the bottom adapter-retaining clip and the top corner of the adapter is seated into the adjustable top adapter-retaining clip. Note: If the adapter is not a full-height adapter, you must slide the adjustable top adapter-retaining clip downward until the lower edge of the adapter is seated into the slot on the bottom adapter-retaining clip.
Page 605 3. Slide the short-adapter retaining arm toward the adapter or blank filler on the cassette linkage rail. If the short-adapter retaining arm has been removed from the cassette linkage rail, install the short-adapter retaining arm and then slide the arm until it contacts the adapter or blank filler as shown in the following illustration.
Page 606 4. Ensure that the adjustable top retaining clip catches the corner of the adapter as shown in the following illustration: 1 Short Adapter Top Retaining Clip 5. Use the lower short adapter arm clip to engage and hold the bottom of the adapter. Note: It might be necessary to apply pressure to engage and hold the bottom of the adapter.
Page 607 arm. 1 Adjustable Top Adapter-Retaining Clip Chapter 9. Removal and Replacement Procedures...
Page 608 7. Press the lock on the handle, and rotate the adapter handle until it is in the down position (adapter or blank filler moves up into the cassette assembly). 1 Handle Release Lever 2 Lock Ensure the right end of the cassette linkage rail moves up into the cassette linkage assembly as shown in the following illustration: 1 Right End of Cassette Linkage EserverpSeries 650 Service Guide...
Page 609 8. Position the adapter and cassette assembly with the handle on the left (in the down position) and the top facing away from you. 1 Top of Cassette 2 Handle Chapter 9. Removal and Replacement Procedures...
Page 610 9. Install the cover on the cassette assembly, as follows: a. Place the cassette cover on the cassette assembly as shown in the following illustration. Slide the cover toward the handle until the hole in the cover aligns with the hole in the cassette assembly. 1 Handle 2 Holes Aligned EserverpSeries 650 Service Guide...
Page 611 Install the bezel assembly using the following procedure: a. Carefully slide the bezel onto the cassette assembly. 1 Bezel Align and insert the cover arm latch in the hooked notch in the bezel. 1 PCI Adapter Pull Tab 2 Hooked Notch in the Bezel Chapter 9.
Page 612 c. Align the top of the bezel assembly into the grooves on the top of the cassette assembly. Push the bezel onto the cassette linkage until the tab on the top of the bezel is seated in the recess of the cassette assembly.
Page 613 11. Check for the following: a. Ensure that the extension arm engages the pins on the cassette. You should be able to see the three pins in the holes in the arm. The bezel tab should be seated as shown in the following illustration.
Page 614 c. Turn the cassette assembly over so the cover is up. Check the cover latch to ensure it is holding the bezel to the cover as shown. 1 Cover Latch 12. Position the adapter with the cover side up. Ensure the holes are aligned, and insert the bushing as shown.
Page 615 13. Insert the bushing lock pin into the hole in the bushing and push it in until it seats. 1 Bushing Lock Pin 14. By pulling on both sides, ensure the gray plastic locking bar on the handle is pulled into the unlocked position.
Page 616 15. To install the metal EMC shield on the adapter bracket, grasp the EMC shield as shown in the following illustration, and do the following: 1 Metal EMC Shield 2 Installation Location for the Metal EMC Shield a. Ensure that the shield slides up inside the top of the cassette. 1 Metal EMC Shield EserverpSeries 650 Service Guide...
Page 617 b. The metal shield has clips that slide over the top of the tailstock. Ensure that these clips are holding the EMC shield to the tailstock. 1 Top of Tailstock 16. Depress the handle release lever on the handle and rotate the adapter handle until the handle is in the down position (adapter or blank filler moves up into the cassette assembly).
Page 618 17. Using the system documentation, determine if the adapter you are installing is hot-swappable. If the adapter is hot-swappable, move the slider on the color indicator to allow the orange to be visible. If the adapter is not hot-swappable, the blue color is visible. 1 Orange for Hot-Swappable 2 Blue for Not Hot-Swappable 18.
Page 619 1. Place the adapter into the cassette so that the upper-left corner of the adapter engages the top adjustable adapter-retaining clip as shown in the following illustration: 1 Top Adapter-Retaining Clip 3 Adapter 2 Cassette Linkage Assembly 4 Bottom of Tailstock 5 Handle Chapter 9.
Page 620 2. Rotate the adapter so that the adapter engages the slot in the bottom retaining clip and the top corner of the adapter is seated into the top adjustable adapter-retaining clip. Note: If the adapter is not a full-height adapter, slide the top adjustable adapter-retaining clip downward until the lower edge of the adapter is seated into the slot on the bottom retaining clip.
Page 621 3. Install the long adapter-retaining arm onto the cassette linkage rail, as shown in the following illustration, and slide the arm toward the adapter. 1 Cassette Linkage Assembly 3 Top Adapter Retaining Clip 2 Adapter Retaining Arm Chapter 9. Removal and Replacement Procedures...
Page 622 4. Ensure that the top adjustable adapter-retaining clip catches the corner of the adapter as shown in the following illustrations. 1 Top Adjustable-Retaining Clip 5. Ensure that the bottom edge of the adapter is held by the groove in the lower part of the adapter-retaining arm.
Page 623 6. To hold the top of the adapter, slide down the top adjustable adapter-retaining clip on the retaining arm. 1 Long Adapter Retaining Arm 7. Depress the handle release lever on the handle. Rotate the adapter handle until it is in the down position (adapter or blank filler moves up into the cassette assembly).
Page 624 Ensure the right end of the cassette linkage rail moves up into the cassette linkage assembly as shown: 1 Right End of Cassette Linkage 8. Position the adapter and cassette assembly with the handle on the left (in the down position) and the top facing away from you.
Page 625 9. Install the cover on the cassette assembly by placing the cassette cover on the cassette assembly as shown. Slide the cover toward the handle until the hole in the cover aligns with the hole in the cassette assembly. 1 Handle 2 Hole in the Cover Chapter 9.
Page 626 Install the bezel assembly using the following procedure: a. Carefully slide the bezel onto the cassette assembly. 1 Bezel Align and insert the cover arm latch in the hooked notch in the bezel. 1 PCI Adapter Pull Tab 2 Hooked Notch in the Bezel EserverpSeries 650 Service Guide...
Page 627 c. Align the top of the bezel assembly into the grooves on the top of the cassette assembly and then push the bezel onto the cassette linkage until the tab on the top of the bezel is seated in the recess of the cassette assembly.
Page 628 11. Check for the following: Ensure that the extension arm engages the three pins on the cassette. You can see the pins in the holes in the arm. The bezel tab is seated as shown in the following illustration. 1 Pins b.
Page 629 c. Turn the cassette assembly over so that the cover is facing up and check the cover latch to ensure it is holding the bezel to the cover as shown. 1 Cover Latch 12. Position the adapter with the cover side facing up. Ensure the holes are aligned, and insert the bushing as shown.
Page 630 13. Insert the bushing-lock pin into the hole in the bushing. Push on the pin until it seats. 1 Bushing-Lock Pin 14. Depress the handle release lever to ensure the locking bar on the handle is pulled into the unlocked position.
Page 631 15. To install the metal EMC shield on the adapter bracket, do the following: 1 Metal EMI Shield 2 Adapter Bracket a. Ensure that the shield slides up inside the top of the cassette. 1 Metal EMC Shield 2 Adapter Bracket Chapter 9.
Page 632 b. The metal EMI shield has clips that slide over the top of the tailstock. Ensure that these clips are holding the EMC shield to the tailstock. 1 Top of Tailstock 16. Press the lock on the handle and rotate the adapter handle until the handle is in the down position (adapter or blank filler moves up into the cassette assembly).
Page 633 the adapter is not hot-swappable, the blue is visible. 1 Orange indicates Hot-Swappable 2 Blue indicates Not Hot-Swappable 18. The adapter is ready to be installed into a system or an I/O drawer. Chapter 9. Removal and Replacement Procedures...
Page 634 Processor Subsystem Procedures The removal and replacement procedures for the processor subsystem follow. Handle all processor subsystem FRUs with extreme care. Processor Card Before replacing a processor card, check with your support center to ensure you have been directed to replace the processor card for an error code in Chapter 5, “Error Code to FRU Index,”...
Page 635 Note: If you have memory DIMMs to install on the new processor card, install the memory DIMMs before continuing in this procedure. For more information about removing and replacing memory DIMMs, see “Memory DIMMs” on page 618. 7. Unlatch the latches on the processor card and carefully slide the card into the processor subsystem until it contacts the connectors.
Page 636 6. Remove the screws that hold the processor bus connector to the bottom of the chassis. 1 Screw 2 Processor bus connector 7. Lift the processor bus connector out of the chassis. Replacement 1. Place the processor bus connector into the chassis. 1 Screw 2 Processor bus connector 2.
Page 637 3. If blank processor fillers were removed earlier, install them in the positions from which they were removed. 4. Unlatch the latches on the processor card and carefully slide each processor card into the processor subsystem until it contacts the connectors. Attention: Do not drop or force the processor card against the connectors.
Page 638 Memory DIMMs Removal 1. Turn off power as described in “Powering Off and Powering On the System” on page 545. 2. Determine on which processor card the memory is installed. 3. Perform the removal procedure under “Processor Card” on page 614. 4.
Page 639 Service Processor/PCI Backplane This procedure is for removing, and replacing the service processor/PCI backplane. Before You Begin Read the following notes before you begin any removal or replacement actions. Notes: 1. If you are replacing a service processor/PCI backplane, check the system firmware level prior to replacing this part.
Page 640 Note: If the service processor menus are not available, the customer will have to provide the service processor settings after the Service Processor/PCI Backplane is replaced. 5. Boot to the SMS Main Menu. 6. Select option 7, Select Boot Options. 7.
Page 641 8. Remove the PCI adapter cassette bracket from over the service processor/PCI backplane. Save the screws and the bracket. 1 Air cover 4 Screw 2 Screw 5 Front cover plate 3 PCI adapter cassette bracket 6 SCSI Repeater Card 9. Record the connector locations of all internal cables attached to the service processor/PCI backplane for easier replacement.
Page 642 10. Remove the processor card cage from the processor subsystem. Attention: In the next step the flex cable is disconnected. The flex cable connectors and latch are fragile. Do not use the latch handle to pull or push the connector. Use extreme care when using the latch handle to disconnect or reconnect either connector of the flex cable.
Page 643 Replacement To replace a service processor/PCI backplane, do the following: 1. Inspect the new service processor/PCI backplane for damage. 2. Taking care not to hit the connectors against the processor subsystem chassis, use both hands to carefully place the service processor/PCI backplane down into the processor subsystem drawer. Align the mounting posts so that the holes in the backplane fit over the mounting posts.
Page 644 3. If you are replacing a service processor/PCI backplane, make sure you set the time and date using the operating system date command or smitty in AIX. Note: To restore the service processor settings and to set the date and time using service processor (if the system is running Linux), see “Restoring Service Processor Settings”...
Page 645 System Backplane This procedure is for removing and replacing the system board. Removal To replace a system backplane, do the following: 1. Turn off power as described in “Powering Off and Powering On the System” on page 545. 2. Perform the removal procedures under “Service Processor/PCI Backplane” on page 619. 3.
Page 646 Battery CAUTION: A lithium battery can cause fire, explosion, or a severe burn. Do not recharge, disassemble, heat above 100 degrees C (212 degrees F), solder directly to the cell, incinerate, or expose cell contents to water. Keep away from children. Replace only with the part number specified for your system. Use of another battery may represent a risk of fire or explosion.
Page 647 2. Before a disk can be removed from a volume group, all data must be backed up and the data removed from the disk to be replaced. Use AIX Logical Volume Manager to perform this task. Documentation for the AIX operating system is available from the IBM Eserver pSeries Information Center at http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base. Select AIX documentation.
Page 648 13. See the AIX System Management Guide: Operating System and Devices to finish the drive configuration. Documentation for the AIX operating system is available from the IBM Eserver pSeries Information Center at http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base. Select AIX documentation. The AIX Documentation CD contains the base set of publications for the operating system, including system-management and end-user documentation.
Page 649 Removal Attention: The Linux operating system does not support these hot-pluggable procedures. Also, Linux does not support hot-plugging any hot-pluggable PCI adapters or devices. The system with Linux installed on one or more partitions must be shutdown and powered off before replacing any PCI adapter or device assigned to a Linux partition.
Page 650 Replacement Attention: The Linux operating system does not support these hot-pluggable procedures. Also, Linux does not support hot-plugging any hot-pluggable PCI adapters or devices. The system with Linux installed on one or more partitions must be shutdown and powered off before replacing any PCI adapter or device assigned to a Linux partition.
Page 651 SCSI Repeater Card Removal 1. Turn off the power as described in “Powering Off and Powering On the System” on page 545. 2. Remove the bezel from the processor subsystem by grasping the top of the bezel on either side, and pulling it outward.
Page 652 3. Perform the top cover removal procedure; see “Processor Subsystem Top Covers” on page 549. Note: Leave the system in the service position after removing the top covers. 4. Remove the disk drives and the disk drive fillers as described in the removal procedure under “Disk Drive Assembly”...
Page 653 8. Remove the flange screws from the front of the disk drive 4-pack. 1 SCSI and Power Cables 3 Flange Screws 2 Cage Screws 9. Remove the two cage screws from the lower-left and upper-right corners of the inside rear of disk drive 4-pack cage.
Page 654 Do not open the drive; no user adjustments or serviceable parts are inside. 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.
Page 655 10. Pull the release levers that hold the SCSI media drive assembly in the subsystem. 1 Media drive 2 Release levers 11. Carefully, holding the release levers, pull the drive assembly straight out until you can remove the drive from the subsystem. Replacement Attention: To precondition the media bay to allow hot-plug replacement of a media drive, the hot-plug...
Page 656 1 Media drive 2 Release levers 2. When you are sure that the drive is seated in the media bay, press Enter . 3. Press F3 to return to the SCSI Hot Swap Manager. 4. Choose Configure Added/Replaced Devices. 5. Press F10 to exit diagnostics. 6.
Page 657 Media Cage Removal 1. Turn off the power as described in “Powering Off and Powering On the System” on page 545. 2. Remove the bezel from the processor subsystem by grasping top of the bezel on either side, and pull it outward.
Page 658 Diskette Drive Removal 1. Turn off the power as described in “Powering Off and Powering On the System” on page 545. 2. Remove the bezel from the processor subsystem by grasping top of the bezel on either side, and pull it outward.
Page 659 Operator Panel The operator panel can be removed and replaced using the following procedures: Removal 1. Turn off power as described in “Powering Off and Powering On the System” on page 545. 2. Remove the bezel from the processor subsystem by grasping top of the bezel on either side, and pull it outward.
Page 660 2. Remove the VPD module and the CUoD capacity card (if installed) from the old operator panel and insert them in the new operator panel. Install the CUoD capacity card in connector J5 of the operator panel connector card. Make sure you insert the VPD module in the same position as it was in the old operator panel.
Page 661 CUoD Capacity Card The capacity card can be removed and replaced using the following procedures: Removal 1. Turn off power as described in “Powering Off and Powering On the System” on page 545. 2. Perform the operator panel removal procedure; see “Operator Panel” on page 639. 3.
Page 662 The activate CUoD Processors window displays. c. Enter the 34-character string of zeros (0s) into the Activation Code field. d. Reboot the system and return control of the system to the customer. 6. Service support will ask for system information to generate an activation code. To access this information, complete the following steps: a.
Page 663 The Activate CUoD Processors window displays. 8. Type the 34-character activation code that service support dictates to you into the Activation Code field. 9. Return to the Processor Capacity Settings window by completing steps a and b in 6 on page 642. Verify that the number of processors shown in this window match the number of processors service support tells you the customer is entitled to.
Page 664 Power Supplies Use the following procedures to remove or replace a processor-subsystem power supply. Attention: The processor-subsystem power supplies are replaced concurrently with the system operational when the remove and replace instructions are followed. Check for FRU redundancy to determine if the repair can be performed concurrently. If you cannot determine redundancy, delay the repair until the system can be shut down.
Page 665 Power Distribution Assembly Use the following procedures to remove or replace a power distribution assembly. Removal 1. Turn off power as described in “Powering Off and Powering On the System” on page 545. 2. Perform the removal procedures under “System Backplane” on page 625. 3.
Page 666 EserverpSeries 650 Service Guide...
Page 667 Chapter 10. Parts Information This chapter contains parts information for the Eserver pSeries 650.
Page 668 7038 Model 6M2 Processor Subsystem Parts information for the processor subsystem chassis follows: Front View EserverpSeries 650 Service Guide...
Page 669 Index Part Number Units Per Assy Description 34G6909 Mounting screws, system backplane 00P5794 System backplane assembly 34G6909 Mounting screw, system backplane 21P5195 Flex cable assembly 75G2878 Mounting screws, system unit bottom 53P1881 System unit bottom cover 21P5735 Chassis 53P0874 Cover interlock switch 34G6909 Interlock switch retaining screw 75G2878...
Page 670 Rear View EserverpSeries 650 Service Guide...
Page 671 Index Part Number Units Per Assy Description 21P8169 Mounting screw, processor chassis 21P5783 Processor card cage 21P5195 See page 649 Flex cable assembly (same part as shown on 649) 75G2878 Mounting screw, processor card cage to rear bulkhead 07L7411 Standoff, external SCSI cable 75G2878 Mounting screw 21P5204...
Page 672 Internal Cables EserverpSeries 650 Service Guide...
Page 673 Index Part Number Units Per Assy Description Reference only PCI slot plugging bracket (part of the service processor/PCI backplane assembly) 21P5195 See page 649 Flex cable assembly (same part shown on 649) 21P5196 Service processor/PCI backplane power cable See page 651 Service processor/PCI backplane (same part shown on 651) 21P5197...
Page 674 Processor Bus Connector, Power, and Cooling EserverpSeries 650 Service Guide...
Page 675 (FC 4962) type A-F 53P5450* As needed Bracket for Gigabit Ethernet PCI-X Adapter (FC 5700), 10/100/1000 Base-TX Ethernet PCI-X Adapter (FC 5701), IBM 2-Port 10/100/1000 Base-TX Ethernet PCI-X Adapter (FC 5706), or IBM 2-Port Gigabit Ethernet-SX PCI-X Adapter (FC 5707) 44P2661*...
Page 676 Media Bays and Disk Bays EserverpSeries 650 Service Guide...
Page 677 Index Part Number Units Per Assy Description 97P2677 See page 649 Power distribution cable harness (same part shown on 649) 21P5205 SCSI cable, media backplane to disk-drive backplane 21P5199 See page 653 SCSI cable, internal (same part shown on 653) 21P5882 Up to 1 Disk drive cage and backplane (one four-pack,...
Page 678 Cooling and Diskette Drive EserverpSeries 650 Service Guide...
Page 679 Index Part Number Units Per Assy Description 21P5197 See page 653 Diskette drive signal cable (same part shown on 653) 21P5892 Slim diskette drive 75G2878 Mounting screw, diskette drive 21P4490 Fan assembly, processor subsystem 53P4334 Air baffle 52P4069 Spring gasket Chapter 10.
Page 680 Processor Cards and Memory EserverpSeries 650 Service Guide...
Page 681 Index Part Number Units Per Assy Description 97P4099 Up to 4 1.2 GHz Processor board (firmware level 3K040323 or later required) 00P5506 Up to 4 1.45 GHz Processor board (firmware level 3K040323 or later required) 80P3168 Up to 3 1.45 GHz CUoD Processor board (firmware level 3K040323 or later required) 53P3226 Up to 32...
Page 682 Processor Subsystem Disks and Media EserverpSeries 650 Service Guide...
Page 683 Index Part Number Units Per Assy Description 53P1880 Processor top cover See note Up to 4 Disk drives 44H8406 Media filler See note Media device 97P2908 Operator panel (same part shown on page 657) Note: See Eserver pSeries Diagnostic Information for Multiple Bus Systems for part numbers. The following table lists parts not shown in the previous illustration.
Page 684 Processor Subsystem Covers and Bezel EserverpSeries 650 Service Guide...
Page 685 Index Part Number Units Per Assy Description 21P5308 Internal processor EMC cover 21P5309 PCI access cover 21P8177 Front cover Chapter 10. Parts Information...
Page 686 Processor Subsystem Internal Cables Op Panel Disk Service Processor/ Drives PCI Backplane Diskette System Backplane Media 11 12 Disk Drives Disk Drives Media System Backplane EserverpSeries 650 Service Guide...
Page 687 Index Part Number Units Per Assy Description 21P5199 See page 653 SCSI cable, Internal (same part shown on page 653) 97P2677 See page 649 Power distribution cable harness (same part shown on page 649) Note: If the system has a split disk drive backplane, the signal cable that normally connects to middle connector of the disk drive backplane is connected to the C position on the...
Page 688 SPCN, RIO, and Rack Beacon Cables Index Part Number Units Per Assy Description 53P2231 Up to 12 Rack beacon junction box, 7-port mini connector (4693) 53P2237 Up to 12 Rack beacon connector cable, subsystem to junction box, 4-pin std to 4-pin mini connector, 3 meter (4691) 07H6655 As needed Velcro tape...
Page 689 Keyboards and Mouse Index Number FRU Part Number Units Per Assy Description 24P0440 Keyboard, 101 US English (ID 103P) USB 24P0450 Keyboard, 101 French (ID 189) USB 24P0458 Keyboard, 101 Italian (ID 142) USB 24P0453 Keyboard, 101 German/Austrian (ID 129) USB 24P0476 Keyboard, 101 UK English (ID 166) USB 24P0470...
Page 690 I/O Subsystem Parts For information related to parts for the 7311 Model D10 I/O Subsystem. or the 7311 Model D20 I/O Subsystem, see the pSeries 7311 Model D10 and Model D20 Service Guide, order number SA38-0627. EserverpSeries 650 Service Guide...
Page 691 Chapter 11. SRNs for Linux The x in the following group of SRNs is encoded as follows: 8 4 2 1 | | | | | | | Replace all FRUs listed | | Hot swap supported | Software might be the cause Reserved Note: Some SRNs in this chapter may have 4 rather than 3 digits after the dash (-).
Page 692 Description and Action Service Request Number Description: System bus parity error. Action: Use “MAP 1230: Linux Platform Error Problem Resolution” on page 89. A01-07x Description: System bus protocol/transfer error. Action: Use “MAP 1230: Linux Platform Error Problem Resolution” on page 89. A01-08x Description: Error log analysis indicates an error detected by the memory controller, but the failure could not be isolated.
Page 693 Description and Action Service Request Number Description: I/O bridge/device time-out, access or other error. Action: Use “MAP 1230: Linux Platform Error Problem Resolution” on page 89. A03-03x Description: I/O bridge/device internal error. Action: Use “MAP 1230: Linux Platform Error Problem Resolution” on page 89. A03-04x Description: I/O Error on non-PCI bus.
Page 694 Description and Action Service Request Number Description: Sensor indicates an abnormally high internal temperature. Action: Verify that: A05-05x 1. The room ambient temperature is within the system operating environment. 2. There is unrestricted air flow around the system. 3. All system covers are closed. 4.
Page 695 Description and Action Service Request Number A0D-01x Note: Ensure that the system IPLROS and Service Processor are at the latest firmware level before removing any parts from the system. Description: Time-out communication response from Service Processor. Action: Use “MAP 1230: Linux Platform Error Problem Resolution”...
Page 696 Description and Action Service Request Number Description: Service Processor detected a surveillance time-out. Action: Use “MAP 1230: Linux Platform Error Problem Resolution” on page 89. A0D-24x Description: Power Control Network general connection failure. Action: Use “MAP 1230: Linux Platform Error Problem Resolution” on page 89. A0D-25x Description: Power Control Network node failure.
Page 697 Description and Action Service Request Number Description: A non-critical error has been detected, an external cache parity or multi-bit ECC error. Action: Schedule deferred maintenance. Use “MAP 1230: Linux Platform Error A11-03x Problem Resolution” on page 89. Description: A non-critical error has been detected, an external cache ECC single-bit error. Action: Schedule deferred maintenance.
Page 698 Description and Action Service Request Number Description: Recoverable errors on resource indicate a trend toward an unrecoverable error. However, the resource could not be deconfigured and is still in use. The system is operating A11-550 with the potential for an unrecoverable error. Action: If repair is not immediately available, reboot and the resource will be deconfigured.
Page 699 Description and Action Service Request Number Description: A non-critical error has been detected, a system bus time-out error. Action: Schedule deferred maintenance. Use “MAP 1230: Linux Platform Error Problem Resolution” A12-10x on page 89. Description: A non-critical error has been detected, a system bus protocol/transfer error. Action: Schedule deferred maintenance.
Page 700 Description and Action Service Request Number Description: A non-critical error has been detected, a system bus data parity error. Action: Schedule deferred maintenance. Use “MAP 1230: Linux Platform Error Problem Resolution” A13-09x on page 89. Description: A non-critical error has been detected, a mezzanine bus time-out error. Action: Schedule deferred maintenance.
Page 701 Description and Action Service Request Number Description: Sensor detected redundant power supply failure. Action: Schedule deferred maintenance. Use “MAP 1230: Linux Platform Error Problem Resolution” on page 89. A15-12x Description: Sensor detected a redundant FRU that has failed. Action: Schedule deferred maintenance.
Page 702 Description and Action Service Request Number Description: A non-critical error has been detected, an internal service processor memory error. Action: Schedule deferred maintenance. Use “MAP 1230: Linux Platform Error A1D-04x Problem Resolution” on page 89. Description: A non-critical error has been detected, a service processor error accessing special registers.
Page 703 Description and Action Service Request Number Description: A non-critical error has been detected: Loss of heart beat from Service Processor. Action: Schedule deferred maintenance. Use “MAP 1230: Linux Platform Error A1D-23x Problem Resolution” on page 89. Description: A non-critical error has been detected, a service processor detected a surveillance time-out.
Page 704 Description and Action Service Request Number Description: Recoverable errors on resource indicate a trend toward an unrecoverable error. However, the resource could not be deconfigured and is still in use. The system is operating A1D-50x with the potential for an unrecoverable error. Action: If repair is not immediately available, reboot and the resource will be deconfigured.
Page 705 Chapter 12. Fault and Attention LEDs This chapter contains information about fault and attention LEDs, which assist in identifying failing components in your system. Component LEDs Individual LEDs are located on or near the failing components. The LEDs are located either on the component itself or on the carrier of the component (for example, memory card, fan, memory module, CPU).
Page 706 Unit Location Viewable LED Color OFF Blink (FRU) Function Location Power and Packaging LEDs Rack Amber Normal Fault Identify External Rack Summary Top of Rack Indicator AC Input External Front Green No Input AC Good Fault Processor External Front Amber Normal Fault Identify...
Page 707 Unit Location Viewable LED Color OFF Blink (FRU) Function Location Power and Packaging LEDs Processor No LED connector Backplane Disk Drive No LED Backplane Media No LED Backplane Port LED Indicators Top of Each Rio Ports Identify External External Back Amber Normal Identify...
Page 708 Resetting the LEDs After the repair action is completed, do the following: 1. Log in as root user. 2. At the command line, type diag. 3. Select Task Selection. 4. Select Log Repair Action. 5. Select the device that was repaired. 6.
Page 709 Recycling facilities may not be available in your area. In the United States, IBM has established a collection process for reuse, recycling, or proper disposal of used sealed lead acid, nickel cadmium and nickel metal hydride batteries and battery packs from IBM equipment. For information on proper disposal of the batteries in this product, please contact IBM at 1-800-426-4333.
Page 710 Acoustical Noise Emissions The equivalent continuous A-weighted sound pressure level at workstations (emission sound pressure level at the 1-meter bystander positions) does not exceed 70 dB(A). Der Geräuschpegel der Einheit ist kleiner oder gleich 70 db(A). Declared Acoustical Noise Emissions Acoustical Characteristic Product Configuration Declared A-Weighted Sound Power...
Page 711 Appendix B. Notices This information was developed for products and services offered in the U.S.A. The manufacturer may not offer the products, services, or features discussed in this document in other countries. Consult the manufacturer’s representative for information on the products and services currently available in your area.
Page 712 EserverpSeries 650 Service Guide...
Page 713 Attention: This procedure applies to modems attached to the serial ports (S1 and S2) on the system drawer. It does not affect the operation of the modem attached to the IBM Hardware Management Console for pSeries (HMC). The call-out function is usually handled by the Service Focal Point application running on the HMC.
Page 714 Testing the Setup This section contains sample testing procedures to help ensure your setup is working. These tests include communicating with the server operating system. Before you start, ensure that the necessary serial port(s) is configured. If you need assistance, refer to “Serial Port Configuration” on page 695.
Page 715 Testing Call-Out During the setup, you entered your phone numbers for the pager and customer voice. These numbers are used for this test. 1. Your remote terminal is disconnected as a result of the Call-In test. 2. Call your server again. 3.
Page 716 EserverpSeries 650 Service Guide...
Page 717 This appendix applies only to modems attached to the serial ports (S1 and S2) on the primary I/O book (location U1.18-P1-H2). These configuration files do not apply to the modem attached to the IBM Hardware Management Console for pSeries (HMC).
Page 718 If Yes, use modem configuration file modem_m0.cfg and go to step 7. Note: The IBM 7852-400 modem has DIP switches on the right side of the unit. See “IBM 7852-400 DIP Switch Settings” on page 700 for the correct switch settings.
Page 719 Some modems, such as the IBM 7857-017, are not designed for the paging function. Although they can be used for paging, they 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 causes the service processor to retry, continuing to place pager calls for the number of retries specified in the Call-Out Policy Setup Menu.
Page 720 4. Save the changes. IBM 7852-400 DIP Switch Settings If you are using a 7852-400 modem to enable service processor communications, for proper operation, the dual inline package (DIP) switches must be set according to the following table:...
Page 721 Xon/Xoff Modems Some early modems assume software flow control (Xon/Xoff) between the computer and the modem. Modems with this design send extra characters during and after the transmitted data. The service processor cannot accept these extra characters. If your configuration includes such a modem, your functional results may be unpredictable.
Page 722 Ring Detection Most modems produce an interrupt request each time they detect a ring signal. Some modems generate an interrupt only on the first ring signal that they receive. AT&T DataPort 2001 is an example of such a modem. The service processor uses the ring interrupt request to count the number of rings when Ring Indicate Power-On (RIPO) is enabled.
Page 723 Transfer of a Modem Session Because many modem command variations exist, the sample modem configuration files located at the end of this appendix have been written to capture the largest number of workable modem settings. The modem command &Dn (where n is a number) generally sets the modem response to the Data Terminal Ready (DTR) signal from the server’s serial port.
Page 724 Recovery Strategy The recovery strategy consists of making two calls to establish a remote session. This solution is the easiest to implement and allows more freedom for configuring your server’s serial ports. To set up a remote terminal session, dial into the service processor and start the system. After the operating system is loaded and initialized, the connection will be dropped.
Page 725 # Licensed Materials - Property of IBM # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # The modem has configuration switches. They should be set to the # factory default settings, except switches 11 and 12.
Page 726 "19\r" or "13\r" or "12\r" or "1\r" busy "7\r" timeout 60 done disconnect: delay 2 # Separate from previous data. send "+++" # Assure command mode. delay 2 # Allow mode switching delay. send "ATH0T\r" # Set modem switch-hook down # (i.e., hang up).
Page 727 expect "0\r" or "OK\r\n" timeout 2 # Confirm commands successful. send "ATV0S0=0\r" # Numeric response code # Auto Answer OFF expect "0\r" timeout 2 # Confirm commands successful. done error: # Handle unexpected modem # responses. expect "8\r" or "7\r" or "6\r" or "4\r" or "3\r" delay 2 done Appendix D.
Page 728 Sample File modem_m1.cfg # COMPONENT_NAME: (ESPSETUP) ENTRY SERVICE PROCESSOR SETUP modem_m1 # FUNCTIONS: Modem configuration file specifically for IBM 7857-017 modem with # Auto-Reliable feature. This feature must be turned off for Catcher calls. # This example uses the AT&F reset command to choose the factory defaults.
Page 729 send "ATE0Q1\r" # Initialize modem: Echo OFF, # Disable responses. ignore "0\r" timeout 1 done condin: send "AT&F*E0E0\r" # Reset to factory defaults. # *E0=data compression disabled # E0=echo disabled ignore "0\r" or "OK\r\n" timeout 2 # Ignore modem response. send "AT#F0*Q2\r"...
Page 730 # Licensed Materials - Property of IBM # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # If the modem has configuration switches, they should be set to the # factory default settings.
Page 731 done retry: send "A/" # Repeat the previous command. # Expect a connection response. expect "16\r" or "15\r" or "14\r" or "12\r" or "10\r" or "5\r" or "1\r" busy "7\r" timeout 60 done disconnect: delay 2 # Separate from previous data. send "+++"...
Page 732 error: # Handle unexpected modem # responses. expect "8\r" or "7\r" or "6\r" or "4\r" or "3\r" delay 2 done EserverpSeries 650 Service Guide...
Page 733 # Licensed Materials - Property of IBM # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # If the modem has configuration switches, they should be set to the # factory default settings.
Page 734 timeout 60 done retry: send "A/" # Repeat the previous command. # Expect a connection response. expect "16\r" or "15\r" or "14\r" or "12\r" or "10\r" or "5\r" or "1\r" busy "7\r" timeout 60 done disconnect: delay 2 # Separate from previous data. send "+++"...
Page 735 done # RI Power On enabled. error: # Handle unexpected modem # responses. expect "8\r" or "7\r" or "6\r" or "4\r" or "3\r" delay 2 done Appendix D. Modem Configurations...
Page 736 # Licensed Materials - Property of IBM # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # If the modem has configuration switches, they should be set to the # factory default settings.
Page 737 connect: send "ATDT%N\r" # Tone dialing command. # %N from Call Home setup. # Expect a connection response. expect "16\r" or "15\r" or "14\r" or "12\r" or "10\r" or "5\r" or "1\r" busy "7\r" timeout 60 done retry: send "A/" # Repeat the previous command.
Page 738 ignore "0\r" or "OK\r\n" timeout 2 # Ignore modem response. send "ATE0T\r" # Initialize modem: Echo OFF, expect "0\r" or "OK\r\n" timeout 2 # Enable responses (Numeric), send "ATQ0V0X0T\r" # Limit response codes. expect "0\r" timeout 2 # Confirm commands successful. send "ATS0=0\r"...
Page 739 # Licensed Materials - Property of IBM # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # If the modem has configuration switches, they should be set to the # factory default settings.
Page 740 done connect: send "ATDT%N\r" # Tone dialing command. # %N from Call Home setup. # Expect a connection response. expect "16\r" or "15\r" or "14\r" or "12\r" or "10\r" or "5\r" or "1\r" busy "7\r" timeout 60 done retry: send "A/" # Repeat the previous command.
Page 741 done ripo: send "AT&F0Q0T\r" # Reset modem. Select profile 0 ignore "0\r" or "OK\r\n" timeout 2 # Ignore modem response. send "ATE0T\r" # Initialize modem: Echo OFF, expect "0\r" or "OK\r\n" timeout 2 # Enable responses (Numeric), send "ATQ0V0X0T\r" # Limit response codes. expect "0\r"...
Page 742 # Licensed Materials - Property of IBM # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # If the modem has configuration switches, they should be set to the # factory default settings.
Page 743 connect: send "ATDT%N\r" # Tone dialing command. # %N from Call Home setup. # Expect a connection response. expect "16\r" or "15\r" or "14\r" or "12\r" or "10\r" or "5\r" or "1\r" busy "7\r" timeout 60 done retry: send "A/" # Repeat the previous command.
Page 744 ripo: send "AT&F1Q0T\r" # Reset modem. Select profile 1 ignore "0\r" or "OK\r\n" timeout 2 # Ignore modem response. send "ATE0T\r" # Initialize modem: Echo OFF, expect "0\r" or "OK\r\n" timeout 2 # Enable responses (Numeric), send "ATQ0V0X0T\r" # Limit response codes. expect "0\r"...
Page 745 Index configuration client 474 about this book xvii modem accessing information xvii customizing files 700 acoustical file selection 698 noise sample files 697 emissions 690 specific files 697 adapter cassette NIM server 473 removing 552 service processor replacing 555 serial port 695 adding configurations FRUs 71...
Page 746 documentation AIX 471, 559, 561, 564, 627, 628 handling static-sensitive devices 543 dvd-ram removal 634 hardware service functions activating and deactivating FRU LEDs 72 attention LED 74 entry MAP 63, 75 resetting the system attention LED 74 environmental HMC (hardware management console) design 689 system error interrogation 72 notices 689...
Page 747 location code menu (continued) format 28 modem configuration 501 location codes 28, 42 OS surveillance AIX 30 setup 483 physical 28 power control network utilities 493 location codess privileged AIX 32 user 479 D10 I/O subsystem, rear 36 processor configuration/deconfiguration 491 FRU identify LEDs 42 reboot/restart policy setup 487 location code reference tables 32...
Page 748 operational phases powering on 545 service processor 522 powering on and off 545 operator panel error codes 248 preface xvii operator panel removal 639 primary console 704 OS defined restart policy 487 primary I/O book 619 overview 1 privileged user menus 479 diagnostics 63 problem determination MAP 84 hot-pluggable PCI adapter 564...
Page 749 removal and replacement procedures (continued) Service Focal Point (continued) starting the system 546 viewing and adding serviceable event comments 70 stopping the system without an HMC 545 viewing error details 70 removal procedures 541 viewing service processor error details 70 hot-plug disk drives 629 viewing serviceable event details 70 removing a PCI adapter cassette 552...
Page 750 service processor (continued) system management services (continued) telephone setup menu 504 password, privileged-access 530 test 693 SCSI settings, change 534 using service processor 66 select console 535 service processor checkpoints 189 select language 529 service processor error codes 289 settings, display current 541 serviceable event settings, restore default 541 viewing partition information 72...
Page 751 Thank you for your responses. May we contact you? h Yes h No When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you. Name...
Page 752 Readers’ Comments — We’d Like to Hear from You Cut or Fold Along Line SA38-0612-02 Fold and Tape Please do not staple Fold and Tape _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ NO POSTAGE NECESSARY IF MAILED IN THE...
Page 754 September 2003 SA38-0612-02...

This manual is also suitable for:

Eserver p650

IBM eserver p Series Service Manual

Chapter 1. Reference Information

Chapter 2. Diagnostics Overview

Chapter 3. Maintenance Analysis Procedures (Maps)

Chapter 4. Checkpoints

Chapter 5. Error Code to FRU Index

Chapter 6. Using the Online and Standalone Diagnostics

Quick Links

Related Manuals for IBM eserver p Series

Summary of Contents for IBM eserver p Series

This manual is also suitable for:

Table of Contents