IBM 9114-275, IntelliStation POWER 9114 275 Service Manual

Download

IntelliStation POWER 911 4 Model 275

Service Gui d e

򔻐򗗠򙳰

SA38-0636-00

IntelliStation POWER 911 4 Model 275

Service Gui d e

򔻐򗗠򙳰

SA38-0636-00

First Edition (July 2003)

Before using this information and the product it supports, read the information in “Safety Notices” on page ix, Appendix A, “Environmental Notices,” on page 311, and Appendix B, “Notices,” on page 313.

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, 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix

Electrical Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x

Laser Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi

Laser Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi

Data Integrity and Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

ISO 9000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

Highlighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

Accessing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

Ergonomic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

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

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

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

Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Media Bays and Media Backplane . . . . . . . . . . . . . . . . . . . . . . . . . .2

Disk Drives and Disk Drive Backplane . . . . . . . . . . . . . . . . . . . . . . . .3

Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Powering the System On and Off . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Power-On Self-Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

POST Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

POST Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

System Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Power Supply Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Fan Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

System Backplane Locations . . . . . . . . . . . . . . . . . . . . . . . . . . .11

PCI-X Slot Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Memory DIMM Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Operator Panel Component Locations . . . . . . . . . . . . . . . . . . . . . . . .15

SCSI IDs and Bay Locations . . . . . . . . . . . . . . . . . . . . . . . . . . .16

System LED Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

System Logic Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Location Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Physical Location Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Location Code Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

AIX Location Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Mapping AIX and Physical Location Codes . . . . . . . . . . . . . . . . . . . . . . .23

AIX and Physical Location Code Table . . . . . . . . . . . . . . . . . . . . . . . .25

System Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

External AC Power Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Service Inspection Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Chapter 2. Diagnostic Overview . . . . . . . . . . . . . . . . . . . . . . . . . .33

Maintenance Analysis Procedures (MAPs) . . . . . . . . . . . . . . . . . . . . . . .33

System LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

iii

System Attention LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

FRU Isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

FRU Identify LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Service Agent for the Model 275 . . . . . . . . . . . . . . . . . . . . . . . . . . .36

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

Service Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Service Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Service Focal Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Accessing System Log Error Information . . . . . . . . . . . . . . . . . . . . . . . .38

Accessing Errors when a System is Running AIX . . . . . . . . . . . . . . . . . . . .38

Accessing Errors when a System is Running Linux . . . . . . . . . . . . . . . . . . .38

Resetting the System Attention LED . . . . . . . . . . . . . . . . . . . . . . . . .38

Resetting the LED when a System is Running AIX . . . . . . . . . . . . . . . . . . .38

Resetting the LED when a System is Running Linux . . . . . . . . . . . . . . . . . .39

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

Entry MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Quick Entry MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

MAP 1020: Problem Determination . . . . . . . . . . . . . . . . . . . . . . . . . .49

MAP 1240: Memory Problem Resolution . . . . . . . . . . . . . . . . . . . . . . . .55

MAP 1320: Service Focal Point . . . . . . . . . . . . . . . . . . . . . . . . . . .60

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

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

MAP 1520: Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

FRU Identify LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

MAP 1521: System Unit With Power Failure and No Error Codes . . . . . . . . . . . . . . .78

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

MAP 1540: Problem Isolation Procedures . . . . . . . . . . . . . . . . . . . . . . .87

FRU Identify LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

MAP 1541: JTAG Problem Isolation . . . . . . . . . . . . . . . . . . . . . . . . . .89

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

MAP 1548: System Processor Problem Isolation . . . . . . . . . . . . . . . . . . . . .90

MAP 1549: Attention Problem Isolation . . . . . . . . . . . . . . . . . . . . . . . . 101

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

Chapter 4. Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

IPL Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Service Processor Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Firmware Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

Boot Problems/Concerns . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

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

Performing a Slow Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Confirming the Initial Error Code . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Four-Character Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Replacing the Operator Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Replacing the Network Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Determining Location Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

FRU Identify LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Checkpoint and Error Code Index . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Operator Panel Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

SPCN Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Firmware Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Service Processor Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

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

iv IntelliStation POWER 9114 Model 275 Service Guide

Error Log Utility Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

System Firmware Update Messages . . . . . . . . . . . . . . . . . . . . . . . . . 171

Scan Dump Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Common Firmware Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Scan Log Dump Progress Codes . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Problem Determination Generated Error Codes . . . . . . . . . . . . . . . . . . . . . 183

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

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

Identifying the Terminal Type to the Diagnostics . . . . . . . . . . . . . . . . . . . . 185

Undefined Terminal Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Resetting the Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Online Diagnostics Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . 186

Service Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Concurrent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Maintenance Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Standalone Diagnostic Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 189

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

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

Booting Standalone Diagnostics from the NIM Server . . . . . . . . . . . . . . . . . . 191

Chapter 7. Using the Service Processor . . . . . . . . . . . . . . . . . . . . . . . 193

Service Processor Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Accessing the Service Processor Menus Locally . . . . . . . . . . . . . . . . . . . 193

Accessing the Service Processor Menus Remotely . . . . . . . . . . . . . . . . . . . 193

Saving and Restoring Service Processor Settings . . . . . . . . . . . . . . . . . . . 193

Menu Inactivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

General User Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Privileged User Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Service Processor Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

System Power Control Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

System Information Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Language Selection Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

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

Modem Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Serial Port Selection Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Serial Port Speed Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Telephone Number Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Call-Out Policy Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Customer Account Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Call-out Test Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Service Processor Parameters in Service Mode . . . . . . . . . . . . . . . . . . . . . 215

System Power-On Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Service Processor Reboot/Restart Recovery . . . . . . . . . . . . . . . . . . . . . . 216

Boot (IPL) Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Failure During Boot Process . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Failure During Normal System Operation . . . . . . . . . . . . . . . . . . . . . . 216

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

System Firmware Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

General Information on System Firmware Updates . . . . . . . . . . . . . . . . . . . 218

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

System Firmware Update Using a Locally Available Image . . . . . . . . . . . . . . . . 219

Updating System Firmware from the Service Processor Menus . . . . . . . . . . . . . . 220

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

Contents v

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

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

Recovery Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Configuring and Deconfiguring Processors or Memory . . . . . . . . . . . . . . . . . . 221

Run-Time CPU Deconfiguration (CPU Gard) . . . . . . . . . . . . . . . . . . . . . 221

Service Processor System Monitoring - Surveillance . . . . . . . . . . . . . . . . . . . 222

System Firmware Surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Operating System Surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Call-Out (Call-Home) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Console Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Service Processor Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

LCD Progress Indicator Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Service Processor Operational Phases . . . . . . . . . . . . . . . . . . . . . . . . 226

Pre-Standby Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Standby Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Bring-Up Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Runtime Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Chapter 8. Using System Management Services . . . . . . . . . . . . . . . . . . . 229

Select Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Change Password Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Set Privileged-Access Password . . . . . . . . . . . . . . . . . . . . . . . . . 231

View Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

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

Change SCSI Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Select Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Select Boot Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Select Boot Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Display Current Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Restore Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Multiboot Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Exiting System Management Services . . . . . . . . . . . . . . . . . . . . . . . . 242

Chapter 9. Removal and Replacement Procedures . . . . . . . . . . . . . . . . . . . 243

Handling Static-Sensitive Devices . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Procedure List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Stopping the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Starting the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Placing the Model 275 into the Service and Operating Position . . . . . . . . . . . . . . . 248

Covers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Removing the Service Access Cover . . . . . . . . . . . . . . . . . . . . . . . . 249

Replacing the Service Access Cover . . . . . . . . . . . . . . . . . . . . . . . . 249

Bezel Door . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Removing the Bezel Door . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Replacing the Bezel Door . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Bezels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Removing the Front Bezel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Replacing the Front Bezel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

PCI Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Removing a Non-Hot-Pluggable PCI Adapter . . . . . . . . . . . . . . . . . . . . . 253

Replacing or Installing a Non-Hot-Pluggable PCI Adapter . . . . . . . . . . . . . . . . 255

PCI Adapter Dividers and Light Pipes . . . . . . . . . . . . . . . . . . . . . . . . 257

Removing a PCI Adapter Divider . . . . . . . . . . . . . . . . . . . . . . . . . 257

Replacing a PCI Adapter Divider . . . . . . . . . . . . . . . . . . . . . . . . . 258

Removing the PCI-Adapter-Divider Light Pipes . . . . . . . . . . . . . . . . . . . . 259

vi IntelliStation POWER 9114 Model 275 Service Guide

Replacing the PCI-Adapter-Divider Light Pipes . . . . . . . . . . . . . . . . . . . . 259

Service Processor Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Removing the Service Processor Assembly . . . . . . . . . . . . . . . . . . . . . 260

Replacing the Service Processor Assembly . . . . . . . . . . . . . . . . . . . . . 262

Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Before Replacing the Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Hot-Swap System Fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Removing a Hot-Swap System Fan . . . . . . . . . . . . . . . . . . . . . . . . 266

266

Replacing a Hot-Swap System Fan . . . . . . . . . . . . . . . . . . . . . . . . 267

Fan Tray Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Removing the Fan Tray Assembly . . . . . . . . . . . . . . . . . . . . . . . . . 268

Replacing the Fan Tray Assembly . . . . . . . . . . . . . . . . . . . . . . . . . 269

Media Devices (Diskette, DVD, DVD-RAM,or Tape Drive) . . . . . . . . . . . . . . . . . 271

Slimline Media Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

272

SCSI Media Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Disk Drive Bezels and Fillers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Removing a Disk Drive Bezel from a Disk Drive or Filler . . . . . . . . . . . . . . . . 275

Replacing or Installing a Disk Drive Bezel onto a Disk Drive . . . . . . . . . . . . . . . 275

Hot-Swap Disk Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Deconfiguring a Disk Drive for Removal . . . . . . . . . . . . . . . . . . . . . . . 276

Configuring a Disk Drive after Replacement or Installation . . . . . . . . . . . . . . . . 276

Removing a Hot-Swap Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . 277

Replacing or Installing a Hot-Swap Disk Drive . . . . . . . . . . . . . . . . . . . . 279

Removing a Hot-Swap Disk Drive with the System Power Off . . . . . . . . . . . . . . . 280

Replacing or Installing a Hot-Swap Disk Drive with the System Power Off . . . . . . . . . . 280

Disk Drive Backplane and Filler . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Removing the Disk Drive Backplane or Filler . . . . . . . . . . . . . . . . . . . . . 281

Replacing the Disk Drive Backplane or Filler . . . . . . . . . . . . . . . . . . . . . 282

Operator Panel and Power Cable . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Removing the Operator Panel . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Replacing the Operator Panel . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Removing the Operator Panel Power Cable . . . . . . . . . . . . . . . . . . . . . 284

Replacing the Operator Panel Power Cable . . . . . . . . . . . . . . . . . . . . . 284

Media Bay Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Removing the Media Bay Chassis . . . . . . . . . . . . . . . . . . . . . . . . . 285

Replacing the Media Bay Chassis . . . . . . . . . . . . . . . . . . . . . . . . . 286

Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Power Supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Removing a Power Supply with the System Power Off . . . . . . . . . . . . . . . . . 288

Replacing a Power Supply with the System Power Off . . . . . . . . . . . . . . . . . 290

Installing or Replacing a Power Supply with the System Power On . . . . . . . . . . . . . 291

Memory DIMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Removing Memory DIMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Replacing or Installing Memory DIMMs . . . . . . . . . . . . . . . . . . . . . . . 294

Voltage Regulator Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Removing Voltage Regulator Modules . . . . . . . . . . . . . . . . . . . . . . . 295

Replacing Voltage Regulator Modules . . . . . . . . . . . . . . . . . . . . . . . 296

System Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Removing the System Backplane . . . . . . . . . . . . . . . . . . . . . . . . . 297

Replacing the System Backplane . . . . . . . . . . . . . . . . . . . . . . . . . 299

Chapter 10. Parts Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

System Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Model 275 Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Internal Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Contents vii

Power Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Keyboards and Mouse (White) . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Keyboards and Mouse (Black) . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Chapter 11. Component and Attention LEDs . . . . . . . . . . . . . . . . . . . . . 309

Operator Panel Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Component LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Appendix A. Environmental Notices . . . . . . . . . . . . . . . . . . . . . . . .311

Product Recycling and Disposal . . . . . . . . . . . . . . . . . . . . . . . . . . .311

Environmental Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311

Acoustical Noise Emissions . . . . . . . . . . . . . . . . . . . . . . . . . . . .311

Declared Acoustical Noise Emissions . . . . . . . . . . . . . . . . . . . . . . . .311

Appendix B. Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

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

Service Processor Setup Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Testing the Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Testing Call-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Testing Call-Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Serial Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Appendix D. General Attributes Required When Using a TTY Terminal . . . . . . . . . . . 319

Additional Communication Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 320

Additional Keyboard Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

Additional Printer Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Appendix E. Modem Configurations . . . . . . . . . . . . . . . . . . . . . . . . 323

Sample Modem Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . 323

Generic Modem Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . 323

Specific Modem Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . 323

Configuration File Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Examples for Using the Generic Sample Modem Configuration Files . . . . . . . . . . . . 325

Customizing the Modem Configuration Files . . . . . . . . . . . . . . . . . . . . . 326

IBM 7852-400 DIP Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . 327

Xon/Xoff Modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Ring Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Terminal Emulators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Recovery Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Transfer of a Modem Session . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Recovery Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Prevention Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Modem Configuration Sample Files . . . . . . . . . . . . . . . . . . . . . . . . . 331

Sample File modem_m0.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Sample File modem_m1.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Sample File modem_z.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

Sample File modem_z0.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

Sample File modem_f.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

Sample File modem_f0.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Sample File modem_f1.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

viii IntelliStation POWER 9114 Model 275 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 x v 76 v 77 v 243 v 287

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 x v xi v 76 v 244 v x v 264

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

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

prevent electrical shock hazard, disconnect all power cables from the electrical outlet before

To relocating the system.

D01

CAUTION:

A lithium battery can cause fire, explosion, or a severe burn. Do not recharge, disassemble, heat above 100 degrees C (212 degrees F), solder directly to the cell, incinerate, or expose cell contents to water. Keep away from children. Replace only with the part number specified for your system. Use of another battery may represent a risk of fire or explosion.

The battery connector is polarized; do not attempt to reverse the polarity.

Dispose of the battery according to local regulations.

DANGER

not attempt to open the covers of the power supply. Power supplies are not serviceable and

Do are to be replaced as a unit.

D02

x IntelliStation POWER 9114 Model 275 Service Guide

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

Laser Compliance

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

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

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

C26

C25,

Safety Notices xi

xii IntelliStation POWER 9114 Model 275 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.

xiii

xiv IntelliStation POWER 9114 Model 275 Service Guide

About This Book

This book provides maintenance information that is specific to the IntelliStation POWER 9114 Model 275, 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 IntelliStation POWER 9114 Model 275 is 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 unit.

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.

Related Publications

The following publications provide additional information about your system: v The IntelliStation POWER 9114 Model 275 Installation Guide, order number SA38-0634, contains

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

operation. v The IntelliStation POWER 9114 Model 275 User’s Guide, order number SA38-0635, contains

information to help users use the system, use the service aids, and solve minor problems. 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 Site and Hardware Planning Information, 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.

Ergonomic Information

After you have set up your system, we encourage you to visit the Healthy Computing Web site. Good ergonomic practice is important to get the most from your workstation and to avoid discomfort. This means that the equipment and the workplace should be arranged to suit your individual needs and the kind of work you do.

The Healthy Computing Web site gives ergonomic guidelines to help you understand the ergonomic considerations that you should know when working at a computer workstation. The address is: http://www.us.pc.ibm.com/healthycomputing

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 IntelliStation v LANstreamer v PowerPC v pSeries v RS/6000

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

Other

xvi IntelliStation POWER 9114 Model 275 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 “Overview” v “System Features” on page 2 v “Input/Output Ports” on page 4 v “Security Features” on page 5 v “Powering the System On and Off” on page 5 v “Console” on page 5 v “POST Indicators” on page 6 v “POST Keys” on page 6 v “System Locations” on page 7 v “System Logic Flow” on page 18 v “Location Codes” on page 19 v “Mapping AIX and Physical Location Codes” on page 23 v “System Cables” on page 28 v “Specifications” on page 29 v “External AC Power Cables” on page 30 v “Service Inspection Guide” on page 31

Overview

This chapter provides information about the system features of the IntelliStation POWER 9114 Model 275 .

The Model 275 can be configured as a 1-way to 2-way symmetric multiprocessing (SMP) system. It has up to four disk drives and six PCI adapters. Redundant power supplies and cooling fans are supported.

Note: Hot-plug PCI adapters are not supported on this model.

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

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

v IDE DVD-ROM drive v Diskette drive

Another full-height (1 inch) media bay supports a SCSI tape drive or DVD-RAM drive.

A DVD-ROM and diskette drive are recommended for use in the base configuration of this model.

Note:

System Features

Processors

v One-way and two-way processor DCMs (double chip modules) are available. v One 1.45 GHz L3 cache is contained in the processor DCM.

Memory

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

random-access memory).

v Memory DIMMs plug into the system backplane (8 DIMM slots). v DIMMs must be populated in quads (a single memory feature contains four DIMMs). v Memory quads can be different memory sizes. v A system can have a maximum of 16 GB of memory.

Media Bays and Media Backplane

Two Slimline media bays and one full-height media bay are provided. The Slimline media bays are for IDE optical devices or diskette drives. The full-height bay is for a SCSI tape drive or DVD-RAM drive.

1 System Unit 5 Blue Retaining Ta b (For Slimline Devices) 2 Optional SCSI Media Device

6 Front Bezel

(Shown in Media Bay Chassis)

3 Media Bay Chassis 7 Slimline Diskette or Optical Device (Media Bay

4 Optional SCSI Media Device

8 Slimline Optical Device (Media Bay 1)

Screw (3)

Note: The following restrictions apply to the media drives:

v Media devices are not hot-pluggable. v The first optical device, such as a DVD-ROM device, can only be plugged into media bay 1.

Media bay 1 is the right drive slot.

v Media bay 2, the left Slimline bay, accepts a second optical device or the single, supported,

floppy drive.

2 IntelliStation POWER 9114 Model 275 Service Guide

v An error occurs if two diskette drives are installed simultaneously in the Slimline bays.

media backplane plugs into the system backplane and provides connections for the operator panel as

The well as the devices in the media bays.

v Media bay 1 can accommodate a Slimline IDE DVD-ROM or a diskette drive. v Media bay 2 can accommodate a Slimline DVD-ROM. v Media bay 3 can accommodate a SCSI DVD-RAM or tape drive.

Note: A built-in external SCSI port is not provided. Customers can use an optional SCSI adapter for

connections to an external SCSI subsystem.

For an updated listing of hot-swappable disk-drive sizes, contact your sales representative.

Disk Drives and Disk Drive Backplane

The system supports one DASD backplane that supports four disk drives. This backplane is standard on the system and is located next to the media backplane. Disk drives of different sizes and speeds can be mixed on this system. The following types of disk drives are supported:

v 36.4 GB Ultra160 10K RPM v 73.4 GB Ultra160 10K RPM v 146.8 GB Ultra160 10K RPM v 36.4 GB Ultra160 15K RPM v 73.4 GB Ultra160 15K RPM v 146.8 GB Ultra160 15K RPM

Power Supplies

Two power supplies maximum per system; the second power supply is for redundant power:

v ac input type 100-127V ac or 200-240V ac v Single phase

Keyboard

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

Mouse

v Three-button

Operator Panel

v 32-character LED diagnostics display. v LEDs for power on and attention. v Power-on button. v System reset button – Dumps AIX (if dump is enabled) and reboots. v Service processor reset switch – Resets the service processor into standby mode. The service

processor reset switch is the pinhole located above the system reset button on the operator panel.

Chapter 1. Reference Information 3

Input/Output Ports

v One 25-pin parallel v Keyboard v Mouse v One Dual channel Ultra320 SCSI bus, to which the internal 4-pack disk drive backplanes are connected v Integrated Drive Electronics (IDE) v Two System Power Control Network (SPCN) Connectors v One 10/100 Ethernet and One 1 Gigabit Ethernet (IEEE 802.3 compliant) v Three serial ports located on the rear of the chassis

1 Serial Port 1 Connector 2 Serial Port 2 Connector 3 Serial Port 3 Connector 4 Parallel Connector

Current usage for the serial port connectors are as follows:

Serial Port Number Location Examples of Applicable Usage

Serial Port 1 (S1 Rear)

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

applications (interface cable required), ASCII Terminal for operating system Console, and Modems

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

system Console, and Modems

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

operating system Console, and Modems

Notes:

1. Serial port S1 is never used to run HACMP or to 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 S2 and the UPS cable to serial port S3. Do not run a UPS connected to serial port S2. If you decide to 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.

4 IntelliStation POWER 9114 Model 275 Service Guide

Security Features

The Model 275 allows you to 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.

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 the System” on page 246 and “Starting the System” on page 247.

Console

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 (keyboard installed or removed, mouse

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

console-selection sequence allows you to select (from the appropriate input device) any one of the

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

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

the

After a console has been selected, the console-selection sequence is only started at boot time 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 loaded, 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 loaded. 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.

Chapter 1. Reference Information 5

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.

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 system unit 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 AIX diagnostics from CD-ROM.

The default boot sequence is:

1. Diskette (if installed)

2. DVD-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 or the service processor menus.

6 IntelliStation POWER 9114 Model 275 Service Guide

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

System Locations

The locations listed in this section can be used to help identify a component of the system.

Model 275

Front View

1 Operator Panel 2 Slimline Media Bay 3 Slimline Media Bay 4 SCSI Media-Device Bay 5 Disk Drives

Chapter 1. Reference Information 7

Rear View

2 3 4 5 6

1 Parallel Connector 9 Mouse 2 Keyboard 10 1 Gb Ethernet Connector 3 Serial Connector 2 11 10/100 Gb Ethernet Connector 4 Serial Connector 3 12 Reserved 5 Test Connector (For Manufacturing

13 Reserved

Use Only)

6 Serial Connector 1 14 Primary Power Supply V2 Receptacle 7 PCI-X Slot Access 15 Redundant Power Supply V1

Receptacle

8 Rack Indicator

8 IntelliStation POWER 9114 Model 275 Service Guide

Power Supply Locations

Each power supply has three LEDs. 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 Primary Power Supply V2 4 System Unit (In Service Position) 2 Redundant Power Supply V1 5 Fault LED (Amber) 3 Power Supply Filler (Required in

6 DC Good LED (Green)

place of redundant power supply)

7 AC Good LED (Green)

Chapter 1. Reference Information 9

Fan Locations

The following illustration identifies the system cooling fans. Each fan has one green LED and one amber LED located on top of the fan. A lit amber LED indicates that the fan is not operating correctly.

1 Cooling Fan 1 3 Cooling Fan 3 2 Cooling Fan 2 4 System Unit (In Service Position)

10 IntelliStation POWER 9114 Model 275 Service Guide

System Backplane Locations

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

J3B J3A

J2B J2A

910

1112

2 3

4 5

17 18

J0A

J0B

J1A J1B

V3 V2

J3B

J3A

J2B

J2A

1 Media Backplane 15 2.5V Voltage Regulator Module (V2)

J0A

J0B J1B

J1A

2 Memory DIMM 5, J0A 16 (Hardware Management Console)

3 Memory DIMM 6, J0B 17 Primary Power Supply V2

4 Memory DIMM 7, J1A 18 Ethernet #1 10/100

5 Memory DIMM 8, J1B 19 Ethernet #2 1GB

6 DASD Backplane 20 Service Processor Assembly

7 (Reserved) 21 PCI-X Slot 1

8 (Reserved) 22 PCI-X Slot 2

9 Memory DIMM 1, J3B 23 PCI-X Slot 3

10 Memory DIMM 2, J3A 24 PCI-X Slot 4

11 Memory DIMM 3, J2B 25 PCI-X Slot 5

12 Memory DIMM 4, J2A 26 PCI-X Slot 6

13 Redundant Power Supply V1 27 1.2V Voltage Regulator Module (V3)

14 1.8V Voltage Regulator Module (V1)

Chapter 1. Reference Information 11

PCI-X Slot Locations

Six PCI-X slots are available. Slots 1, 4, 5, and 6 are 64-bit capable at 133 MHz, 3.3 volts. Slots 2 and 3 are 32-bit capable at 66 MHz, 3.3 volts. All slots have hot-swap capabilities. The slots are numbered on the rear of the chassis from left to right, 1 through 6.

All PCI-X slots are capable of running 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 PCI-X Slot 1 4 PCI-X Slot 4 2 PCI-X Slot 2 5 PCI-X Slot 5 3 PCI-X Slot 3 6 PCI-X Slot 6

12 IntelliStation POWER 9114 Model 275 Service Guide

Memory DIMM Locations

The memory DIMMs used in the system are located on the system backplane. Your system contains eight memory DIMM slots. Associated with each memory DIMM slot is an LED, which is located on the edge of the system backplane. A lit LED indicates a problem with a specific memory DIMM. For more information on the locations of the system LEDs, go to “System LED Locations” on page 17. 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. Exchange each DIMM, starting the system after each change, until the faulty DIMM has been replaced.

Notes:

1. Memory DIMMs must be installed in quads and in the correct slots. A quad is a group of four memory DIMMs.

2. Quads are populated in DIMM slots 1, 3, 6, 8 first, and then 2, 4, 5, 7. The only two valid slot combinations that you can use are 1, 3, 6, and 8 and 2, 4, 5, and 7.

3. At least one quad of DIMMs is installed on the system backplane. See the following illustration.

4. Each memory DIMM in a quad must be the same type and size. However, both quads on the system backplane are not required to be the same.

The system must have at least four memory DIMMs installed (1 quad).

Chapter 1. Reference Information 13

J3B (U0.1-P1-M1) J3A (U0.1-P1-M2)

J2B (U0.1-P1-M3)

J2A (U0.1-P1-M4)

J0A (U0.1-P1-M5)

J0B (U0.1-P1-M6)

J1A (U0.1-P1-M7)

J1B (U0.1-P1-M8)

V3 V2 J3B

J0A

J3A

J2B

J0B J1B

J1A

J2A

Number Description Location Code

M1 Memory slot 1 (J3B) U0.1-P1-M1

M2 Memory slot 2 (J3A) U0.1-P1-M2

M3 Memory slot 3 (J2B) U0.1-P1-M3

M4 Memory slot 4 (J2A) U0.1-P1-M4

M5 Memory slot 5 (J0A) U0.1-P1-M5

M6 Memory slot 6 (J0B) U0.1-P1-M6

M7 Memory slot 7 (J1A) U0.1-P1-M7

M8 Memory slot 8 (J1B) U0.1-P1-M8

14 IntelliStation POWER 9114 Model 275 Service Guide

Operator Panel Component Locations

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

Number Component Name Component Description

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

information in the event of a hardware problem.

2 Attention LED Normal State - LED is off

3 System Reset Button Resets the system

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

standby mode). Solid - When power-on button has been pressed.

Note: There is approximately a 30-second transition period

from the time the power-on 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.

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

6 Power-On Button Guard Prevents accidental power-on and power-off operations.

7 Service Processor Reset Switch

(Pinhole)

8 Serial Number Label Displays the system serial number

Service Personnel Use

Chapter 1. Reference Information 15

SCSI IDs and Bay Locations

The following figure shows the SCSI bay locations for the Model 275.

Index Drive Name SCSI ID

1 Operator Panel

2 Diskette Drive

(U0.1-P1-X1/Q6-A1, for optical drive)

or IDE Optical Drive

3 IDE DVD-ROM (Default) IDE (Non-SCSI)

(U0.1-P1-X1/Q6-A0)

Tape Drive (Optional) SCSI ID 0

SCSI DVD-RAM (Optional) SCSI ID 1

5 Disk Drive 1 SCSI Bus 0 SCSI ID 3

6 Disk Drive 2 SCSI ID 4

7 Disk Drive 3 SCSI ID 5

8 Disk Drive 4 SCSI ID 8

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. One disk drive backplane is standard in the Model 275. In the figure above, the system is shown fully populated with one backplane and four disk drives.

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

v IDE Optical Drive v Diskette Drive

Any SCSI device used in media bay location Index 4 must be connected to a PCI SCSI adapter.

16 IntelliStation POWER 9114 Model 275 Service Guide

System LED Locations

The following illustration shows the system LED locations for the Model 275. Grey dots represent amber LEDs and black dots represent green LEDs.

Front View

Rear View

Top View

= Green LED = Amber LED

1 Disk Drive LEDs 7 Power Supply LEDs 2 Power LED 8 Service Processor Assembly LED 3 System AttentionLED 9 PCI Adapter LEDs 4 PCI Adapter LEDs 10 Voltage Regulator Modules LEDs 5 System Attention LED 11 Memory DIMM LEDs 6 Fan LEDs 12 Backplane LEDs

Chapter 1. Reference Information 17

System Logic Flow

The following diagram is a detailed representation of the system’s logic flow:

S1 Rear

S1 Frt

S2 Rear

S3 Rear

IDE (pSeries only) DVD-ROM From Winbond

Floppy

Disk

Conn

Floppy

Disk

Kbd/Mse

Parallel

XCVR

R/M

DASD

optical device

Floppy

Disk

SCSI LVD Tape

DIMM

SMI Bus

ISA

Super

I/O

Mux

1655x

DUART

VPD Conc (Part of Drexel)

32Kx8

83C51

SRAM

Ch_4_1

Ch_15_1 Ch_16_1

Op Panel

CPU VPD

Debug

YAW L

RJ45

Conn

Ultra 4 SCSI Bus 1

Ultra 4 SCSI Bus 0

WOL

PCI-X Slot 4 (64b, L)

PCI-X Slot 5 (64b, L)

PCI-X Slot6 (64b, L)

PCI-X Slot 1 (64b, L)

LVD

SCSI RAID Card (opt)

IDE

HMC 1

Ser Mux

2ea

Ch_1_2

Mem DIMMs

SCSI Ultra320 Gemstone

10/100 Enet (Scurry)

PCI-X Slot 3 (32b, S)

PCI-X Slot 2 (32b, S)

Enet 1G b ,Golia d

SMI-E

JTAG

SMI-E

Port

JTAG

RIP

PCI 32b

25MHz

Debug

Conn

XCVR

XCVRHMC 2

XCVRSPCN 1

XCVRSPCN 2

Ch_1_1

Ch_8_2

133 MHz

33 MHz

133 MHz

66 MHz

133 MHz

5,6

EADSX-1

EADSX-2

5,6

7,8

1,2

Tit an

Te l c o

I2C_2

PCI-X 64b 133MHz

Dual Chip Module

L3 Cache Data Unit

Main Stor e

Async

Cntl

8MB

Intfc

Unit

DRAM

JTAG

Fan Cntl &Status

I2C

SDRAM

32MB

SRAM

256/512KB

PPC

403

Flash

8/16MB

8B 8B

GX Bus

JTAG

EPOW

core

1.5MB L2

core

Processor Interrupt

L3 Bus

Int Bus Clk

10.2MHz Osc

JTAG

RIOG

Port

18 IntelliStation POWER 9114 Model 275 Service Guide

Location Codes

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.

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.

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-M1 is a memory DIMM (M1) plugged into a system backplane (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, P1-X1/S1 describes the location of the serial port 1 controller and its connector (S1), which is located on the system backplane P1 (its base location code), but the / (slash) 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 P1-X1/K1, which means they have the same base location code (P1-X1) as serial port 1, but a different external connector. In contrast, the location code P1-X1/K1-K1 actually points to the device connected to connector K1; that is, the keyboard.

following are examples:

The

v U0.1-P1-M1 identifies memory DIMM M1 plugged into the system backplane P1. v U0.1-P1-X1/S1 identifies serial port 1 controller on the system backplane P1 or the connector for serial

port 1.

v U0.1-P1-X1/K1-K1 identifies a keyboard K1, attached to connector K1 on system backplane P1.

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

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:

Chapter 1. Reference Information 19

AB-CD-EF-GH

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.

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.

an integrated adapter, EF-GH is the same as the definition for a pluggable adapter. For example, the

For 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

20 IntelliStation POWER 9114 Model 275 Service Guide

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 Memory DIMM 2 of on system backplane P1:

U0.1-P1-M2

Examples of AIX location codes displayed are as follows:

v Pluggable PCI adapters:

1Z-08 Any PCI card in slot 1 1c-08 Any PCI card in slot 2 1f-08 Any PCI card in slot 3 1n-08 Any PCI card in slot 4 1H-08 Any PCI card in slot 5 1V-08 Any PCI card in slot 6

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 131, a location code for a failing part may also be specified. If the location code includes a blank space followed by a lowercase x followed by a number, this is an error code with multiple FRU callouts. This error can typically happen with memory DIMMs or processors, and may involve mixed types of parts. In this case, check the system’s configuration for FRU part numbers to determine the appropriate set of FRUs.

You can determine the FRU part numbers of the electronic assemblies in the entire system by using 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).

If the system is running AIX, you can determine the FRU part numbers of the electronic assemblies in a partition by using the lscfg -vp | pg command. This command displays the detailed VPD of the electronic assemblies in the system. Notice that the FRU part number information for processors and memory DIMMs may be at the bottom of the command’s output.

If the system is running Linux, you can determine the FRU part numbers of the electronic assemblies in a partition by using the lscfg -vp | more command. This command displays the detailed VPD of the electronic assemblies in 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:

v Power subsystem FRUs v System unit FRUs

Chapter 1. Reference Information 21

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 system unit or I/O drawer identify LED to locate the failing FRU more easily.

Any identify LED in the system may 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

205..

Any identify LED in the system may 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 Chapter 27 of 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 may be flashed. If the system is configured as a full system partition, the system can be booted to the open firmware prompt and the FRU-LED-MENU command entered. A menu displays that will allow you to turn on the desired FRU identify LED. For instructions on setting the boot mode to enable the boot to the open firmware prompt, see “System Power Control Menu” on page 202.

22 IntelliStation POWER 9114 Model 275 Service Guide

Mapping AIX and Physical Location Codes

Note: AIX location codes are not available when using the Linux operating system.

Use the following illustration to help you map a location code to its connector on the system backplane.

Chapter 1. Reference Information 23

Use the following illustration to help you map a location code to its connector on the rear of the system.

AIX Location Codes

01-S1

01-S3

01-S2

01-R1

Physical Location Codes

U0.1-P1/Q1

U0.1-P1-X1/S1

U0.1-P1-X1/S3

U0.1-P1-X1/S2

U0.1-P1-X1/R1

01-K1-00

01-K1-01

1L-08

1j-08

1Z-08

1c-08

1f-08

1n-08

1H-08

1V-08

U0.1-P1-X1/K1

U0.1-P1-X1/O1

U0.1-P1-X1/Q4

U0.1-P1-X1/Q5

U0.1-P1/Q2

U0.1-P1/Q3

U0.1-P1-X1/S4

U0.1-P1-X1/S5

U0.1-P1/E1

U0.1-P1/E2

U0.1-P1-I1

U0.1-P1-I2

U0.1-P1-I3

U0.1-P1-I4

U0.1-P1-I5

U0.1-P1-I6

24 IntelliStation POWER 9114 Model 275 Service Guide

AIX and Physical Location Code Table

Note: AIX location codes are not available when using the LINUX operating system.

The following table contains AIX and physical location codes for the IntelliStation POWER 9114 Model 275 .

Component Name Physical Location Code AIX Location Code

System Unit Backplane

(Reserved) U0

System Unit Drawer U0.1

System Backplane U0.1-P1

IDE Controller U0.1-P1-X1/Q6 1G-19

IDE Optical Drive U0.1-P1-X1/Q6-A0 1G-19-00

Other Optical Drive U0.1-P1-X1/Q6-A1 1G-19-01

PHB2 U0.1-P1 1Y-10, 1Y-12, 1Y-13, 1Y-14, 1Y-16

EADS_X under PHB0 U0.1-P1

PHB1 U0.1-P1

EADS_X under PHB1 U0.1-P1 1G-10, 1G-12, 1G-14, 1G-16

Service Processor Card U0.1-P1-X1

DASD Backplane U0.1-P2

(Reserved) U0.1-P3

Media Backplane U0.1-P4

(Reserved) U0.1-P5

Memory DIMMs

Memory DIMM 1 J3B

Memory DIMM 2 J3A

Memory DIMM 3 J2B

Memory DIMM 4 J2A

Memory DIMM 5 J0A

Memory DIMM 6 J0B

Memory DIMM 7 J1A

Memory DIMM 8 J1B

Debug Connector (Manufacturing Use Only)

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

ISA Bus U0.1-P1-X1 1G-18

U0.1-P1-M1

U0.1-P1-M2

U0.1-P1-M3

U0.1-P1-M4

U0.1-P1-M5

U0.1-P1-M6

U0.1-P1-M7

U0.1-P1-M8

System Backplane Integrated Devices

Labeled Debug Connector

Chapter 1. Reference Information 25

Component Name Physical Location Code AIX Location Code

(Reserved) U0.1-P1-X1/S4

(Reserved) U0.1-P1-X1/S5

SPCN Connector1 (SPCN Port0) U0.1-P1-X1/Q4

SPCN Connector2 (SPCN Port1) U0.1-P1-X1/Q5

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

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

Mouse Port U0.1-P1-X1/O1 01-K1-01

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

Ethernet #1 Controller U0.1-P1/E1 1L-08

Ethernet #2 Controller 1Gb U0.1-P1/E2 1j-08

(Reserved) U0.1-P1/Q1

Serial Port 1 U0.1-P1-X1/S1 01-S1

Serial Port 2 U0.1-P1-X1/S2 01-S2

Serial Port 3 U0.1-P1-X1/S3 01-S3

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

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

Pluggable Adapters

PCI Slot 1 U0.1-P1/I1

PCI Slot 1 Card U0.1-P1-I1 1Z-08

PCI Slot 2 U0.1-P1/I2

PCI Slot 2 Card U0.1-P1-I2 1c-08

PCI Slot 3 U0.1-P1/I3

PCI Slot 3 Card U0.1-P1-I3 1f-08

PCI Slot 4 U0.1-P1/I4

PCI Slot 4 Card U0.1-P1-I4 1n-08

PCI Slot 5 U0.1-P1/I5

PCI Slot 5 Card U0.1-P1-I5 1H-08

PCI Slot 6 U0.1-P1/I6

PCI Slot 6 Card U0.1-P1-I6 1V-08

SCSI Controller for Internal DASD U0.1-P1/Z1 1S-08-00

SCSI Controller for Internal devices U0.1-P1/Z2 1S-08-01

Disk Drive 1 U0.1-P1/Z1-A3 1S-08-00-3,0

Disk Drive 2 U0.1-P1/Z1-A4 1S-08-00-4,0

Disk Drive 3 U0.1-P1/Z1-A5 1S-08-00-5,0

Disk Drive 4 U0.1-P1/Z1-A8 1S-08-00-8,0

SES for SCSI bus 0 (in backplane on

U0.1-P1/Z1-Af 1S-08-00-15,0

right)

SES for SCSI bus 1 (in backplane on

U0.1-P1/Z2-Af 1S-08-01-15,0

left)

Media Device 1 (for example, SCSI

U0.1-P1/Z2-A0

Tape, DVD)

Fans

26 IntelliStation POWER 9114 Model 275 Service Guide

Component Name Physical Location Code AIX Location Code

System Cooling Fan 1 U0.1-F1

System Cooling Fan 2 U0.1-F2

System Cooling Fan 3 U0.1-F3

Operator Panel

Operator panel U0.1-L1

System VPD module U0.1-L1-N1

Temperature Sensor (on Operator

U0.1-L1

Panel)

Time-of-Day Clock (TOD) U0.1-P1-X1

Power Supply

Power supply V1 (Redundant) U0.1-V1

Power supply V2 (Primary) U0.1-V2

Voltage Regulator Module - 1.2V U0.1-P1-V3

Voltage Regulator Module - 2.5V U0.1-P1-V2

Voltage Regulator Module - 1.8V U0.1-P1-V1

Battery

Battery U0.1-P1-X1-V4

Platform Firmware

Platform Firmware U0.1-P1-X1/Y1

Notes:

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

2. The SCSI bus IDs are the recommended values. The 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.

Chapter 1. Reference Information 27

System Cables

The following diagrams show the internal cable routing for the Model 275.

1 System Chassis 2 Media Bay Chassis 3 Operator Panel Cable 4 Operator Panel 5 Fan Tray Assembly Cable 6 Fan Tray Assembly

28 IntelliStation POWER 9114 Model 275 Service Guide

Specifications

This section contains system specifications for the Model 275.

Dimensions

Height 535.0 mm (21.1 in.) Width 190.0 mm (7.5 in.) Depth 685.0 mm (27.0 in.)

Weight

Minimum configuration 32.0 kg (70.5 lbs.) Maximum configuration 43.1 kg (94.8 lbs.)

Electrical

Power source loading (typical in kVA) 0.31 Power source loading (max. in kVA) 0.49 Voltage range (V ac) 100 to 127 or 200 to 240 (auto-ranging) Frequency (hertz) 47-63 Voltage range (V dc) Not supported Thermal output (typical) 1024 Btu/hr Thermal output (max.) 1587 Btu/hr Power requirements (typical) 300 watts Power requirements (max.) 465 watts Power factor - US, World Trade, Japan 0.95 Inrush current Maximum altitude²,³ 3048 m (10000 ft.)

85 amps (max. at <10ms)

Temperature Requirements² Operating

to 32°C

50 to 90°F)

Non-Operating

to 43°C

(50 to 109°F)

Humidity Requirements³ Operating Non-Operating

(Noncondensing) 8 to 80% 8 to 80%

Wet Bulb 27°C (80°F) 27°C (80°F)

Noise Emissions Operating Idle

WAd

<LpA>

6.1 bels 5.6 bels 44 dBA 44 dBA

Install/Air Flow Maintenance of service clearance will allow proper air flow.

1. Inrush currents occur only at initial application of power, no inrush occurs during normal power off-on cycle. The inrush current exponentially decays over 5 ac cycles.

2. The upper limit of the dry bulb temperature must be derated 1°C per 137 m (450 ft.) above 915 m (3000 ft.).

3. The upper limit of the wet bulb temperature must be derated 1°C per 274 m (900 ft. ) above 305 m (1000 ft.).

Chapter 1. Reference Information 29

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 115V 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, 125V.″

″For 230V 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, 250V.″

v Appliance couplers complying with International Electrotechnical Commission (IEC) Standard 320, Sheet

C13.

cables used in other countries consist of the following:

Power

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 an AWG equivalent.

To find the power cables that are available, refer to Chapter 10, “Parts Information,” on page 301.

30 IntelliStation POWER 9114 Model 275 Service Guide

Service Inspection Guide

Perform a service inspection on the system when:

v The system is inspected for a maintenance agreement. v Service is requested and service has not recently been performed. v An alterations and attachments review is performed. v Changes have been made to the equipment that may affect the safe operation of the equipment. v External devices with their own power cables have those cables attached.

the inspection indicates an unacceptable safety condition, the condition must be corrected before anyone

If 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.

Install the covers.

13.

Chapter 1. Reference Information 31

32 IntelliStation POWER 9114 Model 275 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 105, Chapter 5, “Error Code to FRU Index,” on page 131, Chapter 6, “Using the Online and Standalone Diagnostics,” on page 185, and Chapter 10, “Parts Information,” on page 301, 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 1320: Service Focal Point Procedures v MAP 1321: Quick Entry MAP for Systems with Service Focal Point. This MAP contains information for

systems not running 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 1548: Processor Subsystem Problem Isolation v MAP 1549: Attention Problem Isolation

Entry Map is the starting point for problem determination. The purpose of this MAP is to quickly point

The 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 provide a means to identify components in your system. For more information about these LEDs, see Chapter 11, “Component and Attention LEDs,” on page 309.

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

the system attention LED is turned on, you can access the system logs to determine the reason. The

If 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, see“Accessing System Log Error Information” on page 38.

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 105, Chapter 5, “Error Code to FRU Index,” on page 131, Chapter 6, “Using the Online and Standalone Diagnostics,” on page 185, and Chapter 10, “Parts Information,” on page 301). 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.

Certain checkpoints may remain in the display for long periods of time. A

Note:

spinning cursor is visible in the upper-right corner of the display during these periods to indicate that system activity is continuing.

Exxx checkpoints indicate that a system processor is in control and is initializing

Exxx

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.

0xxx and

0xxx and 2xxx codes are AIX progress codes and configuration codes. Location

2xxx

34 IntelliStation POWER 9114 Model 275 Service Guide

codes may also be shown on the operator panel display during this time. AIX progress codes and location codes will not appear if the LINUX operating system is booting.

Codes If a fault is detected, an 8-digit error code is displayed in the operator panel display. A

Error

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 105. 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 131. These actions can refer to Chapter 10, “Parts Information,” on page 301, Chapter 3, “Maintenance Analysis Procedures (MAPs),” on page 41, 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 19.

Note: When the system is running under 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 301. 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 Power subsystem FRUs v System unit 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 system unit or I/O drawer 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 contained in the “System Information Menu” on page 205.

Any identify LED in the system can also be flashed by using the ″Identify and Attention Indicators″ task in AIX online 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:

Chapter 2. Diagnostic Overview 35

v Boot to the open firmware prompt. See the “System Power Control Menu” on page 202 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.

Service Agent for the Model 275

Service support for the Model 275 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.

Using the Service Processor and Service Agent Features

The service processor and service agent features protect users against unnecessary system downtime by keeping support personnel (both internal and external) aware of any unexpected changes in the system environment. In combination, the two features provide a flexible solution to automated system maintenance.

Service Processor

The service processor runs on its own power boundary and continually monitors hardware attributes, the AIX operating system, and the environmental conditions within the system. Any system failure which prevents the system from returning to an operational state (a fully functional AIX operating system) is reported by the service processor. The service processor is controlled by firmware and does not require the AIX operating system to be operational to perform its tasks. If any system failures are detected, the service processor can take predetermined corrective actions. The methods of corrective actions are:

v Surveillance v Call home v AIX operating system monitoring

Surveillance

is a function in which the service processor monitors the system through heartbeat

communication with the system firmware. The heartbeat is a periodic signal that the firmware can monitor. During system startup, the firmware surveillance monitor is automatically enabled to check for heartbeats from the firmware. If a heartbeat is not detected within a default period, the service processor cycles the system power and attempts to restart until the system either restarts successfully, or a predetermined retry threshold is reached. In the event that the service processor is unsuccessful in bringing the system online (or in the event that the user asked to be alerted to any service processor-assisted restarts), the system can call home to report the error.

The call home function can be initialized to call either a service center telephone number, a customer administration center, or a digital pager telephone number. The service processor can be configured to stop at the first successful call to any of the numbers listed, or can be configured to call every number provided. If connected to the service center, the service processor transmits the relevant system information (the system’s serial number and model type) and service request number (SRN). If connected to a digital pager service, the service processor inputs a customer voice telephone number defined by the customer. An established sequence of digits or the telephone number to a phone near the failed system could be used to signal a system administrator to a potential system failure.

During normal operations, the service processor can also be configured to monitor the AIX operating system. If AIX does not respond to the service processor heartbeat, the service processor assumes the operating system is hung. The service processor can automatically initiate a restart and, if enabled, initiate the call home function to alert the appropriate people to the system hang. Enabling operating system surveillance also affords AIX the means to detect any service processor failures and report those failures to the service agent application.

36 IntelliStation POWER 9114 Model 275 Service Guide

Unlike the service agent, the service processor cannot be configured in a client/server environment where one system can be used to manage all dial-out functions for a set of systems.

Prior to installing the service agent feature, ensure that you have the latest level of system firmware. You also need a properly configured modem. For more information on configuring a modem, see “Modem Configuration Menu” on page 212.

Service Agent

The service agent is a software extension to the AIX operating system that monitors the system while the AIX operating system is running. The service agent monitors and analyzes all recoverable system failures, and, if needed, can automatically place a service call to a service center (without user intervention).

The service center receives the machine type/serial number, host name, SRN, and a problem description. The service center analyzes the problem report and, if warranted, dispatches a service person to the customer site. The service center also determines if any hardware components need to be ordered prior to the service person’s arrival.

The service agent code also gives the user the option to establish a single system as the problem reporting server. A single system, accessible over the user network, can be used as the central server for all the other systems on the local area network (LAN) that are running the service agent application. If the service agent application on a remote client decides a service request needs to be placed, the client forwards the information to the service agent server which dials the service center telephone number from its locally attached modem. In this scenario, the user only needs to maintain a single analog line for providing call-out capabilities for a large set of servers.

A modem is required for enabling automated problem reporting to the IBM service center. Configuration files for several types of modems are included as part of the service agent package. Refer to “Modem Configuration Menu” on page 212 for more information on configuring your modem.

Service Focal Point

The Service Focal Point application aides service representatives in developing service strategies in an HMC environment. HMC and Service Focal Point are not supported on the Model 275.

Chapter 2. Diagnostic Overview 37

Accessing System Log Error Information

Note: The system attention LED can be reset by following the procedures described in “Resetting the

System Attention LED.”

When an error is detected by the system, information about the error 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 Running AIX.” v “Accessing Errors when a System is Running Linux.”

Accessing Errors when a System is Running AIX

If the system attention LED comes on and the system is running AIX, 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 41 with the information noted from the error log.

Accessing Errors when a System is Running Linux

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 70 in “MAP 1321: Quick Entry MAP for Systems with Service

Focal Point” on page 61, return to “Step 1321-43” on page 70 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 61, go to step “Step 1321-1” on page 61 and perform the procedures in the MAP.

Resetting the System Attention LED

Complete one of the following procedures to reset your attention LED.

Because this system runs a single operating system in a full system partition and does not connect

Note:

to an HMC, references to Service Focal Point software do not apply. If you were directed here to reset the system attention LED, use the following procedures.

Resetting the LED when a System is Running AIX

As a user with root authority or CE login, 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.

the system is powered off, access the service processor menus. From the service processor main menu,

If 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.

38 IntelliStation POWER 9114 Model 275 Service Guide

Resetting the LED when a System is Running Linux

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.

Chapter 2. Diagnostic Overview 39

40 IntelliStation POWER 9114 Model 275 Service Guide

Chapter 3. Maintenance Analysis Procedures (MAPs)

This chapter contains Maintenance Analysis Procedures (MAPs) for the Model 275.

HMC configurations and CD-ROM drives are not supported on this model. The diagnostics

Note:

CD-ROM is placed in the supported DVD-ROM drive. Responses to questions referring to HMC should be ″no.″

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.

Note: AIX Online diagnostics are not available when running the Linux operating system.

If this system is running the Linux operating system and you have not previously been directed to MAP 1321, go to the “MAP 1321: Quick Entry MAP for Systems with Service Focal Point” on page 61. Otherwise, locate the symptom for the problem in the following table, and go to the appropriate starting point.

Notes:

1. Licensed programs frequently rely on system information stored on the VPD module on the operator panel assembly. If the MAPs indicate that the operator panel assembly should be replaced, refer to “Replacing the Operator Panel” on page 284. If you replace the operator panel, the system VPD information (for example the machine type and serial number) is restored to the new VPD module in the operator panel.

2. 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.

3. If more than eight digits are displayed in the operator panel, use only the first eight digits to find the error in the tables. The digits that display beyond the first eight digits are location codes that can assist you in diagnosing the problem. See “Location Codes” on page 19.

4. If you are not able to isolate the problem, try loading AIX standalone diagnostics from the CD-ROM or a NIM server.

The following table is used to help identify the types of error data in this guide.

Number of Digits in Error Code Error Code Name in this Service Guide

Any Contains # Menu Goal

Any Contains - (hyphen) SRN

5 Does not contain # or - SRN

6 Does not contain # or - Error Code

8 Does not contain # or - Error Code, SRC, or Ref Code

Symptom Starting Point

You have a problem that does not prevent the system from booting. The operator panel is functional.

You do not have a symptom. Go to MAP 0020 in the RS/6000 Eserver pSeries

You have an SRN. Go to the Fast Path MAP in the RS/6000 Eserver

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 43.

Go to the Fast Path MAP in the RS/6000 Eserver

pSeries Diagnostic Information for Multiple Bus Systems.

Diagnostic Information for Multiple Bus Systems.

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.

42 IntelliStation POWER 9114 Model 275 Service Guide

Quick Entry MAP

Quick Entry MAP Table of Contents

Problem Description Page No.

Service actions 44

The system attention LED on the operator panel is on. 44

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 44

System stops with an 8-digit number displayed 44

System stops with a 4-digit number displayed that does not begin with 0 or 2. 45

System stops with a 3-digit number displayed (see below for 888 sequence). 45

There appears to be a display problem (distortion, blurring, and so on) 45

Power and cooling problems 45

888 sequence in operator panel display 45

Other Symptoms or Problems

The operator panel displays OK and the fans are off. The service processor is ready. The system is waiting

for power-on. Boot the system. If the boot is unsuccessful, and the system returns to the OK “MAP 1020: Problem Determination” on page 49.

The operator panel displays STBY. The service processor is ready. The system was shut

down by the operating system and is still powered on. This condition can be requested by a privileged system user with no faults. See the service processor error log for possible operating system fault indications.

All of the system POST indicators are displayed on the

Go to “Boot Problems/Concerns” on page 128. system console, the system pauses and then restarts. The term POST indicators refers to the device mnemonics (the words memory, keyboard, network, scsi, and speaker) that appear on the system console during the power-on self-test (POST).

The system stops and all of the POST indicators are

Go to “Boot Problems/Concerns” on page 128. displayed on the system console. The term POST indicators refers to the device mnemonics (the words memory, keyboard, network, scsi, and speaker) that appear on the system console during the power-on self-test (POST).

The system stops and the message STARTING SOFTWARE

Go to Chapter 4, “Checkpoints,” on page 105. PLEASE WAIT... is displayed on the firmware console.

The system does not respond to the password being entered or the system login prompt is displayed when booting in service mode.

1. If the password is being entered from a keyboard attached to the system, the keyboard or its controller may be faulty. In this case, replace these parts in the following order:

a. Keyboard

b. Service processor, location: U0.1-P1-X1. (See

notes on page 41).

If the password is being entered from an ASCII

2. terminal, use the problem determination procedures for the ASCII terminal. Make sure the ASCII terminal is connected to S1.

If the problem persists, replace the service processor, location: U0.1-P1-X1. (See notes on page 41).

46 IntelliStation POWER 9114 Model 275 Service Guide

the problem is fixed, go to ″MAP 0410: Repair

Checkout″, in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

If the problem is still not corrected, go to “MAP 1548: System Processor Problem Isolation” on page 90.

No codes are displayed on the operator panel within a few seconds of turning on the system. The operator panel is blank before the system is powered on.

The SMS configuration list or boot sequence selection menu shows more SCSI devices attached to a controller/adapter than are actually attached.

Reseat the operator panel cable. If the problem is not resolved, replace in the following order:

1. Operator panel assembly, location: U0.1-L1. Swap the VPD module from the old operator panel to the new operator panel.

2. Service processor, location: U0.1-P1-X1. (See notes on 41).

the problem is fixed, go to ″MAP 0410: Repair

Checkout″, in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

If the problem is still not corrected, go to “MAP 1548: System Processor Problem Isolation” on page 90.

A device may be set to use the same SCSI bus ID as the control adapter. Note the ID being used by the controller/adapter (this can be checked and/or changed through an SMS utility), and verify that no device attached to the controller is set to use that ID.

If settings do not appear to be in conflict:

1. Go to “MAP 1548: System Processor Problem Isolation” on page 90.

2. Replace the SCSI cable.

3. Replace the device.

4. Replace the SCSI adapter

In a ″twin-tailed″ configuration where there is

Note:

more than one initiator device (normally another system) attached to the SCSI bus, it may be necessary to use SMS utilities to change the ID of the SCSI controller or adapter.

Chapter 3. Maintenance Analysis Procedures (MAPs) 47

The System Management Services menu is displayed. If you are loading diagnostics from the CD-ROM, you

may not have pressed the correct key when you were trying to indicate a service mode IPL of the diagnostic programs. If this is the case, start again at the beginning of this step.

If you are sure you pressed the correct key, the device or media you are attempting to boot from may be faulty.

1. If you are using a keyboard and a graphic display attached to the system:

v Select View Error Log

v If an error is logged, check the time stamp.

v If the error was logged during the current boot

attempt, record it.

v Look up the error in Chapter 5, “Error Code to

FRU Index,” on page 131

v If no recent error is logged in the error log, go

to step 3.

If you are using an ASCII terminal:

v Select View Error Log

v If an error is logged, check the time stamp.

v If the error was logged during the current boot

attempt, record it.

v Look up the error in Chapter 5, “Error Code to

FRU Index,” on page 131 and do the listed action.

v If no recent error is logged in the error log, go

to step 3.

Try to boot from an alternate boot device

3. connected to the same controller as the original boot device. If the boot succeeds, replace the original boot device (for removable media devices, try the media first).

4. Go to “MAP 1548: System Processor Problem Isolation” on page 90.

You suspect a cable problem. Go to RS/6000 Eserver pSeries Adapters, Devices,

and Cable Information for Multiple Bus Systems.

All other problems. Go to “MAP 1020: Problem Determination” on page

49..

48 IntelliStation POWER 9114 Model 275 Service Guide

MAP 1020: Problem Determination

Purpose of This MAP

Use this MAP to get an error code if you were not provided one by the customer or you are unable to load diagnostics. If you are able to load the diagnostics, go to MAP 0020 in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

The service processor may have recorded one or more symptoms in its error log. Examine this error log before proceeding (see “System Information Menu” on page 205).

The service processor may have been set by the user to monitor system operations and to attempt recoveries. You can disable these actions while you diagnose and service the system. If the system was set up according to the recommendations of the IntelliStation POWER 9114 Model 275 User’s Guide, all the settings of the service processor (except language) were saved by using the SAVE/RESTORE HARDWARE MAINTENANCE POLICIES service aid. Yo u can use the same service aid to restore the settings at the conclusion of your service action.

In case the service processor settings were not saved by the user, if you disable them, make notes of their current settings for restoration before you leave.

In addition to the parameters in the following table, you can disconnect the modem to prevent incoming signals that could cause the system to power on.

Following are the service processor settings. The service processor menus are described in Chapter 7, “Using the Service Processor,” on page 193.

Surveillance From the service processor Setup Menu, go to the

Surveillance Setup Menu and disable surveillance.

Unattended Start From the service processor System Power Control Menu,

disable unattended start mode.

Reboot Policy From the System Power Control Menu, go to the

Reboot/Restart Policy Setup Menu and set:

1. Number of reboot attempts to 0 (zero)

2. Use OS-Defined restart policy to No

3. Enable supplemental restart policy to No.

Call-Out From the Call-In/Call-Out Setup Menu, go to the Serial

Port Selection Menu and disable call-out on both serial ports.

Chapter 3. Maintenance Analysis Procedures (MAPs) 49

Another feature that could disrupt a service action by powering on the system is an AIX function called timed power-on. This function is not available when using the Linux operating system. For more information about timed power-on, see “System Power-On Methods” on page 215.

Be prepared to record code numbers and use those numbers in the course of analyzing a problem. Go to “Step 1020-1.”

Step 1020-1

The following steps analyze a failure to load the diagnostic programs.

Note: Be prepared to answer questions regarding the operator panel display and to perform certain

actions based on displayed POST indicators. Please be observant of these conditions.

1. Power off the system. Refer to “Stopping the System” on page 246.

2. Select slow boot mode (select disable fast boot) on the system power control menu from the service processor main menu.

3. Power on the system. Refer to “Starting the System” on page 247.

4. Insert the diagnostic CD-ROM into the DVD-ROM drive.

5. When the keyboard indicator is displayed (the word keyboard), press the 5 key on the system console.

6. Enter a password, if requested.

7. Wait until the diagnostics are loaded or the system appears to stop. If you receive an error code or if the system stops before diagnostics are loaded, find your symptom in the following table, then follow the instructions given in the Action column.

If no fault is identified, continue to the next step.

8. Run the standalone diagnostics on the entire system. Find your symptom in the following table, then follow the instructions given in the Action column.

If no fault is identified, call service support for assistance.

50 IntelliStation POWER 9114 Model 275 Service Guide

Symptom Action

The system stopped and a code is displayed on the

Go to the “Quick Entry MAP” on page 43.

operator panel.

The system stops with a prompt to enter a password. Enter the password. You cannot continue until a correct

password has been entered. When you have entered a valid password, go to the beginning of this table and wait for one of the other conditions to occur.

The diagnostic operating instructions are displayed. Go to ″MAP 0020: Problem Determination Procedure″ in

the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

The system login prompt is displayed. If you are loading the diagnostics from a CD-ROM, you

may not have pressed the correct key or you may not have pressed the key soon enough when you were trying to indicate a service mode IPL of the diagnostic programs. If this is the case, start again at the beginning of this step.

Note: Perform the system shutdown procedure before

turning off the system.

If you are sure you pressed the correct key in a timely manner, go to “Step 1020-2” on page 53.

If you are loading diagnostics from a NIM server, check for the following:

v The bootlist on the client may be incorrect.

v Cstate on the NIM server may be incorrect.

v There may be network problems preventing you from

connecting to the NIM server.

The system does not respond when the password is entered.

Verify

the settings and the status of the network. If you

continue to have problems refer to “Boot Problems/Concerns” on page 128 and follow the steps for network boot problems.

Go to “Step 1020-2” on page 53.

Chapter 3. Maintenance Analysis Procedures (MAPs) 51

Symptom Action

The system stopped. A POST indicator is displayed on the system console and an eight-digit error code is not displayed.

If the POST indicator represents:

1. Memory, go to “MAP 1240: Memory Problem Resolution” on page 55.

2. Keyboard

a. Replace the keyboard.

b. Replace the service processor, location:

c. Go to “MAP 1548: System Processor Problem

Network, go to “MAP 1548: System Processor

3. Problem Isolation” on page 90.

4. SCSI, go to “MAP 1548: System Processor Problem Isolation” on page 90.

5. Speaker

a. Replace the operator panel, location: U0.1-L1.

b. Replace the service processor, location:

c. Go to “MAP 1548: System Processor Problem

U0.1-P1-X1. (See notes on page 41).

Isolation” on page 90.

Refer to “Operator Panel and Power Cable” on page 283.

U0.1-P1-X1. (See notes on page 41).

Isolation” on page 90.

52 IntelliStation POWER 9114 Model 275 Service Guide

Symptom Action

The System Management Services menu is displayed. If you are loading diagnostics from the CD-ROM, you

may not have pressed the correct key when you were trying to indicate a service mode IPL of the diagnostic programs. If this is the case, start again at the beginning of this step.

If you are sure you pressed the correct key, the device or media you are attempting to boot from may be faulty.

1. If you are using a keyboard and a graphic display attached to the system:

v Select View Error Log

v If an error is logged, check the time stamp.

v If the error was logged during the current boot

attempt, record it.

v Look up the error in Chapter 5, “Error Code to FRU

Index,” on page 131 and do the listed action.

v If no recent error is logged in the error log, go to

step 3.

If you are using an ASCII terminal:

v Select View Error Log

v If an error is logged, check the time stamp.

v If the error was logged during the current boot

attempt, record it.

v Look up the error in Chapter 5, “Error Code to FRU

Index,” on page 131 and do the listed action.

v If no recent error is logged in the error log, go to

step 3.

Try to boot from an alternate boot device connected

3. to the same controller as the original boot device. If the boot succeeds, replace the original boot device (for removable media devices, try the media first).

4. Go to “MAP 1548: System Processor Problem Isolation” on page 90.

All other symptoms. If you were directed here from the Entry MAP, go to “MAP

1548: System Processor Problem Isolation” on page 90. Otherwise, find the symptom in the “Quick Entry MAP” on page 43.

Step 1020-2

There is a problem with the keyboard.

Find the type of keyboard you are using in the following table; then follow the instructions given in the Action column.

Keyboard Type Action

Type 101 keyboard (U.S.). Identified by the size of the Enter key. The Enter key is in only one horizontal row of keys.

Type 102 keyboard (W.T.). Identified by the size of the Enter key. The Enter key extends into two horizontal rows.

v Replace the type 101 keyboard.

v Replace the service processor, location: U0.1-P1-X1.

(See notes on page 41.)

v Replace the type 102 keyboard.

v Replace the service processor, location: U0.1-P1-X1.

(See notes on page 41.)

Chapter 3. Maintenance Analysis Procedures (MAPs) 53

Keyboard Type Action

Type 106 keyboard. (Identified by the Japanese characters.)

v Replace the type 106 keyboard.

v Replace the service processor, location: U0.1-P1-X1.

(See notes on page 41.)

ASCII terminal keyboard Go to the documentation for this type of ASCII terminal

and continue with problem determination.

If the problem was not corrected by one of the previous actions and you were not already directed to go to

MAP 1548, go to “MAP 1548: System Processor Problem Isolation” on page 90.

54 IntelliStation POWER 9114 Model 275 Service Guide

MAP 1240: Memory Problem Resolution

Note: The firmware or error code that sent you here could be one of the following:

v Service Processor Checkpoints 910B, 910C, 910E or 95xx v Firmware Checkpoints E134 or E701 v System Power Control Network Error Code 1011840C v Firmware Error Codes 25Cyy001, 25Cyy002, 25B00001 or 25B00004 v Service Processor Error Codes 406x001x, 406x010x, 406x013x, 406x0CA6 or 450x30xx v Common Firmware Error Codes B1xx466x v Problem Determination Error Code M0MEM002

checkpoints and error codes are referred to as a memory code in this MAP.

These

Purpose of This MAP

This MAP is used to troubleshoot a problem when the system stops with a memory checkpoint or memory error code on the operator panel display or console.

Notes:

1. If the symptom changes while you are using this MAP, check for loose cards, cables, and obvious problems. If you do not find a problem, go to “MAP 1548: System Processor Problem Isolation” on page 90.

2. The service processor may have recorded one or more symptoms in its error log. It is a good idea to examine that error log before proceeding (see Service Processor System Information Menu).

3. The service processor may have been set by the user to monitor service operations and to attempt recoveries. You might want to disable these actions while you diagnose and service the system. If you disable them, make note of their current settings so that you can restore them before you leave. The following settings may be of interest to you.

Surveillance From the Service Processor Setup Menu, go to the

Surveillance Setup menu and disable surveillance.

Unattended Start From the Service Processor System Power Control Menu,

disable unattended start mode.

Reboot Policy From the System Power Control Menu, go to the

Reboot/Restart Policy Setup Menu and set:

1. Number of reboot attempts to 0 (zero)

2. Use OS-Defined restart policy to No.

3. Enable supplemental restart policy to No.

Call Out From the Call-In/Call-Out Setup Menu, go to the Serial

Port Selection Menu and disable call-out on both serial ports.

Chapter 3. Maintenance Analysis Procedures (MAPs) 55

General Memory Information

Be sure to unplug the power cables before removing or installing memory DIMMs to avoid damage to them.

Memory DIMMs must be installed in matched (size and speed) quads. Refer to “Memory DIMMs” on page 293 for labeling of the system backplane and instructions on memory DIMM removal and installation. Do not, however, replace the covers as directed while troubleshooting this problem. Memory DIMM quads can only be installed in one of the following two memory DIMM slot combinations:

v 1, 3, 6, and 8 v 2, 4, 5, and 7

is no requirement that memory DIMM slots 1, 3, 6, and 8 be populated before memory DIMM slots

There 2, 4, 5, and 7.

Attention: Go to the service processor menus. In the System Information Menu, select Memory Configuration/ Deconfiguration. Verify on the first screen that memory repeat gard is disabled. If it is

enabled, disable it for the duration of this MAP. When exiting this MAP to go to MAP 0410 in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems, return the setting to enabled if necessary.

Step 1240-1

1. Turn off the power. Remove the power cord.

2. Reseat the DIMMs.

3. Reattach the power cord. Wait for OK in the operator panel.

4. Turn on the power. Attempt to boot to the SMS menus. (The system may stop with an 8-digit error code before it reaches the SMS menus.)

5. Power down the system using the white button. After the OK appears in the operator panel, look at the memory configuration/deconfiguration menu.

Are any DIMMs deconfigured or does the error code recorded in “Step 1240-1” still appear?

NO Reseating the DIMMs has corrected the problem.

Enable memory repeat gard if necessary.

Go to ″MAP 0410: Repair Checkout″ in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

YES If there is only one quad of DIMMs on the planar, go to “Step 1240-5” on page 57.

If there are two quads of DIMMs on the planar, go to “Step 1240-2” on page 57.

56 IntelliStation POWER 9114 Model 275 Service Guide

Step 1240-2

1. Turn off the power. Remove the power cord.

2. Remove one quad of DIMMs. Record the positions of the DIMMs as they are removed. When instructed to reinstall the DIMMs, install them back into the same slots from which they were removed.

3. Reattach the power cord. Wait for OK in the operator panel.

4. Turn on the power. Attempt to boot to the SMS menus. (The system may stop with an 8-digit error code before it reaches the SMS menus.)

5. Power down the system using the white button. After the OK appears in the operator panel, look at the memory configuration/deconfiguration menu.

Are any DIMMs deconfigured or does the error code recorded in “Step 1240-1” on page 56 still appear?

NO Go to “Step 1240-3.”

YES Go to “Step 1240-5.”

Step 1240-3

1. Turn off the power. Remove the power cord.

2. Move the quad of DIMMs located on the card to the other quad’s slots.

3. Reattach the power cord. Wait for OK in the operator panel.

4. Turn on the power. Attempt to boot to the SMS menus. (The system may stop with an 8-digit error code before it reaches the SMS menus.)

5. Power down the system using the white button. After the OK appears in the operator panel, look at the memory configuration/deconfiguration menu.

Are any DIMMs deconfigured or does the error code recorded in “Step 1240-1” on page 56 still appear?

NO Go to “Step 1240-4.”

YES Replace the system planar.

Enable memory repeat gard if necessary.

Go to ″MAP 0410: Repair Checkout″ in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

Step 1240-4

The failing DIMM(s) is in the quad of DIMMs that was removed in “Step 1240-2.” Do the following:

1. Turn off the power. Remove the power cord.

2. Remove the quad of DIMMs that is on the system planar and reinstall the quad of DIMMs that had been removed. The DIMMs can be reinstalled in either quad.

3. Go to “Step 1240-6” on page 59.

Step 1240-5

1. Turn off the power. Remove the power cord.

2. Move the quad of DIMMs that is on the system planar to the other quad’s location.

3. Reattach the power cord. Wait for OK in the operator panel.

4. Turn on the power. Attempt to boot to the SMS menus. (The system may stop with an 8-digit error code before it reaches the SMS menus.)

5. Power down the system using the white button. After the OK appears in the operator panel, look at the memory configuration/deconfiguration menu.

Chapter 3. Maintenance Analysis Procedures (MAPs) 57

Are any DIMMs deconfigured or does the error code recorded in “Step 1240-1” on page 56 still appear?

NO Replace the system planar.

Enable memory repeat gard if necessary.

Go to ″MAP 0410: Repair Checkout″ in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

YES One or more of the DIMMs on the card is defective. Go to “Step 1240-6” on page 59.

58 IntelliStation POWER 9114 Model 275 Service Guide

Step 1240-6

Note: If only one quad of DIMMs is on the system planar, you must have at least one replacement DIMM

of the same size and speed as the DIMMs that are on the system planar.

If there were two quads of DIMMs on the system planar, but they are not the same size, you must have at least one replacement DIMM of the same size and speed as the DIMMs in the quad that is failing.

If there were two quads of DIMMs on the system planar, and they are the same size and speed, DIMMs from the good quad can be used when isolating the failing DIMM in the suspect quad.

1. Turn off the power. Remove the power cord.

2. Remove one of the DIMMs on the system planar, and install the replacement DIMM or another DIMM that is known to be good.

3. Reattach the power cord. Wait for OK in the operator panel.

4. Turn on the power. Attempt to boot to the SMS menus. (The system may stop with an 8-digit error code before it reaches the SMS menus.)

5. Power down the system using the white button. After the OK appears in the operator panel, look at the memory configuration/deconfiguration menu.

Are any DIMMs deconfigured or does the error code recorded in “Step 1240-1” on page 56 still appear?

NO The DIMM that was just removed was the failing DIMM; replace it.

Enable memory repeat gard if necessary.

Go to ″MAP 0410: Repair Checkout″ in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

YES Go to “Step 1240-7.”

Step 1240-7

Have all the DIMMs in the quad located on the system planar been replaced?

NO Go to “Step 1240-6” to test the next DIMM of the quad on the system planar.

YES Go to “Step 1240-8.”

Step 1240-8

Did the processor originally have only one quad of DIMMs at the start of this map?

NO Call support.

YES Replace the system planar. This ends the procedure. Enable memory repeat gard if necessary. Go

to ″MAP 0410: Repair Checkout″ in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

Chapter 3. Maintenance Analysis Procedures (MAPs) 59

MAP 1320: Service Focal Point

These procedures define the steps to take when servicing a machine that is equipped with Service Focal Point (SFP). Yo u might also be directed to these procedures if the system is running Linux as its only operating system.

Note: If the system is attached to an HMC and Service Focal Point is enabled, 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.

Number of Digits in Error Code Error code Name Used in this Service Guide

Any Contains # (pound sign) Menu Goal

Any Contains - (hyphen) SRN

5 Does not contain # or - SRN

6 Does not contain # or - Error Code

8 Does not contain # or - Error Code, Service Reference Code

(SRC)

For steps to be taken when beginning service on a machine with SFP, see the “MAP 1321: Quick Entry

MAP for Systems with Service Focal Point” on page 61.

For steps to be taken after service is complete on a machine with SFP, see the “MAP 1322: End of Call MAP for Systems with Service Focal Point” on page 71.

60 IntelliStation POWER 9114 Model 275 Service Guide

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

Notes:

1. If you are working on a system that is managed by an HMC, the term service action event is synonymous with serviceable event in this MAP.

2. If you are working on a system that is managed by an HMC, some steps in this MAP may ask you to open the details of the service action event and obtain error codes and FRU location codes. Depending on the error code(s), this operation may involve looking at service processor error code details. Be sure you select all listed error codes one at a time. Select details to display all error codes and location codes for the serviceable event that you are working with.

Step 1321-1

For future reference, record the error code and the location code (that brought you to this MAP) of the FRU to be replaced. Record any other symptoms if an error code is not available.

Does the system have an HMC attached?

No Go to “Step 1321-23” on page 65.

Yes Go to “Step 1321-2.”

Step 1321-2

At the HMC console, start Service Focal Point (SFP) and examine the service action event log for any open service action events. For SFP operating instructions, see “Service Focal Point” on page 37.

Does the HMC appear to operate correctly?

No Go to “Quick Entry MAP” on page 43, look up the HMC symptom, and follow the directions there.

Yes Go to “Step 1321-3.”

Step 1321-3

Are there any service action events that are open?

No Go to “Step 1321-40” on page 69.

Yes Go to “Step 1321-4.”

Step 1321-4

Record the list of open service action events.

Step 1321-5

From the list of serviceable events recorded in “Step 1321-4,” open the details of each service action event and examine the FRU list and error code(s) for each.

Step 1321-6

Are there any serviceable actions events with error codes of the form #xxxxxx in the list of error codes found in “Step 1321-5”?

No Go to “Step 1321-7.”

Yes Go to “Step 1321-18” on page 64.

Step 1321-7

Are there any serviceable events with FRU location codes reported in “Step 1321-5”?

Chapter 3. Maintenance Analysis Procedures (MAPs) 61

No Go to “Step 1321-14.”

Yes Go to “Step 1321-8.”

Step 1321-8

From the list of open service action events with FRUs reported, examine the details of each service action event and record the error code.

Step 1321-9

Examine the list of error codes you obtained from “Step 1321-8” and look for any of the form 4xxB xxxx, A0D-34x, or A1D-34x.

Step 1321-10

Are there any error codes from “Step 1321-8” of the form 4xxB xxxx, A0D-34x, or A1D-34x?

No Go to “Step 1321-13.”

Yes Go to “Step 1321-11.”

Step 1321-11

Do any of the error codes from “Step 1321-8” of the form 4xxB xxxx, A0D-34x, or A1D-34x have the same first two characters on the left as the first two characters on the left of the error code recorded in “Step 1321-1” on page 61 that sent you to this MAP?

No Go to “Step 1321-13.”

Yes Record the error codes from “Step 1321-8” of the form 4xxB xxxx, A0D-34x, or A1D-34x that have

the same first two characters on the left as the first two characters on the left of the error code recorded in “Step 1321-1” on page 61 that sent you to this MAP. Also, record the service action event associated with each error code. Go to “Step 1321-12.”

Step 1321-12

From the list of open service action events with error codes of the form 4xxB xxxx, A0D-34x, or A1D-34x recorded in “Step 1321-11,” choose the service action event with the earliest time stamp (the one that occurred first), record its error code and FRU location(s), and proceed to “Step 1321-14” with this new code.

When future steps refer to the error code recorded in “Step 1321-1” on page 61, use this new error code and its location code(s) instead of the original error code that sent you to this MAP.

Step 1321-13

From the list of open service action events with FRUs reported, choose the service action event with the earliest time stamp (the one that occurred first), record its error code and FRU location(s), and proceed to “Step 1321-14” with this new error code. When future steps refer to the error code recorded in “Step 1321-1” on page 61, use this new error code and its location code(s) instead of the original error code that sent you to this MAP.

Step 1321-14

At the HMC console, open Service Focal Point (SFP) and examine the service action event log for any closed service action events. For SFP operating instructions, refer to “Service Focal Point” on page 37.

Step 1321-15

Are there any service action events that are closed?

No Go to the table in “Entry MAP” on page 41.

62 IntelliStation POWER 9114 Model 275 Service Guide

Yes Go to “Step 1321-16” on page 64.

Chapter 3. Maintenance Analysis Procedures (MAPs) 63

Step 1321-16

Examine the details of the ten most-recently closed service action events.

Are there any error codes or symptoms in the ten latest closed service action events that are the same as the error code or symptom recorded in “Step 1321-1” on page 61?

No Go to the table in “Entry MAP” on page 41.

Yes Go to “Step 1321-17.”

Step 1321-17

Examine the FRUs of the same error codes or symptoms.

Are there any FRUs in the same error codes or symptoms of the closed service action events left to be replaced?

No Go to the table in “Entry MAP” on page 41.

Yes Replace the next FRU of same error codes or symptoms of the closed service action events. Go

to ″MAP 0410: Repair Checkout″ in RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

Step 1321-18

From the list of serviceable events with error code(s) of the form #xxxxxx, examine the details of each serviceable event to display the description field of the error code(s) of the form #xxxxxx.

Step 1321-19

Double-click on the description field to view the complete text.

Step 1321-20

Perform any actions that may be listed in the descriptions of all error codes of the form #xxxxxx before proceeding.

Step 1321-21

Did you find a problem?

No Go to “Step 1321-7” on page 61.

Yes Go to ″MAP 0410: Repair Checkout″ in RS/6000 Eserver pSeries Diagnostic Information for

Multiple Bus Systems.

Step 1321-22

Look for and record any additional error information or software messages on the operator panel or the console (serial TTY, Vterm, or HMC). Choose a running Linux partition (preferably the partition with the problem).

64 IntelliStation POWER 9114 Model 275 Service Guide

Step 1321-23

Is Linux usable in any partition with Linux installed?

No Go to “Step 1321-30” on page 67.

Go to “Step 1321-24.”

Yes

Attention: “Step 1321-24” through “Step 1321-36” on page 68 must be performed on a partition running

the Linux operating system.

Step 1321-24

If your system is functional, examine the Linux system log by logging in to the system as the root user and entering the following command:

cat /var/log/messages |grep RTAS |more

Linux run-time error messages are logged in the messages file under /var/log. The following is an example of the Linux system error log.

Aug 27 18:13:41 rasler kernel: RTAS: -------- event-scan begin -------- Aug 27 18:13:41 rasler kernel: RTAS: Location Code: U0.1-P1-C1 Aug 27 18:13:41 rasler kernel: RTAS: WARNING: (FULLY RECOVERED) type: INTERN_DEV_FAIL Aug 27 18:13:41 rasler kernel: RTAS: initiator: UNKNOWN target: UNKNOWN Aug 27 18:13:41 rasler kernel: RTAS: Status: predictive new Aug 27 18:13:41 rasler kernel: RTAS: Date/Time: 20020827 18134000 Aug 27 18:13:41 rasler kernel: RTAS: CPU Failure Aug 27 18:13:41 rasler kernel: RTAS: CPU id: 0 Aug 27 18:13:41 rasler kernel: RTAS: Failing element: 0x0000 Aug 27 18:13:41 rasler kernel: RTAS: A reboot of the system may correct the problem Aug 27 18:13:41 rasler kernel: RTAS: -------- event-scan end ----------

Step 1321-25

Record any RTAS messages found in the Linux system log in Step 1321-24. Ignore all other messages in the Linux system log. If the system is configured with more than one logical partition with Linux installed, repeat “Step 1321-24” and “Step 1321-25” for all logical partitions that have Linux installed.

Chapter 3. Maintenance Analysis Procedures (MAPs) 65

Step 1321-26

Examine the Linux boot (IPL) log by logging in to the system as the root user and entering the following command:

cat /var/log/boot.msg |grep RTAS |more

Linux boot (IPL) error messages are logged into the boot.msg file under /var/log. The following is an example of the Linux boot error log.

RTAS daemon started RTAS: -------- event-scan begin -------- RTAS: Location Code: U0.1-F3 RTAS: WARNING: (FULLY RECOVERED) type: SENSOR RTAS: initiator: UNKNOWN target: UNKNOWN RTAS: Status: bypassed new RTAS: Date/Time: 20020830 14404000 RTAS: Environment and Power Warning RTAS: EPOW Sensor Value: 0x00000001 RTAS: EPOW caused by fan failure RTAS: -------- event-scan end ----------

Step 1321-27

Record any RTAS messages found in the Linux boot (IPL) log in Step 1321-26. Ignore all other messages in the Linux boot (IPL) log. If the system is configured with more than one logical partition with Linux installed, repeat “Step 1321-26” and “Step 1321-27” for all logical partitions that have Linux installed.

Step 1321-28

Examine the extended data in both logs.

The following is an example of the Linux extended data.

<3>RTAS daemon started <3>RTAS: -------- event-scan begin -------- <3>RTAS: Location Code: U0.1-P1-C2 <4>RTAS: Log Debug: 04 4b2726fb04a00011702c0014000000000000000000000000f1800001001801d3ffffffff010000000000000042343138 20202020383030343236464238454134303030303 <4>RTAS: Log Debug: D2 5046413405020d0a000001000271400100000033434d502044415441000001000000000000010000f180000153595 320444154410000000000000000200216271501050920021627150105092002063715010509535243204441544170 2c001400000000000000020018820201d382000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000280048ea400000000000000000000 000000000000000000004350542044415441702cff08000000001c000000702cf0080000000080000000702cf10070 2cf200702c000400000800702c01040bf2002e702c02040c1fffbf702c0300702c1000702c11040bf2002e702c12040 c1fffbf702c1300702ca000702ca108000000000000a03c702ca208000000000000effc702cb000702cb10800000000 0000a03c702cb208000000000000effc702cc000702cc108000000000000a03c702cc208000000000000effc702c3 000702c31080000000000000003702c3208000000000000007b702c8000702c81080000000020e27a39702c820800 000000fffeffff702cd000702cd1080000000010004010702cd208000000007777f3ffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffff <3>RTAS:

WARNING: (FULLY RECOVERED) type: INTERN_DEV_FAIL

<3>RTAS: initiator: UNKNOWN target: UNKNOWN <3>RTAS: Status: unrecoverable new <3>RTAS: Date/Time: 20020905 15372200 <3>RTAS: CPU Failure <3>RTAS: Internal error (not cache) <3>RTAS: CPU id: 0 <3>RTAS: Failing element: 0x0000 <3>RTAS: -------- event-scan end ---------

030303030303030

66 IntelliStation POWER 9114 Model 275 Service Guide

Step 1321-29

Record any extended data found in the Linux system log in Step 1321-24 or the Linux boot (IPL) log in Step 1321-26. Be sure to record word 13.

Note: The line(s) in the Linux extended data that begin with ″<4>RTAS: Log Debug: 04″ contain the error

code listed in the next 8 hex characters. In the previous example, ″4b27 26fb″ is an error code. The error code is also known as word 11 . Each 4 bytes after the error code in the Linux extended data is another word (for example, ″04a0 0011″ is word 12, and ″702c 0014″ is word 13, and so on).

If the system is configured with more than one logical partition with Linux installed, repeat “Step 1321-28” on page 66 and “Step 1321-29” for all logical partitions that have Linux installed.

Step 1321-30

Were any error codes or checkpoints recorded in Steps 1321-1, 1321-22, 1321-25, 1321-27, or 1321-29?

No Go to “Step 1321-31.”

Yes Go to the “Quick Entry MAP” on page 43 with each recorded error code or symptom. Perform the

indicated actions one at a time for each error code until the problem has been corrected. If all recorded error codes have been processed and the problem has not been corrected, go to “Step 1321-31.”

Step 1321-31

If no additional error information is available and the problem has not been corrected, shut down the system.

If an HMC is not attached, you need a laptop computer (and cable, part number 62H4857) capable of connecting to serial port 1 on the processor subsystem.

Note: The Linux login prompt cannot be seen on a laptop computer connected to serial port 1.

1. If there is no HMC, attach the laptop computer and cable to serial port 1 on the processor subsystem.

2. When OK displays in the operator panel, press a key on the virtual terminal on the laptop computer. The service processor menus are available on the attached laptop computer or on the HMC.

3. Examine the service processor (SP) error log. Record all error codes and messages written to the SP error log. Go to “Step 1321-32.”

4. If the service processor menus are not available, go to “Step 1321-33.”

Step 1321-32

Boot the system to the system management services (SMS) menus. Record all error codes and messages written to the SMS error log.

Step 1321-33

Were any error codes recorded in steps 1321-31 or 1321-32?

No Go to “Step 1321-41” on page 69.

Yes Go to the “Quick Entry MAP” on page 43 with each error code or symptom you have recorded.

Perform the indicated actions, one at a time, until the problem has been corrected. If all recorded error codes have been processed and the problem has not been corrected, go to “Step 1321-41” on page 69.

Chapter 3. Maintenance Analysis Procedures (MAPs) 67

Step 1321-34

Reboot the system and and bring all partitions to the login prompt. If Linux is not usable in all partitions, go to “Step 1321-38” on page 69.

Step 1321-35

Use the lscfg command to list all resources assigned to all partitions. Record the adapter and the partition for each resource.

Step 1321-36

To determine if any device(s) or adapter(s) are missing, compare the list of found resources and partition assignments to the customer’s known configuration. Record the location of any missing devices. Also record any differences in the descriptions or the locations of devices.

You may also compare this list of found resources to a prior version of the device tree as follows:

Note: Every time that the partition is booted, the update-device-tree command is run and the device tree

is stored in the /var/lib/lsvpd/ directory in a file with the file name device-tree-YYYY-MM-DDHH:MM:SS, where YYYY is the year, MM is the month, DD is the day, and HH, MM, and SS are the hour, minute and second, respectively, of the date of creation.

v At the command line, type the following:

cd /var/lib/lsvpd/

v At the command line, type the following:

lscfg -vpd device-tree-2003-03-31-12:26:31. This displays the device tree created on 03/31/2003 at 12:26:31.

The diff command offers a way to compare the output from a current lscfg command to the output from an older lscfg command. If the files names for the current and old device trees are current.out and old.out, respectively, type: diff old.out current.out. Any lines that exist in the old, but not in the current will be listed and preceded by a less-than symbol (<). Any lines that exist in the current, but not in the old will be listed and preceded by a greater-than symbol (>). Lines that are the same in both files are not listed; for example, files that are identical will produce no output from the diff command. If the location or description changes, lines preceded by both < and > will be output.

If the system is configured with more than one logical partition with Linux installed, repeat “Step 1321-35” and “Step 1321-36” for all logical partitions that have Linux installed.

Step 1321-37

Was the location of one and only one device recorded in “Step 1321-36”?

No If you previously answered Ye s to “Step 1321-37,” return the system to its original configuration.

This ends the procedure. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

If you did not previously answer Ye s to “Step 1321-37,” go to “Step 1321-38” on page 69.

Yes Perform the following steps one at a time. Power off the system before performing each step. After

performing each step, power on the system and go to “Step 1321-34.”

1. Check all connections from the system to the device.

2. Replace the device (for example, tape or DASD)

3. If applicable, replace the device backplane.

4. Replace the device cable.

5. Replace the adapter.

6. If the adapter resides in an I/O drawer, replace the I/O backplane.

68 IntelliStation POWER 9114 Model 275 Service Guide

7. If the device adapter resides in the CEC, replace the I/O riser card, or the CEC backplane where the device adapter is located.

8. Call service support. Do not go to “Step 1321-34” on page 68.

Step 1321-38

Does the system appear to stop or hang before reaching the login prompt or did you record any problems with resources in “Step 1321-36” on page 68?

Note: If the system console or VTERM window is always blank, choose NO. If you are sure the console

or VTERM is operational and connected correctly, answer the question for this step.

No Go to “Step 1321-39.”

There may be a problem with an I/O device. Go to “MAP 1542: I/O Problem Isolation” on page 89.

Yes

In MAP 1542, when instructed to boot the system, boot a full system partition.

Step 1321-39

Boot the AIX standalone diagnostics, and run diagnostics in problem determination mode on all resources. Be sure to boot a full system partition. Ensure that AIX diagnostics was run on all known resources. Yo u may need to select each resource individually and run diagnostics on each resource one at a time.

Did AIX standalone diagnostics find a problem?

No Go to “Step 1321-43” on page 70.

Go to the table in “Entry MAP” on page 41 with each error code or SRN you have recorded. Until

Yes

the problem has been corrected, perform the indicated actions, one at a time, for each SRN or error code not already processed in “Step 1321-37” on page 68. If all recorded SRNs or error codes have been processed and the problem has not been corrected, go to “Step 1321-43” on page 70.

Step 1321-40

Does the system have Linux installed on one or more partitions?

No Go to “Step 1321-14” on page 62.

Go to “Step 1321-22” on page 64.

Yes

Step 1321-41

Were any location codes recorded in Steps 1321-1, 1321-22, 1321-25, 1321-27, 1321-29, 1321-31, or 1321-32?

No Go to “Step 1321-34” on page 68.

Replace, one at a time, all parts whose location code was recorded in Steps 1321-1, 1321-22,

Yes

1321-25, 1321-27, 1321-29, 1321-31, and 1321-32 that have not been replaced. Power off the system before replacing a part. After replacing the part, power on the system to check if the problem has been corrected. Go to “Step 1321-42” when the problem has been corrected, or all parts in the location codes list have been replaced.

Step 1321-42

Was the problem corrected in Step 1321-41?

No Go to “Step 1321-34” on page 68.

Return the system to its original configuration. This ends the procedure. Go to ″MAP 0410: Repair

Yes

Checkout″ in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems.

Chapter 3. Maintenance Analysis Procedures (MAPs) 69

Step 1321-43

Were any other symptoms recorded in step 1321-1?

No Call support.

Go to the “Quick Entry MAP” on page 43 with each symptom you have recorded. Perform the

Yes

indicated actions for all recorded symptoms, one at a time, until the problem has been corrected. If all recorded symptoms have been processed and the problem has not been corrected, call support.

70 IntelliStation POWER 9114 Model 275 Service Guide

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

Note: If you are working on a system that not managed by an HMC go to ″MAP 0410: Repair Checkout″

in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems

Step 1322-1

For future reference, record the SRC or symptom and the location code of the FRU you replaced.

Step 1322-2

For Service Focal Point operating instructions, refer to “Service Focal Point” on page 37. At the HMC, open Service Focal Point and examine the service action event log for any open service action events.

Step 1322-3

Are there any service action events that are open?

No If the system attention LED is still on, use the HMC to turn off the LED as described in “Resetting

the System Attention LED” on page 38. This completes the repair, return the system to the customer.

Yes Go to “Step 1322-4”.

Step 1322-4

Record the list of open service action events.

Step 1322-5

From the list of serviceable events recorded in “Step 1322-4,” perform “Step 1322-6” through “Step 1322-33” on page 74 for each open service action event.

Step 1322-6

Determine the error class of the serviceable event. Record for future use.

Step 1322-7

Examine the details of the open service action event.

Is the error code associated with this service action event the same as recorded in ″Step 1322-1″?

No Go to “Step 1322-8.”

Yes Go to “Step 1322-11” on page 72.

Step 1322-8

Examine the FRU list of the service action event.

Are there any FRUs listed for the service action event?

No Go to “Step 1321-11” on page 62.

Yes Go to “Step 1321-9” on page 62.

Chapter 3. Maintenance Analysis Procedures (MAPs) 71

Step 1322-9

Is the FRU list identical (same FRUs, same number of FRUs, and same order of FRUs) to the FRU list of the error code recorded in “Step 1322-1” on page 71?

No Go to “Step 1322-10.”

Yes Go to “Step 1322-11.”

Step 1322-10

The FRU list is different.

Is the FRU you replaced and recorded in “Step 1322-1” on page 71 in the list of FRUs for this service action event?

No Go to “Step 1322-33” on page 74.

There are service action events that will remain open when you leave this MAP. Further

Note:

service actions may be required to complete the repair.

Go to “Step 1322-11.”

Yes

Step 1322-11

Examine the details of this service action event, and record the partition(s) involved in this service action event for use in a later step.

Step 1322-12

Is the error code associated with this service action event of the form A11-xxx or A01-xxx?

No Go to “Step 1322-17” on page 73.

Yes Go to “Step 1322-13.”

Step 1322-13

Have you begun a list of “Axx” partitions from prior service action events that you processed in this MAP?

No Go to “Step 1322-14.”

Yes Go to “Step 1322-15.”

Step 1322-14

Begin a new list of “Axx” partitions by copying the list of partitions obtained in “Step 1322-11.” Go to “Step 1322-16” on page 73.

Step 1322-15

Add the partition list obtained in “Step 1322-11” to the existing list of “Axx” partitions obtained from processing previous service action events in this MAP.

72 IntelliStation POWER 9114 Model 275 Service Guide

Step 1322-16

Remove all entries in the list of all partition(s) you recorded in “Step 1322-11” on page 72. If you are referred to the list of partition(s) obtained in “Step 1322-11” on page 72 in future steps, the list is empty. Go to “Step 1322-17.”

Step 1322-17

Select and highlight the service action event from the “Error Associated With This Serviceable Event” window.

Step 1322-18

Click Close Event.

Step 1322-19

Add comments for the serviceable event. Include any unique additional information. Click OK.

Step 1322-20

The following steps will add or update FRU information.

Step 1322-21

Did you replace, add, or modify a FRU of the open service action event?

No Go to “Step 1322-23.”

Yes Go to “Step 1322-22.”

Step 1322-22

From the FRU list, select a FRU that you need to update. Double-click on the FRU, and update the FRU information. Go to “Step 1322-24.”

Step 1322-23

Select the No FRU Replaced for this Serviceable Event option.

Step 1322-24

Click OK to close the service action event.

Step 1322-25

Is the list of all partition(s) you recorded in “Step 1322-11” on page 72 empty?

No Go to “Step 1322-26.”

Yes Go to “Step 1322-33” on page 74.

Step 1322-26

Does the list of all partition(s) you recorded in “Step 1322-11” on page 72 contain more than one entry?

No Go to “Step 1322-33” on page 74.

Yes Go to “Step 1322-27” on page 74.

Chapter 3. Maintenance Analysis Procedures (MAPs) 73

Step 1322-27

Is the error class recorded in “Step 1322-6” on page 71 AIX?

No Go to “Step 1322-33.”

Yes Go to “Step 1322-28.”

Step 1322-28

Perform the following steps for each entry in the list of all partition(s) you recorded in “Step 1322-11” on page 72, except the partition you were using to debug the original problem.

Step 1322-29

From the HMC virtual terminal window of a partition in the list of all partitions, type diag at the AIX command prompt.

Step 1322-30

1. When the diagnostic operating instructions are displayed, press Enter.

2. Select the Task Selection option.

Note: If the terminal type is not defined, you are prompted to define it before you can proceed.

3. Select the Log Repair option.

4. Select the resource associated with the repair action. If the repair action was reseating a cable or adapter, select the resource associated with that repair action. If the resource associated with your repair action is not displayed on the Resource List, select sysplanar0.

5. Click commit after you have made your selection.

Step 1322-31

Exit from diagnostics in this partition and return to the AIX prompt.

Step 1322-32

Have all the partitions in the list of all partition(s) you recorded in “Step 1322-11” on page 72 been processed?

No Go to “Step 1322-28” to process the next partition in the list you recorded in “Step 1322-11” on

page 72.

Yes Go to “Step 1322-33”.

Step 1322-33

Have all the serviceable events recorded in “Step 1322-4” on page 71 been processed?

No Go to “Step 1322-5” on page 71 and process the next service action event in the list of

serviceable events recorded in “Step 1322-4” on page 71.

Yes Go to “Step 1322-34” on page 75.

74 IntelliStation POWER 9114 Model 275 Service Guide

Step 1322-34

While processing all service action events, were you directed to “Step 1322-14” on page 72?

No If the system attention LED is still on, use the HMC to turn off the LED as described in “Resetting

the LED when a System is Running AIX” on page 38. This completes the repair. Return the system to the customer.

If during the processing of the list of open service action events, some service action

Note:

events remained open, further service actions may be required to complete the repair.

Yes Go to “Step 1322-35.”

Step 1322-35

Perform the following steps for each entry in the list of “Axx” partitions you began recording in “Step 1322-14” on page 72, except the partition you were using to debug the original problem.

Step 1322-36

From the HMC virtual terminal window of a partition in the list of “Axx” partitions, type diag at the AIX command prompt.

Step 1322-37

1. When the diagnostic operating instructions are displayed, press Enter.

2. Select the Task Selection option.

Note: If the terminal type is not defined, you are prompted to define it before you can proceed.

3. Select the Log Repair option.

5. Click commit after you have made your selection.

Step 1322-38

Exit from diagnostics in this partition and return to the AIX prompt.

Step 1322-39

Have all the partitions in the list of “Axx” partitions(s) you began recording in “Step 1322-14” on page 72 been processed?

No Go to “Step 1322-35” to process the next partition in the list you recorded in “Step 1322-14” on

page 72.

Yes If the system attention LED is still on, use the HMC to turn off the LED as described in “Resetting

the LED when a System is Running AIX” on page 38. This completes the repair. Return the system to the customer.

If during the processing of the list of open service action events, some service action

Note:

events remained open, further service actions may be required to complete the repair.

Chapter 3. Maintenance Analysis Procedures (MAPs) 75

MAP 1520: Power

Notes:

1. This is not a start-of-call MAP. Use this Power MAP only if you have been directed here from another MAP, an SRN in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems, or an error code.

2. This procedure is used to locate power problems in system units. If a problem is detected, this procedure helps you isolate the problem to a failing unit.

3. The Model 275 can accommodate two power supplies with separate power receptacles on the rear of the power supply. There are three LEDs located on the front and top of the power supply:

v AC Good LED (green) v DC Good LED (green) v Power Supply Fault Indicator LED (amber)

The LEDs indicate the condition of the power supply. The meaning of each LED and the conditions that light it are explained in this section. For additional information, refer to “Component LEDs” on page

309..

4. The condition of two power supplies present, but only one working, can be determined by the service processor and a warning level EPOW.

5. Observe the following safety notices during service procedures.

DANGER

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

An 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.

Before installing or removing signal cables, ensure that the power cables for the system unit and all attached devices are unplugged.

When adding or removing any additional devices to or from the system, ensure that the power cables for those devices are unplugged before the signal cables are connected. If possible, disconnect all power cables from the existing system before you add a device.

Use one hand, when possible, to connect or disconnect signal cables to prevent a possible shock from touching two surfaces with different electrical potentials.

During an electrical storm, do not connect cables for display stations, printers, telephones, or station protectors for communications lines.

D05

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

76 IntelliStation POWER 9114 Model 275 Service Guide

DANGER

prevent electrical shock hazard, disconnect all power cables from the electrical outlet before

To relocating the system.

D01

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:

v Power subsystem FRUs v System unit FRUs v I/O adapter identify LED v Disk drive 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 may 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 205. See “System Information Menu” on page 205 for information on how to use the LED Control Menu.

Any identify LED in the system may also be flashed by using the “Identify and Attention Indicators” task in the AIX diagnostic programs. The procedure for operating the Identify and Attention Indicators task in the AIX diagnostics is outlined in the chapter entitled “Tasks and Service Aids” in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems, order number SA38-0509.

If the service processor menus and the AIX diagnostics are not available, the FRU identify LEDs may be flashed by one using the open firmware prompt. If the system is configured as a full partition, the system can be booted to the open firmware prompt and the FRU-LED-MENU command entered. A menu displays that will allow you to turn on the desired FRU identify LED. For instructions on setting up the boot mode to enable the boot to the open firmware prompt, see the “System Power Control Menu” on page 202.

Find the symptom in the following table; then follow the instructions given in the action column.

Symptom Action

The system will not power on and no error codes are available.

Error code 1011 1B0x in the SPCN error codes table directed you here.

Go to “MAP 1521: System Unit With Power Failure and No Error Codes” on page 78.

Go to “MAP 1523: The SPCN Error Codes Table Directed You Here and the Error Code is 1011 1B0x” on page 84.

Chapter 3. Maintenance Analysis Procedures (MAPs) 77

MAP 1521: System Unit With Power Failure and No Error Codes

Step 1521-1

Do the following:

1. Place the deskside unit into a comfortable position for you to work on.

2. Remove the service access cover as described in “Removing the Service Access Cover” on page 249.

You may have been directed to this MAP for one or more of the following reasons. From the list below, select the item that best describes the state of the system and go to the appropriate step in these MAPs:

v The ac power supply power LEDs are not on. The power LEDs on the operator panel and the power

LEDs on the rear of the system unit are not blinking. The operator panel display is blank. Go to “Step 1521-5.”

v The ac power supply power LED(s) are on. Power LEDs, for ac power supplies, on the operator panel

and the rear of the system unit are not blinking, and the operator panel display is blank. Go to “Step 1521-7” on page 79.

v The ac power supply power LEDs are on. Power LEDs located on the operator panel and the rear of

the system unit are blinking and OK is displayed on the operator panel. When the power button, located on the operator panel, is pressed: – The power LED, located on the operator panel, does not come on. – None of the cooling fans start to turn.

Go to “Step 1521-7” on page 79.

v The ac power supply power LEDs are on. The power LED, located on the operator panel, is blinking

and OK is displayed on the operator panel. When the power button on the operator panel is pressed, the power LED on the operator panel, comes

on and all the fans start to turn. However, the dc power LEDs located on the power supplies, and the power LED located on the operator panel, and the cooling fans do not stay on.

Go to “Step 1521-7” on page 79.

v An SRN referenced in the RS/6000 Eserver pSeries Diagnostic Information for Multiple Bus Systems

listed MAP 1521 in the ″Actions/Descriptions″ column. Go to “Step 1521-11” on page 81.

Step 1521-2

Go to “Step 1521-3.”

Step 1521-3

Go to “Step 1521-4.”

Step 1521-4

Go to “Step 1521-5.”

Step 1521-5

Turn off the power and do the following:

1. Unplug the power cables from the wall outlet.

2. Unplug the power cables from the system unit.

3. Check that the power cables have continuity.

4. Check that the wall outlet has been wired correctly with the correct voltage.

Did you find a problem?

78 IntelliStation POWER 9114 Model 275 Service Guide

NO Go to “Step 1521-6.”

YES Correct the problem. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 Eserver pSeries

Diagnostic Information for Multiple Bus Systems.

Step 1521-6

1. One of the following may be defective:

v Power supplies v VRMs v Memory DIMMs v System backplane

To test each FRU, exchange the FRUs that have not already been exchanged in the following order.

v Primary power supply v Redundant power supply (if installed) v VRM at U0.1-P1-V1 v VRM at U0.1-P1-V2 v VRM at U0.1-P1-V3 v Memory DIMMs v System backplane

Unplug the power cables from the system unit.

4. Exchange one of the FRUs in the list.

5. Connect the power cables to the system unit.

Do the ac power LEDs on the power supplies come on within 30 seconds after applying ac power?

NO Reinstall the original FRU.

Repeat this step until the defective FRU is identified or all the FRUs have been exchanged.

If the symptom did not change and all the FRUs have been exchanged, call your support representative for assistance.

YES Go to ″MAP 0410: Repair Checkout″ in the RS/6000 Eserver pSeries Diagnostic Information for

Multiple Bus Systems.

Step 1521-7

1. Unplug the power cables from the system unit.

2. Exchange the operator panel assembly.

3. Plug the power cables into the system unit and wait for the OK prompt located on the operator panel display.

4. Turn on the power.

Does the power LED on the operator panel come on and stay on?

NO Reinstall the original operator panel assembly. Go to “Step 1521-8.”

YES Go to ″MAP 0410: Repair Checkout″ in the RS/6000 Eserver pSeries Diagnostic Information for

Multiple Bus Systems.

Step 1521-8

1. Turn off the power.

2. Unplug the power cables from the system unit.

Chapter 3. Maintenance Analysis Procedures (MAPs) 79

3. Record the slot numbers of all the adapters. Label and record the location of any cables attached to the adapters. Disconnect any cables attached to the adapters and remove all the adapters

4. Remove all but one quad of memory DIMMs from the system planar.

5. Unplug the signal and power cables from the DASD backplane.

6. Unplug the disk drives from the DASD backplane.

7. Unplug the signal and power cables from any devices in the media bays.

8. Remove all the fans.

9. Plug the power cables into the system unit.

10. Turn on the power.

Does the power LED on the operator panel come on and stay on?

NO Go to “Step 1521-9.”

YES Go to “Step 1521-10.”

Step 1521-9

Note: Either the system backplane or the power supplies may be defective.

To test each FRU, exchange the FRUs that have not already been exchanged in the following order:

1. Primary power supply

2. Redundant power supply (if installed)

3. VRM at U0.1-P1-V1

4. VRM at U0.1-P1-V2

5. VRM at U0.1-P1-V3

6. Memory DIMMs

7. System backplane.

Perform the following procedures as you exchange each of the above FRUs in the order listed:

1. Turn off the power.

2. Unplug the power cable from the system unit.

3. Exchange one of the FRUs in the list.

4. Connect the power cable to the system unit.

5. Turn on the power.

Does the power LED on the operator panel come on and stay on?

NO Reinstall the original FRU.

Repeat this step until the defective FRU is identified or all the FRUs have been exchanged.

If the symptom did not change and all the FRUs have been exchanged, call your service support person for assistance.

YES Go to ″MAP 0410: Repair Checkout″ in the RS/6000 Eserver pSeries Diagnostic Information for

Multiple Bus Systems.

Step 1521-10

One of the parts that was removed or unplugged is causing the problem. Install or connect the parts in the following order:

1. Memory DIMMs

2. DASD backplanes

80 IntelliStation POWER 9114 Model 275 Service Guide

3. Disk drives

4. Media bay devices

5. PCI adapters, lowest slot to highest slot

6. Fans

Turn on the power after each part is installed or connected. If the system does not power on or the power LED located on the operator panel does not stay on, the most recently installed or connected part is causing the failure.

Perform the following procedures as you exchange each of the above FRUs in the order listed:

1. Turn off the power.

2. Unplug the power cable from the system unit.

3. Install or connect one of the parts in the list.

4. Plug the power cable into the system unit.

5. Turn on the power.

Does the power LED on the operator panel come on and stay on?

NO Replace the last part installed. If memory DIMMs on the system planar were the last parts

installed, exchange the memory DIMMs one at a time to isolate the failing module. If all memory DIMMs have been exchanged and the problem is not resolved, replace the system backplane.

Repeat until all the parts have been installed. Go to “Step 1521-9” on page 80.

YES If all parts have been reinstalled, go to ″MAP 0410: Repair Checkout″ in the RS/6000 Eserver

pSeries Diagnostic Information for Multiple Bus Systems. If all parts have not been reinstalled,

continue reinstalling parts in the in this step.

Step 1521-11

Does the system contain two power supplies?

NO Go to “Step 1521-12.”

YES Go to “Step 1521-14” on page 82.

Step 1521-12

Shut down the system, and remove all power cables from the rear of the system unit.

Exchange the following FRUs in the order listed:

1. Power supply

2. VRM at U0.1-P1-V1

3. VRM at U0.1-P1-V2

4. VRM at U0.1-P1-V3

5. System backplane

Restart the system and perform error log analysis.

Do you get an SRN indicating a voltage sensor is out of range?

NO The last FRU exchanged is defective. Go to ″MAP 0410: Repair Checkout″ in the RS/6000

Eserver pSeries Diagnostic Information for Multiple Bus Systems.

YES Reinstall the original FRU.

Repeat the FRU replacement steps until a defective FRU is identified or all the FRUs have been exchanged.

Chapter 3. Maintenance Analysis Procedures (MAPs) 81

If the symptom did not change and all FRUs have been exchanged, go to “Step 1521-13.”

If the symptom changed, check for loose cards, cables, and obvious problems. If you do not find a problem, go to the “Quick Entry MAP” on page 43 and follow the instructions for the new symptom.

Step 1521-13

Check that the wall outlet is properly wired and is providing the correct voltage.

Did you find a problem?

NO Go to “MAP 1548: System Processor Problem Isolation” on page 90.

YES Correct the problem. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 Eserver pSeries

Diagnostic Information for Multiple Bus Systems.

Step 1521-14

Because the Model 275 and Model 275 accommodate redundant power supplies, it is not necessary to power down the system when replacing a power supply.

The power supplies are symmetrical. Replacement starts with the unit closest to the system wall of the system drawer (power supply 1). For instructions on replacing a power supply, refer to “Power Supply” on page 287.

Notes:

1. Always service first the power supply whose green LED, located on the front of the power supplies, is out.

2. Before removing a power supply, be sure the redundant power supply is operational by observing the green LED. The green LED must be on solid.

Replace the following FRUs in order:

1. Power supply #1 (primary)

2. Power supply #2 (redundant)

Perform error log analysis.

Do you receive an SRN indicating a voltage sensor out of range?

NO The last FRU exchanged is defective. Go to ″MAP 0410: Repair Checkout″ in the RS/6000

Eserver pSeries Diagnostic Information for Multiple Bus Systems

YES Reinstall the original FRU.

Repeat the FRU replacement steps until a defective FRU is identified or all the FRUs have been exchanged.

If the symptom did not change and all FRUs have been exchanged, go to “Step 1521-15.”

If the symptom changed, check for loose cards, cables, and obvious problems. If you do not find a problem, go to the “Quick Entry MAP” on page 43 and follow the instructions for the new symptom.

Step 1521-15

The problem is within the system unit hardware or with the line voltage/wiring.

Shut down the system, and remove the power cable from the system unit.

82 IntelliStation POWER 9114 Model 275 Service Guide

IBM 9114-275, IntelliStation POWER 9114 275 Service Manual

Specifications and Main Features

Frequently Asked Questions

User Manual