IBM pSeries 630 6C4, pSeries 630 6E4 Service Manual

Download

ERserver

򔻐򗗠򙳰

pSeries 630 Model 6C4 and Model 6E4

Service Guide

SA38-0604-03

ER s e r v e r

򔻐򗗠򙳰

pSeries 630 Model 6C4 and Model 6E4

Service Guide

SA38-0604-03

Fourth Edition (May 2003)

Before using this information and the product it supports, read the information in “Safety Notices” on page xi, Appendix A, “Environmental Notices”, on page 549, and Appendix B, “Notices”, on page 555.

A reader’s comment form is provided at the back of this publication. If the form has been removed, address comments to Information Development, Department H6DS-905-6C006, 11501 Burnet Road, Austin, Texas 78758-3493. To send comments electronically, use this commercial internet address: aix6kpub@austin.ibm.com. Any information that you supply may be used without incurring any obligation to you.

© International Business Machines Corporation, 2002, 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.

Contents

Safety Notices .................................xi

Rack Safety Instructions ..............................xi

Rack Safety Instructions ..............................xii

Electrical Safety .................................xii

Laser Safety Information ..............................xii

Laser Compliance ...............................xiii

Data Integrity and Verification ...........................xv

About This Book ................................xvii

ISO 9000 ...................................xvii

Highlighting ..................................xvii

Accessing Information ..............................xvii

References to AIX Operating System .........................xvii

Related Publications ...............................xviii

Trademarks ..................................xviii

Chapter 1. Reference Information ..........................1

Overview ....................................1

System Features .................................2

Processor Cards ................................3

I/O Expansion Drawer ..............................4

Hardware Management Console (HMC).........................6

Powering the System on and Off ...........................7

Console ....................................7

Power-On Self-Test ................................7

POST Indicators .................................7

POST Keys ...................................8

System Unit Locations ...............................9

Model 6C4 Rear View ..............................9

Power Supply Locations .............................12

Fan Locations .................................14

CEC Backplane Locations ............................15

PCI Riser Card Locations ............................16

Memory DIMM Location .............................18

Reading the Operator Panel and System LEDs ....................19

SCSI IDs and Bay Locations ...........................20

System Logic Flow ................................21

Systems Configured with a GP Processor and Four-Slotted PCI Riser Card ..........21

Systems Configured with a GQ Processor and Six-Slotted PCI Riser Card ..........22

Location Codes .................................23

Physical Location Codes .............................23

Location Code Format..............................23

AIX Location Codes ..............................24

Mapping AIX and Physical Location Codes .......................28

Four-Slotted PCI Riser Card Location Codes .....................29

Six-Slotted PCI Riser Card Location Codes ......................30

Disk Drive Backplane Location Codes ........................30

AIX and Physical Location Code Table........................31

System Cables .................................39

Subsystem Positioning and Cabling ..........................41

SPCN Cabling ................................41

RIO-2 Cabling.................................44

iii

Specifications ..................................46

External AC Power Cables .............................47

Service Inspection Guide..............................48

Chapter 2. Diagnostic Overview ..........................49

Maintenance Analysis Procedures (MAPs) .......................49

System LEDs ..................................50

System Attention LED ..............................50

Checkpoints ..................................50

FRU Isolation ..................................51

FRU Identify LEDs ................................51

Service Agent for the pSeries 630 Model 6C4 and Model 6E4 ................52

Using the Service Processor and Service Agent Features..................52

Service Focal Point ................................52

Getting Started ................................53

Testing Error Reporting .............................53

Service Focal Point Settings ...........................53

Working With Serviceable Events .........................55

Activating and Deactivating FRU LEDs .......................57

Accessing System Log Error Information ........................58

Accessing Errors when a System is Attached to an HMC .................58

Accessing Errors when a System is Running AIX and the Console is Not an HMC .......59

Accessing Errors when a System is Running Linux and the Console is Not an HMC .......59

Resetting the System Attention LED .........................60

Resetting the LED when a System is Attached To an HMC ................60

Resetting the LED when a System is Running AIX and the Console is not an HMC .......60

Resetting the LED when a System is Running Linux and the Console is not an HMC ......60

Chapter 3. Maintenance Analysis Procedures (MAPs) ..................61

Entry MAP ...................................61

Quick Entry MAP ................................63

MAP 1020: Problem Determination ..........................69

MAP 1240: Memory Problem Resolution ........................73

MAP 1230: Linux Platform Error Problem Resolution ...................80

Purpose of This MAP ..............................80

MAP 1235: System Array Self-Repair Problem Resolution for Linux ..............85

Purpose of This MAP ..............................85

MAP 1320: Service Focal Point ...........................86

MAP 1321: Quick Entry MAP for Systems with Service Focal Point ..............87

MAP 1322: End of Call MAP for Systems with Service Focal Point ..............100

MAP 1520: Power ................................105

FRU Identify LEDs ..............................106

MAP 1521: Base System Drawer With Power Failure and No Error Codes ...........107

MAP 1522: Cannot Power On the I/O Drawer, Power Present LED Does Not Come On ......114

MAP 1523: The SPCN Error Codes Table Directed You Here and the Error Code is 1011 1B0x . . . 121

MAP 1540: Problem Isolation Procedures .......................124

FRU Identify LEDs ..............................124

MAP 1541: JTAG Problem Isolation .........................126

MAP 1542: I/O Problem Isolation ..........................127

MAP 1548: Processor Subsystem Problem Isolation ...................139

MAP 1549: Attention Problem Isolation ........................153

MAP 154B: Insufficient Hardware Resources Problem Isolation ...............155

Step 154B-1 .................................155

Step 154B-2 .................................155

Step 154B-3 .................................155

Step 154B-4 .................................155

iv Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Step 154B-5 .................................155

Step 154B-6 .................................155

Step 154B-7 .................................156

Step 154B-8 .................................156

Step 154B-9 .................................156

Step 154B-10 ................................156

Step 154B-11 ................................156

Step 154B-12 ................................156

Step 154B-13 ................................156

Step 154B-14 ................................156

MAP 154C: SPCN Cable Problem Isolation ......................157

Chapter 4. Checkpoints .............................159

IPL Flow with an HMC Attached to the System .....................159

IPL Flow without an HMC Attached to the System ....................160

Service Processor Checkpoints ...........................161

Firmware Checkpoints ..............................168

Boot Problems/Concerns ............................204

Chapter 5. Error Code to FRU Index ........................209

Performing Slow Boot ..............................209

Confirming Initial Error Code ............................210

Four-Character Checkpoints ............................211

Replacing the Operator Panel ...........................211

Replacing the Network Adapter ...........................211

Determining Location Code ............................211

FRU Identify LEDs ...............................212

Checkpoint and Error Code Index ..........................213

Operator Panel Error Codes ............................216

SPCN Error Codes ...............................217

Firmware Error Codes ..............................226

Service Processor Error Codes ...........................249

Memory DIMM Present Detect Bits (PD-Bits) ......................334

Error Log Utility Procedure ............................335

System Firmware Update Messages .........................335

Scan Dump Messages ..............................335

Common Firmware Error Codes ..........................335

Error Code B1xx 4699 .............................344

Error Code B1xx 8FF0 .............................348

HMC/Partition Surveillance Error Codes ........................349

Scan Log Dump Progress Codes ..........................350

Problem Determination Generated Error Codes .....................351

Chapter 6. Using the Online and Standalone Diagnostics ................353

Operating Considerations for Online and Standalone Diagnostics ..............353

Identifying the Terminal Type to the Diagnostics ....................354

Undefined Terminal Types ............................354

Resetting the Terminal .............................354

Online Diagnostics Modes of Operation ........................354

Service Mode ................................354

Concurrent Mode ...............................356

Maintenance Mode ..............................356

Standalone Diagnostics Operations.........................357

Considerations for Running Standalone Diagnostics on a Partitioned System .........357

Considerations for Running Standalone Diagnostics from CD-ROM.............358

Running Standalone Diagnostics from a Network Installation Management (NIM) Server .....360

Contents v

Booting Standalone Diagnostics from the NIM Server on a System with or without an HMC

Attached .................................361

Chapter 7. Using the Service Processor .......................363

Service Processor Menus .............................363

Accessing the Service Processor Menus Locally ...................363

Accessing the Service Processor Menus Remotely...................364

Saving and Restoring Service Processor Settings ...................364

Menu Inactivity ................................364

General User Menu ...............................364

Privileged User Menus ..............................365

Main Menu .................................365

Service Processor Setup Menu ..........................367

Passwords .................................367

System Power Control Menu ...........................372

System Information Menu ............................376

Language Selection Menu ............................385

Call-In/Call-Out Setup Menu ...........................386

Modem Configuration Menu ...........................387

Serial Port Selection Menu ...........................387

Serial Port Speed Setup Menu ..........................388

Telephone Number Setup Menu..........................388

Call-Out Policy Setup Menu ...........................389

Customer Account Setup Menu ..........................390

Call-out Test Menu ..............................390

Service Processor Parameters in Service Mode (Full System Partition) ............391

System Power-On Methods ............................391

Service Processor Reboot/Restart Recovery ......................392

Boot (IPL) Speed ...............................392

Failure During Boot Process ...........................392

Failure During Normal System Operation ......................392

Service Processor Reboot/Restart Policy Controls ...................392

Firmware Updates................................393

General Information on System Firmware Updates ...................394

Determining the Level of Firmware on the System ...................395

System Firmware Update in AIX Using a Locally Available Image .............396

Updating System Firmware From the Service Processor Menus ..............397

Updating System Firmware from the AIX Service Aids .................397

Updating System Firmware from a NIM Server ....................398

Recovery Mode................................398

Updating System Firmware from the AIX Command Line ................398

Configuring and Deconfiguring Processors or Memory ..................398

Run-Time CPU Deconfiguration (CPU Repeat Gard) ..................399

Service Processor System Monitoring - Surveillance ...................399

System Firmware Surveillance ..........................399

Operating System Surveillance ..........................399

Call-Out (Call-Home) ...............................400

Console Mirroring ................................401

System Configuration .............................401

Service Processor Error Logs ...........................402

LCD Progress Indicator Log ............................403

Service Processor Operational Phases ........................404

Pre-Standby Phase ..............................404

Standby Phase ................................404

Bring-Up Phase ...............................405

Runtime Phase ................................406

vi Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Chapter 8. Using System Management Services ...................407

Select Language ................................408

Change Password Options ............................409

View Error Log .................................409

Setup Remote IPL (Initial Program Load) .......................410

Change SCSI Settings ..............................413

Select Console .................................413

Select Boot Options ...............................414

Select Boot Devices ...............................416

Display Current Settings .............................418

Restore Default Settings .............................419

Multiboot Startup ................................419

Exiting System Management Services ........................419

Chapter 9. Removal and Replacement Procedures...................421

Color Coded Indicators ..............................422

Procedure List .................................422

Handling Static-Sensitive Devices ..........................423

Stopping and Starting Your System .........................424

Stopping the System without an HMC Attached ....................424

Stopping the System with an HMC Attached and AIX Installed ..............424

Stopping the System with an HMC Attached and Linux Installed ..............425

Starting the System without an HMC Attached ....................425

Starting the System with an HMC Attached .....................426

Model 6C4 Drawer-Release Latch and Brackets.....................427

Drawer-Release Latch Removal..........................427

Drawer-Release Latch Replacement ........................428

Drawer-Release Latch Bracket Removal ......................428

Drawer-Release Latch Bracket Replacement .....................429

Placing the Model 6C4 into the Service Position.....................429

Returning the Model 6C4 to the Operating Position ...................430

Covers ....................................431

Service Access Cover Removal (Model 6C4) .....................431

Service Access Cover Replacement (Model 6C4) ...................431

Top Cap Removal (Model 6E4) ..........................432

Top Cap Replacement (Model 6E4) ........................432

Top Cover Removal (Model 6E4) .........................433

Top Cover Replacement (Model 6E4)........................434

Outer Side Cover Removal (Model 6E4) ......................435

Outer Side Cover Replacement (Model 6E4) .....................435

Service Access Cover Removal (Model 6E4) .....................436

Service Access Cover Replacement (Model 6E4) ...................437

Back Cover Removal (Model 6E4) .........................437

Back Cover Replacement (Model 6E4) .......................438

Disk Drive Access Cover Removal (Model 6E4) ....................438

Disk Drive Access Cover Replacement (Model 6E4) ..................438

Right Side Cover (System Base) Removal (Model 6E4) .................439

Right Side Cover (System Base) Replacement (Model 6E4) ...............440

Bezel Door (Model 6E4) .............................441

Bezel Door Removal ..............................441

Bezel Door Replacement ............................441

Bezels ....................................442

Front Bezel Removal (Model 6C4) .........................442

Front Bezel Replacement (Model 6C4) .......................442

Front Bezel Removal (Model 6E4) .........................443

Front Bezel Replacement (Model 6E4) .......................443

Contents vii

PCI Adapters .................................444

PCI Hot-Plug Manager Access ..........................444

Non-Hot-Pluggable PCI Adapter Removal ......................446

Adding or Replacing a Non-Hot-Pluggable PCI Adapter .................448

Hot-Pluggable PCI Adapter Removal ........................450

Replacing a Hot-Pluggable PCI Adapter .......................453

Installing a Hot-Pluggable PCI Adapter .......................457

Fans.....................................460

Removing a Processor Fan in a Non-Hot-Swap Environment ...............460

Replacing a Processor Fan in a Non-Hot-Swap Environment ...............461

Hot-Swap Fan Assembly Removal .........................462

Model 6C4 Fan Assembly ............................463

Model 6E4 Fan Assembly ............................464

Hot-Swap Fan Assembly Replacement .......................464

Media Drives (Diskette, CD-ROM, Tape, or Disk Drive) ..................466

Media Removal................................466

Model 6C4 Media Drive.............................467

Model 6E4 Media Drive .............................468

Media Replacement ..............................469

Hot-Plug Disk Drives ...............................470

Deconfiguring (Removing) or Configuring a Disk Drive .................470

Deconfiguring (Removing) ............................470

Configuring (Replacing) .............................471

Hot-Plug Disk Drive Removal ..........................471

Hot-Plug Disk Drive Replacement .........................473

PCI Riser Card .................................474

PCI Riser Card Removal ............................474

PCI Riser Card Replacement...........................478

Disk Drive Backplane ..............................480

Disk Drive Backplane Removal ..........................480

Disk Drive Backplane Replacement ........................483

Operator Panel .................................484

Operator Panel Removal ............................484

Model 6C4 Operator Panel ...........................484

Model 6E4 Operator Panel ...........................485

Operator Panel Replacement...........................485

System Vital Product Data (VPD) Update Procedure ...................486

Processor Card.................................488

Processor Card Removal ............................488

Adding or Replacing a Processor Card .......................490

Memory DIMMs ................................492

Memory DIMM Removal ............................492

Memory DIMM Replacement ...........................496

Replacing the Battery ..............................497

Power Supplies.................................501

Non-Hot-Swap Power Supply Removal .......................501

Non-Hot-Swap Power Supply Replacement .....................503

Hot-Swap Power Supply Removal .........................504

Hot-Swap Power Supply Replacement .......................506

Central Electronics Complex (CEC) Backplane .....................508

CEC Backplane Removal ............................508

CEC Backplane Replacement ..........................513

Chapter 10. Parts Information ...........................515

System Parts .................................516

System Parts (continued) ............................518

viii Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Model 6E4 Cover Set and Brackets .........................520

System Internal Cables ..............................523

Power Cable ..................................526

Keyboards and Mouse (White) ...........................527

Keyboards and Mouse (Black) ...........................528

Chapter 11. SRNs for Linux............................529

Chapter 12. Fault and Attention LEDs........................543

Operator Panel Display ..............................543

Component LEDs ................................544

Resetting the LEDs ..............................547

Appendix A. Environmental Notices ........................549

Product Recycling and Disposal...........................549

Environmental Design ..............................553

Acoustical Noise Emissions ............................554

Declared Acoustical Noise Emissions .........................554

Appendix B. Notices ..............................555

Appendix C. Service Processor Setup and Test ....................557

Service Processor Setup Checklist..........................557

Testing the Setup ................................558

Testing Call-In ................................558

Testing Call-Out ...............................558

Serial Port Configuration ............................559

Appendix D. Setting Up the System Rack ......................561

Rack Specifications ...............................561

7014 Model T00 and T42 Rack ..........................561

Noise Emission Notes .............................562

System Service Clearances ...........................563

Model 6C4 Rack Installation Inventory ........................563

Read the Rack Safety Instructions ..........................566

Rack Safety Instructions ............................566

Attaching the Mounting Hardware to the Rack Enclosure .................567

System Rail Assembly (Type 1) ..........................573

System Rail Assembly (Type 2) ..........................576

Removal and Installation of the Model 6C4 into a Rack ..................579

System Drawer Removal ............................579

Installing the Model 6C4 into the Rack Enclosure ...................580

Installing the RIO-2 Cable Support Bracket ......................584

Installing the Cable-Management Arm ........................586

Appendix E. Installing a Hardware Management Console (HMC) .............587

Position the HMC and Monitor ...........................587

Connect the Cables ...............................588

Connect the 8-Port Adapter Cables .........................590

Connect the External Modem ...........................590

Check the Microswitch Setting on the Modem ....................591

Connect the LAN Cable (If Applicable) ........................592

Plug in the HMC Power Cable ...........................592

Configure the Network ..............................592

Configure Inventory Scout Services .........................592

Collect Vital Product Data Information .......................593

Contents ix

Configure the Service Agent ............................594

Appendix F. Modem Configurations ........................597

Sample Modem Configuration Files .........................597

Configuration File Selection ............................597

Transfer of a Modem Session ...........................601

Modem Configuration Sample Files .........................603

Index ....................................619

x Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

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 105 v 106 v 421 v 501

A caution notice indicates the presence of a hazard that has the potential of causing moderate or minor personal injury. Caution notices appear on the following pages:

v xii v xii v 105 v 421

Note: For a translation of these notices, see System Unit Safety Information, order number SA23-2652.

Rack Safety Instructions

v Do not install this unit in a rack where the internal rack ambient temperatures will exceed 35 degrees C. v Do not install this unit in a rack where the air flow is compromised. Any side, front or back of the unit

used for air flow through the unit must not be in direct contact with the rack. v Care should be taken to ensure that a hazardous condition is not created due to uneven mechanical

loading when installing this unit in a rack. If the rack has a stabilizer it must be firmly attached before

installing or removing this unit. v Consideration should be given to the connection of the equipment to the supply circuit so that

overloading of circuits does not compromise the supply wiring or overcurrent protection. To provide the

correct power connection to the rack, refer to the rating labels located on the equipment in the rack to

determine the total power requirement for the supply circuit. v An electrical outlet that is not correctly wired could place hazardous voltage on the metal parts of the

system or the devices that attach to the system. It is the responsibility of the customer to ensure that

the outlet is correctly wired and grounded to prevent an electrical shock.

Rack Safety Instructions

v Do not install this unit in a rack where the internal rack ambient temperatures will exceed 35 degrees C. v Do not install this unit in a rack where the airflow is compromised. Any side, front or back of the unit

used for air flow through the unit must not be in direct contact with the rack.

v Care should be taken to ensure that a hazardous condition is not created due to uneven mechanical

loading when installing this unit in a rack. If the rack has a stabilizer it must be firmly attached before installing or removing this unit.

v Consideration should be given to the connection of the equipment to the supply circuit so that

overloading of circuits does not compromise the supply wiring or overcurrent protection. To provide the correct power connection to the rack, refer to the rating labels located on the equipment in the rack to determine the total power requirement for the supply circuit.

v An electrical outlet that is not correctly wired could place hazardous voltage on the metal parts of the

system or the devices that attach to the system. It is the responsibility of the customer to ensure that the outlet is correctly wired and grounded to prevent an electrical shock.

Electrical Safety

Observe the following safety instructions any time you are connecting or disconnecting devices attached to the workstation.

In the system you are about to setup or service:

v The ac power interface connector is considered the main power disconnect device. v This system has redundant power supply capabilities, meaning that it has the ability to have two power

supplies running simultaneously in the same system unit. When instructed to disconnect the power source, ensure that all power cables have been unplugged.

DANGER

To prevent electrical shock hazard, disconnect all power cables from the electrical outlet before relocating the system.

D01

CAUTION: This product is equipped with a three-wire power cable and plug for the user’s safety. Use this power cable with a properly grounded electrical outlet to avoid electrical shock.

C01

DANGER

To prevent electrical shock hazard, disconnect all power cables from the electrical outlet before relocating the system.

D01

Laser Safety Information

CAUTION: This product may contain a CD-ROM, DVD-ROM, or laser module on a PCI card, which are class 1 laser products.

C30

xii Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Laser Compliance

All lasers are certified in the U.S. to conform to the requirements of DHHS 21 CFR Subchapter J for class 1 laser products. Outside the U.S., they are certified to be in compliance with the IEC 825 (first edition

1984) as a class 1 laser product. Consult the label on each part for laser certification numbers and approval information.

CAUTION: All mentioned laser modules are designed so that there is never any human access to laser radiation above a class 1 level during normal operation, user maintenance, or prescribed service conditions. Data processing environments can contain equipment transmitting on system links with laser modules that operate at greater than class 1 power levels. For this reason, never look into the end of an optical fiber cable or open receptacle. Only trained service personnel should perform the inspection or repair of optical fiber cable assemblies and receptacles.

C25, C26

Safety Notices xiii

xiv Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Data Integrity and Verification

IBM computer systems contain mechanisms designed to reduce the possibility of undetected data corruption or loss. This risk, however, cannot be eliminated. Users who experience unplanned outages, system failures, power fluctuations or outages, or component failures must verify the accuracy of operations performed and data saved or transmitted by the system at or near the time of the outage or failure. In addition, users must establish procedures to ensure that there is independent data verification before relying on such data in sensitive or critical operations. Users should periodically check the IBM support websites for updated information and fixes applicable to the system and related software.

xvi Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

About This Book

This book provides maintenance information that is specific to the Eserver pSeries 630 Model 6C4 and Model 6E4, 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. In this book, the pSeries 630 Model 6C4 and Model 6E4 are hereafter referred to as the system.

MAPs that are common to all systems are contained in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

This book is used by the service representative to repair system failures. This book assumes that the service representative has had training on the system.

ISO 9000

ISO 9000 registered quality systems were used in the development and manufacturing of this product.

Highlighting

The following highlighting conventions are used in this book:

Bold Identifies commands, subroutines, keywords, files, structures, directories, and other items

whose names are predefined by the system. Also identifies graphical objects such as buttons, labels, and icons that the user selects.

Italics Identifies parameters whose actual names or values are to be supplied by the user.

Monospace Identifies examples of specific data values, examples of text similar to what you might see

displayed, examples of portions of program code similar to what you might write as a programmer, messages from the system, or information you should actually type.

Accessing Information

Documentation for the IBM Eserver pSeries is available online. Visit the IBM Eserver pSeries Information Center at http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base.

v To access the pSeries publications, click Hardware documentation. v To view information about the accessibility features of Eserver pSeries hardware and the AIX operating

system, click AIX and pSeries accessibility.

References to AIX Operating System

Note: This document may contain references to the AIX operating system. If you are using another

operating system, consult the appropriate documentation for that operating system.

This document may describe hardware features and functions. While the hardware supports them, the implementation of these features and functions depends upon support from the operating system. AIX provides this support. If you are using another operating system, consult the appropriate documentation for that operating system regarding support for those features and functions.

xvii

Related Publications

The following publications provide additional information about your system: v The Eserver pSeries 630 Model 6C4 and Model 6E4 Installation Guide, order number SA38-0605,

contains information on how to set up and cable the system, install and remove options, and verify system operation.

v The Eserver pSeries 630 Model 6C4 and Model 6E4 User’s Guide, order number SA38-0606, contains

information to help users use the system, use the service aids, and solve minor problems.

v The D20 I/O Drawer Installation Guide, order number SA23-1296, contains information on how to set

up, cable, install and remove options, and verify the subsystem operations.

v The pSeries 7311 Model D10 and Model D20 Service Guide, order number SA38-0627, contains

reference information, maintenance analysis procedures (MAPs), error codes, removal and replacement procedures, and a parts catalog.

v The RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems, order number

SA38-0509, contains diagnostic information, service request numbers (SRNs), and failing function codes (FFCs).

v The RS/6000 Eserver pSeries Adapters, Devices, and Cable Information for Multiple Bus Systems,

order number SA38-0516, contains information about adapters, devices, and cables for your system. This manual is intended to supplement the service information found in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

v The IBM Hardware Management Console for pSeries Installation and Operations Guide, order number

SA38-0590, contains information on how to set up a hardware management console and how to use it to manage a system.

v The IBM Hardware Management Console for pSeries Maintenance Guide, order number SA38-0603,

contains information about servicing your HMC, and includes diagnostic and error information.

v The Site and Hardware Planning Guide, order number SA38-0508, contains information to help you plan

your installation.

v The System Unit Safety Information, order number SA23-2652, contains translations of safety

information used throughout this book.

v The PCI Adapter Placement Reference, order number SA38-0538, contains information regarding slot

restrictions for adapters that can be used in this system.

Trademarks

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:

v AIX v Electronic Service Agent v Eserver v IBM v LANstreamer v POWER4 v POWER4+ v pSeries v Service Director v SP

Other company, product, and service names may be trademarks or service marks of others.

xviii Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Chapter 1. Reference Information

This chapter provides an overview of the system, including a logical description and a physical overview. The following additional details pertaining to the system are also provided:

v Memory overview and placement v General description of the operator panel v Cabling rules v System location rules and descriptions v Power flow v Data flow

Overview

The pSeries 630 Model 6C4 and Model 6E4 have similar operational capabilities but are packaged differently.

The Model 6E4 is a deskside system while the Model 6C4 is a 4 EIA-unit drawer designed to be housed in a 19-inch rack. Both models can be configured as a 1-way to 4-way symmetric multiprocessing (SMP) system; each can have up to 4 hot-plug disk drives and 6 hot-plug PCI adapters. Both models support redundant hot-plug power supplies as well as hot-pluggable PCI adapters.

Power is provided through ac power cords. Either model can be set up to use 100-127 V ac or 200-240 V ac power.

The two media bays can be used to accommodate any of the following drives:

v SCSI DVD-RAM drive v IDE DVD-ROM drive v IDE CD-ROM drive v Diskette drive (special mounting carriage needed) v Tape drive

Note: A CD-ROM is recommended for use in the base configuration of either model.

System Features

Bus Architecture

Depending on your system configuration, four or six PCI-X slotted riser cards are available. The slots are 64-bit capable at 133 MHz, 3.3 volts. If your system has four PCI-X slots, use slots 3 and 4 with PCI adapters that require high performance. Use slots 1 and 2 with PCI adapters that do not require high performance. On the six-slotted PCI riser cards, all slots are equal. All slots are capable of using the full-length PCI-X adapters. The PCI-X slots are numbered on the rear of the chassis, from left to right.

When equipped with POWER4+ processors and a six-slotted PCI riser card, the Model 6C4 and Model 6E4 include six hot-plug PCI-X slots, dual integrated Ultra3 SCSI controllers, dual 10/100 Mbps integrated Ethernet controllers, and four front-accessible disk bays supporting hot-swappable disks. These disk bays can accommodate up to 587.2 GB of disk storage using 146.8 GB Ultra3 SCSI disk drives. Two media bays are used for a CD-ROM, DVD-RAM, DVD-ROM, or another optional media device, such as a tape or diskette drive. The Converged Service Processor (CSP), including system power control, is also integrated, along with the native I/O functions such as serial ports, keyboard, and mouse. Also included are an enhanced I/O subsystem with the implementation of the remote I/O (RIO) interconnect and PCI-X bus protocols.

The Model 6C4 can support up to two high-density 7311 Model D20 I/O drawers to provide additional PCI-X slots and disk drive bays. A fully configured system with two I/O drawers has 20 PCI-X slots and 4.1 TB of disk space. Optionally redundant hot-plug cooling fans and power supplies are available.

All PCI-X slots can run either 64-bit or 32-bit adapters. However, a 32-bit adapter operates in a 32-bit mode and shows no performance advantage while running in a 64-bit slot. The following illustration shows the PCI adapter slot locations when viewing from the rear of the system.

1 Model 6C4 Using a 4-Slotted PCI

Riser Card

2 Model 6C4 Using a 6-Slotted PCI

Riser Card

2 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

3 Model 6E4 Using a 4-Slotted PCI

Riser Card

4 Model 6E4 Using a 6-Slotted PCI

Riser Card

Processor Cards

The Model 6C4 and Model 6E4 have two processor types and three processor speeds from which to choose.

The GP processor has a processing speed of 1.0 GHz, while the GQ processors have a processing speed of either 1.2 GHz or 1.45 GHz.

Use only processor cards of the same type and speed when adding, replacing, or upgrading processor cards in your system.

Processor cards can be configured in any one of following combinations:

v One 1-way processor card v Two 1-way processor cards v One 2-way processor card v Two 2-way processor cards

Notes:

1. Feature conversions are available for upgrading from a 1-way to a 2-way processor and when

upgrading from a POWER4 to POWER4+ processor.

2. The processor feature conversions must be performed by a service representative.

Memory

v 1 GB to 32 GB ECC (error code correction) DDR (double data rate) SDRAM (synchronous dynamic

random-access memory).

v Memory DIMMs plug into the processor cards (8 DIMM slots per card). v DIMMs must be populated in quads (four DIMMs). A memory feature consists of a quad. Additional

quads can consist of any memory size. v A system with a single processor card (1-way or 2-way) can have a maximum of 16 GB of memory.

Media Drives

Typical system configuration consists of two media bays. One of the media bays can be configured with either an IDE CD-ROM or an IDE DVD-ROM.

v Media bay 1 can accommodate an IDE CD-ROM or IDE DVD-ROM. v Media bay 2 can accommodate a SCSI DVD-RAM, diskette drive, or tape drive.

Note: The SCSI DVD-RAM can read CD-ROM installation media.

The following media drives are available for the Model 6C4 and Model 6E4.

– Diskette drive

– DVD-RAM drive (4.7 GB capacity)

– 650 MB IDE 48x CD-ROM drive

– 4.7 GB IDE 16x/48x DVD-ROM drive

– 80/160 GB VXA tape drive

– 8 mm 60/150 GB tape drive

– 4 mm 20/40 GB tape drive

Chapter 1. Reference Information 3

Hot-Pluggable Disk Drives

Four hot-pluggable disk-drive bays:

v 18.2 GB to 587.2 GB of disk storage v The following disk-drive sizes and speeds are available:

– 18.2 GB Ultra3 10K RPM 1 inch – 36.4 GB Ultra3 10K RPM 1 inch – 73.4 GB Ultra3 10K RPM 1 inch – 146.8 GB Ultra3 10K RPM 1 inch – 36.4 GB Ultra3 15K RPM 1 inch – 73.4 GB Ultra3 15K RPM 1 inch – 146.8 GB Ultra3 15K RPM 1 inch

I/O Expansion Drawer

Expansion is provided by adding additional 7311 Model D20 I/O drawers (up to two) for the Model 6C4. The Model D20 provides additional PCI-X slots and disk drive bays for the Model 6C4.

v Seven hot-plug PCI-X slots, 64-bit, 133 MHz, 3.3 volt v Up to 12 hot-pluggable disk drive bays

The optional disk backplane consists of two 6-pack disk bays and requires SCSI cables to connect a required Ultra3 SCSI PCI adapter or Ultra3 SCSI RAID adapter in slot 7 to each of the 6-packs, or two SCSI adapters (one in slot 4 and one in slot 7 of the I/O drawer).

Power Supplies

Up to two power supplies maximum per system; the second power supply is for redundant power.

v AC input type 100-127 V ac or 200-240 V ac v Single phase v Frequency = 47 Hz - 63 Hz

Keyboard

v Standard: 101-key enhanced keyboard v 101/102 or 106-key enhanced keyboard is also available

Mouse

v Three-button

4 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Operator Panel

v 32-character LED diagnostics display v LEDs for power on, attention, SCSI activity, and LAN activity v Buttons for power on, system reset, and service processor reset switch:

System Reset Button

Dumps AIX (if dump is enabled) and reboots

Service Processor Reset Switch

Resets the service processor (into standby mode). The service processor reset switch is the pinhole located on the operator panel above the system reset button.

Input/Output Ports

v One 25-pin parallel port (The parallel port is not accessible when in partitioned mode.) v Keyboard v Mouse v Two Ultra3 SCSI (one external Ultra3 SCSI (with VHDCI 4 mini 68-pin port), and one internal Ultra3

SCSI disk drive backplane). VHDCI may require a mini 68-pin connector or FC 2118 mini 68-pin to

68-pin 0.3 meter cable as an additional feature.

v Integrated Drive Electronics (IDE) v Two System Power Control Network (SPCN) Connectors v Two RIO Connectors v Two 10/100 Ethernet (IEEE 802.3 compliant) v Three serial. Serial port 1 (S1) has two physical connectors, one RJ-48 connector located in front on the

operator panel, and a 9-pin D-shell connector located on the rear of the chassis. The use of the front

port disables the rear S1 port.

1 Serial Port 1 Connector 3 Serial Port 3 Connector

1a Serial Port 1 Front Connector (RJ-48) 4 Parallel Connector

2 Serial Port 2 Connector

Chapter 1. Reference Information 5

Current usage for the serial port connectors are as follows:

Serial Port Number Location Examples of Applicable Usage

Serial Port 1 (S1 Front)

Serial Port 1 (S1 Rear)

Serial Port 2 (S2) Rear of the System Service Processor menus, HACMP, ASCII terminal for the operating

Serial Port 3 (S3) Rear of the System HACMP, UPS (uninterruptible power supply), ASCII terminal for the

Operator Panel Service Agent, PDA system management applications (for example,

handheld devices, laptop systems), Service Processor menus, ASCII terminal for the operating system console, and modems

Rear of the System Service Processor menus, Service Agent, PDA system management

applications (interface cable required), ASCII terminal for the operating system console, and modems

system console, and modems

operating system console, and modems

Notes:

1. Serial port 1 is never used to run HACMP or attach a UPS. If you are configuring your system to run

HACMP with a UPS attached, you must connect the HACMP cable to serial port 2 and the UPS cable to serial port 3. Do not run UPS connected to serial port 2. If you disconnect HACMP, you must reset the service processor using the pinhole reset switch before running another application. The service processor pinhole reset switch is located on the operator panel.

2. A modem can be attached to any of the serial ports.

Security Features

On the Model 6C4 and Model 6E4, you can set the following types of passwords to limit access to these systems:

v General-access password - set only from the service processor menus. It provides limited access to the

service processor menus and is usually available to all users who are allowed to power on the system.

v Privileged-access password - Set from the service processor menus or from System Management

Services (SMS) utilities. Used by the system administrator or root user and allows access to all service processor functions.

Hardware Management Console (HMC)

The Hardware Management Console (HMC) is an optional feature that allows you to manage configuration and operation of partitions in a system, as well as add and remove hardware without interrupting system operation.

In this book, a system that is managed by the HMC is referred to as the managed system. The HMC uses its serial connection to the managed system to perform various functions. The HMC’s main functions include the following:

v Detecting, reporting, and storing changes in hardware conditions v Acting as a service focal point for service representatives to determine an appropriate service strategy

Service representatives use the Service Focal Point application on the HMC to start and end their service calls. Service Focal Point provides service representatives with serviceable event information, vital product data (VPD), and diagnostic information.

The HMC is a closed system. Additional applications cannot be loaded on the HMC. All the tasks needed to maintain the platform, the underlying operating system, and the HMC application code are available by using the HMC’s management applications.

6 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Powering the System on and Off

For procedures to power off and power on the system for various system configurations and operating systems, see “Stopping and Starting Your System” on page 424.

Console

Note: This section applies to a system that does not have an HMC attached.

The firmware starts a console-selection sequence at system boot time if any of the following is true:

v A console has not yet been selected. v A previous console-selection sequence timed out. v A change in the system configuration affects the console (for example, keyboard installed or removed,

mouse installed or removed, graphics adapter installed/removed or moved to another PCI slot).

The console-selection sequence allows you to select (from the appropriate input device) any one of the available console devices. If no console is selected within approximately 60 seconds, serial port 1 (S1) is selected as the console and the selection sequence times out.

Attention: If an ASCII terminal is attached to serial port 1 (S1), and there is any interaction with this terminal:

v After OK displays in the operator panel

AND v Before the power-on sequence is initiated

the firmware will use this terminal as the console, regardless of the previous console selection.

After a console has been selected, the console-selection sequence is started at boot time only if there is a change in the system configuration (as previously described), or the contents of the system’s nonvolatile memory (NVRAM) are lost.

Note: Moving an ASCII terminal from one serial port to another (from S1 to S2) cannot be detected by the

firmware, so it does not constitute a configuration change.

You can also initiate a system console-selection sequence from the SMS menus.

Power-On Self-Test

After power is turned on and before the operating system is installed, the system does a power-on self-test (POST). This test performs checks to ensure that the hardware is functioning correctly before the operating system is installed. During the POST, a POST screen displays, and POST indicators appear on the firmware console (if one is connected). The next section describes the POST indicators and functions that can be accessed during the POST.

POST Indicators

POST indicators indicate tests that are being performed as the system is preparing to load the operating system. The POST indicators are words that display on the system console. Each time that the system starts a different step in the POST, a POST indicator word appears on the console. Each word is an indicator of the tests that are being performed.

Chapter 1. Reference Information 7

The POST screen displays the following words:

Memory Memory test

Keyboard Initialize the keyboard and mouse. The time period for pressing a key to access the

System Management Services, or to initiate a service mode boot is now open. See “POST Keys” for more information.

Network Self-test on network adapters

SCSI Adapters are being initialized

Speaker Sounds an audible tone at the end of POST

POST Keys

The POST keys, if pressed after the keyboard POST indicator displays and before the last POST indicator speaker displays, cause the system to start services or to initiate service mode boots used for configuring

the system and diagnosing problems. The keys are described below:

Note: The program function keys (F1-F12) on a keyboard attached to the CEC drawer are not used and

will be ignored. After the keyboard POST indicator displays, you must use the numeric number keys.

1 Key

The numeric 1 key, when pressed during POST, starts the System Management Services (SMS) interface.

5 Key

The numeric 5 key, when pressed during POST, initiates a system boot in service mode using the default service mode boot list.

This mode attempts to boot from the first device of each type found in the list. It does not search for other bootable devices of that type if the first device is not bootable. Instead, it continues to the next device type in the list. The firmware supports up to five entries in the boot list.

Note: This is the preferred method of loading standalone diagnostics from CD-ROM.

The default boot sequence is:

1. Diskette (if installed)

2. CD-ROM (if installed)

3. Hard file

4. Tape drive (if installed)

5. Network a. Token ring b. Ethernet

6 Key

The numeric 6 key works like the numeric 5 key, except that firmware uses the customized service mode bootlist that was set up in the AIX service aids.

Note: This is the preferred method of loading online diagnostics from the boot hard disk.

8 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

System Unit Locations

Model 6C4 Front View

1 Operator Panel 4 Media Bay 2 Front Serial Port 5 Hot-Plug Disk Drives 3 CD-ROM Drive (optional)

Model 6C4 Rear View

1 PCI-X Slot Access 11a RIO-2 0 Connector 2 Redundant Power Cable Receptacle 11b RIO-2 1 Connector 3 Primary Power Cable Receptacle 12 Serial Connector 2 4 System Power Control Network Connector

SPCN2

5 System Power Control Network Connector

SPCN1

6 Parallel Connector 15 Mouse Connector 7 Hardware Management Console Connector

HMC2

8 Hardware Management Console Connector

HMC1

9 Ethernet Connector 1 18 External SCSI Connector

10 Ethernet Connector 2

13 Serial Connector 3

14 Serial Connector 1

16 Keyboard Connector

17 Rack Indicator

Chapter 1. Reference Information 9

Model 6E4 Front View

1 Operator Panel 4 Media bay 2 Front Serial Connector 5 Hot-Plug Disk Drives 3 CD-ROM Drive

10 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Rear View

1 PCI-X Slot Access 10 Ethernet Connector 2 2 Redundant Power Cable Receptacle 11 RIO Connector Cover 3 Primary Power Cable Receptacle 12 Serial Connector 2 4 System Power Control Network Connector

SPCN2

5 System Power Control Network Connector

SPCN1

6 Parallel Connector 15 Mouse Connector 7 Hardware Management Console Connector

HMC2

8 Hardware Management Console Connector

HMC1

9 Ethernet Connector 1 18 External SCSI Connector

13 Serial Connector 3

14 Serial Connector 1

16 Keyboard Connector

17 Rack Indicator

Chapter 1. Reference Information 11

Power Supply Locations

Model 6C4

1 Power Supply #1 (Primary) 3 AC Good LED (Green) 2 Power Supply #2 (Redundant) 4 DC Good LED (Green)

12 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

5 Fault LED (Amber)

Model 6E4

1 Power Supply #2 (Redundant) (Front

View)

2 Power Supply #1 (Primary) (Front

View)

3 Fault LED (Amber) 7 Primary Power Supply (Rear View) 4 DC Good LED (Green)

Note: The preceding illustration does not show the LEDs located on the top of the power supplies. For location

references, see the illustration on page 12 showing the power supplies for the Model 6C4.

5 AC Good LED (Green)

6 Redundant Power Supply (Rear View)

Chapter 1. Reference Information 13

Fan Locations

The following illustration identifies the system cooling fans. The fans have an amber LED located on top of the housing. A lit amber LED indicates that the fan is not operating correctly.

The power supplies have two groups of three LEDs located on the front and top. The amber LED on the power supply indicates a problem with the power supply. If a power supply is diagnosed with a cooling problem, the entire power supply must be replaced.

1 Processor Card Cooling Fan (Primary Fan

#1 )

2 Processor Card Cooling Fan (Redundant

Fan #2)

3 PCI Adapter Cooling Fan (Fan #4)

4 PCI Adapter Cooling Fan (Fan #3)

5 Stacked Power Supply Cooling Fans

Note: The preceding illustration does not show the two cooling fans integrated into each power supply.

14 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

CEC Backplane Locations

The following illustration of the CEC backplane identifies the primary connectors used in your system.

1 CEC Backplane 17 Serial Port #3 Connector

2 Power Supply #1 (Primary) Connectors 18 Mouse

3 Power Supply #2 (Redundant) Connectors 19 Keyboard

4 SPCN1 Connector 20 Rack Indicator Connector

5 SPCN2 Connector 21 PCI Riser Card Connectors

6 HMC2 Connector 22 Battery Connector

7 Parallel Port Connector 23 For Manufacturing Use Only

8 HMC1 Connector 24 PCI Cooling Fan #3 and #4 Connector

9 Ethernet #1 Connector 25 IDE CD-ROM Signal Connector

10 Ethernet #2 Connector 26 Diskette Drive Signal Connector

11 Connector RIO-2 1 Connector 27 Diskette Drive Power Connector

12 Processor Cooling Fan #1 Connector

(Primary Fan)

13 Processor Cooling Fan #2 Connector

(Redundant Fan)

14 Connector RIO-2 0 Connector 30 Processor Card #2 Connector

15 Serial Port #2 Connector 31 For Manufacturing Use Only

16 Serial Port #1 Connector 32 Operator Panel Connector

28 Media Power Connector

29 Disk Drive Backplane Power Connector

33 Processor Card #1 Connector

Chapter 1. Reference Information 15

PCI Riser Card Locations

The PCI card has two integrated SCSI controllers. One SCSI controller (PCI, 64-bit) is an SYM53C1010 that operates at 66MHz and has dual LVD (low voltage differential) ports. The other is a 53C875, SE-SCSI controller and is only available on the six-slotted PCI riser card. The internal port from SCSI controller SYM53C1010 connects to the DASD board through a 68-pin SCSI cable. The port from the SE-SCSI controller is available only on the six-slotted PCI riser card, and connects to the media bay through a 68-pin SCSI cable.

All PCI-X slots can run either 64-bit or 32-bit adapters. However, a 32-bit adapter operates in a 32-bit mode and shows no performance advantage while running in a 64-bit slot.

The following illustrations show the PCI adapter slot locations when viewing from the rear of the system.

1 Model 6C4 Using a 4-Slotted PCI-X

Riser Card

2 Model 6C4 Using a 6-Slotted PCI-X

Riser Card

3 Model 6E4 Using a 4-Slotted PCI-X

Riser Card

4 Model 6E4 Using a 6-Slotted PCI-X

Riser Card

16 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

The following illustrations show the connector and slot locations on the four-slotted PCI riser card and six-slotted PCI riser card, respectively.

Four-Slotted PCI Riser Card

1 PCI Slot 1 7 4-Slotted PCI Riser Card

2 PCI Slot 2 8 ″Push″ Labels

3 PCI Slot 3 9 Internal Disk Drive SCSI Connector (for internal

disk drive use only)

4 PCI Slot 4 10 External SCSI Connector

5 Manufacturing Use Only 11 Removal Sling

6 Riser Card to CEC Backplane Standoff

Connectors (Quantity 4) located on the underside of the PCI Riser Card

12 Riser Card to Disk Drive Backplane Signal

Connector

Six-Slotted PCI Riser Card

1 PCI Slot 1 9 6-Slotted PCI Riser Card

2 PCI Slot 2 10 ″Push″ Labels

3 PCI Slot 3 11 Internal Disk Drive SCSI Connector (for internal

4 PCI Slot 4 12 Single-Ended SCSI to Media Connector

5 PCI Slot 5 13 External SCSI Connector

6 PCI Slot 6 14 Removal Sling

7 Manufacturing Use Only 15 Riser Card to Disk Drive Backplane Signal

8 Riser Card to CEC Backplane Standoff

Connectors (Quantity 4) located on the underside of the PCI Riser Card

disk drive use only)

Connector

Chapter 1. Reference Information 17

Memory DIMM Location

The memory DIMMs used in the pSeries 630 Model 6C4 and Model 6E4 are located on the processor card. Your system contains either one or two processor cards, each card with 8 memory DIMM slots. Associated with each memory DIMM slot is an LED, which is located on the edge of the processor card. A lit LED indicates a problem with a specific memory DIMM. The following rules must be followed when removing or installing memory DIMMs:

v Memory DIMMs must be installed in quads. However, you do not need to install four new DIMMs in a

quad when you have a memory problem. Swap out each DIMM, starting the system after each change, until the faulty DIMM has been replaced.

Note: A quad is a group of four memory DIMMs. Each memory DIMM in a quad must be the same type

and size. However, both quads on the same processor card are not required to be the same.

v The system must have at least four memory DIMMs installed (one quad). v The quad slot combinations are 1, 3, 6, and 8 (or 2, 4, 5, and 7).

Note: 1, 3, 6, and 8 (or 2, 4, 5, and 7) combinations are the only slot combinations recognized by the

system.

v On a two-processor-card system, either processor card can be populated with memory.

Note: A processor card containing no memory is still functional. (For example, a system containing two

processor cards has all of its memory installed on processor card 1, and no memory installed on processor card 2. Processor card 2 has no memory-storage capacity, but functions as a processor card.)

The following are valid memory configurations for one and two processor cards:

Number of Processor Cards Allowable Memory Configurations

1 Processor Card 1 GB through 16 GB installed in quads of 256 MB DIMMs

to 2 GB DIMMs

2 Processor Cards 1 GB through 32 GB installed in quads of 256 MB DIMMs

to 2 GB DIMMs

Note: The maximum amount of system memory varies by model.

The following processor card illustration shows the memory DIMM slot locations, as well as the LED location associated with each memory DIMM slot.

1 Memory Module Slot 1 (J2A) 6 Memory Module Slot 6 (J1A) 2 Memory Module Slot 2 (J2B) 7 Memory Module Slot 7 (J0B) 3 Memory Module Slot 3 (J3A) 8 Memory Module Slot 8 (J0A) 4 Memory Module Slot 4 (J3B) 9 Processor Card 5 Memory Module Slot 5 (J1B) 10 Memory Module Fault LEDs

18 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Reading the Operator Panel and System LEDs

The following illustration shows the component location on the operator panel.

1 Power-On Button 6 Operator Panel Display 2 Power LED 7 (FS1) Front Serial Connector

(RJ-48 Connector)

3 Attention LED 8 Service Processor Reset Switch

(Pinhole)

4 SCSI Port Activity 9 System Reset Button 5 Ethernet Port Activity

Index Component Name Component Description

1 Power-On Button Turns the system power on and off.

2 Power LED Blinking - When connected to the power source (System is

in standby mode). Solid - When power button has been pressed. Note: There is approximately a 30 second transition period from the time the power button is pressed to when the power LED goes from blinking to on solid. During the transition period, you may observe the blinking intervals speed up.

3 Attention LED Normal State - LED is off.

4 SCSI Port Activity Normal State - LED is on when there is SCSI activity.

5 Ethernet Port Activity Normal State - LED is on when there is Ethernet activity.

6 Operator Panel Display Displays current status of system startup, or diagnostic

information in the event of a hardware problem.

7 Front Serial Connector (FS1) Serial port uses RJ-48 connector. Use to plug in external

devices at the front of the system unit.

8 Service Processor Reset Switch

(Pinhole)

9 System Reset Button Resets the system

Service Personnel Use Only

For more information about other system LEDs, see “Component LEDs” on page 544.

Chapter 1. Reference Information 19

SCSI IDs and Bay Locations

Note: To show the disk drive and disk drive bay locations, the pSeries 630 Model 6C4 and Model 6E4 are

shown with their bezels removed.

Index Bay Location Drive Name SCSI ID

1 Operator Panel

2 D01 IDE CD-ROM (Default)

or IDE DVD-ROM (Optional)

Tape Drive (Optional) SCSI ID 0

3 D02

4 D10 Disk Drive SCSI ID 8

5 D11 Disk Drive SCSI ID 9

6 D12 Disk Drive SCSI ID 10

7 D13 Disk Drive SCSI ID 11

SCSI DVD-RAM (Optional) SCSI ID 1

Diskette Drive (Optional) Not Applicable

IDE (Non-SCSI) SCSI ID 1

Notes:

1. The SCSI bus IDs are the recommended values and indicate how the IDs are set when the system is shipped from the factory. Field installations might not comply with these recommendations.

2. Media bay location D02 is designed to house one of the following optional devices:

v Tape Drive v SCSI DVD-RAM v Diskette Drive

20 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

System Logic Flow

When viewing the following system logic flow illustrations, select the diagram that is closest to your system configuration.

Systems Configured with a GP Processor and Four-Slotted PCI Riser Card

Chapter 1. Reference Information 21

Systems Configured with a GQ Processor and Six-Slotted PCI Riser Card

22 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Location Codes

This system unit uses physical location codes in conjunction with AIX location codes to provide mapping of the failing field replaceable units. The location codes are produced by the system unit’s firmware and AIX.

Note: When the system is running under the Linux operating system, no ″Linux location codes″ exist, but

physical location codes might display in the Linux error logs.

Physical Location Codes

Physical location codes provide a mapping of logical functions in a platform (or expansion sites for logical functions, such as connectors or ports) to their specific locations within the physical structure of the platform.

Location Code Format

The location code is an alphanumeric string of variable length, consisting of a series of location identifiers, separated by a dash (-), or slash (/), or a pound sign (#) character. The series is hierarchical; that is, each location identifier in the string is a physical or logical child of the one preceding it.

v The - (dash) separator character represents a normal structural relationship where the child is a

separate physical package and it plugs into (or is connected to) the parent. For example, P1-C1 is a processor card (C1) plugged into a planar (P1), or P1-M1 is a memory card (M1) plugged into a planar (P1).

v The / (slash) separator character separates the base location code of a function from any extended

location information. A group of logical devices can have the same base location code because they are all on the same physical package, but may require extended location information to describe the connectors they support. For example, P2/S1 describes the location of the serial port 1 controller and its connector (S1), which is located on planar P2 (its base location code), but the / indicates that further devices can be connected to it at the external S1 serial connector. The keyboard controller and its connector likewise have location code P2/K1, which means they have the same base location code (P2) as serial port 1, but a different external connector. In contrast, the location code P2-K1 actually points to the device connected to connector K1; that is, the keyboard. The location code P2/Z1 indicates an integrated SCSI controller which drives connector Z1, while location codes of P2-Z1-... point to the actual SCSI bus and devices.

v The # (pound sign) separator character indicates a cable connection between a connector and parent.

The following are examples:

v U0.1-P1-C1 identifies processor card C1 plugged into the CEC backplane P1. v U0.1-P1-C2-M1 identifies memory card M1 plugged into slot 1 on processor card C2 connected to the

CEC backplane P1.

v U0.1-P1/S1 identifies serial port 1 controller on the CEC backplane P1 or the connector for serial port 1. v U0.1-P1-K1 identifies a keyboard K1, attached to connector K1 on CEC backplane P1. v U0.1-P2/Z1 identifies an integrated SCSI port controller on PCI riser card P2 that drives internal SCSI

drive connector Z1.

v U0.1-P2-Z1-A8... points to the actual SCSI bus and devices attached to Z1; in this case, a hot-plug disk

drive in bay location D10 with a SCSI ID of 8.

Chapter 1. Reference Information 23

AIX Location Codes

Note: When the system is running under the Linux operating system, AIX location codes are not available.

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/Drives

For planars, cards, and non-SCSI devices, the location code is defined as follows:

AB-CD-EF-GH

|||| | | | Device/FRU/Port ID | | Connector ID | devfunc Number, Adapter Number or Physical Location Bus Type or PCI Parent Bus

v The AB value identifies a bus type or PCI parent bus as assigned by the firmware. v The CD value identifies adapter number, the adapter’s devfunc number, or physical location. The

devfunc number is defined as the PCI device number times 8, plus the function number.

v The EF value identifies a connector. v The GH value identifies a port, address, device, or FRU.

Adapters and cards are identified only with AB-CD.

The possible values for AB are:

00 Processor bus 01 ISA bus 02 EISA bus 03 MCA bus 04 PCI bus used in the case where the PCI bus cannot be identified 05 PCMCIA buses xy For PCI adapters where x is equal to or greater than 1. The x and y are characters in the range of 0-9, A-H,

J-N, P-Z (O, I, and lowercase are omitted) and are equal to the parent bus’s ’ibm, aix-location’ open firmware property.

The possible values for CD depend on the adapter/card: v For pluggable PCI adapters/cards, CD is the device’s devfunc number (PCI device number times 8, plus

the function number). The C and D are characters in the range of 0-9, and A-F (hex numbers). Location codes therefore uniquely identify multiple adapters on individual PCI cards.

v For pluggable ISA adapters, CD is equal to the order of the ISA cards defined/configured either by SMIT

or the ISA Adapter Configuration Service Aid.

v For integrated ISA adapters, CD is equal to a unique code identifying the ISA adapter. In most cases,

this code is equal to the adapter’s physical location code. In cases where a physical location code is not available, CD will be FF.

EF is the connector ID. It is used to identify the adapter’s connector to which a resource is attached.

GH is used to identify a port, device, or FRU. For example:

v For ASYNC devices, GH defines the port on the fanout box. The values are 00 to 15. v For a diskette drive, H identifies either diskette drive 1 or 2. G is always 0. v For all other devices, GH is equal to 00.

24 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

For an integrated adapter, EF-GH is the same as the definition for a pluggable adapter. For example, the location code for a diskette drive is 01-D1-00-00. A second diskette drive is 01-D1-00-01.

SCSI Devices/Drives

For SCSI devices, the location code is defined as follows:

AB-CD-EF-G,H

| | ||| | | | | Logical Unit address of the SCSI Device | | | Control Unit Address of the SCSI Device | | Connector ID | devfunc Number, Adapter Number or Physical Location Bus Type or PCI Parent Bus

Where AB-CD-EF are the same as non-SCSI devices.

G defines the control unit address of the device. Values of 0 to 15 are valid.

H defines the logical unit address of the device. Values of 0 to 255 are valid.

A bus location code is also generated as ’00-XXXXXXXX’ where XXXXXXXX is equivalent to the node’s unit address.

Examples of physical location codes displayed by AIX are as follows: v Processor card C1 plugged into CEC backplane P1:

U0.1-P1-C1

v Processor card C2 attached to CEC backplane P1:

U0.1-P1-C2

v Memory DIMM in slot 2 of processor card C1 attached to CEC backplane P1:

U0.1-P1-C1-M2

Examples of AIX location codes displayed are as follows: v Integrated PCI adapter:

10-80 Ethernet 10-60 Integrated SCSI Port 1 (internal) 10-88 Integrated SCSI Port 2 (external)

Chapter 1. Reference Information 25

v Pluggable PCI adapters:

Note: The number of PCI-X slots available is dependent on the number of slots your PCI riser card has

available. Your system can be configured with either a four or six slotted PCI riser card.

20-58 to 20-5F Any PCI card in slot 1 20-60 to 20-67 Any PCI card in slot 2 10-68 to 10-6F Any PCI card in slot 3 10-70 to 10-77 Any PCI card in slot 4 10-78 to 10-7F Any PCI card in slot 5 10-80 to 10-87 Any PCI card in slot 6

v Integrated ISA adapters:

01-D1 Diskette adapter 01-R1 Parallel port adapter 01-S1 Serial port 1 adapter 01-S2 Serial port 2 adapter 01-S3 Serial port 3 adapter 01-K1 Keyboard adapter

v Device attached to SCSI controller:

10-60-00-4,0 Device attached to integrated SCSI Port 1

Multiple FRU Callout Instructions

If an eight-digit error code appears in the operator panel display or in Chapter 5, “Error Code to FRU Index”, on page 209, a location code for a failing part might also be specified. If the location code includes a blank space followed by a lowercase x followed by a number, this is an error code with multiple FRU callouts. This error can typically happen with memory DIMMs or processors, and might involve mixed types of parts. In this case, check the system’s configuration for FRU part numbers to determine the appropriate set of FRUs.

To determine the FRU part numbers of the electronic assemblies in the entire system, use the service processor menus. From the General User menu, select Read VPD Image from Last System Boot, then enter 90 to display detailed Vital Product Data (VPD).

To determine the FRU part numbers of the electronic assemblies in a partition by using the lscfg -vp | pg command on the AIX command line to display the detailed VPD of all assemblies. The FRU part number information for processors and memory DIMMs might be located at the bottom of the command output.

26 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

FRU Identify LEDs

This system is configured with an arrangement of LEDs that help identify various components of the system. These include, but are not limited to the following:

v Rack identify LED v CEC drawer identify LED v I/O drawer identify LED v RIO port identify LED v FRU identify LED

– Power subsystem FRUs – CEC subsystem FRUs – I/O subsystem FRUs

v I/O adapter identify LED v DASD identify LED

The identify LEDs are arranged hierarchically, with the FRU identify LED at the bottom of the hierarchy, followed by the corresponding CEC or I/O drawer identify LED, and the corresponding rack identify LED to locate the failing FRU more easily.

Any identify LED in the system can be flashed when the system is in the failed state with power on by using the service processor LED Control Menu shown in “System Information Menu” on page 376.

Any identify LED in the system can also be flashed by using the ″Identify and Attention Indicators″ task in diagnostics. The procedure to operate the ″Identify and Attention Indicators″ task in diagnostics is outlined in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

If the service processor menus and the AIX diagnostics are not available, the FRU identify LEDs can be flashed by one of following:

v If the system is configured as a full system partition, boot to the open firmware prompt. See the “System

Power Control Menu” on page 372 for instructions on setting up the boot mode to enable the boot to the open firmware prompt. To display a menu that will allow you to turn on the desired FRU identify LED, type FRU-LED-MENU on the command line.

v If the system is logically partitioned, the HMC must be attached. For instructions on activating and

deactivating a FRU identify LED, see the Service Focal Point chapter of the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590.

Chapter 1. Reference Information 27

Mapping AIX and Physical Location Codes

Note: When the system is running under the Linux operating system, AIX location codes are not available.

Use the following illustration to aid you in the mapping of a location code to its connector on the system backplane.

28 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Use the following illustration to aid you in the mapping of a location code to its DIMM slot on the processor cards.

Four-Slotted PCI Riser Card Location Codes

Use the following illustration to aid you in the mapping of a location code to its slot on the PCI riser card.

Chapter 1. Reference Information 29

Six-Slotted PCI Riser Card Location Codes

Disk Drive Backplane Location Codes

Use the following illustration to aid you in the mapping of a location code to its slot on the disk drive backplane.

30 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

AIX and Physical Location Code Table

Note: When the system is running under the Linux operating system, AIX location codes are not available.

This section covers the AIX and Physical Location Code tables for the pSeries 630 Model 6C4 and Model 6E4, as well as the 7311 Model D20 I/O Drawer.

pSeries 630 Model 6C4 and Model 6E4 Location Codes

Component Name Physical Location Code AIX Location Code

Central Electronics Complex (CEC)

Rack Frame U0

CEC Drawer U0.1

CEC Backplane U0.1-P1

PCI Riser Card U0.1-P2

Disk Drive Backplane U0.1-P3

Processor Cards

Processor Card 1 U0.1-P1-C1

Processor Card 2 U0.1-P1-C2

Memory DIMMs on Processor Card 1

Memory DIMM 1

Memory DIMM 2

Memory DIMM 3

Memory DIMM 4

Memory DIMM 5

Memory DIMM 6

Memory DIMM 7

Memory DIMM 8

Memory DIMM 1

Memory DIMM 2

Memory DIMM 3

Memory DIMM 4

Memory DIMM 5

Memory DIMM 6

U0.1-P1-C1-M1

U0.1-P1-C1-M2

U0.1-P1-C1-M3

U0.1-P1-C1-M4

U0.1-P1-C1-M5

U0.1-P1-C1-M6

U0.1-P1-C1-M7

U0.1-P1-C1-M8

Memory DIMMs on Processor Card 2

U0.1-P1-C2-M1

U0.1-P1-C2-M2

U0.1-P1-C2-M3

U0.1-P1-C2-M4

U0.1-P1-C2-M5

U0.1-P1-C2-M6

Chapter 1. Reference Information 31

Component Name Physical Location Code AIX Location Code

Memory DIMM 7

Memory DIMM 8

Debug Connector (Manufacturing Use Only)

Parallel Port U0.1-P1/R1 01-R1

ISA Bus U0.1-P1 1G-18

HMC2 Connector U0.1-P1/S5

HMC1 Connector U0.1-P1/S4

SPCN2 Connector U0.1-P1/Q5

SPCN1 Connector U0.1-P1/Q4

Keyboard Connector U0.1-P1/K1 01-K1-00

Keyboard U0.1-P1/K1-K1 01-K1-00-00

Mouse Connector U0.1-P1/O1 01-K1-01

Mouse U0.1-P1/O1-O1 01-K1-01-00

Ethernet Connector 1 U0.1-P1/E1 14-08

Ethernet Connector 2 U0.1-P1/E2 1L-08

RIO-2 1 Connector U0.1-P1/Q3

RIO-2 0 Connector U0.1-P1/Q2

Rack Indicator USB Connector U0.1-P1/Q1

Serial Connector 1 U0.1-P1/S1 01-S1

Serial Connector S1F (Located on Operator Panel)

Serial Connector 2 U0.1-P1/S2 01-S2

Serial Connector 3 U0.1-P1/S3 01-S3

Diskette Port U0.1-P1/D1 01-D1

Diskette U0.1-P1-D1 01-D1-00-00

CD-ROM (IDE) U0.1-P1/Q6-A0 1G-19-00

Base CD-ROM (IDE) Controller U0.1-P1/Q6 1G-19

PCI Host Bridge 0 U0.1-P2

PCI Host Bridge 1 U0.1-P2

PCI Slot 1 U0.1-P2/I1

PCI Slot 1 Card U0.1-P2-I1 1V-08

PCI Slot 2 U0.1-P2/I2

PCI Slot 2 Card U0.1-P2-I2 1H-08

PCI Host Bridge 2 U0.1-P2

PCI Slot 3 U0.1-P2/I3

PCI Slot 3 Card U0.1-P2-I3 1n-08

PCI Slot 4 U0.1-P2/I4

U0.1-P1-C2-M7

U0.1-P1-C2-M8

Integrated Devices

Labeled Debug Connector

U0.1-P1/S1 01-S1

Pluggable Adapters

32 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Component Name Physical Location Code AIX Location Code

PCI Slot 4 Card U0.1-P2-I4 1Z-08

PCI Slot 5 (six-slotted PCI riser card

U0.1-P2/I5

only)

PCI Slot 5 Card (six-slotted PCI riser

U0.1-P2-I5 1D-08

card only)

PCI Slot 6 (six-slotted PCI riser card

U0.1-P2/I6

only)

PCI Slot 6 Card (six-slotted PCI riser

U0.1-P2-I6 11-08

card only)

SCSI Devices

Internal SCSI Port (for internal disk

U0.1-P2/Z1 1S-08

drive)

External SCSI Port U0.1-P2/Z2 1S-09

Single-Ended SCSI (six-slotted PCI

U0.1-P2/Z3 1c-08

riser card only)

Media Device #1

U0.1-P2-Ix/Zn-A0 Dependent on Ix

(for example, a tape drive)

Media Device #2

U0.1-P2-Ix/Zn-A1 Dependent on Ix

(for example, a DVD drive)

Hot-swap Disk Drive bay 1 U0.1-P2/Z1-A8 1S-08-00-8,0

Hot-swap Disk Drive bay 2 U0.1-P2/Z1-A9 1S-08-00-9,0

Hot-swap Disk Drive bay 3 U0.1-P2/Z1-AA 1S-08-00-10,0

Hot-swap Disk Drive bay 4 U0.1-P2/Z1-AB 1S-08-00-11,0

Fans

Fan 1 (Primary Processor Fan) U0.1-F1

Fan 2 (Redundant Processor Fan) U0.1-F2

Fan 3 (PCI Fan) U0.1-F3

Fan 4 (PCI Fan) U0.1-F4

Operator Panel

Operator panel U0.1-L1

Power Supply

Power supply 1 (Primary) U0.1-V1

Power supply 2 (Redundant) U0.1-V2

Battery

Battery U0.1-P1-V3

Platform Firmware

Platform Firmware U0.1-P1/Y1

System VPD module

System VPD module U0.1-L1-N1

Chapter 1. Reference Information 33

Component Name Physical Location Code AIX Location Code

Notes:

1. The physical location code for the PCI slots, when empty, uses the P1/Ix notation, where the ’/’ identifies an integrated device (in this case the empty slot). A PCI device plugged into the slot uses the P1-Ix notation, where the ’-’ identifies a plugged device.

2. SCSI bus IDs are the recommended values. SCSI IDs shown for media devices indicate how the devices are set when they are shipped from the factory. Field installations may not comply with these recommendations.

I/O Subsystem Locations

This section covers the AIX and physical location code tables for the 7311 Model D20 I/O drawer.

The tables in this section contain the location codes for I/O subsystems when they are attached to the processor-subsystem drawer. A separate table is shown for each I/O subsystem. In the tables, the drawer number for the I/O subsystem is represented by dd. The first time that a system is powered on, the I/O subsystems are numbered according to the order in which they are configured. For example, if a system is first installed with eight I/O subsystems connected, the dd values for the subsystems should number from 2 through 9.

If at a later time, an I/O subsystem is removed from the system and another I/O subsystem is substituted, the substitute is assigned the next higher number available for its value of dd. In the earlier example, this is 10.

Also, if an I/O backplane is replaced inside an I/O subsystem and power is applied, the system will configure the I/O subsystem with the new backplane in the order following the other I/O subsystems. Its value for dd will not be the same as the one it replaced. In the case of the earlier example, the next higher value for dd is 10, so a drawer number of 10 is assigned to the new I/O backplane.

Note: If the I/O backplane VPD module is moved to the new I/O backplane, the I/O subsystem retains its

original dd value.

If the original I/O subsystem or I/O backplane is reinstalled in the system, the system uses the original dd value for the I/O subsystem.

The following diagram defines each part of a location code:

Ux.dd-xx-yy |||| |||| |||yyThis code is used for the next component (yy, yy, yy, ...) | | xx This code is used for the next component (Px, Fx, Vx, ...) | dd This code is the drawer number for the I/O drawer (2 to 63) Ux This code normally identifies the rack in which a drawer is installed.

The x will always be zero (0) for this system.

Determining the AIX Location Code of a Physical Slot: Every slot of every I/O subsystem has a unique AIX location code assigned to it. For instance, the PCI adapter in slot 1 of I/O subsystem 1 is 29-08. There is no obvious way to determine the value of the dd number for the I/O subsystem that is interpreted by the system as the first I/O subsystem. If you have only the AIX location code, you might determine the associated I/O subsystem dd number by performing the following steps:

1. On the AIX command line, type lsdev -Ccadapter |pg

The resulting list gives the logical AIX name of all resources and the corresponding AIX location code. Look for the appropriate AIX location code, and record the corresponding AIX logical name of the resource.

34 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

2. On the AIX command line, type lsslot -c pci |pg

This list relates the AIX logical name of all resources to location code. Look for the AIX logical name that you recorded in the first step and read the location code of the resource. You can then determine the physical location of the resource by flashing the FRU identify LED (see “FRU Identify LEDs” on page 27) that corresponds to the location code.

FRU Name Physical Location Code AIX Location Code

Model D20 I/O Drawer U0.dd (dd = any number from 2 through 63)

First I/O Subsystem Location Codes

Rack frame U0

I/O drawer backplane U0.dd-P1

I/O subsystem drawer U0.dd

RIO Bus Adapter

RIO bus adapter U0.dd-P1.1

RIO port 1 upper connector U0.dd-P1.1/Q1

RIO port 1 cable U0.dd-P1.1/Q1#

RIO port 0 lower connector U0.dd-P1.1/Q2

RIO port 0 cable U0.dd-P1.1/Q2#

PCI Bus Controller

PCI bus controller PHB0 U0.dd-P1

PCI to PCI bridge EADS-X U0.dd-P1 1r-10, 1r-12, 1r-16

PCI Bus Controller PHB2

PCI bus controller PHB2 U0.dd-P1

PCI to PCI bridge (EADS_X) U0.dd-P1 2Q-10, 2Q-12, 2Q-14, 2Q-16

Pluggable Adapter Slots

PCI slot 1 U0.dd-P1/I1

PCI card in slot 1 U0.dd-P1-I1 2R-08

PCI slot 2 U0.dd-P1/I2

PCI card in slot 2 U0.dd-P1-I2 2U-08

PCI slot 3 U0.dd-P1/I3

PCI card in slot 3 U0.dd-P1-I3 2a-08

PCI slot 4 U0.dd-P1/I4

PCI card in slot 4 U0.dd-P1-I4 2d-08

PCI slot 5 U0.dd-P1/I5

PCI card in slot 5 U0.dd-P1/I5 1s-08

PCI slot 6 U0.dd-P1/I6

PCI card in slot 6 U0.dd-P1/I6 1v-08

PCI slot 7 U0.dd-P1/I7

PCI card in slot 7 U0.dd-P1/I7 25–08

Power Supply

Power supply 1 (no internal blower) U0.dd-V1

Power supply 2 (no internal blower) U0.dd-V2

Cooling Blowers

Chapter 1. Reference Information 35

FRU Name Physical Location Code AIX Location Code

Cooling blower 1 U0.dd-F1

Cooling blower 2 U0.dd-F2

Cooling blower 3 U0.dd-F3

Cooling blower 4 U0.dd-F4

SPCN Connectors

Reserved U0.dd-P1/Q3

Reserved U0.dd-P1/Q4

SPCN3 connector U0.dd-P1/Q5

SPCN4 connector U0.dd-P1/Q6

Rack Indicator

Rack beacon (4-pin) U0.dd-P1/Q7

Operator Panel

Operator panel U0.dd-L1

Temperature Sensor

Temperature sensor (on operator panel)

Disk drive backplane 1 U0.dd-P3

Disk drive backplane 2 U0.dd-P4

Disk drive bay location are numbered from left to right with the left most bay being #1.

Hot-swap disk drive bay 1 U0.dd-P1-Ix/Zn-A8 Dependent on Ix

Hot-swap disk drive bay 2 U0.dd-P1-Ix/Zn-A9 Dependent on Ix

Hot-swap disk drive bay 3 U0.dd-P1-Ix/Zn-AA Dependent on Ix

Hot-swap disk drive bay 4 U0.dd-P1-Ix/Zn-AB Dependent on Ix

Hot-swap disk drive bay 5 U0.dd-P1-Ix/Zn-AC Dependent on Ix

Hot-swap disk drive bay 6 U0.dd-P1-Ix/Zn-AD Dependent on Ix

Hot-swap disk drive bay 7 U0.dd-P1-Iy/Zn-A8 Dependent on Iy

Hot-swap disk drive bay 8 U0.dd-P1-Iy/Zn-A9 Dependent on Iy

Hot-swap disk drive bay 9 U0.dd-P1-Iy/Zn-AA Dependent on Iy

Hot-swap disk drive bay 10 U0.dd-P1-Iy/Zn-AB Dependent on Iy

Hot-swap disk drive bay 11 U0.dd-P1-Iy/Zn-AC Dependent on Iy

Hot-swap disk drive bay 12 U0.dd-P1-Iy/Zn-AD Dependent on Iy

SES0 U0.dd-P1-Ix/Zn-AF Dependent on Ix

SES1 U0.dd-P1-Iy/Zn-AF Dependent on Iy

U0.dd-L1

Disk Drive Backplanes

Disk Drive Locations

SCSI

FRU Name Physical Location Code AIX Location Code

Model D20 I/O Drawer U0.dd (dd = any number from 2 through 63)

Rack frame U0

36 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Second I/O Subsystem Location Codes

FRU Name Physical Location Code AIX Location Code

I/O drawer backplane U0.dd-P1

I/O subsystem drawer U0.dd

RIO Bus Adapter

RIO bus adapter U0.dd-P1.1

RIO port 1 upper connector U0.dd-P1.1/Q1

RIO port 1 cable U0.dd-P1.1/Q1#

RIO port 0 lower connector U0.dd-P1.1/Q2

RIO port 0 cable U0.dd-P1.1/Q2#

PCI Bus Controller

PCI bus controller PHB0 U0.dd-P1

PCI to PCI bridge EADS-X U0.dd-P1 2g-10, 2g-12, 2g-16

PCI Bus Controller PHB2

PCI bus controller PHB2 U0.dd-P1

PCI to PCI bridge (EADS_X) U0.dd-P1 3G-10, 3G-12, 3G-14, 3G-16

Pluggable Adapter Slots

PCI slot 1 U0.dd-P1/I1

PCI card in slot 1 U0.dd-P1-I1 3H-08

PCI slot 2 U0.dd-P1/I2

PCI card in slot 2 U0.dd-P1-I2 3L-08

PCI slot 3 U0.dd-P1/I3

PCI card in slot 3 U0.dd-P1-I3 3S-08

PCI slot 4 U0.dd-P1/I4

PCI card in slot 4 U0.dd-P1-I4 3V-08

PCI slot 5 U0.dd-P1/I5

PCI card in slot 5 U0.dd-P1/I5 2h-08

PCI slot 6 U0.dd-P1/I6

PCI card in slot 6 U0.dd-P1/I6 2m-08

PCI slot 7 U0.dd-P1/I7

PCI card in slot 7 U0.dd-P1/I7 2w–08

Power Supply

Power supply 1 (no internal blower) U0.dd-V1

Power supply 2 (no internal blower) U0.dd-V2

Cooling Blowers

Cooling blower 1 U0.dd-F1

Cooling blower 2 U0.dd-F2

Cooling blower 3 U0.dd-F3

Cooling blower 4 U0.dd-F4

SPCN Connectors

Reserved U0.dd-P1/Q3

Reserved U0.dd-P1/Q4

SPCN3 connector U0.dd-P1/Q5

Chapter 1. Reference Information 37

FRU Name Physical Location Code AIX Location Code

SPCN4 connector U0.dd-P1/Q6

Rack Indicator

Rack beacon (4-pin) U0.dd-P1/Q7

Operator Panel

Operator panel U0.dd-L1

Temperature Sensor

Temperature sensor (on operator panel)

Disk drive backplane 1 U0.dd-P3

Disk drive backplane 2 U0.dd-P4

Disk drive bay location are numbered from left to right with the left most bay being #1.

Hot-swap disk drive bay 1 U0.dd-P1-Ix/Zn-A8 Dependent on Ix

Hot-swap disk drive bay 2 U0.dd-P1-Ix/Zn-A9 Dependent on Ix

Hot-swap disk drive bay 3 U0.dd-P1-Ix/Zn-AA Dependent on Ix

Hot-swap disk drive bay 4 U0.dd-P1-Ix/Zn-AB Dependent on Ix

Hot-swap disk drive bay 5 U0.dd-P1-Ix/Zn-AC Dependent on Ix

Hot-swap disk drive bay 6 U0.dd-P1-Ix/Zn-AD Dependent on Ix

Hot-swap disk drive bay 7 U0.dd-P1-Iy/Zn-A8 Dependent on Iy

Hot-swap disk drive bay 8 U0.dd-P1-Iy/Zn-A9 Dependent on Iy

Hot-swap disk drive bay 9 U0.dd-P1-Iy/Zn-AA Dependent on Iy

Hot-swap disk drive bay 10 U0.dd-P1-Iy/Zn-AB Dependent on Iy

Hot-swap disk drive bay 11 U0.dd-P1-Iy/Zn-AC Dependent on Iy

Hot-swap disk drive bay 12 U0.dd-P1-Iy/Zn-AD Dependent on Iy

SES0 U0.dd-P1-Ix/Zn-AF Dependent on Ix

SES1 U0.dd-P1-Iy/Zn-AF Dependent on Iy

U0.dd-L1

Disk Drive Backplanes

Disk Drive Locations

SCSI

38 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

System Cables

The following diagrams show the system cable connections. The following diagram illustrates the routing of the internal power cables.

Internal Power Cable Routing Diagram

1 Operator Panel 2 IDE CD-ROM 3 SCSI Media Device 4 CEC Backplane to Operator Panel Signal/Power Cable 5 2-drop Power Cable from CEC Backplane to IDE CD-ROM and other SCSI Media Devices 6 CEC Backplane to Disk Drive Backplane Power Cable 7 Disk Drive Backplane 8 Diskette Drive to CEC Backplane Power Cable

9 PCI Cooling Fans #3 and #4 Power Cable 10 Diskette Drive 11 CEC Backplane

Chapter 1. Reference Information 39

Internal Signal Cable Routing Diagram

The following diagram illustrates the routing of the signal cables.

40 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

1 Operator Panel

2 SCSI Media Device (50-pin)

3 SCSI Media Device (68-pin)

4 SCSI Media Device (68-pin)

5 CEC Backplane to Operator Panel Signal Cable

6 SCSI Media (68-pin) to 50-pin Converter Cable

7 SCSI Media Device Signal Cable to Integrated Single-Ended SCSI Connector on the PCI Riser Card

8 CEC Backplane Connector to Diskette Drive Signal Cable

9 CEC Backplane to IDE CD-ROM Signal Cable 10 Diskette Drive 11 IDE CD-ROM 12 Disk Drive Backplane 13 PCI Riser Card to Disk Drive Backplane Signal Cable 14 PCI Riser Card to Disk Drive Backplane Signal Cable 15 6-Slotted PCI Riser Card

15a 4-Slotted PCI Riser Card (Used on 4-slotted models only)

16 CEC Backplane 17 PCI Riser Card to External SCSI Signal Cable 18 External SCSI Port 19 CEC Backplane to Rack Indicator Signal Cable 20 Rack Indicator Port 21 CEC Backplane to Debug Port Signal Cable 22 Debug Parallel Port

Subsystem Positioning and Cabling

The I/O subsystem drawer can be installed in a standard 19-inch EIA rack in any location near to the system. The cables that connect the drawers allow some flexibility in drawer placement, but the I/O drawers should be located as close to the system unit as possible.

The Model 6C4 can have a total of two I/O drawers connected. Each drawer is connected to the system unit using a system power control network (SPCN) cable loop and a remote I/O (RIO) cable loop.

Although the SPCN cables are connected in a loop, only one loop is needed for both of the I/O drawers.

SPCN Cabling

I/O drawer SPCN cables are connected to the system using a loop configuration. The SPCN cables are connected in a loop so that the system has two paths to each I/O drawer. The Model 6C4 can have a total of two I/O drawers connected in one SPCN loop.

The location codes for the I/O drawers are assigned during the system power-on sequence. Each drawer’s location is determined by its position in the SPCN loop. The first drawer in the SPCN loop (the drawer connected to SPCN 0) is given the location U0.2. If there is a second I/O drawer in the SPCN loop, it is assigned the location U0.3. The I/O drawers are numbered sequentially until the end of the loop is reached at SPCN 1. For cabling examples, see the following illustrations.

Chapter 1. Reference Information 41

Cabling SPCN Cables to One or Two I/O Subsystems

The following illustration shows the SPCN cabling for either one or two I/O drawer configurations.

One I/O Drawer Attached to Model 6C4:

1 Model 6C4 3 Cable from Model 6C4 Connector SPCN 2 to 7311 Model D20

Connector SPCN 4 (J16)

2 7311 Model D20 4 Cable from Model 6C4 Connector SPCN 1 to 7311 Model D20

Connector SPCN 3 (J15)

42 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Two I/O Drawers Attached to Model 6C4:

1 Model 6C4 4 Cable from Model 6C4 Connector SPCN 1 to 7311 Model D20

2 7311 Model D20 I/O

Drawer

3 7311 Model D20 I/O

Drawer

Connector SPCN 3 (J15)

5 Cable from Model 6C4 Connector SPCN 2 to 7311 Model D20

Connector SPCN 4 (J16)

6 Cable from 7311 Model D20 Connector SPCN 4 (J16) to 7311

Model D20 Connector SPCN 3 (J15)

Chapter 1. Reference Information 43

RIO-2 Cabling

I/O drawers are connected to the system through remote I/O (RIO-2) cable loops. The cable loops are connected to ports located on the rear of the system. The RIO-2 cables are connected in loops so that the system has two paths to each I/O drawer.

Up to two I/O drawers can be connected to a system using one RIO-2 loop. For cabling examples, see the following illustrations.

Cabling RIO-2 Cables to One or Two I/O Subsystems

The following illustrations show the RIO-2 cabling for either one or two I/O drawer configurations.

One I/O Drawer Attached to Model 6C4:

1 Model 6C4 3 Cable from Model 6C4 Connector RIO-2 0 to 7311 Model D20

Connector RIO-2 0

2 7311 Model D20 4 Cable from Model 6C4 Connector RIO-2 1 to 7311 Model D20

Connector RIO-2 1

44 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Two I/O Drawers Attached to Model 6C4:

1 Model 6C4 4 Cable from Model 6C4 Connector RIO-2 0 to 7311 Model D20

2 7311 Model D20 I/O

Drawer

3 7311 Model D20 I/O

Drawer

Connector RIO-2 0

5 Cable from Model 6C4 Connector RIO-2 1 to 7311 Model D20

Connector RIO-2 1

6 Cable from 7311 Model D20 Connector RIO-2 1 to 7311 Model

D20 Connector RIO-2 0

Chapter 1. Reference Information 45

Specifications

This section contains system specifications for both Model 6C4 and Model 6E4.

Note: Refer to the 7014 Series Model T00 and T42 Rack Installation and Service Guide, order number

SA38-0577, for information on cabling power from the rack to the I/O subsystem.

Dimensions Rack (Model 6C4) Tower (Model 6E4)

Height 176 mm 6.9 in. 544.0 mm (21.42 in.)

4 EIA Units

Width 448 mm 17.5 in. 308.0 mm (12.13 in.) 191 mm without

legs

Depth 816 mm 32.13 in. - Includes 145 mm

for cable management arm

Weight

Minimum configuration 32.0 kg 70.4 lbs. 36.0 kg 79.2 lbs. Maximum configuration 47.3 kg 104.0 lbs. 51.0 kg 112.2 lbs.

Electrical

Power source loading (maximum in kVA)

Power source loading (typical in kVA) 0.75 Voltage range (V ac) 100-127 Vac or 200-240 Vac (single phase) Frequency (hertz) 50 / 60 Thermal output (maximum) 2540 Btu/hr Thermal output (typical) Btu/hr Power Requirements (minimum load) 350 watts Power Requirements (maximum load) 670 watts Power factor - U.S., World Trade,

Japan Inrush current¹ 75/amps (maximum at <10ms)

25/amps (maximum at 10ms - 150ms)

Note: The above amps are held for the full input range of 180 V/ac to 259

V/ac and 47 to 63 Hz.

789.0 mm (31 in.) - Includes 70 mm for rear acoustic cover

1.20

0.95

Maximum Altitude², ³ 2135 m (7000 ft.)

Temperature Requirements Operating

5 to 35°C

(41 to 95°F)

Storage

1 to 60°C

(34 to 140°F)

Humidity Requirements Operating Storage

(Noncondensing) 8 to 80% 5 to 80%

Wet Bulb 27°C (80°F) 27°C (80°F)

Model 6E4 Noise Emissions⁴ Operating Idle

L <L

WAd

pA>m

6.0 bels 5.9 bels 42 dBA 41 dBA

Model 6C4 Noise Emissions⁴ Operating Idle

L <L

WAd

pA>m

6.1 bels 6.0 bels 44 dBA 43 dBA

46 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Dimensions Rack (Model 6C4) Tower (Model 6E4)

Install/Air Flow Maintenance of proper service clearance should allow proper airflow.

Service When installing a rack unit, refer to “System Service Clearances” on

page 563 for the rack correct clearances.

1. Inrush currents occur only at initial application of power, no inrush occurs during normal power off-on cycle.

2. The upper limit of the dry bulb temperature must be derated 1 degree C per 137 m (450 ft.) above 915 m (3000 ft.).

3. The upper limit of the wet bulb temperature must be derated 1 degree C per 274 m (900 ft. ) above 305 m (1000 ft.).

4. Levels are for a single system installed in a T00 32-EIA rack with the center of the unit approximately 1500 mm (59 in.) off the floor.

External AC Power Cables

To avoid electrical shock, a power cable with a grounded attachment plug is provided. Use only properly grounded outlets.

Power cables used in the United States and Canada are listed by Underwriter’s Laboratories (UL) and certified by the Canadian Standards Association (CSA). These power cords consist of the following:

v Electrical cables, Type SVT or SJT. v Attachment plugs complying with National Electrical Manufacturers Association (NEMA) 5-15P, that is:

″For 115 V operation, use a UL listed cable set consisting of a minimum 14 AWG, Type SVT or SJT three-conductor cord a maximum of 15 feet in length and a parallel blade, grounding type attachment plug rated at 15 A, 125 V.″

″For 230 V operation in the United States use a UL listed cable set consisting of a minimum 18 AWG, Type SVT or SJT three-conductor cable a maximum of 15 feet in length, and a tandem blade, grounding type attachment plug rated at 15 A, 250 V.″

v Appliance couplers complying with International Electrotechnical Commission (IEC) Standard 320, Sheet

C13.

Power cables used in other countries consist of the following:

v Electrical cables, Type HD21. v Attachment plugs approved by the appropriate testing organization for the specific countries where they

are used.

″For units set at 230 V (outside of U.S.): use a cable set consisting of a minimum 18 AWG (1.0 mm nominal cross sectional area). Outside of North America , a more common cordage reference is in mm

and for a HAR (harmonized) cord, you may not find a AWG equivalent.

To find the power cables that are available, refer to Chapter 10, “Parts Information”, on page 515.

Chapter 1. Reference Information 47

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 the safe operation of the equipment. v External devices with their own power cables have those cables attached.

If the inspection indicates an unacceptable safety condition, the condition must be corrected before anyone can service the machine.

Note: The owner of the system is responsible to correct any unsafe conditions.

Perform the following checks:

1. Check the covers for sharp edges and for damage or alterations that expose the internal parts of the system.

2. Check the covers for proper fit to the system. They should be in place and secure.

3. Gently rock the system from side to side to determine if it is steady.

4. Set the power button of the system to Off.

5. Remove the covers.

6. Check for alterations or attachments. If there are any, check for obvious safety hazards, such as broken wires, sharp edges, or broken insulation.

7. Check the internal cables for damage.

8. Check for dirt, water, and any other contamination within the system.

9. Check the voltage label on the back of the system to ensure that it matches the voltage at the outlet.

10. Check the external power cable for damage.

11. With the external power cable connected to the system, check for 0.1 ohm or less resistance between the ground lug on the external power cable plug and the metal frame.

12. Perform the following checks on each device that has its own power cables:

a. Check for damage to the power cable. b. Check for the correctly grounded power cable. c. With the external power cable connected to the device, check for 0.1 ohm or less resistance

between the ground lug on the external power cable plug and the metal frame of the device.

13. Install the covers.

48 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Chapter 2. Diagnostic Overview

The system uses an integrated set of software diagnostic procedures to help isolate failing components and system maintenance. This book, along with the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems, is the basis of the diagnostic procedures for the system. In particular, Chapter 4, “Checkpoints”, on page 159, Chapter 5, “Error Code to FRU Index”, on page 209, Chapter 6, “Using the Online and Standalone Diagnostics”, on page 353, and Chapter 10, “Parts Information”, on page 515, in this book are important for the trained service representative to understand and use when isolating a failure on the system.

The manufacturer recommends that systems configured with 4 GB of memory or greater 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.

Maintenance Analysis Procedures (MAPs)

Maintenance Analysis Procedures (MAPs) guide the trained service representative through the system. These MAPs are the entry point for all isolation and error recovery procedures. The MAPs are consistent with existing procedures and methods. The system uses a set of integrated procedures, mentioned earlier, to which the MAPs are the primary entry point.

The MAPS are as follows:

v Entry MAP v Quick Entry MAP v MAP 1020: Problem Determination MAP v MAP 1240: Memory Problem Resolution v MAP 1321: Quick Entry MAP for Systems with Service Focal Point. This MAP contains information for

systems not running under the AIX operating system.

v MAP 1322: End of Call MAP for Systems with Service Focal Point v MAP 1520: Power MAP v MAP 1521: The Base System Drawer will not Power On and No Error Codes are Available v MAP 1522: Cannot Power On the I/O Drawer, Power Present LED Does Not Come On v MAP 1523: The SPCN Error Codes Table Directed You Here and the Error Code is 1011 1B0x v MAP 1540: Problem Isolation Procedures v MAP 1541: JTAG Problem Isolation v MAP 1542: I/O Problem Isolation v MAP 1548: Processor Subsystem Problem Isolation

The Entry Map is the starting point for problem determination. The purpose of this MAP is to quickly point to the appropriate MAP or service reference information either in this book, or in the common book set, which includes the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems and PCI Adapter Placement Reference.

The Quick Entry MAP is a subset of the Entry MAP and helps to save time for some types of problems.

The Problem Determination MAP provides a structured analysis method to get an error code if one is not provided by the customer, or if diagnostics cannot be loaded.

The Power MAP deals with isolation of components to diagnose a power problem. Power problems can be related to powering on and powering off the system, or power failures that occur after power is turned on.

The Minimum Configuration MAP is used to locate defective components not found by normal diagnostics or error-isolation methods. This MAP provides a systematic method of isolation to the failing item.

System LEDs

LEDs provides a means to identify components in your system. See Chapter 12, “Fault and Attention LEDs”, on page 543 for more information about these LEDs.

System Attention LED

The system attention LED, on the operator panel turns on when an entry is made in the service processor error log. When the LED is on, it indicates that user intervention or service is needed. The error entry is transmitted and recorded in the following logs:

v The system-level error logs v The operating system error log v The service action event log (such as loss of surveillance from the HMC to a logical partition) in the

Service Focal Point application

If the system attention LED is turned on, you can access the system logs to determine the reason. The method used to access your system logs depends on how your system is set up. For more information about how to access the system logs, refer to “Accessing System Log Error Information” on page 58.

Checkpoints

The system uses various types of checkpoints, error codes, and SRNs, which are referred to throughout this book (primarily in Chapter 4, “Checkpoints”, on page 159, Chapter 5, “Error Code to FRU Index”, on page 209, Chapter 6, “Using the Online and Standalone Diagnostics”, on page 353, and Chapter 10, “Parts Information”, on page 515). These codes can appear in the service processor boot progress log, the operating system error log, and the operator panel display. Understanding the definition and relationships of these codes is important to the service personnel who are installing or maintaining the system.

Codes that can appear in the service processor boot progress log, the operating system error log, the virtual terminal, and the operator panel display are as follows:

Checkpoints Checkpoints display in the operator panel from the time ac power is connected to the

system until the operating system login prompt is displayed after a successful operating system boot. These checkpoints have the following forms:

8xxx 8xxx checkpoints are displayed from the time ac power is connected to the system

until the OK prompt is displayed by the service processor on the operator panel display. (Several 9xxx checkpoints are displayed just before the OK prompt displays.)

9xxx 9xxx checkpoints are displayed by the service processor after the power-on

sequence is initiated. A system processor takes control when 91FF displays on the operator panel display.

Note: Certain checkpoints may remain in the display for long periods of time. A

spinning cursor is visible in the upper-right corner of the display during these periods to indicate that system activity is continuing.

Exxx Exxx checkpoints indicate that a system processor is in control and is initializing

the system resources. Control is being passed to the operating system when E105 displays on the operator panel display. Location code information may also display on the operator panel during this time.

50 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

0xxx and 2xxx 0xxx and 2xxx codes are AIX progress codes and configuration codes. Location

codes may also be shown on the operator panel display during this time. AIX progress codes will not appear when Linux is the operating system.

Error Codes If a fault is detected, an 8-digit error code is displayed in the operator panel display. A

location code may be displayed at the same time on the second line.

SRNs Service request numbers, in the form xxx-xxx, xxx-xxxx, xxxx-xxx, or xxxx-xxxx may also

be displayed on the operator panel display and be noted in the AIX error log. SRNs will not appear in the Linux system error log when Linux is the operating system.

Checkpoints can become error codes if the system fails to advance past the point at which the code is presented. For a list of the checkpoints, see Chapter 4, “Checkpoints”, on page 159. 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 Eserver pSeries Diagnostic Information for Multiple Bus Systems, order number SA38-0509.

FRU Isolation

For a list of error codes and recommended actions for each code, see Chapter 5, “Error Code to FRU Index”, on page 209. These actions can refer to Chapter 10, “Parts Information”, on page 515, Chapter 3, “Maintenance Analysis Procedures (MAPs)”, on page 61, or provide informational message and directions. If a replacement part is indicated, direct reference is made to the part name. The respective AIX and physical location codes are listed for each occurrence as required. For a list of locations codes, see “Location Codes” on page 23.

Note: When the system is running the Linux operating system, AIX location codes are not available.

To look up part numbers and view component diagrams, see Chapter 10, “Parts Information”, on page 515. The beginning of that chapter provides a parts index with the predominant field replaceable units (FRUs) listed by name. The remainder of the chapter provides illustrations of the various assemblies and components that make up the system.

FRU Identify LEDs

This system is configured with an arrangement of LEDs that help identify various components of the system. These include, but are not limited to the following:

v Rack identify LED v CEC drawer identify LED v I/O drawer identify LED v RIO port identify LED v FRU identify LED

– Power subsystem FRUs – CEC subsystem FRUs – I/O subsystem FRUs

v I/O adapter identify LED v DASD identify LED

Chapter 2. Diagnostic Overview 51

Any identify LED in the system can be flashed when the system is in the failed state with power on by using the service processor LED Control Menu contained in the “System Information Menu” on page 376.

If the service processor menus and the AIX diagnostics are not available, the FRU identify LEDs can be flashed by one of following:

v If the system is configured as a full system partition, boot to the open firmware prompt. See the “System

v If the system is logically partitioned, the HMC must be attached. For instructions on activating and

deactivating a FRU identify LED, see the Service Focal Point chapter of the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590.

Service Agent for the pSeries 630 Model 6C4 and Model 6E4

Service support for the pSeries 630 Model 6C4 and Model 6E4 can be enhanced through the use of the service agent application. This application provides a number of advantages for the system user, including automatic error reporting and analysis without customer intervention. The service agent is shipped with the system or with the HMC.

Using the Service Processor and Service Agent Features

The service processor and service agent features protect users against unnecessary system downtime by advising support personnel of any unexpected changes in the system environment. For more information about the service processor, see Chapter 7, “Using the Service Processor”, on page 363. For more information about the service agent application, see the IBM Hardware Management Console for pSeries Installation and Operations Guide.

Service Focal Point

The Service Focal Point application is used to help the service representative diagnose and repair problems on partitioned systems. Service representatives use the HMC as the starting point for all service issues. The HMC groups various system management issues at one control point, allowing service representatives to use the Service Focal Point application to determine an appropriate service strategy.

Traditional service strategies become more complicated in a partitioned environment. Each partition runs on its own, unaware that other partitions exist on the same system. If one partition reports an error for a shared resource, such as a managed system power supply, other active partitions report the same error. The Service Focal Point application enables service representatives to avoid long lists of repetitive call-home information by recognizing that these errors repeat, and by filtering them into one error code.

The following types of errors are reported to Service Focal Point:

v Permanent hardware errors (detected by the managed system or operating system) v LAN Surveillance errors detected by Service Focal Point v Hardware boot failure errors

The following errors are not reported to Service Focal Point:

v Software errors v Temporary hardware errors v Undetermined hardware errors

52 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

v Informational hardware errors

Errors that require service are reported to the HMC as serviceable events. Because the HMC stores these serviceable events for 90 days and then discards them, it is important to have the partition and HMC date and time set correctly. For instance, if the date on a partition’s software is set 90 days behind the HMC’s set time, the serviceable events reported from this partition are immediately discarded. For more information about setting the HMC’s date and time, see the IBM Hardware Management Console Operations Guide for pSeries, order number SA38-0590. To set the partition’s date and time, see the documentation provided with the operating system that is running on that partition.

Getting Started

When you are setting up Service Focal Point, keep the following in mind: v If the time configured on a partition is 90 days older than time configured on the HMC, serviceable

events cannot be reported.

v Verify that the HMC host names are defined. For more information about using fully qualified and short

host names, see the IBM Hardware Management Console Operations Guide for pSeries, order number SA38-0590.

v If you need to add or change a partition name, see the IBM Hardware Management Console Operations

Guide for pSeries.

Testing Error Reporting

To ensure that Service Focal Point is configured correctly, generate a test error by doing the following:

1. In the partition, run diagnostics to test the managed system’s operator panel.

2. When the diagnostics window asks you if you see 0000 on the managed system’s operator panel, select NO. This action generates an error.

3. In the SRN window, press Enter to proceed.

4. When the system asks you if you want the error sent to Service Focal Point, select YES.

5. Type F3 to exit diagnostics.

6. Wait for one minute while the managed system sends the error to Service Focal Point.

7. Check the Serviceable Event window to ensure that the error was sent to Service Focal Point and that Service Focal Point reported the error. For more information about working with serviceable events, see “Working With Serviceable Events” on page 55.

Service Focal Point Settings

The Service Focal Point Settings task in the HMC Contents area allows you to configure your Service Focal Point application.

Note: The Advanced Operator, Operator, and Viewer roles have read-only access to the following tasks.

Automatic Call-Home Feature

You can configure the HMC to automatically call an appropriate service center when it identifies a serviceable event.

To enable or disable the call-home feature, you must be a member of one of the following roles:

v System Administrator v Service Representative

To enable or disable the call-home feature for one or more systems, do the following:

Note: It is strongly recommended that you not disable the call-home feature. When you disable the

call-home feature, serviceable events are not automatically reported to your service representative.

1. In the Navigation area, click the Service Applications icon.

Chapter 2. Diagnostic Overview 53

2. In the Navigation area, double-click the Service Focal Point icon.

3. In the Contents area, click Service Focal Point Settings.

4. The Service Focal Point Settings window opens. Select the CEC Call Home tab at the top of the window.

5. Click on the managed system you want to enable or disable.

6. Click Enable to enable call-home for the selected system, or click Disable to disable call-home for the selected system.

7. Click OK.

Setting Up Surveillance

Service Focal Point surveillance generates serviceable events when it detects communication problems between the HMC and its managed systems.

You can configure how you want the HMC to survey the following:

v The number of disconnected minutes that are considered an outage v The number of connected minutes you want the HMC to consider a recovery v The number of minutes between outages that are considered a new incident

To set up surveillance, you must be a member of one of the following roles:

v System Administrator v Service Representative

To set up surveillance, do the following:

1. In the Navigation area, click the Service Applications icon.

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 Setup tab on the top of the window.

5. In the first field, select the number of minutes you want the HMC to wait before sending a disconnection error message.

6. In the second field, select the amount of connection time that the HMC is considered to be recovered. This amount is expressed in minutes.

7. In the third field, select the number of minutes between outages that you want the HMC to wait before sending a new incident report.

8. Select one or more managed systems from the table in the lower part of the window, then click Enable or Disable. Surveillance is then either enabled or disabled for the selected managed systems.

Enabling Surveillance Notifications

You can enable or disable surveillance-error notification from this HMC to connected managed systems. Enabling this notification causes errors to be passed to the Service Agent application for notification.

Note: You must further configure Service Agent to handle notifications sent by Service Focal Point. For

more information about Service Agent, refer to the IBM Hardware Management Console Operations Guide for pSeries, order number SA38-0590

To set up surveillance, you must be a member of one of the following roles:

v System Administrator v Service Representative

To set up surveillance-error notification, do the following:

1. In the Navigation area, click the Service Applications icon.

2. In the Navigation area, double-click the Service Focal Point icon.

54 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

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. Select one or more managed systems from the list, and click Enable or Disable. Surveillance notification is then either enabled or disabled for the selected managed systems.

Working With Serviceable Events

You can view, add, or update serviceable event information, including error details.

Viewing Serviceable Events

To view serviceable events, you must be a member of one of the following roles:

v System Administrator v Service Representative v Advanced Operator v Operator v Viewer

To view a serviceable event, do the following:

1. In the Navigation area, click the Service Applications icon.

2. In the Navigation area, double-click the Service Focal Point icon.

3. In the Contents area, click Select Serviceable Event.

4. Designate the set of serviceable events you want to view. When you are finished, click OK.

5. The Serviceable Event Overview window opens, and the entries displayed are ordered by time stamp. Each line in the Serviceable Event Overview window corresponds to one error within a serviceable event. On this window, designate the set of serviceable events you want to view by specifying your search criteria (such as event status or error class).

Note: Only events that match all of the criteria that you specify are shown.

6. When you are finished, click OK.

When you select a line in the Serviceable Event Overview window, all lines in the same serviceable event are selected. To open the Serviceable Event Details window for the selected event, select the event and click Event Details.

Viewing Serviceable Event Details

To view serviceable event details, do the following:

1. Perform the steps in “Viewing Serviceable Events”.

2. The Serviceable Event Details window opens, showing extended serviceable event information, including the following:

v Status v Earliest original time stamp of any managed object v AIX error log. (The Linux system error log does not place entries into Service Focal Point.) v Should this error ever get called home? v Error was called home v Pointer to extended error-data collection on the HMC

The window’s lower table displays all of the errors associated with the selected serviceable event. The information is shown in the following sequence:

v Failing device system name v Failing device machine type/model/serial v Error class

Chapter 2. Diagnostic Overview 55

v Descriptive error text

Viewing Serviceable Event Error Details: To view serviceable event error details, do the following:

1. Perform the steps in “Viewing Serviceable Event Details” on page 55.

2. Select an error in the lower table, and click Error Details.

Viewing Service Processor Error Details: To view service processor error details, do the following:

1. Perform the steps in “Viewing Serviceable Event Error Details”.

2. If the serviceable event error details you are viewing are for a service processor-class error, the lower table on the resulting window contains service processor errors. Select a service processor error from the lower table, and click Service Processor Error Details to see further details.

Saving and Managing Extended Error Data

To save extended error (EE) data, do the following:

1. Perform the steps in “Viewing Serviceable Event Details” on page 55.

2. Click Save EE Data. To save extended error data for only one error associated with the serviceable event (rather than for the entire serviceable event), select the error from the lower table, and click

Error Details. In the next menu, click Manage EE Data.

Viewing and Adding Serviceable Event Comments

To add comments to a serviceable event, you must be a member of the Service Representative or System Administrator roles.

To add comments to a serviceable event, do the following:

Note: You cannot edit or delete previous comments.

1. Perform the steps in “Viewing Serviceable Event Details” on page 55.

2. Select the error to which you want to add comments to and click Comments. If you want to close the event and add comments, click Close Event from this window. The Serviceable Event Comments window opens.

3. Type your name and add comments as appropriate. You can also review previous comments, but you cannot edit this information.

4. If you clicked Comments on the Serviceable Event Details window, clicking OK commits your entry and returns you to the Serviceable Event Details window.

If you clicked Close Event on the Serviceable Event Details window, clicking OK commits all changes and opens the Update FRU Information window. For more information about updating field replaceable unit information, see “Updating Field Replaceable Unit (FRU) Information” on page 57.

Closing a Serviceable Event

To close a serviceable event, do the following:

1. Perform the steps in “Viewing Serviceable Event Details” on page 55.

2. Click Close Event from this window. The Serviceable Event Comments window opens.

3. Click OK to commit your comments. The Update FRU Information window displays. For information on completing this window, see “Updating Field Replaceable Unit (FRU) Information” on page 57. To close the serviceable event, click OK on the Update FRU Information window .

Note: You must close a serviceable event after it has been serviced to ensure that if a similar error is

reported later, it is called home. If an old problem remains open, the new similar problem is reported as a duplicate. Duplicate errors are neither reported nor called home to a service center. Close a serviceable event when the partition that reports the error is active. Closing the event causes the new status of the serviceable event to be correctly sent to the partition.

56 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

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.

To update FRU information, do the following:

1. Perform the steps in “Viewing Serviceable Event Details” on page 55.

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. The changes from the lower table are committed by clicking OK or Apply.

From this window, you can also activate and deactivate LEDs and search for other serviceable events that contain the same FRU entries.

Replacing an Existing FRU

To replace a part already listed for this serviceable event, do the following:

1. Perform the steps in “Updating Field Replaceable Unit (FRU) Information”.

2. In the upper table, double-click the part you want to replace.

3. If the FRU has a new part number, type it in the New FRU Part Number field.

4. Click Replace FRU. The Update FRU Information window displays the FRU replacement information in the lower table. Click OK or Apply to commit the changes to the serviceable event.

Adding a New FRU

You can add a part to the serviceable event that was not listed in the upper table of the Update FRU Information window. To add a new FRU for this serviceable event, do the following:

1. Perform the steps in “Updating Field Replaceable Unit (FRU) Information”.

2. Click Add New FRU.

3. Type the FRU’s location code and its part number in the appropriate fields.

4. Click Add to List. The Update FRU Information window opens and displays the newly added FRU in the lower table.

5. Click OK or Apply to commit these changes to the serviceable event.

Note: After you click OK or Apply, you cannot change this information. If you clicked the Close Event

button in the Serviceable Event Details window, then clicking OK also completes the close dialog and changes the status of the serviceable event to Closed.

Viewing Serviceable Event Partition Information

You can view partition information associated with this serviceable event. This information includes each affected partition’s state and resource use.

1. Perform the steps in “Viewing Serviceable Event Details” on page 55.

2. Click Partition Information.

Activating and Deactivating FRU LEDs

This task allows you to activate or deactivate a managed system’s system attention LED or any FRU LED. FRU LEDs are helpful in determining which FRUs need servicing.

To activate or deactivate a managed system’s system attention LED, do the following:

1. In the Navigation area, click the Service Applications icon.

2. In the Navigation area, double-click the Service Focal Point icon.

3. In the Contents area, select Hardware Service Functions. The LED Management window opens.

4. In the LED Management window, select one or more managed systems from the table.

Chapter 2. Diagnostic Overview 57

5. Select either Activate LED or Deactivate LED. The associated System Attention LED is then either turned on or off.

To activate or deactivate a FRU associated with a particular managed system, do the following:

1. In the Navigation area, click the Service Applications icon.

2. In the Navigation area, double-click the Service Focal Point icon.

3. In the Contents area, click Hardware Service Functions. The LED Management window opens.

4. In the LED Management window, select one managed system from the table.

5. Click the List FRUs... button. The list of FRU slot indexes and their respective current LED states display.

6. Select one or more FRU slot indexes.

7. Click either the Activate LED or the Deactivate LED button.

The associated FRU LEDs are now either enabled (blinking) or off.

Accessing System Log Error Information

Note: The system attention LED can be reset by following the procedures described in “Resetting the

System Attention LED” on page 60.

When an error is detected by the system, the attention LED on the operator panel is turned on. Information about the error or potential problem is stored in error logs. The following sections explain how to access the logs that are available on a system. The error logs are accessed from the console that is used to manage the system. From the following console descriptions, go to the instructions under the heading that best describes the system on which you are working:

v “Accessing Errors when a System is Attached to an HMC”. v “Accessing Errors when a System is Running AIX and the Console is Not an HMC” on page 59. v “Accessing Errors when a System is Running Linux and the Console is Not an HMC” on page 59.

Accessing Errors when a System is Attached to an HMC

If the system attention LED comes on and the system is attached to an HMC for its console, do the following to access the error logs:

1. Open the Service Action Event Log in the Service Focal Point application on the HMC.

2. Check the open service events using the procedure described in ″Working with Serviceable Events″ in the 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.

Events requiring customer intervention are marked Call Home Candidate? NO. For each of these events, examine the description in the serviceable event error details. If actions are listed in the description, perform those actions. If the error indicates a loss of surveillance between the HMC and a partition, check the status of the partition, the network, and the cabling between the HMC and the partition. Correct any problems found. If a surveillance problem is still indicated, call service support.

If the service action event is labeled Call Home Candidate? YES, an error code is supplied to identify the problem. If the system is configured to automatically call home on error, the request for service is placed.

If the system attention LED comes on and an HMC is used to manage the system, do one of the following: v If you performed “Step 1321-43” on page 99 in “MAP 1321: Quick Entry MAP for Systems with Service

Focal Point” on page 87, return to “Step 1321-43” on page 99 to process any other symptoms.

58 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

v If you have not performed any of the steps in “MAP 1321: Quick Entry MAP for Systems with Service

Focal Point” on page 87, go to step “Step 1321-1” on page 87 and perform the procedures in the MAP.

Accessing Errors when a System is Running AIX and the Console is Not an HMC

If the system attention LED comes on and the system is running AIX and the console is not an HMC, do the following to access the error logs:

1. If the system is operational, examine the AIX error log to see if user intervention is required.

2. If the system is powered off, examine the service processor error log for entries.

3. If the AIX error log indicates service support is required, or there are entries in the service processor error log, go to “Entry MAP” on page 61 with the information noted from the error log.

Accessing Errors when a System is Running Linux and the Console is Not an HMC

If the system attention LED comes on and the system is running Linux and is not attached to an HMC, do one of the following:

v If you performed “Step 1321-43” on page 99 in “MAP 1321: Quick Entry MAP for Systems with Service

Focal Point” on page 87, return to “Step 1321-43” on page 99 to process any other symptoms.

v If you have not performed any of the steps in “MAP 1321: Quick Entry MAP for Systems with Service

Focal Point” on page 87, go to step “Step 1321-1” on page 87 and perform the procedures in the MAP.

Chapter 2. Diagnostic Overview 59

Resetting the System Attention LED

Choose one of the following procedures to reset your attention LED.

Resetting the LED when a System is Attached To an HMC

To reset the system attention LED on HMC-attached systems, do the following:

1. On the HMC graphical interface, click Service Applications.

2. Double-click Service Focal Point.

3. In the Contents area of the screen, select Hardware Service Functions. The LED Management window opens.

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 Hardware Management Console for pSeries Installation and Operations Guide.

Resetting the LED when a System is Running AIX and the Console is not an HMC

As a user with root authority, type diag on the AIX command line, and do the following:

1. Select Task Selection.

2. On the Task Selection Menu, select Identify and Attention Indicators.

3. When the list of LEDs displays, use the cursor to highlight Set System Attention Indicator to Normal.

4. Press Enter, and then press F7 to commit. This action turns off the LED.

If the system is powered off, access the service processor menus. From the service processor main menu, do the following:

1. Select System Information Menu.

2. Select LED Control Menu.

3. Select Clear System Attention Indicator. This action turns off the LED.

Resetting the LED when a System is Running Linux and the Console is not an HMC

The system must be powered off to access the service processor menus. From the service processor main menu, do the following:

1. Select System Information Menu.

2. Select LED Control Menu.

3. Select Clear System Attention Indicator. This action turns off the LED.

60 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Chapter 3. Maintenance Analysis Procedures (MAPs)

This chapter contains Maintenance Analysis Procedures (MAPs) for the pSeries 630 Model 6C4 and Model 6E4.

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. The AIX error log and SMIT are only available when diagnostics are run from the hard drive. Always check Service Focal Point for any open service events in Service Action Event log.

Note: Online AIX diagnostics from the hard drive are not available when the running operating system is

Linux.

If this system has a IBM Hardware Management Console for pSeries Installation and Operations Guide(HMC) with Service Focal Point (SFP) and you have not previously been directed to MAP 1321, go to “MAP 1321: Quick Entry MAP for Systems with Service Focal Point” on page 87. Otherwise, use the following table to help determine your next step.

Notes:

1. If a network adapter is replaced, the network administrator must be notified so that the client IP addresses used by the system can be changed. In addition, the operating system configuration of the network controller may need to be changed in order to enable system startup. Also check to ensure that any client or system that addresses this system is updated.

Note: The various codes that might display on the HMC are all listed as error codes by Service Focal

Point (SFP). To assist you in identifying the types of error data in this guide, use the following table.

SFP Name Number of Digits in Error

Code

Error Code Any Contains # Menu Goal

Error Code Any Contains - (hyphen) SRN

Error Code 5 Does not contain # or - SRN

Error Code 6 Does not contain # or - Error Code

Error Code 8 Does not contain # or - Error Code, SRC, or Ref

Error code Service Guide Name

Code

Symptom Starting Point

You have a problem that does not prevent the system from booting and the media subsystem operator panel is functional.

You do not have a symptom. Go to MAP 0020 in the RS/6000 Eserver pSeries

You have an SRN, from a partition running Linux, that is one of the following: 651-88x, 651-89x, 652-88x, 652-89x, Axx-xxx, or Axx-xxxx.

You have an SRN, from a partition running Linux, that is not one of the following: 651-88x, 651-89x, 652-88x, 652-89x, Axx-xxx, or Axx-xxxx.

You have an SRN from a partition running AIX or AIX standalone diagnostics

The system stops and a 3-digit number is displayed in the operator panel display.

The system stops and a 4-digit number beginning with 0 or 2 is displayed in the operator panel display.

All other symptoms. Go to “Quick Entry MAP” on page 63.

Go to the Fast Path MAP in the RS/6000 Eserver

pSeries Diagnostic Information for Multiple Bus Systems.

Diagnostic Information for Multiple Bus Systems.

Go to Chapter 11, “SRNs for Linux”, on page 529 and perform the actions listed there.

Go to the Fast Path MAP in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

Record SRN 101-xxx, where xxx is the 3-digit number displayed in the operator panel display, then go to the Fast Path MAP in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

Go to the Fast Path MAP in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

62 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide

Quick Entry MAP

The following is a Quick Entry MAP table of contents.

Problem Description Page No.

Service actions 64

The rack indicator LED does not operate as expected. 64

The system attention LED on the operator panel is on. 64

OK does not appear in the operator panel display before pressing the power-on button. Other symptoms appear in the operator panel display or LEDs before the power-on button is pressed.

8-digit error codes 65

System stops with an 8-digit number displayed 65

System stops with a 4-digit number displayed that does not begin with 0 or 2. 65

System stops with a 3-digit number displayed (see below for 888 sequence). 65

Hardware Management Console (HMC) Problem 65

There appears to be a display problem (distortion, blurring, etc.) 66

Power and cooling problems 66

888 sequence in operator panel display 66

IBM pSeries 630 6C4, pSeries 630 6E4 Service Manual

Specifications and Main Features

Frequently Asked Questions

User Manual