Page 1 ERserver pSeries 670 Service Guide SA38-0615-03...
Page 3 ERserver pSeries 670 Service Guide SA38-0615-03...
Page 4 © Copyright International Business Machines Corporation, 2001, 2003. All rights reserved. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth is GSA ADP Schedule Contract with IBM Corp.
Page 5: Table Of Contents
Chapter 1. Reference Information ......1 pSeries 670 Overview ....... 1 Hardware Management Console (HMC).
Page 6 ....... 109 Service Agent for the Eserver pSeries 670 ..... . 110 Using the Service Processor and Service Agent Features .
Page 7 Quick Entry MAP Table of Contents ......113 MAP 1020: Problem Determination ......120 Purpose of This MAP .
Page 8 Call-out Test ....... . . 742 Service Processor Parameters in Service Mode (Full System Partition) ... . 742 Eserver pSeries 670 Service Guide...
Page 9 System Power-On Methods ......742 Service Processor Reboot/Restart Recovery ..... . 744 Boot (IPL) Speed .
Page 10 Rear ........956 viii Eserver pSeries 670 Service Guide...
Page 11 Customizing the Modem Configuration Files ..... 974 IBM 7852-400 DIP Switch Settings ......974 Xon/Xoff Modems .
Page 12 Eserver pSeries 670 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 xii v 144 v 778 v 797 v 925 A caution notice indicates the presence of a hazard that has the potential of causing moderate or minor personal injury.
Page 14 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. Eserver pSeries 670 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 Eserver pSeries 670 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 Eserver pSeries 670 Service Guide...
Page 19: About This Book
About This Book This book provides maintenance information that is specific to the Eserver pSeries 670, as well as adapters, and attached devices that do not have their own service information. It also contains Maintenance Analysis Procedures (MAPs) that are not common to other systems.
Page 20: Trademarks
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: v AIX v e (logo) v pSeries v RS/6000 v LANstreamer Other company, product, and service names may be trademarks or service marks of others. xviii Eserver pSeries 670 Service Guide...
Page 21: Chapter 1. Reference Information
Chapter 1. Reference Information This chapter provides an overview of the Eserver pSeries 670, including a logical description and a physical overview of the system. Additional details pertaining to the server are also provided. They include the following: v Memory overview and ordering rules...
Page 22 64-bit PCI adapters. Slots 8 through 10 are 64-bit 5 V dc slots, running at 33 MHz. The media subsystem provides space for up to three media devices (diskette drive, CD-ROM drive, and optional tape drive or DVD-RAM) in the front and two additional optional devices in the rear. Eserver pSeries 670 Service Guide...
Page 23: Hardware Management Console (Hmc)
An entry I/O drawer is available that is a 4 EIA-unit- high drawer containing 1 I/O board (10 PCI slots maximum), 1 I/O planar assembly, up to 8 disk drives, 2 DASD backplanes, a midplane card, 4 cooling fans, and 2 power supplies (which are independent of the bulk power assembly). There can only be one of these drawers per system and it must be in position 1.
Page 24: Partition Requirements
Keep this in mind when you record the amount of memory used when you are completing the planning worksheets in the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590.
Page 25: Getting Started
IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590. v If you need to add or change a partition name, see the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590.
Page 26 Note: You must further configure Service Agent to handle notifications sent by Service Focal Point. For more information about Service Agent, see the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590.refer to the Hardware Management Console Installation and Operations Guide, order number SA38-0590.
Page 27 2. In the Navigation area, double-click the Service Focal Point icon. 3. In the Contents area, select Service Focal Point Settings. 4. The Service Focal Point Settings window opens. Select the Surveillance Notification tab at the top of the window. 5.
Page 28 Updating Field Replaceable Unit (FRU) Information: This task allows you to update the FRU information you changed or modified as a result of this serviceable event. From this panel, you can also activate and deactivate LEDs and search for other serviceable events that contain the same FRU entries. Eserver pSeries 670 Service Guide...
Page 29 To update FRU information, do the following: 1. Perform the steps in “Viewing Serviceable Event Details” on page 7. 2. Click FRU Information. The Update FRU Information window opens. The lower table shows any parts that you have replaced or added during your current update session but that have not been committed to the serviceable event.
Page 30: Capacity Upgrade On Demand
For further information about activating processor CUoD on your system, refer to “Activation Process for CUoD Features” on page 13, or refer to the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590, that was delivered with your hardware management console.
Page 31: Trial Capacity On Demand
For further information about activating and deactivating On/Off Capacity on Demand on your system, refer to “Activation Process for CUoD Features” on page 13, or refer to the IBM Hardware Management Console for pSeries Installation and Operations Guide that was delivered with your hardware management console.
Page 32: Software Licenses And Processor Cuod
Activating a processor may change the terms and conditions for applications that you use on your server. To determine if the license terms and conditions requirements change based on hardware configuration, consult the application documentation. Eserver pSeries 670 Service Guide...
Page 33: Activation Process For Cuod Features
3. The sales representative places an order to the system coordinator or feature coordinator for the features you request. The order specifies the upgrade features to add. 4. To process the order, you must send the system Vital Product Data (VPD) to IBM in either of the following ways: v Electronic process (Electronic Service Agent) v Web-based VPD entry.
Page 34: Pseries 670 Data Flow
670 Data Flow The following figure shows the data flow for the system. Eserver pSeries 670 Service Guide...
Page 35: Power-On Self-Test
Power-On Self-Test After power is turned on and before the operating system is loaded, the partition does a power-on self-test (POST). This test performs checks to ensure that the hardware is functioning correctly before the operating system is loaded. During the POST, a POST screen displays, and POST indicators display on the virtual terminal.
Page 36: Key
To exit from the open firmware command prompt, type reset-all or power off the system and reboot. pSeries 670 System Locations The pSeries 670 system consists of a minimum of four subsystems in one rack as follows: v Processor subsystem...
Page 37 In each of the following figures, the minimum system configuration is shown on the left. The minimum system configuration with the integrated battery feature (IBF) is shown on the right in each of the figures. 1 Rack 5 Media Subsystem 2 Bulk Power Assembly 6 Optional Integrated Battery Feature 3 UEPO Switch...
Page 38 Note: The I/O subsystem fan assemblies are inside the I/O subsystems, positioned from left to right behind the DASD 4-packs in order of fan assembly 1, fan assembly 2, fan assembly 3, and fan assembly 4. Eserver pSeries 670 Service Guide...
Page 39: Uepo Switch
UEPO Switch The UEPO (Unit Emergency Power Off) switch is accessible through the external cover. The switch contains a room emergency power off (EPO) interlock connector and bypass switch, a dual element rack service amber LED (one element driven per bulk power controller, a service complete button (white) and start service button (green), an off button and four thermistors for BPC ambient temperature sensing.
Page 40: 7040 Model 671 Processor Subsystem Locations
7040 Model 671 Processor Subsystem Front View Note: For slot assignments, see “Memory to Processor Relationships” on page 49. 1 Processor Subsystem Chassis 5 Fan Controller 2 Blank Cover 6 Fan Chassis 3 Inner Memory Book 7 Fan Filter 4 Fan Eserver pSeries 670 Service Guide...
Page 41 7040 Model 671 Processor Subsystem Rear View 1 I/O Book – Slot 1 8 Reserved 2 DCA Book 1 9 I/O Book 2 - Slot 2 (Inner Connectors) 3 DCA Book 2 10 I/O Book 2 - Slot 2 (Outer Connectors) 4 Capacitor Book 5 DCA Book 3 6 Reserved...
Page 42: Media Subsystem Locations
The following figures show locations for devices installed in the media subsystem, and the SCSI IDs for the media devices. Note: The SCSI IDs shown for media indicate how installed devices are set when shipped from the factory. Eserver pSeries 670 Service Guide...
Page 43 Media Subsystem Front View SCSI SCSI 1 Diskette Drive 3 Optional Media Drive (4 mm Tape, CD-ROM, or DVD-RAM), SCSI Address 2 CD-ROM Drive, SCSI Address 05 4 Operator Panel Media Subsystem Rear View Note: DVD-RAM and 4-mm tape drives can be located in the rear of the media subsystem only if the room is maintained at a nominal room temperature of 24C (75.2F).
Page 44: Disturbance Or System Attention Led
The system attention LED lights on solid when an event occurs that either needs customer intervention or IBM service. The system attention LED is turned on when an entry is made in the service processor error log. The error entry is transmitted to the following:...
Page 45: Resetting The System Attention Led
IBM Hardware Management Console for pSeries Installation and Operations Guide. Note: For information on these Service Focal Point settings, see ″Setting Up Surveillance and Enabling Surveillance Notifications″ in the IBM Hardware Management Console for pSeries Installation and Operations Guide.
Page 46 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.
Page 47: 7040 Model 61D I/O Subsystem Locations
7040 Model 61D I/O Subsystem Locations This section shows the locations for the I/O subsystem. A front view and a rear view with descriptions and locations for each part of the I/O subsystem are shown. 7040 Model 61D I/O Subsystem Front View 1 DASD 4-Pack 9 Drawer Fault/Identify LED (Amber) 2 DASD Disk Drive...
Page 48: 7040 Model 61D I/O Subsystem Rear View
4 I/O port connector 1 (Ux.y-P2/Q2) 10 I/O Subsystem Backplane Fault (Amber) 5 I/O port connector 0 (Ux.y-P2/Q1) 11 I/O Subsystem Backplane Power On (Green) 6 Media subsystem power connector 12 I/O LED (Currently Unused) (Ux.y-P2-V1/Q3) Eserver pSeries 670 Service Guide...
Page 49: I/O Subsystem Dasd Locations
I/O Subsystem DASD Locations The following figures show the DASD drive positions in an I/O subsystem. Note: The SCSI IDs are set when the drive is installed into the DASD 4-pack. 7040 Model 61D I/O Subsystem DASD Locations 1 Ux.y-P2/Z2-A8 9 Ux.y-P1/Z2-A8 2 Ux.y-P2/Z2-A9 10 Ux.y-P1/Z2-A9...
Page 50: I/O Subsystem Pci And Pci-X Phb And Pci And Pci-X Slot Locations
PCI- PCI PCI- PCI Bridge Bridge Bridge SCSI Media Subsystem Power Ultra3 Internal SCSI SCSI Ultra3 Controllers SCSI PCI Slot - 64 bit 66/33mhz 3.3V PCI Slot - 64 bit 33mhz 5.0V Media Subsystem Front Eserver pSeries 670 Service Guide...
Page 51: I/O Subsystem Internal Scsi Distribution
I/O Subsystem Internal SCSI Distribution DASD 4 pack DASD 4 pack Rear DASD 4 pack DASD 4 pack P=PCI-PCI bridge RP=RIO-PCI bridge IS=Internal SCSI Ultra 3 I/O Subsystem Power Distribution Fan 4 DCA 2 Power Supply Fan 2 Rear Fan 3 DCA 1 Power Supply Fan 1...
Page 52: Power Subsystem Locations
2 Bulk Power Distributor (BPD) 7 Connectors to IBF 3 Bulk Power Controller (BPC) 8 UEPO Power (PWR) LED UEPO Power Complete (CMPLT) LED 4 Bulk Power Fan (BPF) 9 BPC Power Good LED 5 Bulk Power Regulators (BPR) Eserver pSeries 670 Service Guide...
Page 53: Power Distribution Cabling
Power Distribution Cabling Power to the I/O subsystems, DCAs, Fans, and IBFs is connected from the bulk power distribution connectors to each subsystem through cables. The cable connectors are labeled on each end. The following describes the cables that connect from the BPC BPDs, and BPRs to the DCAs, fans, power supplies, I/O subsystems, and integrated battery features.
Page 54 A35-BPC-P04 to (AMD1-P01) J02 A35-BPC-J04 A09-MDA1-J01 A35-BPC-P04 to Red with white stripe (AMD1-P00) J01 A35-BPC-J06 A18-MDA3-J01 A35-BPC-P06 to Red with white stripe (AMD3-P00) J01 B35-BPC-J06 A18-MDA3-J02 B35-BPC-P06 to (AMD3-P01) J02 B35-BPC-J07 A18-MDA4-J02 B35-BPC-P07 to (AMD4-P00) J02 Eserver pSeries 670 Service Guide...
Page 55 From Description Label Color A35-BPC-J07 A18-MDA4-J01 B35-BPC-P07 to Red with white stripe (AMD4-P01) J01 B35-BPC-J02 UEPO Switch J01 B35-BPC-P02 to UEPO A35-BPC-J02 UEPO Switch J00 A35-BPC-P02 to UEPO Red with white stripe A35-BPR-J00 A13-IBF1-J01 A35-BPR-P00 to A13-IBF1-P00 B35-BPR-J00 B13-IBF1-J01 B35-BPR-P00 to B13-IBF1-P00 Note: * DCA 6 is populated only for the 32-way 1.7 GHz MCMs.
Page 56: I/O Subsystem Power Distribution Cabling
Green With Stripes A35P-BPD1B-P05 A01B-DCA2-P00 BPD1B to I/O Subsystem Green The following 4 rows apply to systems that are not configured with 32-way with 1.7 GHz MCMs. Integrated Battery Feature Locations 1 Connector to BPR Eserver pSeries 670 Service Guide...
Page 57: Subsystem Positioning And Cabling
Subsystem Positioning and Cabling This section describes subsystem positioning and cabling for the pSeries 670Eserver pSeries 670. Operator Panel Cable and Diskette Drive Cable to the Media Subsystem (Rear View) 1 Primary I/O Book 3 Diskette Drive Data Cable 2 Cable Connecting the Operator Panel to the...
Page 58: I/O Subsystem Positions, Fully Populated Rack (Rear View Without Ibf)
I/O Subsystem Positions, Fully Populated Rack (Rear View without IBF) C1 Primary Rack 2 Second I/O Subsystem Position 1 First I/O Subsystem Position 3 Third I/O Subsystem Position Eserver pSeries 670 Service Guide...
Page 59: I/O Subsystem Positions, Fully Populated Rack (Rear View With Ibfs)
I/O Subsystem Positions, Fully Populated Rack (Rear View with IBFs) C1 Rack 2 Second I/O Subsystem C2 I/O Book (Book 0) 3 Third I/O Subsystem 1 First I/O Subsystem 4B Two IBFs (primary rack), Position 4 Chapter 1. Reference Information...
Page 60: Rio And Rio-2 Cabling Rules
Note: If all I/O planars are connected to the CEC with one I/O planar loops, the maximum number of I/O subsystems connected to the system is reduced to 2, or four I/O planars (two I/O subsystems). Eserver pSeries 670 Service Guide...
Page 61: I/O Subsystem (One Side Of Subsystem 1 With Ibf) Rio Cabling To I/O Books, Two I/O Planar Loop Configuration
I/O Subsystem (One Side of Subsystem 1 with IBF) RIO Cabling to I/O Books, Two I/O Planar Loop Configuration Note: The following figure applies to CECs with RIO, or thumbscrew retention, connections. 1 Primary Rack 3 First I/O Subsystem (Minimum I/O, Single I/O Board Installed) 2 Primary I/O Book 4 Secondary I/O Book...
Page 62: I/O Subsystems (1 Through 3 ) Rio Cabling To I/O Books, Two I/O Planar Loop Configuration
Note: The following figure applies to CECs with RIO, or thumbscrew retention, connections. 1 Primary Rack 4 Second I/O Subsystem 2 Primary I/O Book 5 First I/O Subsystem 3 Third I/O Subsystem 6 Secondary I/O Book Eserver pSeries 670 Service Guide...
Page 63: I/O Subsystems (1 Through 3 ) Rio-2 Cabling To I/O Books, Two I/O Planar Loop Configuration
I/O Subsystems (1 through 3 ) RIO-2 Cabling to I/O Books, Two I/O Planar Loop Configuration Note: The following figure applies to CECs with RIO-2, or bayonette retention, connections. 1 Primary Rack 4 Second I/O Subsystem 2 Primary I/O Book 5 First I/O Subsystem 3 Third I/O Subsystem 6 Secondary I/O Book...
Page 64: I/O Subsystem (One Side Of Subsystem 1 With Ibf) Rio-2 Cabling To I/O Books, Two I/O Planar Loop Configuration
I/O Books, Two I/O Planar Loop Configuration Note: The following figure applies to CECs with RIO-2, or bayonette retention, connections. 1 Primary Rack 3 First I/O Subsystem (Minimum I/O, Single I/O Board Installed) 2 Primary I/O Book 4 Secondary I/O Book Eserver pSeries 670 Service Guide...
Page 65: I/O Subsystem (One Side Of Subsystem 1 With Ibf) Rio-2 Cabling To I/O Books, One I/O Planar Loop Configuration
I/O Subsystem (One Side of Subsystem 1 with IBF) RIO-2 Cabling to I/O Books, One I/O Planar Loop Configuration Note: The following figure applies to CECs with RIO-2, or bayonette retention, connections. 1 Primary Rack 3 First I/O Subsystem (Minimum I/O, Single I/O Board Installed) 2 Primary I/O Book 4 Secondary I/O Book...
Page 66: I/O Subsystems (1 Through 2) Rio-2 Cabling To I/O Books, One I/O Planar Loop Configuration
Note: The maximum number of I/O subsystems that can be attached in the one planar loop configuration is 2, or four I/O planars. Only eight RIO or RIO-2 ports are available in the CEC. The last two CEC RIO ports must only be used for single I/O planar loop connections. Eserver pSeries 670 Service Guide...
Page 67: Power And Scsi Cables To The Media Subsystem
Power and SCSI Cables to the Media Subsystem 1 Rack 5* SCSI Cable for Media Subsystem Rear Drives 2 Primary I/O Book 6 SCSI Cable for Media Subsystem Front Drives 3 Power Cable for Media Subsystem Front 7* Power Cable for Media Subsystem Rear Drives Drives 4 Rear of Media Subsystem Note: *Items 5 and 7 are for applications with a single I/O planar.
Page 68: Ibm Hardware Management Console For Eserver Pseries (Hmc) To The Primary I/O Book
Primary I/O Book To connect your HMC to the pSeries 670Eserver pSeries 670, connect the serial cable into serial port 1 located on the back of the HMC. Connect the other end of the serial cable into the HMC1 connector located on the primary I/O book in the managed system.
Page 69: System Memory
System Memory All of the main memory for the Eserver pSeries 670 consists of pluggable memory books in reserved slots with two memory controllers per book. The memory books are available in various sizes. Memory modules are not removable from the memory books. A minimum of 4 GB of memory must be installed for the system to operate.
Page 70 It is recommended that all systems have access to a 4-mm or 8-mm tape drive for submission of system dump information, if required. This function can be accomplished through locally attached or network-attached devices as appropriate. Eserver pSeries 670 Service Guide...
Page 71: I/O Subsystem Features
I/O Subsystem Features 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 power distribution board contained in the I/O subsystem.
Page 72 On, steady green System power connected System power connected System power connected and turned on and turned on and turned on Eserver pSeries 670 Service Guide...
Page 73: Logical And Physical Locations
Logical and Physical Locations The Eserver pSeries 670 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 operating system. There are no Linux-specific location codes, but physical location codes may appear in the Linux error logs.
Page 74: Multiple Fru Callout Instructions
If the system is logically partitioned, the HMC must be attached. You can use the HMC to enable any FRU identify LED to be flashed. See the IBM Hardware Management Console for pSeries Installation and Operations Guide for instructions on activating and deactivating a FRU identify LED.
Page 75: Aix Location Codes
AIX Location Codes Note: AIX location codes are not available if Linux is the operating system. The basic formats of the AIX location codes are as follows: v For non-SCSI devices/drives: AB-CD-EF-GH v For SCSI devices/drives: AB-CD-EF-G,H Non-SCSI Devices For planars (backplanes), cards, and non-SCSI devices, the location code is defined as follows: AB-CD-EF-GH | | | | | | | Device/FRU/Port ID...
Page 76: Scsi Devices
PCI adapter in first I/O subsystem, slot 1 (primary rack): – Physical location code U1.9-P1-I1 – AIX location code 2V-08 PCI adapter in fifth I/O subsystem, slot 1 (secondary rack): – Location Code U2.1-P1-I1 – AIX location Code 8V-08 Eserver pSeries 670 Service Guide...
Page 77: Aix And Physical Location Code Reference Tables
AIX location codes are not available when the operating system is Linux. The following illustrations show the location codes that are used to identify the major functional units in the pSeries 670 rack. The following figure shows the primary rack locations. Chapter 1. Reference Information...
Page 78 5 Clock Card, Location: U1.18-P1-X5 16 L3, Location: U1.18-P1-C18 6 L3, Location: U1.18-P1-C7 17 Reserved 7 Reserved 18 Reserved 8 Reserved 19 L3, Location: U1.18-P1-C14 9 L3, Location: U1.18-P1-C11 20 Reserved 10 Reserved 21 Reserved 11 L3, Location: U1.18-P1-C15 Eserver pSeries 670 Service Guide...
Page 79 The following tables contain location codes that are used to identify functional units in the Eserver pSeries 670 systems. Each table shows the locations for a physical part of the system. Location Physical Logical FRU Name Code Location Connection Connection...
Page 80 Bulk Power Distribution U1.35-P1-X2 I/O Subsystem -5A U1.35-P1-X2/Q1 Connector 0 I/O Subsystem 5 (DCA 1) I/O Subsystem -5A Cable U1.35-P1-X2/Q1# I/O Subsystem -5B U1.35-P1-X2/Q2 Connector 1 I/O Subsystem 5 (DCA 2) I/O Subsystem -5B Cable U1.35-P1-X2/Q2# Eserver pSeries 670 Service Guide...
Page 81 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Subsystem -6A U1.35-P1-X2/Q3 Connector 2 I/O Subsystem 6 (DCA 1) I/O Subsystem -6A Cable U1.35-P1-X2/Q3# I/O Subsystem -6B U1.35-P1-X2/Q4 Connector 3 I/O Subsystem 6 (DCA 2) I/O Subsystem -6B Cable U1.35-P1-X2/Q4# I/O Subsystem -7A U1.35-P1-X2/Q5 Connector 4...
Page 82 AC TO BPE (A) Line U1.35-P2/Q1 Cord Connector AC TO BPE (A) Line U1.35-P2/Q1# Cord Bulk Power Regulator U1.35-P2-V1 (BPR) 1 BPR 1 Connector U1.35-P2-V1/Q1 BPR 1 cable to IBF 1A U1.35-P2-V1/Q1# Bulk Power Distribution U1.35-P2-X2 Eserver pSeries 670 Service Guide...
Page 83 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Subsystem -5A U1.35-P2-X2/Q1 Connector 0 I/O Subsystem 5 (DCA 1) I/O Subsystem -5A Cable U1.35-P2-X2/Q1# I/O Subsystem -5B U1.35-P2-X2/Q2 Connector 1 I/O Subsystem 5 (DCA 2) I/O Subsystem -5B Cable U1.35-P2-X2/Q2# I/O Subsystem -6A U1.35-P2-X2/Q3 Connector 2...
Page 84 Bulk Power Regulator 3 U1.35-P2-V3 BPR 2 Connector U1.35-P2-V3/Q1 BPR 2 Cable to IBF 3A U1.35-P2-V3/Q1# Bulk Power Distribution U1.35-P2-X1 (Unused) SPARE U1.35-P2-X1/Q1 SPARE cable U1.35-P2-X1/Q1# SPARE U1.35-P2-X1/Q2 SPARE cable U1.35-P2-X1/Q2# SPARE U1.35-P2-X1/Q3 SPARE cable U1.35-P2-X1/Q3# SPARE U1.35-P2-X1/Q4 Eserver pSeries 670 Service Guide...
Page 85 Location Physical Logical FRU Name Code Location Connection Connection Code SPARE cable U1.35-P2-X1/Q4# SPARE U1.35-P2-X1/Q5 SPARE cable U1.35-P2-X1/Q5# SPARE U1.35-P2-X1/Q6 SPARE cable U1.35-P2-X1/Q6# SPARE U1.35-P2-X1/Q7 SPARE cable U1.35-P2-X1/Q7# SPARE U1.35-P2-X1/Q8 SPARE cable U1.35-P2-X1/Q8# SPARE U1.35-P2-X1/Q9 SPARE cable U1.35-P2-X1/Q9# SPARE U1.35-P2-X1/Q10 SPARE cable U1.35-P2-X1/Q10# Bulk Power Fan...
Page 86 Serial Port 1 Connector U1.18-P1-H2/S1 01-S1 Serial Port 1 Cable U1.18-P1-H2/S1# Serial Port 2 Connector U1.18-P1-H2/S2 01-S2 Serial Port 2 Cable U1.18-P1-H2/S2# HMC Serial Port 1 U1.18-P1-H2/S3 01-S3 Connector HMC Serial Port 1 Cable U1.18-P1-H2/S3# Eserver pSeries 670 Service Guide...
Page 87 Location Physical Logical FRU Name Code Location Connection Connection Code HMC Serial Port 2 U1.18-P1-H2/S4 01-S4 Connector HMC Serial Port 2 Cable U1.18-P1-H2/S4# Debug Port Only U1.18-P1-H2/R1 01-R1 Operator Panel U1.18-P1-H2/Q7 Connector Diskette Drive Connector U1.18-P1-H2/Q10 Diskette Drive Cable U1.18-P1-H2/Q10# BPC A&B Connector U1.18-P1-H2/Q8 BPC A Connector...
Page 88 U1.18-P1-H1/Q1# Connector 3 (1-1) Cable I/O Book 1, Port 11 U1.18-P1-H1/Q2 Connector 2 (1-0) (B0) I/O Book 1, Port 11 U1.18-P1-H1/Q2# Connector 2 (1-0) Cable I/O Book 1, Port 10 U1.18-P1-H1/Q3 Connector 1 (2-1) (A1) Eserver pSeries 670 Service Guide...
Page 89 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Book 1, Port 10 U1.18-P1-H1/Q3# Connector 1 (2-1) Cable I/O Book 1, Port 10 U1.18-P1-H1/Q4 Connector 0 (2-0) (A0) I/O Book 1, Port 10 U1.18-P1-H1/Q4# Connector 0 (2-0) Cable I/O Book 1, Port 5 U1.18-P1-H1/Q5 Connector 3 (1-1) (D1)
Page 90 6, see “I/O Subsystem (One Side of Subsystem 1 with IBF) RIO Cabling to I/O Books, Two I/O Planar Loop Configuration” on page 41 for cable connections. I/O Book 2, Port 4 U1.18-P1-H3/Q7 Connector 1 (2-1) (C1) Eserver pSeries 670 Service Guide...
Page 91 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Book 2, Port 4 U1.18-P1-H3/Q7# Connector 1 (2-1) Cable 7, see “I/O Subsystem (One Side of Subsystem 1 with IBF) RIO Cabling to I/O Books, Two I/O Planar Loop Configuration”...
Page 92 U1.18-P1-V4/Q2 Connector DCA 3- BPA B - BPC - 7 U1.18-P1-V4/Q2# Cable DCA 4-RH U1.18-P1-V5 DCA 4- BPA A - BPD1 - 9 U1.18-P1-V5/Q1 Connector DCA 4- BPA A - BPD1 - 9 U1.18-P1-V5/Q1# Cable Eserver pSeries 670 Service Guide...
Page 93 Location Physical Logical FRU Name Code Location Connection Connection Code DCA 4- BPA B - BPD1 - 9 U1.18-P1-V5/Q2 Connector DCA 4- BPA B - BPD1 - 9 U1.18-P1-V5/Q2# Cable DCA 5-RH U1.18-P1-V6 DCA 5- BPA A - BPD1 - U1.18-P1-V6/Q1 10 Connector DCA 5- BPA A - BPD1 -...
Page 94 Processor 18 (W/ L1 & U1.18-P1-C4 00-18 L2 Cache Processor 19 (W/ L1 & U1.18-P1-C4 00-19 L2 Cache Processor 20 (W/ L1 & U1.18-P1-C4 00-20 L2 Cache Processor 21 (W/ L1 & U1.18-P1-C4 00-21 L2 Cache) Eserver pSeries 670 Service Guide...
Page 95 Location Physical Logical FRU Name Code Location Connection Connection Code Processor 22 (W/ L1 & U1.18-P1-C4 00-22 L2 Cache) Processor 21 (W/ L1 & U1.18-P1-C4 00-23 L2 Cache) L3 Module (Proc 3D) U1.18-P1-C5 00-00 L3 Module (Proc 0A) U1.18-P1-C6 00-00 L3 Module (Proc 0B) U1.18-P1-C7 00-00...
Page 96 Operator Panel Cable U1.17-L1/Q1# System VPD Module U1.17-L1-N1 Media Drawer - Diskette U1.17-D1 Diskette Drive Connector U1.17-D1/Q2 Diskette Drive Cable U1.17-D1/Q2# Media Drawer - U1.x-Px-Ix/Z1-A1 DVD-RAM/CD-ROM Media Drawer - Tape U1.x-Px-Ix/Z1-A0 Drive Media Drawer connector U1.17-A1/Q3 Eserver pSeries 670 Service Guide...
Page 97 Location Physical Logical FRU Name Code Location Connection Connection Code Media Drawer cable U1.17-A1/Q3# Media Drawer Power U1.17-A1/Q4 Connector Media Drawer Power U1.17-A1/Q4# Cable Location Physical Logical FRU Name Code Location Connection Connection Code Integrated Battery Feature Locations (If Installed) IBF (Battery) 1A to BPA A U1.13-P1-V1 If Installed IBF 1A Connector...
Page 98 PCI Slot 1 Content U1.9-P2-I1 3F-08 to 3F-0F or 3G-xx or 3H-xx PCI Slot 2 Content U1.9-P2-I2 3J-08 to 3J-0F or 3K-xx or 3L-xx PCI Slot 3 Content U1.9-P2-I3 3M-08 to 3M-0F or 3N-xx or 3P-xx Eserver pSeries 670 Service Guide...
Page 99 Location Physical Logical FRU Name Code Location Connection Connection Code PCI Slot 4 Content U1.9-P2-I4 3Q-08 to 3Q-0F or 3R-xx or 3S-xx EADS 2 - PCI Controller U1.9-P2 3U-58, 3U-5A, 3U-5E PCI Slot 5 Content U1.9-P2-I5 3V-08 to 3V-0F or 3W-xx or 3X-xx PCI Slot 6 Content U1.9-P2-I6 3Y-08 to 3Y-0F...
Page 100 1 on P2 SCSI DASD 4 hdisk at ID U1.9-P2/Z1-Ab 3b-08-00-11,0 B connected to controller 1 on P2 SCSI Enclosure Services U1.9-P2/Z1-Af 3b-08-00-15,0 SES connected to controller 1 on P2 DASD 4-pack Cage and U1.9-P5 card (3) Eserver pSeries 670 Service Guide...
Page 101 Location Physical Logical FRU Name Code Location Connection Connection Code DASD 4-pack Cage and U1.9-P5-N1 card (3) VPD SCSI DASD 1 hdisk at ID U1.9-P1/Z2-A8 37-08-00-8,0 8 connected to controller 2 on P1 SCSI DASD 2 hdisk at ID U1.9-P1/Z2-A9 37-08-00-9,0 9 connected to controller 2 on P1...
Page 102 4Z-xx or 4a-xx PCI Slot 10 Content U1.5-P1-I10 4e-08 to 4e-0F or 4f-xx or 4g-xx I/O Riser Card U1.5-P1 I/O Port Connector U1.5-P1/Q1 I/O Port Cable From U1.5-P1/Q1# GX1A-port 1 I/O Port Connector U1.5-P1/Q2 Eserver pSeries 670 Service Guide...
Page 103 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Port Cable to port 0 U1.5-P1/Q2# on next Riser card U1.5-P2.1/Q1 I/O Subsystem Right IO U1.5-P2 backplane assembly I/O Subsystem Right IO U1.5-P2-N1 backplane assembly VPD EADS 1 - PCI Controller U1.5-P2 4j-58, 4j-5A, 4j-5C, 4j-5E...
Page 104 SES connected to controller 2 on P2 DASD 4-pack Cage and U1.5-P4 card (2) DASD 4-pack Cage and U1.5-P4-N1 card (2) VPD SCSI DASD 1 hdisk at ID U1.5-P2/Z1-A8 57-08-00-8,0 8 connected to controller 1 on P2 Eserver pSeries 670 Service Guide...
Page 105 Location Physical Logical FRU Name Code Location Connection Connection Code SCSI DASD 2 hdisk at ID U1.5-P2/Z1-A9 57-08-00-9,0 9 connected to controller 1 on P2 SCSI DASD 3 hdisk at ID U1.5-P2/Z1-Aa 57-08-00-10,0 A connected to controller 1 on P2 SCSI DASD 4 hdisk at ID U1.5-P2/Z1-Ab 57-08-00-11,0...
Page 106 5f-xx or 5g-xx EADS 2 - PCI Controller U1.1-P1 5j-58, 5j-5A, 5j-5E PCI Slot 5 Content U1.1-P1-I5 5k-08 to 5k-0F or 5m-xx or 5n-xx PCI Slot 6 Content U1.1-P1-I6 5p-08 to 5p-0F or 5q-xx or 5r-xx Eserver pSeries 670 Service Guide...
Page 107 Location Physical Logical FRU Name Code Location Connection Connection Code PCI Slot 7 Content U1.1-P1-I7 5v-08 to 5v-0F or 5w-xx or 5w-xx EADS 3 - PCI Controller U1.1-P1 60-58, 60-5A, 60-5E PCI Slot 8 Content U1.1-P1-I8 61-08 to 61-0F or 62-xx or 63-xx PCI Slot 9 Content U1.1-P1-I9 64-08 to 64-0F...
Page 108 DASD 4-pack Cage and U1.1-P3-N1 card (1) VPD SCSI DASD 1 hdisk at ID U1.1-P2/Z2-A8 6s-08-00-8,0 8 connected to controller 2 on P2 SCSI DASD 2 hdisk at ID U1.1-P2/Z2-A9 6s-08-00-9,0 9 connected to controller 2 on P2 Eserver pSeries 670 Service Guide...
Page 109 Location Physical Logical FRU Name Code Location Connection Connection Code SCSI DASD 3 hdisk at ID U1.1-P2/Z2-Aa 6s-08-00-10,0 A connected to controller 2 on P2 SCSI DASD 4 hdisk at ID U1.1-P2/Z2-Ab 6s-08-00-11,0 B connected to controller 2 on P2 SCSI Enclosure Services U1.1-P2/Z2-Bf 6s-08-00-15,0...
Page 110 I/O Subsystem Fan U1.1-F2 (MSA) I/O Subsystem Fan U1.1-F3 (MSA) I/O Subsystem Fan U1.1-F4 (MSA) Media Drawer Power U1.1-P1-X1/Q3 Connector Media Drawer Power U1.1-P1-X1/Q3# Cable Media Drawer Power U1.1-P2-X2/Q3 Connector Media Drawer Power U1.1-P2-X2/Q3# Cable Eserver pSeries 670 Service Guide...
Page 111: System Requirements For Adding Processor Mcms
System Requirements for Adding Processor MCMs Processor Total BUS Total DCA, Total L3 Cache VPD Locations Memory Book Pass-Thru Power Capacitor Plug Plug Locations Modules Converter (FC Books (FC Positions (FC5257) 6170 and 6198) Required, 6189) Required Locations Required, Locations Locations Add 1st MCM Qty = 0...
Page 112: Number Of Bulk Power Regulators (Bpr) Fc 6186 Required As A Function Of Mcms And I/O Drawers
Front BPA U1.35-P1-V1 U1.35-P1-V2 Back BPA U1.35-P2-V 1 U1.35-P2-V2 3 I/O Drawer Location 4 BPRs 4 BPRs 4 BPRs U1.1 4 I/O Drawer at Rack 4 BPRs 4 BPRs #1, Loc= U1.13 at Rack#2, Location U2.9 Eserver pSeries 670 Service Guide...
Page 113 5 I/O Drawer Location 6 BPRs 6 BPRs U2.1 Front BPA U1.35-P1-V1 U1.35-P1-V2 U1.35-P1-V3 Back BPA U1.35-P2-V1 U1.35-P2-V2 U1.35-P2-V3 6 I/O Drawer Location 6 BPRs 6 BPRs U2.5 7 I/O Drawer Location 6 BPRs U2.13 8 I/O Draw Location 6 BPRs U2.19 Chapter 1.
Page 114: Specifications
670 system configurations. Power and Electrical Requirements Redundant power line cords are standard on the pSeries 670. The system uses dual ac power cords. For maximum availability, each of the power cords should be fed from independent power grids.
Page 115 The system has one bulk power regulator (BPR) per BPA, with its Phase A and Phase B Line Currents determined by Power/Vline, and a Phase C Line Current of 0. Note: Power is calculated from “Total System Power Consumption” on page 103. Vline is line-to-line nominal input voltage.
Page 116 The following figure shows another way of distributing the unbalanced load evenly. Using this method, the three-pole breakers are alternated with two-pole breakers. Power Cord Configuration: The power cords exit the system from different points of the frame as indicated in the following illustration. Rear Front (Top Down View) Eserver pSeries 670 Service Guide...
Page 117: Dimensions And Weight
__ 1. The pSeries 670 is equipped to use 200-240 V / 380-415 V / 480 V ac, three-phase. Check that the correct power source is available.
Page 118: Acoustical Noise Emissions
A-weighted sound power level; LpAm is the mean A-weighted sound pressure level at the 1-meter bystander positions; 1 B = 10 dB. 4. All measurements made in conformance with ISO 7779 and declared in conformance with ISO 9296. Eserver pSeries 670 Service Guide...
Page 119: Environmental Specifications
Environmental Specifications Environmental Specification Operating Non-Operating Storage Shipping Temperature 10 to 32°C 10 to 43°C 1 to 60°C –40 to 60°C (50 to 90°F) (50 to 109°F) (34 to 140°F) (–40 to 140°F) Max. of 24 ° C (75.2 ° F) with 4mm tape or DVD RAM in rear positions of the...
Page 120 36 in. for the rear of the frame (measured from the base frame). 2. Weight-distribution areas should not be overlapped. 3. Floor-loading weight distribution distances should not exceed 762 mm (30 in.) in any direction when measured from the base frame. Eserver pSeries 670 Service Guide...
Page 121 The following table shows floor-loading specifications for systems with acoustical covers. The values contained in the Condition column are described following the table. Condition a (sides) b (front) c (back 1 Frame mm (in.) mm (in.) mm (in.) kg/m (lb./ft. 25 (1.0) 135 (5.3) 135 (5.3)
Page 122 Plan Views The following illustration shows dimensional planning information for single-frame systems and double-frame systems. Eserver pSeries 670 Service Guide...
Page 123: Total System Power Consumption
Total System Power Consumption The following tables contain minimum and maximum power consumption for the 1.1 pSeries 670. Minimum power consumption is based on a configuration consisting of a single 4 GB memory card, 1 PCI card per I/O subsystem, and 1 DASD device per I/O subsystem.
Page 124 8 GB memory book - 151 Watts v 16 GB memory book - 235 Watts v 32 GB memory book - 294 Watts v Each PCI card - 20 Watts v DASD - 20 Watts Eserver pSeries 670 Service Guide...
Page 125: Service Inspection Guide
Service Inspection Guide Perform a service inspection on the system when: v The system is inspected for a maintenance agreement. v Service is requested and service has not recently been performed. v An alterations and attachments review is performed. v Changes have been made to the equipment that may affect its safe operation. v External devices with their own power cables have those cables attached.
Page 126 3 Processor Subsystem 7 Bottom Filter Pull Tab 4 Top Filter Replacement To replace an air filter into the processor subsystem, slide the air filter into the slot. The filter is keyed to ensure correct orientation. Eserver pSeries 670 Service Guide...
Page 127: Chapter 2. Diagnostics Overview
This MAP provides a systematic method of isolation to the failing item or items. Checkpoints Eserver pSeries 670 systems use various types of checkpoints, error codes, and SRNs that are referred to throughout this book (primarily in Chapters 3, 4 and 5).
Page 128 For a list of the checkpoints, see Chapter 4, “Checkpoints”, on page 307. Each entry provides a description of the event and the recommended action if the system fails to advance. SRNs are listed in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems, order number SA38-0509. Eserver pSeries 670 Service Guide...
Page 129: Fru Isolation
If the system is logically partitioned, the HMC must be attached. You can use the HMC to enable any FRU identify LED to be flashed. See the IBM Hardware Management Console for pSeries Installation and Operations Guide for instructions on activating and deactivating a FRU identify LED.
Page 130: Service Agent For The Eserver Pseries 670
Service Agent for the Eserver pSeries 670 Service support for the Eserver pSeries 670 can be enhanced through the use of the application program known as service agent for the Eserver pSeries 670. This application provides a number of advantages for the Eserver pSeries 670 customer, including automatic error reporting and analysis without customer intervention.
Page 131: Chapter 3. Maintenance Analysis Procedures (Maps)
Chapter 3. Maintenance Analysis Procedures (MAPs) This chapter contains Maintenance Analysis Procedures (MAPs) for the pSeries 670. 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 132 The system stops and a 4-digit number beginning with 0 or 2 is displayed in the operator panel display. pSeries Diagnostic Information for Multiple Bus Systems. All other symptoms. Go to “Quick Entry MAP” on page 113. Eserver pSeries 670 Service Guide...
Page 133: Quick Entry Map
Quick Entry MAP Quick Entry MAP Table of Contents Problem Description Page No. Service actions The system attention LED on the media subsystem operator panel is on. OK does not appear in the media subsystem operator panel display before pressing the power-on button.
Page 134 LEDs on the operator panel appear to behave normally. cable. 2. Replace the operator panel assembly, Location: U1.17-L1. Refer to “Operator Panel” on page 938. 3. Replace the primary I/O book, Location: U1.18-P1-H2. Refer to “I/O Books and I/O Blanks” on page 792. Eserver pSeries 670 Service Guide...
Page 135 Symptom Action You have a blank display on the operator panel. Other Go to “MAP 1520: Power” on page 144. LEDs on the operator panel are off. 8-Digit Error Codes You have an 8-digit error code displayed 1. Look up the error code in the table in “Checkpoints and Error Codes Index”...
Page 136 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 137 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 138 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 139 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 140: Map 1020: Problem Determination
You can disable these actions while you diagnose and service the system. If the system was set up according to the recommendations of the Eserver pSeries 670 User’s Guide, all the settings of the service processor (except language) were saved by using the SAVE/RESTORE HARDWARE MAINTENANCE POLICIES service aid.
Page 141 Step 1020-1 The following steps analyze a failure to load the diagnostic programs. Note: Be prepared to answer questions regarding the operator panel display and to perform certain actions based on displayed POST indicators. 1. Run diagnostics on any partition. Find your symptom in the following table; then follow the instructions given in the Action column.
Page 142 Go to “Step 1020-4” on page 124. All other symptoms. If you were directed here from the Entry MAP, go to “MAP 1542: I/O Problem Isolation” on page 261. Otherwise, find the symptom in the “Entry MAP” on page 111. Eserver pSeries 670 Service Guide...
Page 143 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 144 Look up the error in the Chapter 5, “Error Code to FRU Index”, on page 345 and do the listed action. e. If no recent error is logged in the error log, go to “MAP 1542: I/O Problem Isolation” on page 261. Eserver pSeries 670 Service Guide...
Page 145: 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 146: Map 1321: Quick Entry Map For Systems With Service Focal Point
Are there any serviceable actions events with error codes of the form #xxxxxx in the list of error codes found in “Step 1321-5”? Go to “Step 1321-7”. Go to “Step 1321-18” on page 128. Step 1321-7 Are there any serviceable events with FRU location codes reported in “Step 1321-5”? Eserver pSeries 670 Service Guide...
Page 147 Go to “Step 1321-14”. 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. Step 1321-9 Examine the list of error codes you obtained from “Step 1321-8” and look for any of the form 4xxB xxxx, A0D-34x, or A1D-34x.
Page 148 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). Eserver pSeries 670 Service Guide...
Page 149 Step 1321-23 Is Linux usable in any partition with Linux installed? Go to “Step 1321-30” on page 131. Go to “Step 1321-24”. Attention: “Step 1321-24” through “Step 1321-36” on page 132 must be performed on a partition running the Linux operating system. Step 1321-24 If your system is functional, examine the Linux system log by logging in to the system as the root user and entering the following command:...
Page 150 <3>RTAS: WARNING: (FULLY RECOVERED) type: INTERN_DEV_FAIL <3>RTAS: initiator: UNKNOWN target: UNKNOWN <3>RTAS: Status: unrecoverable new <3>RTAS: Date/Time: 20020905 15372200 <3>RTAS: CPU Failure <3>RTAS: Internal error (not cache) <3>RTAS: CPU id: 0 <3>RTAS: Failing element: 0x0000 <3>RTAS: -------- event-scan end --------- Eserver pSeries 670 Service Guide...
Page 151 Step 1321-29 Record any extended data found in the Linux system log in Step 1321-24 or the Linux boot (IPL) log in Step 1321-26. Be sure to record word 13. Note: The line(s) in the Linux extended data that begin with ″<4>RTAS: Log Debug: 04″ contain the error code listed in the next 8 hex characters.
Page 152 2. Replace the device (for example, tape or DASD) 3. If applicable, replace the device backplane. 4. Replace the device cable. 5. Replace the adapter. 6. If the adapter resides in an I/O drawer, replace the I/O backplane. Eserver pSeries 670 Service Guide...
Page 153 7. If the device adapter resides in the CEC, replace the I/O riser card, or the CEC backplane where the device adapter is located. 8. Call service support. Do not go to “Step 1321-34” on page 132. 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”...
Page 154 Go to the “Quick Entry MAP” on page 113 with each symptom you have recorded. Perform the indicated actions for all recorded symptoms, one at a time, until the problem has been corrected. If all recorded symptoms have been processed and the problem has not been corrected, call support. Eserver pSeries 670 Service Guide...
Page 155: 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 RS/6000 and 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 156 Begin a new list of “Axx” partitions by copying the list of partitions obtained in “Step 1322-11”. Go to “Step 1322-16” on page 137. Step 1322-15 Add the partition list obtained in “Step 1322-11” to the existing list of “Axx” partitions obtained from processing previous service action events in this MAP. Eserver pSeries 670 Service Guide...
Page 157 Step 1322-16 Remove all entries in the list of all partition(s) you recorded in “Step 1322-11” on page 136. If you are referred to the list of partition(s) obtained in “Step 1322-11” on page 136 in future steps, the list is empty. Go to “Step 1322-17”.
Page 158 Have all the serviceable events recorded in “Step 1322-4” on page 135 been processed? Go to “Step 1322-5” on page 135 and process the next service action event in the list of serviceable events recorded in “Step 1322-4” on page 135. Go to “Step 1322-34” on page 139. Eserver pSeries 670 Service Guide...
Page 159 Step 1322-34 While processing all service action events, were you directed to “Step 1322-14” on page 136? 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 25. This completes the repair. Return the system to the customer.
Page 160: Map 1420: Recovery Procedures For Hot-Pluggable Pci Adapters
Remove the faulty resource from the partition that will not boot. Record the slot location and the adapter type. Step 1421-4 Attempt to boot the partition. Does the partition boot? Go to “Step 1421-12” on page 141. Go to “Step 1421-5”. Step 1421-5 Shut down the partition. Eserver pSeries 670 Service Guide...
Page 161: 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 140 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 162 Are there any empty PCI slots attached to the system that are not assigned to any partitions? Go to “Step 1422-14” on page 143. Go to “Step 1422-10”. Step 1422-10 Assign the available empty and unassigned slot to the partition that the faulty slot is assigned to. Eserver pSeries 670 Service Guide...
Page 163 Step 1422-11 Insert a new adapter of the same type recorded in “Step 1422-1” on page 141 into the slot assigned in “Step 1422-10” on page 142. Step 1422-12 Move any external cabling from the adapter in the slot recorded in “Step 1422-1” on page 141 to the adapter in the slot assigned in “Step 1422-10”...
Page 164: Map 1520: Power
CAUTION: Energy hazard, remove power before servicing. Attention: To identify a FRU, these MAPs refer to FRU Identify LEDs. Information about the FRU Identify LEDs can be found in “FRU Identify LEDs” on page 54. Eserver pSeries 670 Service Guide...
Page 165 Find the symptom in the following table; then follow the instructions given in the Action column. Power Problems Symptom/Reference Code Action The system will not power on and no error codes are Go to “MAP 1521: The System Will Not Power On And available No Error Codes Are Available”...
Page 166 (BPA) Communication Failure” on page 163. 101A F806 or 101A F906 for BPC A Go to “MAP 152a: Loss of ac Power or Phase Missing” on page 165. 101B F806 or 101B F906 for BPC B Eserver pSeries 670 Service Guide...
Page 167 Power Problems Symptom/Reference Code Action 1014 xx15, 1014 xx25, 1015 xx15, 1015 xx25, Go to “MAP 152m: Cable Problem in Power Subsystem” 1016 xx15, 1016 xx25, 1017 xx15, 1017 xx25, on page 246. 101C xx15, 101C xx25, 101C xx35, 101C xx45, 101C xx55, 101C xx75, 101C xx85, 101C xx95, 101C xxA5, 101A x115, 101A x125, 101A x135, 101A x215,...
Page 168: Map 1521: The System Will Not Power On And No Error Codes Are Available
UEPO PWR LED turned on v BPC GOOD LED turned on v All other LEDs are off Are all of the above true? Go to “Step 1521-4” on page 149. Go to “Step 1521-5” on page 149. Eserver pSeries 670 Service Guide...
Page 169 Step 1521-4 Independent faults are indicated on both sides of the BPA. Each side must be isolated separately. Call for support. This ends the procedure. Step 1521-5 Check the External (Room) EPO Connection if used. If a room emergency power off (EPO) circuit is used, the external room EPO circuit is connected to the J02 connector on the lower edge of the UEPO Switch.
Page 170 Inform the customer that the line voltage into the BPA is missing or too low. This ends the procedure. Independent faults are indicated on both sides of the BPA. Each side must be isolated separately. Call for support. This ends the procedure. Eserver pSeries 670 Service Guide...
Page 171: Map 1522: Uepo Switch On The Bpc Is In The Bypass Position
MAP 1522: UEPO Switch On The BPC Is In The Bypass Position Step 1522-1 Check the UEPO Switch on the BPC on the BPA that is exhibiting the failure. Is the switch in the NORMAL position? Set UEPO switch on the BPC to the NORMAL position and go to “Step 1522-2”. Go to “Step 1522-2”.
Page 172: Map 1523: There Is A Bulk Power Regulator (Bpr) Communications Fault
Step 1524-1 Check the unit emergency power off (UEPO) panel. Is a customer room EPO cable plugged into the UEPO panel? Go to “Step 1524-3” on page 153. Go to “Step 1524-2” on page 153. Eserver pSeries 670 Service Guide...
Page 173 Step 1524-2 1. Set UEPO switch on both BPCs to the BYPASS position. 2. Unplug the customer room EPO cable. 3. Set switch (J4) on the UEPO panel to EPO BYPASS position. 4. Set UEPO switch on both BPCs back to the NORMAL position. 5.
Page 174: Map 1525: There Is A 350 Volt Bulk Failure
The following steps check all the BPRs on the side of the BPA (A or B) referenced by the error code that sent you to this MAP. Are there any remaining BPRs to be checked? Go to “Step 1525-3” on page 155. Go to “Step 1525-4” on page 155. Eserver pSeries 670 Service Guide...
Page 175 Step 1525-3 Notes: 1. This problem can be caused by any BPD plugged into the failing BPA. 2. The system can have up to three BPDs, depending on the system configuration. 3. Each BPD on the failing BPA must be checked independently. The following steps check all the BPDs on the side of the BPA (A or B) referenced by the error code that sent you to this MAP.
Page 176 Is the error code that sent you to this MAP reported? The problem has been corrected. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Call for support. Eserver pSeries 670 Service Guide...
Page 177: Map 1526: There Is An Integrated Battery Feature (Ibf) Failure
MAP 1526: There Is An Integrated Battery Feature (IBF) Failure Step 1526-1 Is the IBF feature installed? Replace the BPR that is connected to the IBF referenced in the error code that brought you to this MAP. Follow all steps in the removal and replacement procedures in “Bulk Power Regulator (BPR)”...
Page 178 Replace the IBF referenced in the error code that brought you to this MAP. Follow all steps in the removal and replacement procedures in “Integrated Battery Feature (IBF)” on page 789. Go to “Step 1526-7” on page 159. Eserver pSeries 670 Service Guide...
Page 179 Step 1526-6 Set the breaker to the on (down) position. Wait 10 seconds after the LED on the IBF referenced in the error code that brought you to this MAP comes on. Does the circuit breaker remain on? Exchange the following FRUs one at a time: v The BPR that is connected to the IBF referenced in the error code that brought you to this MAP.
Page 180: Map 1527: An Airflow Loss Has Been Detected
The enclosure is not a replaceable FRU. Call your next level of support. Reinstall the blower or fans removed earlier and go to “Step 1527-5” on page 161 ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 670 Service Guide...
Page 181 Step 1527-5 1. Replace the BPR on the side indicated by the error code that sent you to this MAP. 2. Call your next level of support. Chapter 3. Maintenance Analysis Procedures...
Page 182: Map 1528: There Is A Processor (Critical/Warning) Overtemperature Fault
The problem has been corrected. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Replace the next FRU on the list. If all FRUs on the list have been replaced, call for support. Eserver pSeries 670 Service Guide...
Page 183: Map 1529: There Is A Bulk Power Assembly (Bpa) Communication Failure
MAP 1529: There Is A Bulk Power Assembly (BPA) Communication Failure Step 1529-1 Check the position of the on/off switch on the BPRs. Is the switch in the ON position (to the left)? Set the switch to the ON position (to the left), and go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 184 Is error code that sent you to this MAP still reported? The problem has been corrected. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. This ends the procedure. Call for support. This ends the procedure. Eserver pSeries 670 Service Guide...
Page 185: Map 152A: Loss Of Ac Power Or Phase Missing
MAP 152a: Loss of ac Power or Phase Missing Step 152a-1 Press the Service complete button. Is the error code that sent you to this MAP still reported? This was a transient condition. The condition no longer exists. No service action is required. Go to “Step 152a-2”.
Page 186 Is error code that sent you to this MAP still reported? The problem has been corrected. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. This ends the procedure. Call for support. This ends the procedure. Eserver pSeries 670 Service Guide...
Page 187: Map 152B: 2.5 V Current/Voltage Problem In Processor Subsystem
MAP 152b: 2.5 V Current/Voltage Problem in Processor Subsystem Step 152b-1 Record the error code and location code(s) that sent you to this MAP. Step 152b-2 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152b-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152b-4”.
Page 188 2. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152b-18 Reinsert one of the books that is pulled out and listed in step “Step 152b-14”. Step 152b-19 Turn on the power. Eserver pSeries 670 Service Guide...
Page 189 Step 152b-20 Did the system stop with the same error code as recorded in “Step 152b-1” on page 167? The book just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 190 DCA 1-RH, at location U1.18-P1-V1 v DCA 2-RH, at location U1.18-P1-V2 v DCA 3-RH, at location U1.18-P1-V4 v DCA 4-RH, at location U1.18-P1-V5 v DCA 5-RH, at location U1.18-P1-V6 v DCA 6-RH, at location U1.18-P1-V8 Eserver pSeries 670 Service Guide...
Page 191 Step 152b-35 Turn on the power. Step 152b-36 Did the system stop with the same error code as recorded in “Step 152b-1” on page 167? Go to “Step 152b-37”. The book just replaced is defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
Page 192 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152b-46 Has the system backplane been replaced? Call for support. Go to “Step 152b-42” on page 171. Eserver pSeries 670 Service Guide...
Page 193: Map 152C: 1.8 V Current/Voltage Problem In Processor Subsystem
MAP 152c: 1.8 V Current/Voltage Problem in Processor Subsystem Step 152c-1 For future reference, record the error code in the operator panel display. Step 152c-2 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152c-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152c-4”.
Page 194 2. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152c-18 Reinsert one of the books that is pulled out and listed in “Step 152c-14”. Step 152c-19 Turn on the power. Eserver pSeries 670 Service Guide...
Page 195 Step 152c-20 Did the system stop with the same error code as recorded in “Step 152c-1” on page 173? The book just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 196 Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152c-33 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152c-34” on page 177. Call for support. Eserver pSeries 670 Service Guide...
Page 197 Step 152c-34 Replace the books in the following list, if present, one at a time and in the order listed: v Primary I/O book, at location U1.18-P1-H2 v DCA 1-RH, at location U1.18-P1-V1 v DCA 2-RH, at location U1.18-P1-V2 v DCA 3-RH, at location U1.18-P1-V4 v DCA 4-RH, at location U1.18-P1-V5 v DCA 5-RH, at location U1.18-P1-V6 v DCA 6-RH, at location U1.18-P1-V8...
Page 198 The module just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152c-49” on page 179. Eserver pSeries 670 Service Guide...
Page 199 Step 152c-49 Have all the modules listed in “Step 152c-42” on page 178 been reinstalled? The symptom has changed. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 200: Map 152D: 1.5 V Auxiliary Current/Voltage Problem In Processor Subsystem
Go to “Step 152d-12” on page 181. Go to “Step 152d-7”. Step 152d-7 One of the books just removed is defective. Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Eserver pSeries 670 Service Guide...
Page 201 Step 152d-8 Reinsert one of the books that is pulled out and listed in “Step 152d-4” on page 180. Step 152d-9 Turn on the power. Step 152d-10 Did the system stop with the same error code as recorded in “Step 152d-1” on page 180? The book just reinserted is defective.
Page 202 The symptom has changed. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152d-18”. Eserver pSeries 670 Service Guide...
Page 203 Step 152d-22 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152d-23 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152d-24”. Call for support. Step 152d-24 Pull out the following books about 25 mm (1 inch), if present: v Secondary I/O book, at location U1.18-P1-H3 v Third I/O book, at location U1.18-P1-H4...
Page 204 DCA 2-RH, at location U1.18-P1-V2 v DCA 3-RH, at location U1.18-P1-V4 v DCA 4-RH, at location U1.18-P1-V5 v DCA 5-RH, at location U1.18-P1-V6 v DCA 6-RH, at location U1.18-P1-V8 Step 152d-35 Turn on the power. Eserver pSeries 670 Service Guide...
Page 205 Step 152d-36 Did the system stop with the same error code as recorded in “Step 152d-1” on page 180? Go to “Step 152d-37”. The book just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
Page 206 The module just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152d-49” on page 187. Eserver pSeries 670 Service Guide...
Page 207 Step 152d-49 Have all the modules listed in “Step 152d-42” on page 186 been reinstalled? The symptom has changed. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 208: Map 152E: 1.5 V Cpu Current/Voltage Problem In Processor Subsystem
Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152e-8 Reinsert one of the books that is pulled out and listed in “Step 152e-4”. Step 152e-9 Turn on the power. Eserver pSeries 670 Service Guide...
Page 209 Step 152e-10 Did the system stop with the same error code as recorded in “Step 152e-1” on page 188? The book just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 210 Record the original location on each MCM. Remove the following MCM modules, if present: v MCM module 0, at location U1.18-P1-C1 v MCM module 3, at location U1.18-P1-C2 v MCM module 1, at location U1.18-P1-C3 v MCM module 2, at location U1.18-P1-C4 Eserver pSeries 670 Service Guide...
Page 211 Step 152e-23 Turn on the power. Step 152e-24 Did the system stop with the same error code as recorded in “Step 152e-1” on page 188? Go to “Step 152e-30” on page 192. Go to “Step 152e-25”. Step 152e-25 One of the modules just removed is defective. Turn off the power.
Page 212 Step 152e-35 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152e-36 Has the system backplane been replaced? Call for support. Go to “Step 152e-32”. Eserver pSeries 670 Service Guide...
Page 213: Map 152F: 3.3 V Current/Voltage Problem In Processor Subsystem
MAP 152f: 3.3 V Current/Voltage Problem in Processor Subsystem Step 152f-1 Record the error code and the location code(s) that sent you to this MAP. Step 152f-2 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152f-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152f-4”.
Page 214 Pull out the following books about 25 mm (1 inch), if present: v Memory book 4, at location U1.18-P1-M4 v Memory book 5, at location U1.18-P1-M8 v Memory book 6, at location U1.18-P1-M5 v Memory book 7, at location U1.18-P1-M1 Step 152f-15 Turn on the power. Eserver pSeries 670 Service Guide...
Page 215 Step 152f-16 Did the system stop with the same error code as recorded in “Step 152f-1” on page 193? Go to “Step 152f-22”. Go to “Step 152f-17”. Step 152f-17 One of the books just removed is defective. Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off.
Page 216 The book just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152f-31” on page 197. Eserver pSeries 670 Service Guide...
Page 217 Step 152f-31 Have all the books listed in “Step 152f-24” on page 196 been reinserted? The symptom has changed. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 218 The system clock card just reinserted is defective, replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152f-49” on page 199. Eserver pSeries 670 Service Guide...
Page 219 Step 152f-49 Have all the modules listed in “Step 152f-42” on page 198 been reinstalled? The symptom has changed. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 220: Map 152G: 5.0 V Current/Voltage Problem In Processor Subsystem
Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152g-8 Reinsert one of the books that is pulled out and listed in “Step 152g-4”. Step 152g-9 Turn on the power. Eserver pSeries 670 Service Guide...
Page 221 Step 152g-10 Did the system stop with the same error code as recorded in “Step 152g-1” on page 200? The book just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 222 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152g-18”. Step 152g-22 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Eserver pSeries 670 Service Guide...
Page 223 Step 152g-23 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152g-24”. Call for support. Step 152g-24 Pull out the following books about 25 mm (1 inch), if present: v Fourth I/O book, at location U1.18-P1-H1 v Secondary I/O book, at location U1.18-P1-H3 v Third I/O book, at location U1.18-P1-H4 v Cap card at U1.18-P1-V3...
Page 224 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Step 152g-37 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Eserver pSeries 670 Service Guide...
Page 225 Step 152g-38 Remove the new book that was just installed in “Step 152g-34” on page 204 and reinstall the original book. Step 152g-39 Have all the books listed in “Step 152g-34” on page 204 been replaced with new or original books? Go to “Step 152g-40”.
Page 226: Map 152H: 3.3V Current/Voltage Problem In I/O Subsystem
Step 152h-6 Turn on the power. Step 152h-7 Did the system stop with the same error code as recorded in “Step 152h-1”? Go to “Step 152h-13” on page 207. Go to “Step 152h-8” on page 207. Eserver pSeries 670 Service Guide...
Page 227 Step 152h-8 One of the cards just removed is defective. Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152h-9 Reinsert one of the cards that is removed and listed in “Step 152h-5” on page 206. Step 152h-10 Turn on the power.
Page 228 The card just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152h-22” on page 209. Eserver pSeries 670 Service Guide...
Page 229 Step 152h-22 Have all the cards listed in “Step 152h-15” on page 208 been reinserted? The symptom has changed. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 230 Remove the following adapter cards, if present, from the I/O subsystem. Record the adapter locations: v Adapter card at P2-I6 v Adapter card at P2-I7 v Adapter card at P2-I8 v Adapter card at P2-I9 v Adapter card at P2-I10 Eserver pSeries 670 Service Guide...
Page 231 Step 152h-36 Turn on the power. Step 152h-37 Did the system stop with the same error code as recorded in “Step 152h-1” on page 206? Go to “Step 152h-43”. Go to “Step 152h-38”. Step 152h-38 One of the cards just removed is defective. Turn off the power.
Page 232 Have all the DCAs listed in “Step 152h-45” been replaced with new or original cards? Go to “Step 152h-51” Go to “Step 152h-45”. Step 152h-51 Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Eserver pSeries 670 Service Guide...
Page 233 Step 152h-52 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152h-53”. Call for support. Step 152h-53 Replace the parts in the following list, one at a time and in the order listed: v I/O subsystem backplane at P1 v I/O subsystem backplane at P2 Step 152h-54...
Page 234: Map 152I: 5.0 V Current/Voltage Problem In I/O Subsystem
Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152i-9 Reinsert one of the cards that is removed and listed in “Step 152i-5”. Step 152i-10 Turn on the power. Eserver pSeries 670 Service Guide...
Page 235 Step 152i-11 Did the system stop with the same error code as recorded in “Step 152i-1” on page 214? The card just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 236 Turn on the power. Step 152i-27 Did the system stop with the same error code as recorded in “Step 152i-1” on page 214? Go to “Step 152i-33” on page 217. Go to “Step 152i-28” on page 217. Eserver pSeries 670 Service Guide...
Page 237 Step 152i-28 One of the cards just removed is defective. Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152i-29 Reinsert one of the cards that is removed and listed in “Step 152i-25” on page 216. Step 152i-30 Turn on the power.
Page 238 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152i-39”. Step 152i-43 Turn off the power. Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Eserver pSeries 670 Service Guide...
Page 239 Step 152i-44 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152i-45”. Call for support. Step 152i-45 Remove the following DASD 4-packs, if present, from the I/O subsystem. Record the DASD locations: v DASD 4-pack at P3 v DASD 4-pack at P4 v DASD 4-pack at P5...
Page 240 Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152i-59 Remove the new card that was just installed in “Step 152i-55” and reinstall the original card. Eserver pSeries 670 Service Guide...
Page 241 Step 152i-60 Have all the cards listed in “Step 152i-55” on page 220 been replaced with new or original cards? Go to “Step 152i-61”. Go to “Step 152i-55” on page 220. Step 152i-61 Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Step 152i-62 Are all the green ″power good out″...
Page 242: Map 152J: 2.5 V Current/Voltage Problem In I/O Subsystem
Step 152j-6 Turn on the power. Step 152j-7 Did the system stop with the same error code as recorded in “Step 152j-1”? Go to “Step 152j-13” on page 223. Go to “Step 152j-8” on page 223. Eserver pSeries 670 Service Guide...
Page 243 Step 152j-8 One of the cards just removed is defective. Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152j-9 Reinsert one of the cards that is removed and listed in “Step 152j-5” on page 222. Step 152j-10 Turn on the power.
Page 244 The card just reinserted is defective. Replace it.This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152j-22” on page 225. Eserver pSeries 670 Service Guide...
Page 245 Step 152j-22 Have all the cards listed in “Step 152j-15” on page 224 been reinserted? The symptom has changed. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 246 Remove the following adapter cards, if present, from the I/O subsystem. Record the adapter locations: v Adapter card at P2-I6 v Adapter card at P2-I7 v Adapter card at P2-I8 v Adapter card at P2-I9 v Adapter card at P2-I10 Step 152j-36 Turn on the power. Eserver pSeries 670 Service Guide...
Page 247 Step 152j-37 Did the system stop with the same error code as recorded in “Step 152j-1” on page 222? Go to “Step 152j-43”. Go to “Step 152j-38”. Step 152j-38 One of the cards just removed is defective. Turn off the power. Make sure all the green ″power good out″...
Page 248 Have all the cards listed in “Step 152j-45” been replaced with new or original cards? Go to “Step 152j-51” Go to “Step 152j-45”. Step 152j-51 Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Eserver pSeries 670 Service Guide...
Page 249 Step 152j-52 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152j-53”. Call for support. Step 152j-53 Replace the parts in the following list one at a time and in the order listed: v I/O subsystem backplane at P1 v I/O subsystem backplane at P2 Step 152j-54...
Page 250: Map 152K: 12.0 V Current/Voltage Problem In I/O Subsystem
Step 152k-6 Turn on the power. Step 152k-7 Did the system stop with the same error code as recorded in “Step 152k-1”? Go to “Step 152k-13” on page 231. Go to “Step 152k-8” on page 231. Eserver pSeries 670 Service Guide...
Page 251 Step 152k-8 One of the cards just removed is defective. Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152k-9 Reinsert one of the cards that is removed and listed in “Step 152k-5” on page 230. Step 152k-10 Turn on the power.
Page 252 The card just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152k-22” on page 233. Eserver pSeries 670 Service Guide...
Page 253 Step 152k-22 Have all the cards listed in “Step 152k-15” on page 232 been reinserted? The symptom has changed. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 254 Go to “Step 152k-43” on page 235. Go to “Step 152k-38”. Step 152k-38 One of the cards just removed is defective. Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Eserver pSeries 670 Service Guide...
Page 255 Step 152k-39 Reinsert one of the cards that is removed and listed in “Step 152k-35” on page 234. Step 152k-40 Turn on the power. Step 152k-41 Did the system stop with the same error code as recorded in “Step 152k-1” on page 230? The card just reinserted is defective.
Page 256 Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Eserver pSeries 670 Service Guide...
Page 257 Step 152k-49 Reinsert one of the DASD 4-packs that is removed and listed in “Step 152k-45” on page 235. Step 152k-50 Turn on the power. Step 152k-51 Did the system stop with the same error code as recorded in “Step 152k-1” on page 230? One of the DASD in the DASD 4-pack just reinserted is defective.
Page 258 Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152k-67 Have all the cards listed in “Step 152k-63” been replaced? Call for support. Go to “Step 152k-63”. Eserver pSeries 670 Service Guide...
Page 259: Map 152L: -12.0V Current/Voltage Problem In I/O Subsystem
MAP 152l: -12.0V Current/Voltage Problem in I/O Subsystem Step 152l-1 Record the error code and location code(s) that sent you to this MAP. Step 152l-2 Determine the I/O subsystem number from the error code (10yy xxxx) and the following list. The remaining steps of this map refer to this I/O subsystem: v If yy=14, I/O subsystem number is 1, location is U1.9 v If yy=15, I/O subsystem number is 2, location is U1.5...
Page 260 Go to “Step 152l-23” on page 241. Go to “Step 152l-18”. Step 152l-18 One of the cards just removed is defective. Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Eserver pSeries 670 Service Guide...
Page 261 Step 152l-19 Reinsert one of the cards that is removed and listed in “Step 152l-15” on page 240. Step 152l-20 Turn on the power. Step 152l-21 Did the system stop with the same error code as recorded in “Step 152l-1” on page 239? The card just reinserted is defective.
Page 262 Remove the following adapter cards, if present, from the I/O subsystem. Record the adapter locations: v Adapter card at P2-I6 v Adapter card at P2-I7 v Adapter card at P2-I8 v Adapter card at P2-I9 v Adapter card at P2-I10 Eserver pSeries 670 Service Guide...
Page 263 Step 152l-36 Turn on the power. Step 152l-37 Did the system stop with the same error code as recorded in “Step 152l-1” on page 239? Go to “Step 152l-43”. Go to “Step 152l-38”. Step 152l-38 One of the cards just removed is defective. Turn off the power.
Page 264 Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Step 152l-52 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152l-53” on page 245. Call for support. Eserver pSeries 670 Service Guide...
Page 265 Step 152l-53 Replace the parts in the following list one at a time and in the order listed: v I/O subsystem backplane at P1 v I/O subsystem backplane at P2 Step 152l-54 Turn on the power. Step 152l-55 Did the system stop with the same error code as recorded in “Step 152l-1” on page 239? Go to “Step 152l-56”.
Page 266: Map 152M: Cable Problem In Power Subsystem
Step 152m-6 Have you replaced the first FRU in the list of FRUs recorded in “Step 152m-1” in a previous service action? Go to “Step 152m-18” on page 248. Go to “Step 152m-7” on page 247. Eserver pSeries 670 Service Guide...
Page 267 Step 152m-7 Is the power-on LED of the first FRU generated from the location codes recorded in “Step 152m-1” on page 246 off? Go to “Step 152m-8”. Call for support. Step 152m-8 Replace the first FRU in the list of FRUs recorded in “Step 152m-1” on page 246 with power-on LED off. Press the white service complete button on the panel with the UEPO switch after replacement.
Page 268 Does the error code recorded in “Step 152m-1” on page 246 reappear? Call for support. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 670 Service Guide...
Page 269 Step 152m-29 Is the error code recorded in “Step 152m-1” on page 246 of the form 101A xxxx or 101B xxxx? Go to “Step 152m-12” on page 247. All system partitions must be shut down and the system must be powered off to correct the power cabling.
Page 270: Map 152N: Dasd Subsystem Power Problem
Turn off the power. Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Step 152n-5 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152n-6” on page 251. Call for support. Eserver pSeries 670 Service Guide...
Page 271 Step 152n-6 Are there any DASD in positions A8, A9, Aa, or Ab of the DASD backplane found in “Step 152n-2” on page 250 and “Step 152n-3” on page 250? Go to “Step 152n-7”. Go to “Step 152n-15” on page 252. Step 152n-7 Turn on the power.
Page 272 The book just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 670 Service Guide...
Page 273: Map 1540: Problem Isolation Procedures
MAP 1540: Problem Isolation Procedures These procedures are used to locate problems in the processor subsystem, I/O subsystems, or rack. If a problem is detected, these procedures help you isolate the problem to a failing unit. Find the symptom in the following table;...
Page 274: Map 1541: Jtag Problem Isolation
L3 module at U1.18-P1-C18 v L3 module at U1.18-P1-C19 v L3 module at U1.18-P1-C8 v MCM module 0 at U1.18-P1-C1 v MCM module 3 at U1.18-P1-C2 v MCM module 1 at U1.18-P1-C3 v MCM module 2 at U1.18-P1-C4 Eserver pSeries 670 Service Guide...
Page 275 Step 1541-3 Is (are) the location code(s) recorded in “Step 1541-1” on page 254 also listed in “Step 1541-2” on page 254? Go to “Step 1541-19” on page 257. Go to “Step 1541-4”. Step 1541-4 Check the following list to find the location code(s) recorded in “Step 1541-1” on page 254: v Fourth I/O book, at location U1.18-P1-H1 v Primary I/O Book at U1.18-P1-H2 v Secondary I/O Book at U1.18-P1-H3...
Page 276 Are all the amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 1541-16”. Call for support. Step 1541-16 Replace the primary I/O book at U1.18-P1-H2. Step 1541-17 Turn on the power. Eserver pSeries 670 Service Guide...
Page 277 Step 1541-18 Did the system stop with the same error code as recorded in “Step 1541-1” on page 254? Go to “Step 1541-37” on page 260. The part just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
Page 278 Memory Book 6 at U1.18-P1-M5 if not recorded in “Step 1541-1” on page 254. v Memory Book 7 at U1.18-P1-M1 if not recorded in “Step 1541-1” on page 254. Step 1541-28 Turn on the power. Eserver pSeries 670 Service Guide...
Page 279 Step 1541-29 Did the system stop with the same error code as recorded in “Step 1541-1” on page 254? Go to “Step 1541-30”. The book just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
Page 280 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Step 1541-43 Turn off the power. Make sure the amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 1541-44 Call for support. This ends the procedure. Eserver pSeries 670 Service Guide...
Page 281: Map 1542: I/O Problem Isolation
MAP 1542: I/O Problem Isolation This MAP is used to locate defective FRUs not found by normal diagnostics. For this procedure, diagnostics are run on a minimally configured system. If a failure is detected on the minimally configured system, the remaining FRUs are exchanged one at a time until the failing FRU is identified. If a failure is not detected, FRUs are added back until the failure occurs.
Page 282 Restore fast-boot mode (select Enable Fast Boot) on the System Power Control menu from the service processor main menu. Go to “Checkpoints and Error Codes Index” on page 348, and follow the actions for the new error code. Eserver pSeries 670 Service Guide...
Page 283 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 284 RIO cable from I/O subsystem 1 right I/O port connector 1 (U1.9-P2/Q1) to processor subsystem RIO port A1 on primary I/O book (U1.18-P1-H2/Q2). Reconfigure the system to its original condition. Go to “MAP 0410: Repair Checkout” in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 670 Service Guide...
Page 285 Step 1542-6 The Eserver pSeries 670 server must have a minimum of one I/O subsystem and one media subsystem attached to the processor subsystem. The following steps reduce the system I/O to the required minimum of one I/O subsystem: 1. Turn off the system power.
Page 286 (U1.9-P2-V1/Q3) and the media subsystem. The media subsystem operator panel momentarily displays an OK prompt. 9. Set the current drawer location to x.y=1.9. Use this value in future steps until changed in a later step. Go to “Step 1542-9” on page 267. Eserver pSeries 670 Service Guide...
Page 287 Step 1542-9 Are there any adapters in slots 1, 2, 3, 4 or 5 (location codes Ux.y-P1-I1 through I5) on the left side of the I/O subsystem? Go to “Step 1542-10”. Go to “Step 1542-13”. Step 1542-10 Are there any adapters in slots 6, 7, 8, 9 or 10 (location codes Ux.y-P1-I6 through I10) on the left side of the I/O subsystem? Go to “Step 1542-11”.
Page 288 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? Go to “Step 1542-12” on page 267. Go to “Step 1542-17” on page 269. Eserver pSeries 670 Service Guide...
Page 289 Step 1542-16 1. If it is not already off, turn off the power. 2. Remove all adapters from slots 6, 7, 8, 9 and 10 (location codes Ux.y-P2-I6 through I10) from the right side of the I/O subsystem that are not attached to the boot device. 3.
Page 290 The I/O subsystem backplane is defective. Replace the I/O subsystem backplane on the side of the problem adapter (Ux.y-P1 or Ux.y-P2). Go to “Step 1542-20” on page 272. The adapter was defective. Go to “Step 1542-20” on page 272. Eserver pSeries 670 Service Guide...
Page 291 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. Boot device SCSI cable b. Boot device SCSI adapter c. Boot device SCSI backplane d.
Page 292 “Step 1542-28” on page 278 2.13 2.19 “Step 1542-29” on page 279 2.19 2.19 “Step 1542-30” on page 279 Note: The I/O subsystems should be cabled as shown in “Subsystem Positioning and Cabling” on page 37. Eserver pSeries 670 Service Guide...
Page 293 Step 1542-23 1. Turn off the power. 2. At the primary I/O book, disconnect the cable connection at RIO port B0 (U1.18-P1-H2/Q3). 3. Disconnect the cable connection at I/O subsystem 2 left I/O port connector 0 (U1.5-P1/Q2). The RIO cable that was connected to RIO port B0 should now be loose and can be removed. 4.
Page 294 RIO cable from I/O subsystem 3 right I/O port connector 1 (U1.1-P2/Q1) to processor subsystem RIO port C1 on secondary I/O book (U1.18-P1-H3/Q7). Reconfigure the system to its original condition. Go to “MAP 0410: Repair Checkout” in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 670 Service Guide...
Page 295 Step 1542-25 1. Turn off the power. 2. At the secondary I/O book, disconnect the cable connection at RIO port D0 (U1.18-P1-H3/Q6). 3. Disconnect the cable connection at I/O subsystem 4 left I/O port connector 0 (Ux.y-P1/Q2). The RIO cable that was connected to RIO port D0 should now be loose and can be removed. 4.
Page 296 RIO cable from I/O subsystem 5 right I/O port connector 1 (U2.1-P2/Q1) to processor subsystem RIO port A1 on secondary I/O book (U1.18-P1-H3/Q3). Reconfigure the system to its original condition. Go to “MAP 0410: Repair Checkout” in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 670 Service Guide...
Page 297 Step 1542-27 1. Turn off the power. 2. At the secondary I/O book, disconnect the cable connection at RIO port B0 (U1.18-P1-H3/Q2). 3. Disconnect the cable connection at I/O subsystem 6 left I/O port connector 0 (U2.5-P1/Q2). The RIO cable that was connected to RIO port B0 should now be loose and can be removed. 4.
Page 298 RIO cable from I/O subsystem 7 right I/O port connector 1 (U2.13-P2/Q1) to processor subsystem RIO port C1 on secondary I/O book (U1.18-P1-H4/Q7). Reconfigure the system to its original condition. Go to “MAP 0410: Repair Checkout” in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 670 Service Guide...
Page 299 Step 1542-29 1. Turn off the power. 2. At the secondary I/O book, disconnect the cable connection at RIO port D0 (U1.18-P1-H4/Q6). 3. Disconnect the cable connection at I/O subsystem 8 left I/O port connector 0 (U2.19-P1/Q2). The RIO cable that was connected to RIO port D0 should now be loose and can be removed 4.
Page 300: Map 1543: Mcm Module Problem Isolation
9. MCM module 2 at U1.18-P1-C4 if not recorded in “Step 1543-1”. 10. MCM module 1 at U1.18-P1-C3 if not recorded in “Step 1543-1”. 11. MCM module 3 at U1.18-P1-C2 if not recorded in “Step 1543-1”. Step 1543-5 Turn on the power. Eserver pSeries 670 Service Guide...
Page 301 Step 1543-6 Did the system stop with the same error code as recorded in “Step 1543-1” on page 280? Go to “Step 1543-7”. The module just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
Page 302: Map 1544: Inner L3 Module Problem Isolation
The book or module just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 670 Service Guide...
Page 303 Step 1544-7 Have all the books or modules listed in “Step 1544-4” on page 282 been replaced? Go to “Step 1544-8”. Go to “Step 1544-2” on page 282. Step 1544-8 Turn off the power. Step 1544-9 Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 1544-10 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 1544-11”.
Page 304: Map 1545: Outer L3 Module Problem Isolation
1. First location code item recorded, if any, in “Step 1545-1”. 2. Second location code item recorded, if any, in “Step 1545-1”. 3. Third location code item recorded, if any, in “Step 1545-1”. Step 1545-5 Turn on the power. Eserver pSeries 670 Service Guide...
Page 305 Step 1545-6 Did the system stop with the same error code as recorded in “Step 1545-1” on page 284? Go to “Step 1545-7”. The book or module just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
Page 306: Map 1546: Memory Book Problem Isolation
L3 module at U1.18-P1-C18 if not recorded in “Step 1546-1”. v L3 module at U1.18-P1-C19 if not recorded in “Step 1546-1”. v L3 module at U1.18-P1-C20 if not recorded in “Step 1546-1”. Step 1546-5 Turn on the power. Eserver pSeries 670 Service Guide...
Page 307 Step 1546-6 Did the system stop with the same error code as recorded in “Step 1546-1” on page 286? Go to “Step 1546-7”. The book or module just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
Page 308: Map 1547: I/O Book Problem Isolation
Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 1547-11”. Call for support. Step 1547-11 Attention: Before replacing the system backplane, call for support. Replace the system backplane at U1.18-P1. Eserver pSeries 670 Service Guide...
Page 309 Step 1547-12 Turn on the power. Step 1547-13 Did the system stop with the same error code as recorded in “Step 1547-1” on page 288? Go to “Step 1547-14”. The part just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
Page 310: Map 1548: Memory And Processor Problem Isolation
MCM module 2 at U1.18-P1-C4 if not recorded in “Step 1548-1”. v MCM module 1 at U1.18-P1-C3 if not recorded in “Step 1548-1”. v MCM module 3 at U1.18-P1-C2 if not recorded in “Step 1548-1”. Eserver pSeries 670 Service Guide...
Page 311 Step 1548-5 Turn on the power. Step 1548-6 Did the system stop with the same error code as recorded in “Step 1548-1” on page 290? Go to “Step 1548-7”. The book or module just replaced was defective. This ends the procedure. Return the system to its original configuration.
Page 312 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Step 1548-14 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 1548-15 Call for support. This ends the procedure. Eserver pSeries 670 Service Guide...
Page 313: 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. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 1549-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Call for support.
Page 314 Multiple Bus Systems. Go to “Step 1549-8”. Step 1549-8 Have all the books or modules listed in “Step 1549-5” been replaced? Go to “Step 1549-37” on page 299. Go to “Step 1549-2” on page 293. Eserver pSeries 670 Service Guide...
Page 315 Step 1549-9 Attention: Some of the parts in the following list are modules that have a limit of three plug cycles. Before replacing any of the modules in the following list, call for support. Replace the following books and modules, if present, one at a time: v First location code item recorded, if any, in “Step 1549-1”...
Page 316 Memory book 3 at U1.18-P1-M6 if not recorded in “Step 1549-1” on page 293. v Primary I/O Book at U1.18-P1-H2 if not recorded in “Step 1549-1” on page 293. Step 1549-18 Turn on the power. Eserver pSeries 670 Service Guide...
Page 317 Step 1549-19 Did the system stop with the same error code as recorded in “Step 1549-1” on page 293? The book or module just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
Page 318 The book or module just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 1549-32” on page 299. Eserver pSeries 670 Service Guide...
Page 319 Step 1549-32 Have all the books or modules listed in “Step 1549-29” on page 298 been replaced? Go to “Step 1549-2” on page 293. Go to “Step 1549-37”. Step 1549-33 Replace the following books and modules, if present, one at a time: v Replace the Primary I/O Book at U1.18-P1-H2 if not recorded in “Step 1549-1”...
Page 320 Multiple Bus Systems. Go to “Step 1549-43”. Step 1549-43 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 1549-44 Call for support. This ends the procedure. Eserver pSeries 670 Service Guide...
Page 321: Map 154A: I2C Bus Problem Isolation
MAP 154A: I2C Bus Problem Isolation Step 154A-1 Record the error code, location code(s), word 13, and word 16 that sent you to this MAP. Step 154A-2 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 154A-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Call for support.
Page 322 Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 154A-16 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Call for support. Go to “Step 154A-17” on page 303. Eserver pSeries 670 Service Guide...
Page 323 Step 154A-17 Attention: Before replacing the system backplane, call for support. Replace the system backplane at U1.18-P1. Step 154A-18 Turn on the power. Step 154A-19 Did the system stop with the same error code as recorded in “Step 154A-1” on page 301? The book or module just replaced was defective.
Page 324 Go to “Step 154A-14” on page 302. Eserver pSeries 670 Service Guide...
Page 325: 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. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 154B-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Call for support.
Page 326 Multiple Bus Systems. Go to “Step 154B-14”. Step 154B-14 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 154B-15 Call for support. This ends the procedure. Eserver pSeries 670 Service Guide...
Page 327: 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 328 Number of bootable adapters Phase 4 0xxx or 2xxx => blank 2 to 30+ Number of SSA drives Number of SCSI drives Number of async sessions Number of processors Number of adapters Amount of memory Eserver pSeries 670 Service Guide...
Page 329 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 330: Service Processor Checkpoints
Primary service processor thread waiting See note 1 on page 315. for response 9020 Service processor state set to pre-standby See note 1 on page 315. 9021 Service processor state set to standby See note 1 on page 315. Eserver pSeries 670 Service Guide...
Page 331 Checkpoint Description Action/ Possible Failing FRU 9022 Service processor state set to IPL See note 1 on page 315. 9023 Service processor state set to runtime See note 1 on page 315. 9024 Service processor state set to terminate See note 1 on page 315. 9025 Service processor state set to DPO See note 1 on page 315.
Page 332 See note 1 on page 315. from service processor 9200 Scan interface BATs See note 1 on page 315. 9300 Logic BIST See note 1 on page 315. 9301 Scanned ABIST See note 1 on page 315. Eserver pSeries 670 Service Guide...
Page 333 Checkpoint Description Action/ Possible Failing FRU 9302 Dedicated ABIST See note 1 on page 315. 9303 Dedicated ABIST array fuse repair See note 1 on page 315. calculation 9380 Built-in-self-test (BIST) See note 2 on page 315. 9400 Service processor is requesting system See note 1 on page 315.
Page 334 See note 1 on page 315. A80D Reserved; not used See note 1 on page 315. A80E Reserved; not used See note 1 on page 315. A80F Service processor dump done See note 1 on page 315. Eserver pSeries 670 Service Guide...
Page 335 Checkpoint Description Action/ Possible Failing FRU A810-A8FF Scan log dump in progress Informational message. (See “Scan Log Dump Policy” on page 718.) The last two characters of the checkpoints will change as the scan log dump progresses. If the last two characters do not change after five minutes, the service processor is hung and must be reset.
Page 336 If there is not, or the update does not fix the problem, replace the following FRUs, one at a time, in the following order: 1) Modem cable 2) Modem d. If this procedure does not fix the problem, call service support. Eserver pSeries 670 Service Guide...
Page 337: 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 310. If you have a checkpoint with no location code associated with it, see “Determining Location Code”...
Page 338 Follow the repair action listed for checkpoint E151. E170 Start of PCI Bus Probe Follow the repair action listed for checkpoint E151. E172 First pass of PCI device probe Follow the repair action listed for checkpoint E151. Eserver pSeries 670 Service Guide...
Page 339 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 340 Procedures” on page 253. E1AF System booted to utilities menu via NVRAM Go to “MAP 1540: Problem Isolation settings Procedures” on page 253. E1B1 Create serial node Go to “MAP 1540: Problem Isolation Procedures” on page 253. Eserver pSeries 670 Service Guide...
Page 341 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. 6. There may be a hardware problem with the service processor in the managed system.
Page 342 E1F4 End self-test sequence on boot devices; Go to “MAP 1542: I/O Problem Isolation” on begin SMS. page 261. E1F5 Build boot device list Go to “MAP 1542: I/O Problem Isolation” on page 261. Eserver pSeries 670 Service Guide...
Page 343 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E1F6 Determine boot device sequence Go to “MAP 1542: I/O Problem Isolation” on page 261. E1F7 No boot image located Go to “Boot Problems” on page 342. E1F8 Partition (system firmware) is waiting for a Open a virtual terminal for the partition on virtual terminal to be opened on HMC.
Page 344 2. Go to “MAP 1542: I/O Problem Isolation” on page 261. E50A Check for missing I/O interface chips 1. Check for system firmware updates. 2. Go to “MAP 1542: I/O Problem Isolation” on page 261. Eserver pSeries 670 Service Guide...
Page 345 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E50B Save I/O hub information 1. Check for system firmware updates. 2. Go to “MAP 1542: I/O Problem Isolation” on page 261. E50C Copy all of the memory ranges 1.
Page 346 I./O book that the RIO cables in step 1 are attached to. 4. Replace the I/O subsystem backplane specified by the location code, or the I/O subsystem backplane that the RIO cables in step 1 are attached to. Eserver pSeries 670 Service Guide...
Page 347 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E529 Enable the control port and driver of the 1. Check the RIO cable specified by the current RIO hub 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 348 3. Replace the I/O book that the failing I/O subsystem is attached to, U1.18-P1-Hx. 4. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached 5. Go to “MAP 1542: I/O Problem Isolation” on page 261. Eserver pSeries 670 Service Guide...
Page 349 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E535 Valid node ID detected at other end of the 1. Replace the I/O cable specified by the I/O cable location code. 2. Replace the I/O book that the failing I/O subsystem is attached to, U1.18-P1-Hx.
Page 350 1. Replace the I/O cable specified by the location code. 2. Replace the I/O book that the failing I/O subsystem is attached to, U1.18-P1-Hx. 3. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached Eserver pSeries 670 Service Guide...
Page 351 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E54A Configure the I/O drawer Check the RIO cable specified by the 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 352 I/O cable in step 1 is attached E565 Set up I/O interface chip registers 1. Replace the I/O cable specified by the location code. 2. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached Eserver pSeries 670 Service Guide...
Page 353 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E566 Enable device arbitration on the I/O 1. Replace the I/O cable specified by the interface chip location code. 2. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached E567 Set up I/O interface chip registers 1.
Page 354 I/O cable in step 1 is attached E583 Running BIST on the current EADS 1. Replace the I/O cable specified by the location code. 2. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached Eserver pSeries 670 Service Guide...
Page 355 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E584 Checking function of current EADS 1. Replace the I/O cable specified by the location code. 2. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached E585 Valid function of current EADS detected 1.
Page 356 2. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached E595 Detected valid adapter in slot 1. Check for system firmware updates. 2. Go to “MAP 1542: I/O Problem Isolation” on page 261. Eserver pSeries 670 Service Guide...
Page 357 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E596 Read the EADS revision ID and class code 1. Replace the RIO cable specified by the location code. 2. Replace the I/O subsystem planar to which the RIO cable in Step 1 is attached.
Page 358 2. Call for support. E705 Create clock card VPD. 1. Check for system firmware updates. 2. Call for support. E706 Create RIO extender card VPD. 1. Check for system firmware updates. 2. Call for support. Eserver pSeries 670 Service Guide...
Page 359 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E707 Create system VPD. 1. Check for system firmware updates. 2. Call for support. E708 Create RIO to PCI adapter VPD. Go to “MAP 1542: I/O Problem Isolation” on page 261.
Page 360 1. Check for system firmware updates. 2. Call service support. E871 Initializing RTAS/EEH handling interface 1. Check for system firmware updates. 2. Go to “MAP 1542: I/O Problem Isolation” on page 261. 3. Call service support. Eserver pSeries 670 Service Guide...
Page 361 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E872 Initializing RTAS/error inject interface 1. Check for system firmware updates. 2. Call service support. E873 Initializing RTAS/error handling interface 1. Check for system firmware updates. 2. Call service support. E880 Initializing RTAS/debug interface 1.
Page 362: Boot Problems
1) Remove all removable media from devices in the boot list from which you do not want to boot. 2) If attempting to boot from a network, go to step 3 on page 343. If attempting to boot from a disk drive or CD-ROM, go to step 4 on page 343. Eserver pSeries 670 Service Guide...
Page 363 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 364 Check the network settings and flag settings, as detailed in “Running Standalone Diagnostics from a Network Installation Management (NIM) Server” on page 706. c. Follow the procedure outlined in step 3 on page 343. 5. Go to “MAP 1542: I/O Problem Isolation” on page 261. Eserver pSeries 670 Service Guide...
Page 365: 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 366: Confirming Initial Error Code
Return to the step in the “Checkpoints and Error Codes Index” on page 348 table immediately after the step that sent you to this ″Confirming Initial Error Code″ procedure to perform the listed repair actions. Eserver pSeries 670 Service Guide...
Page 367: Four-Character Checkpoints
If the repair actions for an error code are ineffective, continue to work upward through this group of 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. Four-Character Checkpoints Four-character checkpoints in the form 8xxx, 9xxx, Axxx, Bxxx, and Exxx are listed in “Firmware Checkpoints”...
Page 368: Checkpoints And Error Codes Index
Go to “SPCN Error Codes” on page 352 with the error code(s) from step 2 and follow the instructions in the SPCN error code table. 2xxx xxxx Firmware Error Codes Go to “Firmware/POST Error Codes” on page 413, and follow the instructions in the firmware error code table. Eserver pSeries 670 Service Guide...
Page 369 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 step 3 below.
Page 370 Go to “Firmware Checkpoints” on page 317 for more information on these checkpoints. Mxxx xxxx Problem Determination-Generated Error Codes Go to “Problem Determination-Generated Error Codes” on page 695, and follow the instructions in the error code table. Eserver pSeries 670 Service Guide...
Page 371: 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 261 unless you were already directed to any MAP 154x by the error code.
Page 372: Spcn Error Codes
Primary I/O book Location: U1.18-P1-H2 1011 3104 I2C bus 4 fault Primary I/O book Location: U1.18-P1-H2 1011 3106 I2C bus 6 fault Primary I/O book Location: U1.18-P1-H2 1011 3113 RIO Bus Adapter Primary I/O book Location: U1.18-P1-H2 Eserver pSeries 670 Service Guide...
Page 373 Error Code Description Action/ Possible Failing FRU 1011 3114 PCI Backplane Was the primary I/O book at location U1.18-P1-H2 changed prior to the most recent reboot of the system? This error code may be due to down-level system power control network firmware on the new primary I/O book.
Page 374 See note on page 441. 2. Primary I/O book Location: U1.18-P1-H2 1011 8423 No MCM 0 VPD card or MCM 1. Location: U1.18-P1-H2.3 and U1.18-P1-C1 See note on page 441. 2. Primary I/O book Location: U1.18-P1-H2 Eserver pSeries 670 Service Guide...
Page 375 Error Code Description Action/ Possible Failing FRU 1011 8424 No MCM 2 VPD card or MCM 1. Location: U1.18-P1-H2.4 and U1.18-P1-C4 See note on page 441. 2. Primary I/O book Location: U1.18-P1-H2 1011 8425 No MCM 1 VPD card or MCM 1.
Page 376 2. BPC A controller Location: U1.35-P1-X4 and BPC-B controller, Location: U1.35-P2-X4 3. Primary I/O book Location: U1.18-P1-H2 1011 8750 BPC download failure on BPA A 1. BPC A controller, Location: U1.35-P1-X4 2. Primary I/O book, Location: U1.18-P1-H2 Eserver pSeries 670 Service Guide...
Page 377 Error Code Description Action/ Possible Failing FRU 1011 8751 BPC download failure on BPA B 1. BPC-B controller, Location: U1.35-P2-X4 2. Primary I/O book, Location: U1.18-P1-H2 1011 8800 BPC A cable missing 1. BPC A cable to primary I/O book Location: U1.18-P1-H2/Q8# 2.
Page 378 1014 B844 Overcurrent or overvoltage problem with 12.0V Go to “MAP 1520: Power” on page 144. in first I/O subsystem 1014 B854 Overcurrent or overvoltage problem with -12.0V Go to “MAP 1520: Power” on page 144. in first I/O subsystem Eserver pSeries 670 Service Guide...
Page 379 Error Code Description Action/ Possible Failing FRU 1014 BF06 Unable to resolve the chassis VPD in an I/O The chassis VPD in the I/O subsystem drawer subsystem identified by the location code could not be resolved. This may be an indication that more than one FRU in the drawer was replaced during a service action.
Page 380 1. DCA-1 primary rack. Location: U1.5-V2 2. Fan 1 Location: U1.5-F2 1015 1C06 Loss of airflow in second I/O subsystem, Go to “MAP 1527: An Airflow Loss Has Been location: U1.5 Detected” on page 160. Eserver pSeries 670 Service Guide...
Page 381 Error Code Description Action/ Possible Failing FRU 1015 6014 Overcurrent or overvoltage problem with 3.3V in Go to “MAP 1520: Power” on page 144. second I/O subsystem 1015 6024 Overcurrent or overvoltage problem with 5.0V in Go to “MAP 1520: Power” on page 144. second I/O subsystem 1015 6034 Overcurrent or overvoltage problem with 2.5V in Go to “MAP 1520: Power”...
Page 382 FRU indicated with this error code, if any, should be replaced. 1015 xx11 Second I/O subsystem in primary rack, DCA-1 U1.5-V1 1015 xx13 Seeprom fault on DCA-1 in second I/O U1.5-V1 subsystem in primary rack Eserver pSeries 670 Service Guide...
Page 383 Error Code Description Action/ Possible Failing FRU 1015 xx15 Second I/O subsystem in primary rack, DCA-1, Go to “MAP 1520: Power” on page 144 with cable fault these pairs of location codes: 1. U1.5-V1/Q1 and U1.35-P2-X3/Q3 2. U1.5-V1/Q2 and U1.35-P1-X3/Q3 1015 xx17 Problem with fan 1 and fan 3 in second I/O 1.
Page 384 2. Fans 1 and 3 Location: U1.1-F1 and U1.1-F3 1016 7127 Problem with fan 2 and fan 4 in third I/O 1. DCA-2 subsystem in primary rack Location: U1.1-V2 2. Fans 2 and 4 Location: U1.1-F2 and U1.1-F4 Eserver pSeries 670 Service Guide...
Page 385 Error Code Description Action/ Possible Failing FRU 1016 B014 Overcurrent or overvoltage problem with 3.3V in Go to “MAP 1520: Power” on page 144. third I/O subsystem 1016 B024 Overcurrent or overvoltage problem with 5.0V in Go to “MAP 1520: Power” on page 144. third I/O subsystem 1016 B034 Overcurrent or overvoltage problem with 2.5V in Go to “MAP 1520: Power”...
Page 386 I/O subsystem in primary rack 1016 xx51 Third I/O subsystem in primary rack, DASD U1.1-P3 backplane 1 fault 1016 xx53 Seeprom fault on DASD backplane 1 in third I/O U1.1-P3 subsystem in primary rack Eserver pSeries 670 Service Guide...
Page 387 Error Code Description Action/ Possible Failing FRU 1016 xx61 Third I/O subsystem in primary rack, DASD U1.1-P4 backplane 2 fault 1016 xx63 Seeprom fault on DASD backplane 2 in third I/O U1.1-P4 subsystem in primary rack 1016 xx71 Third I/O subsystem in primary rack, DASD U1.1-P5 backplane 3 fault 1016 xx73 Seeprom fault on DASD backplane 3 in third I/O...
Page 388 Go to “MAP 1520: Power” on page 144. subsystem in an I/O drawer. 1017 CDB6 A power short has been detected in the DASD Go to “MAP 1520: Power” on page 144. subsystem in an I/O drawer. Eserver pSeries 670 Service Guide...
Page 389 Error Code Description Action/ Possible Failing FRU 1017 CDC6 A power short has been detected in the DASD Go to “MAP 1520: Power” on page 144. subsystem in an I/O drawer. 1017 F4x6 Hardware configuration does not support Call Service Support N-mode power.
Page 390 Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault” on page 152. 101A 0866 BPR 2A communications fault Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault” on page 152. Eserver pSeries 670 Service Guide...
Page 391 Error Code Description Action/ Possible Failing FRU 101A 0876 BPR 3A communications fault Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault” on page 152. 101A 0D06 350 volt bulk failure, BPA-A Go to “MAP 1525: There Is a 350 Volt Bulk Failure”...
Page 392 Informational message. If a problem is message) suspected: 1. Verify the cabling between the UPS and the BPCs. 2. Refer to the manufacturer’s documentation for the UPS. 3. Call service support. 101A DC56 Informational message about the IBF. Informational message. Eserver pSeries 670 Service Guide...
Page 393 Error Code Description Action/ Possible Failing FRU 101A DC66 Informational message about the IBF. Informational message. 101A DC76 Informational message about the IBF. Informational message. 101A DD16 External UPS: bypass ended (informational Informational message. If a problem is message) suspected: 1.
Page 394 Go to “MAP 1520: Power” on page 144 with these location codes: U1.35-P1-X3/Q3# to U1.5-V1/Q2# 101A x335 Power cable fault Go to “MAP 1520: Power” on page 144 with these location codes: U1.35-P1-X2/Q3# to U2.5-V1/Q1# Eserver pSeries 670 Service Guide...
Page 395 Error Code Description Action/ Possible Failing FRU 101A x415 Power cable fault Go to “MAP 1520: Power” on page 144 with these location codes: U1.35-P1-X4/Q4# to U1.18-X4/Q1# 101A x425 Power cable fault Go to “MAP 1520: Power” on page 144 with these location codes: U1.35-P1-X3/Q4# to U1.5-V2/Q2# 101A x435 Power cable fault...
Page 396 101A xx22 BPC-A to BPD-1 communications fault 1. BPD-1 Location: U1.35-P1-X3 2. BPC-A Location: U1.35-P1-X4 3. BPE backplane A Location: U1.35-P1 101A xx23 Seeprom (VPD) fault on BPD-1A U1.35-P1-X3 101A xx31 BPA-A / BPD-2 U1.35-P1-X2 Eserver pSeries 670 Service Guide...
Page 397 Error Code Description Action/ Possible Failing FRU 101A xx32 BPC-A to BPD-2 communications fault 1. BPD-2 Location: U1.35-P1-X2 2. BPC-A Location: U1.35-P1-X4 3. BPE backplane A Location: U1.35-P1 101A xx33 Seeprom (VPD) fault on BPD-2A U1.35-P1-X2 101A xx41 BPA-A / BPD-3 U1.35-P1-X1 101A xx42 BPC-A to BPD-3 communications fault 1.
Page 398 Go to “MAP 1526: There Is An Integrated Battery Feature (IBF) Failure” on page 157. 101B 7BA6 IBF 3B failure Go to “MAP 1526: There Is An Integrated Battery Feature (IBF) Failure” on page 157. Eserver pSeries 670 Service Guide...
Page 399 Error Code Description Action/ Possible Failing FRU 101B CE16 BPC-BPC communication failure 1. Check the cable between the two BPCs; reseat and look for bent pins. 2. Replace BPC-A, location: U1.35-P1-X4 3. Replace BPC-B, location: U1.35-P2-X4. 101B D216 BPA-BPA communication failure Go to “MAP 1520: Power”...
Page 400 101B FE16 UEPO switch on BPC B is in the bypass position Go to “MAP 1522: UEPO Switch On The BPC Is In The Bypass Position” on page 151. 101B FE56 BPR 1B communications fault Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault” on page 152. Eserver pSeries 670 Service Guide...
Page 401 Error Code Description Action/ Possible Failing FRU 101B FE66 BPR 2B communications fault Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault” on page 152. 101B FE76 BPR 3B communications fault Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault”...
Page 402 Go to “MAP 1520: Power” on page 144 with these location codes: U1.35-P2-X2/Q7# to U2.13-V1/Q2# 101B x825 Power cable fault Go to “MAP 1520: Power” on page 144 with these location codes: U1.35-P2-X3/Q8# to U1.13-V2/Q1# Eserver pSeries 670 Service Guide...
Page 403 Error Code Description Action/ Possible Failing FRU 101B x835 Power cable fault If there is no DCA in U1.18-P1-V8, go to “MAP 1520: Power” on page 144 with these location codes: U1.35-P2-X3/Q8# to U1.13-V2/Q1# If there is a 6th DCA in U1.18-P1-V8, this error code will not be reported.
Page 404 101B xx83 Seeprom (VPD) fault on IBF-1B U1.13-P2-V3 101B xx91 BPA-B / IBF 2 U1.15-P2-V4 101B xx93 Seeprom (VPD) fault on IBF-2B U1.15-P2-V4 101B xxA1 BPA-B / IBF 3 U2.17-P2-V6 101B xxA3 Seeprom (VPD) fault on IBF-3B U2.17-P2-V6 Eserver pSeries 670 Service Guide...
Page 405 Error Code Description Action/ Possible Failing FRU 101B xxB1 BPA-B / EPO_SW 1. Replace the UEPO switch, Location: U1-V1 2. Check the cable from BPC-B to the UEPO switch, Location U1-V1/Q2# 101C 0FB6 MCM 0 running over temperature 1. Verify that the MCM at U1.18-P1-C1 is installed.
Page 406 2. Verify that the processor MCMs are seated properly. 3. Verify the processor VPD cards in the primary I/O book are of the proper number and are positioned and seated correctly. 4. Call service support. Eserver pSeries 670 Service Guide...
Page 407 Error Code Description Action/ Possible Failing FRU 101C 7EB6 MCM 0 running over temperature 1. Verify that the MCM at U1.18-P1-C1 is installed. 2. Verify that there are no airflow problems with the MCM at U1.18-P1-C1 or its heatsink. 3. Verify that the MCM at U1.18-P1-C1 is installed correctly onto the processor backplane.
Page 408 2. Verify that there are no airflow problems with the MCM at U1.18-P1-C3 or its heatsink. 3. Verify that the MCM at U1.18-P1-C3 is installed correctly onto the processor backplane. 4. Call service support. Eserver pSeries 670 Service Guide...
Page 409 Error Code Description Action/ Possible Failing FRU 101C E1D6 MCM 2 running over temperature 1. Verify that the MCM at U1.18-P1-C4 is installed. 2. Verify that there are no airflow problems with the MCM at U1.18-P1-C4 or its heatsink. 3. Verify that the MCM at U1.18-P1-C4 is installed correctly onto the processor backplane.
Page 410 Examine the service processor error log. If there are no other power-related error codes (in the time frame in which this code was generated) in the service processor error log, the FRU indicated with this error code, if any, should be replaced. Eserver pSeries 670 Service Guide...
Page 411 Error Code Description Action/ Possible Failing FRU 101C F596 An N+1 boundary (DCA or fan) has dropped to This is normally an informational message. It N-mode status in the processor subsystem, should be accompanied by other error codes location: U1.18 that more precisely indicate where the failure is.
Page 412 1. U1.18-X3/Q1 and U1.35-P1-X4/Q3 2. U1.18-X3/Q2 and U1.35-P2-X4/Q3 101C xx97 Fan fault on processor subsystem fan 3 1. Fan 3 controller Location: U1.18-X3 2. Fan 3 Location: U1.18-F3 101C xxA1 Processor subsystem / MDA-4 U1.18-X4 Eserver pSeries 670 Service Guide...
Page 413 Error Code Description Action/ Possible Failing FRU 101C xxA3 Seeprom (VPD) fault on processor subsystem U1.18-X4 MDA-4 101C xxA5 Processor subsystem / MDA-4 cable fault Go to “MAP 1520: Power” on page 144 with these pairs of location codes: 1. U1.18-X4/Q1 and U1.35-P1-X4/Q4 2.
Page 414 Go to “MAP 1520: Power” on page 144. subsystem in an I/O drawer. 1021 CDB6 A power short has been detected in the DASD Go to “MAP 1520: Power” on page 144. subsystem in an I/O drawer. Eserver pSeries 670 Service Guide...
Page 415 Error Code Description Action/ Possible Failing FRU 1021 CDC6 A power short has been detected in the DASD Go to “MAP 1520: Power” on page 144. subsystem in an I/O drawer. 1021 F4x6 Hardware configuration does not support Call Service Support N-mode power.
Page 416 I/O subsystem in second rack (I/O subsystem 6) 1022 6054 Overcurrent or overvoltage problem with -12.0V Go to “MAP 1520: Power” on page 144. in second I/O subsystem in second rack (I/O subsystem 6) Eserver pSeries 670 Service Guide...
Page 417 Error Code Description Action/ Possible Failing FRU 1022 6814 Overcurrent or overvoltage problem with 3.3V in Go to “MAP 1520: Power” on page 144. second I/O subsystem in second rack (I/O subsystem 6) 1022 6824 Overcurrent or overvoltage problem with 5.0V in Go to “MAP 1520: Power”...
Page 418 1022 xx11 Second I/O subsystem in second rack (I/O U2.5-V1 subsystem 6), DCA-1 1022 xx13 Seeprom fault on DCA-1 in second I/O U2.5-V1 subsystem in second rack (I/O subsystem 6) Eserver pSeries 670 Service Guide...
Page 419 Error Code Description Action/ Possible Failing FRU 1022 xx15 Second I/O subsystem in second rack (I/O Go to “MAP 1520: Power” on page 144 with subsystem 6), DCA-1, cable fault these pairs of location codes: 1. U2.5-V1/Q1 and U1.35-P2-X2/Q3 2. U2.5-V1/Q2 and U1.35-P1-X2/Q3 1022 xx17 Problem with fan 1 and fan 3 in second I/O 1.
Page 420 I/O subsystem (with IBF, moves to second rack) 1023 6854 Overcurrent or overvoltage problem with -12.0V Go to “MAP 1520: Power” on page 144. in fourth I/O subsystem (with IBF, moves to second rack) Eserver pSeries 670 Service Guide...
Page 421 Error Code Description Action/ Possible Failing FRU 1023 7017 Problem with fan 3 in fourth I/O subsystem (with 1. DCA-1 IBF, moves to second rack) Location: U2.9-V1 2. Fan 3 Location: U2.9-F3 1023 7027 Problem with fan 4 in fourth I/O subsystem (with 1.
Page 422 2. U2.9-V1/Q2 and U1.35-P1-X2/Q5 1023 xx17 Problem with fan 1 and fan 3 in fourth I/O 1. DCA-1 subsystem (with IBF, moves to second rack) Location U2.9–V1 2. Fan 1, Location U2.9–F1 3. Fan 3, Location U2.9–F3 Eserver pSeries 670 Service Guide...
Page 423 Error Code Description Action/ Possible Failing FRU 1023 xx21 Fourth I/O subsystem moves to second rack U2.9-V2 (with IBF), DCA-2 1023 xx23 Seeprom fault on DCA-2 in fourth I/O subsystem U2.9-V2 (with IBF) in secondary rack 1023 xx25 Fourth I/O subsystem moves to second rack Go to “MAP 1520: Power”...
Page 424 (I/O subsystem 7) Location: U2.13-V1 2. Fan 3 Location: U2.13-F3 1024 7027 Problem with fan 4 in third I/O subsystem in 1. DCA-2 second rack (I/O subsystem 7) Location: U2.13-V2 2. Fan 4 Location: U2.13-F4 Eserver pSeries 670 Service Guide...
Page 425 Error Code Description Action/ Possible Failing FRU 1024 7117 Problem with fan 1 and fan 3 in third I/O 1. DCA-1 subsystem in second rack (I/O subsystem 7) Location: U2.13-V1 2. Fans 1 and 3 Location: U2.13-F1 and U2.13-F3 1024 7127 Problem with fan 2 and fan 4 in third I/O 1.
Page 426 1024 xx15 Third I/O subsystem in second rack (I/O Go to “MAP 1520: Power” on page 144 with subsystem 7), DCA-1, cable fault these pairs of location codes: 1. U2.13-V1/Q1 and U1.35-P2-X2/Q7 2. U2.13-V1/Q2 and U1.35-P1-X2/Q7 Eserver pSeries 670 Service Guide...
Page 427 Error Code Description Action/ Possible Failing FRU 1024 xx17 Problem with fan 1 and fan 3 in third I/O 1. DCA-1 subsystem in second rack (I/O subsystem 7) Location U2.13–V1 2. Fan 1, Location U2.13–F1 3. Fan 3, Location U2.13–F3 1024 xx21 Third I/O subsystem in second rack (I/O U2.13-V2 subsystem 7), DCA-2...
Page 428 I/O subsystem in second rack (I/O Location: U2.19-V1 subsystem 8) 2. Fan 3 Location: U2.19-F3 1025 7027 Problem with fan 4 in fourth I/O subsystem in 1. DCA-2 second rack (I/O subsystem 8) Location: U2.19-V2 2. Fan 4 Location: U2.19-F4 Eserver pSeries 670 Service Guide...
Page 429 Error Code Description Action/ Possible Failing FRU 1025 7117 Problem with fan 1 and fan 3 in fourth I/O 1. DCA-1 subsystem in second rack (I/O subsystem 8) Location: U2.19-V1 2. Fans 1 and 3 Location: U2.19-F1 and U2.19-F3 1025 7127 Problem with fan 2 and fan 4 in fourth I/O 1.
Page 430 3. Fan 3, Location U2.19–F3 1025 xx21 Fourth I/O subsystem in second rack (I/O U2.19-V2 subsystem 8), DCA-2 1025 xx23 Seeprom fault on DCA-2 in fourth I/O subsystem U2.19-V2 in second rack (I/O subsystem 8) Eserver pSeries 670 Service Guide...
Page 431 Error Code Description Action/ Possible Failing FRU 1025 xx25 Fourth I/O subsystem in second rack (I/O If there is no DCA in U1.18-P1-V8, second rack subsystem 8), DCA-2, cable fault (I/O go to “MAP 1520: Power” on page 144 subsystem 8), DCA-2, with these pairs of location codes: 1.
Page 432 Error Code Description Action/ Possible Failing FRU SPCNtoB Go to “MAP 1529: There Is A Bulk Power Assembly (BPA) Communication Failure” on page 163. Eserver pSeries 670 Service Guide...
Page 433: 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 261 unless you were already directed to any MAP 154x by the error code.
Page 434 Refer to Table 2 on page 317 using code E175. 20A8 0005 File transmission (TFTP) failed. Check network connection, try again. 20A8 0006 Boot image too large Contact your next level of support for assistance. Eserver pSeries 670 Service Guide...
Page 435 Error Code Description Action/ Possible Failing FRU 20D0 0001 I/O subsystem has changed locations This is an informational message. The I/O subsystem at the location code associated with this messages was found at another location code during a prior boot of the system.
Page 436 2. Contact your next level of support for assistance. 20D0 0A0E Error initializing interface/timebase access 1. Check for system firmware updates. Apply update if available. 2. Contact your next level of support for assistance. Eserver pSeries 670 Service Guide...
Page 437 Error Code Description Action/ Possible Failing FRU 20D0 0A0F Error initializing interface/time-of-day access 1. Check for system firmware updates. Apply update if available. 2. Contact your next level of support for assistance. 20D0 0A10 Error initializing interface/cache access 1. Check for system firmware updates. Apply update if available.
Page 438 VPD module onto the new operator panel. Call service support for instructions on programming the VPD information into the new VPD module. 2. If the location code indicates an I/O subsystem, call service support. Eserver pSeries 670 Service Guide...
Page 439 Error Code Description Action/ Possible Failing FRU 20D0 9005 Subsystem serial number field is empty in 1. If the location code starts with U1.17 or U1.18, the problem is in the system VPD module on the media subsystem operator panel. Replace the operator panel; do not swap the old VPD module onto the new operator panel.
Page 440 2. Contact your next level of support for assistance. 20D1 000C Failed to send LMB-TABLE-INFO mailbox 1. Check for system firmware updates. Apply repair update if available. 2. Contact your next level of support for assistance. Eserver pSeries 670 Service Guide...
Page 441 Error Code Description Action/ Possible Failing FRU 20D1 000D Hypervisor function to get time-of-day failed 1. Check for system firmware updates. Apply update if available. 2. Contact your next level of support for assistance. 20D1 000F Hypervisor call to reset PHB or to check for 1.
Page 442 2. Call service support. 20EE 000B The system was not able to find an operating Go to “Boot Problems” on page 342. system on the devices in the boot list. Eserver pSeries 670 Service Guide...
Page 443 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 444 Installation Guide and Reference, order number SC23-4389, for more information. If this error occurs at any other time, complete the following steps: 1. Check for platform firmware updates. Apply if available. 2. Call service support. Eserver pSeries 670 Service Guide...
Page 445 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 446 20FF0090 Invalid VPD (empty VPD data from the Replace the part specified by the location service processor mailbox command) code. 2. If no location code is shown with the error code, call service support. Eserver pSeries 670 Service Guide...
Page 447 Error Code Description Action/ Possible Failing FRU 20FF00A0 Invalid VPD (getvpd mailbox command failed) 1. Replace the part specified by the location code. 2. If no location code is shown with the error code, call service support. 20FF00B0 Invalid VPD (the FG keyword is not found for 1.
Page 448 3. Replace the SCSI controller. 21ED 0002 SCSI changer: test unit ready failed; sense Before replacing any system components, data available refer to the Action under error code 21A0 0001. 1. Replace the SCSI device. 2. Replace the media. Eserver pSeries 670 Service Guide...
Page 449 Error Code Description Action/ Possible Failing FRU 21ED 0003 SCSI changer: send diagnostic failed; sense Before replacing any system components, data available refer to the Action under error code 21A0 0001. Replace the SCSI device. 21ED 0004 SCSI changer: send diagnostic failed - devofl Before replacing any system components, command refer to the Action under error code 21A0...
Page 450 20EE 0013 Unable to allocate memory for root-lpar-vpd 1. Verify that the system is in LPAR mode, and reboot the system. 2. Reflash the system with the latest level of system firmware. 3. Call service support. Eserver pSeries 670 Service Guide...
Page 451 Error Code Description Action/ Possible Failing FRU 25A0 0001 L2 Cache controller failure Replace the MCM module specified by the location code. 25A1 0001 L2 Cache SRAM failure Replace the MCM module specified by the location code. 25A8 0xxx NVRAM problems Errors reported against NVRAM can be caused by low battery voltage and (more rarely) power outages that occur during...
Page 452 25Cy y001 Memory book is not supported Replace unsupported memory book(s) specified by the location code. 25Cy y002 Memory book failure Replace the memory book(s) specified by the location code. Eserver pSeries 670 Service Guide...
Page 453 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 power subsystem cables, are not routed specified in the location code that appears correctly to the I/O subsystems with this error code.
Page 454 Check for system firmware updates. Apply if available. 2. If the location code identifies an I/O planar: a. Check for system firmware updates. Apply if available. b. Replace the I/O planar. 3. Call service support. Eserver pSeries 670 Service Guide...
Page 455 Error Code Description Action/ Possible Failing FRU 2602 0010 PCI probe error, bridge in freeze state If the location code identifies a slot or PCI adapter: 1. Check for system firmware updates. Apply if update available. 2. Check the cabling to the adapter (in particular, the adapters that have serial ports). Serial ports may require null modems or special cabling configurations to avoid connecting driver outputs together.
Page 456 See “Determining Location Code” on page 347 for location code information related to this error. 2680 0Dxx Machine check occurred; unable to isolate to Go to “MAP 1542: I/O Problem Isolation” on a single device page 261. Eserver pSeries 670 Service Guide...
Page 457 Error Code Description Action/ Possible Failing FRU 27A0 0001 Error obtaining external RIO cable IDs 1. Check the SPCN and RIO cabling going to the I/O subsystem specified by the location code. 2. Check for system firmware updates. 3. Replace the I/O subsystem planar specified by the location code.
Page 458 AIX error log entry in which the description says I/O bus time out, access, or other error, or I/O bridge/device internal error. Replace the FRUs listed in this entry. 2B20 8888 Operating system termination request Informational message. received Eserver pSeries 670 Service Guide...
Page 459 Error Code Description Action/ Possible Failing FRU 2B2x 00EE An exception error has been reported on a The type of interrupt that caused the global processor exception 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 460 Replace the MCM that contains the failing processor according to the following table: v hhh = 0 - 7: U1.18-P1-C1 v hhh = 8-15: U1.18-P1-C3 v hhh = 16-23: U1.18-P1-C4 v hhh = 24-31: U1.18-P1-C2 Eserver pSeries 670 Service Guide...
Page 461: Service Processor Error Codes
Service Processor Error Codes Attention: Follow the procedure defined in “Checkpoints and Error Codes Index” on page 348. 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 462 2. MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 4064 00B7 Processor subsystem tests detected Insufficient Go to “MAP 1540: Problem Isolation hardware resources to continue IPL after Procedures” on page 253. processor subsystem testing and initialization completed Eserver pSeries 670 Service Guide...
Page 463 Error Code Description Action/ Possible Failing FRU 4064 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. If AIX is available on the system, go to MAP 0235 in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems, order number SA38-0509.
Page 464 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 465 Error Code Description Action/ Possible Failing FRU 4064 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 466 4064 0B14 Processor subsystem tests detected fault in I/O 1. Check for system firmware updates. book 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4. Call service support. Eserver pSeries 670 Service Guide...
Page 467 Error Code Description Action/ Possible Failing FRU 4064 0B15 Processor subsystem tests detected fault in I/O 1. Check for system firmware updates. book 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4.
Page 468 4064 0B31 Processor subsystem tests detected fault in I/O 1. Check for system firmware updates. book 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 670 Service Guide...
Page 469 Error Code Description Action/ Possible Failing FRU 4064 0B32 Processor subsystem tests detected fault in I/O 1. Check for system firmware updates. book 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
Page 470 Location: U1.18-P1-H4 4064 0BF7 Processor subsystem tests detected fault in I/O 1. Check the cabling on the following RIO hub chip 7 (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 670 Service Guide...
Page 471 Error Code Description Action/ Possible Failing FRU 4064 0BF8 Processor subsystem tests detected fault in I/O 1. Check the cabling on the following RIO hub chip 8 (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 4064 0BF9 Processor subsystem tests detected fault in I/O 1.
Page 472 L3 cache module 14 and L3 VPD card cache module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 4064 0D0F Processor subsystem tests detected fault in L3 L3 cache module 15 and L3 VPD card cache module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 670 Service Guide...
Page 473 Error Code Description Action/ Possible Failing FRU 4064 0EA0 Processor subsystem tests detected fault in 1. Access the service processor error log. Find MOPS service processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
Page 474 4065 0005 Display alter tests detected fault in MCM MCM module 1 and VPD card module 1 Location: U1.18-P1-C3 and U1.18-P1-H2.5 4065 0006 Display alter tests detected fault in MCM MCM module 3 and VPD card module 3 Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 670 Service Guide...
Page 475 Error Code Description Action/ Possible Failing FRU 4065 0007 Display alter tests detected fault in L3 VPD 1. L3 VPD card card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective.″)
Page 476 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 477 Error Code Description Action/ Possible Failing FRU 4065 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 478 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 479 Error Code Description Action/ Possible Failing FRU 4065 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 480 4065 0B14 Display alter tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4. Call service support. Eserver pSeries 670 Service Guide...
Page 481 Error Code Description Action/ Possible Failing FRU 4065 0B15 Display alter tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4.
Page 482 4065 0B31 Display alter tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 670 Service Guide...
Page 483 Error Code Description Action/ Possible Failing FRU 4065 0B32 Display alter tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
Page 484 Location: U1.18-P1-H4 4065 0BF7 Display alter tests detected fault in I/O hub chip 1. Check the cabling on the following RIO 7 (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 670 Service Guide...
Page 485 Error Code Description Action/ Possible Failing FRU 4065 0BF8 Display alter tests detected fault in I/O hub chip 1. Check the cabling on the following RIO 8 (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 4065 0BF9 Display alter tests detected fault in I/O hub chip 1.
Page 486 L3 cache module 14 and L3 VPD card module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 4065 0D0F Display alter tests detected fault in L3 cache L3 cache module 15 and L3 VPD card module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 670 Service Guide...
Page 487 Error Code Description Action/ Possible Failing FRU 4065 0EA0 Display alter tests detected fault in MOPS 1. Access the service processor error log. Find service processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
Page 488 MCM module 1 and VPD card fault in MCM module 1 Location: U1.18-P1-C3 and U1.18-P1-H2.5 4066 0006 Scan interface basic assurance tests detected MCM module 3 and VPD card fault in MCM module 3 Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 670 Service Guide...
Page 489 Error Code Description Action/ Possible Failing FRU 4066 0007 Scan interface basic assurance tests detected 1. L3 VPD card fault in L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
Page 490 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 491 Error Code Description Action/ Possible Failing FRU 4066 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 492 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 493 Error Code Description Action/ Possible Failing FRU 4066 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 494 4066 0B14 Scan interface basic assurance tests detected 1. Check for system firmware updates. fault in I/O book 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4. Call service support. Eserver pSeries 670 Service Guide...
Page 495 Error Code Description Action/ Possible Failing FRU 4066 0B15 Scan interface basic assurance tests detected 1. Check for system firmware updates. fault in I/O book 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4.
Page 496 4066 0B31 Scan interface basic assurance tests detected 1. Check for system firmware updates. fault in I/O book 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 670 Service Guide...
Page 497 Error Code Description Action/ Possible Failing FRU 4066 0B32 Scan interface basic assurance tests detected 1. Check for system firmware updates. fault in I/O book 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
Page 498 4066 0BF7 Scan interface basic assurance tests detected 1. Check the cabling on the following RIO fault in I/O hub chip 7 (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 670 Service Guide...
Page 499 Error Code Description Action/ Possible Failing FRU 4066 0BF8 Scan interface basic assurance tests detected 1. Check the cabling on the following RIO fault in I/O hub chip 8 (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 4066 0BF9 Scan interface basic assurance tests detected 1.
Page 500 L3 cache module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 4066 0D0F Scan interface basic assurance tests detected L3 cache module 15 and L3 VPD card fault in L3 cache module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 670 Service Guide...
Page 501 Error Code Description Action/ Possible Failing FRU 4066 0EA0 Scan interface basic assurance tests detected 1. Access the service processor error log. Find fault in MOPS service processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
Page 502 4067 0004 Bus tests detected fault in MCM module 2 MCM module 2 and VPD card Location: U1.18-P1-C4 and U1.18-P1-H2.4 4067 0005 Bus tests detected fault in MCM module 1 MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 Eserver pSeries 670 Service Guide...
Page 503 Error Code Description Action/ Possible Failing FRU 4067 0006 Bus tests detected fault in MCM module 3 MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 4067 0007 Bus tests detected fault in L3 VPD card 1. L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card.
Page 504 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 505 Error Code Description Action/ Possible Failing FRU 4067 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 506 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 507 Error Code Description Action/ Possible Failing FRU 4067 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 508 4067 0B14 Bus tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4. Call service support. Eserver pSeries 670 Service Guide...
Page 509 Error Code Description Action/ Possible Failing FRU 4067 0B15 Bus tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4.
Page 510 4067 0B31 Bus tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 670 Service Guide...
Page 511 Error Code Description Action/ Possible Failing FRU 4067 0B32 Bus tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
Page 512 2. Replace the RIO book, Location: U1.18-P1-H4 4067 0BF7 Bus tests detected fault in I/O hub chip 7 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 670 Service Guide...
Page 513 Error Code Description Action/ Possible Failing FRU 4067 0BF8 Bus tests detected fault in I/O hub chip 8 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 4067 0BF9 Bus tests detected fault in I/O hub chip 9 (port 1.
Page 514 L3 cache module 14 and L3 VPD card Location: U1.18-P1-C9 and U1.18-P1-H2.1 4067 0D0F Bus tests detected fault in L3 cache module 15 L3 cache module 15 and L3 VPD card Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 670 Service Guide...
Page 515 Error Code Description Action/ Possible Failing FRU 4067 0EA0 Bus tests detected fault in MOPS service 1. Access the service processor error log. Find processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
Page 516 4068 0005 Other bus tests detected fault in MCM module MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 4068 0006 Other bus tests detected fault in MCM module MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 670 Service Guide...
Page 517 Error Code Description Action/ Possible Failing FRU 4068 0007 Other bus tests detected fault in L3 VPD card 1. L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
Page 518 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 519 Error Code Description Action/ Possible Failing FRU 4068 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 520 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 521 Error Code Description Action/ Possible Failing FRU 4068 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for Processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 522 4068 0B14 Other bus tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4. Call service support. Eserver pSeries 670 Service Guide...
Page 523 Error Code Description Action/ Possible Failing FRU 4068 0B15 Other bus tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4.
Page 524 4068 0B31 Other bus tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 670 Service Guide...
Page 525 Error Code Description Action/ Possible Failing FRU 4068 0B32 Other bus tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
Page 526 Location: U1.18-P1-H4 4068 0BF7 Other bus tests detected fault in I/O hub chip 7 1. Check the cabling on the following RIO (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 670 Service Guide...
Page 527 Error Code Description Action/ Possible Failing FRU 4068 0BF8 Other bus tests detected fault in I/O hub chip 8 1. Check the cabling on the following RIO (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 4068 0BF9 Other bus tests detected fault in I/O hub chip 9 1.
Page 528 L3 cache module 14 and L3 VPD card module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 4068 0D0F Other bus tests detected fault in L3 cache L3 cache module 15 and L3 VPD card module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 670 Service Guide...
Page 529 Error Code Description Action/ Possible Failing FRU 4068 0EA0 Other bus tests detected fault in MOPS service 1. Access the service processor error log. Find processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
Page 530 4069 0005 Memory tests detected fault in MCM module 1 MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 4069 0006 Memory tests detected fault in MCM module 3 MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 670 Service Guide...
Page 531 Error Code Description Action/ Possible Failing FRU 4069 0007 Memory tests detected fault in L3 VPD card 1. L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
Page 532 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 533 Error Code Description Action/ Possible Failing FRU 4069 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 534 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 535 Error Code Description Action/ Possible Failing FRU 4069 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 536 4069 0B14 Memory tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4. Call service support. Eserver pSeries 670 Service Guide...
Page 537 Error Code Description Action/ Possible Failing FRU 4069 0B15 Memory tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4.
Page 538 4069 0B31 Memory tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 670 Service Guide...
Page 539 Error Code Description Action/ Possible Failing FRU 4069 0B32 Memory tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
Page 540 Location: U1.18-P1-H4 4069 0BF7 Memory tests detected fault in I/O hub chip 7 1. Check the cabling on the following RIO (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 670 Service Guide...
Page 541 Error Code Description Action/ Possible Failing FRU 4069 0BF8 Memory tests detected fault in I/O hub chip 8 1. Check the cabling on the following RIO (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 4069 0BF9 Memory tests detected fault in I/O hub chip 9 1.
Page 542 L3 cache module 14 and L3 VPD card module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 4069 0D0F Memory tests detected fault in L3 cache L3 cache module 15 and L3 VPD card module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 670 Service Guide...
Page 543 Error Code Description Action/ Possible Failing FRU 4069 0EA0 Memory tests detected fault in MOPS service 1. Access the service processor error log. Find processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
Page 544 406A 0005 Self tests detected fault in MCM module 1 MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 406A 0006 Self tests detected fault in MCM module 3 MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 670 Service Guide...
Page 545 Error Code Description Action/ Possible Failing FRU 406A 0007 Self tests detected fault in L3 VPD card 1. L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
Page 546 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 547 Error Code Description Action/ Possible Failing FRU 406A 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 548 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 549 Error Code Description Action/ Possible Failing FRU 406A 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 550 406A 0B14 Self-tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4. Call service support. Eserver pSeries 670 Service Guide...
Page 551 Error Code Description Action/ Possible Failing FRU 406A 0B15 Self-tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4.
Page 552 406A 0B31 Self-tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 670 Service Guide...
Page 553 Error Code Description Action/ Possible Failing FRU 406A 0B32 Self-tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
Page 554 2. Replace the RIO book, Location: U1.18-P1-H4 406A 0BF7 Self-tests detected fault in I/O hub chip 7 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 670 Service Guide...
Page 555 Error Code Description Action/ Possible Failing FRU 406A 0BF8 Self-tests detected fault in I/O hub chip 8 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 406A 0BF9 Self-tests detected fault in I/O hub chip 9 (port 1.
Page 556 406A 0D0E Self-tests detected fault in L3 cache module 14 L3 cache module 14 and L3 VPD card Location: U1.18-P1-C9 and U1.18-P1-H2.1 406A 0D0F Self-tests detected fault in L3 cache module 15 L3 cache module 15 and L3 VPD card Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 670 Service Guide...
Page 557 Error Code Description Action/ Possible Failing FRU 406A 0EA0 Self-tests detected fault in MOPS service 1. Access the service processor error log. Find processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
Page 558 406B 0005 Wire tests detected fault in MCM module 1 MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 406B 0006 Wire tests detected fault in MCM module 3 MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 670 Service Guide...
Page 559 Error Code Description Action/ Possible Failing FRU 406B 0007 Wire tests detected fault in L3 VPD card 1. L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
Page 560 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 561 Error Code Description Action/ Possible Failing FRU 406B 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 562 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 563 Error Code Description Action/ Possible Failing FRU 406B 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 564 406B 0B14 Wire tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4. Call service support. Eserver pSeries 670 Service Guide...
Page 565 Error Code Description Action/ Possible Failing FRU 406B 0B15 Wire tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4.
Page 566 406B 0B31 Wire tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 670 Service Guide...
Page 567 Error Code Description Action/ Possible Failing FRU 406B 0B32 Wire tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
Page 568 2. Replace the RIO book, Location: U1.18-P1-H4 406B 0BF7 Wire tests detected fault in I/O hub chip 7 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 670 Service Guide...
Page 569 Error Code Description Action/ Possible Failing FRU 406B 0BF8 Wire tests detected fault in I/O hub chip 8 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 406B 0BF9 Wire tests detected fault in I/O hub chip 9 (port 1.
Page 570 406B 0D0E Wire tests detected fault in L3 cache module 14 L3 cache module 14 and L3 VPD card Location: U1.18-P1-C9 and U1.18-P1-H2.1 406B 0D0F Wire tests detected fault in L3 cache module 15 L3 cache module 15 and L3 VPD card Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 670 Service Guide...
Page 571 Error Code Description Action/ Possible Failing FRU 406B 0EA0 Wire tests detected fault in MOPS service 1. Access the service processor error log. Find processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
Page 572 406C 0005 IPL detected fault in MCM module 1 MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 406C 0006 IPL detected fault in MCM module 3 MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 670 Service Guide...
Page 573 Error Code Description Action/ Possible Failing FRU 406C 0007 IPL detected fault in L3 VPD card 1. L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.) 2.
Page 574 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 575 Error Code Description Action/ Possible Failing FRU 406C 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 576 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 577 Error Code Description Action/ Possible Failing FRU 406C 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 578 406C 0B14 IPL detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4. Call service support. Eserver pSeries 670 Service Guide...
Page 579 Error Code Description Action/ Possible Failing FRU 406C 0B15 IPL detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4.
Page 580 I/O book (slot 3 RIO port 0) Location: U1.18-P1-H4/Q1 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 670 Service Guide...
Page 581 Error Code Description Action/ Possible Failing FRU 406C 0B31 IPL detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
Page 582 2. Replace the RIO book, Location: U1.18-P1-H3 406C 0BF6 IPL detected fault in I/O hub chip 6 (port x) 1. Check the cabling on the following RIO ports: a. U1.18-P1-H4/Q5 b. U1.18-P1-H4/Q6 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 670 Service Guide...
Page 583 Error Code Description Action/ Possible Failing FRU 406C 0BF7 IPL detected fault in I/O hub chip 7 (port x) 1. Check the cabling on the following RIO ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 406C 0BF8 IPL detected fault in I/O hub chip 8 (port x) 1.
Page 584 406C 0D0D IPL detected fault in L3 cache module 13 L3 cache module 13 and L3 VPD card Location: U1.18-P1-C5 and U1.18-P1-H2.1 406C 0D0E IPL detected fault in L3 cache module 14 L3 cache module 14 and L3 VPD card Location: U1.18-P1-C9 and U1.18-P1-H2.1 Eserver pSeries 670 Service Guide...
Page 585 Error Code Description Action/ Possible Failing FRU 406C 0D0F IPL detected fault in L3 cache module 15 L3 cache module 15 and L3 VPD card Location: U1.18-P1-C13 and U1.18-P1-H2.1 406C 0EA0 IPL detected fault in MOPS service processor 1. Access the service processor error log. Find code the error log entry for the 406x 0EA0 error.
Page 586 406D 0005 Attention handler detected fault in MCM module MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 406D 0006 Attention handler detected fault in MCM module MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 670 Service Guide...
Page 587 Error Code Description Action/ Possible Failing FRU 406D 0007 Attention handler detected fault in L3 VPD card 1. L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
Page 588 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 589 Error Code Description Action/ Possible Failing FRU 406D 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 590 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 591 Error Code Description Action/ Possible Failing FRU 406D 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 592 406D 0B14 Attention handler detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4. Call service support. Eserver pSeries 670 Service Guide...
Page 593 Error Code Description Action/ Possible Failing FRU 406D 0B15 Attention handler detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4.
Page 594 406D 0B31 Attention handler detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 670 Service Guide...
Page 595 Error Code Description Action/ Possible Failing FRU 406D 0B32 Attention handler detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
Page 596 Location: U1.18-P1-H4 406D 0BF7 Attention handler detected fault in I/O hub chip 1. Check the cabling on the following RIO 7 (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 670 Service Guide...
Page 597 Error Code Description Action/ Possible Failing FRU 406D 0BF8 Attention handler detected fault in I/O hub chip 1. Check the cabling on the following RIO 8 (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 406D 0BF9 Attention handler detected fault in I/O hub chip 1.
Page 598 L3 cache module 14 and L3 VPD card module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 406D 0D0F Attention handler detected fault in L3 cache L3 cache module 15 and L3 VPD card module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 670 Service Guide...
Page 599 Error Code Description Action/ Possible Failing FRU 406D 0EA0 Attention handler detected fault in MOPS 1. Access the service processor error log. Find service processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
Page 600 406E 0005 Scan control routines detected fault in MCM MCM module 1 and VPD card module 1 Location: U1.18-P1-C3 and U1.18-P1-H2.5 406E 0006 Scan control routines detected fault in MCM MCM module 3 and VPD card module 3 Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 670 Service Guide...
Page 601 Error Code Description Action/ Possible Failing FRU 406E 0007 Scan control routines detected fault in L3 VPD 1. L3 VPD card card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
Page 602 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 603 Error Code Description Action/ Possible Failing FRU 406E 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 604 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 605 Error Code Description Action/ Possible Failing FRU 406E 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 606 406E 0B14 Scan control routines detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4. Call service support. Eserver pSeries 670 Service Guide...
Page 607 Error Code Description Action/ Possible Failing FRU 406E 0B15 Scan control routines detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4.
Page 608 406E 0B31 Scan control routines detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 670 Service Guide...
Page 609 Error Code Description Action/ Possible Failing FRU 406E 0B32 Scan control routines detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
Page 610 Location: U1.18-P1-H4 406E 0BF7 Scan control routines detected fault in I/O hub 1. Check the cabling on the following RIO chip 7 (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 670 Service Guide...
Page 611 Error Code Description Action/ Possible Failing FRU 406E 0BF8 Scan control routines detected fault in I/O hub 1. Check the cabling on the following RIO chip 8 (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 406E 0BF9 Scan control routines detected fault in I/O hub 1.
Page 612 L3 cache module 14 and L3 VPD card module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 406E 0D0F Scan control routines detected fault in L3 cache L3 cache module 15 and L3 VPD card module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 670 Service Guide...
Page 613 Error Code Description Action/ Possible Failing FRU 406E 0EA0 Scan control routines detected fault in MOPS 1. Access the service processor error log. Find service processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
Page 614 406F 0005 Error code generation/logging detected fault in MCM module 1 and VPD card MCM module 1 Location: U1.18-P1-C3 and U1.18-P1-H2.5 406F 0006 Error code generation/logging detected fault in MCM module 3 and VPD card MCM module 3 Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 670 Service Guide...
Page 615 Error Code Description Action/ Possible Failing FRU 406F 0007 Error code generation/logging detected fault in 1. L3 VPD card L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
Page 616 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 617 Error Code Description Action/ Possible Failing FRU 406F 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 618 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 670 Service Guide...
Page 619 Error Code Description Action/ Possible Failing FRU 406F 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
Page 620 406F 0B14 Error code generation/logging detected fault in 1. Check for system firmware updates. I/O book 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4. Call service support. Eserver pSeries 670 Service Guide...
Page 621 Error Code Description Action/ Possible Failing FRU 406F 0B15 Error code generation/logging detected fault in 1. Check for system firmware updates. I/O book 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H1 4.
Page 622 406F 0B31 Error code generation/logging detected fault in 1. Check for system firmware updates. I/O book 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 670 Service Guide...
Page 623 Error Code Description Action/ Possible Failing FRU 406F 0B32 Error code generation/logging detected fault in 1. Check for system firmware updates. I/O book 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
Page 624 Location: U1.18-P1-H4 406F 0BF7 Error code generation/logging detected fault in 1. Check the cabling on the following RIO I/O hub chip 7 (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 670 Service Guide...
Page 625 Error Code Description Action/ Possible Failing FRU 406F 0BF8 Error code generation/logging detected fault in 1. Check the cabling on the following RIO I/O hub chip 8 (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 406F 0BF9 Error code generation/logging detected fault in 1.
Page 626 L3 cache module 14 and L3 VPD card L3 cache module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 406F 0D0F Error code generation/logging detected fault in L3 cache module 15 and L3 VPD card L3 cache module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 670 Service Guide...
Page 627 Error Code Description Action/ Possible Failing FRU 406F 0EA0 Error code generation/logging detected fault in 1. Access the service processor error log. Find MOPS service processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
Page 628 406F 25E6 SMA 4-port switch adapter fault Replace the I/O book (switch adapter) specified by the location code. 406F 273F SMA 2-port switch adapter fault Replace the I/O book (switch adapter) specified by the location code. Eserver pSeries 670 Service Guide...
Page 629 Error Code Description Action/ Possible Failing FRU 4503 302A This error code indicates that the memory Do the following: repeat gard function has deconfigured or 1. Go to the memory partially deconfigured a memory book. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 630 If any of the books have a status of ″deconfigured by the system″, either before or after the boot to the SMS menus, go to step 2. 2. Replace the memory book specified by the location code. Eserver pSeries 670 Service Guide...
Page 631 Error Code Description Action/ Possible Failing FRU 4503 305A This error code indicates that the memory Do the following: repeat gard function has deconfigured or 1. Go to the memory partially deconfigured a memory book. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 632 If any of the books have a status of ″deconfigured by the system″, either before or after the boot to the SMS menus, go to step 2. 2. Replace the memory book specified by the location code. Eserver pSeries 670 Service Guide...
Page 633 Error Code Description Action/ Possible Failing FRU 4503 305E This error code indicates that the memory Do the following: repeat gard function has deconfigured or 1. Go to the memory partially deconfigured a memory book. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 634 If any of the books have a status of ″deconfigured by the system″, either before or after the boot to the SMS menus, go to step 2. 2. Replace the memory book specified by the location code. Eserver pSeries 670 Service Guide...
Page 635 Error Code Description Action/ Possible Failing FRU 4503 307C This error code indicates that the memory Do the following: repeat gard function has deconfigured or 1. Go to the memory partially deconfigured a memory book. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 636 If any of the books have a status of ″deconfigured by the system″, either before or after the boot to the SMS menus, go to step 2. 2. Replace the memory book specified by the location code. Eserver pSeries 670 Service Guide...
Page 637 Error Code Description Action/ Possible Failing FRU 4503 308B This error code indicates that the memory Do the following: repeat gard function has deconfigured or 1. Go to the memory partially deconfigured a memory book. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 638 If any of the books have a status of ″deconfigured by the system″, either before or after the boot to the SMS menus, go to step 2. 2. Replace the memory book specified by the location code. Eserver pSeries 670 Service Guide...
Page 639 Error Code Description Action/ Possible Failing FRU 4503 30BD This error code indicates that the memory Do the following: repeat gard function has deconfigured or 1. Go to the memory partially deconfigured a memory book. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 640 If any of the books have a status of ″deconfigured by the system″, either before or after the boot to the SMS menus, go to step 2. 2. Replace the memory book specified by the location code. Eserver pSeries 670 Service Guide...
Page 641 Error Code Description Action/ Possible Failing FRU 4503 30C6 This error code indicates that the memory Do the following: repeat gard function has deconfigured or 1. Go to the memory partially deconfigured a memory book. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
Page 642 Problem Isolation” on page 290. 1.1 GHz MCM and 1.3 GHz MCM 4504 25E7 Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs Problem Isolation” on page 290. Eserver pSeries 670 Service Guide...
Page 643 Error Code Description Action/ Possible Failing FRU 4504 25E8 Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs Problem Isolation” on page 290. 4504 25F1 Memory subsystem and processor subsystem Go to “MAP 1548: Memory and Processor tests detected fault in L3 VPD card used with Problem Isolation”...
Page 644 4505 25C0 Memory subsystem and display alter tests System backplane detected fault in system backplane Location: U1.18-P1 4505 25C1 Memory subsystem and display alter tests Clock card detected fault in 1.0 GHz clock card Location: U1.18-P1-X5 Eserver pSeries 670 Service Guide...
Page 645 Error Code Description Action/ Possible Failing FRU 4505 25D9 Memory subsystem and display alter tests Go to “MAP 1548: Memory and Processor detected fault in L3 VPD card used with 1.1 Problem Isolation” on page 290. GHz MCM and 1.3 GHz MCM 4505 25E7 Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs...
Page 646 Problem Isolation” on page 290. 4506 25F1 Memory subsystem and scan interface basic Go to “MAP 1548: Memory and Processor assurance tests detected fault in L3 VPD card Problem Isolation” on page 290. used with 1.3 GHz MCM Eserver pSeries 670 Service Guide...
Page 647 Error Code Description Action/ Possible Failing FRU 4506 25F9 Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs Problem Isolation” on page 290. 4506 269A Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs Problem Isolation”...
Page 648 I/O subsystem PCI backplane at location in I/O subsystem PCI backplane specified in error code 4507 28B1 Memory subsystem and bus tests detected fault I/O subsystem DASD backplane at location in I/O subsystem DASD backplane specified in error code Eserver pSeries 670 Service Guide...
Page 649 Error Code Description Action/ Possible Failing FRU 4507 302A Memory subsystem and bus tests detected fault Go to “MAP 1540: Problem Isolation in 8 GB memory book (inner) Procedures” on page 253 to isolate the failing component. 4507 302B Memory subsystem and bus tests detected fault Go to “MAP 1540: Problem Isolation in 8 GB memory book (outer) Procedures”...
Page 650 Procedures” on page 253 to isolate the failing component. 4508 302D Memory subsystem and other bus tests Go to “MAP 1540: Problem Isolation detected fault in 32 GB memory book (outer) Procedures” on page 253 to isolate the failing component. Eserver pSeries 670 Service Guide...
Page 651 Error Code Description Action/ Possible Failing FRU 4508 305A Memory subsystem and processor subsystem Go to “MAP 1544: Inner L3 Module Problem tests detected fault in 8 GB memory book Isolation” on page 282. (inner) 4508 305B Memory subsystem and processor subsystem Go to “MAP 1545: Outer L3 Module Problem tests detected fault in 8 GB memory book Isolation”...
Page 652 16 GB inner memory book Isolation” on page 282. 4509 305F Memory subsystem and memory tests detected Go to “MAP 1545: Outer L3 Module Problem fault in 16 GB outer memory book Isolation” on page 284. Eserver pSeries 670 Service Guide...
Page 653 Error Code Description Action/ Possible Failing FRU 4509 307A Memory subsystem and processor subsystem Go to “MAP 1544: Inner L3 Module Problem tests detected fault in 4 GB inner memory book Isolation” on page 282. 4509 307B Memory subsystem and processor subsystem Go to “MAP 1544: Inner L3 Module Problem tests detected fault in 8 GB inner memory book Isolation”...
Page 654 16 GB inner memory Isolation” on page 282. book 450A 307E Memory subsystem and processor subsystem Go to “MAP 1544: Inner L3 Module Problem tests detected fault in 16 GB inner memory Isolation” on page 282. book Eserver pSeries 670 Service Guide...
Page 655 Error Code Description Action/ Possible Failing FRU 450A 308A Memory subsystem and processor subsystem Go to “MAP 1545: Outer L3 Module Problem tests detected fault in 4 GB outer memory book Isolation” on page 284. 450A 308B Memory subsystem and processor subsystem Go to “MAP 1545: Outer L3 Module Problem tests detected fault in 4 GB outer memory book Isolation”...
Page 656 Isolation” on page 284. 450B 30BD Memory subsystem and processor subsystem Go to “MAP 1544: Inner L3 Module Problem tests detected fault in 8 GB or 16 GB CUoD Isolation” on page 282. inner memory book Eserver pSeries 670 Service Guide...
Page 657 Error Code Description Action/ Possible Failing FRU 450B 30C3 Memory subsystem and processor subsystem Go to “MAP 1544: Inner L3 Module Problem tests detected fault in 32 GB or 64 GB CUoD Isolation” on page 282. inner memory book 450B 30C6 Memory subsystem and processor subsystem Go to “MAP 1545: Outer L3 Module Problem tests detected fault in 8 GB or 16 GB CUoD Isolation”...
Page 658 Go to “MAP 1545: Outer L3 Module Problem tests detected fault in 32 GB or 64 GB CUoD Isolation” on page 284. outer memory book 450D 248B Memory subsystem and attention handler Operator panel detected fault in operator panel Location: U1.17-L1 Eserver pSeries 670 Service Guide...
Page 659 Error Code Description Action/ Possible Failing FRU 450D 25C0 Memory subsystem and attention handler System backplane detected fault in system backplane Location: U1.18-P1 450D 25C1 Memory subsystem and attention handler Clock card detected fault in 1.0 GHz clock card Location: U1.18-P1-X5 450D 25D9 Memory subsystem and attention handler Go to “MAP 1548: Memory and Processor detected fault in L3 VPD card used with 1.1...
Page 660 1.7 GHz MCMs Problem Isolation” on page 290. 450E 25E8 Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs Problem Isolation” on page 290. Eserver pSeries 670 Service Guide...
Page 661 Error Code Description Action/ Possible Failing FRU 450E 25F1 Memory subsystem and scan control routines Go to “MAP 1548: Memory and Processor detected fault in L3 VPD card used with 1.3 Problem Isolation” on page 290. GHz MCM 450E 25F9 Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs Problem Isolation”...
Page 662 1.7 GHz MCMs Problem Isolation” on page 290. 450F 269A Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs Problem Isolation” on page 290. Eserver pSeries 670 Service Guide...
Page 663 Error Code Description Action/ Possible Failing FRU 450F 28B0 Memory subsystem and error code I/O subsystem PCI backplane at location generation/logging detected fault in I/O specified in error code subsystem PCI backplane 450F 28B1 Memory subsystem and error code I/O subsystem DASD backplane at location generation/logging detected fault in I/O specified in error code subsystem DASD backplane...
Page 664 I/O book 1, 3, or 4 problem exists. Ensure that the number of MCMs is consistent with the number of I/O books. 2. Replace I/O book 1, 3, or 4 at location specified in error code. Eserver pSeries 670 Service Guide...
Page 665 Error Code Description Action/ Possible Failing FRU 4604 2806 I/O subsystem and processor subsystem tests 1. If word 13 is CFF1 xxxx, a configuration detected fault in I/O book 1, 3, or 4 problem exists. Ensure that the number of MCMs is consistent with the number of I/O books.
Page 666 1. Verify that the system firmware is RH021114 or later. CUoD is not supported by the earlier firmware levels. 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys. Eserver pSeries 670 Service Guide...
Page 667 Error Code Description Action/ Possible Failing FRU 4605 527C CUoD capacity card fault 1. Verify that the system firmware is RH021114 or later. CUoD is not supported by the earlier firmware levels. 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys.
Page 668 I/O book 1, 3, or 4 problem exists. Ensure that the number of MCMs is consistent with the number of I/O books. 2. Replace I/O book 1, 3, or 4 at location specified in error code. Eserver pSeries 670 Service Guide...
Page 669 Error Code Description Action/ Possible Failing FRU 4607 2806 I/O subsystem and processor subsystem tests 1. If word 13 is CFF1 xxxx, a configuration detected fault in I/O book 1, 3, or 4 problem exists. Ensure that the number of MCMs is consistent with the number of I/O books.
Page 670 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys. 4609 248B I/O subsystem and memory tests detected fault Operator panel in operator panel Location: U1.17-L1 Eserver pSeries 670 Service Guide...
Page 671 Error Code Description Action/ Possible Failing FRU 4609 25C0 I/O subsystem and memory tests detected fault System backplane in system backplane Location: U1.18-P1 4609 25C1 I/O subsystem and memory tests detected fault Clock card in 1.0 GHz clock card Location: U1.18-P1-X5 4609 2738 I/O subsystem and memory tests detected fault 1.
Page 672 I/O subsystem PCI backplane at location I/O subsystem PCI backplane specified in error code 460A 28B1 I/O subsystem and self-tests detected fault in I/O subsystem DASD backplane at location I/O subsystem DASD backplane specified in error code Eserver pSeries 670 Service Guide...
Page 673 Error Code Description Action/ Possible Failing FRU 460A 525E CUoD capacity card fault 1. Verify that the system firmware is RH021114 or later. CUoD is not supported by the earlier firmware levels. 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys.
Page 674 1, 3, or 4 problem exists. Ensure that the number of MCMs is consistent with the number of I/O books. 2. Replace I/O book 1, 3, or 4 at location specified in error code. Eserver pSeries 670 Service Guide...
Page 675 Error Code Description Action/ Possible Failing FRU 460C 273C I/O subsystem and IPL detected fault in primary Primary I/O book - Slot 0 I/O book - Slot 0 Location: U1.18-P1-H2 460C 273D I/O subsystem and processor subsystem tests Primary I/O book - Slot 0 detected fault in primary I/O book - Slot 0 Location: U1.18-P1-H2 460C 2776 I/O subsystem and processor subsystem tests...
Page 676 1. Verify that the system firmware is RH021114 or later. CUoD is not supported by the earlier firmware levels. 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys. Eserver pSeries 670 Service Guide...
Page 677 Error Code Description Action/ Possible Failing FRU 460D 527A CUoD capacity card fault 1. Verify that the system firmware is RH021114 or later. CUoD is not supported by the earlier firmware levels. 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys.
Page 678 I/O Location: U1.18-P1-H2 book - Slot 0 460F 273D I/O subsystem and processor subsystem tests Primary I/O book - Slot 0 detected fault in primary I/O book - Slot 0 Location: U1.18-P1-H2 Eserver pSeries 670 Service Guide...
Page 679 Error Code Description Action/ Possible Failing FRU 460F 2776 I/O subsystem and processor subsystem tests 1. If word 13 is CFF1 xxxx, a configuration detected fault in I/O book 1, 3, or 4 problem exists. Ensure that the number of MCMs is consistent with the number of I/O books.
Page 680 ″deconfigured by the system,″ either before or after the boot to the SMS menus, go to step 2 on page 609. 2. Replace the processor MCM (on which the deconfigured processor resides) specified by the location code. Eserver pSeries 670 Service Guide...
Page 681 Error Code Description Action/ Possible Failing FRU 4B23 25C8 The processor repeat gard function has Do the following: deconfigured a processor. 1. Go to the processor configuration/deconfiguration menu, which is under the system information menu in the service processor menus. Look at the status of the processors.
Page 682 ″deconfigured by the system,″ either before or after the boot to the SMS menus, go to step 2 on page 609. 2. Replace the processor MCM (on which the deconfigured processor resides) specified by the location code. Eserver pSeries 670 Service Guide...
Page 683 Error Code Description Action/ Possible Failing FRU 4B23 25D7 The processor repeat gard function has Do the following: deconfigured a processor. 1. Go to the processor configuration/deconfiguration menu, which is under the system information menu in the service processor menus. Look at the status of the processors.
Page 684 ″deconfigured by the system,″ either before or after the boot to the SMS menus, go to step 2 on page 609. 2. Replace the processor MCM (on which the deconfigured processor resides) specified by the location code. Eserver pSeries 670 Service Guide...
Page 685 Error Code Description Action/ Possible Failing FRU 4B23 526B The processor repeat gard function has Do the following: deconfigured a processor. 1. Go to the processor configuration/deconfiguration menu, which is under the system information menu in the service processor menus. Look at the status of the processors.
Page 686 Procedures” on page 253 to isolate the failing component. 4B24 25C0 Processor subsystem detected fault in system System backplane backplane Location: U1.18-P1 4B24 25C1 Processor subsystem detected fault in 1.0 GHz Clock card clock card Location: U1.18-P1-X5 Eserver pSeries 670 Service Guide...
Page 687 Error Code Description Action/ Possible Failing FRU 4B24 25C7 Processor subsystem detected fault in 4-way Go to “MAP 1540: Problem Isolation processor MCM Procedures” on page 253 to isolate the failing component. 4B24 25C8 Processor subsystem detected fault in 4-way Go to “MAP 1540: Problem Isolation processor MCM Procedures”...
Page 688 4B25 526D Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures” on page 253 to isolate the failing component. 4B26 248B Processor subsystem and scan interface basic Operator panel assurance tests detected fault in operator panel Location: U1.17-L1 Eserver pSeries 670 Service Guide...
Page 689 Error Code Description Action/ Possible Failing FRU 4B26 258A Processor subsystem detected fault in 4-way Go to “MAP 1540: Problem Isolation processor MCM Procedures” on page 253 to isolate the failing component. 4B26 25C0 Processor subsystem and scan interface basic System backplane assurance tests detected fault in system Location: U1.18-P1...
Page 690 I/O subsystem DASD backplane specified in error code 4B27 526B Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures” on page 253 to isolate the failing component. Eserver pSeries 670 Service Guide...
Page 691 Error Code Description Action/ Possible Failing FRU 4B27 526C Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures” on page 253 to isolate the failing component. 4B27 526D Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures”...
Page 692 MCM Procedures” on page 253 to isolate the failing component. 4B29 28B0 Processor subsystem and memory test I/O subsystem PCI backplane at location detected fault in I/O subsystem PCI backplane specified in error code Eserver pSeries 670 Service Guide...
Page 693 Error Code Description Action/ Possible Failing FRU 4B29 28B1 Processor subsystem and memory test I/O subsystem DASD backplane at location detected fault in I/O subsystem DASD specified in error code backplane 4B29 526B Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures”...
Page 694 Go to “MAP 1540: Problem Isolation Procedures” on page 253 to isolate the failing component. 4B2B 25D8 Fault in 4-way processor MCM detected Go to “MAP 1540: Problem Isolation Procedures” on page 253 to isolate the failing component. Eserver pSeries 670 Service Guide...
Page 695 Error Code Description Action/ Possible Failing FRU 4B2B 25E5 Processor subsystem detected fault in 4-way Go to “MAP 1540: Problem Isolation processor MCM Procedures” on page 253 to isolate the failing component. 4B2B 25E9 Processor subsystem detected fault in 8-way Go to “MAP 1540: Problem Isolation processor MCM Procedures”...
Page 696 4B2D 25D5 Processor subsystem and attention handler Go to “MAP 1540: Problem Isolation detected fault in 8-way processor MCM with Procedures” on page 253 to isolate the failing VPD card (8-, 16-, or 24-way) component. Eserver pSeries 670 Service Guide...
Page 697 Error Code Description Action/ Possible Failing FRU 4B2D 25D7 Fault in 4-way processor MCM detected Go to “MAP 1540: Problem Isolation Procedures” on page 253 to isolate the failing component. 4B2D 25D8 Fault in 4-way processor MCM detected Go to “MAP 1540: Problem Isolation Procedures”...
Page 698 Procedures” on page 253 to isolate the failing processor MCM component. 4B2F 25C8 Processor subsystem and error code Go to “MAP 1540: Problem Isolation generation/logging detected fault in 4-way Procedures” on page 253 to isolate the failing processor MCM component. Eserver pSeries 670 Service Guide...
Page 699 Error Code Description Action/ Possible Failing FRU 4B2F 25CF Processor subsystem detected fault in 8-way Go to “MAP 1540: Problem Isolation processor MCM Procedures” on page 253 to isolate the failing component. 4B2F 25D3 Processor subsystem and error code Go to “MAP 1540: Problem Isolation generation/logging detected fault in 8-way Procedures”...
Page 700: System Firmware Update Messages
A100 3000 Successful completion of scan dump Informational message; may or may not be seen during a scan log dump. A1FF 3000 Scan dump has been disabled Informational message; may or may not be seen during a scan log dump. Eserver pSeries 670 Service Guide...
Page 701: Common Firmware Error Codes
Common Firmware Error Codes Attention: Follow the procedure defined in “Checkpoints and Error Codes Index” on page 348. 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 702 B1xx 4600 Service processor failure 1. Check for system firmware updates. 2. Primary I/O book Location: U1.18-P1-H2 B1xx 4601 System processor failure Reboot the system in slow mode to isolate the failure. Eserver pSeries 670 Service Guide...
Page 703 Error Code Description Action/ Possible Failing FRU B1xx 4602 Hardware failure 1. Was this error code logged shortly after the system crashed? Go to 3. Go to 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 704 2. Check for system firmware updates. 3. Modem and modem cable. 4. Primary I/O book Location: U1.18-P1-H2 B1xx 4622 Service processor failure 1. Operator panel Location: U1.17-L1 2. Check for system firmware updates. 3. Primary I/O book Location: U1.18-P1-H2 Eserver pSeries 670 Service Guide...
Page 705 Error Code Description Action/ Possible Failing FRU B1xx 4633 System power control network (SPCN) failure 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 706 Procedures” on page 253. B1xx 4650 System processor failure (all processors reset). Reboot the system in slow mode to isolate the problem. B1xx 4651 CPU GARD VPD on MCM 0 U1.18-P1-C1 and U1.18-P1-H2.3 Eserver pSeries 670 Service Guide...
Page 707 Error Code Description Action/ Possible Failing FRU B1xx 4652 CPU GARD VPD on MCM 1 U1.18-P1-C3 and U1.18-P1-H2.5 B1xx 4653 CPU GARD VPD on MCM 2 U1.18-P1-C4 and U1.18-P1-H2.4 B1xx 4654 CPU GARD VPD on MCM 3 U1.18-P1-C2 and U1.18-P1-H2.6 B1xx 4660 Memory subsystem failure (cannot isolate) Reboot the system in slow mode to isolate the failure, then check the service processor error...
Page 708 B1xx 4692 Operator panel task interface failure 1. Check for system firmware updates. 2. Call service support B1xx 4693 Service processor firmware failure 1. Check for system firmware updates. 2. Call service support Eserver pSeries 670 Service Guide...
Page 709 Error Code Description Action/ Possible Failing FRU B1xx 4694 System processor firmware failure 1. Check for system firmware updates. 2. Primary I/O book Location: U1.18-P1-H2 B1xx 4695 System power control network (SPCN) to 1. Check for system firmware updates. service processor interface failure 2.
Page 710 1. Reset the system using the pin-hole reset button on the operator panel. Retry the operation that caused this error code. 2. Check for a later level of firmware than the one that you were trying to install. Apply if available. 3. Call service support. Eserver pSeries 670 Service Guide...
Page 711 690 (7040 model 681). Actions: 1. Verify that the system being upgraded is a pSeries 670 (7040 model 671). This error will occur if the system has already been upgraded. 2. The special model upgrade diskette might be damaged. Obtain another model upgrade diskette.
Page 712 B1xx 469C Firmware to I/O interface 1. Check for system firmware updates. 2. Primary I/O book Location: U1.18-P1-H2 B1xx 469D Service processor firmware 1. Check for system firmware updates. 2. Primary I/O book Location: U1.18-P1-H2 Eserver pSeries 670 Service Guide...
Page 713: Hmc Surveillance Error Codes
Error Code Description Action/ Possible Failing FRU B1xx 469E Service processor firmware failure 1. Check for system firmware updates. 2. Reboot the system in slow mode to isolate a problem in the processor subsystem. 3. Primary I/O book Location: U1.18-P1-H2 B1xx 469F Service processor failure 1.
Page 714 HMC and partitions. 2. If short host names are not being used, or the previous step does not correct the problem, contact service support. Eserver pSeries 670 Service Guide...
Page 715: Problem Determination-Generated Error Codes
Go to “MAP 1542: I/O Problem Isolation” on error code is generated by the customer page 261. performing “Problem Determination” as described in the Eserver pSeries 670 User’s Guide. M0BT 0001 The system hung during “Starting Software...”. Go to “MAP 1542: I/O Problem Isolation” on This error code is generated by the customer page 261.
Page 716: Hypervisor Dump Retrieval Procedure
1 is necessary: devices.chrp_lpar.base.ras 5.X.X.X COMMITTED CHRP LPAR RAS Support If no output is returned, the devices.chrp_lpar.base LPP must be installed from the AIX installation media by the customer or system administrator. Eserver pSeries 670 Service Guide...
Page 717 After the fileset is installed, the dump file is ready to be retrieved. 2. Enter fetchdbg -k at the command prompt. This produces the following output: Retrieving Dump File ....Dump read successful This action results 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.
Page 718 Eserver pSeries 670 Service Guide...
Page 719: Chapter 6. Using The Online And Standalone Diagnostics
Chapter 6. Using the Online and Standalone Diagnostics 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. If the AIX operating system is not installed, use the standalone diagnostic procedures. Online diagnostics, when they are installed, reside with AIX in the file system.
Page 720: Identifying The Terminal Type To The Diagnostics
The diagnostics cannot be loaded on a system (client) from a server if that system is not set up to boot from a server over a network. When the system is set up to boot from a server, the diagnostics are run in the same manner as they are from disk. Eserver pSeries 670 Service Guide...
Page 721 v On a full system partition, if the diagnostics are loaded from disk or a server, you must shut down the AIX operating system before turning off the system unit to prevent possible damage to disk data. Do this in either of the following ways: –...
Page 722: Concurrent Mode
The full-test level requires the device not be assigned to or used by any other operation. This level of testing on a disk drive might require the use of the varyoff command. The diagnostics display menus to allow you to vary off the needed resource. Eserver pSeries 670 Service Guide...
Page 723: 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 724: Standalone Diagnostic Operation
(get help if needed). Stop all programs. 2. Remove all tapes, diskettes, and CD-ROMs. 3. From the following list, select the type of partitioned system you are running the standalone diagnostics in, then follow the power or reboot instructions. Eserver pSeries 670 Service Guide...
Page 725 v If you are running standalone diagnostics in a full machine partition, power off the system unit. Wait until the Power-on LED stops flashing and remains off, then press the power button to turn on the system. v If you are running standalone diagnostics in an LPAR partition, reboot the partition that will be running the standalone diagnostics.
Page 726: Running Standalone Diagnostics From A Network Installation Management (Nim) Server
Registering a client on the NIM server v Enabling a client to run diagnostics from the NIM server 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 727: Booting Standalone Diagnostics From The Nim Server On A System With An Hmc Attached
Booting Standalone Diagnostics from the NIM Server on a System with an HMC Attached To run standalone diagnostics on a client from the NIM server, do the following: 1. Remove any removable media (tape or CD-ROM). 2. Stop all programs including the AIX operating system (get help if needed). If you are running standalone diagnostics in a full system partition, verify with the system administrator and system users that the system unit can shut down.
Page 728: Booting Standalone Diagnostics From The Nim Server On A System With No Hmc Attached
Booting Standalone Diagnostics from the NIM Server on a System with No HMC Attached Eserver pSeries 670 Service Guide...
Page 729: Chapter 7. Using The Service Processor
U1.18-P1-H2). 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, which is equivalent to the term partitioned system.
Page 730: Accessing The Service Processor Menus Remotely
The service processor exits menu mode after ten minutes of inactivity and displays a message indicating that it has done so. Pressing any key on the virtual terminal window causes the main menu to display. Eserver pSeries 670 Service Guide...
Page 731: General User Menu
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 732: Privileged User Menus
(for example, your system administrator, network administrator, or service representative) to more quickly identify the location, configuration, and history of your server. Set the system name, from the main menu, using option 6. Eserver pSeries 670 Service Guide...
Page 733 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 734: Service Processor Setup Menu
9. Scan Log Dump Policy: Currently Never 98. Return to Previous Menu 99. Exit from Menus 0> Note: Unless otherwise stated in menu responses, settings become effective when a menu is exited using option 98 or 99. Eserver pSeries 670 Service Guide...
Page 735: Passwords
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”, on page 763).
Page 736 Selecting Start Talk Mode activates the keyboards and displays for such communications while console mirroring is established. This is a full duplex link, so message interference is possible. Alternating messages between users works best. Eserver pSeries 670 Service Guide...
Page 737 v OS Surveillance Setup Menu Note: This option is disabled in partitioned systems. This menu can be used to set up operating system (OS) surveillance. OS Surveillance Setup Menu 1. Surveillance: Currently Enabled 2. Surveillance Time Interval: 2 minutes 3. Surveillance Delay: 2 minutes 98.
Page 738 When the scan log dump is complete, depending on how the reboot policy is set, the system will either: – Go to the standby state (and the service processor menus will be available), indicated by OK or STBY in the operator panel – Attempt to reboot. Eserver pSeries 670 Service Guide...
Page 739 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 740: System Power Control Menu
Services (SMS) menus. This option is intended to be used on servers that require automatic power-on after a power failure. For more information, see “System Power-On Methods” on page 742. v Ring Indicate Power-On Menu Eserver pSeries 670 Service Guide...
Page 741 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 742 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. Eserver pSeries 670 Service Guide...
Page 743 v Boot Mode Menu Note: This option is disabled in partitioned systems. The Boot Mode Menu allows you to select a boot mode. Boot Mode Menu 1. Boot to SMS Menu: Currently Disabled 2. Service Mode Boot from Saved List: Currently Disabled 3.
Page 744: System Information Menu
Read Service Processor Error Logs Displays error conditions detected by the service processor. Refer to “Service Processor Error Logs” on page 757 for an example of this error log. v Read System POST Errors Eserver pSeries 670 Service Guide...
Page 745 This option should only be used by service personnel to obtain additional debug information. v Read NVRAM Displays Non Volatile Random Access Memory (NVRAM) content. v Read Service Processor Configuration Displays current service processor configuration. v Processor Configuration/Deconfiguration Menu Enable/Disable CPU Repeat Gard: CPU repeat gard automatically deconfigures a CPU during a system boot if a processor has failed BIST (built-in self test), caused a machine check or check stop, or has reached a threshold of recoverable errors.
Page 746 Runtime Recoverable Error Repeat Gard is disabled by default. These configuration/deconfiguration menus allow the user to change the system memory configuration. If it is necessary to take one of the memory books partially or completely offline, this menu allows you Eserver pSeries 670 Service Guide...
Page 747 to deconfigure a book, and then reconfigure the book at a later time. This menu also allows you to see if the repeat gard function has partially or completely deconfigured a memory book. When this option is selected, a menu displays. The following is an example of this menu: MEMORY CONFIGURATION/DECONFIGURATION MENU 77.
Page 748 - For the I/O type, type 98. If either value is not valid, a failure message displays on the console. Press Enter to return to the Power Control Network Utilities Menu. – Collect & display SPCN trace data Eserver pSeries 670 Service Guide...
Page 749 This option is used by service personnel to dump the SPCN trace data from the processor subsystem (CEC drawer) 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, as shown in the example screen: Enter the SPCN drawer number:...
Page 750 The I/O drawer fault/identify LED is located on the front of each I/O subsystem. If option 1 is selected, a list of location codes of the I/O subsystems and the CEC drawer displays. The screen will be similar to the following: Eserver pSeries 670 Service Guide...
Page 751 1. U1.9-P1 2. U1.9-P2 3. U1.5-P1 4. U1.5-P2 5. U1.1-P1 6. U1.1-P2 7. U2.1-P1 8. U2.1-P2 9. U2.5-P1 10. U2.5-P2 Enter number corresponding to the location code, or press Return to continue, or ’x’ to return to the menu. 0>4 If one of the devices is selected using the index number, the present state of its LED will be displayed, and you are given the option to toggle it, as shown in the following screen.
Page 752 9. L3_7 U1.18-P1-C12 10. MCM_3 U1.18-P1-C2 11. MCM_2 U1.18-P1-C3 12. L3_15 U1.18-P1-C13 13. L3_10 U1.18-P1-C14 14. MCM_1 U1.18-P1-C4 15. L3_11 U1.18-P1-C15 16. L3_6 U1.18-P1-C16 17. L3_12 U1.18-P1-C17 18. L3_9 U1.18-P1-C18 19. L3_8 U1.18-P1-C19 20. L3_5 U1.18-P1-C20 Eserver pSeries 670 Service Guide...
Page 753 To change the plug count for a particular module, enter a menu index number. For example, to change the plug count of the L3 module that is physically in the upper-right corner (U1.18-P1-C8), type 5, then enter the new plug count. When all of the new plug counts have been entered, select 50, Commit the values and write to the VPD.
Page 754 500 Mbps. However, if the hardware capability is 500 Mbps and the user selects 1000 Mbps, the user’s selection will be ignored by the system. If this option is chosen, the menu similar to the following is displayed: Eserver pSeries 670 Service Guide...
Page 755: Language Selection Menu
Remote I/O (RIO) Link Speed Set Up Menu Hardware Capability (internal and external): 1000 Mbps 1. Maximum RIO speed setting (internal and external): Currently Uninitialized 98. Return to previous menu. 0>1 If option 1 is selected, the RIO interface speed can be set as follows: Enter new value for this option: (1 = 1000 MBPS, 2 = 500 Mbps) 0>...
Page 756: Call-In/Call-Out Setup Menu
Customer Account Setup Menu, see “Customer Account Setup Menu” on page 742. v Call-Out Test tests the configuration after the modem is installed and configured correctly. Note: If the system is running in partition mode, the call-out option is disabled. Eserver pSeries 670 Service Guide...
Page 757: Modem Configuration Menu
Modem Configuration Menu Note: This option applies only to a modem attached to serial port 1 (S1) or serial port 2 (S2) on the primary I/O book. The first two lines of the Modem Configuration Menu contain status of the current selections. Selections are made in the sections labeled Modem Ports and Modem Configuration File Name.
Page 758: Serial Port Selection Menu
Call-in and ring indicate power-on cannot be enabled at the same time. If ring-indicate power-on is already enabled and you try to enable call-in, a message prompts you for confirmation. Refer to the message displayed on the screen. Eserver pSeries 670 Service Guide...
Page 759: Serial Port Speed Setup Menu
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 760 Note: If the system is running in partition mode, call-out is disabled. However, if the system is booted in full system partition mode, at least one of the preceding three telephone numbers must be assigned in order for the call-out test to complete successfully. Eserver pSeries 670 Service Guide...
Page 761: Call-Out Policy Setup Menu
v Customer Voice Telephone Number is the telephone number of a phone near the server or answered by someone responsible for the server. This is the telephone number left on the pager for callback. For test purposes, use a test number, which you can change later. v Customer System Telephone Number is the telephone number to which your server’s modem is connected.
Page 762: Customer Account Setup Menu
The service processor can be enabled to recover from the loss of ac power (see Enable/Disable Unattended Power-On Mode in the SYSTEM POWER CONTROL MENU). When ac power is restored, the system returns to the power state at the time ac loss occurred. For example, if the system was Eserver pSeries 670 Service Guide...
Page 763 powered on when ac loss occurred, it reboots/restarts when power is restored. If the system was powered off when ac loss occurred, it remains off when power is restored. v Timed power-on - refer to the shutdown -t command on servers using AIX. Working in conjunction with AIX, the Service Processor in your server can operate a timer, much like the wake-up timer on your clock radio.
Page 764: Service Processor Reboot/Restart Recovery
Enable supplemental restart policy - The default setting is yes. When set to yes on a full system partition, the service processor restarts the server when the operating system loses control and either: The Use OS-Defined restart policy is set to No. Eserver pSeries 670 Service Guide...
Page 765: System Firmware Updates
The Use OS-Defined restart policy is set to Yes and the operating system has no automatic restart policy. If set to Yes on a partitioned system, the service processor restarts the system when the system loses control and it is detected by service processor surveillance. Refer to “Service Processor Reboot/Restart Recovery”...
Page 766: General Information On System Firmware Updates
Download the detailed instructions, as well as the latest flash images, from the following Web address: http://techsupport.services.ibm.com/server/mdownload2. 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 767: Determining The Level Of Firmware On The System
The firmware level can be denoted in either of the following forms: v RHyymmdd, where RH = the pSeries 670’s firmware designation, yy = year, mm = month, and dd = day of the release. v vHyymmdd, where v = version number, H= the pSeries 670’s firmware designation, yy = year, mm = month and dd = day of the release.
Page 768: System Firmware Update In Aix Using A Locally Available Image
It is strongly recommended that you create a set of firmware update diskettes from CORE as soon as possible after a system is installed. As noted below, the diskette images can be downloaded to any Eserver pSeries 670 Service Guide...
Page 769: Updating System Firmware From The Service Processor Menus
personal computer or Eserver pSeries machine with access to CORE. This method is the only way to acquire a set of firmware update diskettes; they cannot be created by using the service processor menus or by using AIX. Retain and store the latest firmware diskettes each time the firmware gets updated in the event that the firmware gets damaged and must be reloaded.
Page 770: Updating System Firmware From The Aix Command Line
Refer to the detailed instructions that are provided with the latest image on CORE. Note: Because the system always reboots itself during this type of firmware update process, the update process can take from twenty to sixty minutes. Eserver pSeries 670 Service Guide...
Page 771: Recovery Mode
Recovery Mode If the service processor detects that its programming has been damaged when it is powering on to standby mode, it will enter recovery mode. In recovery mode, it will ask for the firmware update diskettes by putting eight-digit codes on the operator panel. The eight-digit codes are as follows: Code Action...
Page 772: Configuring And Deconfiguring Processors Or Memory
Note: Operating system surveillance is disabled on partitioned systems. System Firmware Surveillance System firmware surveillance is automatically enabled during system power-on. It cannot be disabled by the user, and the surveillance interval and surveillance delay cannot be changed by the user. Eserver pSeries 670 Service Guide...
Page 773 If the service processor detects no heartbeats during system IPL (for a set period of time), it cycles the system power to attempt a reboot. The maximum number of retries is set from the service processor menus. If the fail condition persists, the service processor leaves the machine powered on, logs an error, and displays menus to the user.
Page 774: Operating System Surveillance
If surveillance is selected from the service processor menus that are only available at system boot, then surveillance is enabled by default as soon as the system boots. From service aids, the selection is optional. Eserver pSeries 670 Service Guide...
Page 775: Call-Out (Call-Home)
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 776: Console Mirroring
1. Local session is already in progress. 2. The service processor receives a call from the remote user. 3. The local user selects the option to enable console mirroring. The service processor immediately begins mirroring service processor menus. Eserver pSeries 670 Service Guide...
Page 777: Service Processor Error Logs
Service Processor Error Logs The service processor error logs, an example of which follows, 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’ to return to menu. Press "C"...
Page 778: Lcd Progress Indicator Log
This action causes the system to shut down and the system power is turned off. To reset the service processor when the managed system is powered off, perform either of the following: Eserver pSeries 670 Service Guide...
Page 779 v If the service processor is responding to input from the HMC (or ASCII terminal), select Service Processor Setup Menu from the main menu, then select Reset Service Processor. This can only be done by a privileged user. v Put the UEPO switch in the off position, then back to the on position. Note: Do not use the pinhole reset switch to reset the service processor.
Page 780: Pre-Standby Phase
The service processor does not wait for user input or power-on command, but moves through the phase and into the bring-up phase. Access the SMS menus or the service processor menus to reset the unattended start mode. Eserver pSeries 670 Service Guide...
Page 781: Standby Phase
Standby Phase The standby phase can be reached in either of two ways: v With the server off and power connected (the normal path), recognized by OK in the LCD display. 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 782: Run-Time Phase
On an HMC-managed system, the service processor monitors the communication link between the managed system and the HMC. If the service processor detects that this communication link has been broken, it will post an error to the operating system running on the managed system. Eserver pSeries 670 Service Guide...
Page 783: Chapter 8. Using System Management Services
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 784: Select Language
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: _ Eserver pSeries 670 Service Guide...
Page 785: Change Password Options
Change Password Options The Change Password Options menu enables you to select from password utilities. Note: This option is not available in partitioned systems. Password Utilities 1 Set Privileged-Access Password 2 Remove Privileged-Access Password -------------------------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services --------------------------------------------------------------------------------------------------...
Page 786: Setup Remote Ipl (Initial Program Load)
Type the number of the menu item and press Enter or Select a Navigation key: _ To change IP parameters, type the number of the parameters for which you want to change the value. Entering IP parameters on this screen will automatically update the parameters on the ping test screen. Eserver pSeries 670 Service Guide...
Page 787 Attention: If the client system and the server are on the same subnet, set the gateway IP address to [0.0.0.0]. Selecting Adapter Configuration allows the setting of the network speed, enabling or disabling spanning tree, and setting the protocol as shown in the following example menu: Adapter Configuration 10/100 Mbps Ethernet PCI Adapter II: U1.9-P1-I4/E1 1.
Page 788: Change Scsi Settings
SMS menus and does not affect the display used by the operating system. Follow the instructions that display on the screen. The firmware automatically returns to the SMS main menu. Eserver pSeries 670 Service Guide...
Page 789: Select Boot Options
Select Boot Options Use this menu to view and set various options regarding the installation devices and boot devices. 1. Select Install or Boot a Device 2. Select Boot Devices 3. Multiboot Startup -------------------------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services --------------------------------------------------------------------------------------------------...
Page 790 If either Normal Mode Boot or Service Mode Boot is selected, the next screen will ask, Are you sure?. If you answer yes, the device will be booted in the appropriate mode. If you answer no, the firmware will return to the Select Task menu. Eserver pSeries 670 Service Guide...
Page 791: Select Boot Devices
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 that is 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.
Page 792 When a device type is selected, the Select Task menu allows you to see detailed information about the device or set the device’s location in the boot list as shown below in the example menu. The following is an example of the menu for a hard disk. Eserver pSeries 670 Service Guide...
Page 793: Display Current Settings
Select Task SCSI 18200 MB Harddisk (loc=U0.1-P2/Z1-A8,0) 1. Information 2. Set Boot Sequence: Configure as 1st Boot Device -------------------------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _ Selecting Information displays a menu similar to the following for a hard disk.
Page 794: Restore Default Settings
Multiboot Startup toggles the multiboot startup flag, which controls whether the multiboot menu is invoked automatically on startup. Exiting System Management Services After you have finished using the system management services, type x (for exit) to boot your system or partition. Eserver pSeries 670 Service Guide...
Page 795: Chapter 9. Removal And Replacement Procedures
Chapter 9. Removal and Replacement Procedures Introduction ........778 Handling Static-Sensitive Devices .
Page 796 Removal ....... . . 925 Eserver pSeries 670 Service Guide...
Page 797 Replacement....... . 926 I/O Subsystem I/O Backplane Assembly..... . . 927 Removal .
Page 798: Introduction
If you need to lay the device down while it is out of the antistatic container, lay it on the antistatic container. Before picking it up again, touch the antistatic container and the metal frame of the system unit at the same time. v To prevent permanent damage, handle the devices carefully. Eserver pSeries 670 Service Guide...
Page 799: Powering Off And Powering On The System
Powering Off and Powering On the System This section provides procedures for powering off and powering on the system. If you are instructed to remove the power from the system, the power cords must be disconnected from the power source. Powering Off the System With an HMC Attached and AIX Installed The HMC user interface provides a power-off function to turn off the power to the system.
Page 800: Powering Off The System With An Hmc Attached And Linux Installed
This indicates that power levels are satisfactory in the subsystems. Powering On the System Using the Service Processor The system can be powered on using the System Power Control menu, which is a Service Processor menu that is available to the privileged user. Eserver pSeries 670 Service Guide...
Page 801: Hot-Pluggable Frus
Hot-Pluggable FRUs Notes: 1. The Linux operating system does not support some hot-pluggable procedures. 2. Linux does not support hot-plugging any hot-pluggable PCI adapters or devices. A 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 802 Optional media SCSI Yes (AIX only) Must be removed from the configuration and the partition devices must be booted afterwards to ensure correct operation. Might require additional consideration or preparation by the customer for replacement. Eserver pSeries 670 Service Guide...
Page 803: Power Subsystem
Power Subsystem This section contains the removal and replacement procedures for the power subsystem. Notes: 1. All pluggable BPA FRUs are replaced concurrent with system operation when the removal and replacement instructions are followed. Exceptions to this occur when multiple failures exist in the BPA. 2.
Page 804: Bulk Power Controller (Bpc)
5. Move the UEPO bypass switch to the NORMAL position. 6. Press the white Service Complete button on the UEPO switch to indicate completion of this procedure. The BPA automatically configures as it powers on. Eserver pSeries 670 Service Guide...
Page 805: Bulk Power Distributor (Bpd)
Bulk Power Distributor (BPD) There can be two BPDs, located immediately above the BPC. If only one BPD is required, an airflow baffle must installed in the top BPD position. Attention: This service procedure may produce other power error code(s) (101x xxxx) between the time the Start Service button is pressed, and the Service Complete button is pressed, during concurrent repair.
Page 806: Bulk Power Fan (Bpf)
5. Plug the BPF cable to the BPC, ensuring that the plug location and the cable label agree. 6. Press the white Service Complete button on the UEPO switch to indicate completion of this procedure. Eserver pSeries 670 Service Guide...
Page 807: Bulk Power Enclosure (Bpe)
Bulk Power Enclosure (BPE) Attention: This service procedure may produce other power error code(s) (101x xxxx) between the time the Start Service button is pressed and the Service Complete button is pressed, during concurrent repair. If the system behaves normally, as described by this procedure, ignore these error codes. Removal Attention: The BPE unit weighs approximately 18.14 kg (40 lbs).
Page 808: Unit Emergency Power Off (Uepo) Card Assembly
2. Plug all cables to the UEPO card assembly, ensuring that the plug location and the cable label agree. 3. Install the external cable, if required, to connector J02. a. If the external EPO connection is installed, the internal toggle switch is mechanically forced into the ROOM EPO ACTV position (to the right). Eserver pSeries 670 Service Guide...
Page 809: Integrated Battery Feature (Ibf)
b. If there is no external EPO cable, manually set the internal toggle switch to the ROOM EPO BYPASS position. To set this switch, pull the knob down, to the ROOM EPO BYPASS position, and release the knob (to the left). 4.
Page 810 11. Reinstall all components removed during the removal process. 12. Set the circuit breaker to the on (left) position. 13. Press the white Service Complete button on the UEPO switch to indicate completion of this procedure. Eserver pSeries 670 Service Guide...
Page 811: Installing The Mcm/L3/Passthrough Plug Map
Processor Subsystem This section contains the removal and replacement procedures for the processor subsystem. Handle all processor subsystem FRUs with extreme care. Installing the MCM/L3/Passthrough Plug Map If the MCM/L3/Passthrough Plug Map is not installed in the system, install it before continuing with any repair action for MCMs or L3 cache module.
Page 812: I/O Books And I/O Blanks
If the ″version mismatch″ error does not appear on the HMC, the firmware level of the new primary I/O book must still be determined. Note: You need a laptop computer (and cable part number 62H4857) capable of connecting to serial port 2 on the primary I/O book. Eserver pSeries 670 Service Guide...
Page 813 a. Open a virtual terminal window on the HMC. b. When OK is displayed in the operator panel on the media drawer, press a key on the virtual terminal on the laptop computer. The firmware version (from the new I/O book) is displayed above the main menu, in the format RHyymmdd or vHyymmdd.
Page 814 2. If you are replacing a primary I/O book, make sure you set the system time and date through the date operating system command, and enter the I/O type as described in “Change I/O Type” on page 728. Eserver pSeries 670 Service Guide...
Page 815: Battery
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 816 2. Reset the service processor settings. See “Saving and Restoring Service Processor Settings” on page 710 for information about restoring the service processor settings. 3. Ensure that the customer resets the service processor information such as the date, time, and passwords. Eserver pSeries 670 Service Guide...
Page 817: Processor Subsystem Dca (Distributed Converter Assembly) Books And Dca Blanks
Processor Subsystem DCA (Distributed Converter Assembly) Books and DCA Blanks Removal The following safety notice applies to power-related field replaceable units. DANGER Do not attempt to open the covers of the power supply. Power supplies are not serviceable and are to be replaced as a unit. 1.
Page 818: Capacitor Books And Blanks
5. Check torque on both fasteners. 6. If any cables were removed during the removal procedure, plug all cables into their correct locations. 7. Turn on the power as described in “Powering the System On” on page 780. Eserver pSeries 670 Service Guide...
Page 819: Mcm Module (Processor) And Pass Through Modules
MCM Module (Processor) and Pass Through Modules Attention: All components must be replaced to the location from which they were removed. Before replacing MCMs, check with your support center to ensure you have been directed to replace the MCM(s) by a valid error code in Chapter 5, “Error Code to FRU Index”, on page 345. Handling Static-Sensitive Modules Attention: MCM and L3 modules are sensitive to static electricity discharge.
Page 820 7. If the MCM modules that you are removing have a copper heatsink and an aluminum stiffener attached to the backplane, do the following: Note: Remove each MCM processor from the processor drawer, one at a time, until all MCM processors that you planned to remove have been removed. Eserver pSeries 670 Service Guide...
Page 821 8. Beginning with the upper most module to be removed, loosen the two captive heatsink bushing screws until they are free floating. See the following illustration for heatsink bushing screw locations. 9. Insert the two steel alignment rods through the MCM alignment holes and into the aluminum stiffener. See the following illustration for MCM clearance hole locations.
Page 822 The steel alignment rods are used to relieve some of the weight of the MCM processor when removing them from the processor drawer. b. The field restocking plan, is to replace the 1.7 GHz copper heatsink MCM (factory installed) with a 1.7 GHz aluminum heatsink MCM. Eserver pSeries 670 Service Guide...
Page 823 19. With both hands, grasp the module across the narrow span of the heatsink cap, and pull the MCM module from the system board and place it, posts-down, on the ESD mat. 1 Processor Backplane 2 MCM (aluminum heatsink version) 3 MCM Pass Through 20.
Page 824 (top side) or counter bore pin indent (bottom side). Missing buttons 23. Record on the system log sheet on the system the date that this MCM has been removed. Eserver pSeries 670 Service Guide...
Page 825 Returning MCM Modules: The following procedure provides handling instructions for MCM modules to be packaged and returned to the plant of manufacture. 1. If you are replacing an MCM, use the packaging from the new module to return the old module. If the packaging is not available, order the following parts for MCM or pass through protective packaging: v 1 Black Plastic Case (Top and Bottom) 02P3750 v 1 MCM Heat Sink Cap - 7335949 or 7335963 (not required for pass through)
Page 826 MCM when securing both locking cams. 6. Loosen the actuation bolt at the rear of the MCM module. 7. Push the actuation bolt in and slide the spring plate assembly to the down position. Eserver pSeries 670 Service Guide...
Page 827 8. Use the torque wrench (supplied with the system tool kit, see “Tools” on page 962 for the tool part number) to tighten the actuation bolt. When the wrench clicks, followed by about 15 degrees of free motion, the bolt is seated. 9.
Page 828 8. Exit the menu completely before powering on the system. Eserver pSeries 670 Service Guide...
Page 829: Methods For Testing Mcms And Pass Through Modules For A Short Circuit
17. Turn on power as described in “Powering the System On” on page 780. Note: The 4-way processor MCM FRU can have odd-numbered processors or even-numbered processors. If you have just replaced a 4-way MCM module, notify the customer that they can determine their processor numbering by issuing the command lsdev -C on the partition that is using the new processors.
Page 830: Method 1. Testing Mcms And Pass Through Modules For A Short Circuit
MCM Installation Shorts Test, Step 1: Attention: Be sure to record the resistance readings taken during these tests so that you can refer to them if needed. * See “Shorts Test Qualified Service Meters and Fail Criteria” on page 837. Eserver pSeries 670 Service Guide...
Page 831 MCM Installation Shorts Test, Step 2: * See the Fail Criteria value in “Shorts Test Qualified Service Meters and Fail Criteria” on page 837. Chapter 9. Removal and Replacement Procedures...
Page 832 Update the history Log on SFP Fold the paper with the recorded data and place inside the plug tracking chart and then fold the chart * See “L3 Cache Modules” on page 819. Eserver pSeries 670 Service Guide...
Page 833: Method 2. Testing Mcms And Pass Through Modules For A Short Circuit
Method 2. Testing MCMs and Pass Through Modules for a Short Circuit Performing this test ensures that a short circuit was not created when installing an MCM or a pass through module. Follow the procedure to install and use a multimeter and capacitor book (part number 44P2471 or later) during MCM replacement.
Page 834 MCM Installation Shorts Test, Step 2: * See the Fail Criteria value in “Shorts Test Qualified Service Meters and Fail Criteria” on page 837. Eserver pSeries 670 Service Guide...
Page 835 MCM Installation Shorts Test, Step 3: * See “L3 Cache Modules” on page 819. Chapter 9. Removal and Replacement Procedures...
Page 836: Method 3. Testing Mcms And Pass Through Modules For A Short Circuit
2) If the battery appears to be functioning and the LEDs are not lit as shown in this table, the LGA-ST is defective. Replace the unit before proceeding. Eserver pSeries 670 Service Guide...
Page 837 c. Power off the system. d. Set UEPO to OFF. e. Disengage all DCAs from the back plane. f. Plug the LGA-ST Tester D-Shell into the Capacitor card 9-pin D-Shell and tighten the screws. g. Place the toggle switch into the MCM/L3 PWR/GND position and observe the lit LEDs. Refer to the following table for valid LED states: Toggle Switch MCM Green...
Page 838 L3 modules before power the system on, perform “Method 3. Testing L3 Cache Modules for a Short Circuit” on page 835. 5. Install another MCM or pass through module and repeat step 4 until all required MCMs are installed. Eserver pSeries 670 Service Guide...
Page 839: L3 Cache Modules
L3 Cache Modules Handling Static-Sensitive Modules Attention: MCM and L3 modules are sensitive to static electricity discharge. These devices are shipped in antistatic containers to prevent damage caused by electrostatic discharge. Take the following precautions: v Use an antistatic wrist strap while handling the device. v Do not remove the device from the antistatic container until you are ready to install the device in the system unit.
Page 840 10. Clean the LGA site using the brush supplied with the new module. Note: Before you remove the brush from its protective bag, loosen the bristles by pressing them on the ESD mat until they are 90 degrees from the handle. Eserver pSeries 670 Service Guide...
Page 841 Attention: Each time an L3 cache module is removed from the system backplane, the LGA site where the module connects must be cleaned. With the brush supplied with the replacement kit, use only downward strokes, starting in the upper left corner. Move left to right, top to bottom, using overlapping strokes as shown in the following illustration.
Page 842 5. If you are installing a new L3 cache module, replace the sleeves that you removed earlier with the new sleeves provided with the L3 cache module kit. If you are reseating an existing module, use a lint-free cloth to wipe any dust from the sleeves that you removed earlier. Eserver pSeries 670 Service Guide...
Page 843 6. Be sure to align the notches at the upper right corner of each spring plate as shown in the following illustration. Replace the spring plates that you removed earlier with the new spring plates provided with the L3 cache module kit. 1 Notch on upper right corner 2 5-mm set screw 3 Reinforced center...
Page 844: Methods For Testing L3 Cache Modules For A Short Circuit
(or any capacitor books with the necessary LGA test support features), and the new LGA-ST. Refer to “Method 3. Testing L3 Cache Modules for a Short Circuit” on page 835. Eserver pSeries 670 Service Guide...
Page 845: Method 1. Testing L3 Cache Modules For A Short Circuit
Method 1. Testing L3 Cache Modules for a Short Circuit Performing this test ensures that a short circuit was not created when an L3-cache module is installed. Follow this procedure to install and use the MCM/L3 module short-circuit test tool (part number 44P0209) and a multimeter during L3-cache module replacement.
Page 846 Reject the L3 cache module Are Shorts Visible? Are all The Memory Disengaged? Disengage One I/O Book Disengage A Memory Book Primary I/O Book First Memory are removed one at a time Secondary I/O Books second Eserver pSeries 670 Service Guide...
Page 847 L3 Cache Shorts Test, Step 3: * See “Shorts Test Qualified Service Meters and Fail Criteria” on page 837. Chapter 9. Removal and Replacement Procedures...
Page 848 L3 Cache Shorts Test, Step 4: Eserver pSeries 670 Service Guide...
Page 849 L3 Cache Shorts Test, Step 5: Chapter 9. Removal and Replacement Procedures...
Page 850: Method 2. Testing L3 Cache Modules For A Short Circuit
L3 Cache Shorts Test, Step 1: Attention: Be sure to record the resistance readings taken during these tests so that you can refer to them if needed. * See “Shorts Test Qualified Service Meters and Fail Criteria” on page 837. Eserver pSeries 670 Service Guide...
Page 851 L3 Cache Shorts Test, Step 2: Chapter 9. Removal and Replacement Procedures...
Page 852 L3 Cache Shorts Test, Step 3: * See “Shorts Test Qualified Service Meters and Fail Criteria” on page 837. Eserver pSeries 670 Service Guide...
Page 853 L3 Cache Shorts Test, Step 4: Chapter 9. Removal and Replacement Procedures...
Page 854 L3 Cache Shorts Test, Step 5: Eserver pSeries 670 Service Guide...
Page 855: Method 3. Testing L3 Cache Modules For A Short Circuit
Method 3. Testing L3 Cache Modules for a Short Circuit You must test the LGA-ST unit before you can begin testing the MCM and pass through modules for a short circuit with the following steps: 1. Plug the LGA-ST test head on the test box into the 9-pin female self-test D-shell, located on the LGA-ST control box, which looks similar to the following: 1 Test head 5 Toggle switch...
Page 856 Capacitor book from the system. If the LED states are not as shown in this table after the Capacitor book is disengaged, the LGA-ST is defective. Replace the unit before proceeding. 3. Install an L3 module. Eserver pSeries 670 Service Guide...
Page 857: Shorts Test Qualified Service Meters And Fail Criteria
4. Press the toggle switch on the LGA-ST forward to the MCM/L3 PWR/GND position. This action will test the L3 modules for power-to-ground shorts. Observe the lit LEDs on the LGA-ST and take the corresponding following actions: Green L3 LED is lit This is a pass state.
Page 858 83 (with CAT III front 400 Ohms +/-0.20 +0.50 panel marking) Fluke 83-3 400 Ohms +/-0.20 +0.50 Fluke 85 (with CAT III front 400 Ohms +/-0.20 +0.50 panel marking) Fluke 85-3 400 Ohms +/-0.20 +0.50 Eserver pSeries 670 Service Guide...
Page 859: Capacity Upgrade On Demand (Cuod) Vpd Module
Manufacturer Model Range Accuracy @ 1.0 Fail Criteria ohms or less Fluke 87 (with CAT III front 400 Ohms +/-0.20 +0.50 panel marking) Fluke 87-3 200 Ohms +/-0.20 +0.50 Capacity Upgrade on Demand (CUoD) VPD Module Use the following instructions to replace the CUoD VPD module. This action should only be taken if the VPD module is listed as a failing FRU.
Page 860 If the number of processors match, reboot the system and return control of the system to the customer. v If the number of processors does not match, return to the Processor Order Information panel and verify the information with service support. Eserver pSeries 670 Service Guide...
Page 861: Vpd Card
VPD Card Notes: 1. The MCM module and its associated VPD card are a single FRU and must be replaced as a set. 2. There is only one VPD card for all of the L3 modules. Replacing any L3 module requires replacing the associated VPD card.
Page 862: System Clock Card
1. Squeeze the tabs on the clock card and push the card straight in. 2. Replace the fan chassis. See “Fan Chassis” on page 849. 3. Turn on power as described in “Powering the System On” on page 780. Eserver pSeries 670 Service Guide...
Page 863: Aluminum Backplane Stiffener
Aluminum Backplane Stiffener Use the following procedure when populating the system with MCM processors that employ the use of copper heatsinks, or if you will be replacing a system backplane prior to November 2003. Removal 1. Turn off the power as described in “Powering Off and Powering On the System” on page 779. 2.
Page 864 3 Aluminum Backplane Stiffener 7 MCM with VPD Card Kit 4 MCM Alignment Rods 8 Aluminum Backplane Stiffener Retaining Screws (quantity 8) Replacement To replace the aluminum stiffener follow the removal procedure in reverse order. Eserver pSeries 670 Service Guide...
Page 865: Processor Subsystem Chassis
Processor Subsystem Chassis CAUTION: This unit weighs more than 55 kg (121.2 pounds). Material handling systems such as levers, slings, or lifts are required to safely move it. When this is not possible, specially trained persons or services (such as riggers or movers) must be used. Three people are required to handle this operation: one person to push the chassis, and two people to pull the chassis.
Page 866 Mating the two surfaces is critical for the processor to function properly. 1. Position the lift tool such that the new processor subsystem chassis can be moved onto the lift plate. 2. Install the wheel chocks and engage the brake. Eserver pSeries 670 Service Guide...
Page 867: Memory Books And Memory Blanks
3. Position the plate at the correct level, and move the new processor subsystem chassis onto the tool with the rear side flush with the lift plate. Strap the processor subsystem chassis to the lift plate using the tie-down strap. 4.
Page 868: Fan Controller
3. Tighten the knurled captive screws to the fan assembly. 4. Plug all cables into their correct location in the DCA. 5. Press the white Service Complete button on the UEPO switch to indicate completion of this procedure. Eserver pSeries 670 Service Guide...
Page 869: Processor Fan Assemblies
Processor Fan Assemblies Removal Attention: The fan controller weighs approximately 5 Kg (11 lb.) 1. Locate the fan assembly to be replaced. 2. Note the state of the fan controller’s LEDs. 3. Press the green Start Service button on the UEPO switch. 4.
Page 870: I/O Subsystem Pci Slot Led Definitions
Perform PCI adapter remove, replace, or install only when directed by the PCI hot-plug procedures. Off/No power The PCI slot power is off. If the system power is off, perform non-hot-plug PCI adapter remove, replace, or install procedure. Eserver pSeries 670 Service Guide...
Page 871: Pci Adapters
PCI Adapters Note: Linux does not support hot-plugging any hot-pluggable PCI adapters or devices. A system with Linux installed on one or more partitions must be shut down and powered off before replacing any PCI adapter or device assigned to a Linux partition. Follow the non-hot-pluggable adapter or device procedures when replacing a PCI adapter or device in any partition with Linux installed.
Page 872: Removing A Pci Adapter Cassette
The following illustration shows the PCI adapter cassette. 1 PCI Adapter Cassette 2 Handle-Release Lever Latch 3 Locking Bar 4 Handle Release Lever 5 Handle 6 PCI Adapter Tailstock Tab 7 Adapter Cassette Pull Tab Eserver pSeries 670 Service Guide...
Page 873 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 874 Do not force the PCI adapter cassette out of the PCI adapter slot. The cassette will slide out smoothly when this step is performed correctly. c. Do not remove more than one adapter cassette at a time. Eserver pSeries 670 Service Guide...
Page 875 Replacing a PCI Adapter Cassette: Attention: Perform this procedure only when you are instructed to from “Removing a Non-Hot-Pluggable PCI Adapter” on page 857 or “Hot-Pluggable PCI Adapter” on page 858. Before you replace the PCI adapter cassette, check the following: v Before installing a PCI adapter cassette in the system, an adapter or blank filler must be installed in each PCI adapter cassette and the top cover for the system must be installed.
Page 876 7. As you slide the cassette into the slot, ensure that the dovetail rail on the top of the PCI adapter cassette aligns with the mating slots on any cassettes that might be installed on the left and right sides. 8. Push the cassette in until it is flush with any other installed cassettes. Eserver pSeries 670 Service Guide...
Page 877 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 878 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 879 11. Answer YES to Keep Definition. Press Enter. 12. The ARE YOU SURE screen displays. Press Enter to verify the information. Successful unconfiguration is indicated by the OK message displayed next to the Command field at the top of the screen.
Page 880 Align the bottom edge of the PCI cassette cover with the PCI adapter guide rail on the I/O backplane. Note: If there is a cassette to the left of the one you are installing, align the ridge on the cover with the ″tick″ in the notch of the neighboring cassette. Eserver pSeries 670 Service Guide...
Page 881 e. Slide the cassette partially into the guide. f. Ensure that the dovetail on the top track aligns with its mating component(s) on both sides. 1 I/O Subsystem 2 PCI Adapter Cassette g. When the cassette is fully inserted, prepare to activate the handle by lowering the locking bar. Lift the handle all the way up until you hear a click.
Page 882 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 883 Identify a PCI Hot-Plug Slot Allows the user to identify a PCI slot. The selected PCI slot will go into the Identify state. Unconfigure a Device Allows the user to put an existing PCI adapter into the Defined state if the device is no longer in use. This step must be completed successfully before starting any removal or replacement operation.
Page 884 9. Use a small screwdriver to lift the guide lock, and slide the card arm away from the PCI card until the card end is free. 10. Push the lower-front heel off the card, and remove the PCI card from the assembly. Eserver pSeries 670 Service Guide...
Page 885 Replacement: 1. Ensure that you have the following parts: v Bezel and linkage subassembly v Cover v Clip v Insertion Clip (see the following note) v Short card arm v Long card arm Screws (10--2 are extra) Note: If you are installing a Gigabit Ethernet (FC 2969 type 9U), Ultra3 SCSI (FC 6203 Type 4Y), or 10/100 BaseT Ethernet (FC 4962 Type AF), use the additional clips listed below to help when you are seating the adapter during installation.
Page 886 2) To remove any slack between the top and bottom clips, use pliers or screwdriver to adjust the top front clip downward. If the top clip is pushed too far down without engaging the card, remove the top front clip by popping it off the rail. Reattach the clip and start again. Eserver pSeries 670 Service Guide...
Page 887 4. Attach the appropriate short card (if the card does not extend beyond the mark at the top of the linkage subassembly) or long card arm to the support arm of the linkage subassembly as follows: 1 Mark at the Top of Linkage 5 Short Adapter Subassembly 2 Top Rear Clip (Shown on the long...
Page 888 5. Tilt the top of the bezel away from the PCI card while lowering the bottom of the tailstock into bottom of the bezel, as shown in the following illustration. 1 Adapter Cassette Bezel 2 Short Card Arm 3 Long Card Arm Eserver pSeries 670 Service Guide...
Page 889 6. When the lower corner of the card is fully seated into the bezel, rotate the top of the bezel over the tailstock of the card. 1 Adapter Card 2 Adapter Card (Lower Corner) 3 Front Bottom Clip 4 Adapter Cassette Bezel 7.
Page 890 9. With the tailstock to the left on a flat surface, position the cover over the linkage assembly. 10. Tuck the top and bottom tabs at the left of the cover under the bezel. 1 Front Top Tab Eserver pSeries 670 Service Guide...
Page 891 2 Front Bottom Tab Snap the top-right corner of the cover over the guide bump on the linkage assembly. 12. Align the holes at the top of the cover with those in the linkage subassembly and screw the cover to the linkage subassembly in the sequence shown in the following illustration.
Page 892 1. Place the PCI adapter cassette assembly on a flat work surface with the cover facing up, and the top of the adapter facing you. See the following illustration. 1 Cover 3 Top of Cover 2 Handle Eserver pSeries 670 Service Guide...
Page 893 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 Chapter 9. Removal and Replacement Procedures...
Page 894 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 Eserver pSeries 670 Service Guide...
Page 895 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 896 This action allows the bezel to be removed. 1 Bezel Extension 2 Plastic Cover Latch in Bezel Hook d. On the opposite side of the cassette (cover side), push the cover latch to release the bezel. 1 Cover Side 2 Cover Latch Eserver pSeries 670 Service Guide...
Page 897 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 898 Raise the handle on the cassette linkage assembly until it locks into the up position (the blank filler or adapter moves downward). 1 Handle Release Lever 2 Locking Bar Eserver pSeries 670 Service Guide...
Page 899 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 900 Slide the long and short adapter arms away from the blank filler or adapter. 1 Long Adapter Arm 2 Release Tab 3 Release Tab 4 Short Adapter Arm 5 Slotted Tab Eserver pSeries 670 Service Guide...
Page 901 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 902: Replacing An Adapter In A Pci Adapter Cassette
Metal edges might be sharp. This procedure is performed when preparing to install a new adapter or a blank filler in the processor subsystem or an I/O drawer. Familiarize yourself with the entire procedure before performing the following steps. Eserver pSeries 670 Service Guide...
Page 903 1. Place the empty PCI Adapter Cassette Assembly linkage on a flat work surface in front of you. Position the cassette so that the handle is in the raised (up) position, and on the left, with the top of the linkage facing away from you.
Page 904 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 905 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 887. a. Remove the adapter from its protective packaging and, if present, remove the plastic extension handle from the end of the adapter.
Page 906 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. LONG SHORT 1 Top Adapter-Retaining Clip Eserver pSeries 670 Service Guide...
Page 907: Short Adapter Or Blank Filler Installation
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 assembly will extend down beyond the cassette top).
Page 908 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 Eserver pSeries 670 Service Guide...
Page 909 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 910 1 Short-adapter Retaining Arm 2 Adapter or Blank Filler 3 Cassette Linkage Rail Eserver pSeries 670 Service Guide...
Page 911 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 912 6. To hold the top of the adapter, slide down the adjustable top adapter-retaining clip on the retaining arm. Ensure that the bottom edge of the adapter is held by the lower part of the adapter retaining arm. 1 Adjustable Top Adapter-Retaining Clip Eserver pSeries 670 Service Guide...
Page 913 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 that 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 Chapter 9.
Page 914 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 Eserver pSeries 670 Service Guide...
Page 915 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 Chapter 9.
Page 916 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 for the Cover Arm Latch Eserver pSeries 670 Service Guide...
Page 917 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 assembly until the tab on the top of the bezel is seated in the recess of the cassette assembly. 1 Recess 3 Tab 2 Groove...
Page 918 The bezel tab should be seated as shown in the following illustration. 1 Pin b. Ensure that the cover arm latch is completely pressed into the hooked notch on the bezel as shown. 1 PCI Adapter Pull Tab 2 Hooked Notch in the Bezel Eserver pSeries 670 Service Guide...
Page 919 c. Turn the cassette assembly over so the cover is facing up. Check the cover latch to ensure that it is holding the bezel to the cover as shown. 1 Cover Latch 12. Ensure the holes are aligned, and insert the bushing-lock pin into the bushing as shown. 1 Bushing 2 Bushing-Lock Pin Chapter 9.
Page 920 1 Location of the Installed Bushing and Bushing-Lock Pin 13. Insert the bushing-lock pin into the hole in the bushing, and push it in until it seats as shown in the following illustration. 1 Bushing-Lock Pin Eserver pSeries 670 Service Guide...
Page 921 14. Depress the handle release lever to ensure the locking bar on the handle is pulled into the unlocked position. Raise the handle on the cassette linkage assembly until it locks into the up position (the blank filler or adapter moves downward). 1 Handle Release Lever 2 Locking Bar 15.
Page 922 1 Metal EMC Shield b. The metal EMC shield has clips that slide over the top of the tailstock. Ensure that these clips are holding the metal EMC shield to the tailstock. 1 Top of Tailstock Eserver pSeries 670 Service Guide...
Page 923 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). 1 Handle 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 color to be visible.
Page 924: Long Adapter Installation
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 Eserver pSeries 670 Service Guide...
Page 925 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 926 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 Eserver pSeries 670 Service Guide...
Page 927 4. Ensure that the top adjustable adapter-retaining clip catches the corner of the adapter as shown in the following illustration. 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 928 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). 1 Handle 2 Handle Release Lever Eserver pSeries 670 Service Guide...
Page 929 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 930 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 Aligned in the Cover Eserver pSeries 670 Service Guide...
Page 931 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 932 1 Recess 3 Tab 2 Grooves 4 Bezel d. Insert the two tabs on the bezel extension into the two slots on the cassette assembly. 1 Tabs Eserver pSeries 670 Service Guide...
Page 933 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 934 1 Cover Latch 12. Position the adapter with the cover side facing up. Ensure that the holes are aligned, and insert the bushing as shown. 1 Bushing 2 Bushing-Lock Pin Eserver pSeries 670 Service Guide...
Page 935 1 Bushing 2 Bushing-Lock Pin 13. Insert the bushing-lock pin into the hole in the bushing. Push on the pin until it seats. 1 Location of the Installed Bushing and Bushing-Lock Pin Chapter 9. Removal and Replacement Procedures...
Page 936 2 Locking Bar 15. To install the metal EMC shield on the adapter bracket, grasp the metal EMC shield as shown in the following illustration, and do the following: 1 Metal EMC Shield 2 Adapter Bracket Eserver pSeries 670 Service Guide...
Page 937 a. Ensure that the shield slides up inside the top of the cassette. 1 Metal EMC Shield 2 Adapter Bracket Chapter 9. Removal and Replacement Procedures...
Page 938 1 Handle 17. Using your 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 color to be Eserver pSeries 670 Service Guide...
Page 939 visible. If the adapter is not hot-swappable, the blue color 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. For more information, refer to your system documentation.
Page 940: Replacing A Double-Wide Blind-Swap Adapter
9. Connect power to the system and go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Refer to “Powering the System On” on page 780 if necessary. 10. Ensure that the adapter is configured when the system completes the boot process. Eserver pSeries 670 Service Guide...
Page 941: Updating Xilinx Code On An Sp Switch2 Pci Attachment Adapter
Updating Xilinx Code on an SP Switch2 PCI Attachment Adapter Note: This section applies only if the system is being used in a clustering environment. This procedure must be followed when an SP Switch2 PCI Attachment Adapter is installed or replaced, or when PSSP software is upgraded on a server or logical partition with an SP Switch2 PCI Attachment Adapter installed.
Page 942 14. When the server or logical partition is back up, from the CWS, type: Eunfence -p x nn (where x is plane 0 or 1 and nn is the node_number of the server or logical partition) RESPONSE: All nodes successfully unfenced. Eserver pSeries 670 Service Guide...
Page 943: Hot-Plug Steps For The Sp Switch2 Pci Attachment Adapter
Hot-Plug Steps for the SP Switch2 PCI Attachment Adapter This procedure must be followed when doing hot-plug removal and replacements steps for the SP Switch2 PCI Attachment Adapter. On the control workstation (CWS) or from the server node, do the following: 1.
Page 944: I/O Subsystem Rio Riser Card
4. Remove the two screws that attach the RIO riser card to the I/O subsystem backplane. 5. Carefully pull the card out of the slot as shown in the following illustration. 1 RIO Riser Card Replacement Replace in reverse order. Eserver pSeries 670 Service Guide...
Page 945: I/O Subsystem Distributed Converter Assembly (Dca)
I/O Subsystem Distributed Converter Assembly (DCA) Notes: 1. If multiple I/O planars or I/O Drawer DCAs are being replaced during a maintenance window, then they must be replaced one at a time in order to ensure the I/O Drawer serial number does not become damaged.
Page 946 5. Alternate tightening the left and right thumbscrews until both are fully torqued in. 6. Check torque on both thumbscrews. 7. Plug all cables into their correct location in the DCA. 8. Press the white Service Complete button on the UEPO switch. Eserver pSeries 670 Service Guide...
Page 947: I/O Subsystem I/O Backplane Assembly
I/O Subsystem I/O Backplane Assembly Removal Note: If multiple I/O planars or I/O Drawer DCAs are being replaced during a maintenance window, then they must be replaced one at a time in order to ensure the I/O Drawer serial number does not become damaged.
Page 948 4. Upon contact, insert the insertion tool (part number 11P4789) to cam the backplane into the connector. 5. Pry with the tool until the screw holes on the chassis and the board align. 6. Secure with two screws. 7. Reinstall all adapters and reconnect all cables to the replaced I/O backplane. Eserver pSeries 670 Service Guide...
Page 949: I/O Subsystem Dasd Hard Disk Drive Assembly
I/O Subsystem DASD Hard Disk Drive Assembly Note: Linux does not support hot-plugging any hot-pluggable PCI adapters or devices. A system with Linux installed on one or more partitions must be shut down and powered off before replacing any PCI adapter or device assigned to a Linux partition. Follow the non-hot-pluggable adapter or device procedures when replacing a PCI adapter or device in any partition with Linux installed.
Page 950 Note: If the tab is not aligned with the slot, do not raise the handle. Remove the assembly and start again. 8. Lift the black handle to move the assembly in slightly. 9. Lift the handle and push forward until the blue latch hooks the assembly body. Eserver pSeries 670 Service Guide...
Page 951: I/O Subsystem Dasd 4-Pack
I/O Subsystem DASD 4-Pack Removal 1. Press the green Start Service button on the UEPO switch. 2. Locate the DASD backplane to be replaced. 3. Turn off the power as described in “Powering Off and Powering On the System” on page 779. 4.
Page 952: I/O Subsystem Fan
Replace in reverse order. When you have completed the replacement of the DASD fan, turn on the power as described in “Powering Off and Powering On the System” on page 779, and press the white Service Complete button on the UEPO switch. This completes the replacement. Eserver pSeries 670 Service Guide...
Page 953: I/O Subsystem Chassis
I/O Subsystem Chassis Removal Attention: This process requires: v The use of a lift tool (part number 09P2481) and lift-plate assembly tool (part number 11P4369). v The lift tool wheels must be chocked to prevent the chassis from moving during the operation. The frame must not be on its casters, the leveling pads must be engaged to prevent the frame from moving during the operation.
Page 954 7 DASD-4 Pack Cage 3 DASD 4-Pack Filler 8 DCA 4 DASD Filler 9 Half I/O drawer filler plate 5 Front Cover Rear: 1 PCI I/O Subsystem Chassis 3 Blind-swap cassette or PCI filler with no adapter Eserver pSeries 670 Service Guide...
Page 955 Replacement Notes: 1. If you are replacing this assembly with a new assembly, the manufacturing label with the machine type, model number, and the serial number for the subsystem must be ordered to apply to the new part. For information on replacement labels, see Chapter 10, “Parts Information”, on page 941. 2.
Page 956: Media Subsystem
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 957: Diskette Drive
Diskette Drive Removal 1. Ensure that the diskette drive is in idle mode (the activity light remains off). 2. Loosen the thumbscrew that attaches the diskette carrier to the media subsystem. SCSI SCSI 3. Carefully grasping the thumbscrew and not the bezel, pull the drive assembly out until you can access the cables at the rear.
Page 958: Operator Panel
3. Push the operator panel into the chassis until the spring clip engages. 4. Push the chassis into the rack, and replace the two mounting screws. 5. Turn on the power as described in “Powering the System On” on page 780. Eserver pSeries 670 Service Guide...
Page 959: Media Subsystem Chassis
Media Subsystem Chassis Removal 1. Turn off power as described in “Powering Off and Powering On the System” on page 779. 2. Label and disconnect all cables from the rear of the media subsystem. SCSI SCSI 3. Remove the screw that holds the left side of the media subsystem chassis to the rack. 4.
Page 960: Media Subsystem Internal Cables
Replace in reverse order. Note: Be sure to secure the cables with the ties as they were originally installed. Allow enough length for a service loop in case the drives are removed in the future. Eserver pSeries 670 Service Guide...
Page 961: Chapter 10. Parts Information
7040 Model 671 Processor Subsystem v 7040 Model 61D I/O Subsystem The following 7040 FRUs each contain an IBM Manufacturing label with the machine type, model number, and the serial number for the subsystem of which they are a part:...
Page 962: Model 61R Rack Subsystem
7040 Model 61R Rack Subsystem The rack subsystem consists of the rack, power subsystem, and the integrated battery feature. 11 - Integrated Battery Feature (not pictured) Eserver pSeries 670 Service Guide...
Page 963 Index Part Number Units Per Description Assembly 44P0107 Rear Door 44P0127 Rear Door (Accoustic) 11P3948 42U Frame 44P0125 Cover, side left 44P0126 Cover, side, right 11P2890 Top hat 11P2923 Shipping bar 44P0105 Front Door Primary Rack 44P0106 Front Door Secondary Rack 11P1097 Front Latch Primary Rack 11P1096...
Page 964: Model 671 Processor Subsystem (Front)
7040 Model 671 Processor Subsystem (Front) This processor subsystem front view consists of the processor chassis, memory books, fans, and filters. Eserver pSeries 670 Service Guide...
Page 965 Index Part Number Units Per Description Assembly 11P4518 Processor subsystem chassis (with backplane) 11P2935 1 to 4 Memory book retainer See “7040 Model 671 Processor Subsystem (Front)” on page 946 for Memory books part numbers. 31L7627 Fan Controller (MDA) 07H5349 Fans 11P3781 Air filter...
Page 966: Model 671 Processor Subsystem (Front)
7040 Model 671 Processor Subsystem (Front) This processor subsystem front view consists of the memory books, MCM and L3 modules. Eserver pSeries 670 Service Guide...
Page 967 Index Part Number CCIN Units Per Description Assembly 44P1282 28AD System Backplane Protective Cover (Included as part of the L3 Cache Module FRU.) Note: Do not discard the protective cover. Use it when returning L3 FRUs. 00P2839 25D9 4 to 8 128 MB (4x32)/400 MHz L3 Cache kit Includes: v PN 21P7972 400 MHz VPD card (CCIN...
Page 968 53P4261 30C6 CUoD 16/32 GB Memory Book I 30C1 30CA 44P4420 Aluminum Backplane Stiffener 44P4415 Steel Alignment Rods Use the 1.7 GHz MCM FRU part number when MCM (with copper heat sync) ordering this FRU. Eserver pSeries 670 Service Guide...
Page 969: Model 671 Processor Subsystem (Rear)
7040 Model 671 Processor Subsystem (Rear) This processor subsystem rear view consists of the RIO books, DCAs, and capacitor books, MCM and L3 modules, as well as the media subsystem. Index Part Number CCIN Units Per Description Assembly 53P1573 2738 Fourth I/O book without RIO-2 ports 53P4554 2806...
Page 970 9-25 pin serial cable connects the managed system primary I/O book to HMC async adapter 53P1573 2738 Secondary I/O book without RIO-2 ports 53P4554 2806 Secondary I/O book with RIO-2 ports 11P2936 I/O book retainer Eserver pSeries 670 Service Guide...
Page 971: Model 671 Media Subsystem
7040 Model 671 Media Subsystem Chapter 10. Parts Information...
Page 972 Media Bay Cover 44P1055 Cassette, PCI adapter 44P3592 Cassette, PCI adapter (type 2) 97P2686 Ultra320 SCSI 44P1055 Ultra320 SCSI cassette 44P0239 Note: See RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems for part numbers. Eserver pSeries 670 Service Guide...
Page 973 Power and SCSI Cables to the Media Subsystem Chapter 10. Parts Information...
Page 974 Cable Connecting the Diskette Drive to the Media Subsystem 11P2352 Power Cable for Media Subsystem Front Components 11P4303 SCSI Cable for Media Subsystem Rear Components 11P4303 SCSI Cable for Media Subsystem Front Components 11P2351 Power Cable for Media Subsystem Rear Components Eserver pSeries 670 Service Guide...
Page 975: Front
7040 Model 61D I/O Subsystem The system can contain up to three I/O subsystems. This section lists detail for one I/O subsystem. Depending on your configuration, the quantities of parts listed may increase by the actual number of I/O subsystems in your system. Front Index Part Number...
Page 976: Rear
10/100 BaseT Ethernet FC 4962 Type AF 44P0406 for Gigabit Fibre Channel PCI FC 6228 Type 4W 11P4861 1 to 20 PCI filler, for slots with no adapter 44P1414 1 to 2 PCI I/O Backplane Eserver pSeries 670 Service Guide...
Page 977: Power Cabling
Power Cabling Rear Front Chapter 10. Parts Information...
Page 978 A35-BPC-P07 to (AMD4-P01) MDA4-J02, Red 11P4465 B35-BPC-P07 to (AMD4-P00) MDA4-J01, Red with white stripe 11P1596 B35-BPC-P02 to UEPO J01, Red 11P1595 A35-BPC-P02 to UEPO J00, Red with white stripe 05N6740 A35-BPR-P00 to A13-IBF1-P00 B35-BPR-P00 to B13-IBF2-P00 Eserver pSeries 670 Service Guide...
Page 979: Rio Cables And I/O Power Cables
RIO Cables and I/O Power Cables Index Number FRU Part Number Units Per Description Assembly 11P2355 RIO cable 0.5-meter, per drawer 11P0272 Up to 2 RIO cable 2-meter, per drawer 44H9137 Up to 2 RIO cable 15-meter, per drawer 00P5238 Up to 2 RIO-2 cable 1.75-meter 00P5239...
Page 980: Keyboards And Mouse
Keyboard, 101 Swedish, Finnish (ID 153) USB 24P0471 Keyboard, 101 LA Spanish (ID 171) USB Keyboard, 101 Korean (ID 413) USB 24P0446 Keyboard, 101 Chinese (ID 467) USB 24P0466 Keyboard, 101 Russian (ID 443) USB 09N5532 Three Button Mouse (USB) 8841 Eserver pSeries 670 Service Guide...
Page 981: System Power Cables
System Power Cables Index Number FRU Part Number Units Per Description Assembly 11P0916 Line Power Cord, US, Canada, Japan, 30 AMP 480 V 11P0367 Line Power Cord, US, Canada, Japan, 60 AMP 240 V 11P0914 Line Power Cord, US, Chicago, 30 AMP 480 V ac 11P0365 Line Power Cord, US, Chicago, 60 AMP 240 V ac 11P0918...
Page 982: Tools
Tools The following tools are needed to perform service actions on the Eserver pSeries 670. These tools can be ordered through your normal tools supplier. Index Part Number Units Per Description Assembly 46H9635 Tool box 11P4486 Torque tool MCM 04N6923...
Page 983: Appendix A. Environmental Notices
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 984: Acoustical Noise Emissions
3. LWAd is the upper-limit A-weighted sound power level; LpAm is the mean A-weighted sound pressure level at the 1-meter bystander positions;1 B =10 dB. 4. All measurements made in conformance with ISO 7779 and declared in conformance with ISO 9296. Eserver pSeries 670 Service Guide...
Page 985: Appendix B. Notices
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 986 Eserver pSeries 670 Service Guide...
Page 987: Appendix C. Service Processor Setup And Test
Attention: This procedure applies to modems attached to the serial ports (S1 and S2) on the primary I/O book (location U1.18-P1-H2). It does not affect the operation of the modem attached to the IBM Hardware Management Console for pSeries (HMC).
Page 988: Testing The Service Processor Setup
5. When your telephone rings, answer the call. You should hear the sound of a telephone being dialed. This is your computer trying to page you. If this test is successful, call-out is working correctly. Eserver pSeries 670 Service Guide...
Page 989: Serial Port Configuration
Serial Port Configuration To configure the serial port on an AIX system, do the following from an AIX console: 1. Log in as root user. 2. To determine if you have any serial ports already configured, type: lsdev -Cc tty If no serial ports are configured, none are listed.
Page 990 Eserver pSeries 670 Service Guide...
Page 991: Appendix D. Modem Configurations
Note: 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 992: Configuration File Selection
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 974 for the correct switch settings.
Page 993: Examples For Using The Generic Sample Modem Configuration Files
See your modem manual for more information. 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.
Page 994: Customizing The Modem Configuration Files
Dial-Up Line Enabled AT Responses Enabled (Extended Responses Disabled) *Down Asynchronous Operation 28.8KB Line Speed CD and DSR Normal Functions 2-Wire Leased Line Enabled * Only switches 11 and 12 are changed from the factory default settings. Eserver pSeries 670 Service Guide...
Page 995: Ring Detection
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 996: Transfer Of A Modem Session
If you are using modem_z.cfg or modem_z0.cfg, you cannot control DTR response. If your remote terminal does not disconnect after logging off, you must command the remote terminal emulator to hang up. This then breaks the connection. Eserver pSeries 670 Service Guide...
Page 997: Recovery Strategy
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 998: Modem Configuration Sample Files
# 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 999 "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 1000 # 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 Eserver pSeries 670 Service Guide...
Page 1001: Sample File Modem_M1.Cfg
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.

IBM pSeries 670 Service Manual

Table of Contents

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

Chapter 7. Using the Service Processor

Chapter 8. Using System Management Services

Chapter 9. Removal and Replacement Procedures

Table of Contents

Chapter 10. Parts Information

Appendix A. Environmental Notices

Appendix B. Notices

Appendix C. Service Processor Setup and Test

Appendix D. Modem Configurations

Appendix E. Ground Path

Quick Links

Chapters

Related Manuals for IBM pSeries 670

Summary of Contents for IBM pSeries 670