RS/6000 Eserver pSeries

Diagnostic Information for Multiple Bus Systems
V ersion 5.1.0.0

SA38-0509-14

Fifteenth Edition (April 2002) Before using this information and the product it supports, read the information in Appendix F, “Notices” on page 663. A reader’s comment form is provided at the back of this publication. If the form has been removed, address comments to Information Development, Department H6DS-905-6C006, 11400 Burnet Road, Austin, Texas 78758-3493. To send comments electronically, use this commercial internet address: aix6kpub@austin.ibm.com. Any information that you supply may be used without incurring any obligation to you. © International Business Machines Corporation 1995, 2001. All rights reserved. Note to U.S. Government Users, Restricted Rights -- Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
About This Book . . . . Who Should Use This Book . How to Use This Book . . ISO 9000 . . . . . . . Online Publications. . . . Related Publications . . . Trademarks . . . . . . CSU/SSR Feature Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix . ix . ix . ix . ix . x . x . xii

Chapter 1. Service Hints . . . . . . . . . . . . . . . . . . . . 1 Using the Maintenance Analysis Procedures . . . . . . . . . . . . . . 1 About Slow Boot . . . . . . . . . . . . . . . . . . . . . . . 2 Multiple SRN or Error Code Reporting and Handling . . . . . . . . . . . . 2 General SCSI Configuration Checks . . . . . . . . . . . . . . . . . 3 High Availability or Multiple SCSI System Checks . . . . . . . . . . . . . 3 SCSI-2 Single-Ended Adapter PTC Failure Isolation Procedure . . . . . . . . 4 External SCSI-2 Single-Ended Bus PTC Isolation Procedure . . . . . . . . . 5 Internal SCSI-2 Single-Ended Bus PTC Isolation Procedure . . . . . . . . . 7 SCSI-2 Differential Adapter PTC Failure Isolation Procedure . . . . . . . . . 9 External SCSI-2 Differential Adapter Bus PTC Isolation Procedure . . . . . . . 10 Dual-Channel Ultra SCSI Adapter PTC Failure Isolation Procedure . . . . . . 13 Chapter 2. Start of Call MAP . Chapter 3. Fast Path MAP Fast Path Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 . 17 . 18 . 29 . 29 . 41 . 41 . 45 . 45 . 47 . 47 . 51 . 51 . 59 . 59 . 63

Chapter 4. MAP 0020: Problem Determination Procedure Purpose of This MAP. . . . . . . . . . . . . .

Chapter 5. MAP 0025: SCSI RAID Problem Determination Procedure Purpose of This MAP. . . . . . . . . . . . . . . . . . Chapter 6. MAP 0030: Additional Problem Determination. Purpose of This MAP. . . . . . . . . . . . . . Chapter 7. MAP 0040: Intermittent Problem Isolation . Purpose of This MAP. . . . . . . . . . . . . Chapter 8. MAP 0050: SCSI Bus Problems . Purpose of This MAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 9. MAP 0070: 888 Sequence in Operator Panel Display . Purpose of This MAP. . . . . . . . . . . . . . . . . Chapter 10. MAP 0080: System Bus Problem Isolation . . . .

iii

Purpose of This MAP.

.

.

.

.

.

.

.

.

.

.

.

.

. . .

. . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. 63 . 67 . 67 . 77 . 77 . 83 . 83 . 91 . 91 . 93 . 93 . 97 . 99 . 99 . 103 . 103 . 113 . 113 . 115 . 115 . 117 . 117 . 119 . 119 . 127 . 127 . 129 . 129 . . . . . . 133 133 135 135 136 137

Chapter 11. MAP 0210: General Problem Resolution . Purpose of This MAP. . . . . . . . . . . . .

Chapter 12. MAP 0220: Hot-Swap FRU Problem Resolution . Purpose of This MAP. . . . . . . . . . . . . . . Chapter 13. MAP 0230: Platform Error Problem Resolution . Purpose of This MAP. . . . . . . . . . . . . . .

Chapter 14. MAP 0235: System Array Self-Repair Problem Resolution . Purpose of This MAP. . . . . . . . . . . . . . . . . . . Chapter 15. MAP 0240: Memory Problem Resolution . Purpose of This MAP. . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 16. MAP 0250: Unexpected System Halts During Diagnostics . Chapter 17. MAP 0260: System Hangs During Resource Configuration . Purpose of This MAP. . . . . . . . . . . . . . . . . . . Chapter 18. MAP 0270: SCSI RAID Problem Resolution and Verification . Purpose of This MAP . . . . . . . . . . . . . . . . . . . Chapter 19. MAP 0280: Boot Problem Resolution . Purpose of This MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 20. MAP 0290: Missing Resource Problem Resolution . Purpose of This MAP . . . . . . . . . . . . . . . .

Chapter 21. MAP 0291: Missing Device or Bus Problem Resolution Purpose of This MAP . . . . . . . . . . . . . . . . . Chapter 22. MAP 0410: Repair Checkout . Purpose of This MAP . . . . . . . . Chapter 23. MAP 0420: System Checkout. Purpose of This MAP . . . . . . . . Chapter 24. Installation Checkout Installation Checkout Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 25. General Diagnostic Information . . AIX Operating System Message Files . . . . . CE Login . . . . . . . . . . . . . . Automatic Diagnostic Tests . . . . . . . . CPU and Memory Testing and Error Log Analysis . Diagnostic Programs . . . . . . . . . .

iv

Diagnostic Information for Multiple Bus Systems

Periodic Diagnostics . . . . . . . . . . . . . . . . . . . Automatic Error Log Analysis (diagela) . . . . . . . . . . . . . Log Repair Action . . . . . . . . . . . . . . . . . . . . System Fault Indicator and System Identify Indicator . . . . . . . . . Testing the Line Printer . . . . . . . . . . . . . . . . . . Array Bit Steering . . . . . . . . . . . . . . . . . . . . Running Diagnostics on the Native Serial Port on a Full Machine Partition with HMC Attached . . . . . . . . . . . . . . . . . . . . . Enhanced I/O Error Handling. . . . . . . . . . . . . . . . . Chapter 26. Using Standalone and Online Diagnostics . . Standalone and Online Diagnostics Operating Considerations . Online Diagnostics Mode of Operation . . . . . . . . Standalone Diagnostic Operation . . . . . . . . . . General Information about Multiple Systems. . . . . . . Determining System Architecture . . . . . . . . . . High-Availability SCSI . . . . . . . . . . . . . . Diagnostic Summary . . . . . . . . . . . . . . Diagnostics Tasks and Resources . . . . . . . . . . SCSI RAID Descriptions and Diagnostic Procedures . . . . Chapter 27. Introduction to Tasks and Service Aids Tasks . . . . . . . . . . . . . . . . Add Resource to Resource List . . . . . . . . AIX Shell Prompt . . . . . . . . . . . . Analyze Adapter Internal Log. . . . . . . . . Backup and Restore Media . . . . . . . . . Certify Media . . . . . . . . . . . . . . Change Hardware Vital Product Data . . . . . . Configure Dials and LPF Keys . . . . . . . . Configure ISA Adapter . . . . . . . . . . . Configure Reboot Policy . . . . . . . . . . Configure Remote Maintenance Policy . . . . . Configure Ring Indicate Power-On Policy. . . . . Configure Ring Indicate Power On . . . . . . . Configure Service Processor . . . . . . . . . Configure Surveillance Policy . . . . . . . . Create Customized Configuration Diskette . . . . Delete Resource from Resource List . . . . . . Disk Maintenance . . . . . . . . . . . . Display Configuration and Resource List . . . . . Display Firmware Device Node Information . . . . Display Hardware Error Report . . . . . . . . Display Hardware Vital Product Data . . . . . . Display Machine Check Error Log . . . . . . . Display Microcode Level . . . . . . . . . . Display or Change Bootlist . . . . . . . . . Display or Change Diagnostic Run-Time Options . . Display Previous Diagnostic Results . . . . . . Display Resource Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . .

139 140 142 142 143 143

. 143 . 144 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 145 152 155 157 158 159 159 160 162 169 170 171 171 171 172 173 176 177 177 178 179 181 181 181 184 184 185 185 186 186 186 187 187 187 187 188 189 189

Contents

v

Display Service Hints . . . . . . . . . . . . Display Software Product Data . . . . . . . . . Display System Environmental Sensors . . . . . . Display Test Patterns . . . . . . . . . . . . Display USB Devices . . . . . . . . . . . . Download Microcode . . . . . . . . . . . . Fibre Channel RAID Service Aids . . . . . . . . Flash SK-NET FDDI Firmware . . . . . . . . . Format Media . . . . . . . . . . . . . . . Gather System Information . . . . . . . . . . Generic Microcode Download . . . . . . . . . Hot Plug Task . . . . . . . . . . . . . . . Local Area Network Analyzer . . . . . . . . . . Log Repair Action . . . . . . . . . . . . . Periodic Diagnostics . . . . . . . . . . . . PCI RAID Physical Disk Identify . . . . . . . . . Process Supplemental Media . . . . . . . . . Run Diagnostics . . . . . . . . . . . . . . Run Error Log Analysis . . . . . . . . . . . Run Exercisers . . . . . . . . . . . . . . Save or Restore Hardware Management Policies . . . Save or Restore Service Processor Configuration . . . SCSI Bus Analyzer . . . . . . . . . . . . . SCSD Tape Drive Service Aid . . . . . . . . . Spare Sector Availability . . . . . . . . . . . SSA Service Aid . . . . . . . . . . . . . . System Fault Indicator . . . . . . . . . . . . Update Disk-Based Diagnostics . . . . . . . . . Update System or Service Processor Flash . . . . . Update System Flash . . . . . . . . . . . . 7135 RAIDiant Array Service Aid . . . . . . . . 7318 Serial Communications Network Server Service Aid

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

189 190 190 192 192 192 194 195 195 197 197 197 201 201 202 202 202 203 203 203 206 206 207 208 209 209 210 211 211 214 214 215 217 217 230 234 236 236 239 243 243 244 244

Chapter 28. Diagnostics Numbers and Location Codes . Operator Panel Display Numbers . . . . . . . . . Diagnostic Load Progress Indicators . . . . . . . . Location Codes for RSPC Model Architecture System Units Location Codes for CHRP Model Architecture System Units Physical Location Codes . . . . . . . . . . . . AIX Location Codes . . . . . . . . . . . . . . Chapter 29. Using the SRN List . . Service Request Number . . . . . Using the Service Request Number List Service Request Number Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 30. Five-Digit SRNs 10104 through SSA03 Service Request Number List . . . . . . . . Chapter 31. SRNs 101-000 through 69d-701 . . .

. 247 . 247 . 259

vi

Diagnostic Information for Multiple Bus Systems

Chapter 32. SRNs 700-102 through 89c-302 . Chapter 33. SRNs 900-001 through xxxxxxx .

. .

. .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. 361 . 441 . 511 . 529 . . . . 535 535 536 538

Chapter 34. SRNs A00-(x)xxx through A1D-(x)xxx . Chapter 35. SRNs 2520-101 through 2590-(x)xxx . Chapter 36. Failing Function Codes (FFCs) Description of the Failing Function Code List Machine Types . . . . . . . . . . Failing Function Code List . . . . . . Chapter 37. FRU Cross-References . . . Using the FRU Name Cross-Reference List . Appendix A. Wrap Plugs. Appendix B. Test Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. 617 . 617 . 625 . 627 . 629 . 629 . . . . . . . . . . . . 633 634 635 635 637 637 639 639 641 651 654 662

Appendix C. System Memory Reference . System Unit Memory Combinations . . .

Appendix D. General Attributes Required When Using Additional Communication Attributes . . . . . . . Additional Keyboard Attributes . . . . . . . . . Additional Printer Attributes . . . . . . . . . . Appendix E. CHRP Error Log Structure . . . . CHRP Error Logs in AIX . . . . . . . . . . Versions of the Error Log Format . . . . . . . RTAS Error Return Format Fixed Part (All Versions) . Extended Error Log Formats . . . . . . . . . Version 2 Extension of CHRP Error Log Format . . RTAS General Extended Error Log Format, Version 3 Extended Log Debug Data . . . . . . . . . Appendix F. Notices . Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

a TTY Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. 663 . 665

Contents

vii

viii

Diagnostic Information for Multiple Bus Systems

About This Book
The diagnostic information contained in this book is common to all multiple bus system units. Any information or diagnostic procedure that is specific to a certain system unit or device is in the service guide for that system unit or device.

Who Should Use This Book
This book is used for problem isolation and service procedures by a service representative specifically trained on the system unit being serviced. This book combines operating instructions for hardware diagnostic programs with Maintenance Analysis Procedures (MAPs), corresponding Service Request Numbers (SRNs) and three-digit display codes. The SRNs are, in turn, keyed to failing function codes (FFCs) and corresponding part numbers for specific machine types.

How to Use This Book
This book has a version number in the title. Always use the book version that is equal to or greater than the first two digits of your diagnostics version level. For example, if your CD-ROM version is 2.2 or 2.25, use version 2.2 or higher of this diagnostics information manual. If you are analyzing a system problem, start with Chapter 2, “Start of Call MAP” on page 15. The SRN lists in Chapters 28-32 direct you to the correct failing function. A cross-reference by name, (such as adapter or device) to Failing Function Code can be found in Chapter 37, “FRU Cross-References” on page 617. Refer to Chapter 24, “Installation Checkout” on page 129 if you are checking the system unit or device after installation.

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

Online Publications
RS/6000 and pSeries publications are available online. To access the online books, visit our Web site at: http://www.rs6000.ibm.com/resource/hardware_docs/.

ix

Related Publications
The following books are used to isolate a problem in the system. v Adapters, Devices, and Cable Information for Multiple Bus Systems contains information about common device, adapter, and cabling of the system unit. v Site and Hardware Planning Information is a planning and site preparation guide. v Installation Guide contains the instructions for installing the operating system. v RS/6000 SP System Service Guide contains the service procedures that are specific to RS/6000 SP systems. v If you are servicing a clustered Eserver, go to the Start of Call MAP 100 in the Clustered Eserver Installation and Service Guide. v The service documentation for the system units or devices contains the service procedures that are specific to that device or system unit. The service documentation contains the following: – Reference information such as data flow, cable diagrams, and specifications – System unit or device-specific Maintenance Analysis Procedures (MAPs), such as the power MAP – Removal and replacement procedures – The system unit or device installation procedures – Parts diagrams and parts lists.

Trademarks
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: v AIX v e (logo) v ESCON v IBM v LANStreamer v Portmaster v POWER Gt1 v POWER Gt3 v POWER Gt4 v pSeries v RETAIN v RS/6000 v S/370 v SP v TURBOWAYS Other company, product, and service names may be trademarks or service marks of others.

x

Diagnostic Information for Multiple Bus Systems

CSU/SSR Feature Installation
Attention: The following information indicates which features on various systems/models are intended to be installed by the customer and which features are to be installed by a System Service Representative (SSR) as part of a Miscellaneous Equipment Specification (MES). This information is for systems/models available as of the edition date. Notes: 1. CSU = Customer Set-Up. 2. SSR = System Service Representative. 3. For a description of Feature Codes. See the Feature Code Descriptions below the following table.

4. The 7013 Model J30 was announced as CSU. U.S. practice has been for SSR installation. 5. The 7014 rack is SSR install. However, the system units which are installed into the 7014 may be CSU. Check the matrix below to verify which system units should be installed by the SSR or are CSU.
Machine Type Model System CSU
1

Features/Options SSR Install

2

Customer Install None None None None None None None None None None All Other Features All Other Features FC 2901, 2908, 2909, 2911, 2913, 3071, 3072, 3074, 3078, 3079, 3083 All Other Features All Features All Features None All Other Features

7006 7007 7008 7009 7010 7011 7012 7013 7015 7017 7024 7025 7026

(All) (All) (All) (All) (All) (All) (All) (All)
3

Yes Yes Yes Yes Yes Yes Yes No No No Yes Yes No

All Features All Features All Features All Features All Features All Features All Features All Features All Features All Features FC 6309 FC 2856, 6309, 6549 All Other Features

(All) (All) (All) (All) (All except B80)

7026 7027 7028 7040 7043 7044

(B80) (All) (All) (All) (All) (All)

Yes No Yes No Yes Yes

FC 4361, 4362, 4363 All Other Features All Features All Features FC 2856 & 6309 FC 2856 & 6309 c.All Other Features

Preface

xi

Machine Type

Model

System CSU

1

Features/Options SSR Install

2

Customer Install All Other Features None All Other Features None None None None

7046 7236 7248 7316 7317 7318 7319

(All) (All) (All) (All) (All) (All) (All)

Yes No Yes No No No No

FC 2856 & 6309 All Features FC 2856 All Features All Features All Features All Features

Feature Code 2616 2856 2901 2908 2909 2911 2913 3071 3072 3074 3078 3079 3080 3083 3084 3090 3133 3134 3137 3138 4361 4362 4363 6142 6147 6153 6294 6295 6309 6549

Feature Code Description Internal CD-ROM 2/4X/Tray Loading, 600KB/s PCI/Short/32bit/3.3 or 5V, 7250 Attach Adapter 4.5GB F/W Ultra SCSI DASD Module 9.1GB Ultra SCSI DASD Module 18.2GB Ultra SCSI DASD Module 9.1GB F/W Ultra SCSI DASD Module 9.1GB F/W Ultra Module, 1″ High 4.5GB SSA DASD Module, 1″ High 9.1GB SSA DASD Module, 1.6″ High 9.1GB SSA DASD Module, Hot Swap 9.1GB SSA DASD Module, 10K 9.1GB SSA DASD Module, 10K 4.5GB F/W SCSI DASD Module 2.2GB F/W SCSI DASD Module 4.5GB F/W SCSI DASD Module 9.1GB F/W SCSI DASD Module Cable SCSI, 3M, to F/W MC SCSI Adapter (SE OR Diff) Cable SCSI, 6M, to F/W MC SCSI Adapter (SE OR Diff) Cable SCSI/DIFF, 12M, to F/W MC SCSI Adapter Cable SCSI/DIFF, 18M, to F/W MC SCSI Adapter 1-Way 375MHz POWER3-II Processor Card 2-Way 375MHz POWER3-II Processor Card 2-Way 375MHz POWER3-II Processor Card (8MB L2/Processor) Internal 4mm 4/8GB Tape 8mm 5/10GB VDAT Tape 4mm Tape Drive + Autoloader, Horizontal Optional AC Power Supply for 7027 SCSI Drawers Optional bifurcated (Y-cable) Power Cord for 7027 SCSI Drawers Digital Trunk Quad Adapter, PCI/Long/32Bit/5V Additional Power Supply for 2nd and 3rd 6-Pks on Model F40

xii

Diagnostic Information for Multiple Bus Systems

Chapter 1. Service Hints
Most hardware errors in the AIX error log contain sysplanar0 as the resource name. The resource name identifies the resource that detected the error; it does not indicate that the resource is faulty or should be replaced. Use the resource name to determine the appropriate diagnostic to analyze the error.

Using the Maintenance Analysis Procedures
Some MAPs or procedures may ask whether the system is running one or more logical partition (LPAR) versus running a full machine partition. If you are not certain about the system configuration, ask the customer. If the system does not have an HMC (Hardware Management Console), then it is running a full machine partition (however, a system with an HMC may be running one or more logical partitions or running a full machine partition). On a partitioned system, some service aids may only be run in a partition that is set up with service authority. To set up a partition with service authority, ask the system administrator to refer to ″Partition Management Tasks″ within the Hardware Management Console Operations Guide. The maintenance analysis procedures (MAPs) provide the service representative a step-by-step procedure to analyze a problem with the system hardware. Hardware procedures are intended for use by a service representative trained on the system unit being serviced. Some of the devices that are supported by the diagnostic programs also have their own maintenance documentation. You may want to use the maintenance documentation for that device before running the diagnostics for the system. Sometimes the maintenance package for an attached device allows the customer to continue operating the system while that device is being diagnosed. You can use the diagnostic programs to check the adapter to which that device is attached. Begin all problem analysis with Chapter 2, “Start of Call MAP” on page 15. MAPs may direct you to run diagnostics. Information on how to run the diagnostics, in various modes, is in Chapter 25, “General Diagnostic Information” on page 133. These MAPs may direct you to other MAPs or to other service information. Be prepared to record code numbers and other data while using these MAPs. Some adapters may show a different SRN than expected if the adapter cannot be configured. If the SRN or FFC are listed by onscreen diagnostics, use that information first. Otherwise, use the part number that is on the adapter.

SRN and Failing Function Code (FFC) Discrepancies
SRNs listed in this book may not list the same FFCs and FRUs as reported by onscreen diagnostics. If the FRUs listed in this book do not solve the problem, check if any other FRUs are listed by onscreen diagnostics, and if so, try them.

1

SRNs with a source code of G are the result of an error log entry. more than one SRN or error code may be reported. See the ″Error Code to FRU Index″ in the system service guide to identify those error codes that require special handling. Multiple 8-digit error codes may not be listed in the correct order. 5. it does not matter which SRN is handled first. This can be specified using the System Power Control Menu on the service processor main menu. This may occur when there are multiple entries in the error log or when the diagnostic tests detect multiple hardware problems. When you run the diagnostics. 2. 6. Device SRNs and error codes (5-digit SRNs). 8-digit Error Codes. Online diagnostics must run in Advanced and Problem Determination Mode to obtain maximum isolation.About Slow Boot Some systems support a service mode fast or slow boot. Multiple SRN or Error Code Reporting and Handling The AIX® Diagnostics can generate SRNs using hardware tests or from error log analysis. The SRNs are normally displayed in the order in which the devices are tested and the error log entries analyzed. Follow the action for the SRN with the earliest time stamp first. Handle multiple SRNs and error codes in the following order: 1. use it in subsequent steps to continue problem analysis. If a new error code is reported. 4. Online diagnostics must be run in Advanced and Problem Determination Mode to obtain maximum isolation. 3. A slow-mode boot may yield a new 8-character error code on the operator panel and new errors in the service processor error log. If there are multiple SRNs within a group. SRNs with a source code other than F or G. A fast-mode boot skips much of the built-in diagnostic testing. Note: The priority for multiple SRNs with a source of G is determined by the time stamp of the failure. The diagnostics also report platform-unique 8-digit error codes detected and logged during POST. SRNs in the range of A01-xxx to A1D-xxx. do a slow-mode boot in service mode. 2 Diagnostic Information for Multiple Bus Systems . and device-unique error codes generated by the device diagnostics. SRNs with a source code of F do not provide maximum isolation. If you suspect a problem in the base system or can’t otherwise localize the defect. SRNs with a source code of G. SRNs with a source code of F. Error log entries logged against a single device type are displayed in descending order with the newest entry first.

Verify that the adapters and devices that you are working with are at the appropriate microcode levels for the customer situation. Diagnostics cannot be run against OEM devices. If the correct software is not in use. some SCSI errors should be expected when multiple adapters attempt to access the same SCSI device. 2. 4. and Cable Information for Multiple Bus Systems for more details on SCSI cabling. contact your service support structure for assistance. You must make the changes to the database only. If problems occur. If the diagnostics are run incorrectly on these devices. This can be done by using SMIT (SMIT Devices > SCSI Adapter > Change/Show characteristics of an adapter). If there are multiple SCSI adapters on the SCSI bus. Contact your service support structure if you need assistance with microcode issues. Verify that the cabling configuration does not exceed the maximum cable length for the adapter in use. and Cable Information for Multiple Bus Systems for more details on SCSI cabling issues. Devices.General SCSI Configuration Checks The following steps apply to all types of SCSI problems: 1. or if more than one system is attached to the same SCSI bus. then reboot the system in order for the change to take effect. Verify that all SCSI devices on the SCSI bus have a unique address. verify that the customer is using the appropriate software (such as HACMP or HANFS) to support such an arrangement. Verify that adapter and devices are at the appropriate microcode levels for the customer situation. be sure to run the proper diagnostics for the device. 3. High Availability or Multiple SCSI System Checks If you have a high-availability configuration. Devices. Also. Refer to Adapters. Chapter 1. misleading SRNs can result. change the address of at least one adapter. Note: Diagnostics defaults to using ID 7 (it is recommended that this ID not be used in high availability configurations). 4. Contact your service support if you need assistance with microcode issues. Verify that the cabling configuration does not exceed the maximum cable length for the adapter in use. Refer to the SCSI Cabling section in the Adapters. If you have more than one adapter on the bus. each adapter should have a unique address. Verify that all cables are connected securely and that both ends of the SCSI bus is terminated correctly. 5. Service Hints 3 . The default SCSI adapter address is always 7. do the following: 1. 5. Verify that the adapters and devices have unique SCSI addresses. 3. If RAID devices such as the 7135 or 7137 are attached. 6. Verify that all cables are connected securely and that there is proper termination at both ends of the SCSI bus. doing so results in misleading SRNs. 2.

then retest. start with the ″External Bus PTC Isolation Procedure″ for your type adapter. The procedures are found in this chapter. 4 Diagnostic Information for Multiple Bus Systems . It is unlikely that the PTC can be tripped by a defective adapter. use these procedures to determine if a short-circuit condition exists on the SCSI bus. If this procedure does not resolve the problem. Wait 5 minutes for the PTC resistor to fully cool. v If there is a combination of external and internal cables start with the ″External Bus PTC Isolation Procedure″ for your type adapter. The procedures are found in this chapter. These procedures determine if the PTC resistor is still tripped and then determine if there is a short somewhere on the SCSI bus. or device. The increase in resistance causes the PTC to halt current flow. terminator. v If there are no external cables attached. Determining Where to Start Use the following to determine the adapter configuration and select the proper procedure: v If there are external cables attached to the adapter. continue with the ″Internal Bus PTC Isolation Procedure″ for your type adapter. start with the “Internal SCSI-2 Single-Ended Bus PTC Isolation Procedure” on page 7. do not replace the adapter because of a tripped PTC resistor. The procedures are found in this chapter. The same positive temperature coefficient (PTC) resistor is used for both the internal and external buses.SCSI-2 Single-Ended Adapter PTC Failure Isolation Procedure Before replacing a SCSI-2 single-ended adapter. A fault (short-circuit) causes an increase in PTC resistance and temperature. The PTC returns to a low resistive and low temperature state when the fault is removed from the SCSI bus or when the system is turned off. The PTC protects the SCSI bus from high currents due to shorts on the cable. Unless instructed to do so by these procedures.

If there are internal cables attached continue to the “Internal SCSI-2 Single-Ended Bus PTC Isolation Procedure” on page 7. Connect the negative lead to the opposite side of the capacitor marked ″GND. allow the PTC resistor to cool and measure again. then do the following: a. then the resistance reading is high. 4. 5. Note: Some multi-function meters label the leads specifically for voltage measurements. If necessary. the resistance reading is low. 3. the SCSI bus is not faulted (shorted). be sure to probe both sides of the PTC where the solder joints and board come together. then there is no apparent cause for a PTC failure from this bus.External SCSI-2 Single-Ended Bus PTC Isolation Procedure Isolate the external SCSI bus PTC fault with the following procedure: Note: The external bus is of single-ended design. Locate Capacitor C1 and measure the resistance across it by using the following procedure: a. labeled Z1. This step determines if there is a short on the adapter. step 3 on page 7) is cool and in a low resistance state. the fault is on the adapter. v If there is a fault. typically below 10 Ohms. the reading is a function of the Ohmmeter used. Verify with a digital Ohmmeter that the internal PTC resistor. Note: Because this is a measurement across unpowered silicon devices. 1. Measuring across. When using this type of meter to measure resistance. b. Disconnect any internal and external cables from the adapter and remove the adapter from the system. repeat this step with the leads reversed. Connect the positive lead to the side of the capacitor where the + is indicated on the board near C1. Measure across C1 as previously described. If the resistance is still high. If the short circuit is not indicated with the leads reversed. typically hundreds of Ohms. Replace the adapter. Service Hints 5 . If there is no short present. proceed to the next step. The polarity of the test leads is not important. Chapter 1. v If the resistance measured was high. If you are not sure that your meter leads accurately reflect the polarity for measuring resistance. c. the plus lead and negative lead my not be labeled correctly. Ensure the system power and all externally attached device power is turned off. in this case above 10 Ohms. b.″ Be sure to probe at the solder joint where the capacitor and board come together. (refer to the illustration after Internal SCSI-2 Single-Ended Bus PTC Isolation Procedure. Because there are no cables attached. 2. typically less than 1/2 Ohm. All testing is accomplished with the power off. Be sure to probe at the solder joint where the capacitor and board come together. Reattach the external cable to the adapter.

as in the case of this procedure. Note: The SCSI-2 Fast/Wide and Ultra PCI Adapters use an onboard electronic terminator on the external SCSI bus. Go to Chapter 22. Troubleshoot the external SCSI bus by disconnecting devices and terminators. External SCSI-2 Single-Ended Bus Probable Tripped PTC Causes The following list provides some suggestions of things to check when the PTC is tripped: v A shorted terminator or cable. other than it is high. v A shorted device. When power is removed from the adapter. v Plugging or unplugging a cable or terminator while the system is turned on (hot plugging). v Intermittent PTC failures can be caused by improperly seated cable connectors. Replace the failing component. Some external terminators use an electronic terminator. which also goes to a high impedance state when power is removed. this procedure is designed to find a short or low resistance fault as opposed to the presence of a terminator or a missing terminator. “MAP 0410: Repair Checkout” on page 119. Therefore. 6 Diagnostic Information for Multiple Bus Systems . Measure across C1 to determine if the fault has been removed. Reseat the connector and flex the cable in an attempt to duplicate the fault condition across C1. the terminator goes to a high impedance state and the resistance measured cannot be verified. v Differential devices or terminators are attached to the single-ended SCSI bus. If the resistance is less than 10 Ohms.c. Check for bent pins on each connector and removable terminator. there is a possibility of a fault on the external SCSI bus.

typically less than 1/2 Ohm. Service Hints 7 . Verify with a digital Ohmmeter. 3. 1.Internal SCSI-2 Single-Ended Bus PTC Isolation Procedure Isolate the internal SCSI bus PTC resistor fault with the following procedure: Note: The internal bus is single-ended. that the internal PTC resistor. labeled Z1. Measuring across. The polarity of the test leads is not important. Disconnect any internal and external cables from the adapter then remove the adapter from the system. Refer to the following illustration. be sure to probe both sides of the PTC where the solder joints and board come together. Do not allow the probes to touch any other part of the component. If necessary. 2. is cool and in a low resistance state. Chapter 1. Note: Only the probe tips are touching the solder joints. allow the PTC to cool and measure again. Ensure that system power and all externally attached device power is turned off.

Because there are no cables attached. c. v If there is a fault. If you are not sure that your meter leads accurately reflect the polarity for measuring resistance. b.4. If there is no short present. a fault on the internal SCSI bus is possible. then do the following: a. 5. Measure across C1 to determine if the fault has been removed. v If the resistance is high and there is an internal cable to reattach. Connect the positive lead to the side of the capacitor where the + is indicated. above 25 Ohms. typically below 10 Ohms. c. Measure across C1 as described above. Note: Because this is a measurement across unpowered silicon devices. the resistance reading is high. v If the resistance is high and there is no internal cable to reattach. the plus lead and negative lead my not be labeled correctly. the SCSI bus is not faulted (shorted). Be sure to probe at the solder joint where the capacitor and board come together. Locate capacitor C1 and measure the resistance across it using the following procedure: a. the fault is on the adapter. Be sure to probe at the solder joint where the capacitor and board come together. proceed to the next step. there is no apparent cause for the PTC resistor diagnostic failure. If the resistance is still high. repeat this step with the leads reversed. the resistance reading is low. typically hundreds of Ohms. Connect the negative lead to the opposite side of the capacitor. 8 Diagnostic Information for Multiple Bus Systems . Note: Some multi-function meters label the leads specifically for voltage measurements. there is no apparent cause for a PTC failure. If the short circuit is not indicated with the leads reversed. If the resistance is less than 10 Ohms. the reading is a function of the Ohmmeter used. When using this type of meter to measure resistance. Reattach the internal cable to the adapter. This step determines if there is a short on the adapter. Note: Some internal cables have nonremovable terminators. Polarity is important in this measurement to prevent forward-biasing diodes which lead to a false low resistance reading. Troubleshoot the internal SCSI bus by disconnecting devices and terminators. Replace the adapter. b.

Some internal terminators use an electronic terminator. other than it is high. v A shorted device. The differential adapter can be identified by the 4-B or 4-L on the external bracket plate. When power is removed from the adapter. Therefore. this procedure is designed to find a short or low resistance fault as opposed to the presence of a terminator or a missing terminator. use these procedures to determine if a short-circuit condition exists on the SCSI Bus. terminator. v Intermittent PTC failures can be caused by incorrectly seated cable connectors. Check for bent pins on each connector and removable terminator. Note: The SCSI-2 Fast/Wide and Ultra PCI adapters use an onboard electronic terminator on the internal SCSI bus. A fault (short-circuit) causes an increase in PTC resistance and temperature. do not replace the adapter because of a tripped PTC resistor. the terminator is fixed to the internal cable and cannot be removed. Unless instructed to do so by these procedures. It is unlikely that the PTC can be tripped by a defective adapter. Service Hints 9 . Chapter 1. then retest. which also goes to a high impedance state when power is removed. Before replacing a SCSI-2 differential adapter. Reseat the connector and flex the cable in an attempt to duplicate the fault condition across C1. v On some systems. The increase in resistance causes the PTC to halt current flow. The PTC returns to a low resistive and low temperature state when the fault is removed from the SCSI bus or when the system is turned off. SCSI-2 Differential Adapter PTC Failure Isolation Procedure Use this procedure when SRN xxx-240 or xxx-800 has been indicated. These procedures determine if the PTC resistor is still tripped and then determine if there is a short somewhere on the SCSI bus.Internal SCSI-2 Single-Ended Bus Probable Tripped PTC Resistor Causes The following list provides some suggestions of things to check when the PTC is tripped: v A shorted terminator or cable. then the cable should be replaced. If all devices are removed from the cable and the resistance is still low. or device. as in the case of this procedure. the terminator goes to a high impedance state and the resistance measured cannot be verified. The PTC protects the SCSI bus from high currents due to shorts on the cable. Wait 5 minutes for the PTC resistor to fully cool.

The polarity of the test leads is not important. 4. Do not allow the probes to touch any other part of the component. continue. 2. The entire SCSI bus may appear to be intermittent.External SCSI-2 Differential Adapter Bus PTC Isolation Procedure Isolate the external SCSI bus PTC fault with the following procedure: Notes: 1. Check to ensure all devices are marked SCSI Differential and that the terminator on the end of the SCSI bus is also marked differential. 2. (refer to the illustration on page “External SCSI-2 Differential Adapter Bus PTC Isolation Procedure”) is cool and in a low resistance state. Ensure that system power and all externally attached device power is turned off. If not. allow the PTC resistor to cool and measure again. Single-ended devices do not work on a differential SCSI bus and may cause a PTC type error to be reported. If necessary. typically less than 1/2 Ohm. After ensuring the system is completely differential. 1. be sure to probe both sides of the PTC resistor where the solder joints and board come together. Disconnect the external cables from the adapter and remove the adapter from the system. The external bus is differential. Measuring across. you may have a single-ended SCSI device or terminator on the differential SCSI bus. 10 Diagnostic Information for Multiple Bus Systems . Only the probe tips are touching the solder joints. 3. Verify with a digital Ohmmeter that the internal PTC resistor. labeled Z1.

Be sure to probe at the solder joint where the capacitor and board come together. Locate capacitor C1 and measure the resistance across it using the following procedure: a. Connect the positive lead to the side of the capacitor marked ″Cathode D1″ on the board near C1. If the resistance measurement is not low enough to be suspected as a fault (lower than 10 Ohms). and RN3 are plugged into their sockets. Be sure to probe at the solder joint where the capacitor and board come together.5. The adapter is not faulty. check to see if RN1. If these sockets are empty. This step determines if there is a short on the adapter. you are working with a Multi-Initiators or High-Availability system. a resistive reading across C1 cannot be verified other than it measures a high resistance (not a short). b. v If there is no fault present. Continue to the next step. Service Hints 11 . then the resistance reading is 25 to 35 Ohms. RN2. continue to the next step. Chapter 1. Connect the negative lead to the side of the capacitor marked ″GND″. With these sockets empty. v If the resistance measured is higher than 35 Ohms.

v A shorted device. Because there are no cables attached. SCSI-2 Differential Adapter Probable Tripped PTC Causes The following list provides some suggestions of things to check when the PTC is tripped: v A shorted terminator or cable. Measure across C1 as previously described. there is no apparent cause for the PTC diagnostic failure. If the resistance is between 10 to 20 Ohms. typically below 10 Ohms. v Single-ended devices are attached to the differential SCSI bus. there is no apparent cause for a PTC resistor failure. 12 Diagnostic Information for Multiple Bus Systems . Reseat the connector and flex the cable in an attempt to duplicate the fault condition across C1.v If the resistance is high and there is no external cable to reattach. 6. c. b. the fault is on the adapter. proceed to the next step. v If the resistance reading is low. Check for bent pins on each connector and removable terminator. Measure across C1 to determine if the fault has been removed. If the resistance is less than 10 Ohms. Troubleshoot the external SCSI bus by disconnecting devices and terminators. Reattach the external cable to the adapter. a. v Plugging or unplugging a cable or terminator while the system is turned on (hot-plugging). v If the resistance measured was high and there is an external cable to reattach. v Intermittent PTC failures can be caused by incorrectly seated cable connectors. there is a fault. Replace the adapter. there is a possibility of a fault on the external SCSI bus.

Dual-Channel Ultra SCSI Adapter PTC Failure Isolation Procedure Use the following procedures if diagnostics testing indicates a potential positive temperature coefficient (PTC) resistor fault or the TERMPWR Shorted LED is lit. terminator. If the TERMPWR Shorted LED is lit. Service Hints 13 . A fault (short-circuit) causes an increase in PTC resistance and temperature. 3. 1. verify that the parts exchanged are in the correct channel (internal or external. If the failure is on the external cable. determine if the failure is on channel A or channel B. This procedure is used for SRNs 637-240 and 637-800 on the Dual-Channel Ultra SCSI Adapter. continue isolating the problem by going to “Step 0050-9” on page 53. If the failure persists. or device. Identify the adapter by its label of 4-R on the external bracket. replace the components of the failing channel in the following order (wait five minutes between steps): a. Wait 5 minutes for the PTC resistor to fully cool. Chapter 1. then retest. The PTC protects the SCSI bus from high currents due to shorts on the cable. If the errors are still occurring. or the TERMPWR Shorted LED is lit. If this same error persists. use this procedure to help isolate the source of the problem on the failing channel. replace the following: 1) Cable 2) Device 3) Backplane 4) Adapter c. The same PTC is used for both the internal and external buses. The increase in resistance causes the PTC to halt current flow. A or B). Then. replace the following: 1) Cable 2) Device 3) Attached subsystem 4) Adapter b. It is unlikely that the PTC can be tripped by a defective adapter. 2. The PTC returns to a low resistive and low temperature state when the fault is removed from the SCSI bus or when the system is turned off. If the failure is on the internal cable.

14 Diagnostic Information for Multiple Bus Systems .

The Fast Path MAP in Chapter 3 is provided to help you quickly resolve a problem. Note: Do not run the diagnostics until you are instructed to do so. Use the Fast Path MAP when you know or have been provided with a symptom. You may want to use the maintenance documentation for that device before running the diagnostics for the system. Note: Some of the devices that are supported by the diagnostic programs also have their own maintenance documentation. go to the Start of Call MAP 100 in the RS/6000 SP System Service Guide. 1. “MAP 0020: Problem Determination Procedure” on page 29 in this manual. Otherwise. Sometimes the maintenance package for the attached device allows the customer to continue operating the system while that device is being diagnosed. If you are servicing a clustered Eserver. go to the ″Quick Entry MAP for Systems with Service Focal Point″ in the system service guide. go to the Start of Call MAP 100 in the Clustered Eserver Installation and Service Guide. Symptom You do not have a problem or symptom. Start of Call MAP This MAP is the starting point for a service call. but you want to generate one. Action Go to Chapter 4. If this system has a Hardware Management Console (HMC) with Service Focal Point (SFP). 15 .Chapter 2. Go to Chapter 3. If you are servicing an SP system. go to step 2. “Fast Path MAP” on page 17 in this manual. You have been provided with a problem or symptom. Use the following table to help determine your next step. 2. You can use the diagnostic programs to check the adapter to which that device is attached.

16 Diagnostic Information for Multiple Bus Systems .

If you are servicing a clustered Eserver. run the Online Diagnostics in Service Mode unless you are directed otherwise. 3. 5.Chapter 3. go to the Start of Call MAP 100 in the SP System Service Guide. go to Chapter 4. “MAP 0410: Repair Checkout” on page 119 to verify the fix. If none of the MAPs in the service guide have you verify the fix. return to this book and use Chapter 22. Fast Path MAP In most cases. When possible. Fast Path MAP Table of Contents Problem Description Eight-Digit Error Codes Six-Digit Error Codes Containing No Dash (-) 888 Sequence in Operator Panel Display The System Stops or Hangs With a Value Displayed in the Operator Panel Display Diagnostic SRNs System Automatically Reboots System does not Reboot When Reset Button Pushed ASYNC Communication Problems SCSI Adapter Problems SCSI Bus Problems Tape Drive Problems CD-ROM Drive Problems SCSI Disk Drive Problems Diskette Drive Problems Token-Ring Problems Page No. If you replace a part. 2. the Standalone Diagnostics should be used. Notes: 1. 4. If you are directed to the system unit’s service guide. “MAP 0410: Repair Checkout” on page 119. use Chapter 22. go to the Start of Call MAP 100 in the Clustered Eserver Installation and Service Guide. “MAP 0020: Problem Determination Procedure” on page 29. If the actions listed for a specific symptom do not resolve the problem. use the MAPs in the service guide to complete the repair. If you are servicing an SP system. If the Online Diagnostics are not installed. these procedures direct you to run the Online Diagnostics. 18 18 19 19 19 19 20 20 20 20 21 21 22 23 23 17 .

Go to the ″Error Code to FRU Index″ in the service guide. if you run an AIX command that fixes the problem or if you change a hot-pluggable FRU). read the notes at the beginning of this section. 23 24 24 24 25 25 25 25 26 26 26 27 27 27 27 28 28 27 Fast Path Table Symptoms What You Should Do Eight-Digit Error Codes You have an eight-digit error code. Six-Digit Error Codes Containing No Dash (-) You have a six-digit error code (like an SRN) containing no dash (-) between the third and fourth digit. Note: If the repair for this code does not involve replacing a FRU (for instance. Go to the ″Error Code to FRU Index″ in the service guide.Problem Description Ethernet Problems Display Problems Keyboard or Mouse Printer and TTY Problems Other Adapter Problems System Messages Processor and Memory Problems Service Processor Problems Degraded Performance or Installed Memory Mismatch Missing Resources System Hangs or Loops When Running the Operating System or Diagnostics Exchanged FRUs Did Not Fix the Problem RAID Problems System Date and Time Problems SSA Problems Power Indicator Light is Not On System Power Problems You Cannot Find the Symptoms in This Table Page No. then run the Log Repair Action option on resource sysplanar0 from the Task Selection menu under Online Diagnostics to update the AIX error log. 18 Diagnostic Information for Multiple Bus Systems . read the notes on the first page. and do the listed action for the eight-digit error code. and do the listed action for the six-digit error code.

You have an SRN. then find the SRN in the SRN chapters and do the indicated action. Find the SRN in the SRN chapters and do the indicated action. Go to the Entry MAP in the service guide. 2.3.3 or later is installed. or device name displays on system units with a multiple-line operator panel display if AIX 4. Fast Path MAP 19 . System Automatically Reboots Chapter 3.Symptoms What You Should Do 888 Sequence in Operator Panel Display An 888 sequence in the operator panel display. Find the SRN in the SRN chapters and do the indicated action. The System Stops or Hangs With a Value Displayed in the Operator Panel Display The operator panel display alternates between two codes that begin with the letter E. The system stopped with a 4-digit code that begins with a 2 (two) displayed in the operator panel display. Record SRN 101-xxx (where xxx is the three digits of the code displayed). Go to the Entry MAP in the service guide. If a physical location code or an AIX location code is displayed. record it. Record the SRN and location code. The system stopped with a 3-digit code that begins with a digit or character other than A or F in the operator panel display. The system stopped with a 4-digit code that begins with 0 (zero) displayed in the operator panel display. Look up the SRN in the SRN chapters and do the listed action. The system stopped with a 3-digit code that begins with either A or F displayed in the operator panel display. 1. The physical location code. “MAP 0070: 888 Sequence in Operator Panel Display” on page 59. Diagnostic SRNs An SRN is displayed when running diagnostics. Record SRN 101-xxxx (where xxxx is the four digits of code displayed). Note: Customer-provided SRNs should be verified. The system stopped with a 4-digit code that Go to the Entry MAP in the service guide. This can be done by using the Display Previous Results Service Aid or by running the diagnostics again. Go to Chapter 9. Record SRN 101-xxx (where xxx is the last three digits of the code displayed). Look up the SRN in the SRN chapters and do the listed action. AIX location code. begins with a digit other than 0 (zero) or 2 (two) displayed in the operator panel display.

SCSI Adapter Problems You suspect a SCSI adapter problem. Problems are reported if the number of errors is above defined thresholds. System does not Reboot When Reset Button is Pushed System does not reboot (reset) when the reset button is pushed. Run the Advanced Async Diagnostics on the ports you are having problems with. Note: If you cannot load diagnostics (standalone or online) go to MAP 1540 in the service guide. If an SRN is displayed. “MAP 0050: SCSI Bus Problems” on page 51. Remote Async Node. The POST tests any SCSI Adapter before attempting to use it for booting. Use Chapter 8. Turn off the system unit power. lookup the SRN in the SRN chapters and do the action listed. If an SRN is displayed.Symptoms System automatically reboots. 1. and Cable Information for Multiple Bus Systems on these devices and perform any tests or checks listed. Run the Online SCSI Adapter Diagnostic in Problem Determination Mode. If an SRN displays. 6. look up the SRN in the SRN chapters and do the listed action. Select the All Resources option from the Resource Selection menu to test all resources. 3. and so on. Record SRN 111-999. then the adapter is most likely good. Find the SRN in the SRN chapters and do the indicated action. If you suspect a problem with the Async Concentrator. refer to the documentation in Adapters. If the system was able to boot using a SCSI adapter. SCSI adapters problems are also logged into the error log and are analyzed when the Online SCSI Diagnostics are run in Problem Determination Mode. 1. Turn on the system unit power and boot from a removable media. suspect a power supply or power source problem. What You Should Do 1. ASYNC Communication Problems You suspect an Async communication problem. 2. disk. 2. SCSI Bus Problems 20 Diagnostic Information for Multiple Bus Systems . 2. SCSI Adapter Diagnostics can only be run on a SCSI adapter that was not used for booting. 4. Devices. look up the SRN in the SRN chapters and do the listed action. or LAN in service mode. Run the diagnostics in Problem Determination Mode. 5. If an SRN is not displayed.

Run the Online Advanced Tape Diagnostics in Problem Determination Mode. 5. Refer to the tape drive documentation and clean the tape drive. look up the SRN in the SRN chapters and do the listed action. “MAP 0050: SCSI Bus Problems” on page 51. If an SRN is displayed. Use the SCSI Bus Service Aid to exercise and test the SCSI bus. 2. 2. 3. Use the Backup/Restore Media Service Aid to exercise and test the drive and media. Refer to the device section of Adapters. 1.Symptoms You suspect a SCSI bus problem. 6. Refer to the tape documentation and do any listed problem determination procedures. Note: Information on tape cleaning and tape-problem determination is normally either in the tape drive operator guide or the system operator guide. Tape Drive Problems You suspect a tape drive problem. “MAP 0050: SCSI Bus Problems” on page 51. 7. “MAP 0020: Problem Determination Procedure” on page 29 of this manual for problem determination procedures. 4. Use the SCSI Bus Service Aid to exercise and test the SCSI Bus. What You Should Do 1. Fast Path MAP 21 . Devices. Use Chapter 8. and Cable Information for Multiple Bus Systems for additional information and Chapter 4. CD-ROM Drive Problems Chapter 3. Use Chapter 8.

Note: Information on CD-ROM problem determination is usually in the CD-ROM drive operator guide or the system user’s guide. “MAP 0050: SCSI Bus Problems” on page 51. Run the Online Advanced CD-ROM Diagnostics in Problem Determination Mode. Use the SCSI Bus Service Aid to exercise and test the SCSI Bus. Refer to the device section of Adapters. 4. replace the CD-ROM drive. Refer to the CD-ROM documentation and do any listed problem determination procedures. look up the SRN in the SRN chapters and do the listed action. What You Should Do 1. Use Chapter 8. and Cable Information for Multiple Bus Systems for additional information and Chapter 4. Devices. “MAP 0020: Problem Determination Procedure” on page 29 of this manual for problem determination procedures. 5.Symptoms You suspect a CD-ROM drive problem. Before servicing a CD-ROM Drive ensure that it is not in use and that the power connector is correctly attached to the drive. If an SRN is displayed. SCSI Disk Drive Problems 22 Diagnostic Information for Multiple Bus Systems . If the load or unload operation does not function. 2. 3. 6.

look up the SRN in the SRN chapters and do the listed action. Token-Ring Problems You suspect a Token-Ring Adapter or network problem. Use the ping command to exercise and test the network. Use the SCSI Bus Service Aid to exercise and test the SCSI Bus. Ethernet Problems Chapter 3. Refer to the device section of Adapters. “MAP 0050: SCSI Bus Problems” on page 51. 5. Use the Diskette Media Service Aid to test the diskette media. 3. and Cable Information for Multiple Bus Systems for additional information and Chapter 4. “MAP 0020: Problem Determination Procedure” on page 29 for additional information and problem determination procedures. the Standalone Diagnostics must be used. 2. 4. If an SRN is displayed. look up the SRN in the SRN chapters and do the listed action. SRN chapters and do the listed action. Use the Backup/Restore Media Service Aid to exercise and test the drive and media. 2. 3. “MAP 0020: Problem Determination Procedure” on page 29 of this manual for problem determination procedures. Diskette Drive Problems You suspect a diskette drive problem. Problems are reported if the number of errors is 2. Run the Online Advanced Disk Diagnostics in Problem Determination Mode. What You Should Do 1. Refer to Chapter 4.Symptoms You suspect a disk drive problem. error log analysis is run if these drives are selected. To run the disk diagnostic tests on disks that are part of the root volume group. If an SRN is displayed. 6. If an SRN is displayed. Run the diskette drive diagnostics. Disk problems are logged in the error log and are analyzed when the Online Disk Diagnostics are run in Problem Determination Mode. Devices. Run Standalone Disk Diagnostics. However. look up the SRN in the SRN chapters and do the listed action. then the diagnostics can only be run on those drives that are not part of the root volume group. 1. 1. Fast Path MAP 23 . Use the Certify Disk Service Aid to verify that the disk can be read. 3. If the diagnostics are booted from a disk. Use Chapter 8. If an SRN is displayed. look up the SRN in the above defined thresholds. Run the Online Advanced Token-Ring Diagnostics in Problem Determination Mode.

1. What You Should Do 1. If an SRN is displayed. 2. 3. Note: If the problem is with the keyboard it could be caused by the mouse device. Display Problems You suspect a display problem.Symptoms You suspect an Ethernet Adapter or network problem. “MAP 0020: Problem Determination Procedure” on page 29 for additional information and problem determination procedures. If you are unable to run diagnostics because the system does not respond to the keyboard. If an SRN is displayed. replace the keyboard or system planar. look up the SRN in the SRN chapters and do the listed action. unplug the mouse and then recheck the keyboard. look up the SRN in the SRN chapters and do the listed action. 3. 2. Refer to Chapter 4. Run the device diagnostics. To check. If an SRN is displayed. Go to the Problem Determination Procedures for the display. look up the SRN in the SRN chapters and do the listed action. “MAP 0020: Problem Determination Procedure” on page 29 for additional information and problem determination procedures. Printer and TTY Problems 24 Diagnostic Information for Multiple Bus Systems . If the keyboard works. Refer to Chapter 4. Use the ping command to exercise and test the network. replace the mouse. Run diagnostics on the adapter that the display is attached. Run the Online Advanced Ethernet Diagnostics in Problem Determination Mode. Keyboard or Mouse You suspect a keyboard or mouse problem.

Run the Online Advanced Diagnostics in Problem Determination on the adapter you suspect. Port the printer or terminal is connected to. Use the ″Testing the Line Printer″ procedure in Chapter 25. look up the SRN in the SRN chapters and do the listed action. “MAP 0020: Problem Determination Procedure” on page 29 for additional information and problem determination procedures. Check the port that the device is attached to by running diagnostics on the port. 2. Device cable b. Fast Path MAP 25 . look up the SRN in the SRN chapters and do the listed action. Look for another symptom to use. 1. Only problems that prevent the system from booting are reported during POST. Run either the sysplanar0 or the Memoryoption under the Advanced Diagnostics in Problem Determination Mode. What You Should Do 1. Memory tests are only done during POST. 2. Turn on the system unit power and load the Online Diagnostics in Service Mode. Processor and Memory Problems You suspect a memory problem. System Crashes are logged in the AIX Error Log. 2. Look up the SRN in the SRN chapters and do the listed action. System Messages A System Message is displayed. attempt to correct it. 2. 3. replace the following in the order listed: a. The sysplanar0 option under the Advanced Diagnostic Selection menu is run in Problem Determination Mode to analyze the error. If the message describes the cause of the problem. If a problem exists. If an SRN is displayed. Refer to Chapter 4. Go to problem determination procedures for the printer or terminal. Other Adapter Problems You suspect a problem on another adapter that is not listed above. If an SRN is displayed. If an SRN is displayed. Power off the system. All other problems are logged and analyzed when the sysplanar0 option under the Advanced Diagnostics Selection menu is run. 5. record the SRN and location code. Service Processor Problems Chapter 3. 3.Symptoms You suspect a TTY terminal or printer problem. 4. 1. “General Diagnostic Information” on page 133 to test the connection to the printer. 1.

Missing Resources Missing Resources Note: ISA resources must be configured before they appear in the configuration. v Service Processor menus do not display or display incorrectly on a TTY terminal. v AIX 4. If the problem is not corrected. go to MAP 0020. The Display Vital Product Data (VPD) option shows the amount of memory that is installed.2. v Cannot input to the Service Processor menus using a TTY keyboard.1 and Higher From the Task Selection Menu select the ’Display Resource Attribute’. If the problem remains after replacing the Service Processor. To verify that the system detected the full complement of installed memory use one of the following methods based on the level of AIX being used. v All Other AIX Versions Use the Display or Change Configuration Service Aid to verify that all installed memory is being detected. Verify the amount of memory listed matches the amount actually installed. If an installed resource does not appear. replace the system planar. lookup the SRN and do the indicated action. replace the card or board that contains the missing memory. What You Should Do Remove the Service Processor and then run advanced diagnostics on the built-in serial ports. If no SRN is reported. If an installed memory module or card does not appear or appears as the wrong size. System Hangs or Loops When Running the OS or Diagnostics 26 Diagnostic Information for Multiple Bus Systems . From the Resource Selection menu select one of the listed memory resources. replace it. The ISA Adapter Configuration Service Aid is used to configure ISA adapter for Standalone Diagnostics. check that it is installed correctly.Symptoms v Modem does not dial out or answer calls using Service Processor functions. Degraded Performance or Installed Memory Mismatch Degraded Performance or Installed Memory Mismatch Degraded Performance can be caused by memory problems that cause a reduction in the size of available memory. replace the Service Processor. If an SRN is reported. If you do not find a problem. SMIT can be used to configure during Online Diagnostics. Use the ’Display or Change Configuration or Vital Product Data (VPD) Service Aid’ to verify that the resource was configured.

Select the All Resources option from the Resource Selection menu to test all resources. To check the system: 1. A potential problem with a RAID adapter exists. If an SRN is reported. 2. record the SRN and location code. Go to Chapter 4. Run diagnostics on the RAID adapter. 4. Look up the SRN in the SRN chapters and do the listed action. Run the sysplanar0 option under the Advanced Diagnostics in Problem Determination mode. Turn on the system unit power and load the Online Diagnostics in Service Mode. 2. Select the All Resources option from the Resource Selection menu to test all resources. Fast Path MAP 27 . Refer to the RAID Adapters User’s Guide and Maintenance Information or the service guide for the RAID. Exchanged FRUs Did Not Fix the Problem A FRU or FRUs you exchanged did not fix the problem. 3. Go to Chapter 6. Power off the system. Look up the SRN in the SRN chapters and do the listed action. v The system does not retain the time of day record the SRN and location code after the system has been booted. “MAP 0030: Additional Problem Determination” on page 45. information and do the indicated action for Note: It is normal for the system time of day the SRN. If this does not fix the problem. “MAP 0020: Problem Determination Procedure” on page 29. The system hangs in different applications. replace the system planar. What You Should Do Suspect the application. 4.Symptoms The system hangs in the same application. 5. 1. The system hangs when running diagnostics. 5. If an SRN is displayed at anytime. RAID Problems You suspect a problem with a RAID. If an SRN is displayed at anytime. record the SRN and location code. SSA Problems Chapter 3. Turn on system unit power and load the Online Diagnostics in Service Mode. 2. You Cannot Find the Symptom in This Table All other problems. 3. Power off the system. Replace the resource that is being tested. Replace the TOD (NVRAM) battery. System Date and Time Problems v The system does not retain the calendar date after the system has been booted. to gain or lose a few seconds each month. 1.

Run diagnostics on the SSA adapter. Go to the Entry MAP in the service guide. refer to the SSA Adapters User’s Guide and Maintenance Information or the service guide for your disk subsystem. System Power Problem The system does not power on. Go to the Entry MAP in the service guide. What You Should Do A potential problem with an SSA adapter exists. If the system has internal SSA drives.Symptoms You suspect an SSA problem. Power Indicator Light is Not On A drawer power indicator is not on. Refer to the Entry MAP section of the Maintenance Analysis Procedures (MAPs) in the system service manual. The system powers on when it should not. go to the SSA MAP in either the system unit’s service guide or user’s guide. 28 Diagnostic Information for Multiple Bus Systems . If the system has external SSA drives.

perform its shutdown procedure. MAP 0020: Problem Determination Procedure Purpose of This MAP Use this MAP to get a service request number (SRN) if the customer or a previous MAP provided none. answer it yes. NO YES If the operating system is running. Fix the problem. “MAP 0410: Repair Checkout” on page 119.Chapter 4. Go to “Step 0020-4” on page 30. refer to Chapter 26. Get help if needed. refer to the MAP 1520 in the system’s service guide. “Using Standalone and Online Diagnostics” on page 145 for pertinent information before proceeding further. Did you find an obvious problem? NO YES Go to “Step 0020-2”. 29 . then go to Chapter 22. If you are unable to power the system on. Note: If another system connects to this system. Step 0020-1 Visually check the system for obvious problems such as unplugged power cables or external devices that are powered off. Go to “Step 0020-3” on page 30. Step 0020-2 Are the Online Diagnostics installed? Note: If you are uncertain how to answer the above question.

Turn on the system unit power. Go to “Step 0020-5” on page 31. Go to “Step 0020-5” on page 31. If the system supports Slow boot (See “About Slow Boot” on page 2). 4. If an SRN displays. If the system unit is already running in the service mode and you want to run online diagnostics. Log in with root authority or use CE login. 8. 6. perform its shut down procedure (get help if needed). Follow any instructions displayed. Turn off the system unit power and wait 45 seconds before proceeding.Step 0020-3 Note: When possible. 1. Load the Online Diagnostics in Service Mode (if needed. Enter the diag command. Wait until the Diagnostic Operating Instructions display or the system appears to have stopped. Go to “Step 0020-5” on page 31. If there are no instructions display or missing resources. 9. proceed to the question in this MAP. do a slow boot on the system. Refer to the system unit service guide if needed. If the system does not support slow boot. Turn on the system unit power. Enter the diag -a command to check the system for missing resources. 30 Diagnostic Information for Multiple Bus Systems . To run Online Diagnostics in Service Mode. 2. proceed to the next substep to run concurrent diagnostics. If necessary. otherwise do substeps 1 through 4. ask the customer for the password. If the operating system is running. 7. Run Online Diagnostics in Concurrent Mode when the customer does not let you power-off the system unit. 5. Wait until the Diagnostic Operating Instructions display or the system appears to have stopped. Are the Diagnostic Operating Instructions Displayed? NO YES Go to “Step 0020-16” on page 39. do a normal boot 3. 2. 4. Online diagnostics perform additional functions. refer to the service guide). record it and go to “Step 0020-15” on page 38. compared to Standalone Diagnostics. Turn off the system unit power and wait 45 seconds before proceeding. go to substep 5. Are the Diagnostic Operating Instructions Displayed? NO YES Go to “Step 0020-16” on page 39. 3. substep 5. run Online Diagnostics in Service Mode. Load the Standalone Diagnostics in Service Mode. Step 0020-4 1.

The system halted while testing a resource. To continue with diagnostics. where xxx is the first three digits of the menu number displayed in the upper-right corner of the diagnostic menu. Is the FUNCTION SELECTION menu displayed (screen number 801002)? NO YES Go to “Step 0020-13” on page 36. go to “Step 0020-6”. System Response The RESOURCE SELECTION menu or the ADVANCED DIAGNOSTIC SELECTION menu is displayed (screen number 801006). do so now. “FRU Cross-References” on page 617 to obtain the failing function code (FFC) for the device. Step 0020-6 Press the Enter key. If the DIAGNOSTIC MODE SELECTION menu (screen number 801003) displays. Follow the instructions in the Action column. Note: This table spans several pages. Go to “Step 0020-7”. 2. 3. Chapter 4. blurred or distorted)? NO YES For display problems. You cannot proceed until this is done. select the PROBLEM DETERMINATION option. go to “Step 0020-12” on page 36. If no menu number is displayed. Select the ADVANCED DIAGNOSTICS ROUTINES option. Use the FFC code of the device for xxx. use Chapter 37. Action Go to “Step 0020-11” on page 34. Go to “Step 0020-15” on page 38. MAP 0020: Problem Determination Procedure 31 . Step 0020-7 1. Record SRN 110-xxx. Note: If the terminal type is not defined. Find your system response in the following table.Step 0020-5 Are the Diagnostic Operating Instructions Displayed (screen number 801001) with no obvious problem (for example.

System Response The MISSING RESOURCE menu is displayed. go to “Step 0020-11” on page 34. Perform the listed action. and then return to substep 1 of “Step 0020-7” on page 31. and go to “Step 0020-15” on page 38. boot process is displayed continuously on the system unit’s console. go to the system’s service guide and find the error in the ″Error Code to FRU Index″. ISA adapters cannot be detected by the system. The message Processing supplemental diagnostic diskette media is displayed continuously on the system unit’s console. 32 Diagnostic Information for Multiple Bus Systems . The ISA Adapter Configuration Service Aid in Standalone Diagnostics allows the identification and configuration of ISA adapters. If an 8-digit error code is displayed. If the ADVANCED DIAGNOSTIC SELECTION menu is displayed. If an SRN is displayed. Call your service support structure. Action Follow the displayed instructions until either the ADVANCED DIAGNOSTIC SELECTION menu or an SRN is displayed. Note: Run any supplemental media that may have been supplied with the adapter or device. record it. select it first. If the SCSI Enclosure Services device appears on the Missing Resource list along with the other resources. 2. The message The system will now continue the Go to “Step 0020-4” on page 30. Notes: 1.

go to either the system’s or subsystem’s service guide and find the error in the ″Error Code to FRU Index″. and the location code for the FRUs. If an SRN is displayed. or an eight-digit error code is displayed. The system unit emits a continuous sound from the beeper. If the No Trouble Found screen is displayed. Perform the listed action. record it. An 888 message is displayed in the operator panel display. Perform the listed action. If another resource is tested. If an SRN is displayed. and if a recent error has been logged in the error log. Record SRN 101-xxx (where xxx is the rightmost three digits of the displayed code). Record SRN 111-947 and then go to “Step 0020-15” on page 38. The system stopped with a 3-digit or 4-digit code displayed in the operator panel display. If an eight-digit error code is displayed. Notes: 1. “MAP 0070: 888 Sequence in Operator Panel Display” on page 59. A system unit with a beeper did not beep while booting. go to “Step 0020-15” on page 38. Go to “Step 0020-15” on page 38. record it and go to the system unit’s service guide and find the error in the ″Error Code to FRU Index″. Note: If the Problem Determination Option was selected from the DIAGNOSTIC MODE SELECTION menu. Resources attached to serial and parallel ports may not appear in the resource list. If the ADVANCED DIAGNOSTIC SELECTION menu is displayed. 2. MAP 0020: Problem Determination Procedure 33 . The ISA Adapter Configuration Service Aid in Standalone Diagnostics allows the identification and configuration of ISA adapters. and go to “Step 0020-15” on page 38. Step 0020-8 On the DIAGNOSTIC SELECTION or ADVANCED DIAGNOSTIC SELECTION menu. press Enter. ISA adapters cannot be detected by the system. Record SRN 111-947 and then go to “Step 0020-15” on page 38. Chapter 4. An SRN. look through the list of resources to make sure that all adapters and SCSI devices are listed including any new resources. Record the error code. If a six-digit error code containing no dash (-) or an 8-digit error code is displayed. Go to “Step 0020-13” on page 36. or six-digit error code containing no dash (-).System Response The diagnostics begin testing a resource. Action Follow the displayed instructions. Note: The 888 may or may not be flashing. the FRU names. The system did not respond to selecting the Advanced Diagnostics option. the diagnostics automatically begin testing the resource. repeat this step. go to “Step 0020-11” on page 34. Go to Chapter 9.

If it does not work in alternate location. The replacement device or adapter may be defective. 34 Diagnostic Information for Multiple Bus Systems . Step 0020-11 Select and run the diagnostic test problem determination or system verification on one of the following: v The resources with which the customer is having problems. try installing it in an alternate location if one is available. Go to “Step 0020-11”. suspect a bad replacement adapter or device. if it works in that location. try installing it in an alternate location if one is available. Step 0020-9 Is the new device or adapter an exact replacement for a previous one installed at same location? NO YES Go to “Step 0020-10”. v All resources. resources assigned to other partitions will not be displayed on the resource list. suspect a bad replacement adapter or device. then suspect that the location where it failed to appear has a defective slot. then run diagnostics on its parent (the adapter or controller to which the resource is attached). contact your service support structure. If possible.3. schedule time to replace the hardware that supports that slot. If running diagnostics in a partition within a partitioned system. schedule time to replace the hardware that supports that slot. The replacement device or adapter may be defective. If you are still unable to detect the device or adapter. then suspect that the location where it failed to appear has a defective slot. Did you find the all the adapters or devices on the list? NO YES Go to “Step 0020-9”. if it works in that location. contact your service support structure. If possible. v The resources you suspect are causing a problem. If the resource is not shown on the DIAGNOSTIC SELECTION menu. Step 0020-10 Is the operating system software to support this new adapter or device installed? NO YES Load the operating system software. If it does not work in alternate location. If you are still unable to detect the device or adapter. Find the response in the following table or follow the directions on the test results screen.

Note: If you have not run the sysplanar test. and (-). where xxx is the first three digits of the menu number displayed in the upper-right corner of the diagnostic menu screen. Go to “Step 0020-14” on page 37. v If the response is the same. Note: If the missing device is an ISA adapter or a device connected to an ISA adapter. The IBM ARTIC960 Quad T1/E1 Adapter Install a PMC board if not already installed. the device is not listed until you configure it. “Start of Call MAP” on page 15. Record SRN 110-101. “FRU Cross-References” on page 617 to obtain the failing function code (FFC) for the device. If no menu number is displayed.″ Perform the listed action. The system halted while testing a resource. Ensure that the diagnostic support for the device was installed. use Chapter 37. diagnostics displays a message indicating that the interface board (PMC) is either not installed or is When running Online Diagnostics on any of the IBM ARTIC960 family of adapters and the malfunctioning. The TESTING COMPLETE menu and the No trouble was found message are displayed. then run diagnostics. Go back to the Chapter 2. and you have tested all of the resources.Diagnostic Response Action An SRN. an installed device does not appear in the test list. Chapter 4. Use the FFC code of the device for xxx. Press Enter and continue testing other resources. If a six-digit error code containing no dash (-) or an 8-digit error code is displayed. The symptom was not found in the table. or an eight-digit error code is displayed on the the location code for the FRUs. Note: Supplemental diskettes may be required if service aids are run from Standalone Diagnostics. six-digit error code containing no dash Record the error code. “MAP 0410: Repair Checkout” on page 119. replace the PMC and then go to Chapter 22. If an SRN is screen. go to “Step 0020-15” on page 38. When running the Online Diagnostics. do the following: v Reseat the PMC board. Record SRN 110-xxx. The TESTING COMPLETE menu and the No trouble was found message are displayed. the FRU names. Go to “Step 0020-15” on page 38. but it is installed. do so before going to “Step 0020-14” on page 37. The Display Configuration service aid can be used to determine whether diagnostic support is installed for the device. go to either the system’s or subsystem’s service guide and find the error in the ″Error Code to FRU Index. and you have not tested all of the resources. message indicates that the PMC (daughter board) is not installed. Go to “Step 0020-15” on page 38. displayed. MAP 0020: Problem Determination Procedure 35 .

Step 0020-12
The following step analyzes a console display problem. Find your type of console display in the following table. Follow the instructions given in the Action column.
Type of Console Display TTY-type terminal Action Be sure the TTY terminal attributes are set correctly. See ″Running the Diagnostic Programs from a TTY Terminal″ in Chapter 26, “Using Standalone and Online Diagnostics” on page 145. If you did not find a problem with the attributes, go to the documentation for this type of TTY terminal, and continue problem determination. If you do not find the problem, record SRN 111-259; then go the “Step 0020-15” on page 38. Graphics display Go to the documentation for this type of graphics display, and continue problem determination. If you do not find the problem, record SRN 111-82c; then go to “Step 0020-15” on page 38. Go to MAP 1540 of the HMC Maintenance Guide. If HMC tests find no problem, there may be a problem with the communication between the HMC and the managed system. If the HMC communicates with the managed system through a network interface, verify whether the network interface is functional. If the HMC communicates with the managed system through the HMC interface, check the cable between the HMC and the managed system, if it is not causing the problem, suspect a configuration problem of the HMC communications setup.″

HMC (Hardware Management Console)

Step 0020-13
There is a problem with the keyboard. Find the type of keyboard you are using in the following table. Follow the instructions given in the Action column.
Keyboard Type Type 101 keyboard (U.S.). Identify by the size of the Enter key. The Enter key is in only one horizontal row of keys. Type 102 keyboard (W.T.). Identify by the size of the Enter key. The Enter key extends into two horizontal rows. Kanji-type keyboard. (Identify by the Japanese characters.) TTY terminal keyboard Action Record SRN 111-736, then go to “Step 0020-15” on page 38. Record SRN 111-922; then go to “Step 0020-15” on page 38. Record SRN 111-923; then go to “Step 0020-15” on page 38. Go to the documentation for this type of TTY terminal and continue problem determination.

36

Diagnostic Information for Multiple Bus Systems

Keyboard Type HMC (Hardware Management Console)

Action Go to MAP 1540 of the HMC Maintenance Guide. If HMC tests find no problem, there may be a problem with the communication between the HMC and the managed system. If the HMC communicates with the managed system through a network interface, verify whether the network interface is functional. If the HMC communicates with the managed system through the HMC interface, check the cable between the HMC and the managed system, if it is not causing the problem, suspect a configuration problem of the HMC communications setup.″

Step 0020-14
The diagnostics did not detect a problem. If the problem is related to either the system unit or the I/O expansion box, refer to the service guide for that unit. If the problem is related to an external resource, use the problem determination procedures, if available, for that resource. If a problem occurs when running Online Diagnostics but not when running the Standalone Diagnostics, suspect a software problem. Check for the presence of supplemental diagnostic material, such as diskettes or documentation. This is possibly a problem with software or intermittent hardware. If you think that you have an intermittent hardware problem, go to Chapter 7, “MAP 0040: Intermittent Problem Isolation” on page 47.

Chapter 4. MAP 0020: Problem Determination Procedure

37

Step 0020-15
Take the following actions: 1. Handle multiple SRNs and error codes in the following order: a. 8-Digit Error Codes. Multiple 8-digit error codes listings are not always in the correct order. See the ″Error Code to FRU Index″ in the system service guide to identify those error codes that require special handling. b. SRNs in the range of A01-xxx to A1D-xxx. c. SRNs with a source code other than F or G. d. SRNs with a source code of F. Run Online diagnostics in Advanced and Problem Determination Mode to obtain maximum isolation. e. SRNs with a source code of G. Note: The priority for multiple SRNs with a source of G is determined by the time stamp of the failure. Follow the action for the SRN with the earliest time stamp first. f. Device SRNs and error codes (5-digit SRNs). If a group has multiple SRNs, it does not matter which SRN is handled first. 2. Find the SRN in Chapter 29, “Using the SRN List” on page 243. Note: If the SRN is not listed, look for it in the following: v Any supplemental service manual for the device v The diagnostic problem report screen for additional information v The ″Service Hints″ service aid in Chapter 26, “Using Standalone and Online Diagnostics” on page 145 v The “CEREADME File” on page 134 (by using the Service Hints service aid) 3. Perform the action listed. 4. If you replace a part, go to Chapter 22, “MAP 0410: Repair Checkout” on page 119.

38

Diagnostic Information for Multiple Bus Systems

Step 0020-16
Refer to “Configuration Program Indicators” on page 217 for definitions of configuration program indicators. They are normally 0xxx on CHRP systems and Yxx on RSPC systems (where Y is a digit or character other than A or F). Is a Configuration Program Indicator Displayed? NO YES Go to the Entry MAP in the service guide. Record SRN 101-xxx (where xxx is the rightmost three digits or characters of the Configuration Program Indicator). Go to “Step 0020-17”.

Step 0020-17
The physical location code, AIX location code, or device name displays on system units with a multiple-line operator panel display if AIX 4.3.3 or later is installed. Is a physical location code or an AIX location code displayed on the operator panel display? NO YES Go to “Step 0020-15” on page 38. Record the location code, then go to “Step 0020-15” on page 38.

Chapter 4. MAP 0020: Problem Determination Procedure

39

40

Diagnostic Information for Multiple Bus Systems

Chapter 5. MAP 0025: SCSI RAID Problem Determination Procedure
Purpose of This MAP
To determine if there is a problem with the SCSI RAID subsystem.

Step 0025-1
Determining the Status of the SCSI RAID Subsystem. Ask the customer to determine the status of the RAID subsystem. Below is an example of this procedure: 1. Login as root (if not already root). 2. Type smit pdam. 3. Select List PCI SCSI RAID Arrays. 4. Select the adapter associated with the RAID upon which you want to do problem determination. 5. Press Enter. Is the status of the RAID Array listed as optimal? NO YES Go to “Step 0025-2”. Fix the problem; then go to “Step 0025-12” on page 44.

Step 0025-2
Is the status of the RAID Array listed as Degraded? NO YES Go to “Step 0025-3”. Make a note of the failing drive Channel and ID, and go to Chapter 18, “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103 to replace the drive on that channel.

Step 0025-3
Is the status of the RAID Array listed as Reconstructing? NO YES Go to “Step 0025-5” on page 42. Go to “Step 0025-4”.

Step 0025-4
Is the RAID Array reconstructing but no percentage is shown? NO YES Wait for the RAID Array to complete reconstructing, then go to “Step 0025-12” on page 44. Go to “Step 0025-5” on page 42.

41

Step 0025-5
Is the status of the RAID Array listed as Defined? NO YES Go to “Step 0025-11” on page 43. Go to “Step 0025-6”.

Step 0025-6
Ask the customer to determine the status of the RAID adapter. For example, type: lsdev -C -l scraidX where X is the number of the corresponding RAID adapter. Is the result of this command that adapter is listed in Defined state? NO YES Go to “Step 0025-11” on page 43. Go to “Step 0025-7”.

Step 0025-7
Ask the customer to remove the adapter and reconfigure it. For example, to remove the adapter type: rmdev -l scraidX and to reconfigure the adapter, type: cfgmgr -l scraidX where X is the number of the corresponding RAID adapter. Did the adapter become Available? NO YES Go to “Step 0025-10” on page 43. Go to “Step 0025-8”.

Step 0025-8
Ask the customer to configure the defined disk array. An example of this procedure: 1. Type smitty pdam 2. Select Configure a Defined PCI SCSI Disk Array. 3. Select the defined array that you want to make available. 4. A message displays indicating the outcome of the procedure. Make a note of the message.

5. Press PF10 to exit. Did the procedure fail? NO YES Go to “Step 0025-9” on page 43. Go to “Step 0025-10” on page 43.

42

Diagnostic Information for Multiple Bus Systems

Step 0025-9
Was the array listed in optimal state? NO YES Using the new state of the array, go to “Step 0025-2” on page 41. Go to “Step 0025-10”

Step 0025-10
Run Diagnostics on the RAID system. 1. Type diag. 2. Select Advanced Diagnostic Routines. 3. Select System Verification. 4. If any menus other than the Advanced Diagnostics Selection menu are displayed, follow their instructions. 5. When the Advanced Diagnostic Selection menu displays, select scraidX (where X is the ID of the SCSI RAID adapter). Press F7. (an alternative method of running steps 2-6 from AIX command line is to type diag -v -d scraidX where X is the ID of the SCSI RAID adapter). Were any SRNs reported? NO YES Contact you service support structure. Go to Chapter 18, “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103.

Step 0025-11
If the RAID array is not online, it is most likely due to multiple drive failures. If you believe that a failed drive is actually good, ask the customer to revive a failing drive. Below is an example of this procedure: 1. Login as root ( if not already root). 2. Type smit pdam. 3. Select Revive a failed Drive in a PCI SCSI Disk Array. If the drive can be recovered, it will be put into Reconstructing or Degraded mode, repeat “Step 0025-1” on page 41 using the indicated mode. If the drive cannot be recovered, go to Chapter 18, “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103 to replace the drive.

Chapter 5. MAP 0025: SCSI RAID Problem Determination Procedure

43

Step 0025-12
1. Select Advanced Diagnostic Routines. 2. Select Problem Determination. 3. If any menus other than the Advanced Diagnostics Selection menu are displayed, follow their instructions. 4. When the Advanced Diagnostic Selection menu displays, select scraidX (where X is the ID of the SCSI RAID adapter). Press F7. (an alternative method of running substeps 2-6 from the AIX command line is to type diag -d scraidX where X is the ID of the SCSI RAID adapter). If the resource is in use and you do not wish to take it offline, select Testing Should Stop. This will show information about the RAID subsystem including the address of the failing disk drives used by that SCSI RAID channel and ID. Note: Problem determination will not be performed unless the device is NOT in use. Were any SRNs reported? NO YES Go to “Step 0025-13”. Go to Chapter 18, “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103.

Step 0025-13
1. Type diag 2. Select Task Selection 3. Select Analyze Adapter Internal Log Are there any Hard or Media errors reported on specific drives? NO YES Go to “Step 0025-14”. Go to Chapter 18, “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103 to replace drives with media errors one at a time. CAUTION: Only for the 4-Channel PCI SCSI RAID adapter, drives will be decoded as channels 0-3 rather than channels 1-4. So if an error is indicated on channel 1 ID 4, the error is really on channel 2 ID 4.

Step 0025-14
Are there other RAID problems? NO YES No RAID problems were found. Exit this MAP. Contact your service support structure.

44

Diagnostic Information for Multiple Bus Systems

Chapter 6. MAP 0030: Additional Problem Determination
Purpose of This MAP
This MAP is used for problems that still occur after all FRUs indicated by the SRN or error code have been exchanged.

Step 0030-1
Some external devices (including rack drawers that contain devices) have their own problem-determination procedures. If the problem is related to an external device that has its own problem-determination procedure, run those procedures if not already run. If they do not correct the problem, continue with this MAP.

Step 0030-2
The problem may have been caused by a resource that has not been tested. System Checkout tests all resources. If the Online Diagnostics are installed and you are able to load them, then All Resources under the Diagnostic Selection menu should be run. If you get a different SRN, then look up the SRN in the SRN chapters and do the listed action. If you are unable to run All Resources under the Diagnostic Selection menu or you do not get another SRN when running it, continue with this MAP.

Step 0030-3
If the problem is related to a SCSI device, SCSI bus, or SCSI controller, go to Chapter 8, “MAP 0050: SCSI Bus Problems” on page 51. If you are unable to isolate the problem with MAP 0050, continue with “Step 0030-4” on page 46.

45

Step 0030-4
1. Find the resource(s) that are identified by the SRN or error code in the following table. 2. Perform the first action listed for the resource. 3. If you exchange a FRU or change a switch setting, test the resource again. 4. If the action does not correct the problem, perform the next action until all actions have been tried. If an action says to exchange a FRU that you have already exchanged, go to the next action. If an action corrects the problem, go to Chapter 22, “MAP 0410: Repair Checkout” on page 119. 5. If you perform all of the actions and do not correct the problem, check the Service Hints service aid for information. If the service aid does not help, call your service support structure.
Failing Resource SCSI Device Pluggable SCSI or IDE Controller Keyboard, tablet, mouse, dials, LPFK, diskette drive Pluggable adapters, CPU cards, and controllers Repair Action Exchange the SCSI Controller. Replace the power supply. Exchange the planar into which the adapter is plugged. Check the cable attaching the device to its adapter. If you do not find a problem, exchange the device’s adapter. Determine whether the adapter contains any attached FRUs such as fuses, DRAMs, and crossover cables. 1. Check or exchange any attached FRU on the resource. 2. If the adapter is plugged into a riser card, check or exchange the riser card. 3. Exchange the planar into which the adapter is plugged. Note: To check for other FRUs, find the resource in Chapter 37, “FRU Cross-References” on page 617; then go to the FFC listed. System and I/O planars Built-In serial ports A device attached to the system by a cable and an adapter. IDE Device Contact your service support structure. Replace the Service Processor if present. 1. Replace the adapter for the device. 2. Replace the cable to the device. Replace the cable between the IDE controller and the device. If the IDE controller is packaged on a planar, replace that planar, otherwise replace the adapter containing the IDE controller.

46

Diagnostic Information for Multiple Bus Systems

Chapter 7. MAP 0040: Intermittent Problem Isolation
Purpose of This MAP
This MAP provides a structured way of analyzing intermittent problems. It consists of two tables: Hardware Symptoms and Software Symptoms. Because software or hardware can cause intermittent problems, consider all symptoms relevant to your problem.

How to Use This MAP
This MAP contains information about causes of intermittent symptoms. In the following tables, find your symptoms, and read the list of things to check. When you exchange a FRU, go to Chapter 22, “MAP 0410: Repair Checkout” on page 119 to check out the system.

Hardware Symptoms
Note: This table spans several pages.
Symptom of Hardware Problem Things to Check For

Any hardware log entry in the Use the Hardware Error Report service aid to view the error log error log. and check for: v Multiple errors on devices attached to the same SCSI bus. v Multiple errors on devices attached to the same async adapter. v Multiple errors on internally installed devices only. Contact your service support structure for assistance with error report interpretation. Hardware-caused system crashes v The connections on the CPU planar or CPU card v Memory modules for correct connections v Connections to the system planar. v Cooling fans operational v The environment for a too-high or too-low operating temperature. v Vibration: proximity to heavy equipment. v If available, run the system memory test from the System Management Services menu to check for intermittent memory problems.

47

Symptom of Hardware Problem System unit powers off a few seconds after powering On.

Things to Check For v Fan speed. Some fans contain a speed-sensing circuit. If one of these fans is slow, the power supply powers the system unit off. v Correct voltage at the outlet into which the system unit is plugged. v Loose power cables and fan connectors, both internal and external.

System unit powers off after running for more than a few seconds.

v Excessive temperature in the power supply area. v Loose cable connectors on the power distribution cables. v Fans turning at full speed after the system power has been on for more than a few seconds.

Only internally installed devices are failing.

Check the following items that are common to more than one device: v Ground connections on all of the disk drives and other types of drives installed. v Loose connections on the power cables to the planars, drives, fans, and battery. v System unit cooling. Is the input air temperature within limits? Are all the fans running at full speed? Are any of the vent areas blocked? v Signal cables to the diskette drives, and the power supply. v SCSI device signal cables for loose connectors and terminators. v Loose SCSI device address jumpers. v Possible contamination of any device that has a cleaning procedure. See the operator guide for cleaning instructions. v Excessive static electricity. v Correct voltage at the system unit power outlet

48

Diagnostic Information for Multiple Bus Systems

v Check devices that use jumpers to set the SCSI address for loose jumpers. See the operator guide for cleaning instructions. v Check any device that has a cleaning procedure for contamination. MAP 0040: Intermittent Problem Isolation 49 . and so on). v Check the outlet that the device is plugged into for correct voltage. v Check the SCSI signal cables to the devices for loose connectors and terminators. v Check the temperature of the devices. Be sure to check RETAIN® for known problems with your type of system unit or software. Things to Check For Use the software documentation to analyze software problems. Software-caused system crashes Check the following software items: v Is the problem only with one application program? v Is the problem only with one device? v Does the problem occur on a recently installed program? v Was the program recently patched or modified in any way? v Is the problem associated with any communication lines? v Check for static discharge occurring at the time of the failure. v Check the error log for entries for the adapter driving the failing devices. Software Symptoms Symptom of Software Problem Any symptom you suspect is related to software.Symptom of Hardware Problem Only externally attached devices are failing. Chapter 7. printers. Are the cooling vents blocked? Are the fans running? v Check for other devices near the failing device that may be radiating noise (displays. v Check for excessive static electricity. Things to Check For Check the following items that are common to more than one device.

50 Diagnostic Information for Multiple Bus Systems .

MAP steps requiring the removal of the cable from the adapter are inapplicable. v If the SCSI bus is attached to a RAID subsystem. Replace the system board or I/O board when the procedure calls for replacing the adapter. For additional information concerning high-availability configurations. Devices. place an external differential terminator on the external port. Considerations v Remove power from the system before connecting and disconnecting cables or devices to prevent hardware damage or erroneous diagnostic results. v For intermittent problems that cannot be resolved with this MAP. refer to Chapter 1. see Chapter 1. Or. v The differential version of the adapter has socket-type terminators to support high-availability. v If the failure is a terminator power failure (SRNs xxx-226.Chapter 8. and Cable Information for Multiple Bus Systems. Follow the steps in this MAP to isolate a SCSI bus problem. since an adapter that is not terminated always fails diagnostics. Go to “Step 0050-5” on page 52. If the configuration involves a Y-cable. Proper SCSI diagnostics require proper termination. v Also. xxx-800). MAP 0050: SCSI Bus Problems Purpose of This MAP Use this MAP to analyze problems with a SCSI bus. If this is the adapter’s configuration. refer to the RAID subsystem documentation for any problem determination. with the appropriate terminator. Step 0050-1 Have recent changes been made to the SCSI configuration? NO YES Go to “Step 0050-2” on page 52. 51 . always allow five minutes for the PTC to cool. see the Adapters. use this MAP for SCSI adapters that are built into system boards or I/O boards. v If the system uses shared DASD or high-availability configuration. For additional information about this adapter. “Service Hints” on page 1. the terminators would have been removed from the adapter. leave it. “Service Hints” on page 1. attached to the adapter. xxx-240. be sure that the other system sharing the devices is not using those devices.

and inspect Jumper J7. Is the adapter a single-ended adapter? NO YES Go to “Step 0050-6”. Refer to the ″SCSI Cabling″ section of the Adapters. Step 0050-4 Is an enclosure or drawer that supports hot-swap devices controlled by the adapter? NO YES Go to “Step 0050-22” on page 58. Go to “Step 0050-13” on page 54. Using the first three digits of the SRN. Step 0050-5 This step handles cases where recent changes have been made to the SCSI configuration. refer to the FFC listing and determine if the adapter is single-ended or differential. Go to “Step 0050-7” on page 53. Power off the system. 52 Diagnostic Information for Multiple Bus Systems . Devices. Go to “Step 0050-15” on page 55. Step 0050-3 Are there any devices other than hot-swappable devices controlled by the adapter? NO YES Go to “Step 0050-4”. Are the jumpers correct? NO YES Go to “Step 0050-8” on page 53. Go to “Step 0050-9” on page 53. and Cable Information for Multiple Bus Systems for the correct jumper settings.Step 0050-2 Are there any hot-swap devices controlled by the adapter? NO YES Go to “Step 0050-3”. Go to “Step 0050-11” on page 54. Step 0050-6 The adapter’s termination jumper settings may be incorrect.

configurations that exceed the maximum cable lengths. MAP 0050: SCSI Bus Problems 53 . v Cabling problems such as. missing termination. and RN3 are not populated. Step 0050-9 Check for the following problems: v Address conflicts between devices. and run diagnostics on the adapter. or excessive termination. “MAP 0410: Repair Checkout” on page 119. Correct the problem. Devices.Step 0050-7 If the adapter is not being used in a high-availability configuration. Did the diagnostic pass? NO YES Go to “Step 0050-9”. 2. and Cable Information for Multiple Bus Systems for more details about supported SCSI cabling. RN2. Step 0050-8 1. and run diagnostics on the adapter. be sure sockets RN1. Go to “Step 0050-9”. Did a failure occur? NO YES Go to Chapter 22. Refer to the Adapters. 2. Power on the system. RN2. Go to “Step 0050-10”. Correct the jumper settings and reinstall the adapter and all cables. Go to “Step 0050-2” on page 52. Step 0050-10 1. If the adapter is being used in a high-availability configuration. Chapter 8. Power on the system. and RN3 are populated. “MAP 0410: Repair Checkout” on page 119. Did you find a problem? NO YES Go to “Step 0050-2” on page 52. be sure sockets RN1. Go to Chapter 22.

select the The resource has been turned off. If the Missing Options menu displays. Did a failure occur? NO YES Go to “Step 0050-12”. Rerun diagnostics on the adapter. the problem may be with the last device reconnected. Make a record of the problem. but should remain in the system configuration option for all the devices that were disconnected. c. Step 0050-12 Reconnect the hot-swap devices one at time. Rerun diagnostics on the adapter. Disconnect all hot-swap devices attached to the adapter. Follow these steps: 1. follow this procedure: 1. 5. Power off the system. but should remain in the system configuration option for all the devices that were disconnected. 3. contact your support center. 1. g. Go to “Step 0050-3” on page 52. and boot the system in the same mode that you were in when you received the symptom that led you to this MAP. 54 Diagnostic Information for Multiple Bus Systems . 2. Power on the system. Otherwise. Rerun diagnostics. 4. Power on the system. f. If the adapter fails. Step 0050-13 This step determines if a device other than a hot-swappable device is causing the failure. e. Perform these substeps: a. 3. Rerun the diagnostics on the adapter. 2. After reconnecting each device. If the Missing Options menu displays. d. If diagnostics fail. the problem could be intermittent. Follow repair procedures for that last device. If diagnostics pass. 4.Step 0050-11 This step determines if a hot-swap device is causing the failure. b. If diagnostics fail. Run the diagnostics on the adapter. “MAP 0410: Repair Checkout” on page 119. 2. If no errors occur. Running the diagnostics for each device on the bus may provide additional information. Disconnect all devices attached to the adapter. Power off the system. go to Chapter 22. 3. select the The resource has been turned off. put back the last device. replace the SES backplane corresponding to the slot for the device.

Go to “Step 0050-18” on page 56. the problem could be intermittent. Go to “Step 0050-16”. Note that the SES is referred to as the DASD controller in some systems. Run the diagnostics on the adapter. follow this procedure: 1. Rerun the diagnostics on the adapter. MAP 0050: SCSI Bus Problems 55 . Step 0050-14 Reconnect the devices one at time. select the The resource has been turned off. the problem should be with the last device reconnected. If the Missing Options menu displays. 5. Follow the repair procedures for that device. Refer to the system or enclosure service guide to determine if the SES (DASD controller) is a FRU that plugs into the backplane or is integrated on the backplane. “MAP 0410: Repair Checkout” on page 119. Power off the system. 2. Running the diagnostics for each device on the bus may provide additional information. Step 0050-15 This step determines if the SCSI Enclosure Services (SES) is the problem. Locate the SES (DASD controller) part number under FFC 199. If no errors occur. but should remain in the system configuration option for all the devices that were disconnected. After reconnecting each device. 3. Make a record of the problem. then go to Chapter 22. 2. Did a failure occur? NO YES Go to “Step 0050-17” on page 56. Did a failure occur? NO YES Go to “Step 0050-14”. If there is a failure. Does the SES (DASD controller) plug into the backplane? NO YES Go to “Step 0050-18” on page 56. 3. 4. Step 0050-16 Follow these steps: 1. Go to “Step 0050-4” on page 52.5. Power on the system. Chapter 8. Remove the SES (DASD controller). Run the diagnostics on the adapter.

Does the SES (DASD controller) plug into the backplane? NO YES Go to “Step 0050-20” on page 57. Step 0050-19 Follow these steps: 1. 56 Diagnostic Information for Multiple Bus Systems . Replace the SES (DASD controller). Power off the system. select the The resource has been turned off. see “Considerations” on page 51. Run the diagnostics on the adapter. but should remain in the system configuration option for all the devices that were disconnected. 2. Disconnect all cables attached to the adapter. Reconnect the cables to the adapter. 4. Go to Chapter 22. Step 0050-18 Follow these steps: 1. Power off the system. Go to “Step 0050-21” on page 58. “MAP 0410: Repair Checkout” on page 119. 2. 3. “MAP 0410: Repair Checkout” on page 119. Power on the system. 2. 5. For SCSI differential adapters in a high-availability configuration. If the Missing Options menu displays. 3. Power off the system. then go to Chapter 22. Did a failure occur? NO YES Go to “Step 0050-19”. Replace the adapter.Step 0050-17 Follow these steps: 1.

Chapter 8. 2. Go to “Step 0050-21” on page 58. Did a failure occur? NO YES Go to Chapter 22. MAP 0050: SCSI Bus Problems 57 . “MAP 0410: Repair Checkout” on page 119. If the Missing Options menu displays. Run the diagnostics on the adapter. Power on the system. 4.Step 0050-20 Follow these steps: 1. Replace the SES (DASD controller). select the The resource has been turned off. 3. Locate the SES (DASD controller) part number under FFC 199. but should remain in the system configuration option for all the devices that were disconnected.

Follow these steps for each FRU replaced: 1. Refer to FFC 190 for the cable part numbers. 3. but should remain in the system configuration option for all the devices that were disconnected. Run the diagnostics on the adapter. go to Chapter 22. 2. Power on the system.Step 0050-21 One of the cables remaining in the system is defective. 5. If there is no failure. then go to Chapter 22. Rerun the diagnostics for the adapter. Disconnect all cables attached to the adapter. 58 Diagnostic Information for Multiple Bus Systems . “MAP 0410: Repair Checkout” on page 119. 3. Refer to FFC 190 for the cable part numbers. If there is any failure. Replace the parts one at time in the order listed. Step 0050-23 One of the cables remaining in the system is defective. 4. Step 0050-22 Follow these steps: 1. Follow these steps for each FRU replaced: 1. “MAP 0410: Repair Checkout” on page 119. If the Missing Options menu displays. continue with the next FRU. 2. Did a failure occur? NO YES Go to “Step 0050-23”. 3. Rerun the diagnostics for the adapter. Power off the system. continue with the next FRU. If there is any failure. go to Chapter 22. select the The resource has been turned off. “MAP 0410: Repair Checkout” on page 119. Replace the parts one at time in the order listed. Replace the adapter. If there is no failure. 2.

Record the Crash code and the Dump Status from the message you recorded in “Step 0070-1”. see Chapter 28. Step 0070-3 A Type 102 message generates when a software or hardware error occurs during system execution of an application. For an explanation of the Dump Status or the Crash Codes. Wait until the 888 sequence displays. 1. Use the following information to determine the content of the type 102 message. in sequence. Step 0070-2 Using the first code that you recorded. MAP 0070: 888 Sequence in Operator Panel Display Purpose of This MAP An 888 sequence in operator panel display suggests that either a hardware or software problem has been detected and a diagnostic message is ready to be read. On systems with a 3-digit or a 4-digit operator panel. The message readout sequence is: 102 = Message type RRR = Crash code (the three-digit code that immediately follows the 102) SSS = Dump status code (the three-digit code that immediately follows the Crash code). Go to “Step 0070-2”. “Diagnostics Numbers and Location Codes” on page 217. 59 . Type 102 Type 103 Go to “Step 0070-3”. 2.Chapter 9. Note: The 888 may or may not be flashing on the operator panel display. 3. Descriptions of the crash codes and the dump status codes are in Chapter 28. Record. Go to “Step 0070-4” on page 60. Stop recording when the 888 digits reappear. you may need to press the system’s ″reset″ button to view the additional digits after the 888. Step 0070-1 Perform the following steps to record the information contained in the 888 sequence message. use the following list to determine the next step to use. every code displayed after the 888. “Diagnostics Numbers and Location Codes” on page 217.

Step 0070-4 A Type 103 message generates upon hardware error detection. Note: The only way to recover from an 888 type of halt is to turn off the system unit. Is the Diagnostic Mode Selection menu displayed? No Yes Go to Entry MAP in the system unit service guide. 2. v The system stops with an 888 sequence. and load the online diagnostics in service mode. Record the SRN and FRU location codes from the recorded message. Wait until one of the following conditions occurs: v You are able to load the diagnostics to the point where the Diagnostic Mode Selection menu displays. 3. The message also has a type 103 message included in it. Go to “Step 0070-4” to decipher the SRN and field replaceable unit (FRU) information in the Type 103 message. Turn off the system unit power. 2.or four-digit code following the (x)xxx code). The message readout sequence is: 103 = Message type (x)xxx (y)yyy = SRN (where (x)xxx = the three. Go to “Step 0070-6” on page 61. Find the SRN in the Service Request Number List and do the indicated action.or four-digit code following the 103 and (y)yyy is the three. v The system appears hung. Turn on the system unit power. Note: Type 102 messages have no associated SRNs.Are there additional codes following the Dump Status? No YES Go to “Step 0070-5”. Step 0070-5 Perform the following steps: 1. Use the following steps and information you recorded in “Step 0070-1” on page 59 to determine the content of the Type 103 message. 1. 60 Diagnostic Information for Multiple Bus Systems .

Chapter 9. Was an SRN reported by the diagnostics? No Yes This is possibly a software-related 888 sequence. Record the SRN and its location code information. Find the SRN in the SRN Listing and do the indicated action.Step 0070-6 Run the All Resources options under Advanced Diagnostics in Problem Determination Mode. Follow the procedure for reporting a software problem. MAP 0070: 888 Sequence in Operator Panel Display 61 .

62 Diagnostic Information for Multiple Bus Systems .

Perform a system shutdown and then. 2. 3.Chapter 10. “MAP 0040: Intermittent Problem Isolation” on page 47. Is the ″Please Define the System Console″ screen displayed? No Yes The symptom has changed. MAP 0080: System Bus Problem Isolation Purpose of This MAP Use this MAP to analyze a bus problem that does not prevent the system from booting. If you think that you have an intermittent problem. Step 0080-1 1. Turn on the system unit power. 4. Step 0080-2 Follow the displayed instructions until the Installed Resources menu displays. Are all of the installed PCI adapters listed on the Installed Resources menu? No Yes Go to “Step 0080-3” on page 64 and make a note of all PCI adapters not listed and their locations. Go to “Step 0080-2”. Use MAP 1540 in the system unit’s service guide. Locate the diagnostic CD-ROM disc. 5. You may have an intermittent problem. and then load the diagnostic CD-ROM disc into the CD-ROM drive. if necessary. Note: Some devices installed in the system may require the loading of supplemental diskettes for diagnostic support. go to Chapter 7. Load the Standalone Diagnostics. turn off the system unit power. 63 . Wait until the ″Please Define the System Console″ screen displays or all system activity appears to have stopped.

turn off the system unit power. Call your service support structure. 3. if necessary. Go to “Step 0080-4”. Is the ″Please Define the System Console″ screen displayed? No Yes The symptom has changed. 4. Use MAP 1540 in the system unit’s service guide. 64 Diagnostic Information for Multiple Bus Systems . 2. do not remove it. Note: If only one adapter is present. Is the adapter that you did not remove shown as an installed resource? No Yes Record SRN 111-78C and make a note of the adapter you just installed. and load standalone diagnostics from the CD-ROM. 2. Look up the SRN in the SRN listings and perform the indicated action. Wait until the ″Please define the System Console″ screen displays or all system activity appears to have stopped. Wait until the ″Please Define the System Console″ screen displays or all system activity appears to stop. Step 0080-5 Have you installed all of the removed adapters? No Yes Go to “Step 0080-6”. and then. Turn on the system unit power. Step 0080-6 1. Remove all but one of the PCI adapters that was not listed on the Installed Resources menu. 3.Step 0080-3 1. Perform a system shutdown and then. Go to “Step 0080-5”. Is the ″Please Define the System Console″ screen displayed? No Yes The symptom has changed. Turn on the system unit power. Go to “Step 0080-7” on page 65. Install one of the remaining removed adapters into its original location. turn off the system unit power. Use MAP 1540 in the system unit’s service guide. 4. if necessary. Step 0080-4 Follow the displayed instructions until the Installed Resources menu displays. and load Standalone Diagnostics from the CD-ROM. Perform a system shutdown.

Go to “Step 0080-5” on page 64. Look up the SRN in the SRN listings and perform the indicated action. MAP 0080: System Bus Problem Isolation 65 . Is the adapter that you just installed shown as an installed resource? No Yes Record SRN 111-78C and make a note of the adapter you just installed.Step 0080-7 Follow the displayed instructions until the Installed Resources menu displays. Chapter 10.

66 Diagnostic Information for Multiple Bus Systems .

use the part number in the FFC list.Chapter 11. Step 0210-1 Read the following information before proceeding. Do you want to exchange this FRU as a hot-plug FRU? NO YES Go to “Step 0210-3”. 4. “Location Codes for CHRP Model Architecture System Units” on page 236. if available. use it in place of the part number in the FFC List. record the part number and description for each FRU. For additional information. Go to Chapter 12. Step 0210-3 1. the part number provided by the VPD may be incorrect. record the FRU part number and description of each FRU. see “Location Codes for RSPC Model Architecture System Units” on page 234. or the system unit’s service guide. record the SRN source code and the failing function codes in the order of their listing. and if not already recorded. v When identifying the location of a planar or a plug-in card. In some cases.3. 3. the physical location code may contain the failing FRU’s extended location information. and if not already recorded. Step 0210-2 Find the failing function codes in the “Failing Function Code List” on page 538. “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77. if not already recorded.3 and later diagnostics display the part number and the physical location code. Find the failing function codes in the ″Failing Function Code List. MAP 0210: General Problem Resolution Purpose of This MAP Use this MAP to exchange the FRUs in the order of their failure probability. v Version 4. 67 . on the Problem Report screen. perform the operating system’s shutdown procedure (get help if needed). Referring to “Service Request Number Lists” on page 244. The parts are listed in probability-of-failure order. Turn off the system power.″ refer to Chapter 36. v Part numbers display if they are available from vital product data (VPD). 2. If the operating system is running. In that case. Go to “Step 0210-2”. “Failing Function Codes (FFCs)” on page 535. If the part number displays.

Go to “Step 0210-8” on page 70. Go to “Step 0210-8” on page 70. cables. Were you able to load the diagnostics? NO YES The symptom has changed. go to the system unit’s service guide. Go to “Step 0210-8” on page 70. Go to the step indicated in the Action column. SRN Source Code A B C D E F G H Action Go to “Step 0210-8” on page 70. To verify the repair. 2. Go to “Step 0210-8” on page 70. Check for loose cards. Go to “Step 0210-17” on page 73. Turn on the system power. and obvious problems. Step 0210-4 The following steps handle the problems when the system does not detect a resource. Go to “Step 0210-4”. 1. Go to “Step 0210-5” on page 69.Exchange one of the FRUs (normally the first one listed). find the SRN source code that you recorded in the following table. If you do not find a problem. Note: Use the following substeps for the SRNs having source code: C. Wait until the diagnostics are loaded or the system appears to stop. 68 Diagnostic Information for Multiple Bus Systems . Go to “Step 0210-14” on page 72. Load Online Diagnostics in Service Mode (refer to the system’s service guide if needed). 3.

2. Go to “Step 0210-6”. “MAP 0030: Additional Problem Determination” on page 45. MAP 0210: General Problem Resolution 69 . Step 0210-7 1. Load the Online Diagnostics in Service Mode. Were you able to load the diagnostics? NO YES The symptom has changed. 2. “MAP 0410: Repair Checkout” on page 119. 4. You cannot continue until this is done. Press Enter. Go to Chapter 22. and repeat the steps. go to the system’s service guide. Go to “Step 0210-5”. select System Verification. Note: If the terminal type is not defined. Step 0210-6 Look at the failing function codes and the FRU part numbers you recorded for this SRN. After performing a shutdown of the operating system. 3. Refer to the system unit service guide if needed. The SRN did not identify the failing FRU. you are prompted to define it. Wait until the diagnostics are loaded or the system appears to stop. Exchange the next FRU in the list. and obvious problems. Remove the new FRU and install the original FRU. Is the MISSING RESOURCE menu displayed? NO YES This completes the repair.Step 0210-5 1. Turn on the system unit power. Check for loose cards. Have you exchanged all the FRUs that correspond to the failing function codes? NO YES Go to “Step 0210-7”. turn off the system unit power. When the DIAGNOSTIC MODE SELECTION menu displays. 3. Go to Chapter 6. Chapter 11. If you do not find a problem. cables. 5. Select the Advanced Diagnostics option. 6.

Go to “Step 0210-10” on page 71. 2. Select the Advanced Diagnostics Routines option. Were you able to load the diagnostics? NO The symptom has changed. The system time and date information should also be set when the repair is completed. if possible. skip the next step and answer the question below. Refer to the system’s service guide if needed. Check for loose cards. “MAP 0020: Problem Determination Procedure” on page 29 and get a new SRN. Turn on the system power. Wait until the diagnostics are loaded or the system appears to stop. it may be necessary for the customer to set the network boot information. When the DIAGNOSTIC MODE SELECTION menu displays.Step 0210-8 Note: Run Online Diagnostics. 3. 70 Diagnostic Information for Multiple Bus Systems . proceed to the next substep. You cannot continue until this is done. Press Enter. Is the ADVANCED DIAGNOSTIC SELECTION menu displayed? NO YES Go to “Step 0210-15” on page 73. Note: If the terminal type is not defined. 1. 4. you are prompted to define it. If you do not find a problem. and obvious problems. 3. YES Step 0210-9 1. Go to “Step 0210-9”. Load either the Online or Standalone Diagnostics in Service Mode. go to Chapter 4. 2. If it does not display. If the MISSING RESOURCES menu displays. select the System Verification option. If the system planar or battery has been replaced and you are loading diagnostics from a server over a network. cables.

Refer to the system’s service guide if needed. 3. Load either the Online or Standalone Diagnostics in Service Mode. select Commit (F7 key). Wait until the diagnostics are loaded or the system appears to stop. “MAP 0030: Additional Problem Determination” on page 45. Go to Chapter 22. cables. MAP 0210: General Problem Resolution 71 . Check for loose cards. 2. Select the resource that has been replaced from the menu. select sysplanar0. Note: The RESOURCE REPAIR ACTION menu allows a repair action to be logged for the resource being tested. 6. Chapter 11. The SRN did not identify the failing FRU. If the RESOURCE REPAIR ACTION menu displays. Did the FRU pass the test? NO YES Go to “Step 0210-11”. 4. Step 0210-12 1. Remove the new FRU and install the original FRU. “MAP 0410: Repair Checkout” on page 119. Were you able to load the diagnostics? NO YES The symptom has changed. 2. perform the following: 1. turn off the system unit power. and obvious problems. Turn on the system unit power. Go to “Step 0210-13” on page 72. After all selections have been made. If the FRU you exchanged does not appear on the resource selection screen. Have you exchanged all the FRUs that correspond to the failing function codes? NO YES Go to “Step 0210-12”. go to the system’s service guide. This completes the repair. Step 0210-11 Look at the failing function codes and FRU part numbers you recorded for this SRN. This prevents Error Log Analysis from reporting problems on FRUs that have been replaced.Step 0210-10 Select and run the diagnostics for the FRU you exchanged. If you do not find a problem. 5. Go to Chapter 6. Exchange the next FRU in the list. After performing a shutdown of the operating system.

repeated selection of the Problem Determination option continues to reflect the same error for a period of time. based on that error log analysis. select the System Verification option. you are prompted to define it. If the MISSING RESOURCES menu displays. Go to “Step 0210-10” on page 71. If the Problem Determination option needs to be run. 2. Disregard this SRN. and problems are assigned the SRN source: G. Select the Advanced Diagnostics Routines option. Although a FRU may have already been replaced. Go to Chapter 4. 3. If more information is needed. Step 0210-14 Every time the Problem Determination option is selected from the Diagnostics Mode Selection menu. Press Enter. Has the FRU called out by this SRN been replaced within the past week? NO YES Go to “Step 0210-8” on page 70. When the DIAGNOSTIC MODE SELECTION menu displays. the error log for the preceding time period is analyzed. proceed to the next substep. use the operating system’s errclear command to delete the error log entry for the replaced resource. Is the ADVANCED DIAGNOSTIC SELECTION menu displayed? NO YES Go to “Step 0210-15” on page 73. skip the rest of these steps and answer the question below. 72 Diagnostic Information for Multiple Bus Systems . 4. Note: If the terminal type is not defined. If it does not display.Step 0210-13 1. “MAP 0020: Problem Determination Procedure” on page 29. Ensure that the indicated failing FRU has not been replaced in the previous week. The System Verification option does not perform error analysis. see the operating system Commands Reference. You cannot continue until this is done.

1. Did the system stop with an 888 sequence in the operator panel display? NO YES This completes the repair. Step 0210-17 The following steps handle the problem when the machine stops with an 888 sequence displayed in the operator panel display while it is loading diagnostics. cables. Power on the system and load the Online Diagnostics in Service Mode (refer to the system’s service guide if needed). Go to “Step 0210-21” on page 75. v The DIAGNOSTIC OPERATING INSTRUCTIONS displays. Go to Chapter 22. 2. Go to “Step 0210-16”. go to the Chapter 4.Step 0210-15 Is the Missing Resource menu displayed? NO The symptom has changed. Wait until one of the following conditions occurs and answer the question. and obvious problems. When you finish processing the missing resources. Go to “Step 0210-18” on page 74. If you do not find a problem. “MAP 0020: Problem Determination Procedure” on page 29 and get a new SRN. MAP 0210: General Problem Resolution 73 . v An 888 sequence displays in the operator panel display. answer the following: Did you get an SRN? NO YES Go to “Step 0210-22” on page 75. YES Step 0210-16 Follow the displayed instructions. Chapter 11. “MAP 0410: Repair Checkout” on page 119. v The operator panel display is blank. Check for loose cards. v The machine stops for at least three minutes with a steady number in the operator panel display.

74 Diagnostic Information for Multiple Bus Systems . “MAP 0030: Additional Problem Determination” on page 45. “MAP 0070: 888 Sequence in Operator Panel Display” on page 59. 4. Wait until one of the following conditions occurs and answer the question. Replace FRU parts in the order the FFCs are listed. “MAP 0410: Repair Checkout” on page 119. 6. Go to “Step 0210-19”. Set the power switch on the system unit to Off. Have you exchanged all the FRUs that correspond to the failing function codes? NO YES Go to “Step 0210-20”. 2. Power on the system. Go to Chapter 6. v The DIAGNOSTIC OPERATING INSTRUCTIONS displays. 2. 3. Find and record the location codes for the FRUs in the message. Read out the message in the operator panel display. 5. 3. v An 888 sequence displays in the operator panel display. Are the SRN and the location codes the same as the SRN you were analyzing? NO YES Go to “Step 0210-1” on page 67 and analyze the new SRN. If needed see Chapter 9. v The machine stops for at least three minutes with a steady number in the operator panel display. Go to “Step 0210-19”. Step 0210-20 1. v The operator panel display is blank. Remove the new FRU and install the original FRU. Find and record the SRN in the message. Load the Online Diagnostics in Service Mode (refer to the system’s service guide if needed). Go to Chapter 22. The SRN did not identify the failing FRU.Step 0210-18 1. Step 0210-19 Look at the failing function codes and FRU part numbers you recorded for this SRN. Did the system stop with an 888 sequence in the operator panel display? NO YES This completes the repair.

Go to “Step 0210-22”. Chapter 11. and obvious problems. go to the Chapter 4. 2. 3. Go to “Step 0210-10” on page 71. select the System Verification option. Exit the Missing Resources menu. If you do not find a problem. cables. “MAP 0020: Problem Determination Procedure” on page 29 and get a new SRN.Step 0210-21 Is the SRN the Same as the Original SRN? NO The symptom has changed. YES Step 0210-22 1. Check for loose cards. When the DIAGNOSTIC MODE SELECTION menu displays. MAP 0210: General Problem Resolution 75 .

76 Diagnostic Information for Multiple Bus Systems .

77 . If the system displayed a FRU part number on the screen. Step 0220-3 Note: Refer to the system unit’s service guide for removal and replacement procedures. and record the FRU part number and description of each FRU. use that part number to exchange the FRU. 2. Install the new FRU. Refer to the removal and replacements procedures in your system’s service guide or the PCI Adapter Placement Reference Guide to determine if the FRU is hot-swappable. “Step 0210-2” on page 67 and answer NO to the question Do you want to exchange this FRU as a hot-plug FRU?. ask the system administrator to perform any steps necessary to prepare the device for removal. Remove the old FRU. Note: The FRU you want to hot plug might have a defect on it that can cause the hot-plug operation to fail.Chapter 12. 3. 1. If. you continue to get an error message that indicates that the hot-plug operation has failed. Enter the diag command. Then go to MAP 210.plug procedure. Step 0220-1 1. Does this system unit support hot-swapping of the first FRU listed? NO YES Go to MAP 0210. 2. Go to “Step 0220-3”. Step 0220-2 Is the FRU a hot-swap power supply or fan? NO YES Go to “Step 0220-4” on page 78. 3. If there is no FRU part number displayed on the screen. Find the failing function codes in the FFC listing. Go to “Step 0220-2”. Record the SRN source code and the failing function codes in the order listed. after following the hot. Attention: If the FRU is a disk drive or an adapter. refer to the SRN listing. MAP 0220: Hot-Swap FRU Problem Resolution Purpose of This MAP Use this MAP to exchange hot-swappable FRUs. schedule a time for deferred maintenance when the system containing the FRU can be powered dow.

Go to “Step 0220-6”. Is the hot-plug disk drive’s amber LED unlit? NO YES Ask the customer to remove the hot-plug disk drive from the operating system configuration (refer them to System Management guide for more information). Step 0220-8 Does the hot-plug drive’s enclosure have a system guide with procedures for Removing and Replacing hot-plug SCSI Disk drives? NO YES Go to “Step 0220-9”.Go to “Step 0220-14” on page 81. Ask the customer to back up the data on the drive that you intend to replace onto another drive. Step 0220-7 Refer to the system’s service guide in the ″Removing Hot-Plug SCSI Disk Drives″ section under ″Removal and Replacement Procedures″ for information about replacing hot-plug SCSI Disk Drives. Step 0220-6 Is the hot-plug drive located within a system unit? NO YES Go to “Step 0220-8”. Use that procedure to remove the old hot-plug SCSI disk drive and replace it with a new hot-plug SCSI disk drive. Go to “Step 0220-7”. Go to “Step 0220-13” on page 80. Step 0220-4 Is the FRU a hot-plug PCI adapter? NO YES Go to “Step 0220-5”. Go to “Step 0220-10” on page 79. 2. Go to “Step 0220-13” on page 80. The amber LED on the hot-plug disk drive should be off. 78 Diagnostic Information for Multiple Bus Systems . Go to “Step 0220-12” on page 80. Verify that the disk drive has been removed from the operating system configuration. Step 0220-9 1. Step 0220-5 Is the FRU a SCSI hot-plug device? NO YES Go to “Step 0220-11” on page 79.

The physical disk will go into the REMOVE state. Ask Chapter 12. Verify that it is the physical drive you wish to remove. Refer them to the System Management Guide for more information. the drive would not be listed as an IDENTIFY AND REMOVE RESOURCES selection within the RAID HOT PLUG DEVICES screen. Go to “Step 0220-15” on page 81. until you see the ″hot-plug task″ on the service aid menu. then select COMMIT. Select the slot which contains the SCSI hot-plug drive you wish to replace. it is not a SPARE or FAILED drive. 2. replace the hot-plug drive using the following procedure: 1. In that case you must ask the customer to put the drive into FAILED state. press Enter. Select the REPLACE/REMOVE a Device Attached to an SES Device option. Otherwise. You will see a fast blinking green light on the front on the hot-plug drive indicating that it is ready for removal. Use the List the SES Devices option to show the configuration of the hot-plug slots. 5. Once the hot-plug drive is in place. as indicted by the LED on the drive.Step 0220-10 Using the Hot-Plug Task service aid described in Chapter 27. Select the physical disk which you wish to remove from the RAID array and press Enter. 4. 6. replace the hot-plug drive using the hot plug RAID service aid: Note: The drive you wish to replace must be either a SPARE or FAILED drive. Press Enter. 1. Identify the slot number of the adapter for the FRU you want to replace. choose the REMOVE option and press Enter. 6. 4. “Introduction to Tasks and Service Aids” on page 169. At the IDENTIFY AND REMOVE RESOURCES menu. Press the exit key. If the physical disk you wish to remove is not listed. Note: Refer to service guide for the system unit or enclosure that contains the hot-plug drive for removal and replacement procedures. The disk will go into the IDENTIFY state. Wait while configuration is done on the drive. Select the RAID adapter that is connected to the RAID array containing the RAID drive you wish to remove. Choose the IDENTIFY option in the IDENTIFY AND REMOVE RESOURCES menu. Step 0220-11 Using the Hot Plug Task service aid described in Chapter 27. 5. Install the new hot-plug drive. “Introduction to Tasks and Service Aids” on page 169. Ask the customer to back up the data on the drive that you intend to replace. Select the RAID HOT PLUG DEVICES option within the HOT PLUG TASK under DIAGNOSTIC SERVICE AIDS. A list of the physical disks in the system which may be removed will be displayed. select it and press Enter. 7. 2. then press Enter. indicated by a flashing light on the drive. MAP 0220: Hot-Swap FRU Problem Resolution 79 . 3. Remove the old hot-plug drive. If the physical disk you wish to remove is listed. 3.

Return the system to the customer. Remove the old hot-plug RAID drive. The drive will exit the REMOVE state. enter the diag command. Does the hot-plug SCSI disk drive you just replaced appear on the resource list? NO Verify that you have correctly followed the procedures for replacing hot-plug SCSI disk drives in the system service guide. Refer them to system management guide for more information. Ask the customer to add the physical disk drive to the original configuration within the RAID. 3. 8.the customer to put the drive in the FAILED state before you can proceed to remove it. This completes the repair. and will go to the NORMAL state once you exit diagnostics. Go to “Step 0220-14” on page 81. If the disk drive still does not appear in the resource list. Install the new hot-plug RAID drive. Step 0220-13 1. and select the Advanced Diagnostics Routines option. press Enter. you must use the F3 key to return to the DIAGNOSTIC OPERATING INSTRUCTIONS menu before proceeding with the next step. b. When the DIAGNOSTIC MODE SELECTION menu displays. Enter the diag command. select the System Verification option. Note: There are no elective tests to run on a RAID drive itself under diagnostics (the drives are tested by the RAID adapter). go to Chapter 11. If not already running diagnostics. or else the drive might not appear on the resource list. 9. Step 0220-12 Remove the old adapter FRU and install the new adapter FRU. 2. Once the hot-plug drive is in place. Refer to the ″Replacing a Hot-Pluggable PCI Adapter″ section within the ″Removal and Replacement Procedures″ section of the system service guide. Refer the customer to the System Management Guide for more information. Refer to service guide for the system unit or enclosure that contains the physical drive for removal and replacement procedures for the following substeps: a. Go to “Step 0220-14” on page 81. “MAP 0210: General Problem Resolution” on page 67 to replace the resource that the hot-plug SCSI disk drive is plugged in to. YES 80 Diagnostic Information for Multiple Bus Systems . Go to the FUNCTION SELECTION menu. Note: If you are already running service mode diagnostics and have just performed the Configure Added/Replaced Devices task (under the SCSI Hot Swap manager of the Hot Plug Task service aid).

If a previous configuration exists on the replacement adapter. Use the Log Repair Action option in the TASK SELECTION menu to update the AIX error log. Refer to system management guide for more information. ask the customer to add the hot-plug disk drive to the operating system configuration. “MAP 0410: Repair Checkout” on page 119. Note: On systems with a Fault Indicator LED. At the AIX command line. select the resource associated with your repair action.Step 0220-14 Run the diagnostic test on the FRU you just replaced. On the PCI SCSI RAID Adapter selection menu. go to the FUNCTION SELECTION menu. 7. Go to Chapter 22. Did the diagnostics run with no trouble found? NO YES Go to “Step 0220-15”. On the ″PCI SCSI Disk Array Manager″ screen. If it is not displayed on the resource list. 3. Did the diagnostics run with no trouble found? NO YES Go to “Step 0220-16” on page 82. select sysplanar0. The following is an example of how the customer would resolve the configuration: 1. restore the settings to the value they had prior to servicing the system. 3. 5. select RESOLVE PCI SCSI RAID ADAPTER CONFIGURATION. Chapter 12. Before returning the system to the customer. this must be cleared. select the System Verification option. If you performed service on a RAID subsystem involving changing of the RAID adapter cache card or changing the configuration on RAID disks. type smitty pdam. Press F3. select RECOVERY OPTIONS. press Enter. 6. While in diagnostics. Select Clear PCI SCSI RAID Adapter Configuration. select the adapter that you changed. MAP 0220: Hot-Swap FRU Problem Resolution 81 . this changes the Fault Indicator LED from the ″Fault″ state to the ″Normal″ state. On the ″Recovery Options″ screen.″ Step 0220-15 1. 4. Run the diagnostic test on the FRU you just replaced. if a hot-plug disk has been removed. or sysplanar0. 2. select ACCEPT CONFIGURATION on DRIVES. On the ″Resolve PCI SCSI RAID Adapter Configuration″ screen. 2. When the DIAGNOSTIC MODE SELECTION menu displays. ask the customer to run PCI SCSI Disk Array Manager using smitty to resolve the PCI SCSI RAID Adapter configuration. If you changed the Service Processor or Network settings. Select the Advanced Diagnostics Routines option. On the next screen. If the repair action was reseating a cable or adapter.

If you get a Failed status message. then do this complete procedure. “MAP 0410: Repair Checkout” on page 119. exit smitty to return to the AIX command line. go to “Step 0220-14” on page 81. verify that you are doing recovery on the correct adapter. You should get an OK status message when the recovery is complete. “MAP 0410: Repair Checkout” on page 119. If the same SRN is reported in service mode. The SRN did not identify the failing FRU. remove the FRU you just replaced and install the original FRU in its place. press Enter to continue. When you complete the recovery.8. If steps were taken to make the device ready for removal. If the same SRN is reported in service mode. inform the System Administrator of the steps required to return the system to the original state. Schedule a time to run diagnostics in service mode. Does the system unit support hot-swapping of the next FRU listed? NO YES Go to Chapter 11. 82 Diagnostic Information for Multiple Bus Systems . Go to Chapter 22. Go to “Step 0220-17”. If the resource associated with your action is not displayed on the Resource List. run the Log Repair Action service aid under the Online Diagnostics for the resource that was replaced. Schedule a time to run diagnostics in service mode. YES Step 0220-17 Have you exchanged all the FRUs that correspond to the failing function codes? NO YES Go to “Step 0220-18”. “MAP 0210: General Problem Resolution” on page 67. select sysplanar0. “MAP 0030: Additional Problem Determination” on page 45. 9. The SRN did not identify the failing FRU. When you get the ″Are You Sure?″ selection menu. Step 0220-16 Does the original problem persist? NO If a FRU was replaced. go to Chapter 6. Step 0220-18 Note: Before proceeding. Go to Chapter 22.

Refer to the last character in the SRN.Chapter 13. The last character of the SRN is bit-encoded as follows: 8 4 2 1 | | | | | | | Replace all FRUs listed | | Hot-swap is supported | Software or Firmware could be the cause Reserved 2. Has any software or firmware been installed recently? NO YES Go to “Step 0230-4” on page 84. Check with your support center for any known problems with the new software or firmware. Obtain and follow the procedure to correct the software problem. A 4. Step 0230-1 1. Step 0230-3 Suspect the new software or firmware. MAP 0230: Platform Error Problem Resolution Purpose of This MAP Use this MAP to resolve problems reported by SRNs A00-000 to A1F-FFF. Go to “Step 0230-3”. or 7 indicates a possible software or firmware problem. Go to “Step 0230-2”. Are there any known problems with the software or firmware? NO YES Go to “Step 0230-4” on page 84. This completes the repair. 83 . 5. 6. Step 0230-2 Ask the customer if any software or firmware has been installed recently. Does the last character indicate a possible software or firmware problem? NO YES Go to “Step 0230-4” on page 84.

Record the physical location codes and FRU numbers. Step 0230-6 Were there any other SRNs that begin with an A00 to A1F reported? NO YES Go to “Step 0230-7”. Go to “Step 0230-8”. Step 0230-8 1. Follow the procedure for the new error code or SRN. Go to “Step 0230-8”. 2. Obtain the list of physical location codes and FRU numbers that were listed on the Problem Report Screen.Step 0230-4 Were any FRUs reported with the SRN? NO YES Go to “Step 0230-5”. A 2. Step 0230-7 Attempt to boot the system on slow boot mode. Were there any FRUs reported with the SRN? NO YES Go to “Step 0230-6”. Step 0230-5 Run the diagnostics in problem determination mode on sysplanar0. The list can be obtained by running the sysplanar0 diagnostics or using the Display Previous Diagnostic Results task. run the diagnostics in problem determination mode on sysplanar0 Were any new error codes or SRNs reported? NO YES Call your support center. Refer to the last character in the SRN. 6. or 7 indicates that hot-swap is possible. Does the last character indicate that hot-swap is possible? NO YES Go to “Step 0230-9” on page 85. If the system boots. Go to “Step 0230-1” on page 83 and use the new SRN. 84 Diagnostic Information for Multiple Bus Systems . 3. Go to “Step 0230-13” on page 88. 3.

11. 15. Select the Task Selection option. 12. Select the Log Repair Action option. 8. Note: If the Diagnostics Operating Instructions do not display or you are unable to select the Task Selection option. check for loose cards. or 7 indicates that all FRUs listed on the Problem Report Screen need to be replaced. Note: Use the appropriate procedure under ″Removal and Replacement Procedures″ in the system service guide to replace any FRUs indicated. Log a repair action for each replaced resource. If you do not find a problem. in the order listed. 5. “MAP 0020: Problem Determination Procedure” on page 29 and get a new SRN. 9. After the exercisers are complete. Was a problem reported? NO The repair is complete. 13. 4. and obvious problems. Turn off power to the system. perform the operating system’s shutdown procedure. If the resource associated with your repair action is not displayed on the resource list. if the FRU is a MCM containing multiple processors. “MAP 0410: Repair Checkout” on page 119. 10. select sysplanar0. where the processors may be assigned to different partitions) you may wish to also run exercisers on those other partitions containing these resources in addition to running them in the partition that reported the SRN. Wait until the Diagnostics Operating Instructions are displayed or the system appears to stop. exchange one FRU at a time. refer to the section under ″Reference Information″ in the system service guide ″Powering the system on and off″ for information on system shut down and powering the system on and off. 3. 5. Chapter 13. 2. Note: On a partitioned system. Load Online Diagnostics in service mode (see the system’s service guide if needed).Step 0230-9 Note: If necessary. Turn on power to the system. Press Enter. Refer to the last character in the SRN. If the operating system is running. Select Run Exercisers and run the short exercisers on all the resources. if the FRU you replaced contains resources that may be allocated to different partitions (for example. For SRNs ending with any other character. 3. Go to Chapter 22. cables. 1. go to Chapter 4. return to the Task Selection menu. 7. 14. MAP 0230: Platform Error Problem Resolution 85 . A 1. 6. Select Run Error Log Analysis and run analysis on all the resources. Return to the Task Selection Menu.

Go to “Step 0230-11”. 86 Diagnostic Information for Multiple Bus Systems . YES Step 0230-11 Look at the physical location codes and FRU part numbers you recorded. Check for loose cards. Call your support person for assistance. Have you exchanged all the FRUs that were listed? NO YES Go to “Step 0230-12” on page 87. “MAP 0020: Problem Determination Procedure” on page 29 and get a new SRN. and obvious problems. cables. go to Chapter 4.YES Go to “Step 0230-10”. The SRN did not identify the failing FRU. Step 0230-10 Is the problem the same as the original problem? NO The symptom has changed. If you do not find a problem.

After performing a shutdown of the operating system. if the FRU you replaced contains resources that may be allocated to different partitions (for example. 4. where the processors may be assigned to different partitions) you may wish to also run exercisers on those other partitions containing these resources in addition to running them in the partition that reported the SRN. 7. Remove the new FRU and install the original FRU. Select Run Error Log Analysis and run analysis on all the resources. Note: If the Diagnostics Operating Instructions do not display or you are unable to select the Task Selection option. 2. Log a repair action for each replaced resource. 8. 14. go to Chapter 4. “MAP 0410: Repair Checkout” on page 119. Select the Task Selection option. 15. 12. Was a problem reported? NO YES The repair is complete. select sysplanar0. MAP 0230: Platform Error Problem Resolution 87 . After the exercisers are complete. 11. return to the Task Selection Menu. Note: On a partitioned system. 13. Go to “Step 0230-10” on page 86. check for loose cards. turn off power to the system. If the resource associated with your action does not appear on the Resource List. 3. Load Online Diagnostics in service mode (see the system’s service guide if needed). 6. if the FRU is a MCM containing multiple processors. Wait until the Diagnostics Operating Instructions are displayed or the system appears to stop. “MAP 0020: Problem Determination Procedure” on page 29 and get a new SRN. cables. Go to Chapter 22. 10. 5. Turn on power to the system. Press Enter. 9. Return to the Task Selection Menu. Select the Log Repair Action option. and obvious problems. Exchange the next FRU in list.Step 0230-12 1. Chapter 13. Select Run Exercisers and run the short exerciser on all the resources. If you do not find a problem.

9. After the Diagnostics Operating Instructions display. Log a repair action for each replaced resource. 8. 5. have the system administrator enter superuser mode and then enter the diag command. If the resource associated with your action is not displayed on the Resource List. If available. 2. 7. 6. this changes the Fault Indicator LED from the ″fault″ state to the ″normal″ state. Note: See the hot-swap procedures in the ″Removal and Replacement″ section of your system unit’s service guide. Refer to the last character in the SRN. Select the Task Selection option. if the FRU you replaced contains resources that may be allocated to different partitions (for example. 4. 5. If you do not want to use the hot-swap. Note: On systems with a Fault Indicator LED. where the processors may be assigned to different partitions) you can also run exercisers on those other partitions containing these resources in addition to running them in the partition that reported the SRN. exchange one FRU at a time. use the CE Login and enter the diag command. For SRNs ending with any other character. 1. in the order listed. Note: If CE Login is not available. if the FRU is an MCM containing multiple processors. Select Run Exercisers and run the short exerciser on all resources. 3. or 7 indicates that all FRUs listed on the Problem Report Screen must be replaced. Select the Log Repair Action option. select sysplanar0. press Enter. Note: On a partitioned system. If the repair action was reseating a cable or adapter. If it is not displayed on the resource list. select the resource associated with your repair action. 10. Was a problem reported? NO YES The repair is completed. A 1.Step 0230-13 The FRUs can be hot-swapped. Use the Log Repair Action option in the Task Selection menu to update the AIX error log. Return the system to the customer. 3. select sysplanar0. go to “Step 0230-9” on page 85. 88 Diagnostic Information for Multiple Bus Systems . Go to “Step 0230-14” on page 89. Return to the Task Selection menu.

if the FRU is an MCM containing multiple processors. Remove the new FRU and install the original FRU. 3. Select Run Error Log Analysis and run analysis on all exchanged resources. Return to the Task Selection Menu. Call your support person for assistance. Was a problem reported? NO YES The repair is complete. 7. MAP 0230: Platform Error Problem Resolution 89 . 4. If the resource associated with your action is not displayed on the Resource List. Check for loose cards. where the processors may be assigned to different partitions) you can also run exercisers on those other partitions containing these resources in addition to running them in the partition that reported the SRN. If you do not find a problem. Select the Log Repair Action option. Note: On a partitioned system. Exchange the next FRU in the list. go to Chapter 4. 2. 10. “MAP 0020: Problem Determination Procedure” on page 29 and get a new SRN. Chapter 13. 8. Step 0230-16 1. Have you exchanged all the FRUs that were listed? NO YES Go to “Step 0230-16”. Return the system to the customer. Return to the Task Selection Menu. and obvious problems. Select Run Exercisers and run the short exercisers on all resources. if the FRU you replaced contains resources that may be allocated to different partitions (for example. 6. Log a repair action for each replaced resource. After the exercisers are complete. 5. select sysplanar0. cables. YES Step 0230-15 Look at the physical location codes and FRU part numbers you recorded. Go to “Step 0230-15”.Step 0230-14 Is the problem the same as the original problem? NO The symptom has changed. 9. Go to “Step 0230-14”. return to the Task Selection Menu. The SRN did not identify the failing FRU.

90 Diagnostic Information for Multiple Bus Systems .

Note: The following steps may require that the system be rebooted to invoke Array bit steering. Use the Log Repair Action option in the TASK SELECTION menu to update the AIX error log. Note: On systems with fault indicator LED. 91 . this changes the fault indicator LED from the FAULT state to the NORMAL state. at the AIX command line type diag then press enter. . Use the Log Repair Action option in the TASK SELECTION menu to update the AIX error log. Go to “Step 0235-2”. MAP 0235: System Array Self-Repair Problem Resolution Purpose of This MAP Use this MAP to resolve problems reported by SRNS A11-560 to A11-580.Chapter 14. this changes the fault indicator LED from the FAULT state to the NORMAL state. at the AIX command line type diag then press enter. Resolve those errors before proceeding. Were there any other errors on procx? NO YES Go to “Step 0235-4” on page 92. Select procx. Were there any other errors on the resource reporting the array bit steering problem? NO YES Go to “Step 0235-4” on page 92. where x is the processor number of the processor number of the processor that reported the error. Step 0235-1 Was the SRN A11-560? NO YES Go to “Step 0235-3”. Select sysplanar0. Step 0235-2 Logged in as root or using CE Login. Resolve those errors before proceeding. Step 0235-3 Logged in as root or using CE Login. Note: On systems with fault indicator LED. so you may wish to schedule deferred maintenance with the system administrator to arrange a convenient time to reboot their system.

reboot the system to invoke Array Bit steering Go to “Step 0235-5”. If diagnostics are not run (for instance. At the AIX command line. log in as root or use CE Login.Step 0235-4 Schedule deferred Maintenance with the customer. Step 0235-5 After the system has been rebooted. “MAP 0410: Repair Checkout” on page 119. Go to the Chapter 3. then array bit steering was able to correct the problem. if the system returns to Resource Selection menu after running diagnostics in problem determination mode) or there is no problem on the resource that originally reported the problem. “Fast Path MAP” on page 17 with this symptom. If a problem is reported. Exit this MAP and go to Chapter 22. When it is possible. run diagnostics in problem determination mode to determine if the array bit steering was able to correct the problem. use the SRN to resolve the problem. 92 Diagnostic Information for Multiple Bus Systems .

Step 0240-2 1. (other than memory modules) exchange the FRUs one at a time based on the order listed. Find the function codes in the “Failing Function Code List” on page 538 and record the part number and description for each FRU. and obvious problems. use that part number to exchange the FRU. perform the operating system’s shutdown procedure (get help if needed). go to the system unit’s service guide. 4. Record the SRN source code and the failing function codes in the order of their listing. 2. and then replace the next FRU listed when directed by the MAPs. replace all the listed memory modules simultaneously. If more than one memory module is listed. Turn off the system power. If the system displayed a FRU part number on the screen. 5. 3. Notes: 1. 2. Wait until the diagnostics are loaded or the system appears to stop. Exchange the first FRU listed. If an exchanged FRU does not fix the problem. If the SRN table lists multiple FRUs. find your SRN in the “Service Request Number List” on page 247. Go to “Step 0240-2”. MAP 0240: Memory Problem Resolution Purpose of This MAP This MAP handles memory problems. Turn off the system power. Load either the Online or Standalone Diagnostics in Service Mode (refer to the system’s service guide if needed). If the operating system is running. Step 0240-1 1. Go to “Step 0240-3” on page 94. Check for loose cards. If there was no FRU part number displayed on the screen.Chapter 15. 93 . cables. 2. 3. If you do not find a problem. Were you able to load the diagnostics? NO YES The symptom has changed. reinstall the original FRU.

Were you able to load the diagnostics? NO YES The symptom has changed. select the Advanced Diagnostics option. Go to “Step 0240-6” on page 95. turn off the system power. After performing a system shutdown. go to the system unit’s service guide. 3. 5. Check for loose cards. select the sysplanar0 option. Did the test pass? NO YES Go to “Step 0240-4”. 3. When the FUNCTION SELECTION menu is displayed. Wait until the diagnostics are loaded or the system appears to stop. cables. If more than one memory module is listed. This completes the repair. Turn on the system power. Step 0240-4 Have you exchanged all the FRUs that correspond to the failing function codes? NO YES Go to “Step 0240-5”. 2.Step 0240-3 1. If you do not find a problem. you are prompted to define it. 94 Diagnostic Information for Multiple Bus Systems . Remove the new FRU and install the original FRU. Go to “Step 0240-7” on page 95. You cannot continue until this is done. Go to Chapter 22. Press Enter. Step 0240-5 1. 6. When the DIAGNOSTIC MODE SELECTION menu is displayed. replace all of the memory modules simultaneously. 4. select Memory test. and obvious problems. “MAP 0410: Repair Checkout” on page 119. Note: If the terminal type is not defined. 4. select the System Verification option. If the ADVANCED DIAGNOSTIC SELECTION menu is displayed. 2. Load either the Online or Standalone Diagnostics in Service Mode (refer to the system unit’s service guide if needed). Exchange the next FRU in the list. If the RESOURCE SELECTION MENU is displayed.

Select the Advanced Diagnostics option. When the Function Selection menu is displayed. 5. 4. cables. Turn on the system power. Is the only FRU identified by this SRN a memory module? NO YES The SRN did not identify the failing FRU. 5. 3. Chapter 15. “MAP 0410: Repair Checkout” on page 119. This completes the repair. go to the system unit’s service guide. If the ADVANCED DIAGNOSTIC SELECTION menu is displayed. and repeat the steps. Press Enter. You cannot continue until this is done. If you do not find a problem. select Memory test. select the Advanced Diagnostics option. Go to “Step 0240-8”.Step 0240-6 1. select the sysplanar0 option. Check for loose cards. Step 0240-7 Look at the FRU descriptions you recorded for this SRN. If the RESOURCE SELECTION MENU is displayed. Exchange the planar or memory card that contains the memory module. When the DIAGNOSTIC MODE SELECTION menu displays. Go to Chapter 22. Load either the Online or Standalone Diagnostics in Service Mode (refer to the system unit’s service guide if needed). 2. 2. After performing a shutdown. MAP 0240: Memory Problem Resolution 95 . Did the test pass? NO YES Go to “Step 0240-4” on page 94. Were you able to load the diagnostics? NO YES The symptom has changed. Note: If the terminal type is not defined. you are prompted to define it. 3. and obvious problems. turn off the system power. Step 0240-8 1. 4. Wait until the diagnostics are loaded or the system appears to stop. Go to “Step 0240-9” on page 96. Call your support person. select the System Verification option.

select the sysplanar0 option. “MAP 0410: Repair Checkout” on page 119. select the System Verification option. Press Enter. If the RESOURCE SELECTION MENU is displayed. Call your support person. When the DIAGNOSTIC MODE SELECTION menu is displayed. you are prompted to define it. select Memory test.Step 0240-9 1. When the Function Selection menu is displayed. 3. Did the test pass? NO YES The SRN did not identify the failing FRU. If the ADVANCED DIAGNOSTIC SELECTION menu is displayed. Note: If the terminal type is not defined. 2. This completes the repair. select the Advanced Diagnostic option. 4. Go to Chapter 22. You cannot continue until this is done. 96 Diagnostic Information for Multiple Bus Systems .

2. Wait until the diagnostics are loaded or the system appears to stop. Go to “Step 0250-3”. 4. Were you able to identify a failing FRU? NO YES Contact your service support structure. Go to “Step 0250-1”. Go to “Step 0250-3”. 3. Record the FRU part number and description. Step 0250-3 1. Refer to “Failing Function Code List” on page 538 and find the failing function code that matches the last three digits of your SRN. Step 0250-1 The last three or four digits of the SRN following the dash (-) match a failing function code number.Chapter 16. Step 0250-2 One of the multiple FRUs of this kind is defective. Exchange the FRU identified in “Step 0250-2” or the FRU identified by the last three or four digits of the SRN following the dash (-). MAP 0250: Unexpected System Halts During Diagnostics Purpose of This MAP This MAP handles unexpected system halts that occur while running the diagnostic programs. When the test is successful or all FRUs of this kind have been removed. Load either the Online or Standalone Diagnostics in Service Mode (refer to the system unit’s service guide if needed). 97 . Test the system unit after each FRU is removed. Turn off the system unit power. Does this system unit contain only one of this kind of FRU? NO YES Go to “Step 0250-2”. Turn on the system power. 5. Remove this kind of FRU one at a time.

go to the system unit’s service guide. cables. select the Advanced Diagnostics option. Go to Chapter 22. Note: If the terminal type is not defined. Step 0250-4 1. “MAP 0410: Repair Checkout” on page 119. go to Chapter 4. you are prompted to define it. and obvious problems. Check for loose cards. YES Step 0250-5 Run diagnostics on the FRU that you exchanged. Press Enter. If you do not find a problem. You cannot continue until this is done. and obvious problems. This completes the repair. Go to “Step 0250-4”. If you do not find a problem. Go to “Step 0250-5”. “MAP 0020: Problem Determination Procedure” on page 29 and get a new SRN. Did the FRU pass the test? NO YES Contact your support person. 3. select the System Verification option. cables.Were you able to load the diagnostics? NO YES The symptom changed. 2. 98 Diagnostic Information for Multiple Bus Systems . When the FUNCTION SELECTION menu is displayed. When the DIAGNOSTIC MODE SELECTION menu is displayed. Check for loose cards. Did the ADVANCED DIAGNOSTIC SELECTION menu display? NO The symptom changed.

and go to“Step 0260-6” on page 100. Go to “Step 0260-2”. Step 0260-2 Are there any FRUs attached to the device described by the physical location code or AIX location code? No Yes Go to “Step 0260-6” on page 100 Go to “Step 0260-3” Step 0260-3 Remove this kind of FRU attached to the device described in the location code one at a time. or all attached FRUS have been removed from the adapter or device. or device name displays on system units with multiple-line LCD operator panel display if AIX 4. MAP 0260: System Hangs During Resource Configuration Purpose of This MAP This MAP handles problems when the system unit hangs while configuring a resource. Do you have either a physical location code or AIX location code displayed? NO YES Go to “Step 0260-4” on page 100. 99 . Do this until you no longer get a hang.Chapter 17. Record the FRU part number and description (use the first FRU part listed when multiple FRUs are listed).3. Step 0260-1 The last three or four digits of the SRN following the dash (-) match a failing function code number.3 or higher operating system is installed. AIX location code. Look at the “Failing Function Code List” on page 538 and find the failing function code that matches the last three or four digits of your SRN. Note whether the system still hangs after each device is removed. following the dash. Has the symptom changed? No Yes Go to “Step 0260-6” on page 100 Use the location code of the attached device that you removed when the symptom changed. The physical location code.

Exchange the FRU identified by the location code or “Step 0260-5”. Step 0260-8 1. refer to the Service Guide). Turn on the system unit. When the test completes successfully or when you have removed all of the FRUs of this kind. Wait until the Diagnostic Operating Instructions display or the system appears to have stopped. Turn off the system unit. Were you able to identify a failing FRU? NO YES Go to MAP 1540 in the service guide for this system unit. Go to “Step 0260-6”. 3. Step 0260-6 1. Wait until the Diagnostic Operating Instructions display or the system appears to have stopped. Load the Online Diagnostics in Service Mode (if needed. Step 0260-5 One of the FRUs of this kind is defective. Step 0260-7 1. “MAP 0410: Repair Checkout” on page 119. Turn on the system unit. refer to the Service Guide). Go to “Step 0260-6”. Is this system capable of running online diagnostics in Service Mode? NO YES Go to “Step 0260-7”. Remove this kind of FRU one at a time. Load the Standalone diagnostics (if needed. Are the DIAGNOSTIC OPERATING INSTRUCTIONS displayed? 100 Diagnostic Information for Multiple Bus Systems .Step 0260-4 Does your system unit contain only one of this kind of FRU? NO YES Go to “Step 0260-5”. 2. 2. Are the DIAGNOSTIC OPERATING INSTRUCTIONS displayed? NO YES Go to “Step 0260-9” on page 101. 2. Test the system unit after each FRU is removed. 3. Go to Chapter 22. Go to “Step 0260-8”.

Go to “Step 0260-10”. Load the Online Diagnostics in Service Mode (if needed. refer to the service guide). “MAP 0020: Problem Determination Procedure” on page 29 and get a new SRN. “MAP 0410: Repair Checkout” on page 119. 3. Step 0260-11 Was the FRU you exchanged a device? NO YES Go to MAP 1540 in the service guide for this system unit. Note: If the AIX operating system is not used on the system. 4. MAP 0260: System Hangs During Resource Configuration 101 . go to Chapter 4. YES Step 0260-10 Was the FRU you exchanged an adapter or a planar? NO YES Go to “Step 0260-11”. Turn off the system unit. Exchange the adapter for the device. start diagnostics from an alternate source. Turn on the system unit. If you do not find a problem. Wait until the DIAGNOSTIC OPERATING INSTRUCTIONS display or the system appears to have stopped. and obvious problems. Go to “Step 0260-12”. If c31 is displayed. Go to Chapter 22. Are the DIAGNOSTIC OPERATING INSTRUCTIONS displayed? NO YES Go to MAP 1540 in the service guide for this system unit.NO YES Go to “Step 0260-9”. Step 0260-12 The adapter for the device may be causing the problem. 2. 5. cables. 1. Check for loose cards. “MAP 0410: Repair Checkout” on page 119. Step 0260-9 Look at the operator panel display. Go to Chapter 22. follow the displayed instructions to select a console display. Chapter 17. Go to MAP 1540 in the service guide for this system unit. Is the number displayed the same as the last three or four digits after the dash (-) of your SRN? NO The symptom changed.

102 Diagnostic Information for Multiple Bus Systems .

2. Attention: If the FRU is a disk drive or an adapter. 103 . Step 0270-1 1. Record the SRN source code and the failing function codes in the order listed. use that part number. Cache. and record the FRU part number and description of each FRU. Note: This MAP assumes that the RAID adapter and drive microcode is at the correct level. To check microcode level. Go to “Step 0270-2”. MAP 0270: SCSI RAID Problem Resolution and Verification Purpose of This MAP Use this MAP to Resolve SCSI RAID Adapter. see “SCSI RAID Descriptions and Diagnostic Procedures” on page 162. or drive problems. ask the system administrator to perform any steps necessary to prepare the device for removal. If the system displayed a FRU part number on the screen. If there is no FRU part number displayed on the screen. refer to the SRN listing. Step 0270-2 Is the FRU a RAID drive? NO YES Go to “Step 0270-6” on page 107.Chapter 18. Find the failing function codes in the FFC listing. Go to “Step 0270-3” on page 104.

Verify that you are failing the correct drive by looking at the Channel ID row. Select the appropriate disk array by placing the cursor over that array and press Enter. A list of the physical disks in the system which may be removed will be displayed. Press Enter again. it is not a SPARE or FAILED 104 Diagnostic Information for Multiple Bus Systems . 6. 3.Step 0270-3 If the RAID drive you want to replace is not already in the failed state. the drive would not be listed as an IDENTIFY AND REMOVE RESOURCES selection within the RAID HOT PLUG DEVICES screen. Press F10 and type smit pdam 8. At the IDENTIFY AND REMOVE RESOURCES menu. then select COMMIT. Select ″Change/Show PCI SCSI RAID Drive Status -> Remove a Failed Drive 9. 6. If the physical disk you wish to remove is not listed. 5. Otherwise. Type smit pdam. as indicted by the LED on the drive. Choose the IDENTIFY option in the IDENTIFY AND REMOVE RESOURCES menu. 7. If the physical disk you wish to remove is listed. 2. The physical disk will go into the REMOVE state. 4. replace the RAID drive using the RAID HOT PLUG DEVICES service aid: Note: The drive you wish to replace must be either a SPARE or FAILED drive. Login as root. 3. indicated by a flashing light on the drive. 5. An example of this procedure is: 1. The disk will go into the IDENTIFY state. Select the RAID adapter that is connected to the RAID array containing the RAID drive you wish to remove. Select the physical disk which you wish to remove from the RAID array and press Enter. then press Enter. Select the appropriate drive to fail based on the Channel and ID called out in diagnostics. Press Enter when verified correct. Select Fail a Drive in a PCI SCSI Disk Array. 7. Select the drive that just failed. 1. 4. Go to “Step 0270-4”Step 270-4 Step 0270-4 Using the Hot Plug Task service aid described in “Hot Plug Task” on page 197. Select the RAID HOT PLUG DEVICES option within the HOT PLUG TASK under DIAGNOSTIC SERVICE AIDS. choose the REMOVE option and press Enter. Verify that it is the physical drive you wish to remove. The Fail a Drive screen will appear. then ask the customer to run the PCI SCSI Disk Array Manager using smit to fail the drive that you wish to replace. Refer them to the System Management Guide for more information. 2. In that case you must ask the customer to put the drive into FAILED state. select it and press Enter.

press Enter. Type smit pdam. 5. Allow 1-2 hours for completion. Press F3 until you are back at the Change/Show PCI SCSI RAID Drive Status screen. Login as root. Select Change/Show PCI SCSI RAID Drive Status. 3. 9. An example of this procedure is: 1. and will go to the NORMAL state once you exit diagnostics. Reconstruction time will vary based on the size of the RAID array. Refer the customer to the System Management Guide for more information. 2. Chapter 18. Select Add a Spare Drive. Go to “Step 0270-5” Step 0270-5 If the RAID did not begin reconstructing automatically. Refer to Service Guide for the system unit or enclosure that contains the physical drive for removal and replacement procedures for the following substeps: a. 6. b. The drive will exit the REMOVE state. 8. Press Enter when verified. Remove the old hot-plug RAID drive. Select the appropriate adapter. Choose the array containing the drive you replaced. Select Add a Hot Spare 10. If there was no hot spare previously installed in the array then the array will begin reconstructing immediately. Select the drive you just added as a spare. To check the progress of the reconstruction: 1. 11.drive. Ask the customer to put the drive in the FAILED state before you can proceed to remove it. 4. Install the new hot-plug RAID drive. 7. 8. Select List PCI SCSI RAID Arrays. Adding a Disk to the RAID array and Reconstructing: Ask the customer to run the PCI SCSI Disk Array Manager using smit. Once the hot-plug drive is in place. Type smit pdam. 3. then perform the steps that follow. 4. Login as root. Note: There are no elective tests to run on a RAID drive itself under diagnostics (the drives are tested by the RAID adapter). 2. MAP 0270: SCSI RAID Problem Resolution and Verification 105 . Select the Channel and ID of the drive which was replaced.

Go to “Step 0270-17” on page 111. Press F10 to exit.If the state of the RAID Array is reconstructing then it is in process of reconstructing. 5. then reconstruction has completed. If it is optimal. 106 Diagnostic Information for Multiple Bus Systems .

Chapter 18. or RAID adapter battery? NO YES Go to “Step 0270-15” on page 110. Go to “Step 0270-7” on page 108. MAP 0270: SCSI RAID Problem Resolution and Verification 107 . RAID adapter cache card.Step 0270-6 Is the FRU a RAID adapter base card.

Step 0270-10 After physically removing the base card from the system. Step 0270-11 Did you change the FRU using a hotplug operation? No Install the RAID adapter assembly into the system. remove any other good FRUs (RAID cache card or cache battery) from the RAID base card adapter. and remove the RAID adapter. Go to “Step 0270-8”. Yes Step 0270-12 Was the replacement FRU a RAID base card? No Yes NO Go to “Step 0270-14” on page 110. Go to “Step 0270-12”. Go to “Step 0270-11”. Go to “Step 0270-12”. Go to “Step 0270-13” on page 109 108 Diagnostic Information for Multiple Bus Systems . Plug these FRUs on to the replacement RAID base card adapter FRU. if necessary refer to the Removal and Replacement Procedures section of the system Service Guide. Remove the RAID adapter. Step 0270-9 Replace the FRU onto the existing base card. Go to “Step 0270-8”. Power up the system and login to AIX. If needed. Yes Step 0270-8 Is the FRU you want to replace a RAID adapter cache card or RAID adapter battery? NO YES Go to “Step 0270-10”. Install the RAID adapter assembly into the system.Step 0270-7 Do you want to change the FRU using a hotplug operation? No Power down the system. if necessary. Go to “Step 0270-11”. Go to “Step 0270-9”. refer to the Removal and Replacement Procedures section of the system Service Guide. refer to the Replacing a Hot-Pluggable PCI Adapter section within the Removal and Replacement Procedures section of the system Service Guide. if necessary refer to the Replacing a Hot-Pluggable PCI Adapter within the Removal and Replacement Procedures section of the system Service Guide.

If no RAID Arrays are listed. Login as root (if not already root). 3. The configuration on the new adapter should now match the configuration existent on the drives. Type smit pdam from the AIX Command prompt (if not already in the RAID manager) 3. 5. 1. 4. Press F10 to exit You may now proceed to cable up the RAID system array. The replacement base card can overwrite your system’s configuration data if it already has a configuration written to it! Check it before cabling up the SCSI RAID Subsystem Array. Select the adapter which you just installed. Select Recovery Options 4. Type smit pdam. Press Enter to confirm. Chapter 18. Ask to customer to check for pre-existing configuration on the SCSI RAID Base Card. Press F10 key to exit If a pre-existing configuration exists on the base card.Step 0270-13 Warning: Prior to cabling the SCSI RAID adapter to the subsystem check for pre-existing configurations on the replacement SCSI RAID Base Card. 2. Login as root (if not already root) 2. Return to the Recovery Options menu (if not already there). ask the customer to run the PCI SCSI Disk Array Manager using smitty. Press Enter″ to confirm. then there are no preexisting configurations on the base card. 5. Select the adapter which you just installed. Select Clear PCI SCSI RAID Adapter Configuration. MAP 0270: SCSI RAID Problem Resolution and Verification 109 . 6. Go to “Step 0270-16” on page 110. Select List PCI SCSI RAID Arrays. Below is an example of this procedure: 1. Select Resolve PCI SCSI RAID Adapter Configuration. Select Accept Configuration on Drives.

Below is an example of this procedure: 1. Log in as root (if not already root). Step 0270-16 Run the diagnostics in system verification mode on the RAID subsystem. Go to “Step 0270-16”. Turn off the system power. Press F10 to exit. Did the diagnostics run with no trouble found? No Yes Go to “Step 0270-18” on page 111 Go to “Step 0270-17” on page 111 110 Diagnostic Information for Multiple Bus Systems . Go to “Step 0270-16”. A message will be displayed as to the success of the operation. perform the operating system shutdown procedure (get help if needed). 2. 4. Select Retry Current Configuration. 5.Step 0270-14 Ask the customer to resynchronize the RAID Array configuration. Select Recovery Options. If the operating system is running. 8. Step 0270-15 Other RAID FRUs require that the system be shut down prior to replacement. Replace the FRU indicated by the FFC. 3. 1. 3. 7. Type smit pdam. 2. 6. Select Resolve PCI SCSI RAID Adapter Configuration. Select the appropriate scraid adapter.

remove the FRU you just replaced and install the original FRU in it’s place. While in diagnostics.Step 0270-17 1. Select the Advanced Diagnostics Routines option. Use the Log Repair Action option in the TASK SELECTION menu to update the AIX error log. Run the diagnostic test on scraidX (where X is the RAID adapter number) Did the diagnostics run with no trouble found? NO YES Go to the “Step 0270-18” If you changed the Service Processor or Network settings. This completes the repair. Schedule a time to run diagnostics in service mode. 2. The SRN did not identify the failing FRU. Use the next FRU on the list and Go to “Step 0270-2” on page 103. MAP 0270: SCSI RAID Problem Resolution and Verification 111 . select the System Verification option. Select scraidX (where X is the RAID adapter number of the RAID subsystem you’ve been working on). Step 0270-19 Note: Note: Before proceeding. “MAP 0030: Additional Problem Determination” on page 45. go to the FUNCTION SELECTION menu. If the system you are servicing has a hardware management console (HMC) with service focal point (SFP) go to the End of Call MAP for systems with Service Focal Point in the system Service Guide. When the DIAGNOSTIC MODE SELECTION menu displays. Step 0270-18 Have you exchanged all the FRUs that correspond to the failing function codes? NO YES Go to “Step 0270-19”. go to Chapter 6. If the same SRN is reported in service mode. this changes the Fault Indicator LED from the Fault state to the Normal state. Chapter 18. return the system to the customer. Note: On systems with Fault Indicator LED. 3. restore the settings to the value they had prior to servicing the system.

112 Diagnostic Information for Multiple Bus Systems .

3. Go to “Step 0280-3” on page 114.) 1. follow the procedures in the system guide to resolve the problem. “MAP 0410: Repair Checkout” on page 119. “MAP 0030: Additional Problem Determination” on page 45. suspect the display or display cable. Keyboard cable (if not included with the keyboard) Were you able to resolve the problem? No Yes Go to Chapter 6. Try the FRUs in the order listed below: (Test each FRU by retrying the failing operation. If you do not find a problem.Chapter 19. Go to Chapter 22. Keyboard adapter (normally located on the system board) 3. Some systems have a graphic adapter POST. Step 0280-2 1. go to the display problem determination procedures. “MAP 0410: Repair Checkout” on page 119. If the system does not have a graphic adapter POST. Check your system guide for information about graphic adapter POSTs. 2. Go to “Step 0280-2”. Keyboard 2. If a graphic adapter POST is supported and it does not indicate a failure. Go to Chapter 22. Step 0280-1 The system fails to respond to keyboard entries. replace the graphics adapter. “MAP 0030: Additional Problem Determination” on page 45. 113 . MAP 0280: Boot Problem Resolution Purpose of This MAP Use this MAP to handle problems caused during booting of the system unit. If a graphic adapter POST is supported and it indicates a failure. or keyboard cable. keyboard adapter. Entry Table Entry 1 Entry 2 Entry 3 Go to “Step 0280-1”. Were you able to resolve the problem? No Yes Go to Chapter 6. This problem is most likely caused by a faulty keyboard.

suspect the serial port adapter or terminal cable. 114 Diagnostic Information for Multiple Bus Systems .Step 0280-3 Go to the problem determination procedure for the terminal. “MAP 0410: Repair Checkout” on page 119. Go to Chapter 22. Were you able to resolve the problem? No Yes Call your support person. If you do not find a problem.

Go to “Step 0290-2”. 3. 4. Supplemental diskettes may be required for specific adapters and devices if service aids are run from Standalone Diagnostics. Step 0290-2 Is the undetected resource a SCSI device installed in an externally attached enclosure for a SCSI device(s)? NO YES Go to “Step 0290-4”. cabling. first use the parent device as the missing resource when going through this MAP. Return to this step after you check the device. use the children when going through this MAP. and check the device(s) for proper power. based on user input. Did you find a problem? NO YES Go to “Step 0290-4”. If the problem with the parent device is resolved so that it is no longer missing. “MAP 0410: Repair Checkout” on page 119. Go to “Step 0290-5” on page 116. MAP 0290: Missing Resource Problem Resolution Purpose of This MAP Use this MAP to handle problems when a resource is not detected by the diagnostics. Step 0290-1 Use the “Display Configuration and Resource List” on page 186 to display the resources that were sensed by the configuration program when the diagnostic programs were loaded. The ISA Adapter Configuration Service Aid in Standalone Diagnostics allows the identification and configuration of ISA adapters. ISA adapters cannot be detected by the system. Correct the problem. 2. Step 0290-4 Are you running Standalone Diagnostics? NO YES Go to “Step 0290-7” on page 116. Notes: 1. fans running. Go to “Step 0290-3”. If a parent device and all of its children are the missing resources at the same time. and any other checks available.Chapter 20. then go to Chapter 22. Step 0290-3 Go to the documentation for SCSI devices installed in an externally attached enclosure for a SCSI device(s). but any of its children are still missing. 115 . A resource’s software must be installed on the AIX operating system before a resource can be detected by the Online Diagnostics.

Exchange the backplane then go to “Step 0290-9”. If a problem is found. Note: Before exchanging the backplane check that all cables connected to the backplane are properly seated and that all cables and connectors are in good working condition. “MAP 0030: Additional Problem Determination” on page 45.Step 0290-5 Are multiple devices missing that are connected to the same adapter? (If the adapter itself is also missing. Is the resource listed? NO YES Go to Chapter 6. then use the list of resources in the DIAGNOSTIC SELECTION to determine if devices that were previously missing now appear on the resource list. Step 0290-9 Load the standalone diagnostics. correct it. Step 0290-6 Did the diagnostics detect a problem with the adapter? NO YES Go to “Step 0290-8”. Exchange the undetected resource. answer ″No″ to this question. Step 0290-7 Take the following steps: 1. 2. Step 0290-8 Are the missing devices attached to a backplane? NO YES Go to “Step 0290-7”. and then go to Chapter 22. Run diagnostics on the device adapter then go to “Step 0290-6”. Go to Chapter 22. “MAP 0410: Repair Checkout” on page 119. Use the “Display Configuration and Resource List” on page 186 to display the resources sensed by the configuration program. “MAP 0410: Repair Checkout” on page 119. “MAP 0410: Repair Checkout” on page 119. Are the previously missing devices now listed on the resource list? NO YES Go to “Step 0290-7”. Record the SRN then find the SRN in the SRN List and do the listed action. 116 Diagnostic Information for Multiple Bus Systems . Suspect a problem with the device adapter. Go to Chapter 22.) NO YES Go to “Step 0290-7”.

If the missing device is located in a drawer or enclosure. Power problems can sometimes be identified by checking other devices that use the same power source (such as a diskette drive and a SCSI tape drive. Check for any environmental problem indicators such as power or cooling that may indicate a problem. refer to the system or enclosure documentation to resolve the problem. Correct the problem. (if needed. determine the cable numbering. “MAP 0410: Repair Checkout” on page 119. Step 0291-2 Inspect the cables (signal and power) of the missing device. If there is a power problem. MAP 0291: Missing Device or Bus Problem Resolution Purpose of This MAP Use this MAP when a bus or device (such as a disk drive) is reported as a missing resource by the diagnostics. suspect the power source as the problem. then go to Chapter 22. and check for a problem-determination procedure. Be sure all connections are in place and power is present.) 2. even though they have different controllers). 117 . Look for obvious power cabling problems. If a problem is indicated. such as missing or loose cable connectors. Did you find a problem? NO YES Go to “Step 0291-3” on page 118. Refer to the system or enclosure documentation containing the power wiring diagram or system cable diagram to locate specific cables. If other devices that share a power source are reported as missing devices. follow the service documentation to resolve the problem. do the following: 1. Go to “Step 0291-2”. Step 0291-1 The device may be missing because of a power problem. refer to the service documentation.Chapter 21.

Step 0291-3 Is the missing device a SCSI device installed in a SCSI Enclosure Services (AIX resource SESx) or SAF-TE (AIX resource SAFTEx device? NO YES Go to “Step 0210-1” on page 67. “Using the SRN List” on page 243. Note: If the SRN is not listed a Service Request Number Lists. 2. v The Service Hints service aid in Chapter 26. Find the SRN in Chapter 29. Did you get a different SRN than when you ran the diagnostics previously? NO YES Go to “Step 0210-1” on page 67. 118 Diagnostic Information for Multiple Bus Systems . Note: A no trouble found result from the diagnostics indicates that you did not get a different SRN. Perform the action listed. Step 0291-4 Run the Advanced Diagnostics in Problem Determination mode on the SCSI Enclosure Services or SAF-TE device. Take the following action: 1. “Using Standalone and Online Diagnostics” on page 145. look for additional information in the following: v Any supplemental service manual for the device. Go to “Step 0291-4”. v The diagnostic Problem Report screen.

and any other FRUs that were removed during problem analysis. Note: Only use Standalone Diagnostics for repair checkout when no other diagnostics are available on the system. Go to “Step 0410-6” on page 120.Chapter 22. cables. go to the End of Call MAP in the Clustered Eserver Installation and Service Guide. go to the End of Call MAP in the SP System Service Guide. Standalone Diagnostics do not log repair actions. or any other FRUs that were removed during problem analysis that you want to put back into the system? NO YES Go to “Step 0410-4” on page 120. The system time and date information should also be set when the repair is completed. adapters. After performing a system shutdown. If you are servicing a clustered Eserver. Step 0410-1 Did you use a hot-swap operation to change the FRU? NO YES Go to “Step 0410-2”. Do you have cards. cables. turn off the system power and unplug all power cords (cables) from electrical outlets. MAP 0410: Repair Checkout Purpose of This MAP This MAP is used to check out the system after a repair is completed. Go to “Step 0410-4” on page 120. Step 0410-3 1. devices. Step 0410-2 Note: If the system planar or battery has been replaced and you are loading diagnostics from a server over a network. Install all of the cards. If you are servicing an SP system. it may be necessary for the customer to set the network boot information for this system before diagnostics can be loaded. 2. 119 . adapters. devices. Go to “Step 0410-3”.

2. suspect a loose card or connection. Go to “Step 0410-5”. do a normal boot. and reboot the system or partition that contains the FRU. Otherwise. Step 0410-5 1. no resources were detected as missing. 4. 3. Enter the diag -a command and check for missing resources. Step 0410-8 If the Resource Repair Action menu is already displayed. Press Enter. Power on the system. Step 0410-7 Exit service mode diagnostics. If no instructions display. If the system supports Slow boot (See “About Slow Boot” on page 2) do a slow boot on the system.Step 0410-4 Do you want to run the concurrent diagnostics? NO YES Go to “Step 0410-9” on page 121. Follow any instructions that display. 5. “MAP 0020: Problem Determination Procedure” on page 29. Did the AIX login prompt display? NO YES Go to Chapter 4. 3. Step 0410-6 Is the system or partition containing the FRU running service mode diagnostics? NO YES Go to “Step 0410-8”. ask the customer to enter the password) or use the CE login. “MAP 0020: Problem Determination Procedure” on page 29. Did the AIX Login Prompt display? NO YES Go to Chapter 4. Go to “Step 0410-8”. Wait until the AIX operating system login prompt displays or until apparent system activity on the operator panel or display has stopped. If the system does not support slow boot. Go to “Step 0410-8”. Select the Advanced Diagnostics option. 2. Log into the operating system either with root authority (if needed. Wait for the operating system login prompt or until the activity on the operator panel or display stops. Enter the diag command. do the following: 1. go to “Step 0410-15” on page 123. 120 Diagnostic Information for Multiple Bus Systems . If an SRN displays. Go to “Step 0410-7”.

Step 0410-9 Note: If you are uncertain. select System Verification. 5. 7. You cannot continue until this is done. Are the Online Diagnostics Installed on the system? NO YES If the operating system is running. Go to “Step 0410-17” on page 124. Power on the system (if it is not already powered on). Step 0410-11 1. When the DIAGNOSTIC MODE SELECTION menu displays. Did the RESOURCE REPAIR ACTION menu (801015) display? NO YES Go to “Step 0410-14” on page 123. test the FRUs you exchanged by selecting the diagnostics for the individual FRUs. If the resource associated with your action is not displayed on the Resource List. choose System Verification. Chapter 22. “MAP 0020: Problem Determination Procedure” on page 29. Note: If the terminal type is not defined. MAP 0410: Repair Checkout 121 . Go to “Step 0410-10”. Load the Standalone diagnostics. 4. select the All Resources option or test the FRUs you exchanged by selecting the diagnostics for the individual FRU(s). When the DIAGNOSTIC MODE SELECTION menu displays. When the ADVANCED DIAGNOSTIC SELECTION menu displays. do the Shutdown Procedure to stop it (get help if needed). Step 0410-10 1. 3. 2. Go to Chapter 4. no trouble was found menu (801010) display? NO YES There is still a problem. Go to “Step 0410-11”. Press Enter. Wait until the diagnostics are loaded or the system appears to stop. You are prompted to define it. answer Yes to the following question. On the DIAGNOSTIC SELECTION menu. Select the Advanced Diagnostics option. 3. select planar0. Wait until the Diagnostic Operating Instructions display or the system appears to stop. Did the TESTING COMPLETE.6. Go to “Step 0410-15” on page 123. 2. Load the Online Diagnostics in Service Mode (refer to the system unit’s service guide if needed).

“MAP 0020: Problem Determination Procedure” on page 29. Select the Log Repair option. select sysplanar0. Press Enter. Press the key for the previous menu two times to get to the Function Selection menu. Select the resource associated with the repair action. 3.Are the Diagnostic Operating Instructions Displayed? NO YES Go to Chapter 4. 7. Note: If the resource associated with your action is not displayed on the Resource List. Go to “Step 0410-13”. 4. “MAP 0020: Problem Determination Procedure” on page 29. Step 0410-13 Test the FRUs you exchanged by selecting the individual FRUs. 5. 8. Go to “Step 0410-15” on page 123. Select the Advanced Diagnostics Routines option. select the resource associated with that repair action. Press commit after you have made your selection. If the DIAGNOSTIC MODE SELECTION menu displays. Go to “Step 0410-12”. 122 Diagnostic Information for Multiple Bus Systems . select sysplanar0. 6. Is the ADVANCED DIAGNOSTIC SELECTION menu displayed? NO YES Go to Step 1 of Chapter 4. Step 0410-12 1. Did the RESOURCE REPAIR ACTION menu (801015) display? NO YES Go to “Step 0410-14” on page 123. 2. select the System Verification option. Select the Task Selection option. If the repair action was reseating a cable or adapter. You cannot continue until this is done. You are prompted to define it. If the resource associated with your repair action is not displayed on the Resource List. Note: If the terminal type is not defined.

if not previously logged. this changes the Fault Indicator LED from the Fault state to the Normal state. Go to “Step 0410-17” on page 124 Step 0410-15 When a test is run on a resource in System Verification mode. the RESOURCE REPAIR ACTION menu displays.Step 0410-14 Did the TESTING COMPLETE. in the TASK SELECTION menu to update the AIX Error Log. If the repair action was reseating a cable or adapter. Go to “Step 0410-16”. select sysplanar0. After replacing a FRU. Note: On systems with a Fault Indicator LED. If the resource associated with your action is not displayed on the Resource List. Select the resource that has been replaced from the RESOURCE REPAIR ACTION menu. If the repair action was reseating a cable or adapter. Use the Log Repair Action option. Step 0410-16 The parent of the resource you just replaced may also require that you run the RESOURCE REPAIR ACTION service aid on it. 2. MAP 0410: Repair Checkout 123 . select sysplanar0. no trouble was found menu (801010) display? NO YES There is still a problem. you must select the resource for that FRU from the RESOURCE REPAIR ACTION menu. Go to Chapter 4. Press Commit after you make your selections. If the resource associated with your action is not displayed on the Resource List. Note: On systems with a Fault Indicator LED. this changes the Fault Indicator LED from the Fault state to the Normal state. Do the following: 1. select the resource associated with that repair action. go to “Step 0410-17” on page 124. This updates the AIX error log to indicate that a system-detectable FRU has been replaced. and that resource has an entry in the AIX error log. select the resource associated with that repair action. if the test on the resource was successful. “MAP 0020: Problem Determination Procedure” on page 29. Chapter 22. Did another Resource Repair Action (801015) display? NO YES If the No Trouble Found menu displays.

Press COMMIT after you make your selections. 4. press Enter to continue. select the adapter that you changed. On the PCI SCSI Disk Array Manager screen. On the Resolve PCI SCSI RAID Adapter Configuration screen. select Recovery Options. 124 Diagnostic Information for Multiple Bus Systems . select the resource associated with that repair action. 2. This updates the AIX error log to indicate that a system-detectable FRU has been replaced. You should get an OK status message when the recovery is complete. When recovery is complete. 3. perform the following: 1. exit smitty to return to the AIX command line. 5. Press F3. and that resource has an entry in the AIX error log. 8. select sysplanar0. After replacing that FRU. 6. At the AIX command line. restore the settings to the value they had prior to servicing the system. press Enter. Select Clear PCI SCSI RAID Adapter Configuration. select Resolve PCI SCSI RAID Adapter Configuration. When you get the Are You Sure selection menu. 7. Select the parent of the resource that has been replaced from the RESOURCE REPAIR ACTION menu. Do the following: 1. verify that you selected the correct adapter. On the Recovery Options screen. type smitty pdam. Go to step “Step 0410-18” on page 125. as instructed in previous MAPs. 9. the RESOURCE REPAIR ACTION menu displays. Step 0410-17 If you changed the Service Processor or Network settings. On the PCI SCSI RAID Adapter selection menu. this changes the Fault Indicator LED from the FAULT state to the NORMAL state. Note: On systems with a Fault Indicator LED. if the test on the resource was successful. 3. If you performed service on a RAID subsystem involving changing of the RAID adapter cache card or changing the configuration on RAID disks. If the resource associated with your action is not displayed on the Resource List. 2. If a previous configuration exists on the replacement adapter. ask the customer to run the PCI SCSI Disk Array Manager using smitty. this must be cleared. Use the Recovery Options selection to resolve the RAID configuration. go to “Step 0410-17”. On the next screen. If you get a Failed status message. you must select the resource for that FRU from the RESOURCE REPAIR ACTION menu. If the repair action was reseating a cable or adapter. select Accept Configuration on Drives. To do this.When a test is run on a resource in System Verification mode. then repeat this procedure again. If the No Trouble Found menu displays.

Step 0410-18 If the system you are servicing has a Hardware Management Console (HMC). return the system to the customer. MAP 0410: Repair Checkout 125 . Chapter 22. with Service Focal Point (SFP) go to the ″End of call MAP for Systems with Service Focal Point″ in the system service guide This completes the repair.

126 Diagnostic Information for Multiple Bus Systems .

look through the list of resources to make sure that all adapters and SCSI devices are listed including any new resources. b. resources assigned to other partitions are displayed on the resource list. you are prompted to define it. 2. Resources attached to serial and parallel ports may not appear in the resource list. 3. perform the operating system’s shutdown procedure (get help if needed). You cannot continue until this is done.Chapter 23. MAP 0420: System Checkout Purpose of This MAP Use this MAP to verify that the system is working correctly. 2. 4. Press Enter. On the DIAGNOSTIC SELECTION or ADVANCED DIAGNOSTIC SELECTION menu. The ISA Adapter Configuration Service Aid in Standalone Diagnostics allows the identification and configuration of ISA adapters. Go to the system unit’s service guide. Go to “Step 0420-5” on page 128 127 . Notes: a. ISA adapters cannot be detected by the system. c. Load either the Online or Standalone Diagnostics in Service Mode (refer to the system unit’s service guide if necessary). 3. Did you find all the adapters or devices on the list? No Yes Go to “Step 0420-3” on page 128. Power off the system. Step 0420-2 1. Go to “Step 0420-2”. If running diagnostics in a partition within a partitioned system. select the System Verification option. Step 0420-1 1. select Advanced Diagnostics. Note: If the terminal type is not defined. Were you able to load the diagnostics? NO YES There is a problem. Wait until the diagnostics are loaded or the system appears to stop. Power on the system. When the FUNCTION SELECTION menu displays. 4. If the operating system is running. When the DIAGNOSTIC MODE SELECTION menu displays. 5.

This completes the system checkout. Step 0420-5 1. 128 Diagnostic Information for Multiple Bus Systems . If it works in that location. Go to Chapter 4. suspect that the location where it failed to appear has a defective slot. If you are still unable to detect the device or adapter. suspect a bad replacement adapter or device. try installing it in an alternate location if one is available. If it works in that location. “MAP 0020: Problem Determination Procedure” on page 29. If the MISSING RESOURCE menu is displayed. If you are still unable to detect the device or adapter. If the ADVANCED DIAGNOSTIC SELECTION menu displays. contact your service support structure. follow the instructions. schedule time to replace the hardware that supports that slot. contact your service support structure. The replacement device or adapter may be defective. The replacement device or adapter may be defective. try installing it in an alternate location if one is available. If possible. If it does not work in an alternate location. schedule time to replace the hardware that supports that slot. If possible. select the All Resources option to test the system or select each test you want to run. If it does not work in an alternate location. suspect that the location where it failed to appear has a defective slot.Step 0420-3 Is the new device or adapter an exact replacement for a previous one installed at same location? No Yes Go to “Step 0420-4”. 2. then use the All Resources option to test the system or select the individual tests you want to run. select the System Verification option. Did the test pass? NO YES There is a problem. Step 0420-4 Is the operating system software to support this new adapter or device installed? No Yes Load the operating system software. The MISSING RESOURCE menu only displays when a resource was removed or moved. suspect a bad replacement adapter or device. If the RESOURCE SELECTION menu is displayed.

check the TTY Terminal Attributes again. Be sure the system unit power switch is set to Off. Visually check the system unit and attached devices to ensure that: v All power cables are securely attached to the system unit or devices v All signal cables are connected at both ends v All power cables are plugged into the customer’s outlet v All covers are installed and the vent openings are not obstructed v All ribbons. Doing a Visual Check Perform the following actions after initial system installation or system alteration: 1. Step 2.Chapter 24. Checking the TTY Terminal Attributes Checking the TTY Terminal Attributes usually needs to be accomplished only during the initial installation. 2. and check the terminal attributes. guides. Installation Checkout Procedure To start the checkout. When you run the diagnostic programs from an attached TTY terminal. Installation Checkout The installation checkout is used by the service representative to verify system quality after initial installation or after an MES or EC has been installed. Be sure the power switches on all of the attached devices are set to Off. and other attachments are in place. Doing a Visual Check”. Are you going to run this procedure on an attached TTY terminal? NO YES Go to “Step 3. Checking the TTY Terminal Attributes”. 129 . Step 1. The TTY terminal must be attached to the S1 serial port on the system unit. Go to “Running the Diagnostics from a TTY Terminal” on page 151. go to “Step 1. 4. Go to “Step 2. Loading the Diagnostics” on page 130. If you have trouble selecting the console display and you are using an attached terminal. Return to Step 3 when you finish checking the attributes. the attributes for the terminal must be set to match the defaults of the diagnostic programs. 3.

c. If the AIX operating system is installed. Check for loose cables or cards. go to Chapter 4. a problem was detected. or press 6 on a TTY console. Set the power switch on the system unit to On. “MAP 0020: Problem Determination Procedure” on page 29. you can check by turning the system unit on. the AIX operating system is not installed. Did the DIAGNOSTIC OPERATING INSTRUCTIONS display? NO YES Go to Chapter 4. When the diagnostic programs load correctly. Insert the diagnostic CD-ROM disc into the CD-ROM drive. Checking for the Correct Resources” on page 131. If the System Management Service menu displays. Power off the system unit. Note: After the first icon displays on the system console. b. The following procedure attempts to load the diagnostics from a disk or from a server. diagnostics can be loaded from the diagnostic CD-ROM disc. 2. If the AIX operating system is not installed. Go to “Step 4. Note: After the first icon displays on the system console. If you do not find a problem. the AIX operating system is not installed. 3. If the System Management Services menu displays. Set the power switches on all of the attached devices to On. Do the following: a. Loading the Diagnostics The diagnostics can be run from a CD-ROM disc. If they cannot be loaded from a disk or server. the diagnostic CD-ROM disc is used to load and run the checkout. the DIAGNOSTIC OPERATING INSTRUCTIONS display. 130 Diagnostic Information for Multiple Bus Systems . or press 6 on a TTY console. from a locally attached disk. If you are not sure whether the AIX operating system is installed. the diagnostic programs load from a locally attached disk or from a server. wait 45 seconds and then power on the system unit. press F6 if you are using a directly attached console. If the system stops with an eight-digit error code displayed or stops with an icon or icons displayed.Step 3. 1. “MAP 0020: Problem Determination Procedure” on page 29. or from a server if the AIX operating system is installed on the system. 4. press F6 if you are using a directly attached console.

Chapter 24. Select Advanced Diagnostics on the FUNCTION SELECTION menu. it must be defined before you can select the service aids. Completing the Installation” on page 132. If the Dials and LPFK are attached to serial ports S1 or S2. Use the Initialize Terminal option on the FUNCTION SELECTION menu to define the terminal. adapters. Checking the Hardware If you are running Online diagnostics from a disk. “MAP 0020: Problem Determination Procedure” on page 29. go to Chapter 4. 2. “Fast Path MAP” on page 17. If you do not find a problem. Go to “Step 5. they are not listed by the service aid unless they have been configured by the user. 3. All resources can be checked out by selecting System Verification option on the ADVANCED DIAGNOSTIC SELECTION menu. or you can select each resource individually. 2. Were all the resources listed by the service aid? NO YES Check for loose cables or cards. Checking the Hardware”. and input devices). Installation Checkout 131 . the system can be checked by one of the following methods. Check each resource.Step 4. Did all of resources check out good? NO YES Record the SRN. If the terminal type has not been defined. Notes: 1. then select the All Resources option. Checking for the Correct Resources Use the Display or Change System Configuration or VPD service aid to check the resources that are present (memory. SCSI devices. then go to Chapter 3. Step 5. Select System Verification on the DIAGNOSTIC MODE SELECTION menu. Go to “Step 6. disk drives. diskette drives. Refer to the AIX operating system documentation to configure these devices. depending on the version of the diagnostic programs you are using: 1.

1. Microcode must be installed during system installation or after the AIX operating system is installed. The microcode for these adapters must be installed before the adapters can be used. If needed. v Machine History card for each system unit and device. Contact the person that is going to install the software or turn the system over to the customer. The X. the microcode for them is normally not shipped with the AIX operating system. 3. If present. 2. Give the keys to the customer and explain the importance of keeping the reorder tag for the keys in a safe place. If you have the X. Microcode is shipped on microcode diskettes. If the system is using another type of operating system. Completing the Installation Some of the following steps only apply to an initial installation. The adfutil -m (command and flag) is normally used to install microcode shipped on option diskettes.25 Interface Coprocessor. If the system is using the AIX operating system. For the AIX operating system. runtime microcode maintenance can be selected from the SMIT INSTALLATION AND MAINTENANCE MENU or from the Diagnostic Service Aid.25 Interface Coprocessor microcode is shipped on an option diskette. that operating system should include microcode installation instructions. go to the AIX operating system Installation Kit to install and configure the AIX operating system. option diskettes and on the boot disk. all microcode is preinstalled on the boot disk for all adapters and devices that were shipped with the system. and store it in the binder with the operator guides. Keep a copy of the following: v SCSI Address Record from Appendix A of the User’s Guide.Step 6. These steps are provided as reminders in completing the installation or finishing an MES or EC activity. remove the CD-ROM diagnostic disc from the appropriate drive. 132 Diagnostic Information for Multiple Bus Systems .

Chapter 25. The first type of microcode is written on the disk before the original or replacement disk drive is shipped. General Diagnostic Information Information in this section is common to all system units. The second type of microcode is stored on the disk by the operating system during installation of the operating system. the installp and adfutil commands are used to load any microcode not shipped on the disk with the AIX operating system. Microcode There are two types of hardware microcode used in system units. Use the “Download Microcode” on page 192 to load this type of microcode from diskettes to disk. The CD-ROM diagnostic disc contain all of the required microcode for diagnostic purposes. This type of microcode only needs updating when there is an applicable Engineering Change (EC) or Miscellaneous Equipment Specification (MES). All of the microcode stored on the disk for use with the AIX operating system is in either the /etc/microcode or the /usr/lib/microcode directory. Any service information or diagnostic procedure that is specific to a certain system unit or device is in the operator guide or service guide for that system unit or device. This type of microcode loads to the adapter during the system IPL and must be installed before the diagnostics can be run from disk. The first type is the microcode stored on disk and used by the built-in disk drive controller. 133 . If you want to run the diagnostic programs in a language other than English you must install on the system the AIX operating system message locale fileset for the desired language you want displayed. The second type is the microcode used by an adapter. If you are using the AIX operating system. refer to the documentation for that operating system to install microcode. If you are using another operating system. AIX Operating System Message Files English is the default language displayed by the diagnostic programs when run from disk.

lp0 is normally the printer attached to the parallel port. If this file is not the same as the CEREADME file on the disk. Also. choose the appropriate section below and follow the steps listed. Printing the CEREADME File from CD-ROM Insert the diagnostic CD-ROM disc into the CD-ROM drive. a copy of this file should be printed and stored with the Service Information. the message /tmp/diag: not found displays. The file can be printed on a system when the AIX operating system is running in a normal user environment. To determine if this directory already exists. The procedure involves copying the file from the diagnostic media to a temporary file on disk. 134 Diagnostic Information for Multiple Bus Systems . and then deleting the file from disk.CEREADME File A CEREADME (CE read me) file is available on all diagnostic media. which is the printer normally attached to the parallel port. the command for printing the file is as follows: cat /usr/lpp/diagnostics/CEREADME > /dev/lp0 Printing the CEREADME File from a Source other than Disk The CEREADME file cannot be printed while diagnostics are being executed from a source other than from the disk. If a printer is attached to the parallel port and is considered as lp0. The CEREADME file can be copied or printed using the normal commands. enter: cd /tmp/diag If the directory does not exist. For information about using the service hints. refer to “Display Service Hints” on page 189. To print the CEREADME file. you can read the file directly from the disk using the AIX pg command to display /usr/lpp/diagnostics/CEREADME. printing the file. The path to this file is as follows: /usr/lpp/diagnostics/CEREADME A copy of this file should be printed and stored with the Service Information. Check for directory /tmp/diag. Do not attempt to print the CEREADME file if this message is not displayed. Printing the CEREADME File from Disk You can print the CEREADME file from disk using the cat command. This file contains diagnostic and system unit errata not covered in the publications. and then enter the following commands: mkdir /tmp/diag mount -o ro -v cdrfs /dev/cd0 /tmp/diag cd /tmp/diag/usr/lpp/diagnostics cat CEREADME > /dev/lp0 cd /tmp unmount /dev/cd0 The CEREADME file prints on lp0. You can view the CEREADME file by using the Service Hints service aid after the diagnostics are loaded.

ask the customer to create a unique user name and configure these characteristics for that name. These programs test the central electronics complex. (Refer to the Users and Groups section of the AIX 5L Version 5. v Run all the operating system commands run by system group users. If a test stops. the indicator for that test remains displayed to identify the unsuccessful test. format. v Use of shutdown and reboot operations. v Configure and unconfigure devices that are not busy. The POST also checks the memory. you will need to obtain the user name and password from the customer to log in with these capabilities. Power-On Self-Test The Power-On Self-Test (POST) programs check the devices needed to accomplish an initial program load.) After this is set up. Built-In Self-Test Note: This set of programs is not supported on all system units. and so forth. The automatic diagnostic tests display event indicators to track test progress. The recommended CE login user name is qserv. To use CE login. The Built-In Self-Test (BIST) programs run first after the system unit is turned on. certify. General Diagnostic Information 135 . In addition. such as hot plug tasks.1 System Management Guide: Operating System and Devices.CE Login CE login enables a user to perform operating system commands that are required to service the system without being logged in as a root user. This enables the user to: v Run the diagnostics including the service aids. and the direct memory access (DMA) handler. Chapter 25. common interrupt handler. Automatic Diagnostic Tests All automatic diagnostic tests run after the system unit is turned on and before the AIX operating system is loaded. and portions of the central electronics complex. CE login can have shutdown group enabled to allow: v Use of the Update System Microcode service aid. CE login must have a role of RunDiagnostics and a primary group of system.

which must be run to analyze the POST results. 136 Diagnostic Information for Multiple Bus Systems . If POST finds enough good memory. adapters. they are monitored for correct operation by various checkers such as Checkstop or Machine Check. the memory problems are logged and the system continues to boot. they are reported by the Base System or Memory Diagnostics. The Dials and Lighted Program Function Keys (LPFKs) can be tested from Online Diagnostics after they are manually configured. Refer to Chapter 28. and devices are present on the system. CPU and Memory Testing and Error Log Analysis Except for the floating-point tests. however. all CPU and memory testing on the system units are done by POST and BIST. The POST provides an error-free memory MAP. If one of these checks intermittently occurs. No other device attached to the serial and parallel ports is supported by the diagnostics. Normally. The CPU and memory cannot be tested after the AIX based diagnostics are loaded. Memory is tested entirely by the POST. If POST cannot find enough good memory to boot. “Diagnostics Numbers and Location Codes” on page 217 for a listing of program actions associated with displayed numbers. most memory problems that are detected by the POST are isolated to a single FRU. The configuration program displays numbers between 500 and 999 in the operator panel display. The configuration program. Single-bit memory errors are corrected by ECC (Error Checking and Correction) on systems equipped with ECC memory. Devices attached to serial and parallel ports are not configured. it is logged into the error log. which is part of the AIX operating system. it halts and displays an error message. builds a configuration list that is used by the diagnostic programs to control which tests are run during system checkout. If any memory errors were logged.Configuration Program The configuration program determines what features.

Chapter 25.Diagnostic Programs This section provides overview of the various diagnostic programs. the Diagnostic Selection menu is displayed. select the device or adapter from the Diagnostic Selection menu. The resource name identifies the resource that detected the error. the diagnostic programs read and analyze the contents of the error log. The diagnostic controller then loads the diagnostic application program for the selected device or adapter. Diagnostic Controller The diagnostic controller runs as an application program on the AIX operating system. General Diagnostic Information 137 . This menu allows you to select a resource for testing. The amount of testing that the diagnostic application does depends on the mode (service. If there are no recent errors logged or the diagnostic application program runs without detecting an error. The diagnostic controller checks the results of the tests done by the diagnostic application and determines the action needed to continue the testing. When you select the Problem Determination option. The diagnostic controller carries out the following functions: v Displays diagnostic menus v Checks availability of needed resources v Checks error log entries under certain conditions v Loads diagnostic application programs v Loads task and service aid programs v Displays test results To test an adapter or device. Error Log Analysis When you select Diagnostics or Advanced Diagnostics. This menu allows you to select the purpose for running diagnostics. If the error log contains recent errors (approximately the last 7 days). Note: Most hardware errors in the operating system error log contain sysplanar0 as the resource name. or concurrent) under which the diagnostic programs are running. Use the resource name to determine the appropriate diagnostic to analyze the error. the Diagnostic Selection menu displays (other menus may display before this menu). The diagnostic application program loads and runs test units to check the functions of the device or adapter. maintenance. the diagnostic programs automatically select the diagnostic application program to test the logged function. it does not indicate that the resource is faulty or should be replaced.

the diagnostic controller tests a sibling device on the same controller to determine if the drive or the controller is failing. “Introduction to Tasks and Service Aids” on page 169 for information and procedures about tasks and service aids. if the test of a disk drive detects a problem. For example.If an error is detected while the diagnostic application program is running. Enhanced FRU Isolation The diagnostics provide enhanced Field Replaceable Unit (FRU) isolation by automatically selecting associated resources. Advanced Diagnostics Function The advanced diagnostics function is normally used by a service representative. The advanced diagnostics provide additional testing by allowing the service representative to do the following: v Use wrap plugs for testing. check media. Tasks and service aids provide a means to display data. and check functions without being directed by the hardware problem determination procedure. v Loop on a test (not available in concurrent mode) and display the results of the testing. Note: After a FRU is replaced based on an error log analysis program. Task and Service Aid Functions If a device does not show in the Test List or you think a device’s Diagnostic Package is not loaded. These diagnostics may ask you to disconnect a cable and install a wrap plug. Diagnostics begin with that same type of selection. the A PROBLEM WAS DETECTED screen displays a Service Request Number (SRN). run the errclear command from the command line. the Diagnostic Package for the device is not loaded or is not available. If the device has an asterisk (*) preceding its name. This extra FRU isolation is apparent when you test a resource and notice that the diagnostic controller continues to test another resource that you did not select. Refer to Chapter 27. The typical way in which diagnostics select a resource is to present a list of system resources. Fill out the appropriate menu items. and you are then asked to select one. or use System Management Interface Tool (SMIT) to select Problem Determination / Error Log / Clear the Error Log. 138 Diagnostic Information for Multiple Bus Systems . To accomplish this task. If the device you want to test has a plus (+) sign or a minus (-) sign preceding its name. The advanced diagnostics run in the same modes as the diagnostics used for normal hardware problem determination. the Diagnostic Package is loaded. the error log entries for the problem device must be removed or the program may continue to indicate a problem with the device. the diagnostic controller checks for an associated resource. check by using the Display Configuration and Resource List task. If the diagnostic application for the selected resource detects a problem with that resource.

These tests run without interaction. The notification is a message to the system console and either the Service Focal Point for systems with a HMC.m. Periodic Diagnostic Reminders Periodic Diagnostics issues a reminder about detectable deconfigured resources when the system boot completes. The diagnostics are invoked using the diag -c -d Device command. Periodic Diagnostics Periodic testing of the processors are enabled by default. Adding or removing a resource from the periodic test list enables or disables the weekly reminder for deconfigured resources. The weekly reminder is issued every Tuesday at 8 a. Periodic diagnostics are controlled by the Periodic Diagnostic Service Aid. The resources in the periodic test list are tested for deconfigured resources. The battery test does test the real time clock and NV-RAM battery. The sysplanar0 resource looks for resources deconfigured at boot-time. The disk diagnostics test any disk drives that are not in use and perform disk error-log analysis on all disks. Problems are reported by a message to the system console and logged in the error log. or to all system groups. If the resource cannot be tested because it is busy. Chapter 25. error log analysis is performed if supported on the resource.System Checkout The system checkout program uses the configuration list generated by the configuration procedure to determine which devices and features to test. The Periodic Diagnostic Service Aid allows a hardware resource to be tested once a day. Currently the detectable deconfigured resources are processors and memory. select All Resources on the Resource Selection menu. The reminder is also issued weekly as long as the resources remain deconfigured. Diagnostics must be run for an SRN to be reported. Run-time deconfigurations are checked by the diagnostics for the individual resources in the resource list. To use system checkout. General Diagnostic Information 139 .

by enabling the diagela program on all platforms. The diagela program determines if the error should be analyzed by the diagnostics. The message contains the SRN. Running diagnostics in this mode is similar to using the diag -c -e -d Device command. and DType are blank. a diagnostic application is invoked and the error is analyzed. and DType with specifics causes the customer_notify_program to be invoked only for that device type. If the error should be analyzed. No testing is done if the diagnostics determine that the error requires a service action. Filling in the DClass. After the above stanza is added to the ODM data base. then the customer_notify_program applies for all devices. or in addition to sending the message to the Service Focal Point when there is a HMC: PDiagAtt: DClass = " " DSClass = " " DType = " " attribute = "diag_notify" value = "/usr/bin/customer_notify_ program $1 $2 $3 $4 $5" rep = "s" If DClass.Automatic Error Log Analysis (diagela) Automatic Error Log Analysis (diagela) provides the capability to perform error log analysis when a permanent hardware error is logged. The following keyword is expanded automatically as arguments to the notify program: v $1 the keyword diag_notify v $2 the resource name that reported the problem v $3 the Service Request Number v $4 the device type v $5 the error label from the error log entry 140 Diagnostic Information for Multiple Bus Systems . problems are displayed on the system console and the program specified in the value field of the diag_notify predefined attribute is invoked. DSClass. Notification can also be customized by adding a stanza to the PDiagAtt object class. DSClass. or to all system groups. Instead it sends a message to your console. The following example illustrates how a customer’s program can be invoked in place of the normal mail message. and either the Service Focal Point for systems with a HMC.

v $4 the device type v $5 the keywords: – no_trouble_found if the analyzer was run. then the customer_analyzer_program applies for all devices. but no trouble was found.In the case where no diagnostic program is found to analyze the error log entry. and DType with specifics causes the customer_analyzer_program to be invoked only for that device type. – no_analyzer if the analyzer is not available. the program specified is invoked if there is no diagnostic program specified for the error. After the above stanza is added to the ODM data base. and DType are blank. This is accomplished by adding a stanza to the PDiagAtt object class with an attribute = diag_analyze. the keyword PERIODIC if from Periodic Diagnostics. log in as root user (or use CE login) and type the following command: /usr/lpp/diagnostics/bin/diagela DISABLE The diagela program can also be enabled and disabled using the Periodic Diagnostic Service Aid. Chapter 25. but no error found. or if analysis was done. DSClass. or the keyword REMINDER if from a Diagnostic Reminder. Filling in the DClass. log in as root user (or use CE login) and type the following command: /usr/lpp/diagnostics/bin/diagela ENABLE To disable the Automatic Error Log Analysis feature. a separate program can be specified to be invoked. or analysis is done but no error was reported. The following keywords expand automatically as arguments to the analyzer program: v $1 the keyword diag_analyze v $2 the resource name that reported the problem v $3 the error label from the error log entry if from ELA. The following example illustrates how a customer’s program can be invoked for this condition: PDiagAtt: DClass = " " DSClass = " " DType= " " attribute = "diag_anaylze" value = "/usr/bin/customer_analyzer_program $1 $2 $3 $4 $5" rep = "s" If DClass. DSClass. To activate the Automatic Error log Analysis feature. General Diagnostic Information 141 .

System Fault Indicator and System Identify Indicator Some systems support the System Identify Indicator and/or the System Fault Indicator. 142 Diagnostic Information for Multiple Bus Systems . Replaced resources can be selected from the list. Both of these indicator functions can be managed by using the System Identify Indicator and System Fault Indicator Tasks. The default time for error log analysis is seven days. This is done by using the Log Repair Action task. See “System Fault Indicator” on page 210 or “System Identify Indicator” on page 211 for additional information. the indicator is set to Fault condition when a fault is detected. Note: This action keeps the System Fault Indicator from being set to the Fault state due to a previous error. The Log Repair Action task lists all resources. and when commit (F7 key) is selected. see “Log Repair Action”. The System Fault Indicator is used to help physically identify a particular system that has a fault condition. To prevent false problems from being reported when error log analysis is run. A repair action can be logged by using the Log Repair Action task or by running advanced diagnostics in System Verification mode. in the error log.Log Repair Action The diagnostics perform error log analysis on most resources. a repair action is logged for each selected resource. The System Identify Indicator is used to help physically identify a particular system in a room. repair actions need to be logged whenever a FRU is replaced. the system fault indicator should be set back to Normal. this time can be changed from 1 to 60 days using the Display or Change Diagnostic Run Time Options task. For additional information. however. After the problem with the system is fixed. On a system that supports System Fault Indicator. that has already been serviced.

Only those printers that are in the available state can be used (for example. If you close the virtual console window on the managed system. Array Bit Steering An advanced feature of many systems is Array Bit Steering.Testing the Line Printer The following is a simple procedure for determining if a printer attached to your system is responding correctly. In the case of a fault detected during run time. the output of the S1 serial port is redirected. the recoverable fault is reported with a ″Repair Disposition Pending Reboot″ indicator set. then the FRU with that array is replaced. the output of any command is directed from the S1 serial port to the virtual console terminal. you must substitute for x the value obtained from the lsdev command. The implication of this is that the serial port wrap diagnostics may fail with a false SRN if the virtual console window on the managed system is not closed. those printers marked as defined cannot be used). enter the following: cat /usr/lpp/diagnostics/CEREADME > /dev/lpx Note: In the above step. To determine what printers are available. The AIX operating system should be up and running in your normal environment. The processors in these systems have internal cache arrays with extra memory capacity that can be configured to correct certain types of array faults. the contents of the CEREADME file will print. General Diagnostic Information 143 . When the S1 serial port is wrapped. Ensure that a printer is actually connected at the location that was specified in the output of the command. In the above example. enter the following: lsdev -C -c printer This command displays a list of printers currently defined on the system. This allows diagnostics to call out a Service Request Number that identifies the array and directs the Service Representative to a MAP for problem resolution that uses array bit steering. Running Diagnostics on the Native Serial Port on a Full Machine Partition with a HMC Attached For a Full Machine Partition. If the array bit steering cannot be used for the reported fault. Another method to prevent the false SRN is to unplug the HMC from its port before running the wrap tests. normal function is restored to the S1 serial port. This reconfiguration can be used to correct arrays for faults detected at IPL or run time. Chapter 25. To begin printing. or wrapped to the virtual console window.

if you get an SRN involving an EEH error. Not all systems support EEH. 144 Diagnostic Information for Multiple Bus Systems . follow the action listed. make sure that the S1 serial port is enabled for login (AIX command chdev -l ’tty’x -a login=’enable’ where x is the tty number corresponding to the S1 serial port). Enhanced I/O Error Handling Enhanced I/O Error Handling (EEH) is an error recovery strategy for errors that can occur during I/O operations on the PCI bus.After running diagnostics on the serial port.

unless otherwise directed. be sure you isolate this system unit before stopping the operating system or running diagnostic programs. the device does not appear in the resource list when running diagnostics unless the supplemental media has been processed. Standalone and Online Diagnostics Operating Considerations Consider the following items before you use the diagnostics: v Standalone diagnostics can run on systems configured for running either a full machine partition or one or more logical partitions. They have access to the AIX Error Log and the AIX Configuration Data. v Run Online Diagnostics in Service Mode when possible. Attention: The AIX operating system must be installed in order to run Online Diagnostics. If you move devices. Online Diagnostics. that device does not appear in the resource list. they have no access to the AIX Error Log or the AIX Configuration Data. Using Standalone and Online Diagnostics The diagnostics consist of Standalone Diagnostics and Online Diagnostics. reboot both partitions. see “Standalone Diagnostic Operation” on page 155. you should run diagnostics in the partition containing the resource that you wish to test. This may require moving the device from the partition that currently contains the boot device (for example. v When running Online Diagnostics. or run concurrently (called concurrent mode) with other applications. compared to Standalone Diagnostics. The Online Diagnostics perform additional functions. Some system-cabling changes (such as installing wrap plugs or removing a device from the configuration) may require action by the operator of the attached system before making the cabling changes on this system. diagnostics only works with the resources that were assigned to that partition. CD-ROM or network adapter connected to the NIM server that has a standalone diagnostic image) to the partition used to run standalone diagnostics. If the AIX operating system is not installed. If this is the case. If booted. v When running Standalone Diagnostics. run in maintenance mode (called maintenance mode). For more information. when installed.Chapter 26. are resident with AIX on the disk or server. If this is the case. The AIX error log and certain SMIT functions are only available when diagnostics are run from the disk drive. use the standalone diagnostic procedures. They can be booted in single user mode (called service mode). the device from which you are booting standalone diagnostics must be made available to the partition dedicated to running standalone diagnostics. device support for some devices may not have been installed. 145 . The Standalone Diagnostics must be booted before they are run. Attention: If this system unit is attached to another system. When running on a logically partitioned system. device support for some devices may be contained on supplemental diagnostic media. v When running diagnostics on an LPAR partition.

On systems with an HMC. Selecting a Console Display When you run Standalone Diagnostics and under some conditions. you must identify what type of terminal you are using. Resetting the Terminal If the user enters a terminal type that is valid (according to the DEFINE TERMINAL option menu) but is not the correct type for the ASCII terminal being used. v The diagnostic CD-ROM disc cannot be ejected from the CD-ROM drive once the diagnostic programs load.v Support for some TTY terminals is optionally installed. Running Standalone Diagnostics from CD-ROM Consider the following when you run Standalone Diagnostics: v The diagnostic CD-ROM disc must remain in the CD-ROM drive for the entire time that diagnostics are running. you may be unable to read the screen. On an LPAR system. Undefined Terminal Types If you specify an undefined terminal type from the DEFINE TERMINAL option menu. use the function keys or use the Enter key. diagnostics displays on the virtual terminal associated with a given partition. Select LFT for adapter-attached displays. the menu prompts the user to enter a valid terminal type. The screen display which results from this resetting action varies with the mode which the system is being run: v Online Normal or Maintenance Mode . the diagnostics do not allow you to continue until a terminal is selected from the DEFINE TERMINAL option menu. select VT100 when prompted for the type of terminal emulation. The diagnostic CD-ROM disc can only be ejected after the 146 Diagnostic Information for Multiple Bus Systems . If running diagnostics from a virtual terminal on a system with an HMC. If the terminal type is not known when the FUNCTION SELECTION menu is displayed. v Standalone Mode or Online Service Mode . you must select the console display. Online Diagnostics. Identifying the Terminal Type to the Diagnostics Programs Note: This is a different function from selecting a console display. These difficulties can be bypassed by pressing Ctrl-C to reset the terminal. the Diagnostic Operating Instruction panel displays. diagnostics displays on the virtual terminal on the HMC. If you attach a TTY terminal to a system to run diagnostics. The menu is displayed until either a valid type is entered or the user exits the DEFINE TERMINAL option. it might not work correctly because the AIX support for the terminal might not be installed. The diagnostics display instructions on any graphics display and the terminal attached to the S1 serial port. and the user is required to go through the DEFINE TERMINAL process again.The command prompt appears.The terminal type is reset to dumb. When you run diagnostics.

3.rte (Where SPOTNAME is the name of the SPOT from which you want to do a NIM boot (for example. This allows the system to boot up in Standalone Chapter 26. the support code for these adapters must be loaded into the directory pointed to by the NIM SPOT from which you wish to boot that client. the NIM server system administrator must ensure that any needed support for these devices is loaded on the server. is capable of booting Standalone Diagnostics from the NIM server if the client system is registered on the NIM server.diag. Before running standalone diagnostics on these clients from the NIM server. Using Standalone and Online Diagnostics 147 . SPOT433). is 64 MB. The amount of system memory required to run Standalone Diagnostics from a NIM server using the bos. 4. run the following AIX command at the NIM server (you must have root authority): nim -o showres SPOTNAME | grep bos. The diagnostic CD-ROM disc must be ejected before attempts to load the diagnostic programs again. For NIM clients that have adapters that would normally require that supplemental media be loaded when standalone diagnostics are run from CD-ROM.3.diag. If you replace the network adapter in the client. v The CD-ROM drive from which diagnostics were loaded cannot be tested. 2. Running Standalone Diagnostics from a Network Installation Management (NIM) Server A client system connected to a network with a Network Installation Management (NIM) server.25. All operations to configure the NIM server require root authority. 5.rte fileset at level 4.system has been powered off and then powered on (Standalone mode). and the NIM boot settings on both the NIM server and the client system are correct. v Use the following AIX command: lsattr -E -l mem0 3. v Use the Config option under System Management Services (see the system unit service guide). The Control state (Cstate) for standalone clients on the NIM server should be kept in the Diagnostic Boot has been Enabled state. Use one of the following methods to determine the amount of available system memory: v Run the Display Resource Attributes task for resource. or after the diagnostics program has terminated (Online concurrent mode). 6. Notes: 1. v The SCSI adapter (or circuitry) controlling the CD-ROM drive from which diagnostics were loaded cannot be tested. To determine the fileset level. the NIM server network adapter should be put in the bootlist after the boot disk drive. the network adapter hardware address for the client must be updated on the NIM server. On the client system.

Diagnostics from the NIM server should there be a problem booting from the disk drive. and the partition ill be rebooted. Note: If the client system is registered on the NIM server but Cstate has not been enabled. NIM Server Configuration Refer to the Network Installation Management Guide and Reference for information on doing the following: v Register a client on the NIM server. The client system is registered on the NIM server but not enabled to run standalone diagnostics from the NIM server. Stop all programs. restart the AIX operating system in the partition you wish to run online diagnostics. Note: The ClientName is the name of the system on which you are wanting to run the Standalone Diagnostics. turn on the system unit power. v Enable a client to run diagnostics from the NIM server. 2. run the following command: lsnim -a Cstate -Z ClientName Refer to the following table for system responses. do the following: 1. System Response #name:Cstate: ClientName: diagnostic boot has been enabled: #name:Cstate: ClientName:ready for a NIM operation: or #name:Cstate: ClientName:BOS installation has been enabled: 0042-053 lsnim: there is no NIM object named "ClientName" Client Status The client system is registered on the NIM server and enabled to run diagnostics from the NIM server. Verify with the system administrator and system users using that partition that all applications on that partition must be stopped. 3. The client is not registered on the NIM server. 4. Remove all removable media (tape or CD-ROM disc). Stop all programs including the operating system (refer to the operating system documentation). If you are running standalone diagnostics in a full machine partition. Stop all programs on that partition including the operating system. from the command line on the NIM server. 148 Diagnostic Information for Multiple Bus Systems . no data will be returned. If the system is running on a logically partitioned system. including the AIX operating system (get help if needed). Client Configuration and Booting Standalone Diagnostics from the NIM Server To run Standalone Diagnostics on a client system from the NIM server. If the system is running in a full machine partition. Refer to the ″Multiboot″ section under SMS chapter in the service guide for the client system to obtain information about setting the bootlist. verify with the system administrator and system users that the system unit may be shutdown. To verify that the client system is registered on the NIM server and diagnostic boot is enabled.

0. Chapter 26. either ask the system network administrator or compare the first 3 octets of the NIM server address and the client address. the client is prepared to boot from the NIM server. gateway address (if applicable). select Multiboot or Select Boot Devices.) 5. When the keyboard indicator displays (the word keyboard on an ASCII terminal or the Keyboard icon on a graphical display). Enter any requested passwords. Depending on the console type. Under the Ping utility. 10. Change the bootlist so the network adapter attached to the NIM server is first in the bootlist. Using Standalone and Online Diagnostics 149 . press the number 1 key on the keyboard to display the SMS menu. If they are the same. Depending on the console type. Use the following procedure to temporarily changes the system bootlist so that the network adapter attached to the NIM server network. select Set Address or IP Parameters. 11. Note: If the ping fails.126.0.42. 8. To determine if there is a gateway. Then follow the steps for network boot problems. then set the gateway address in the RIPL field to 0.0. If the NIM server is setup to allow the pinging of the client system. Note: RIPL is located under the Utility menu in System Management Services (SMS) and should be referred to for information on setting these parameters. 9. 4.126. use the ping option in the RIPL utility to verify that the client system can ping the NIM server. 6.0. Enter the client address. Follow the instructions on the screen to select the system console. 3.3. select Boot Sequence or Select Boot Devices. server address. Depending on the console type. Exit completely from SMS.126) are the same). the first 3 octets (9. (for example. 2. select RIPL or Remote Initial Program Load Setup. 7.16 and the client address is 9. If there is no gateway between the NIM server and the client. choose the network adapter that provides the attachment to the NIM server to do the ping operation. If the ping comes back with an OK prompt.5.0. set the gateway address to 0.3. 6. Select Utilities. Exit to the SMS Main screen. is first in the bootlist: 1. If ping returns with a FAILED prompt. (You will have to set the bootlist back to the original settings after running diagnostics from the NIM server.0. refer to ″Boot Problems/Concerns″ in the service guide for the system unit. Depending on the console type. and subnet mask into the Remote Initial Program Load (RIPL). if the NIM server address is 9. the client does not proceed with the boot. The system should start loading packets while doing a bootp from the network. Record the current bootlist settings.3.

If you continue to have problems. Standalone Diagnostics did not load. the Electronic Service Agent is already locked out.lck is listed. reboot the system and use SMS to change the bootlist sequence back to the original settings.lck file was created (if the file is present the Electronic Service Agent is locked out): /usr/lpp/servdir/servdir.lck Use the following command to check that the servdir. Then follow the steps for network boot problems. Use the following commands to lock out the Electronic Service Agent: cd /usr/lpp/servdir ls /usr/lpp/servdir/servdir. Locking and Unlocking the Service Agent If the system is setup with a service agent.x is displays. 150 Diagnostic Information for Multiple Bus Systems . use the following command to create the file: /usr/lpp/servdir/servdir.lck If the file is listed. be sure to unlock the service agent to allow it to report problems. If it is not listed. Check the following items: v The bootlist on the client might be incorrect.lck file was deleted (the file should not be present): ls /usr/lpp/servdir/servdir. v Cstate on the NIM server might be incorrect.lck Use the following command to check that the servdir. Locking and Unlocking the Electronic Service Agent If the system is setup with a Electronic Service Agent.If Diagnostics Operating Instructions Version x. After running diagnostics. you must lock out the service agent before running diagnostics. you must lock out the Electronic Service Agent before running diagnostics. refer to ″Boot Problems/Concerns″ in the service guide for the system unit.lck If a file named servdir. When you complete your service action.x. Verify the settings and the status of the network.analyze reset rm /usr/lpp/servdir/servdir. v There might be network problems preventing you from connecting to the NIM server. If the AIX login prompt displays.lck Use the following commands to unlock the Electronic Service Agent: /usr/lpp/servdir/servdir. the Electronic Service Agent is still locked out. Standalone Diagnostics has loaded successfully. Note: The system does not report problems while the service agent is locked out. This prevents the Electronic Service Agent from using the diagnostics while you are running them.

then click Lock. and click Unlock. Follow the instructions to select a console display. When the system is set up to IPL from a server. Use the following procedure to unlock the service agent: 1. Click the Administration folder. v When the system is running in a full machine partition. if the diagnostics were loaded from disk or a server. or the server has not been setup to send a service mode IPL of the diagnostics. The system you unlocked should not have a red X displayed. you must shut down the AIX operating system before powering off the system unit to prevent possible damage to disk data. indicating it is locked out. The system you locked out should have a red X displayed. – If the diagnostic programs were loaded in maintenance or concurrent mode. form number GA18-2633. After the installation of the AIX operating system. Click the Padlock icon to display the lockout status. In the Detail screen. For the 3164. press the F3 key until DIAGNOSTIC OPERATING INSTRUCTIONS displays. select the system you want to unlock.Use the following procedure to lock out the service agent: 1. To verify that the system is locked out. select the system you want to lock out. click the Network folder. v Under some conditions the system may stop. 3. Running Online Diagnostics Consider the following when you run the Online Diagnostics from a server or a disk: v The diagnostics cannot be loaded and run from a disk until the AIX operating system has been installed and configured. all three modes of operation are available. v The diagnostics cannot be loaded on a system (client) from a server if that system is not set up to IPL from a server over a network. enter the shutdown -F command. To verify that the system is unlocked. the diagnostics are executed in the same manner as they are from disk. 5. 2. Click the Padlock icon to display the lockout status. refer to the 3164 ASCII Color Display Station Description. Chapter 26. In the Detail screen. 3. For the 3151. Running the Diagnostics from a TTY Terminal Consider the following when you run diagnostics using a TTY-type terminal as the console display: v See the operator manual for your type of TTY terminal to find the key sequences you need to respond to the diagnostics. form number GA18-2617. 5. Select the Lockout Machines option. then follow the displayed instructions to shut down the AIX operating system. 2. 4. Click the Administration folder. Select the Lockout Machines option. 4. refer to the 3151 ASCII Display Station Guide to Operations. click the Network folder. Using Standalone and Online Diagnostics 151 . with instructions displayed on attached displays and terminals. This is done in one of two ways: – If the diagnostic programs were loaded in Standalone mode.

This mode also requires that no other programs be running on the system. Online Diagnostics Mode of Operation The Online diagnostics can be run in three modes: v Service Mode allows checking of most system resources. “General Attributes Required When Using a TTY Terminal” on page 633. If the system is running in a full machine partition. and the disk drives used for paging can be tested. and CD-ROM discs. If the system is running on a logically partitioned system. These attributes are set as if the diagnostics were using a 3161 display terminal. 3161 or 3164 attached to the S1 serial port. restart the AIX operating system in the partition you wish to run online diagnostics. diskettes. Stop all programs including the AIX operating system (get help if needed). press F6 on the directly-attached keyboard or 6 on the TTY keyboard to indicate that diagnostics are to load. After the first POST indicator appears on the system unit’s console. 7. After the diagnostic controller loads. Error log analysis is done in service mode when you select the Problem Determination option on the DIAGNOSTIC MODE SELECTION menu. your terminal may have different names for the attributes. turn on the system unit power. and use the attribute descriptions to determine the settings for your terminal. the system memory and the processor are only tested during power-on self-test (POST). Follow any instructions to select a console. v If you have a TTY terminal other than a 3151. 152 Diagnostic Information for Multiple Bus Systems . Enter any requested password. All supported system resources except the SCSI adapter. 4. use the following steps: 1. v Maintenance Mode allows checking of most system resources Running the Online Diagnostics in Service Mode (Service Mode IPL) Service mode provides the most complete checkout of the system resources. 3. Remove all tapes. 6. 8. If the system is running in a full machine partition. However. To run the Online diagnostics in service mode. Refer to the tables in Appendix D. DIAGNOSTIC OPERATING INSTRUCTIONS appear on the console display.v When the diagnostics present display information through the S1 serial port. Refer to the tables in Appendix D. “General Attributes Required When Using a TTY Terminal” on page 633 for a list of attributes for the 3161 ASCII Display Terminal and for two other ASCII display terminals commonly used with the system. turn off the system unit power. 2. certain attributes are used. Note: The term POST indicator refers to the icons (graphic display) or device mnemonics (ASCII terminal) that are displayed while the POST is running. 5. v Concurrent Mode allows the normal system functions to continue while selected resources are being checked.

Running the Online Diagnostics in Concurrent Mode Use Concurrent mode to run Online diagnostics on some of the system resources while the system is running normal system activity. Error log analysis is done in concurrent mode when you select the Problem Determination option on the DIAGNOSTIC MODE SELECTION menu. v The full-test level requires the device not be assigned to or used by any other operation. Three levels of testing exist in concurrent mode: v The share-test level tests a resource while the resource is being shared by programs running in the normal operation. Using Standalone and Online Diagnostics 153 . Chapter 26. For undefined terminals. this test could test one port of a multiport device while the other ports are being used in normal operation. When testing is complete. get help). use the F3 key to return to the DIAGNOSTIC OPERATING INSTRUCTIONS. CDE. pressing 99 produces a full screen menu which offers two options: continuing with the shutdown by pressing 99 and then Enter. 11. the following resources cannot be tested in concurrent mode: v SCSI adapters connected to paging devices v Disk drive used for paging v Any graphics-related device running X. or windowing environment v Memory v Processor. or returning to diagnostics by pressing Enter. To run the Online diagnostics in concurrent mode you must be logged onto the AIX operating system and have proper authority to issue the commands (if needed. Because the system is running in normal operation.9. 10. For example. Follow the displayed instructions to test the desired resources. This testing is mostly limited to normal commands that test for the presence of a device or adapter. or returning to diagnostics by pressing Enter. The diagnostics display menus to allow you to vary off the needed resource. v The sub-test level tests a portion of a resource while the remaining part of the resource is being used in normal operation. Press the F3 key (from a defined terminal) or press 99 (for an undefined terminal) to shut down the diagnostics before turning off the system unit (if running in a full machine partition) or rebooting the partition (if running one or more logical partitions). Note: Pressing the F3 key (from a defined terminal) produces a Confirm Exit menu which offers two options: continuing with the shut down by pressing F3. This level of testing on a disk drive might require the use of the varyoff command.

Error log analysis is done in maintenance mode when you select the Problem Determination option on the DIAGNOSTIC MODE SELECTION menu. Stop all programs except the AIX operating system (get help if needed). The diag command is then used to invoke the diagnostic controller so you can run the diagnostics. memory. Press Ctrl-D to log off from root or superuser. To run the Online diagnostics in maintenance mode. All of the system resources except the SCSI adapters. use the following steps: v Log on to the AIX operating system as root or use CE login. The shutdown -m command is used to stop all activity on the AIX operating system and put the operating system into maintenance mode. follow the instructions to test the desired resources. 7. v Enter the diag command. When testing is complete. v Press the Ctrl-D key sequence to log off from root or superuser. follow the normal diagnostic instructions. Log in to the AIX operating system as root or superuser. After the diagnostic controller is loaded. Enter the shutdown -m command. 5. Press the F3 key again to return to the operating system prompt. 4. Running the Online Diagnostics in Maintenance Mode Maintenance mode runs the Online diagnostics using the customer’s version of the AIX operating system. and the disk drive used for paging can be checked. When a message indicates the system is in maintenance mode. To run Online diagnostics in concurrent mode. v When testing is complete. use the F3 key to return to the DIAGNOSTIC OPERATING INSTRUCTIONS. 3.The diag command loads the diagnostic controller and displays the Online diagnostic menus. 2. Note: It may be necessary to set TERM type again. you must be logged in to the customer’s version of the AIX operating system as root or superuser and use the shutdown -m and diag commands. processor. follow the displayed instructions to test the desired resources. This mode requires that all activity on the operating system be stopped so the Online diagnostics have most of the resources available to check. Then press the F3 key again to return to the AIX operating system prompt. enter the diag command. 154 Diagnostic Information for Multiple Bus Systems . When DIAGNOSTIC OPERATING INSTRUCTIONS display. Use the following steps to run the Online diagnostics in maintenance mode: 1. use the F3 key to return to DIAGNOSTIC OPERATING INSTRUCTIONS. Be sure to vary on any resource you had varied to off. v When the DIAGNOSTIC OPERATING INSTRUCTIONS display. 6.

before running standalone diagnostics on a given partition. If running standalone diagnostics in a full machine partition. 2. LPAR Considerations for Standalone Diagnostics v To run standalone diagnostics on an full machine partition. v For an LPAR partition. power off the system unit. you must reboot the whole system. Using Standalone and Online Diagnostics 155 . Note: Error Log Analysis is not done by the Standalone Diagnostics. Stop all programs on that partition. use the following steps: 1. Devices on an LPAR system are moved on a slot basis. Running the Standalone Diagnostics from CD-ROM To run Standalone Diagnostics in service mode. including the operating system. If running standalone diagnostics in an LPAR partition. Turn off the system unit power.Standalone Diagnostic Operation Use Standalone Diagnostics to test the system when the Online Diagnostics are not installed and as a method of testing the disk drives and other resources that can not be tested by the Online Diagnostics. Chapter 26. the user must move the device from the location where standalone diagnostics is booted (the CD-ROM drive or the network adapter connected to the NIM server in the case of NIM boot of standalone diagnostics). along with the CD-ROM drive. If running from the diagnostic CD-ROM disc. Remove all tapes. for an LPAR system. make the CD-ROM drive available to the partition used to run standalone diagnostics (refer to the Hardware Management Console for Operations Guide for more information). 3. between partitions. you may boot standalone diagnostics in a given partition or on the entire system (which is same procedure as on an full machine partition). It is recommended that you attach few SCSI devices to the same SCSI controller card to prevent moving them. verify with the system administrator and system users that the system unit may be shut down. However. all SCSI devices on the same SCSI adapter card to which the CD-ROM drive is attached must also be moved to the same partition. Stop all programs including the AIX operating system (Refer to the AIX operating system documentation for information on the shutdown command). reboot that partition. to the partition that will run standalone diagnostics. the CD-ROM drive and the SCSI controller that controls it cannot be tested by the Standalone Diagnostics. 4. and the partition will be rebooted. power on the system unit. If running standalone diagnostics in a full machine partition. 5. and CD-ROMs. diskettes. but the system itself is not powered off in order to boot standalone diagnostics in an LPAR partition. If you are running standalone diagnostics in a full machine partition. Verify with the system administrator and system users using that partition that all applications on that partition must be stopped. v A reboot is required on the partition containing this device and on the moved device. If the CD-ROM drive is moved from one partition to another. If you are running standalone diagnostics in an LPAR partition.

6. press the F5 key on the directly attached keyboard. use the F3 key to return to the DIAGNOSTIC OPERATING INSTRUCTIONS. 11. After the diagnostic controller loads. 10. or the number 5 key on the TTY keyboard. When testing is complete. 9. When the keyboard POST indicator appears. 8. DIAGNOSTIC OPERATING INSTRUCTIONS appear on the console display. Follow any instructions to select the console. 156 Diagnostic Information for Multiple Bus Systems . Follow the displayed instructions to test the desired resources. 7. Enter any requested passwords.

These considerations and actions are not detailed step-by-step instructions. You are directed to the detailed procedures for the various activities as needed. This information is intended for use by both the operator of the system and the service representative. be sure you isolate this system unit before stopping the operating system or running diagnostic programs. Chapter 26.General Information about Multiple Systems This topic presents general information for anyone needing to run the diagnostic programs on a system unit that is attached to another system. Some system-cabling changes (such as installing wrap plugs or removing a device from the configuration) may require action by the operator of the attached system before making the cabling changes on this system. These guidelines generally present considerations for the following: v Starting and stopping the communications with the other system v Considerations before running diagnostics on the system v Analyzing the error log information v Using the wrap plugs with the diagnostics When this system unit is attached to another system. but are used to ensure that you have considered the attached system before you run diagnostics on this system unit. Using Standalone and Online Diagnostics 157 .

PCI bus Model Architecture: OEM v If you are running AIX 4.Determining System Architecture Location codes and many of the service aids are restricted by the system model architecture (platform).1 or later diagnostics.2. do the following: – Press the F8 key. from an AIX shell enter: lscfg | pg. 2. select Display Configuration and Resource List from the Task Selection Menu. and you are running AIX Diagnostics from Standalone or Online mode. Assume the service aid can be accessed on either platform unless a note is included. enter the dev / command. A menu containing the device_type appears. The service aids in this manual may be identified as being CHRP or RSPC only. v If you are running AIX 4. Refer to “Location Codes for RSPC Model Architecture System Units” on page 234 for RSPC location codes and “Location Codes for CHRP Model Architecture System Units” on page 236 for CHRP location codes. v On any AIX operating system when you are logged in with root authority. – At the prompt.1 or later. Chapter 28. PCI bus Model Architecture: CHRP Model Implementation: Multiple Processor. If location codes or service aids are needed to complete servicing your system. The system platform type is returned. it may be necessary to know which platform your system is using. run the bootinfo -p command. but before the audible tone sounds.2. MCA bus Model Architecture: RSPC Model Implementation: Uniprocessor. To determine the type of platform on which you are working. after turning on power and the first image appears. stating the service aid is CHRP or RSPC only. 158 Diagnostic Information for Multiple Bus Systems . An OK prompt appears. This manual deals with the following platforms: v CHRP (Common Hardware Reference Platform) v RSPC (PowerPC Reference Platform) Notes: 1. enter one of the following commands. v On system units that support the OK prompt. “Diagnostics Numbers and Location Codes” on page 217 contains two location code sections. A screen displays a message similar to one of the following: Model Architecture: RS6k Model Implementation: Uniprocessor. The platform designation (CHRP or RSPC) is identified.

v Error Log Analysis is only performed when running online diagnostics. v A complete memory test is run during POST. v Permanent errors do not necessarily mean a part should be replaced. and Cable Information for Multiple Bus Systems. The configuration provides high availability because either system unit or CPU drawer can continue to access the common devices while the other system is unavailable. v The POST only halts and reports problems that prevent the system from booting. then using the diag command or selecting the Run Error Log Analysis task. refer to Adapters. Thresholds can be from 1 to 100 depending on the error. v Error Log Analysis is part of the diagnostic applications. be sure you use the software documentation to prepare the configuration before turning off a system unit or device. v Error Log Analysis only reports problems if the errors have reached defined thresholds. Memory and Processor Testing v Memory and Fixed-Point Processors are only tested during POST. v Performs error log analysis if the diagnostics are running online in problem determination mode or error log analysis mode. Chapter 26. Devices. v Automatic Error Log Analysis (diagela) provides the capability to do error log analysis whenever a permanent hardware error is logged. The analysis is started by selecting a device from the DIAGNOSTIC SELECTION menu. but did not prevent the system from booting. Error Log Analysis v Error Log Analysis is analysis of the AIX Error Log entries. Sysplanar and Memory Diagnostics v Analyzes POST and firmware errors that were detected during IPL. Therefore. The actions needed to isolate a particular system unit or device from the configuration depends on the software controlling the systems and devices. Diagnostic Summary The following topics provide summary type information about some features of the diagnostics. v All other problems are logged for later analysis by the Sysplanar and Memory Diagnostics. High-Availability Cabling For additional cabling information.High-Availability SCSI A high-availability SCSI configuration consists of two system units or CPU drawers connected to a common set of SCSI devices. Using Standalone and Online Diagnostics 159 . v Error Log Analysisis not performed when running diagnostics from removable media.

Displaying VPD. 160 Diagnostic Information for Multiple Bus Systems . and a resource or group of resources are selected. The FUNCTION SELECTION menu contains two selections allowing either all resources. Run this mode when you are doing a repair verification. Resources are devices used by the system unit. v System Verification Mode does not perform Error Log Analysis. When task selection is made and a task has been selected. “Introduction to Tasks and Service Aids” on page 169. Alternatively. If a problem is not found. and error log analysis (ELA) mode when running diagnostics from the Task Selection menu. Service aids are also considered tasks. v Problem Determination Mode runs all tests unless the resource is being used. a list of supporting resources displays. the FUNCTION SELECTION menu contains Diagnostic routines and Advanced Diagnostic routines selection. or all tasks to be displayed. a screen appears informing the user that the resource needs to be made available for testing. Error Log Analysis is performed even if a resource is being used. Diskette drive and CD-ROM drive are examples of resources. If a resource is being used. a list of common tasks displays. Diagnostics Tasks and Resources Tasks are operations that can be performed on a resource.Diagnostic Modes The Diagnostic Modes consist of Problem Determination Mode and System Verification Mode. to aid with backward compatibility. or Formatting a Device. Also. are examples of tasks. Tasks and service aids are further described in Chapter 27. then Error Log Analysis is performed. Running Diagnostics. when resource selection is made. The Display or Change Diagnostic Run Time Options task can be used to set advanced mode diagnostics. v In Problem Determination Mode. looping capability.

turned off. Using Standalone and Online Diagnostics 161 . Indicates that the machine will not be attended. Storage Devices 7. You must also specify a device with the -d flag. the -v flag takes precedence and the -e flag is ignored. -S testsuite Indicates a particular Test Suite of devices to test: 1. Must also use an option flag (-d. Async Devices 4. -e Performs error log analysis if supported on the selected device. Specifies Advanced mode. If used with the -v flag. May be used with the -d flag.Format Media Task v certify . No tests are performed. The flag works with any other flag. -T taskname Fastpath to specific task to run.2 and later diagnostic command line options: diag [[-a] | [-s[-c]] [-E Days] [-e] | [-d Device] [-v] [-c] [-e] [-A]] | [-B[-c]] | [-T taskname] |-S] testsuite] Flags The diag command line flags are as follows: -a -A -B -c Processes any change in the hardware configuration by asking if missing resources have been remove. Instructs the diagnostics to run the base system test. -d Device Specifies the device to run diagnostics on. -B. Base System 2. No questions are asked. -s) that specifies a device to be tested. -E Days Specifies the number of days to use when searching the error log during Run Error Log Analysis. Commo Devices 8. Current fastpath tasks are the following: v format . otherwise the resource selection menu is displayed. and so on. Multimedia Devices -s Runs diagnostics on all resources.Certify Media Task Chapter 26. SCSI Devices 6. Graphic Devices 5. Error log analysis is also done on areas in the base system that supports error log analysis. I/O Devices 3. Results are written to standard output.diag Command Line Options The following describe the Version 4.

v download - Download Microcode Task v disp_mcode - Display Microcode Level Task v chkspares - Spare Sector Availability Task v identify - PCI RAID Physical Disk Identify Task Note: Tasks are platform and device dependent. Some tasks may not be available on the system. -v Runs diagnostics in System Verification Mode, no error log analysis performed. The default is Problem Determination mode that tests the device and runs error log analysis. If used with the -e flag, the -v flag takes precedence and the -e flag is ignored. Must be used with the -d flag to specify a device to run diagnostics on.

Default execution mode is non-advanced mode.

SCSI RAID Descriptions and Diagnostic Procedures Viewing the Existing Firmware Level Installed on a SCSI RAID Adapter
Below is an example of the steps one might perform to check the microcode level on the RAID adapter: 1. Login as root (if not already root) 2. Type lsdev -C | grep scraid. This lists all the SCSI RAID adapters installed or defined to the system. 3. Identify the number (for example, scraid0) of the card for which you wish to check the microcode level. 4. Type lscfg -vl scraidX (where X is the number of the RAID adapter from above). 5. Look at the Loadable Microcode Level field, compare it to the desired level.

Updating the Firmware on a SCSI RAID Target Adapter
This procedure assumes that you have obtained the SCSI RAID adapter microcode you wish to download, and it is located either on a diskette, or in the /etc/microcode directory of the system containing the RAID adapter you want to update. This section describes the method for transferring the new firmware into the target adapter. Each flash update should complete within one minute. Warning: Do not power off the target server at any time before the flash process completes. If power is removed or the system is reset while flash_update is being run, irrecoverable failures may occur. This could require return of the adapter for exchange. Diagnostic menu procedure: 1. Login as root or use CE Login (if not already logged in) 2. Type diag 3. Select Task Selection -> Download Microcode

162

Diagnostic Information for Multiple Bus Systems

4. When Resource Selection menu displays select scraidX, (Where X is the ID of the desired adapter) and press F7. 5. When Display Microcode Level menu displays select Adapter. 6. When Install Microcode menu displays select Functional Microcode. 7. If the current microcode level on the adapter is below the level you want to install select Latest Level (that is, 4.20.18 is currently on the adapter and you wish to install 4.70.11). or If the current microcode level on the adapter is greater than the level you wish to install select Previous Level (that is, 3.70.01 is currently on the adapter and you wish to install 3.12.01). 8. Select where the microcode is located either, /etc/microcode directory or diskette. Command Line procedure: Use one of the two procedures listed, depending on which level of microcode you want to install relative to the existing level it has: Note: You must be logged in as root’ or use CE login to perform these commands. v If the current microcode level on the adapter is below the level you wish to install use the following command: diag -c -d scraidX -T"download" Where X is the ID of the desired adapter, for example, 4.20.18 is currently on the adapter and you wish to install 4.70.11. v If the current microcode level on the adapter is greater than the level you wish to install use the following command: diag -c -d scraidX -T"download -P" Where X is the ID of the desired adapter, for example 3.70.01 is currently on the adapter and you wish to install 3.12.01. After following either the Diagnostic Menu or the Command Line procedure, you should receive a confirmation that microcode has been updated. If you do not, then make sure the adapter is not in use and repeat the appropriate diagnostic step shown above. To confirm the new installed level of firmware on the adapter, use the “Viewing the Existing Firmware Level Installed on a SCSI RAID Adapter” on page 162 procedure.

Displaying the VPD Information of a Disk Drive in a SCSI RAID Subsystem.
You may use any of 3 ways to display the VPD information of a drive in a SCSI RAID. Diagnostics VPD Display:

Chapter 26. Using Standalone and Online Diagnostics

163

The first way is through diagnostics. However, this cannot be performed concurrently with normal RAID operation. The RAID volume group must be varied off to run from diagnostic menus or diagnostics from the command line. A command the customer (logged in as root) might use to vary off the volume group is: varyoffvg RAID_volumegroup (where RAID_volumegroup is the volume group containing the RAID drive you wish to test). Note: The underlying filesystems may need to be unmounted before varying off the volume group can complete successfully. Diagnostic Menu method: 1. Login as root or use CE Login 2. Type diag 3. Select Task Selection -> PCI Physical Disk Identify 4. When the Resource Selection menu displays select scraidX, (Where X is the ID of the desired adapter) Press F7 5. 6. Look at the ROS and RAM code levels. This is drive microcode level. Ask the customer (logged on as root) to type varyonvg RAID_volumegroup where RAID_volumegroup is the name of the volumegroup you previously varied off. Any filesystem unmounted will have to be remounted.

Command Line method: Logged in as root or use CE Login, type in the command: diag -cd scraidX -T"identify" Where X is replaced by the number of the desired adapter. A list containing the VPD information of all the drives in the RAID subsystem will be displayed on the screen. Look at the ROS and RAM code levels. This is drive microcode level. Compare this to the desired level. When you are done, ask customer (logged on as root) to vary on the volume group using command: varyonvg RAID_volumegroup where RAID_volumegroup is the name of the volumegroup you previously varied off. Any filesystem unmounted will have to be remounted. Note: For either of these two methods, if you see the error message: An adapter configuration error was detected.... Run the Disk Array Manager to resolve the adapter configuration error. 1. Login as root (if not already root) 2. Type smit pdam 3. Select Recovery Options -> Resolve PCI SCSI RAID Adapter Configuration -> Display/Accept Configuration Changes

164

Diagnostic Information for Multiple Bus Systems

4. Select the appropriate SCSI RAID adapter containing the drive. 5. Select YES for the Display only option. Warning: The following steps will change the array’s configuration, if you have any doubts do not proceed! 6. If the propose changes to the array configuration match what is desired, press F3 and Select NO for Display Only. 7. If the propose changes to the array configuration do NOT match what is desired, if not, press F10 to exit. SCSI RAID Manager VPD Display method: The third way to display VPD is through the scraidmgr. This can be performed while the RAID array is operational. From the AIX command prompt, ask the customer to: 1. Login as root (if not already root) 2. Type smit pdam 3. Select Change/Show PCI RAID Drive Status -> Display VPD Information 4. Select the appropriate RAID adapter 5. Select the drives from that adapter one at a time. 6. Look at the ROS and RAM code levels. This is drive microcode level. Compare this to the level you need on the adapter.

Updating the Microcode on a Disk in a SCSI RAID Subsystem
Once you have downloaded the desired microcode, follow the readme and place the microcode image in the /etc/microcode directory or on a diskette. With the RAID volume group varied off, you can flash the drives through the following process: Note: The underlying filesystems may need to be unmounted before varying off the volume group can complete successfully. Then, the volume group containing the disk must be varied off. A command the customer (logged in as root) might use to vary off the volume group is: varyoffvg RAID_volumegroup Where RAID_volumegroup is the volume group containing the RAID drive you wish to test. When you are done, ask customer (logged on as root) to vary on the volume group using command: varyonvg RAID_volumegroup Where RAID_volumegroup is the name of the volumegroup you previously varied off. Any filesystem unmounted will have to be remounted. Diagnostic Menu Method 1. Login as root or use CE Login 2. Type diag
Chapter 26. Using Standalone and Online Diagnostics

165

3. Select Task Selection -> Download Microcode 4. When Resource Selection menu displays select scraidX, (Where X is the ID of the desired adapter) and press F7 5. When Install Microcode menu displays select Physical Disks. 6. Select each drive for which microcode is to be flashed by pressing Enter on those drives. Or, select All drives to update every drive. Press F7 to commit. v If the current microcode level on the drive is below the level you wish to install select Latest Level (for example, S9HA is currently on the drive and you wish to install S9RA). v If the current microcode level on the drive is greater than the level you wish to install select Previous Level (for example, S9RA is currently on the drive and you wish to install S9HA) Note: Microcode levels are consecutive going from 0-9 then A-Z. So, level S9HA would be a later level than S96F. 7. Select the location where the microcode image is stored (from above). v - On system’s /etc/microcode directory v On a diskette 8. A message will be displayed if download was successful or failed. Command Line Method: Log in as root or use CE login, then type the command: diag -c -d scraidX -T "download {-l chID | -A} [-D] [-P] where: -A -D -I -P all disk drives Microcode is on diskette (default to /etc/microcode directory) RAID disk drive-physical disk channel/ID (example 27) Download the previous level of microcode (default to latest level)

For example, the command: diag -c -d scraid0 -T"download -l 28" downloads microcode from /etc/microcode to the drive with channel/ID 28.

Displaying and Updating the Microcode on an External Enclosure (2104) or Backplane in a SCSI RAID Subsystem
Note: Microcode download for backplanes only works if a 4-Channel PCI SCSI RAID adapter is installed with at least level 50 of the diagnostics device driver (devices.pci.14102e00.diag.4.3.3.50). Obtain microcode for the external enclosure or backplane on a diskette or in the /etc/microcode directory on the system.

166

Diagnostic Information for Multiple Bus Systems

Note: The RAID volume group must be varied off in order to display and update the backplane microcode. A command the customer (logged in as root) might use to vary off the volume group is: varyoffvg RAID_volumegroup where RAID_volumegroup is the volume group containing the RAID drive you wish to test. Note: The underlying filesystems may need to be unmounted before varying off the volume group can complete successfully. Diagnostic Menus When you are done, ask customer (logged on as root) to vary on the volume group using the command: ″ varyonvg [RAID_volumegroup] where RAID_volumegroup is the name of the volumegroup you previously varied off. Any filesystem unmounted will have to be remounted. To update enclosure microcode using Diagnostic Menus: 1. Login as root or use CE Login 2. Type diag. 3. Select Task Selection -> Download Microcode 4. Select the appropriate scraid adapter attached to the enclosure. 5. Select Backplanes. 6. A list of all the backplanes attached to the adapter will be displayed. Press Enter to select the appropriate backplane(s) or to select all backplanes. Press F7 to commit. 7. Select Latest Level if updating to a higher level of microcode Previous Level if updating to a lower level of microcode. 8. A message will be displayed noting whether the microcode download was successful or it failed.

Chapter 26. Using Standalone and Online Diagnostics

167

168

Diagnostic Information for Multiple Bus Systems

Chapter 27. Introduction to Tasks and Service Aids
The AIX Diagnostic Package contains programs that are called Tasks. Tasks can be thought of as performing a specific function on a resource; for example, running diagnostics or performing a service aid on a resource. This chapter describes the Tasks available in AIX Diagnostics Version 4.2 and later. Normally, one would run certify if after running diagnostics on a drive and its media, no problem is found, but one still suspects that a problem still does exist. Note: Many of these programs work on all system model architectures. Some programs are only accessible from Online Diagnostics in Service or Concurrent mode, while others might be accessible only from Standalone Diagnostics. Still other programs might only be supported on a particular system architecture, such as CHRP (Common Hardware Reference Platform) or RSPC (PowerPC Reference Platform). Refer to “Determining System Architecture” on page 158 to identify the platform type of your system unit. Note: If the system is running on a logically partitioned system, the following tasks may only be executed in a partition with service authority: v Configure Reboot Policy v Configure Remote Maintenance Policy v Configure Ring Indicate Power On v Configure Ring Indicate Power-On Policy v Update System or Service Processor Flash v Save or Restore Hardware Management Policies To perform one of these tasks, use the Task Selection option from the FUNCTION SELECTION menu. After a task is selected, a resource menu may be presented showing all resources supported by the task. A fast path method is also available to perform a task by using the diag command and the -T flag. By using the fast path, the user can bypass most of the introductory menus to access a particular task. The user is presented with a list of resources available to support the specified task. The fast path tasks are as follows: v Certify - Certifies media v Chkspares - Checks for the availability of spare sectors v Download - Downloads microcode to an adapter or device v Disp_mcode - Displays current level of microcode v Format - Formats media v Identify - Identifies the PCI RAID physical disks v IdentifyRemove - Identifies and removes devices (Hot Plug)

169

To run these tasks directly from the command line, specify the resource and other task-unique flags. Use the descriptions in this chapter to understand which flags are needed for a given task.

Tasks
The following tasks are described in this chapter: v Add Resource to Resource List v AIX Shell Prompt v Analyze Adapter Internal Log v Backup and Restore Media v Certify Media v Change Hardware Vital Product Data v Configure Dials and LPF Keys v Configure ISA Adapters v Configure Reboot Policy v Configure Remote Maintenance Policy v Configure Ring Indicate Power On v Configure Ring Indicate Power-On Policy v Configure Service Processor (RSPC) v Configure Surveillance Policy v Create Customized Configuration Diskette v Delete Resource from Resource List v Disk Maintenance v Display Configuration and Resource List v Display Firmware Device Node Information v Display Hardware Error Report v Display Hardware Vital Product Data v Display Machine Check Error Log v Display Microcode Level v Display or Change Bootlist v Display or Change Diagnostic Run Time Options v Display Previous Diagnostic Results v Display Resource Attributes v Display Service Hints v Display Software Product Data v Display System Environmental Sensors v Display Test Patterns v Display USB Devices v Download Microcode v Fibre Channel RAID Service Aids v Flash SK-NET FDDI Firmware v Format Media v Gather System Information v Generic Microcode Download v Hot Plug Task v Local Area Network Analyzer v Log Repair Action v Periodic Diagnostics v PCI RAID Physical Disk Identify

170

Diagnostic Information for Multiple Bus Systems

v v v v v v v v v v v v v v v v v

Process Supplemental Media Run Diagnostics Run Error Log Analysis Run Exercisers Save or Restore Hardware Management Policies Save or Restore Service Processor Configuration SCSI Bus Analyzer SCSD Tape Drive Service Aid Spare Sector Availability SSA Service Aid System Fault Indicator System Identify Indicator Update Disk-Based Diagnostics Update System or Service Processor Flash Update System Flash 7135 RAIDiant Array Service Aids 7318 Serial Communication Network Server

Add Resource to Resource List
Use this task to add resources back to the resource list. Note: Only resources that were previously detected by the diagnostics and deleted from the Diagnostic Test List are listed. If no resources are available to be added, then none are listed.

AIX Shell Prompt
Note: Use this service aid in Online Service Mode only. This service aid allows access to the AIX command line. To use this service aid, the user must know the root password (when a root password has been established). Note: Do not use this task to install code or to change the configuration of the system. This task is intended to view files, configuration records, and data. Using this service aid to change the system configuration or install code can produce unexplained system problems after exiting the diagnostics.

Analyze Adapter Internal Log
The PCI RAID adapter has an internal log that logs information about the adapter and the disk drives attached to the adapter. Whenever data is logged in the internal log, the device driver copies the entries to the AIX system error log and clears the internal log. The Analyze Adapter Internal Log service aid analyzes these entries in the AIX system error log. The service aid displays the errors and the associated service actions. Entries that do not require any service actions are ignored.

Chapter 27. Introduction to Tasks and Service Aids

171

Backup and Restore Media
This service aid allows verification of backup media and devices. It presents a menu of tape and diskette devices available for testing and prompts for selecting the desired device. It then presents a menu of available backup formats and prompts for selecting the desired format. The supported formats are tar, backup, and cpio. After the device and format are selected, the service aid backs up a known file to the selected device, restores that file to /tmp, and compares the original file to the restored file. The restored file remains in /tmp to allow for visual comparison. All errors are reported.

172

Diagnostic Information for Multiple Bus Systems

Certify Media
This task allows the selection of diskette, DVD-RAM media or hard files to be certified. Normally, this is done for the following two conditions: v To determine the condition of the drive and media. v To verify that the media is error free after a Format Service Aid has been run on the media. Normally, one would run certify if after running diagnostics on a drive and its media, no problem is found, but one still suspects that a problem still does exist. Hard files can be connected either to a SCSI adapter (non-RAID) or a PCI SCSI RAID adapter. The usage and criteria for a hard file connected to a non-RAID SCSI adapter are different from those for a hard file connected to a PCI SCSI RAID adapter. Certify may be used in the following ways: v Certify Diskette This selection enables you to verify the data written on a diskette. When you select this service aid, a menu asks you to select the type of diskette being verified. The program then reads all of the ID and data fields on the diskette one time and displays the total number of bad sectors found. v Certify DVD-RAM media This selection reads all of the ID and data fields. It checks for bad data and counts all errors encountered. If an unrecovered error occurs, or recovered errors exceed the threshold value, the data on the media should be transferred to other media and the original media should be discarded. The Certify service aid will display the following information: – Capacity in bytes – Number of Data Errors Not Recovered – Number of Equipment Check Errors – Number of Recovered Errors If the drive is reset during a certify operation, the operation is restarted. If the drive is reset again, the certify operation is terminated and the user is asked to run diagnostics on the drive. This task can be run directly from the AIX command line. See the following command syntax: diag -c -d -T certify Flag -c -d -T Description No console mode Specifies a device Specifies the certify task

v Certify Hardfile Attached to a Non-RAID SCSI Adapter This selection reads all of the ID and data fields. It checks for bad data and counts all errors encountered. If there are unrecovered data errors that do not exceed the threshold value, then the hard file needs to be formatted and certified. If the
Chapter 27. Introduction to Tasks and Service Aids

173

unrecovered data errors, recovered data errors, recovered and unrecovered equipment errors exceed the threshold values, the disk needs to be replaced. It also makes 2000 random seeks after the read certify of the surface completes. If a disk timeouts before finishing the random seeks, then the disk needs to be replaced. The random seeks also count all errors encountered. The Certify service aid will display the following information: – Drive capacity in megabytes. – Number of Data Errors Recovered. – Number of Data Errors Not Recovered. – Number of Equipment Checks Recovered. – Number of Equipment Checks Not Recovered. This task can be run directly from the AIX command line. See the following command syntax: diag -c -d deviceName -T "certify" Flag -c -d -T Description No console mode Specifies a device Specifies the certify task

v Format and/or Erase Hardfile Attached to a Non-RAID SCSI Adapter Warning: The following commands WILL change the content of the hardfile. Be sure to backup data prior to running the command, and take care in choosing the hardfile upon which you run this task. – Hardfile Format Writes all of the disk. The pattern written on the disk is device-dependant; for example, some drives may write all 0s, while some may write the hexadecimal number 5F. No bad block reassignment occurs. – Hardfile Format and Certify Performs the same function as Hardfile Format. After the format is completed, Certify is run. Certify then reassigns all bad blocks encountered. – Hardfile Erase Disk This option can be used to overwrite (remove) all data currently stored in user-accessible blocks of the disk. The Erase Disk option writes one or more patterns to the disk. An additional option allows data in a selectable block to be read and displayed on the system console. To use the Erase Disk option, specify the number (0-3) of patterns to be written. The patterns are written serially; that is, the first pattern is written to all blocks. Then the next pattern is written to all blocks, overlaying the previous pattern. A random pattern is written by selecting the Write Random Pattern option. Note: The Erase Disk service aid has not been certified as meeting the Department of Defense or any other organization’s security guidelines. Use the following steps to overwrite the data on the drive: 1. Use the Erase Disk selection to overwrite the data on the drive.

174

Diagnostic Information for Multiple Bus Systems

Certify reads the entire disk and checks for recovered errors. This data is used later when the drive is to be overwritten. the user is prompted to replace the physical disk. Use you drive as you would normally. 4. Compare the bad blocks which were recorded for the drive in step 3 with those that now appear in the grown defect MAP. Run a second pass of the Erase Disk selection. To selectively read or write. then all sectors on this drive cannot be overwritten. See the command syntax: diag -c -d deviceName -T "format [-s* fmtcert | erase -a {read | write}] [-F]* Flag fmtcert erase * -F Description Formats and certifies the disk. For a newly installed drive. record the information presented and ensure that this information is kept with the drive. 3. Format the drive. use the diag command in console mode. continue running the service aid to overwrite the disk with the chosen pattern(s). Chapter 27. there may be some blocks which get placed into the grown defect MAP. and reassigned errors. you can ensure that all blocks on the drive are overwritten with your pattern if you use the following procedure: 1. unrecovered errors. 5. v Certify Hardfile attached to a PCI SCSI RAID Adapter This selection is used to certify physical disks attached to a PCI SCSI RAID adapter. Available in no-console mode only. Check the defect MAP by running the Erase Disk selection. When the drive is no longer needed and is to be erased. Note: If there are differences between the saved data and the newly obtained data. 2. Note: The Erase Disk option in command line mode uses default values. 7. 6.2. Introduction to Tasks and Service Aids 175 . If these errors exceed the threshold values. If there are bad blocks in the defect MAP. Force the disk erasure even if all blocks cannot be erased due to errors accessing the grown defect map. Overwrites the data on the disk. Note: If you use Format and Certify option. 3. Note: Using the same version of the service aid is only critical if any bad blocks were found in step 3. Do a format without certify. This task can be run directly from the AIX command line. The new bad blocks are not overwritten. run the same version of the Erase Disk selection which was used in step 2. If the bad block list is the same.

When a resource is selected. The menu lists all resources installed on the system. 176 Diagnostic Information for Multiple Bus Systems . Note: The user cannot alter the VPD for a specific resource unless it is not machine-readable. See the following command syntax: diag -c -d RAIDadapterName -T "certify {-l chID | -A}" Flag -c -d -T -I -A Description No console mode Specifies the RAID adapter to which the disk is attached Specifies the certify task and its parameters Specifies physical Disk channel/ID (example: -l 27) All disks Change Hardware Vital Product Data Use this service aid to display the Display/Alter VPD Selection Menu. a menu displays that lists all the VPD for that resource.This task can be run directly from the AIX command line.

To determine if there are any defined TTYs. the diagnostics fail because the system cannot detect the ISA adapter. If you have problems in standalone mode. then add a new TTY and configure the Dials or LPF keys. Diagnostic support for ISA adapters not shown in the list may be supported from a supplemental diskette. Chapter 27. Whenever an ISA adapter is installed. This selection invokes the SMIT utility to allow Dials and LPF keys configuration. Configure ISA Adapter This task uses SMIT to identify and configure ISA adapters on systems that have an ISA bus and adapters. then a TTY port defined on the adapter. select List All Defined TTYs. you must remove all defined TTYs. Once all defined TTYs have been removed. The task allows an async adapter to be configured. Introduction to Tasks and Service Aids 177 . A TTY must be in the available state on the async port before the Dials and LPF keys can be configured on the port. use the hardfile-based diagnostics. You must also run this service aid to remove an ISA adapter from the system whenever an ISA adapter is physically removed from the system. This service aid provides a tool for configuring and removing dials and LPF keys to the asynchronous serial ports. Before configuring Dials or LPF keys on a serial port. this service aid must be run and the adapter configured before the adapter can be tested. You can use the Process Supplemental Media task to add ISA adapter support from a supplemental diskette. If diagnostics are run on an ISA adapter that has been removed from the system.Configure Dials and LPF Keys Note: The Dials and LPF Keys service aid is not supported in standalone mode (CD-ROM and NIM) on systems with 32 MB or less memory. Dials and LPF keys can then be defined on the port.

an enabled ’Supplemental Restart Policy’ causes a system reset and the reboot process begins. v Maximum Number of Reboot Attempts Enter a number that is 0 or greater. is used when the O/S Defined Restart Policy is undefined. from a system reset or power-on. is used to describe the operating system activation process. is used to describe bringing system hardware back up from scratch. some of the following settings might not be displayed by this service aid. for example. 0=No) When ’Use the O/S Defined Restart Policy’ is set to Yes. then the restart policy is determined by the ’Supplemental Restart Policy’. The term restart. in the context of this service aid. in the context of this service aid. v Call-Out Before Restart (on/off) When enabled. Note: A value of 0 indicates ’do not attempt to reboot’ to a crashed system. the system attempts to reboot from a crash if the operating system has an enabled Defined Restart or Reboot Policy. or is set to False. This service aid controls how the system tries to recover from a system crash. 0=No) The ’Supplemental Restart Policy’. When ’Use the O/S Defined Restart Policy’ is set to No. Such calls can be valuable if the number of these events becomes excessive. When the reboot process completes successfully. When surveillance detects operating system inactivity during restart. thus signalling bigger problems.Configure Reboot Policy Note: This service aid runs on CHRP system units only. if enabled. and a restart begins. When a restart fails. the reboot attempts count is reset to 0. the system attempts to reboot for the maximum number of attempts. 0=No) 178 Diagnostic Information for Multiple Bus Systems . v Enable Unattended Start Mode (1=Yes. Restart always follows a successful reboot. v Use the O/S Defined Restart Policy (1=Yes. Use this service aid to display and change the following settings for the Reboot Policy. or the operating system restart policy is undefined. and a restart policy is enabled. This number is the maximum number of consecutive attempts to reboot the system. Note: Because of system capability. The term reboot. Call-Out Before Restart allows the system to call out (on a serial port that is enabled for call-out) when an operating system restart is initiated. v Enable Supplemental Restart Policy (1=Yes.

v Customer Administration Center Phone Number Chapter 27. The service center usually includes a computer that takes calls from systems with call-out capability. Contact the service provider for the correct telephone number to enter here. v Configuration File for Modem on serial port 1 (S1) Configuration File for Modem on serial port 2 (S2). You can access this service aid directly from the AIX command line. The modem configuration files are located in the directory /usr/share/modems. The Remote Maintenance Policy includes modem configurations and phone numbers to use for remote maintenance support. If a modem file is already loaded. If the system was powered-off when the ac loss occurred.When enabled. For more information about the format and catcher computers.″ The catcher expects messages in a specific format to which the Service Processor conforms. Use this service aid to display and change the following settings for the Remote Maintenance Policy. If the system was powered-on when the ac loss occurred. This computer is referred to as ″the catcher. the system remains off when power is restored. v Modem file currently loaded on S1 Modem file currently loaded on S2 This is the name of the file that is currently loaded on serial port 1 or serial port 2. v Call Out Authorized on S1 (on/off) Call Out Authorized on S2 (on/off) Call Out allows the Service Processor to place calls for maintenance. v Call In Authorized on S1 (on/off) Call In Authorized on S2 (on/off) Call In allows the Service Processor to receive a call from a remote terminal. v Service Center Phone Number This is the number of the service center computer. by typing: /usr/lpp/diagnostics/bin/uspchrp -b Configure Remote Maintenance Policy Note: This service aid runs on CHRP system units only. it is indicated by Modem file currently loaded. Note: Because of system capability. some of the following settings might not be displayed by this service aid. ’Unattended Start Mode’ allows the system to recover from the loss of ac power. refer to the README file in the AIX /usr/samples/syscatch directory. Note: These settings are only shown when a modem file is loaded for a serial port. Introduction to Tasks and Service Aids 179 . Enter the name of a modem configuration file to load on either S1 or S2. v S1 Line Speed S2 Line Speed A list of line speeds is available by using List on the screen. the system reboots when power is restored.

v Remote Timeout. This is also referred to as the Call In phone number. Note: Knowing the system name aids the support team in quickly identifying the location. You can access this service aid directly from the AIX command line. Customer Administration Center 3. or answered by someone responsible for the system. in seconds Remote Latency. v Customer Account Number This number is available for service providers to use for record-keeping and billing. Customer Administration Center 3. v System Name (System Administrator Aid) This is the name given to the system and is used when reporting problem messages. v Number of Retries While Busy This is the number of times the system should retry calls that resulted in busy signals. Service Center 2. Pager v Customer RETAIN Login ID Customer RETAIN Login Password These settings apply to the RETAIN service function. v Customer Voice Phone Number This is the number for a telephone near the system. call out stops at the first successful call to one of the following numbers in the order listed: 1. Service Center 2. The service or administration center representatives need this number to make direct contact with your system for problem investigation. call-out attempts to call all of the following numbers in the order listed: 1.This is the number of the System Administration Center computer (catcher) that receives problem calls from systems. Pager If Call Out Policy is set to All. v Call Out Policy Numbers to call if failure This is set to either First or All. v Customer System Phone Number This is the number to which your system’s modem is connected. in seconds These settings are functions of the service provider’s catcher computer. by typing: /usr/lpp/diagnostics/bin/uspchrp -m 180 Diagnostic Information for Multiple Bus Systems . Contact the system administrator for the correct telephone number to enter here. and so on of your system. configuration. If the call-out policy is set to First. history. This is the telephone number left on the pager for callback. v Digital Pager Phone Number In Event of Emergency This is the number for a pager carried by someone who responds to problem calls from your system.

This service aid allows the user to display and change the NVRAM settings for the Ring Indicate Power On capability of the service processor. If the system is powered off. This service aid allows the user to power-on a system by telephone from a remote location. by typing: /usr/lpp/diagnostics/bin/uspchrp -r Configure Ring Indicate Power On Note: This service aid runs on RSPC system units only. The settings allows the user to: v Enable or disable power-on from Ring Indicate v Read or set the number of rings before power-on Configure Service Processor Note: This service aid runs on RSPC system units only. no action is taken.Configure Ring Indicate Power-On Policy Note: This service aid runs on CHRP system units only. If the system is already on. In either case. Use this service aid to display and change the following settings for the Ring Indicate Power-On Policy: Note: Because of system capability. Introduction to Tasks and Service Aids 181 . the system powers on at a predetermined number of rings. and Ring Indicate Power On is enabled. This service aid supports the following functions: v Surveillance Setup v Modem Configuration v Call in or call out Setup v Site specific call in or call out setup v Reboot or restart policy setup Chapter 27. some of the following settings might not be displayed by this service aid. and the caller receives no feedback that the system has powered on. This service aid allows you to display and change the NVRAM settings for the service processor. v Power On Via Ring Indicate (on/off) v Number of Rings Before Power On You can access this service aid directly from the AIX command line. the telephone call is not answered.

The site-specific NVRAM settings allow you to set the following: v Phone number for the service center v Phone number for the customer administration center v Phone number for a digital pager v Phone number for the customer system to call in v Phone number for the customer voice phone v Customer account number v Call-out policy v Customer RETAIN ID v Customer RETAIN password v Remote timeout value v Remote latency value v Number of retries while busy v System name 182 Diagnostic Information for Multiple Bus Systems . The settings allow you to: v Enable or disable surveillance v Set the surveillance time interval. in minutes v Set the surveillance delay. Call In/Out Setup This selection allows the user to display and change the NVRAM settings for the Call In/Call Out capability of the service processor. Refer to the Service Processor Installation and User’s Guide for more information. The formatted modem configuration file is read. in minutes The current settings are read from NVRAM and displayed on the screen. Modem Configuration Use this selection when setting the NVRAM for a modem attached to any of the Service Processor’s serial ports. The user inputs the file name of a modem configuration file and the serial port number.Surveillance Setup Note: Surveillance is only supported for systems running in full machine partition. The settings allow the user to: v Enable or disable call in on either serial port v Enable or disable call out on either serial port v Set the line speed on either serial port Site Specific Call In/Out Setup This selection allows you to display and change the NVRAM settings that are site-specific for the call-in or call-out capability of the service processor. Any changes made to the data shown are written to NVRAM. and then loaded into NVRAM. converted for NVRAM. This selection allows you to display and change the NVRAM settings for the surveillance capability of the service processor.

Note: A value of 0 indicates ″do not attempt to reboot″ to a crashed system. an enabled ″Restart Policy″ causes a system reset. Introduction to Tasks and Service Aids 183 . ″Call-Out Before Restart″ allows the system to call out (on a serial port that is enabled for call-out) when an operating system restart is initiated. v Enable Unattended Start Mode (1=Yes. the system remains off when power is restored. v Enable Restart Policy (1=Yes. when used in context of this service aid. describes the system hardware being brought back up from scratch. Restart always follows a successful reboot. Such call-outs can be valuable if the number becomes excessive. describes the operating system activation process. When the maximum number of reboot attempts is exceeded. This number is the maximum number of consecutive attempts allowed to reboot the system. when used in context of this service aid.The current settings are read from NVRAM and displayed on the screen. the reboot-attempts count is reset to 0. When the reboot process completes successfully. and a restart begins. v Maximum Number of Reboot Attempts Enter a number that is 0 or greater. If the system was powered-on when the ac loss occurred. the system attempts to reboot for the maximum number of reboot attempts. The term restart. thus signalling bigger problems. 0=No) When the service processor detects operating system inactivity. the system reboots when power is restored. Any changes made to the data shown are written to NVRAM. and a restart policy is enabled. v Call-Out Before Restart (on/off) When enabled. When a restart fails. 0=No) When enabled. the system calls out if that function has been enabled. If the system was powered-off when the ac loss occurred. Examples would be a system reset or turning on the power. The term reboot. Chapter 27. and the reboot process begins. ″Unattended Start Mode″ allows the system to recover from the loss of ac power. Use this service aid to display and change the following settings for the Reboot Policy Setup. Reboot/Restart Policy Setup This selection controls how the system tries to recover from a system crash.

Otherwise the changes take effect beginning with the next system boot. some of the following settings might not be displayed by this service aid: v Surveillance (on/off) v Surveillance Time Interval This is the maximum time between heartbeats from the operating system. by typing: /usr/lpp/diagnostics/bin/uspchrp -s Create Customized Configuration Diskette This selection invokes the Diagnostic Package Utility Service Aid. set the refresh rate to 77. If the display’s refresh rate is 77 Hz. This service aid is only supported for systems running in full machine partition. which allows the user to create a standalone diagnostic package configuration diskette. The Standalone Diagnostic Package Configuration Diskette allows the following to be changed from the console: v Default refresh rate for a low function terminal (LFT) The refresh rate used by the standalone diagnostic package is 60 Hz. v Different async terminal console You can create a console configuration file that allows a terminal attached to any RS232 or RS422 adapter to be selected as a console device. a call is placed to report the failure. You can access this service aid directly from the AIX command line. This service aid monitors the system for hang conditions. v Changes are to Take Effect Immediately Set this to Yes if the changes made to the settings in this menu are to take place immediately. 184 Diagnostic Information for Multiple Bus Systems . The default device is an RS232 TTY device attached to the first standard serial port (S1).Configure Surveillance Policy Note: This service aid runs on CHRP system units only. that is. When enabled. Use this service aid to display and change the following settings for the Surveillance Policy: Note: Because of system capability. hardware or software failures that cause operating system inactivity. and surveillance detects operating system inactivity. v Surveillance Time Delay This is the time to delay between when the operating system is in control and when to begin operating system surveillance.

Use the migratepv command when copying the contents to other disk drive types. To help prevent possible problems with the new drive. both the old and new disks must be installed in or attached to the system with unique SCSI addresses. then none are listed. Set the SCSI address of the new drive to the SCSI address of the old drive. Install any other drives (that were removed) into their original location. The service aid only supports copying from a SCSI drive to another SCSI drive of similar size. Note: Only resources that were previously detected by the diagnostics and have not been deleted from the Diagnostic Test List are listed. Remove both drives. This publication is located on the AIX Documentation CD. Chapter 27. If no resources are available to be deleted. This command also works when copying SCSI disk drives or when copying to a different size SCSI disk drive. To use this service aid. 4. Either remove the target drive to return to the original configuration. This selection allows you to recover data from an old drive when replacing it with a new drive. When the copy is complete. or perform the following procedure to complete the replacement of the old drive with the new drive: 1. To prevent corrupted data from being copied to the new drive. 2.Delete Resource from Resource List Use this task to delete resources from the resource list. Disk Maintenance This service aid provides the following options for the fixed-disk maintenance: v Disk to Disk Copy v Display/Alter Sector Disk to Disk Copy Notes: 1. 3. This requires that the new disk drive SCSI address must be set to an address that is not currently in use and the drive be installed in an empty location. the service aid stops if the number of bad blocks being reassigned reaches a threshold. the service aid stops if an unrecoverable read error is detected. The documentation information is made accessible by loading the documentation CD onto the hard disk or by mounting the CD in the CD-ROM drive. Introduction to Tasks and Service Aids 185 . then one of the other drives must be removed. only one drive can remain installed. Refer to System Management Guide: Operating System and Devices for a procedure on migrating the contents of a physical volume. 2. This service aid cannot be used to update to a different size drive. If there are no empty locations. The service aid recovers all logical volume manager (LVM) software reassigned blocks. Install the new drive in the old drive’s location.

The Display Error Analysis Summary and Display Error Analysis Detail selection provide additional analysis. The format of the output data may differ depending on which level of the AIX operating system is installed. the Diagnostic Package is loaded. This service aid is intended to gather more information about individual or particular devices on the system. from the diagnostics that are loaded from removable media. when possible.To prevent problems that can occur when running this service aid from disk. the service aid does not display information that cannot be read correctly. Display Configuration and Resource List If a device is not included in the Test List or if you think a Diagnostic Package for a device is not loaded. Display Hardware Error Report This service aid uses the errpt command to view the hardware error log. Display/Alter Sector Note: Use caution when you use this service aid because inappropriate modification to some disk sectors can result in the total loss of all data on the disk. If the device has an asterisk (*) preceding its name. check by using the Display Configuration and Resource List task. (No VPD is displayed. 186 Diagnostic Information for Multiple Bus Systems . This service aid displays the item header only for all installed resources. the Diagnostic Package for the device is not loaded or is not available. Use this service aid when there is no need to see the vital product data (VPD). Data is displayed both in hex and in ASCII. Sectors are addressed by their decimal sector number.) Display Firmware Device Node Information Note: This service aid runs on CHRP system units only. This selection allows the user to display and alter information on a disk sector. If the device you want to test has a plus (+) sign or a minus (-) sign preceding its name. The Display Error Summary and Display Error Detail selection provide the same type of report as the errpt command. it is suggested that this service aid be run. This task displays the firmware device node information that appears on CHRP platforms. To prevent corrupted data from being incorrectly corrected.

Introduction to Tasks and Service Aids 187 . In either case. See the following command syntax: diag -c -d device -T "disp_mcode" Flag -c -d -T Description No console mode. Use the disp_mcode option to display microcode. Use this service aid when you want to look at the VPD for a specific resource. or erased. You can display the current level of the microcode on an adapter. information is collected and logged in an NVRAM error log before the system unit shuts down. altered. When booting from the hard disk or LAN. Used to specify a device. along with any VPD for those resources. Display or Change Bootlist This service aid allows the bootlist to be displayed. this service aid converts the logged information into a readable format that can be used to isolate the problem. sys0 may not be available in all cases. Display Microcode Level This task is used to display the microcode or firmware levels of currently installed resources. the information can be viewed from the AIX error log using the Hardware Error Report Service Aid. When the sys0 resource is selected. Display Machine Check Error Log Note: The Machine Check Error Log Service Aid is available only on Standalone Diagnostics. The system attempts to perform an IPL from the first device in the list. the task displays the levels of both the system firmware and service processor firmware. refer to the AIX Commands Reference manual. For information on the lsmcode command. When a machine check occurs. or standalone media. the system proceeds in turn to the other devices in the list to attempt an IPL. The AIX lsmcode command serves as a command line interface to the ″Display Microcode Level″ task.Display Hardware Vital Product Data This service aid displays all installed resources. This information is logged in the AIX error log and cleared from NVRAM when the system is rebooted from the hard disk. If the device is not a valid IPL device or if the IPL fails. the system. Chapter 27. the information is analyzed when the sysplanar0 diagnostics are running in Problem Determination Mode. or a device by using the AIX diag command. LAN. When booting from Standalone Diagnostics.

The run-time options are: v Display Diagnostic Mode Selection Menus This option allows the user to turn on or off displaying the DIAGNOSTIC MODE SELECTION MENU (the default is on). v Run Tests Multiple Times This option allows the user to turn on or off running the diagnostic in loop mode (the default is off). but it can be changed from one to sixty days. Note: The run-time options are used only when selecting the Run Diagnostic task. The default size for the Diagnostic Event Log is 100 KB. v Include Error Log Analysis This option allows the user to turn on or off including the Error Log Analysis (ELA) (the default is off). The default is seven days. v Include Advanced Diagnostics This option allows the user to turn on or off including the Advanced Diagnostics (the default is off). v Display Progress Indicators This option allows the user to turn on or off the progress indicators when running the Diagnostic Applications. The progress indicators are in a popup box at the bottom of the screen which indicate that the test being run (the default is on). v Diagnostic Event Log File Size This option allows the user to select the maximum size of the Diagnostic Event Log. Note: This option is only displayed when you run the Online Diagnostics in Service Mode.Display or Change Diagnostic Run-Time Options The Display or Change Diagnostic Run-Time Options task allows the diagnostic run-time options to be set. v Diagnostic Event Logging This option allows the user to turn on or off logging information to the Diagnostic Event Log (the default is on). v Number of Days Used to Search Error Log This option allows the user to select the number of days for which to search the AIX error log for errors when running the Error Log Analysis. The size can be increased in 100 KB increments to a maximum of 1 MB. 188 Diagnostic Information for Multiple Bus Systems .

Display Previous Diagnostic Results Note: This service aid is not available when you load the diagnostics from a source other than a hard disk drive or a network. Chapter 27. Introduction to Tasks and Service Aids 189 . The file also contains information about using this particular version of diagnostics. Use the arrow keys to scroll through the information in the file. the user can view up to 25 no trouble found (NTF) and service request number (SRN) results. When the Display Previous Diagnostic Results option is selected. You can display the Diagnostic Event Log in a short version or a long version. This information is stored in the /var/adm/ras directory. This service aid displays Diagnostic Event Log information. This service aid allows a service representative to display results from a previous diagnostic session. If more information is available than can be displayed on one screen. This information is not from the AIX operating system error log. This file contains information that is not contained in the publications for this version of the diagnostics. use the Page Down and Page Up keys to scroll through the information. Display Service Hints This service aid reads and displays the information in the CEREADME file from the diagnostics media. This task is similar to running the lsattr -E -l resource command. The Diagnostic Event Log contains information about events logged by a diagnostic session. This service aid displays the information in reverse chronological order. You can run the command from the AIX command line by typing: /usr/lpp/diagnostics/bin/diagrpt [[-o] | [-s mmddyy] | [-a] | [-r]] Flag -o -s mmddyy -a -r Description Displays the last diagnostic results file stored in the /etc/lpp/diagnostics/data directory Displays all diagnostic result files logged since the date specified Displays the long version of the Diagnostic Event Log Displays the short version of the Diagnostic Event Log Display Resource Attributes This task displays the Customized Device Attributes associated with a selected resource.

Run diagnostics on sysplanar0 to determine what repair action is needed. physical location code.The sensor reading indicates a serious problem with the device. The information displayed is the sensor name. and a reading is not available. This could become a critical problem if action is not taken. v Warning High . The sensor status can be any one of the following: v Normal . and the literal value of the sensor reading. v Warning Low . literal value of the sensor status.The sensor reading indicates a serious problem with the device. Run diagnostics on sysplanar0 to determine what repair action is needed.The system has repeatedly returned a busy indication. 190 Diagnostic Information for Multiple Bus Systems . v Hardware Error . v Hardware Busy . list the sensors and their values in numerical format.Display Software Product Data This task uses SMIT to display information about the installed software and provides the following functions: v List Installed Software v List Applied but Not Committed Software Updates v Show Software Installation History v Show Fix (APAR) Installation Status v List Fileset Requisites v List Fileset Dependents v List Files Included in a Fileset v List File Owner by Fileset Display System Environmental Sensors Note: This service aid runs on CHRP system units only. If the problem continues.The sensor reading indicates a problem with the device. Run diagnostics on sysplanar0 in problem-determination mode to determine what repair action is needed. This service aid can also be run as a command. Run diagnostics on sysplanar0 to determine what repair action is needed. Try the service aid again. v Critical Low . This service aid displays the environmental sensors implemented on a CHRP system.The sensor reading indicates a problem with the device. or a specific sensor can be queried to return either the sensor status or sensor value.The sensor reading is within the normal operating range. run diagnostics on sysplanar0 in problem-determination mode to determine what repair action is needed. This could become a critical problem if action is not taken. v Critical High . You can use the command to list the sensors and their values in a text format.The sensor could not be read because of a hardware error. Run diagnostics on sysplanar0 to determine what repair action is needed.

Run the command by entering one of the following: /usr/lpp/diagnostics/bin/uesensor -l | -a /usr/lpp/diagnostics/bin/uesensor -t token -i index [-v] Flag -l -a Description List the sensors and their values in a text format. index 1: /usr/lpp/diagnostics/bin/uesensor -t 9004 -i 1 9 4. Return the status of sensor 9004. -t token Examples The following are examples from this command: 1. For each sensor. index 1: /usr/lpp/diagnostics/bin/uesensor -t 9004 -i 1 -v 2 Chapter 27. Display a list of the environmental sensors: /usr/lpp/diagnostics/bin/uesensor -l Sensor = Fan Speed Status = Normal Value = 2436 RPM Location Code = F1 Sensor = Power Supply Status = Normal Value = Present and operational Location Code = V1 Sensor = Power Supply Status = Critical low Value = Present and not operational Location Code = V2 2. Indicates to return the sensor measured value. Return the value of sensor 9004. -i index -v Specifies the sensor index to query. List the sensors and their values in a numerical format. the following numerical values are displayed as: token index status measured value location code Specifies the sensor token to query. Display a list of the environmental sensors in a numerical list: /usr/lpp/diagnostics/bin/uesensor -a 3 0 11 9001 0 9004 0 9004 1 87 P1 11 2345 F1 11 2 V1 9 2 V2 3. The sensor status is returned by default. Introduction to Tasks and Service Aids 191 .

The service aid presents a list of adapters and devices that use microcode. go to the diagnostics ″TASKS SELECTION″ menu. v Display a list of USB devices that are connected to the selected controller. A list of devices attached to the controller displays. the service aid provides menus to guide you in checking the current level and downloading the needed microcode. See the following sections for instructions on downloading to a particular type adapter or device. where ″X″ is a number. The user works through a series of menus to select the display type and test pattern.Display Test Patterns This service aid provides a means of adjusting system display units by providing displayable test patterns. the test pattern displays. To run the USB devices service aid. Download Microcode This service aid provides a way to copy microcode to an adapter or device. This task can be run directly from the AIX command line. Display USB Devices The following are the main functions of this service aid: v Display a list of USB controllers on an adapter. After the adapter or device is selected. From the controller list that displayed on the screen. After the selections are made. select one of the items that begins with ″OHCDX″. select ″Display USB Devices″. Download Microcode to PCI SCSI RAID Adapter See the following command syntax for a PCI SCSI RAID Adapter: diag -c -d RAIDadapterName -T "download [-B] [-D] [-P]" Flag -B -D -P Description Download boot block microcode (default to functional microcode) Microcode is on diskette (default to /etc/microcode directory) Download the previous level of microcode (default to latest level) Download Microcode to Disk Drive Attached to a PCI SCSI RAID Adapter See the following command syntax for a disk drive attached to a PCI SCSI RAID Adapter: diag -c -d RAIDadapterName -T "download {-l chID | -A} [-D] [-P]" Flag -A -D -l -P Description All disk drives Microcode is on diskette (default to /etc/microcode directory) RAID disk drive-physical disk channel/ID (example 27) Download the previous level of microcode (default to latest level) 192 Diagnostic Information for Multiple Bus Systems .

Introduction to Tasks and Service Aids 193 . for example. It is recommended that a current backup be available and the installation be scheduled during a non-peak production time period. Source of the new microcode image. for example. -l Level of microcode image to be installed.Download Microcode to a PCI FC-AL Adapter Microcode installation occurs while the adapter and attached drives are available for use. The default is /etc/microcode. Use the download option to download microcode. diag -c -d device_name -T "download [-s {/etc/microcode|diskette}] [-l {latest|previous}] [-f]" Flag -c -d -T -s -l -f Description No console mode. -s Source of the new microcode. Default is /etc/microcode. hdisk0. Download Microcode to DVD-RAM Attached to a PCI SCSI Adapter See the following command syntax for a DVD-RAM attached to a PCI SCSI Adapter: diag [-c] -d cdX -T "download [-s {/etc/microcode|diskette}] [-l {latest|previous}] [-f]" Flag -c cdX -s -l -f Description No console mode. See the following command syntax for a PCI FC-AL Adapter. Source of the new microcode. Run without user interaction -d hdiskX Selected device. the diskette must be in a backup format and the image stored in the /etc/microcode directory. Force the installation even if the current level of microcode is not on the source. Chapter 27. Level of microcode image to be installed. Device name is the name of the adapter. Run without user interaction Device selected. -T download Download microcode task. cd0. The default is /etc/microcode. Download Microcode to Disk Attached to PCI SCSI Adapter See following command syntax for a disk drive attached to a PCI SCSI adapter: diag [-c] -d hdiskX -T "download [-s {/etc/microcode|diskette}] [-l {latest|previous}] [-f]" Flag Description -c No console mode. Note: If the source is diskette. Run without user interaction. Latest in default Install the microcode on the device even if the current level is unavailable on the source. Latest in default -f Install the microcode on the device even if the current level is unavailable on the source. Level of microcode to install. The default is latest.

Microcode level.Download Microcode to Other Devices See the following command syntax: diag -c -d device_name -T "download [-s diskette] [-l previous] [-F]" Flag -F -l -s Description Force the download microcode even if the current level is unavailable on the source. Latest is default. Use the following fastpath command: diag -T "certify" Certify Spare Physical Disk This selection allows the user to certify (check integrity of the data) drives that are designated as spares. 194 Diagnostic Information for Multiple Bus Systems . Use the following fastpath command: diag -T "format" Array Controller Microcode Download This selection allows the microcode on the Fibre Channel RAID controller to be updated when required. Fibre Channel RAID Service Aids The Fibre Channel RAID service aids contain the following functions: Certify LUN This selection reads and checks each block of data in the logical unit number (LUN). Source of the new microcode. Default source device is disk. Use the following fastpath command: diag -T "download" Physical Disk Microcode Download This selection is used to update the microcode on any of the disk drives in the array. Replace Controller Use this selection when it is necessary to replace a controller in the array. Use the following fastpath command: diag -T "certify" Format Physical Disk This selection is used to format a selected disk drive. If excessive errors are encountered. You can run this task from the AIX command line. The default is /etc/microcode. You can run this task from the AIX command line. You can run this task from the AIX command line. You can run this task from the AIX command line. You can run this task from the AIX command line. the user is notified. Use the following fastpath command: diag -T "download" Update EEPROM This selection is used to update the contents of the electronically erasable programmable read-only memory (EEPROM) on a selected controller.

Format Media This task allows the selection of diskettes. Run a second pass of the Erase Disk selection. record the information presented and ensure that this information is kept with the drive. there may be some blocks which get placed into the grown defect MAP. for example some drives may write all 0s. For a newly installed drive. specify the number (0-3) of patterns to be written. Note: If you use the Format and Certify option. The Erase Disk option writes one or more patterns to the disk. An additional option allows data in a selectable block to be read and displayed on the system console. that is. Chapter 27. overlaying the previous pattern. A random pattern is written by selecting the Write Random Pattern? option. you can ensure that all blocks on the drive are overwritten with your pattern if you use the following procedure: 1. 2. Each selection is described below. Use the Erase Disk selection to overwrite the data on the drive. 3. hardfiles. 4. 2. Then the next pattern is written to all blocks. 3. To use the Erase Disk option.Flash SK-NET FDDI Firmware This task allows the Flash firmware on the SysKonnect SK-NET FDDI adapter to be updated. Use the drive as you would normally. Check the defect MAP by running the Erase Disk selection. v Hardfile Erase Disk This option can be used to overwrite (remove) all data currently stored in user-accessible blocks of the disk. If there are bad blocks in the defect MAP. Introduction to Tasks and Service Aids 195 . or optical media to be formatted. Format the drive. No bad block reassignment occurs v Hardfile Format and Certify Performs the same function as Hardfile Format. the first pattern is written to all blocks. Note: The Erase Disk service aid has not been certified as meeting the Department of Defense or any other organization’s security guidelines. The pattern written on the disk is device-dependent. Use the following steps to overwrite the data on the drive: 1. This data is used later when the drive is to be overwritten. Certify then reassigns all bad blocks encountered. Do a format without certify. Hardfile Attached to SCSI Adapter (non-RAID) v Hardfile Format Writes all of the disk. while some may write the hexadecimal number 5F. The patterns are written serially. After the format is completed. Certify is run.

6. This task can be run directly from the AIX command line. continue running the service aid to overwrite the disk with the chosen pattern(s). See the following command syntax: diag -c -d RAIDadapterName -T "format {-l chId | -A }" Flag -l -A Description Physical disk channel/ID (An example of a physical disk channel/ID is 27. When the drive is no longer needed and is to be erased. 196 Diagnostic Information for Multiple Bus Systems . This function reassigns the defective blocks and erases all data on the media. v Optical Media Format and Certify Formats and certifies the media. If the bad block list is the same. where the channel is 2 and the ID is 7. This option provides a quick way of formatting the media and cleaning the disk. See the command syntax: diag -c -d deviceName -T "format [-s* fmtcert | erase -a {read | write}] [-F]" Flag fmtcert * -F Description Formats and certifies the disk. then all sectors on this drive cannot be overwritten. The new bad blocks are not overwritten. This function does not reassign the defective blocks or erase the data on the media. Compare the bad blocks which were recorded for the drive in step 3 with those that now appear in the grown defect MAP.5. run the same version of the Erase Disk selection which was used in step 2. 7. Note: The Erase Disk option in command line mode uses default values. Note: It takes approximately one minute to format the media. To selectively read or write. use the diag command in console mode. Available in no-console mode only. Force the disk erasure even if all blocks cannot be erased due to errors accessing grown defect map. Hardfile Attached to PCI SCSI RAID Adapter This function formats the physical disks attached to a PCI SCSI RAID adapter. Note: If there are differences between the saved data and the newly obtained data. This task can be run directly from the AIX command line.) All disks Optical Media Use the following functions to check and verify optical media: v Optical Media Initialize Formats the media without certifying. Note: Using the same version of the service aid is only critical if any bad blocks were found in step 3.

Running the Generic Microcode Download task will search for the genucode script on diskette or tape and execute it. Introduction to Tasks and Service Aids 197 . The genucode program should be downloaded onto diskette or tape in tar format while the microcode image itself goes onto another one in restore format. filesystems. select Gather System Information from the task list. See the following command syntax: diag -c -d deviceName -T "format [-s {initialize | fmtcert} ]" Option Description initialize Formats media without certifying fmtcert Formats and certifies the media Diskette Format This selection formats a diskette by writing patterns to it. This task was previously known as ″SCSI Device Identification and Removal″ or ″Identify and Remove Resource. To use the SNAP task. You can also choose to collect SSA adapter and disk drive configuration data. and some RAID devices. It will ask for a Genucode media to be inserted into the drive. or AIX trace information for software debugging.″ Chapter 27. You can select which components you want to collect information for. The service aid moves the genucode script file to the /tmp directory and runs the program that downloads the microcode to the adapter or device.This task can be run directly from the AIX command line. or loadable media. Generic Microcode Download The Generic Microcode Download service aid provides a means of executing a genucode script from a diskette or tape. security. This service aid is supported in both concurrent and standalone modes from disk. the kernel. Hot Plug Task The Hot Plug Task provides software function for those devices that support hot-plug or hot-swap capability. The output of the SNAP service aid can be used by field service personnel or it can be put on removable media and transferred to remote locations for more extensive analysis. and other system components. and where to store the data (hard disk or removable media). This includes PCI adapters. the ODM. LAN. The purpose of this generic script is to load microcode to a supported resource. SCSI devices. Gather System Information This service aid uses the AIX snap command to collect configuration information on networks.

or replace PCI adapters that are hot-pluggable. work through each menu to complete device configuration. The Add a PCI Hot Plug Adapter function is used to prepare a slot for the addition of a new adapter. After the slot location is confirmed. Depending on the environment and the software packages installed. The Replace/Remove a PCI Hot Plug Adapter function is used to prepare a slot for adapter exchange. The following functions are available under this task: v List PCI Hot Plug Slots v Add a PCI Hot Plug Adapter v Replace/Remove a PCI Hot Plug Adapter v Identify a PCI Hot Plug Slot v Unconfigure Devices v Configure Devices v Install/Configure Devices Added After IPL The List PCI Hot Plug Slots function lists all PCI hot-plug slots. new devices may not be added to the system unless there is already a device with the same FRU part number installed in the system. The function lists all the empty slots that support hot plug. Populated slot information includes the connected logical device. type the following: diag -T"identifyRemove" If you are running the diagnostics in Online Concurrent mode. PCI Hot Plug Manager The PCI Hot Plug Manager task is a SMIT menu that allows you to identify. This restriction is in place because the device software package for the new device cannot be installed in Standalone or Online Service mode.The Hot Plug Task has a restriction when running in Standalone or Online Service mode. add. removing or replacing any device. When a slot is selected. selecting this task displays the following three subtasks: v PCI Hot Plug Manager v SCSI Hot Swap Manager v RAID Hot Plug Devices To run the Hot Plug Task directly from the command line. the visual indicator for the specified PCI slot is set to the Action state. This means the power for the PCI slot is off and the new adapter can be plugged in. run the Missing Options Resolution Procedure immediately after adding. Start the Missing Options Resolution Procedure is by running the diag -a command. the visual indicator for the slot blinks at the Identify rate. Empty slots and populated slots are listed. remove. The function lists all the PCI slots that support hot plug and are 198 Diagnostic Information for Multiple Bus Systems . then device configuration is complete. If the Missing Options Resolution Procedure runs with no menus or prompts. The slot name consists of the physical location code and the description of the physical characteristics for the slot. Otherwise.

The adapter must be in the Defined state before it can be prepared for hot-plug removal.occupied. When a slot is selected for identification. the visual indicator for the slot is set to the Identify state. v The following functions are not available from the Standalone Diagnostics and will not display in the list: – Add a PCI Hot Plug Adapter – Configure Devices – Install/Configure Devices Added After IPL You can run this task directly from the command line by typing the following command: diag -d device -T"identifyRemove" However. The Configure Devices function allows a newly added adapter to be configured into the system for use. because the configuration information for the new adapter is not known after the Standalone Diagnostics are booted. then the Hot Plug Task displays instead of the PCI Hot Plug Manager menu. If the unconfigure function fails. The software installation media or packages are required for this function. in the PCI hot-plug slot. the visual indicator for the slot is set to the Identify state. The Unconfigure Devices function attempts to put the selected device. is off and the adapter can be removed or replaced. the visual indicator for the specified PCI slot is set to the Action state. If this is the case for the device specified. This function should also be done when a new adapter is added to the system. Standalone Diagnostics has restrictions on using the PCI Hot-Plug Manager. The list includes the slot’s physical location code and the device name of the resource installed in the slot. In this case. System Management Guide. This means the power for the PCI slot. The Install/Configure Devices Added After IPL function attempts to install the necessary software packages for any newly added devices. v New adapters cannot be added unless a device of the same FRU part number already exists in the system. More detailed information concerning PCI Hot-Plug Manager can be found in the AIX Operating System. This action must be done before any attempted hot-plug function. into the Defined state. When a slot is selected. the customer or system administrator must be notified to quiesce the device. For example: v Adapters that are replaced must be exactly the same FRU part number as the adapter being replaced. Introduction to Tasks and Service Aids 199 . Chapter 27. note that some devices support both the PCI Hot-Plug task and the RAID Hot-Plug Devices task. The Identify a PCI Hot Plug Slot function is used to help identify the location of a PCI hot-plug adapter. it is possible that the device is still in use by another application. After the slot location is confirmed. The function lists all the PCI slots that are occupied or empty and support hot plug.

After a slot is selected. The Replace/Remove a Device Attached to an SES Device function lists all populated hot-swap slots that are available for removal or replacement of the devices. When a slot is selected for identification. In this case. the device populating that slot is Unconfigured. and replace a SCSI device in a system unit that uses a SCSI Enclosure Services (SES) device. If the Unconfigure operation fails. This task allows the user to identify. the visual indicator for the selected slot is set to the Normal state. the visual indicator. device name. the visual indicator for the selected slot is set to the Remove state. then the power is removed from that slot. Note: Be sure that no other host is using the device before you remove it. the customer or system administrator must be notified to quiesce the device. whether the slot is populated and configured. the visual indicator for the slot is set to the Identify state. it is possible that the device is in use by another application.SCSI Hot Swap Manager This task was known as ″SCSI Device Identification and Removal″ or ″Identify and Remove Resources″ in previous releases. 200 Diagnostic Information for Multiple Bus Systems . remove. if available for the selected slot. After the device is added. This function lists all the slots that support hot swap that are occupied or empty. The status information available includes the slot number. Status information about each slot is also available. The following functions are available: v List the SES Devices v Identify a Device Attached to an SES Device v Attach a Device to an SES Device v Replace/Remove a Device Attached to an SES Device v Configure Added/Replaced Devices The List the SES Devices function lists all the SCSI hot-swap slots and their contents. After a slot is selected. and location. If available. The Identify a Device Attached to an SES Device function is used to help identify the location of a device attached to a SES device. the power is removed. add. The Attach a Device to an SES Device function lists all empty hot-swap slots that are available for the insertion of a new device. the visual indicator for the selected slot is set to the Remove state. is set to the Normal state. and power is restored. If the Unconfigure operation is successful. and power is restored. After the device is removed or replaced.

Specifies the task to run. For example: v Devices being used as replacement devices must be exactly the same type of device as the device being replaced. Introduction to Tasks and Service Aids 201 . and error log analysis should not be done for any errors logged before the repair action. The Log Repair Action task lists all resources. v Monitoring ring (Token-Ring only). The following services are available: v Connectivity testing between two network stations. Log Repair Action The Log Repair Action task logs a repair action in the AIX Error Log. Run the task without displaying menus. See the following command syntax: diag -d device-T"identifyRemove" OR diag [-c] -d device -T"identifyRemove -a [identify|remove]" Flag -a -c -d -T Description Specifies the option under the task. v New devices may not be added unless a device of the same FRU part number already exists in the system. RAID Hot Plug Devices This selection starts the PCI SCSI-2 F/W RAID Adapter Service Aid. Replaced resources can be selected from the list. This function ensures that the devices in the configuration database are configured correctly. You can run this task directly from the command line. Local Area Network Analyzer This selection is used to exercise the LAN communications adapters (Token-Ring. Indicates the SCSI device. and when commit (F7 key) is selected. The ring is monitored for a specified period of time. Only command line prompts are used. a repair action is logged for each selected resource. Data is transferred between the two stations. Soft and hard errors are analyzed. Chapter 27. because the configuration information for the new device is not known after the Standalone Diagnostics are booted. Standalone Diagnostics has restrictions on using the SCSI Hot Plug Manager. A Repair Action log indicates that a FRU has been replaced. requiring the user to provide the Internet addresses of both stations. Ethernet.The Configure Added/Replaced Devices function runs the configuration manager on the parent adapters that had child devices added or removed. This flag is only applicable when running an option such as identify or remove. “Log Repair Action” on page 142. For more information see. and (FDDI) Fiber Distributed Data Interface).

or a mail message to the users belonging to the system group containing information about the failure. If the resource cannot be tested because it is busy. Run diagnostics after each supplemental media is processed. Insert the supplemental media when you are prompted. go to the Resource Selection list to find the resource to test. If a problem is detected. The service aid provides the following functions: v Add or delete a resource to the periodic test list v Modify the time to test a resource v Display the periodic test list v Modify the error notification mailing list v Disable or Enable Automatic Error Log Analysis PCI RAID Physical Disk Identify This selection identifies physical disks connected to a PCI SCSI-2 F/W RAID adapter. You can run this task directly from the AIX command line. Once after each supplement media is processed. If you need to process two supplemental media you need to run diagnostic twice. Process and test one resource at a time. then press Enter. This allows error log analysis to be performed every time a hardware error is put into the error log. This task is supported in Standalone Diagnostics only. Notes: 1. error log analysis is performed.Periodic Diagnostics This selection provides a tool for configuring periodic diagnostics and automatic error log analysis. such as the service request number. at a user-specified time. This task processes the Diagnostic Supplemental Media. See the following command syntax: diag -c -d pci RAID adapter -T identify Process Supplemental Media Diagnostic Supplemental Media contains all the necessary diagnostic programs and files required to test a particular resource. After processing has completed. 2. a message is posted to the system console and either sent to the Service Focal Point when there is an attached HMC.) 202 Diagnostic Information for Multiple Bus Systems . Hardware errors logged against a resource can also be monitored by enabling Automatic Error Log Analysis. You can select a hardware resource to be tested once a day. (for example. Diagnostic Supplemental Media must be used when the device support has not been incorporated into the latest diagnostic CD-ROM. The supplemental media is normally released and shipped with the resource as indicated on the diskette label.

The exercisers runs 5 to 10 minutes depending on the number of processors. and to verify replacement parts. See “Display or Change Diagnostic Run-Time Options” on page 188. the Run Error Log Analysis task can be used to analyze errors after the exerciser completes. Miscompares and recoverable errors are not reported. diagnostics are run on all selected resources. In addition to individual exerciser requirements. Error Log Analysis is run on all selected resources. Please read any text and carefully fill out any prompts before committing. When the commit key is pressed. (The popup does not appear if the task had previously been selected). From this menu choose the resources you want to exercise and then select commit to start the Run Exerciser task.Run Diagnostics The Run Diagnostics task invokes the Resource Selection List menu. processor Chapter 27. the following requirements pertain to all exercisers: v Only supported on CHRP platforms v Only supported in concurrent or service modes v Not supported from standalone diagnostics v System performance will be degraded while running the exerciser. When the commit key is pressed. they may be logged in the AIX Error Log when logging thresholds are exceeded. After choosing the Short Exercise option. When AIX error logging is enabled. Next. so it is recommended that customer applications be shut down before it is run. Run Exercisers The Run Exercisers task provides a tool to troubleshoot intermittent system problems in AIX 4. the exercisers start. The Extended Exercise option allows greater flexibility and control over resources and test duration. v At least 1 MB of free storage in /tmp is available From the TASK SELECTION LIST menu select Run Exercisers then the RESOURCES SELECTION LIST menu displays. however. to test hardware. The Short Exercise option exercises the resources within a relatively short time and exits. The procedures for running the diagnostics depends on the state of the diagnostics run-time options. Hardware errors are logged in the AIX Error Log. The EXERCISER OPTIONS menu displays two options (1) Short Exercise and (2) Extended Exercise. pop-ups and prompts may appear for each resource.3. These files are deleted before an exerciser session begins. Introduction to Tasks and Service Aids 203 . and the Device Status Screen displays. An intermediate popup may appear stating system performance will be degraded. The diagnostic supervisor typically sets up temporary work files in /tmp to log messages and device statistics. Run Error Log Analysis The Run Error Log Analysis task invokes the Resource Selection List menu. Press Enter and the EXERCISER OPTIONS menu prompts for the type of test to run. additional menus.2 or later.

From this menu the exercisers can be activated through option 1 where they will continuously run until halted (option 2) or exited (option x). you will be taken back to the TASK SELECTION LIST menu. Acronym COE CP DD ER HG HOE RN ST Description Continue on error (use number to select). memory size. Please read any text and carefully fill out any prompts before committing. an Exerciser Complete popup displays. Device has run the specified number of cycles and is not running. The device is hung. the System Exerciser Main Menu displays. The exerciser has been terminated by a signal. 204 Diagnostic Information for Multiple Bus Systems . select and run the Error Log Analysis task. Exerciser Commands (CMD) Use the following commands as needed in the exerciser menus and reports. See also the help text for information on how to use other available options. CMD a b c e f q r s x Description Acknowledge an error Back one page Toggle between cycle count and last error View the AIX error log Page forward one page Return to Main Menu Refresh screen Enable or disable beep on error Exit system exerciser Abbreviations The following list describes abbreviations used in the exerciser reports.speed. If any other errors were encountered. press the Enter key. pop-ups and prompts may appear for each resource. To continue. run diagnostics on the resource. If Error Log Analysis does not report a problem then contact your service support structure. Following. Not all commands are available in each menu or report. Following. After choosing the Extended Exercise option. Device has stopped with an error. additional menus. If the problem is not reported then contact your service support structure. If miscompare errors were encountered. Finally. When the task completes any errors that were encountered are displayed for review. Halt on error (use number to select). Device is running. and I/O configuration. Device is stopped.

A scratch diskette is required to run this exerciser. Introduction to Tasks and Service Aids 205 . Tape Exerciser The tape exerciser is labeled rmtx. where x is the number of a specific device. On systems with multiple processors. where x is the number of a specific device. a process is started for each processor. Multiple exercisers can be active. Test requirements are: v Diskette device v Scratch diskette (data on diskette is destroyed) CD-ROM Exerciser The CD-ROM exerciser is labeled cdx. The exerciser performs read and compare operations using known data patterns. Running this service aid requires 128 KB of free space in /etc/lpp/diagnostics/data. and compare operations using known data patterns. The exerciser then fills the memory buffers with specified bit patterns. The exerciser performs read. A CD-ROM device and a Test Disc is required to run this exerciser. A tape device and Test Diagnostic Cartridge are required to run this exerciser. Test requirements are: v CD-ROM device v Test Disc P/N 81F8902 Chapter 27. data on the scratch diskette is destroyed.Memory Exerciser The memory exercisers are labeled memx. where x is the number of a specific device. where x is a number for the exerciser. The exerciser automatically rewinds the tape. The actual Test Diagnostics Cartridge depends upon the specific tape device being tested. (P/N depends upon tape device) Diskette Exerciser The diskette exerciser is labeled fdx. write. The free memory space is split evenly between the available processors. The memory exerciser requests as many memory buffers as possible from AIX. Test Requirements are: v Tape device v Test Diagnostic Cartridge. then reads and compares the memory buffers to the specified bit patterns. The exerciser performs read. and compare operations using known data patterns. thus reducing the time required to exercise all of the memory. write.

by typing: /usr/lpp/diagnostics/bin/uspchrp -a Save or Restore Service Processor Configuration Note: This service aid runs on RSPC system units only. Remote Maintenance Policy and Reboot Policy. Surveillance Policy. The Service Processor Configuration includes the Ring Indicator Power-On Configuration. The following options are available: v Save Hardware Management Policies This selection writes all of the settings for the hardware-management policies to the following file: /etc/lpp/diagnostics/data/hmpolicies v Restore Hardware Management Policies This selection restores all of the settings for the hardware-management policies from the contents of the following file: /etc/lpp/diagnostics/data/hmpolicies You can access this service aid directly from the AIX command line.Save or Restore Hardware Management Policies Note: This service aid runs on CHRP system units only. The following options are available: v Save Service Processor Configuration This selection writes all of the settings for the Ring Indicate Power On and the Service Processor to the following file: /etc/lpp/diagnostics/data/spconfig v Restore Service Processor Configuration This selection restores all of the settings for the Ring Indicate Power On and the Service Processor from the following file: /etc/lpp/diagnostics/data/spconfig 206 Diagnostic Information for Multiple Bus Systems . Use this service aid to save or restore the Service Processor Configuration to or from a file. Use this service aid to save or restore the settings from Ring Indicate Power-On Policy.

When the SCSI Bus Service Aid is started a description of the service aid displays. To use this service aid. If an error occurs or a response is received. Use this menu to enter the address to transmit the SCSI Inquiry Command. the SCSI Bus Test Run menu displays. ensure that it is working. Use this menu to transmit the SCSI Inquiry Command by pressing Enter. Use this service aid when the diagnostics cannot communicate with anything on the SCSI bus and cannot isolate the problem. When the adapter is selected. then start adding additional devices and cables to the bus. the SCSI Bus Address Selection menu displays. the service aid displays a timeout message. Pressing the Enter key displays the Adapter Selection menu. Use this menu to enter the address to transmit the SCSI Inquiry Command. After the address is selected. Notes: 1. v The service aid transmitted a SCSI Inquiry Command and did not receive any response or error status back. Introduction to Tasks and Service Aids 207 . If no response is received within a defined amount of time. This service aid works with any valid SCSI bus configuration. 2. Normally the procedure for finding a problem on the SCSI bus with this service aid is to start with a single device attached. When the transmission is completed.SCSI Bus Analyzer This service aid allows you to diagnose a SCSI bus problem in a freelance mode. AIX does not allow the command to be sent if the device is in use by another process. ensuring that each one works. The SCSI Bus Service Aid transmits a SCSI Inquiry command to a selectable SCSI Address. the service aid then displays one of the following messages: v The service aid transmitted a SCSI Inquiry Command and received a valid response back without any errors being detected. v The service aid transmitted a SCSI Inquiry Command and the adapter indicated a SCSI bus error. v The service aid transmitted a SCSI Inquiry Command and an adapter error occurred. the results of the transmission displays. the user should understand how a SCSI bus works. The service aid then waits for a response. Chapter 27. A Check Condition can be returned when the bus or device is working correctly. The service aid then indicates the status of the transmission. v The service aid transmitted a SCSI Inquiry Command and a check condition occur.

v Copy a tape drive’s trace table. When the trace table is written to a disk file. If the -c is not used. The service aid prompts for a file name when you have selected that the log sense data is to be copied to a file. Copy trace table.SCSD Tape Drive Service Aid This service aid allows you to obtain the status or maintenance information from a SCSD tape drive. See the following command syntax (path is /usr/lpp/diagnostics/bin/utape): utape [-h | -?] [-d device] [-n | -l | -t] OR utape -c -d device [-v] {-n | {-l | -t} { -D | -f [ filename]}} Flag -c Description Run the service aid without displaying menus. -D -f -h. The complete trace table consists of the sequential concatenation of all the diskette data files. v Display or copy a tape drive’s log sense information. to copy it to a DOS formatted diskette. The output is suppressed except for the usage statement and the numeric value for hours since cleaning (if -n and -D flags are used). or to copy it to a file. Verbose mode. The diskettes must be formatted for DOS. The actual number of diskettes is determined by the size of the trace table. The default name is: /tmp/TRACE. If the -c flag is present. Label the diskettes as follows: TRACEx. If the -c flag is present.x. a usage statement displays and the service aid exits. Writing the trace table may require several diskettes. Not all models of SCSD tape drive are supported. The service aid provides options to display the log sense information to the screen. Copy data to diskette. Display time since drive was last cleaned. Display or copy log sense information. the service aid prompts for a file name.DAT (where x is a sequential diskette number). only the return code displays to indicate the service aid did not run. The service aid provides the following options: v Display time since a tape drive was last cleaned. Display a usage statement and/or return code. The return code indicates success or failure. This service aid can be run directly from the AIX command line. the information about tape-head cleaning is printed. -? -l -n -t -v 208 Diagnostic Information for Multiple Bus Systems . where x is the AIX name of the SCSD tape drive being tested. If the -n flag is present.DAT is used when the log sense data is written to the diskette. as well as a message regarding whether the drive is recommended to be cleaned. Copy data to the file name given after this flag or to a default file name if no name is specified. The file name LOGSENSE. The trace table of the tape drive is written to diskettes or a file. The time since the drive was last cleaned displays on the screen. the information displays on the screen.

Introduction to Tasks and Service Aids 209 . See the following command syntax: diag -c -d deviceName -T chkspares SSA Service Aid This service aid provides tools for diagnosing and resolving problems on SSA-attached devices. Formatting the disk does not improve the availability of spare sectors. The spare sectors are used to reassign when defective sectors are encountered during normal usage or during a format and certify operation. Low availability of spare sectors indicates that the disk needs to be backed up and replaced.Spare Sector Availability This selection checks the number of spare sectors available on the optical disk. The following tools are provided: v Set Service Mode v Link Verification v Configuration Verification v Format and Certify Disk Chapter 27. You can run this task directly from the AIX command line.

This indicator is set automatically by hardware firmware. If the serviceable event was not the result of an error log entry.System Fault Indicator This task is used to display or reset the system fault indicator on systems that support this function. or diagnostics when a fault is detected in the system. Use the following example to run this task directly from the AIX command line: /usr/lpp/diagnostics/bin/usysfault [-s normal] Flag -s Description Normal. the current state of the indicator displays. Note: The AIX command does not allow you to set the system fault indicator to the Fault state. sets the system fault indicator to the Normal state. also do a Log Repair Action if the test on the resource was good and that resource had an entry in the error log. When this command is used without the -s flag. Refer to the system unit service guide for additional information concerning the use of this indicator. do a System Verification to verify the fix. 210 Diagnostic Information for Multiple Bus Systems . but the system fault indicator is set back to Normal when you exit this task. The system fault indicator is turned off when a Log Repair Action is performed. At this time. After a serviceable event is complete. use the Log Repair Action task to turn off the system fault indicator. This task is also used to set the system fault indicator for testing purposes. The system fault indicator is used to identify a fault with the system.

newer systems have a combined image that contains both in one image. v If a service partition has not been designated. Update Disk-Based Diagnostics This service aid allows fixes (APARs) to be applied. Use the following example to run this task directly from the AIX command line: /usr/lpp/diagnostics/bin/usysident [-s {normal | identify}] Flag -s {normal | identify} Description Sets the state of the System Identify Indicator to either Normal or Identify. ask the customer or system administrator to shut down all of the partitions except the one with service authority. If the system is already in a full machine partition. Introduction to Tasks and Service Aids 211 . You can install any APAR using this task. the current state of the indicator displays. Some systems may have separate images for system and service processor firmware. The task allows the input device and APARs to be selected. the firmware update can then be done from the service processor menus as a privileged user. use the following normal firmware update procedures: Note: This service aid runs on CHRP system units only. reboot the system in a full machine partition and use the following normal firmware update procedures.System Identify Indicator This task is used to display or set the system identify indicator on systems that support this function. This selection updates the system or service processor flash for CHRP system units. If the firmware update image is available on backup diskettes. This task invokes the SMIT Update Software by Fix (APAR) task. When this command is used without the -s flag. Refer to the system unit service guide for additional information concerning the use of this indicator. The system identify indicator is used to help physically identify a particular system in group of systems. v If it has. If the firmware update image is in a file on the system. Chapter 27. the system must be shut down. The firmware update can then be done using the service aid or the AIX command line in that partition. ask the customer or system administrator if a service partition has been designated. Update System or Service Processor Flash Attention: If the system is running on a logically partitioned system.

When this service aid is run from standalone diagnostics. and retry the service aid. The diskette must be a valid backup format diskette. the microcode image must first be copied onto the NIM server in the /usr/lib/microcode directory pointed to the NIM SPOT (from which you plan to have the NIM client boot standalone diagnostics) prior to performing the NIM boot of diagnostics. or the service guide for the system unit to determine the current level of the system unit or service processor flash memory. The system does not return to the diagnostics. If the update image file is on a diskette. When this service aid is run from online diagnostics. The default device_name is /dev/fd0. The command syntax is as follows: update_flash [-q] -f file_name update_flash [-q] -D device_name -f file_name update_flash [-q] -D update_flash [-q] -D device_name -l Flag -D -f Description Specifies that the flash update image file is on diskette. a screen requests confirmation before continuing with the flash update. Flash update image file source. an error is reported. If there is not enough space in the /var file system for the new flash update image file. If using the NIM server.Look for additional update and recovery instructions with the update kit. When you continue the update flash. and the current flash image is not saved. Refer to the update instructions with the kit. The device_name variable specifies the diskette drive. It is recommended that the source of the microcode that you want to download be put into the /etc/microcode directory on the system. Next. an error is reported. After the file is copied. stating additional system memory is needed. a NIM check operation must be run on the SPOT containing the microcode image on the NIM server. the system reboots using the reboot -u command. If not enough space is available. After the file is copied. The file_name variable specifies the fully qualified path of the flash update image file. After performing the NIM boot of diagnostics one can use this service aid to update the microcode from the NIM server by choosing the /usr/lib/microcode directory when prompted for the source of the microcode that you want to update. increase the size of the /var file system. the system reboots using the shutdown -u command. the flash update image file is copied to the /var file system. the user must provide the image on backup format diskette because the user does not have access to remote file systems or any other files that are on the system. You need to know the fully qualified path and file name of the flash update image file provided in the kit. a screen requests confirmation before continuing with the flash update. you can ignore this message. When you continue with the update. The command is located in the /usr/lpp/diagnostics/bin directory. You can use the update_flash command in place of this service aid. the service aid can list the files on the diskette for selection. After the reboot. 212 Diagnostic Information for Multiple Bus Systems . you can remove the /var/update_flash_image file. the flash update image file is copied to the file system from diskette or from the NIM server. Using a diskette. exit the service aid. The current flash image is not saved. You may receive a Caution: some process(es) wouldn’t die message during the reboot process. If this error occurs.

Forces the update_flash command to update the flash EPROM and reboot the system without asking for confirmation. Chapter 27. Introduction to Tasks and Service Aids 213 . Attention: The update_flash command reboots the entire system.-l -q Lists the files on a diskette. Do not use this command if more than one user is logged on to the system. from which the user can choose a flash update image file.

The diskettes can be in DOS or backup format. 7135 RAIDiant Array Service Aid The 7135 RAIDiant Array service aids contain the following functions: v Certify LUN Reads and checks each block of data in the logical unit number (LUN). v Format Physical Disk Formats a selected disk drive. If excessive errors are encountered. v Replace Controller Replaces a controller in the array. The current flash image is not saved. increase the file size of the /var file system. The flash update image is copied to the /var file system. If not enough space is available in the file system for the flash update image file. The command automatically removes the /var/update_flash_image file. the user is notified. This selection updates the system flash for RSPC systems. v Array Controller Microcode Download Allows the microcode on the 7135 controller to be updated when required.Update System Flash Note: This service aid runs on RSPC system units only. If this error occurs. v Physical Disk Microcode Download Updates the microcode on any of the disk drives in the array. the command reboots the system twice to complete the flash update. v Update EEPROM Updates the contents of the EEPROM on a selected controller. an error is reported. The user provides a valid binary image either on a diskette or with a qualified path name. 214 Diagnostic Information for Multiple Bus Systems . After user confirmation. v Certify Spare Physical Disk Allows the user to certify (check the integrity of the data) on drives designated as spares.

Chapter 27. Introduction to Tasks and Service Aids 215 .Command Examples Use this command syntax to download the adapter microcode: diag -c -d deviceName -T "download [-B][-D][-P]" Flag -B -D -P Description Download boot block microcode (default to functional microcode) Microcode is on diskette (default to /etc/microcode directory) Download the previous level of microcode (default to latest level) Use this command syntax to download physical disk microcode: diag -c -d deviceName -T "download -l ChId [-D][-P]" Flag -D -l -P Description Microcode is on diskette (default to /etc/microcode directory) Physical disk channel/ID (for example. 23) Use this command syntax to identify a physical disk: diag -c -d deviceName -T "identify" 7318 Serial Communications Network Server Service Aid This service aid provides a tool for diagnosing terminal server problems. 27) Use this command syntax to certify a physical disk: diag -c -d deviceName -T "certify -l ChId″ Flag -l Description Physical disk channel/ID (for example. 27) Download the previous level of microcode (default to latest level) Use this command syntax to format a physical disk: diag -c -d deviceName -T "format -l ChId″ Flag -l Description Physical disk channel/ID (for example.

216

Diagnostic Information for Multiple Bus Systems

Chapter 28. Diagnostics Numbers and Location Codes
This chapter provides descriptions for the numbers and characters that display on the operator panel and descriptions of the location codes used to identify a particular item.

Operator Panel Display Numbers
This section contains a list of the various numbers and characters that display in the operator panel display. There are three categories of numbers and characters. The first group tracks the progress of the configuration program. The second group tracks the progress of the diagnostics. The third group provides information about messages that follow an 888 sequence For more detailed explanations of operator panel display numbers, refer to the Messages Guide and Reference.

Configuration Program Indicators
The numbers in this list display on the operator panel as the system loads the operating system and prepares the hardware by loading software drivers. Note: Some systems may produce 4-digit codes. If the leftmost digit of a 4-digit code is 0, use the three rightmost digits. 2E6 2E7 440 441 444 447 500 501 502 503 504 505 506 507 508 The PCI Differential Ultra SCSI adapter or the Universal PCI Differential Ultra SCSI adapter being configured. Configuration method unable to determine if the SCSI adapter type is SE or DE type. 9.1GB Ultra SCSI Disk Drive being identified or configured. 18.2GB Ultra SCSI Disk Drive being identified or configured. 2-Port Multiprotocol PCI Adapter (ASIC) being identified or configured. PCI 64-bit Fibre Channel Arbitrated Loop Adapter being configured. Querying Standard I/O slot. Querying card in Slot 1. Querying card in Slot 2. Querying card in Slot 3. Querying card in Slot 4. Querying card in Slot 5. Querying card in Slot 6. Querying card in Slot 7. Querying card in Slot 8.

217

510 511 512 513 516 517 518 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537

Starting device configuration. Device configuration completed. Restoring device configuration files from media. Restoring basic operating system installation files from media. Contacting server during network boot. Mounting client remote file system during network IPL. Remote mount of the root (/) and /usr file systems failed during network boot. Bus configuration running. /etc/init invoked cfgmgr with invalid options; /etc/inithas been corrupted or incorrectly modified (irrecoverable error). The configuration manager has been invoked with conflicting options (irrecoverable error). The configuration manager is unable to access the ODM database (irrecoverable error). The configuration manager is unable to access the config.rules object in the ODM database (irrecoverable error). The configuration manager is unable to get data from a customized device object in the ODM database (irrecoverable error). The configuration manager is unable to get data from a customized device driver object in the ODM database ( irrecoverable error). The configuration manager was invoked with the phase 1 flag; running phase 1 at this point is not permitted (irrecoverable error). The configuration manager cannot find sequence rule, or no program name was specified in the ODM database (irrecoverable error). The configuration manager is unable to update ODM data (irrecoverable error). The program savebase returned an error. The configuration manager is unable to access the PdAt object class (irrecoverable error). There is not enough memory to continue (malloc failure); irrecoverable error. The configuration manager could not find a configuration method for a device. The configuration manager is unable to acquire database lock (irrecoverable error). HIPPI diagnostics interface driver being configured. The configuration manager encountered more than one sequence rule specified in the same phase (irrecoverable error). The configuration manager encountered an error when invoking the program in the sequence rule.

218

Diagnostic Information for Multiple Bus Systems

538 539 541 549 551 552 553 554 555 556 557 558 559 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586

The configuration manager is going to invoke a configuration method. The configuration method has terminated, and control has returned to the configuration manager. A DLT tape device is being configured. Console could not be configured for the Copy a System Dump Menu. IPL vary-on is running. IPL vary-on failed. IPL phase 1 is complete. The boot device could not be opened or read, or unable to define NFS swap device during network boot. An ODM error occurred when trying to vary-on the rootvg, or unable to create an NFS swap device during network boot. Logical Volume Manager encountered error during IPL vary-on. The root filesystem does not mount. There is not enough memory to continue the system IPL. Less than 2 M bytes of good memory are available to load the AIX kernel. FCS SCSI protocol device is being configured. Virtual SCSI devices being configured. HIPPI common function device driver being configured. HIPPI IPI-3 master transport driver being configured. HIPPI IPI-3 slave transport driver being configured. HIPPI IPI-3 transport services user interface device driver being configured. A 9570 disk-array driver being configured. Generic async device driver being configured. Generic SCSI device driver being configured. Generic commo device driver being configured. Device driver being configured for a generic device. HIPPI TCPIP network interface driver being configured. Configuring TCP/IP. Configuring Token-Ring data link control. Configuring an Ethernet data link control. Configuring an IEEE Ethernet data link control. Configuring an SDLC MPQP data link control. Configuring a QLLC X.25 data link control.
Chapter 28. Diagnostics Numbers and Location Codes

219

587 588 589 590 591 592 593 594 595 596 597 598 599 5C0 5C1 5C2 5C3 5C4 5C5 5C6 600 602 603 604 605 606 607 608 609 60B 610

Configuring a NETBIOS. Configuring a Bisync Read-Write (BSCRW). SCSI target mode device being configured. Diskless remote paging device being configured. Configuring an LVM device driver. Configuring an HFT device driver. Configuring SNA device drivers. Asynchronous I/O being defined or configured. X.31 pseudo-device being configured. SNA DLC/LAPE pseudo-device being configured. OCS software being configured. OCS hosts being configured during system reboot. Configuring FDDI data link control. Streams-based hardware drive being configured. Streams-based X.25 protocol being configured. Streams-based X.25 COMIO emulator driver being configured Streams-based X.25 TCP/IP interface driver being configured. FCS adapter device driver being configured. SCB network device driver for FCS being configured. AIX SNA channel being configured. Starting network boot portion of /sbin/rc.boot. Configuring network parent devices. /usr/lib/methods/defsys, /usr/lib/methods/cfgsys, or /usr/lib/methods/cfgbus failed. Configuring physical network boot device. Configuration of physical network boot device failed. Running /usr/sbin/ifconfig on logical network boot device. /usr/sbin/ifconfig failed. Attempting to retrieve the client.info file with tftp.Note that a flashing 608 indicates multiple attempt(s) to retrieve the client_info file are occurring. The client.info file does not exist or it is zero length. 18.2GB 68-pin LVD SCSI Disk Drive being configured. Attempting remote mount of NFS file system.

220

Diagnostic Information for Multiple Bus Systems

611 612 614 615 616 617 618 619 61B 61D 61E 620 621 622 62D 62E 636 637 638 639 63A 63B 63C 63D 63E 63F 640 646 64A 64B 64C 64D

Remote mount of the NFS file system failed. Accessing remote files; unconfiguring network boot device. Configuring local paging devices. Configuration of a local paging device failed. Converting from diskless to dataless configuration. Diskless to dataless configuration failed. Configuring remote (NFS) paging devices. Configuration of a remote (NFS) paging device failed. 36.4GB 80-pin LVD SCSI Disk Drive being configured. 36.4GB 80-pin LVD SCSI Disk Drive being configured. 18.2GB 68-pin LVD SCSI Disk Drive being configured. Updating special device files and ODM in permanent filesystem with data from boot RAM filesystem. 9.1 GB LVD 80-pin SCSI Drive being configured. Boot process configuring for operating system installation. 9.1GB 68-pin LVD SCSI Disk Drive being configured. 9.1GB 68-pin LVD SCSI Disk Drive being configured. TURBROWAYS 622 Mbps PCI MMF ATM Adapter. Dual Channel PCI-2 Ultra2 SCSI Adapter being configured. 4.5GB Ultra SCSI Single Ended Disk Drive being configured. 9.1GB 10K RPM Ultra SCSI Disk Drive (68-pin). See 62D. 9.1GB 80-pin LVD SCSI Disk Drive being configured. See 60B. 18.2GB 80-pin LVD SCSI Disk Drive being configured. 36.4GB 68-pin LVD SCSI Disk Drive being configured. See 61B. 9.1GB 10K RPM Ultra SCSI Disk Drive (80-pin). High-Speed Token-Ring PCI Adapter being configured. See 62E. 9.1GB 80-pin LVD SCSI Disk Drive being configured. See 61E. 18.2 GB LVD 80-pin Drive/Carrier being configured.
Chapter 28. Diagnostics Numbers and Location Codes

221

64E 64F 650 653 655 657 658 659 660 662 663 664 667 669 66C 66D 66E 674 677 67B 682 689 68C 68E 690 69b 69d 6CC 700 701 702

36.4GB 68-pin LVD SCSI Disk Drive being configured. See 61D. IBM SCSD disk drive being configured. 18.2GB Ultra-SCSI 16-bit Disk Drive being configured. GXT130P Graphics adapter being configured. GXT2000P graphics adapter being configured. PCI Fibre Channel Disk Subsystem Controller being identified or configured. 2102 Fibre Channel Disk Subsystem Controller Drawer being identified or configured. 2102 Fibre Channel Disk Array being identified or configured. Ultra2 Integrated SCSI controller. The ARTIC960RxD Digital Trunk Quad PCI Adapter or the ARTIC960RxF Digital Trunk Resource Adapter being configured. 32x (MAX) SCSI-2 CD-ROM drive being configured. PCI 3-Channel Ultra2 SCSI RAID Adapter being configured. PCI Gigabit Ethernet Adapter being configured. 10/100/1000 Base-T EthernetPCI Adapter. PCI 4-Channel Ultra-3 SCSI RAID Adapter. 4.7 GB DVD-RAM drive. ESCON® Channel PCI Adapter being configured. PCI 32-bit Fibre Channel Arbitrated Loop Adapter being configured. PCI Cryptographic Coprocessor being configured. 20x (MAX) SCSI-2 CD-ROM Drive being configured. 4.5GB Ultra SCSI Single Ended Disk Drive being configured. 20 GB 4-mm Tape Drive being configured. POWER GXT6000P PCI Graphics Adapter. 9.1GB Ultra SCSI Single Ended Disk Drive being configured. 64-bit/66MHz PCI ATM 155 MMF PCI adapter being configured. 64-bit/66MHz PCI ATM 155 UTP PCI adapter being configured. SSA disk drive being configured. A 1.1 GB 8-bit SCSI disk drive being identified or configured. A 1.1 GB 16-bit SCSI disk drive being identified or configured. A 1.1 GB 16-bit differential SCSI disk drive being identified or configured.

222

Diagnostic Information for Multiple Bus Systems

703 704 705 706 707 708 710 711 712 713 714 715 717 718 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 736 741

A 2.2 GB 8-bit SCSI disk drive being identified or configured. A 2.2 GB 16-bit SCSI disk drive being identified or configured. The configuration method for the 2.2 GB 16-bit differential SCSI disk drive is being run. If an irrecoverable error occurs, the system halts. A 4.5 GB 16-bit SCSI disk drive being identified or configured. A 4.5 GB 16-bit differential SCSI disk drive being identified or configured. A L2 cache being identified or configured. POWER GXT150M graphics adapter being identified or configured. Unknown adapter being identified or configured. Graphics slot bus configuration is executing. The IBM ARTIC960 device being configured. A video capture adapter being configured. The Ultramedia Services audio adapter being configured. (this number displays briefly on the panel). TP Ethernet Adapter being configured. GXT500 Graphics Adapter being configured. Unknown read/write optical drive type being configured. Unknown disk or SCSI device being identified or configured. Unknown disk being identified or configured. Unknown CD-ROM being identified or configured. Unknown tape drive being identified or configured. Unknown display adapter being identified or configured. Unknown input device being identified or configured. Unknown async device being identified or configured. Parallel printer being identified or configured. Unknown parallel device being identified or configured. Unknown diskette drive being identified or configured. PTY being identified or configured. Unknown SCSI initiator type being configured. 7GB 8 mm tape drive being configured. 4x SCSI-2 640 MB CD-ROM Drive being configured. Quiet Touch keyboard and speaker cable being configured. 1080 MB SCSI Disk Drive being configured.

Chapter 28. Diagnostics Numbers and Location Codes

223

745 746 747 749 751 754 755 756 757 763 764 772 773 774 776 777 778 77B 77c 783 789 78B 78C 78D 790 797 798 799 79c 7C0 7C1 7cc 800

16GB 4 mm Tape Auto Loader being configured. SCSI-2 Fast/Wide PCI Adapter being configured. SCSI-2 Differential Fast/Wide PCI Adapter being configured. 7331 Model 205 Tape Library being configured. SCSI 32-bit SE F/W RAID Adapter being configured. 1.1GB 16-bit SCSI disk drive being configured. 2.2GB 16-bit SCSI disk drive being configured. 4.5GB 16-bit SCSI disk drive being configured. External 13GB 1.5M/s 1/4 inch tape being configured. SP Switch MX Adapter being configured. SP System Attachment Adapter being configured. 4.5GB SCSI F/W Disk Drive being configured. 9.1GB SCSI F/W Disk Drive being configured. 9.1GB External SCSI Disk Drive being configured. PCI Token-Ring Adapter being identified or configured. 10/100 Ethernet Tx PCI Adapter being identified or configured. POWER GXT3000P 3D PCI Graphics adapter being configured. 4-Port 10/100 Ethernet Tx PCI Adapter being identified or configured. A 1.0 GB 16-bit SCSI disk drive being identified or configured. 4 mm DDS-2 Tape Autoloader being configured. 2.6 GB External Optical Drive being configured. POWER GXT4000P PCI Graphics Adapter. PCI bus configuration executing. GXT300P 2D Graphics adapter being configured. Multi-bus Integrated Ethernet Adapter being identified or configured. TURBOWAYS® 155 UTP/STP ATM Adapter being identified or configured. Video streamer adapter being identified or configured. 2-Port Multiprotocol PCI adapter being identified or configured. ISA bus configuration executing. CPU/System Interface being configured. Business Audio Subsystem being identified or configured. PCMCIA bus configuration executing. TURBOWAYS 155 MMF ATM Adapter being identified or configured.

224

Diagnostic Information for Multiple Bus Systems

803 804 806 807 80c 811 812 813 814 815 816 817 819 821 823 824 825 826 827 828 831 834 835 836 837 838 839 840 841 842 843

7336 Tape Library robotics being configured. 8x Speed SCSI-2 CD-ROM Drive being configured. POWER GXT800 PCI Graphics adapter being configured. SCSI Device Enclosure being configured. SSA 4-Port Adapter being identified or configured. Processor complex being identified or configured. Memory being identified or configured. Battery for time-of-day, NVRAM, and so on being identified or configured, or system I/O control logic being identified or configured. NVRAM being identified or configured. Floating-point processor test. Operator panel logic being identified or configured. Time-of-day logic being identified or configured. Graphics input device adapter being identified or configured. Standard keyboard adapter being identified or configured. Standard mouse adapter being identified or configured. Standard tablet adapter being identified or configured. Standard speaker adapter being identified or configured. Serial Port 1 adapter being identified or configured. Parallel port adapter being identified or configured. Standard diskette adapter being identified or configured. 3151 adapter being identified or configured, or Serial Port 2 being identified or configured. 64-port async controller being identified or configured. 16-port async concentrator being identified or configured. 128-port async controller being identified or configured. 16-port remote async node being identified or configured. Network Terminal Accelerator Adapter being identified or configured. 7318 Serial Communications Server being configured. PCI Single-Ended Ultra SCSI Adapter being configured. 8-port async adapter (EIA-232) being identified or configured. 8-port async adapter (EIA-422A) being identified or configured. 8-port async adapter (MIL-STD 188) being identified or configured.

Chapter 28. Diagnostics Numbers and Location Codes

225

844 845 846 847 848 849 850 851 852 854 855 857 858 859 85c 861 862 865 866 867 868 869 870 871 872 874 875 876 877 878 879

7135 RAIDiant Array disk drive subsystem controller being identified or configured. 7135 RAIDiant Array disk drive subsystem drawer being identified or configured. RAIDiant Array SCSI 1.3GB Disk Drive being configured. 16-port serial adapter (EIA-232) being identified or configured. 16-port serial adapter (EIA-422) being identified or configured. X.25 Interface Coprocessor/2 adapter being identified or configured. Token-Ring network adapter being identified or configured. T1/J1 Portmaster® adapter being identified or configured. Ethernet adapter being identified or configured. 3270 Host Connection Program/6000 connection being identified or configured. Portmaster Adapter/A being identified or configured. FSLA adapter being identified or configured. 5085/5086/5088 adapter being identified or configured. FDDI adapter being identified or configured. Token-Ring High-Performance LAN adapter being identified or configured. Optical adapter being identified or configured. Block Multiplexer Channel Adapter being identified or configured. ESCON Channel Adapter or emulator being identified or configured. SCSI adapter being identified or configured. Async expansion adapter being identified or configured. SCSI adapter being identified or configured. SCSI adapter being identified or configured. Serial disk drive adapter being identified or configured. Graphics subsystem adapter being identified or configured. Grayscale graphics adapter being identified or configured. Color graphics adapter being identified or configured. Vendor generic communication adapter being configured. 8-bit color graphics processor being identified or configured. POWER Gt3™/POWER Gt4™ being identified or configured. POWER Gt4 graphics processor card being configured. 24-bit color graphics card, MEV2 being configured.

226

Diagnostic Information for Multiple Bus Systems

880 887 889 890 891 892 893 894 895 896 897 898 899 89c 900 901 902 903 904 905 908 910 911 912 913 914 915 916 917 918 920 921

POWER Gt1™ adapter being identified or configured. Integrated Ethernet adapter being identified or configured. SCSI adapter being identified or configured. SCSI-2 Differential Fast/Wide and Single-Ended Fast/Wide Adapter/A being configured. Vendor SCSI adapter being identified or configured. Vendor display adapter being identified or configured. Vendor LAN adapter being identified or configured. Vendor async/communications adapter being identified or configured. Vendor IEEE 488 adapter being identified or configured. Vendor VME bus adapter being identified or configured. S/370™ Channel Emulator adapter being identified or configured. POWER Gt1x™ graphics adapter being identified or configured. 3490 attached tape drive being identified or configured. A multimedia SCSI CD-ROM being identified or configured. GXT110P Graphics Adapter being identified or configured. Vendor SCSI device being identified or configured. Vendor display device being identified or configured. Vendor async device being identified or configured. Vendor parallel device being identified or configured. Vendor other device being identified or configured. POWER GXT1000 Graphics subsystem being identified or configured. 1/4GB Fiber Channel/266 Standard Adapter being identified or configured. Fiber Channel/1063 Adapter Short Wave being configured. 2.0GB SCSI-2 differential disk drive being identified or configured. 1.0GB differential disk drive being identified or configured. 5GB 8 mm differential tape drive being identified or configured. 4GB 4 mm tape drive being identified or configured. Non-SCSI vendor tape adapter being identified or configured. A 2.0 GB 16-bit differential SCSI disk drive being identified or configured. A 2 GB 16-bit single-ended SCSI disk drive being identified or configured. Bridge Box being identified or configured. 101 keyboard being identified or configured.
Chapter 28. Diagnostics Numbers and Location Codes

227

922 923 924 925 926 927 928 929 930 931 933 934 935 936 937 938 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957

102 keyboard being identified or configured. Kanji keyboard being identified or configured. Two-button mouse being identified or configured. Three-button mouse being identified or configured. 5083 tablet being identified or configured. 5083 tablet being identified or configured. Standard speaker being identified or configured. Dials being identified or configured. Lighted program function keys (LPFK) being identified or configured. IP router being identified or configured. Async planar being identified or configured. Async expansion drawer being identified or configured. 3.5-inch diskette drive being identified or configured. 5.25-inch diskette drive being identified or configured. An HIPPI adapter being configured. Serial HIPPI PCI adapter being configured. POWER GXT 100 graphics adapter being identified or configured. A 3480 or 3490 control unit attached to a System/370 Channel Emulator/A adapter are being identified or configured. 100MB ATM adapter being identified or configured. 1.0GB SCSI differential disk drive being identified or configured. Serial port 3 adapter being identified or configured. A 730MB SCSI disk drive being configured. Portable disk drive being identified or configured. Unknown direct bus-attach device being identified or configured. Missing SCSI device being identified or configured. 670MB SCSI disk drive being identified or configured. 355MB SCSI disk drive being identified or configured. 320MB SCSI disk drive being identified or configured. 400MB SCSI disk drive being identified or configured. 857MB SCSI disk drive being identified or configured. 670MB SCSI disk drive electronics card being identified or configured. 120 MB DBA disk drive being identified or configured.

228

Diagnostic Information for Multiple Bus Systems

2. 2. 1. 2. 200MB SCSI disk drive being identified or configured. 150 MB 1/4-inch tape drive being identified or configured.2GB 1/4 inch cartridge tape drive being identified or configured.0 GB 4 mm tape drive being identified or configured. 9-track tape drive being identified or configured. Internal 20 GB 8 mm tape drive identified or configured. An optical disk drive being identified or configured. FDDI adapter being identified or configured. M-Audio Capture and Playback Adapter being identified or configured. Diagnostics Numbers and Location Codes 229 . multiprotocol communications adapter being identified or configured. Token-Ring cable T2 Ethernet Adapter being configured.4GB SCSI disk drive being identified or configured. 160 MB SCSI disk drive being identified or configured. Chapter 28. Other SCSI tape drive being identified or configured.0GB SCSI-2 single-ended disk drive being identified or configured. 525MB 1/4-inch cartridge tape drive being identified or configured. 1. 7137 or 3514 Disk Array Subsystem being configured. 5 GB 8 mm tape drive being identified or configured.0 GB SCSI disk drive being identified or configured. CD-ROM drive being identified or configured.3 GB 8 mm SCSI tape drive being identified or configured. Half-inch. A single-port.958 959 960 964 968 970 971 972 973 974 975 977 981 984 985 986 987 989 990 991 994 995 996 997 998 999 D46 D81 2530 160 MB DBA disk drive being identified or configured. 10/100 Mbps Ethernet PCI Adapter II being configured. M-Video Capture Adapter being identified or configured. 2. An Enhanced SCSI CD-ROM drive being identified or configured. 1.37GB SCSI disk drive being identified or configured. 1GB 8-bit disk drive being identified or configured. 540MB SCSI-2 single-ended disk drive being identified or configured.

The loading stopped with an irrecoverable error. use the three rightmost digits. and the system is configured to enter the kernel debug program instead of entering a system dump. A directly attached display (HFT) was selected. Configuration files are being restored. Extracting data files from diskette. Select the console display for the diagnostics. If the leftmost digit of a 4-digit code is 0. If you continue to get the message. set the key mode switch to Normal then to Service. The rc. A TTY terminal attached to serial ports S1 or S2 was selected. Unable to read client’s ClientHostName. Insert the next diagnostic diskette. The system was unable to configure the network device. Diskettes inserted out of sequence. The diskette drive is reading or writing a diskette. The console messages store in a file. The wrong diskette is in diskette drive. A file was selected. To select No console display. Insert the first diagnostic diskette. c00 c01 c02 c03 c04 c05 c06 c07 c08 c09 c20 c21 c22 c24 c25 c26 c29 c31 AIX Install/Maintenance loaded successfully. No console found.Diagnostic Load Progress Indicators Note: Some systems may produce 4-digit codes. c32 c33 c34 c35 c40 c41 c42 230 Diagnostic Information for Multiple Bus Systems . A diskette error occurred. check the cables and make sure you are using the serial port. Client did not mount remote miniroot during network install. RAM file system started incorrectly. Could not determine the boot type or device. The diagnostic programs then load and run the diagnostics automatically. The ifconfig command was unable to configure the network for the client network host. Client did not mount the /usr file system during the network boot. An unexpected halt occurred.boot configuration shell script is unable to determine type of boot.info file during a client network boot. The tftp command was unable to read client’s ClientHostName info file during a client network boot.

c43 c44 c45 c46 c47 c48 c49 c50 c51 c52 c53 c54 c55 c56 c57 c58 c59 c61 c62 c63 c64 c70 c99 Fxx Cannot access the boot/install tape. Changing from RAM environment to disk environment. A dump. Running user-defined customization. Problem Mounting diagnostic CD-ROM disc. Could not copy either device special files. Dump Progress Indicators (Dump Status Codes) The following dump progress indicators. requested by the user. Cannot configure the console. Diagnostics have completed. or dump status codes. Failed to load platform dependent data files. Chapter 28. Not enough space in the /tmp directory to do a preservation installation. it displays in the lower half of the character position. Loading platform dependent debug files. is started. or volume group information from RAM to disk. No paging devices were found. 0c0 0c1 0c2 The dump completed successfully. device ODM. The dump failed due to an I/O error. Failed to create the boot image. (xx is any number) Refer to Firmware chapter of the service manual. Loading platform dependent data files. Could not create or form the JFS log. Could not create a physical volume identifier (PVID) on disk. Use the two rightmost digits. Creating root volume group on target disks. Normal installation processing. are part of a Type 102 message. Could not remove the specified logical volume in a preservation installation. the two leftmost positions can have a blanks or zeros. Displaying message to turn the key. Diagnostics Numbers and Location Codes 231 . Initializing installation database with target disk information. Installing either BOS or additional packages. Some systems produce 4-digit codes. Failure to restore BOS. Note: When a lowercase c is listed. This code is only used when there is no console. Prompting you for input.

Category 2 200 201 202 203 204 Machine check because of a memory bus error. Machine check because of a memory timeout. Both software and hardware support may be needed in Problem Determination. The dump did not start. Program interrupt. Machine check because of an attempt to write to ROS. A dump is in progress. 232 Diagnostic Information for Multiple Bus Systems . The dump function is disabled. These crash codes are grouped into three categories: Category 1 Dump analysis is the appropriate first action in Problem Determination. If the leftmost digit of a 4-digit code is 0. Dump analysis most likely will not aid in Problem Determination. The dump device is not large enough. Instruction storage interrupt. begin the Problem Determination process with hardware support. Reserved. Data storage interrupt because of an I/O exception from IOCC. begin the Problem Determination process with software support. use the three rightmost digits.0c3 0c4 0c5 0c6 0c7 0c8 0c9 0cc The dump is inhibited. Machine check because of a memory card failure. Unknown dump failure Crash Codes Note: Some systems may produce 4-digit codes. The crash codes that follow are part of a Type 102 message. go to Chapter 9. Machine check because of a out of range address. or the dump crashed. Dumping to a secondary dump device. Data storage interrupt because of an I/O exception from SLA. “MAP 0070: 888 Sequence in Operator Panel Display” on page 59 to assist in problem isolation. Category 2 Category 3 Category 1 300 32x 38x 400 700 Data storage interrupt from the processor.

External interrupt because of an IOCC channel check. Category 3 000 558 600 Unexpected system interrupt.3. External interrupt because of a DMA memory bus error. Machine check because of an uncorrectable ECC error.3.3: AIX has crashed because the Portability Assist Layer (PAL) for this machine type has detected a problem. AIX 4.205 206 207 208 500 501 51x 52x 53x 54x 800 Machine check because of an uncorrectable address parity.3 and above: Alignment Interrupt. Diagnostics Numbers and Location Codes 233 . External interrupt because of an unidentified error. Machine check because of an unidentified error.3. Floating point is not available. External interrupt because of an IOCC keyboard check. 605 Chapter 28. External interrupt from an IOCC bus timeout. There is not enough memory to continue the IPL.3. External interrupt because of a scrub memory bus error. AIX has crashed because the Portability Assist Layer (PAL) for this machine type has detected a problem (AIX 4. If pre-AIX 4.3.3.3 and above). Machine check due to an L2 uncorrectable ECC. x represents the IOCC number.

use the “Location Codes for CHRP Model Architecture System Units” on page 236. Because the same diagnostic programs are used on all system units. The basic format of the system unit’s location code is: AB-CD-EF-GH non-SCSI AB-CD-EF-G. device. For integrated adapters. or FRU. and non-SCSI devices. Values for GH are 1 through 16. For systems that have memory cards with memory modules. – For L2 caches. where CD is the card slot and GH is the memory module slot. If the location code is not known. The location code is displayed along with the service request number (SRN) when the diagnostic programs isolate a failure. Values for GH are 1 through 16. If you are working with a CHRP model. GH is equal to 00. v GH identifies a port. – For a diskette drive. GH has several meanings depending upon the resource type. memory module. address. the location code for a diskette drive is 01-A0-00-00. v CD identifies a slot or adapter number. A second diskette drive is 01-A0-00-01. GH defines the PCMCIA. H defines which diskette drive 1 or 2. Values for GH are 1 through 16. refer to “Determining System Architecture” on page 158 before proceeding. they are as follows: – For memory cards. Values are 00 to 15. used to identify the adapter connector to which a resource is attached. If you do not know which model you have. a location code is used to physically locate a failing device or unit. the location code is 00-CD-EF-GH. GH defines a memory module. G is always 0. For systems that have memory modules that plug directly into the system planar. EF-GH is the same as the definition for a pluggable adapter. GH defines the port on the fanout box. GH defines the cache. – For async devices.Location Codes for RSPC Model Architecture System Units Note: You need to know which system architecture the system unit on which you are working uses.H SCSI For planars. the location code is defined as follows: AB-CD-EF-GH | | | | | | | Device/FRU/Port ID | | Connector ID | Slot or Adapter Number Bus Type v AB identifies a bus type. – For all other devices. you can run the Display Previous Diagnostic Results service aid to display the results of the last time the diagnostic programs were run. the location code is 00-00-00-GH where GH is the memory module slot. cards. v EF is the connector identifier. For example. 234 Diagnostic Information for Multiple Bus Systems . – For PCMCIA devices.

Values of 0 to 255 are valid. Values of 0 to 15 are valid.For SCSI. However. For integrated adapters. either by SMIT or the ISA Adapter Configuration Service Aid. The second character (D) is set to 0. v H defines the logical unit address of the device. This ensures unique location codes for the integrated adapters. For pluggable adapters or cards. The possible values for AB are as follows: 00 01 04 05 for for for for processor bus ISA buses PCI buses PCMCIA buses (not supported on 7024) The possible values for CD depend on the adapter or card. Diagnostics Numbers and Location Codes 235 . in the case of ISA cards these numbers do not actually correspond to the physical slot numbers. the first character (C) is a letter in the range from A to Z.H | | | | | | | | | Logical Unit Address of SCSI Device | | | Control Unit Address of SCSI Device | | Connector ID | Slot or Adapter Number Bus Type Where: v AB-CD-EF are the same as non-SCSI devices. v G defines the control unit address of the device. This letter is based on the order in which the integrated adapters are defined in residual data. Adapters and cards are identified with only AB-CD. They simply are based on the order in which the ISA cards are defined or configured. the location code is defined as follows: AB-CD-EF-G. this is a two-digit slot number in the range from 01 to 99. Refer to the following examples: RSPC Location Code Examples Processor-PCI bus 00-00 PCI bus Memory module in system planar 00-00-00-01 Memory module in card 00-0A-00-01 Integrated PCI adapters 04-A0 ISA bus (Integrated PCI-ISA bridge) 04-B0 Secondary PCI bus (Integrated PCI-PCI bridge) 04-C0 Integrated PCI SCSI controller Non-integrated PCI adapters 04-01 Any PCI card in slot 1 04-02 Any PCI card in slot 2 Integrated ISA adapters Chapter 28.

or period (. refer to “Determining System Architecture” on page 158 before proceeding. v P1-K1 identifies a keyboard attached to connector K1 on planar P1. It identifies a cable that is connected to the parent. Physical Location Codes Physical location codes provide a mapping of logical functions in a platform (or expansion sites for logical functions. slash (/). 236 Diagnostic Information for Multiple Bus Systems . If you do not know which model you have. The following are examples: v P1-C1 identifies a CPU card C1 plugged into planar P1. The (CHRP) system unit uses Physical Location Codes in conjunction with AIX Location Codes to provide mapping of the failing field replaceable units.01-A0 Diskette adapter 01-B0 Parallel port adapter 01-C0 Serial port 1 adapter 01-D0 Serial port 2 adapter 01-E0 Keyboard adapter 01-F0 Mouse adapter Non-integrated ISA adapters 01-01 First ISA card defined/configured 01-02 Second ISA card defined/configured 01-03 Third ISA card defined/configured 01-04 Fourth ISA card defined/configured Device attached to SCSI controller 04-C0-01-4. v P1-I2/E3 identifies. a connector. pound sign (#). v P1-M1 identifies a memory card M1 plugged into planar P1. v P1/S1 identifies serial port 1 controller on planar P1. or the cable attached to Ethernet controller 3. It identifies a device that is connected or plugged into the parent. Ethernet controller 3 on the card plugged into slot 2 (I2) on planar P1. or the cable attached to connector S1. The base location is all of the information before the slash (/) or pound sign (#). It identifies a device that is part of the parent. such as connectors or ports) to their specific locations within the physical structure of the platform. Cable information follows the pound sign (#). the connector for serial port 1.0 Device attached to Integrated PCI SCSI controller Location Codes for CHRP Model Architecture System Units Note: You need to know which system architecture the system unit on which you are working uses. Extended location information follows the slash (/). or a cable.). If you are working with a RSPC model use the “Location Codes for RSPC Model Architecture System Units” on page 234. Location Code Format The format for the location code is a string of alphanumeric characters separated by a dash (-). The location codes are produced by the system unit’s firmware and the AIX operating system. the connector for Ethernet controller 3.

Location codes with extended location information that display without a description identifying the devices. so that they would be easier to remember. voltage regulator. In most cases. the prefix value assignments were chosen to provide some mnemonic characteristic.n Xn Single enclosure platform Planar (backplane. Table 1. Depending on the AIX and firmware levels. The underlined characters in the description field are intended to illustrate this mnemonic relationship. backup battery Fan/sensor LED/LCD operator panel CPU/cache card (or pluggable module if on planar) CPU/cache module on CPU card (if pluggable) Memory card or SIMM/DIMM on planar Memory SIMM/DIMM on memory card Other extra-function base system cards (for example.1 identifies a SCSI device with a SCSI address of LUN 1 at SCSI ID 3 attached to SCSI bus 1 from planar 2.) is used to identify sublocations such as memory DIMMs on a base memory card or a specific SCSI address. AIX Diagnostics may include extended location information when identifying a planar or card.v P1-I2#E3 identifies. v P2/Z1-A3. service processor) Chapter 28.2 identifies the second cable in a series of cables attached to Ethernet controller 3 in slot 2 (I2) on planar 1.n Vn Fn Ln Cn Cn.4 identifies DIMM 4 on memory card 1 on planar 1.n if rack cannot be sensed by firmware) (No enclosure location code) Pn Pn. always identify the cable attached to the port. I/O) Planar riser card. The following are examples: v P1-M1.1 identifies CPU 1 on CPU card 1 on planar 1.n (U0. The period (. Location Code Prefix Values Description Rack or non-drawer enclosure unit Drawer unit mounted in a rack Prefix Value (n=instance #) Un Un. system. extender Power/voltage supply.n Mn Mn. v P1-I2#E3. Diagnostics Numbers and Location Codes 237 . The extended location information or cable information is always included when identifying a cable or connector. the cable attached to Ethernet controller 3 plugged into slot 2 (I2) on planar P1. v P1-C1. Physical Location Code Standard Prefixes Table 1 lists the assigned values for the location type prefixes.

Y An An.n Dn 238 Diagnostic Information for Multiple Bus Systems . J. N. W. Location Code Prefix Values (continued) Description I/O adapter Pluggable modules or daughter cards on I/O adapter Diskette drive Ports/Connectors: Graphics/video connector Keyboard/keyboard connector Mouse/mouse connector Serial port Parallel port Ethernet connector Token Ring connector SCSI (pronounced scuzzy) connector Other I/O ports or connectors SCSI device addresses (including SSA (Serial Storage Architecture)) Primary address (SCSI control unit ID) Primary and secondary address (SCSI ID and LUN (Logical Unit Number)) SCSI device location in SCSI Enclosure Services (SES) SCSI bank SCSI bank and bay Undefined prefixes (reserved) Bn Bn.n Gn Kn On Sn Rn En Tn Zn Qn Prefix Value (n=instance #) In In.n H.Table 1.

and lower case are omitted) and are equal to the parent bus’s ibm. v The GH value identifies a port. The devfunc number is defined as the PCI device number times 8. aix-loc Open Firmware Property. address. v The CD value identifies adapter number. or physical location. J-N. Adapters and cards are identified only with AB-CD. or FRU. Chapter 28. Adapter Number or Physical Location Bus Type or PCI Parent Bus v The AB value identifies a bus type or PCI parent bus as assigned by the firmware.H For planars. plus the function number. Diagnostics Numbers and Location Codes 239 . device. The possible values for AB are: 00 01 02 03 04 05 xy Processor bus ISA bus EISA bus MCA bus PCI bus used in the case where the PCI bus cannot be identified PCMCIA buses For PCI adapters where x is equal to or greater than 1. v The EF value identifies a connector. I.AIX Location Codes The basic formats of the AIX location codes are as follows: v For non-SCSI devices/drives: AB-CD-EF-GH v For SCSI devices/drives: AB-CD-EF-G. cards. The x and y are characters in the range of 0-9. P-Z (O. the location code is defined as follows: AB-CD-EF-GH | | | | | | | Device/FRU/Port ID | | Connector ID | devfunc Number. adapter’s devfunc number. A-H. and non-SCSI devices.

CD is FF. – For a diskette drive. CD is equal to the order in which the ISA cards defined or configured.The possible values for CD depend on the adapter or card are as follows: v For pluggable PCI adapters/cards. CD is equal to a unique code identifying the ISA adapter. the location code is defined as: AB-CD-EF-G. In cases where a physical location code is not available. For SCSI devices. For pluggable ISA adapters. v G defines the control unit address of the device.H | | | | | | | | | Logical Unit address of the SCSI Device | | | Control Unit Address of the SCSI Device | | Connector ID | devfunc Number. For the integrated adapters. Adapter Number or Physical Location Bus Type or PCI Parent Bus Where: v AB-CD-EF are the same as non-SCSI devices. Refer to the system unit service guide for additional information. H defines either diskette drive 1 or 2. For example. Values of 0 to 255 are valid. For example: – For async devices. The C and D are characters in the range of 0-9. plus the function number). the location code for a diskette drive is 01-D1-00-00. EF-GH is the same as the definition for the pluggable adapters. – For all other devices. CD is the device’s devfunc number (PCI device number times 8. GH defines the port on the fanout box. 240 Diagnostic Information for Multiple Bus Systems . device. and A-F (hex numbers). GH is equal to 00. v H defines the logical unit address of the device. this is equal to the adapter’s physical location code. v GH is used to identify a port. The values are 00 to 15. either by SMIT or the ISA Adapter Configuration Service Aid. A second diskette drive is 01-D1-00-01. Values of 0 to 15 are valid. In most cases. G is always 0. v EF is the connector ID. It is used to identify a connector on the adapter to which a resource is attached. This allows the location code to uniquely identify multiple adapters on individual PCI cards. There is also a bus location code that is generated as ’00-xxxxxxxx’ where xxxxxxxx is equivalent to the node’s unit address. For integrated ISA adapters. or FRU.

Because different platforms come in different packaging. the specific meaning and actual physical location of a location code might vary. Table 2.12 U1-P1-Q1 U2-P1-I4 P1 P1-C1 P1-M2 P2 P2-I4 P2/S2 P2/K1 P2-K1 V1 F2 L1 P2/Z1 Location Code Chapter 28. Diagnostics Numbers and Location Codes 241 . Location Code Examples Descriptions of Example Locations Locations in a single enclosure platform System planar CPU card in slot 1 (or pluggable CPU module in module socket 1) Memory SIMM in slot 2 on the planar I/O planar (including all integrated I/O devices) Card in I/O slot 4 Serial port 2 controller (with connector) Keyboard port controller (with connector) Keyboard (connected to keyboard port) Power Supply Fan 2 Op panel Integrated SCSI controller (with connector) Locations in a multi-enclosure platform System planar Memory DIMM 12 on memory card in slot 2 on the system planar Connector/cable from system planar to remote I/O expansion planar Adapter in slot 4 of an I/O expansion planar in a second enclosure U1-P1 U1-P1-M2. but the representation is intended to be applied consistently.Location Code Examples Table 2 provides several examples of location codes for elements of typical platforms.

242 Diagnostic Information for Multiple Bus Systems .

Description and Action This column lists a brief description of the failure that this SRN represents. The SRN is from a MAP callout. Failing Function Codes These numbers represent functional areas of the system unit. do not do the Action listed. If you are servicing a clustered Eserver. Note: If you are servicing an SP system. The SRN is from a POST failure. The SRN is from the Error Log Analysis program. Instead. always return to the SP System Service Guide.) SRN source codes identify the program or procedure that produced the SRN: A B C D E F G H J K The SRN is from a steady number in the operator panel display. The SRN is from a diagnostic test after partial isolation testing. Using the SRN List The service request number (SRN) list is in numerical sequence. It also contains instructions as to what to do to continue the problem analysis. The SRNs listed in the following chapters are for all systems and devices for which this version of the diagnostic programs can produce an SRN. 243 . The SRN was due to a missing resource at configuration time. always return to the Clustered Eserver Installation and Service Guide. The SRN is from off-line diagnostics.Chapter 29. The “Failing Function Code List” on page 538 identifies the FRU that contains this function for each specific system unit. The SRN is from built-in ROM diagnostics. The columns in the table are defined as follows: Service Request Number Usually a six-digit number (9333 uses four digits) representing a specific failure of a specific function. Source of SRN (SRN Src. Use the table on page Service Request Number Lists to select the correct chapter for your SRN. The SRN is from a diagnostic message after an 888 sequence. do not do the Action listed. The SRN is from a diagnostic test after complete isolation testing. Instead.

If the SRN contains 3 digits before the dash. use Chapter 22. The xxxx is the last digit within the 950 prefix. If you cannot find SRN information in the ″Service Request Number List. always return to the SP Hardware Manual. column). “MAP 0410: Repair Checkout” on page 119 to verify the fix.″ check for the existence of supplemental material supporting the device for which the SRN was generated. followed by the dash. For example. The chapters are divided into number ranges. The following table identifies each SRN chapter range and the page number on which it begins: Chapter Title Chapter 30. of the SRN you wish to locate. then select the chapter that contains the first 3 digits. 3. The -xxx or -xxxx should always be the last SRN identified within a specific prefix. do not do the Action listed. x in an SRN represents any digit or character. of the SRN you wish to locate. However. For example. d. Service Request Number Lists The following five chapters contain the Service Request Number (SRN) Lists. then select the chapter that contains the first 4 digits. 5. because this SRN falls between the number range of 700-102 and 89c-302. Notes: a. An example would be 950-xxxx. you would go to Chapter 32. do not do the Action listed. you would go to Chapter 35. If you are servicing a clustered Eserver. Instead. Record the failing function codes in the order listed. “SRNs 700-102 through 89c-302”. 2. Note: There may be 7 or 8 digit SRNs within each range. e. b. followed by the dash. Perform the action shown in the Description and Action column. If you are servicing a SP system. Use the list as follows: 1. If your SRN is not listed. if the SRN is 802-xxxx. 4. because this SRN falls between the number range of 2520-(x)xxx and 2590-(x)xxx.Using the Service Request Number List The service request number list is in numerical sequence by the SRN. if your SRN contains 4 digits before the dash. Record the code letter for the Source of SRN (the SRN Src. check to see if xxx or xxxx has been used. “SRNs 2520-101 through 2590-(x)xxx”. “SRNs 101-000 through 69d-701” Page Number 247 259 244 Diagnostic Information for Multiple Bus Systems . Find your SRN in the table. Instead. When replacing a FRU. c. “Five-Digit SRNs 10104 through SSA03” Chapter 31. if the SRN is 2570–603. always return to the Clustered Eserver Installation and Service Guide.

“SRNs 2520-101 through 2590-(x)xxx” Page Number 361 441 511 529 Chapter 29.Chapter Title Chapter 32. “SRNs 900-001 through xxxxxxx” Chapter 34. “SRNs A00-(x)xxx through A1D-(x)xxx” Chapter 35. Using the SRN List 245 . “SRNs 700-102 through 89c-302” Chapter 33.

246 Diagnostic Information for Multiple Bus Systems .

Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. a software error occurred.Chapter 30.) Description: Format in progress. Failing Function Codes Description and Action (Unless otherwise indicated. use Chapter 11. Abbreviation in Table PAA Definition P AA Adapter port number SSA Address Service Request Number 10104 SRN Src. Probably. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and the User’s Guide and Maintenance Information for the SSA adapter. a software error occurred. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and the User’s Guide and Maintenance Information for the SSA adapter. A format operation ended before it completed. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and the User’s Guide and Maintenance Information for the SSA adapter. Five-Digit SRNs 10104 through SSA03 Service Request Number List Replace FRU parts in the order by which the ″Failing Function Codes″ are listed. “MAP 0210: General Problem Resolution” on page 67. Probably. Description: Async code 03 was received. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Description: An SSA Threshold Exceeded link error was detected. Description: Disk drive module error. Probably. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and the User’s Guide and Maintenance Information for the SSA adapter. Description: Async code 04 was received. an x represents a digit 0 through F. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. a software error occurred. 21PAA to 29PAA 2A002 2A003 2A004 247 . Description: Format Degraded. 10112 1xxxx 20PAA Description: An open SSA loop was detected. Note: In this SRN. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Description: Async code 02 was received.

Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Description: A disk drive Microcode Error was detected. Description: Multiple disk drive modules detected the loss of redundant power or cooling. Description: Async code 06 was received. This code indicates that a disk drive module detected the loss of redundant power or cooling. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. The disk drive might be going to fail. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and the User’s Guide and Maintenance Information for the SSA adapter. Description: The disk drive was reset by the adapter. Description: A disk drive module detected that one of its SSA links failed the POST. Description: A disk drive module detected the loss of redundant power or cooling. This code indicates that a disk drive module detected the loss of redundant power or cooling. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Description: Async code 06 was received. use Chapter 11. This code indicates that multiple disk drive modules detected loss of redundant power or cooling. “MAP 0210: General Problem Resolution” on page 67. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Description: An SCSI status that is not valid was received. 2A006 2A106 2A206 2FFFF 300C0 301C0 303FE 303FF 31000 248 Diagnostic Information for Multiple Bus Systems . Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Description: An async code that is not valid was received.) Description: Async code 05 was received.Service Request Number 2A005 SRN Src. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and the User’s Guide and Maintenance Information for the SSA adapter. Failing Function Codes Description and Action (Unless otherwise indicated.

40000 40004 40008 40016 40032 40064 40128 41004 41008 41016 41032 41064 41128 42000 Chapter 30. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Failing Function Codes Description and Action (Unless otherwise indicated. Description: A module on the adapter failed. Description: A module on the adapter card failed. Description: A module on the adapter card failed. Description: A module on the adapter card failed. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: A module on the adapter card failed. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: A module on the adapter card failed. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. “MAP 0210: General Problem Resolution” on page 67. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Five-Digit SRNs 10104 through SSA03 249 .Service Request Number 33PAA SRN Src. Description: A module on the adapter card failed. Description: A module on the adapter card failed. use Chapter 11. Description: A module on the adapter failed. Description: A module on the adapter card failed. Description: A module on the adapter card failed.) Description: Excessive link reconfigurations were detected. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: A module on the adapter card failed. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: The SSA adapter card failed. Description: A module on the adapter card failed.

but the fast-write cache option card cannot be detected. Description: Not enough DRAM available to run an SSA fast-write cache. Description: An SSA fast-write cache option card failure was detected. Description: A fast-write disk drive (or drives) contains unsynchronized data.) Description: Other adapters on the SSA loop are using levels of microcode that are not compatible. Description: A fast-write problem occurred. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: An SSA fast-write cache option card failure was detected. Description: An SSA fast-write cache failure was detected. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. 42500 42510 42515 42520 42521 42522 42523 42524 42525 42526 42527 250 Diagnostic Information for Multiple Bus Systems . Description: An SSA adapter is attempting to use its fast-write cache. Description: This adapter does not support the SSA Fast-Write Cache Option. Description: An SSA adapter detected a failure in its fast-write cache. Description: A dormant SSA fast-write cache entry exists.Service Request Number 42200 SRN Src. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. but a fast-write cache card is not installed. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: A incorrect version number was detected in the fast-write cache option card. “MAP 0210: General Problem Resolution” on page 67. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Failing Function Codes Description and Action (Unless otherwise indicated. use Chapter 11. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter.

Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive or to the User’s Guide and Maintenance Information for the SSA adapter. is not available. Description: An SSA device on the loop is preventing the completion of the loop configuration. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: A disk drive module has a Failed status. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. “MAP 0210: General Problem Resolution” on page 67. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive or to the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. One cache. 42529 4252A 4252B 4252C 42540 43PAA 44PAA 45PAA 46000 Chapter 30. Description: The fast-write cache is disabled. but has since been configured on a different adapter. Description: The supply voltage to the fast-write cache option card is low. Description: The SSA adapter has detected an open SSA loop. Description: The battery to the fast-write cache option card needs to be exchanged for a new one. Description: A RAID array is in the Off-Line state because more than one disk drive is not available.Service Request Number 42528 SRN Src. use Chapter 11. Description: The battery to the fast-write cache option card no longer has the power to maintain data. Failing Function Codes Description and Action (Unless otherwise indicated. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive or to the User’s Guide and Maintenance Information for the SSA adapter. Description: Two-way fast-write cache is configured to operate only when both caches are available. The battery is charging. however. Five-Digit SRNs 10104 through SSA03 251 . The card has switched to Self-Refresh mode. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter.) Description: A fast-write SSA disk drive has been detected that was previously unsynchronized.

Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. 47000 47500 48000 48500 48600 48700 48750 48755 48760 48800 48900 252 Diagnostic Information for Multiple Bus Systems . Description: The SSA adapter is unknown to the array. “MAP 0210: General Problem Resolution” on page 67. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: The SSA adapter detected a link configuration that is not valid. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter.) Description: A member disk drive is missing from a SSA array or the original SSA adapter is not available. Failing Function Codes Description and Action (Unless otherwise indicated. Description: Part of the RAID array data might have been lost. a multiple-device error occurred. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. use Chapter 11. Description: An SSA array is not available. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: An array is in the Off-Line state because the split/join procedure was not performed correctly. Description: The array filter detected a link configuration that is not valid. Description: Two or more member disk drives of an SSA array are on different loops. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: One member disk drive of an array is not on the SSA loop that contains the other member disk drives of the array. Description: An attempt was made to store in the SSA adapter the details of more than 32 RAID arrays. Description: An array is in the Off-Line state because the primary or secondary half of the array is not present. Description: The Invalid-Strip table is full. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter.Service Request Number 46500 SRN Src. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter.

Failing Function Codes Description and Action (Unless otherwise indicated. Description: No hot-spare disk drives are available for an array that is configured for hot-spare disk drives. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter.) Description: A disk drive caused an Array-Build operation to fail. Description: The SSA adapter failed to respond to the device driver. Description: The parity for the RAID array is not complete. use Chapter 11. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: The adapter cannot initialize an SSA disk drive. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. because its UID cannot be read. Description: Adapters that do not support hot-spare pools were detected. 49000 49100 49500 49510 49520 49530 49540 49700 49800 4A100 4BPAA 50000 Chapter 30. Description: A different adapter was detected on each loop. “MAP 0210: General Problem Resolution” on page 67. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: A RAID array is in the Exposed state. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: An SSA disk drive at PAA cannot be configured. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter.Service Request Number 48950 SRN Src. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: Hot-spare configuration is not synchronized. Five-Digit SRNs 10104 through SSA03 253 . Description: A RAID array is in the Degraded state. Description: Hot-spare tuning has been lost. Description: The number of disk drives that remain in a hot-spare pool is less than the specified number.

Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: An attempt was made to log an error against a pdisk that is not available to the using system. Description: The SSA adapter microcode hung. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: A Channel Check occurred. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: A Channel Check occurred. Failing Function Codes Description and Action (Unless otherwise indicated. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: The IOCC detected an internal error.Service Request Number 50001 SRN Src. Description: Duplicate SSA cluster number detected. Description: An SSA adapter DMA error occurred. Description: An SSA adapter or device-driver protocol error occurred. 50002 50004 50005 50006 50007 50008 50010 50012 50013 50100 50200 50411 50422 254 Diagnostic Information for Multiple Bus Systems . “MAP 0210: General Problem Resolution” on page 67. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: SSA adapter detected a SS_TIMEOUT error. Description: A software error occurred. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: The SSA adapter card failed.) Description: A Data Parity error occurred. Description: SSA adapter detected a SS_SIC_CLASS1 error. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. use Chapter 11. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: Unable to read or write the POS registers or PCI configuration space.

use the SRN table in the system unit’s service guide to find this SRN and do the action indicated there. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter or if the system service guide contains integrated SSA (without a distinct model type from the system unit itself). Description: The SSA adapter microcode hung. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. use Chapter 11. Failing Function Codes Description and Action (Unless otherwise indicated. Description: The SSA unit has an unexpected Check light On. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter or if the system service guide contains integrated SSA (without a distinct model type from the system unit itself). use the SRN table in the system unit’s service guide to find this SRN and do the action indicated there. Description: A fan-and-power-supply assembly has its Check light On. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: The SSA unit cannot be turned on. use the SRN table in the system unit’s service guide to find this SRN and do the action indicated there. Description: The SSA adapter is missing from the expected configuration. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter or if the system service guide contains integrated SSA (without a distinct model type from the system unit itself). “MAP 0210: General Problem Resolution” on page 67. Five-Digit SRNs 10104 through SSA03 255 . 504xx 60000 60200 60210 60220 60230 60240 Chapter 30. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter.Service Request Number 50425 SRN Src. Description: A disk drive module has its Check light On. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter or if the system service guide contains integrated SSA (without a distinct model type from the system unit itself). Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter or if the system service guide contains integrated SSA (without a distinct model type from the system unit itself). Description: An SSA configuration problem occurred.) Description: SSA adapter detected a SS_LINK_CONFIG_FAILED error. use the SRN table in the system unit’s service guide to find this SRN and do the action indicated there. use the SRN table in the system unit’s service guide to find this SRN and do the action indicated there.

Description: The Format operation that was started on this disk drive module has not finished. Description: The diagnostics cannot configure the SSA adapter. Description: The disk drive module is Not Ready while the diagnostics are running. 8xxxx D0000 D0100 D0101 D0200 D0300 D0400 D0450 D0460 D4000 D4100 256 Diagnostic Information for Multiple Bus Systems . Note: In this SRN. use Chapter 11. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: The disk drive module timed out while the diagnostics were running. Failing Function Codes Description and Action (Unless otherwise indicated. an x represents a digit 0 through F. an x represents a digit 0 through F. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Description: A Format operation was degraded. Description: Unable to clear a disk drive module reservation. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and to the User’s Guide and Maintenance Information for the SSA adapter.) Description: An SSA disk drive is missing from the expected configuration of the SSA loop. Description: The disk drive module has been reserved since the diagnostics started. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Description: The using system cannot configure the disk drive module. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Description: A Configuration Error occurred.Service Request Number 7xxxx SRN Src. Description: The diagnostics cannot open the SSA adapter. Description: The disk drive module failed the diagnostic test. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. “MAP 0210: General Problem Resolution” on page 67. Note: In this SRN. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter.

Note: In this SRN. Description: An unknown error occurred. D44xx D6PAA DFFFF SSA01 SSA02 SSA03 Chapter 30. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: A high-speed SSA link is running at low speed. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and to the User’s Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. “MAP 0210: General Problem Resolution” on page 67. but cannot download a new version of the microcode. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter.Service Request Number D4300 SRN Src. Description: A command or parameter that was sent or received is not valid. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Description: There is not enough using-system memory available for this service aid to continue. an X represents a digit 0 through F.) Description: The diagnostics have detected an SSA adapter POST failure. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Note: The description and action for this SRN are valid only if you ran the diagnostics on the SSA attachment. Action: Refer to the SRN table in the User’s Guide and Maintenance Information for the SSA adapter. Five-Digit SRNs 10104 through SSA03 257 . Description: The service aid was unable to open a hdisk. Description: The diagnostics detected that the SSA adapter has corrupted microcode. Failing Function Codes Description and Action (Unless otherwise indicated. use Chapter 11.

258 Diagnostic Information for Multiple Bus Systems .

SCSI terminator.) Description: The system hung while attempting to configure a device. open PTC. If a different problem occurs when you run standalone diagnostics. Action: Go to Chapter 8. SCSI cable. Action: Use MAP 1540. If standalone diagnostics run correctly. Note: The boot record was read from the disk. errors occurred when trying to open the disk drive. Action: Use MAP 1540 in the system unit service guide to isolate the cause. the problem may be damaged data on the disk. open PTC. Action: Use MAP 1540. try running standalone diagnostics. 101-517 101-518 A A 101-521 to 101-538 A 101-544 A 259 . Action: If you are running the diagnostics from a disk. correct that problem. errors occurred when trying to mount the CD-ROM file system. This problem can be caused by SCSI device addressing. Description: Disk read problems occurred after booting. Description: CD-ROM read problems after boot. However. or these actions did not resolve the problem. “MAP 0050: SCSI Bus Problems” on page 51. Description: The system unit failed to IPL. Service Request Number 101-000 101-185 SRN Src. etc. “MAP 0210: General Problem Resolution” on page 67. Contact your software support facility. etc. SRNs 101-000 through 69d-701 Replace FRU parts in the order by which the ″Failing Function Codes″ are listed. If you were running standalone at first. A A Failing Function Codes Description and Action (Unless otherwise indicated. However. go to MAP 1540. This problem can be caused by SCSI device addressing. Description: A checkstop occurred. Description: The configuration manager detected an error. Note: The boot record was read from the CD-ROM disk. “MAP 0050: SCSI Bus Problems” on page 51. in either the service guide or the installation and service guide for this system unit.Chapter 31. Action: Go to Chapter 8. SCSI terminator. use Chapter 11. have the same problem running standalone diagnostics that you had when running diagnostics from disk. Note: Some SRNs in this chapter may have 4 rather than 3 digits after the dash (-). SCSI cable.

Description: There is not enough memory to execute diagnostics. This can be caused by a hardware or software problem. isolate the failing resource by removing the adapters or devices one at a time and checking if the system stops with the same value in the three-digit display. If the standalone diagnostics still produces the same SRN. If you still get the same SRN. “MAP 0020: Problem Determination Procedure” on page 29. Action: Run the standalone diagnostics. Note: xxx corresponds to the last three digits of the SRN.Service Request Number 101-551 to 101-557 SRN Src. If the standalone diagnostics run correctly. “MAP 0020: Problem Determination Procedure” on page 29. Otherwise. If the same SRN is generated from standalone diagnostics. Action: Use the standalone diagnostics if not yet used. If the system has 16 MB or more of memory installed. correct that problem. go to Chapter 4.If a different problem occurs when you run the standalone diagnostics. the problem may be a damaged disk data. If the SRN is not generated running standalone diagnostics. go to MAP 1540 in the system unit service guide for problem isolation. Consider having the customer contact Software Support before reinstalling the operating system on the disk. Description: The system halted while software was loading. A Failing Function Codes Description and Action (Unless otherwise indicated. refer to “Failing Function Code List” on page 538 and find the FFC that matches the last three digits of the SRN. Action: Go to MAP 1540 in either the service guide or the installation and service guide for this system unit. suspect a problem with a memory card. suspect a problem with the system’s software. “MAP 0210: General Problem Resolution” on page 67. correct that problem. 101-711 to 101-726 A 260 Diagnostic Information for Multiple Bus Systems . This problem may be attributed to either hardware or software. 101-558 A 101-559 to 101-599 A 101-662 A Description: An unexpected system interrupt. Step 14. xxx Description: The system hung while trying to configure an unknown resource. use Chapter 11. Suspect the device adapter or device itself. go to MAP 1540 in either the service guide or the installation and service guide for this system unit. If more than one adapter or device is installed. If a different problem occurs when you run the standalone diagnostics. Action: There must be a minimum of 16 MB of installed memory.) Description: The system hung while loading the software. Start at Chapter 4. Action: Run standalone diagnostics.

101-840 A 101-888 A 210 227 E10 Description: The system does not IPL. Suspect the graphics adapter being used for the display console first. Description: An unexpected system interrupt. go to the SSA MAP in either the system unit’s service guide or user’s guide.) Description: The system hung while trying to configure an asynchronous adapter. Description: The time-of-day battery failed. Description: The system hung while indicating that a TTY terminal is the system console. Action: Go to MAP 1540 in either the service guide or the installation and service guide for this system unit. 101-c33 D 101-c70 A 101-xxxx A 103-151 109-200 D B 151 Chapter 31. SRNs 101-000 through 69d-701 261 . Action: Use Chapter 17. Suspect either a SCSI adapter or integrated SCSI if so equipped. Description: A problem was encountered mounting the CD-ROM. Description: A potential problem with an SSA device exists. Description: The system crashed while being run by the customer. A Failing Function Codes Description and Action (Unless otherwise indicated. 101-c32 D Description: The system hung while indicating that a direct-attached display was selected as the console. Action: Use Chapter 4. “MAP 0020: Problem Determination Procedure” on page 29. and get a new SRN. Action: Go to MAP 1540 in either the service guide or the installation and service guide for this system unit. Suspect a problem with one of the async adapters. Action: Use MAP 1540 in the service guide or the installation and service guide for the system unit. “MAP 0210: General Problem Resolution” on page 67. The last three or four digits after the dash (-) identify the failing function code for the resource being configured.Service Request Number 101-727 SRN Src. xxxx E10 Description: The system hung while configuring a resource. “MAP 0260: System Hangs During Resource Configuration” on page 99. If the system has internal SSA devices. Action: Go to MAP 1540 in either the service guide or the installation and service guide for this system unit. If the system has external SSA devices refer to the SSA Adapters User’s Guide and Maintenance Information. Action: Use MAP 1540 in the installation and service guide for this system unit. use Chapter 11. 101-7C1 101-80c A A 7C1 80c Description: The system unit halted while configuring an audio subsystem. Suspect the graphics adapter being used for the display console first.

Action: Go to Chapter 4. Description: There is a display problem. Description: The system halted while diagnostics were executing. Action: Do problem determination on the display. “MAP 0280: Boot Problem Resolution” on page 113. Description: Cannot display readable information on the terminal. Action: Go to Chapter 4. Description: An encoded SRN was displayed. Action: If this SRN appeared when running concurrent diagnostics. “MAP 0020: Problem Determination Procedure” on page 29. Description: The keyboard does not respond. “MAP 0280: Boot Problem Resolution” on page 113 Entry 1. Action: Use Chapter 19. “MAP 0280: Boot Problem Resolution” on page 113 Entry 3. Note: Suspect the display adapter attached to the console display. then proceed to the FFC table using the substituted digits as your FFC. 110-921 to 110-926 110-935 110-946 110-xxxx D D D D 935 812 946 221 xxxx 221 111-107 B 111-108 B 111-121 111-259 B B 111-725 B 725 Description: Cannot display readable information on the display.Service Request Number 110-101 SRN Src. “MAP 0210: General Problem Resolution” on page 67. Description: The system halted while diagnostics were executing. Description: The system halted while diagnostics were executing. Action: Use Chapter 19. Note: xxx corresponds to the last three digits of the SRN.) Description: The diagnostics did not detect an installed resource. otherwise use Chapter 20. substitute the last three or four digits of the SRN for xxxx. “MAP 0020: Problem Determination Procedure” on page 29. Action: Use Chapter 19. Note: xxxx corresponds to the last three or four digits of the SRN following the dash (-). Description: The system halted while diagnostics were executing. use Chapter 11. “MAP 0290: Missing Resource Problem Resolution” on page 115. 111-736 B 736 821 262 Diagnostic Information for Multiple Bus Systems . C Failing Function Codes Description and Action (Unless otherwise indicated. Description: A machine check occurred. If your 110 SRN is not listed. then run concurrent using the diag -a command. 110-908 D 908 C33 C36 xxx 812 Description: The system halted while diagnostics were executing.

use Chapter 11. “MAP 0280: Boot Problem Resolution” on page 113 Entry 2. Description: SCSI FIFO underflow. 111-922 B 111-923 B 111-947 111-999 2E6-101 2E6-102 2E6-103 2E6-212 2E6-213 2E6-214 2E6-215 2E6-216 2E6-217 2E6-218 2E6-219 2E6-220 2E6-221 2E6-222 2E6-223 B D D D D D D D D D D D D D D D D 2E6-224 D 2E6 221 Chapter 31. “MAP 0280: Boot Problem Resolution” on page 113 Entry 1. Action: Use Chapter 19. Description: Miscompare during the write/read of the configuration register. Description: Enhanced error handling failure on the bus.) Description: I/O bus problem. Description: Enhanced error handling failure on the adapter. 111-82C B 111-921 B 921 821 922 821 923 821 221 210 221 293 2E6 221 2E6 2E6 2E6 2E6 2E6 2E6 2E6 2E6 2E6 2E6 221 2E6 2E6 Description: The keyboard does not respond. Description: System does not perform a soft reset. Description: SCSI parity error. Description: SCSI configuration register read or write error. Description: Miscompare during the write/read of the memory I/O register. Description: SCSI FIFO data miscompare. Description: Cannot display readable information on the display. Description: Enhanced error handling failure on a PCI-PCI Bridge. “MAP 0280: Boot Problem Resolution” on page 113 Entry 1.Service Request Number 111-78C SRN Src. Description: System beeper not functioning correctly. Action: Use Chapter 19. “MAP 0210: General Problem Resolution” on page 67. Action: Go to Chapter 8. SRNs 101-000 through 69d-701 263 . Note: PCI adapter refers to the adapters you made note of when using Chapter 10. Action: Go to Chapter 19. Description: FIFO empty bit clear. Description: The keyboard does not respond. Description: Error during the write/read of the memory register. Description: The keyboard does not respond. Description: FIFO data miscompare. Action: Use MAP 210. Description: FIFO empty bit set. Description: SCSI FIFO flags error. Description: FIFO full bit set. “MAP 0080: System Bus Problem Isolation” on page 63. Action: Use Chapter 19. “MAP 0050: SCSI Bus Problems” on page 51. B Failing Function Codes PCI adapter 227 E10 Description and Action (Unless otherwise indicated. Description: FIFO full bit clear. “MAP 0280: Boot Problem Resolution” on page 113 Entry 1.

264 Diagnostic Information for Multiple Bus Systems . Description: SCSI wrap or PTC failure. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. If an SRN is reported.) Description: Adapter POST failed. “MAP 0050: SCSI Bus Problems” on page 51. “MAP 0050: SCSI Bus Problems” on page 51. use Chapter 11. Description: Arbitration test failed. Description: Enhanced error handling failure on a PCI-PCI Bridge. If an SRN is not reported. Description: Enhanced error handling failure on the adapter. Description: No terminal power. If an SRN is reported. Action: Go to Chapter 8. 2E6 221 2E6 Description: The parent device open failed. Description: SCSI bus problem. “MAP 0050: SCSI Bus Problems” on page 51. “MAP 0050: SCSI Bus Problems” on page 51. If an SRN is not reported. use the SRN to resolve the problem. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. Description: Error log analysis indicates that multiple attempts to reset the SCSI bus have timed out. Description: Error log analysis indicates that multiple SCSI bus errors have occurred. Action: Go to Chapter 8. Action: Go to Chapter 8. Action: Go to Chapter 8. Action: Run the diagnostics on the adapter in System Verification mode.Service Request Number 2E6-225 2E6-226 2E6-227 2E6-230 2E6-231 2E6-232 2E6-240 2E6-242 2E6-301 2E6-701 2E6-801 SRN Src. Action: Run the diagnostics on the adapter in System Verification mode. Description: Error log analysis indicates a PCI SCSI adapter failure. Action: Go to Chapter 8. use the SRN to resolve the problem. use the SRN to resolve the problem. Action: Go to Chapter 8. Description: Function could not complete. Description: SCSI bus data miscompare. “MAP 0050: SCSI Bus Problems” on page 51. D D D D D D D D D G G Failing Function Codes 2E6 Description and Action (Unless otherwise indicated. Description: Error log analysis indicates a terminator problem. “MAP 0050: SCSI Bus Problems” on page 51. Action: Run the diagnostics on the adapter in System Verification mode. If an SRN is not reported. “MAP 0210: General Problem Resolution” on page 67. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. 2E6 221 Description: SCSI adapter test failure. If an SRN is reported. 2E6-802 G 2E6-803 G 2E7-101 2E7-102 2E7-103 D D D 221 293 2E7 221 Description: Enhanced error handling failure on the bus.

Action: Go to Chapter 8. Description: Arbitration test failed. Description: FIFO empty bit clear. Description: SCSI configuration register read or write error. Description: Miscompare during the write/read of the memory I/O register. “MAP 0050: SCSI Bus Problems” on page 51. Description: SCSI wrap or PTC failure. Action: Go to Chapter 8. Description: FIFO full bit clear. Action: Go to Chapter 8. Description: SCSI FIFO flags error. Description: SCSI bus problem. “MAP 0050: SCSI Bus Problems” on page 51. Action: Go to Chapter 8. Description: SCSI FIFO underflow. Description: Error log analysis indicates a PCI SCSI adapter failure. Description: Adapter POST failed. Description: No terminal power. “MAP 0050: SCSI Bus Problems” on page 51. Description: SCSI FIFO data miscompare. SRNs 101-000 through 69d-701 265 . “MAP 0210: General Problem Resolution” on page 67. Action: Go to Chapter 8. Description: Error during the write/read of the memory register. Action: Go to Chapter 8. D D D D D D D D D D D D Failing Function Codes 2E7 2E7 2E7 2E7 2E7 2E7 2E7 2E7 2E7 2E7 221 2E7 2E7 Description and Action (Unless otherwise indicated.Service Request Number 2E7-212 2E7-213 2E7-214 2E7-215 2E7-216 2E7-217 2E7-218 2E7-219 2E7-220 2E7-221 2E7-222 2E7-223 SRN Src. “MAP 0050: SCSI Bus Problems” on page 51. Description: FIFO data miscompare. “MAP 0050: SCSI Bus Problems” on page 51. use Chapter 11. “MAP 0050: SCSI Bus Problems” on page 51. Chapter 31. 2E7 2E7 Description: Configuration open failed for parent bus. 2E7-224 2E7-225 2E7-226 2E7-227 2E7-230 2E7-231 2E7-232 2E7-240 2E7-242 2E7-301 2E7-701 D D D D D D D D D D G 2E7 221 2E7 2E7 221 Description: SCSI adapter test failure. Action: Go to Chapter 8. Description: FIFO full bit set.) Description: FIFO empty bit set. Description: Miscompare during the write/read of the configuration register. “MAP 0050: SCSI Bus Problems” on page 51. Description: SCSI parity error. Description: SCSI bus data miscompare. Description: Function could not complete.

Action: Run the diagnostics on the adapter in System Verification mode. Description: A SCSI reservation conflict error. G Failing Function Codes Description and Action (Unless otherwise indicated. use the SRN to resolve the problem. Description: The diagnostic test failed. adapter. Description: A SCSI check condition error occurred. and application software to be sure they are all compatible. If an SRN is not reported. If an SRN is reported. If an SRN is reported. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. Action: Check the levels of the device. Action: Run the diagnostics on the adapter in System Verification mode. 2E7-802 G 2E7-803 G 2EF-101 440-102 440-104 440-105 440-106 440-108 440-110 440-112 440-114 440-116 E D D D D D D D D D 751 440 440 440 440 440 440 440 440 Description: Post indicates an adapter failure. If an SRN is not reported. If an SRN is reported. Description: An unrecoverable media error occurred. Description: The electronics card test failed. Description: A SCSI command time-out occurred. Description: The bus test failed. If you do not find a problem. diagnostic software. Action: Run the diagnostics on the adapter in System Verification mode. Description: A software error was caused by a hardware failure. Description: Error log analysis indicates that multiple SCSI bus errors have occurred. Description: Error log analysis indicates that multiple attempts to reset the SCSI bus have timed out.Service Request Number 2E7-801 SRN Src. Description: A protocol error. Description: The drive did not become ready. use the SRN to resolve the problem. call your support person. Description: The error log analysis indicates a hardware failure. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. “MAP 0210: General Problem Resolution” on page 67. Description: The motor failed to restart. Description: The media format is corrupted. 266 Diagnostic Information for Multiple Bus Systems . use Chapter 11.) Description: Error log analysis indicates a terminator problem. Description: A SCSI busy or command error. Description: An unrecoverable hardware error. use the SRN to resolve the problem. If an SRN is not reported. 440-117 440-118 440-120 440-122 440-124 440-126 440-128 D D D D D D G 440 440 B88 440 440 440 440 B88 440 Description: A write-protect error occurred.

Chapter 31. SRNs 101-000 through 69d-701 267 . Description: The motor failed to restart. go to MAP 210. Description: A SCSI busy or command error. that no other system environmental warnings are occurring. adapter. 440-136 440-137 D D Description: The certify operation failed. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. call your support person. and application software to be sure they are all compatible. Description: A protocol error. diagnostic software. If you do not find a problem. use Chapter 11. Otherwise. Description: A disk drive hardware error occurred. Action: Check to be sure none of the air passages in the system covers are blocked. Description: An unrecoverable hardware error. Action: Check the levels of the device. Description: An unrecoverable media error occurred. Description: The drive did not become ready. “MAP 0210: General Problem Resolution” on page 67. G Failing Function Codes 190 440 B88 software 440 440 B88 software 440 B88 software 440 440 B88 190 440 Description and Action (Unless otherwise indicated. Description: The electronics card test failed. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: A software error was caused by a hardware failure. Description: A SCSI reservation conflict error. 440-130 440-132 440-134 440-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: The media format is corrupted. Description: A SCSI command time-out occurred. Description: A SCSI check condition error occurred. Description: The adapter failed to configure.) Description: Error log analysis indicates a SCSI bus problem. 440-138 D 441-102 441-104 441-105 441-106 441-108 441-110 441-112 441-114 441-116 D D D D D D D D D 441 441 441 441 441 441 441 441 441-117 441-118 441-120 441-122 441-124 441-126 D D D D D D 441 441 B88 441 441 441 441 B88 Description: A write-protect error occurred. Description: The device failed to configure.Service Request Number 440-129 SRN Src. Description: The diagnostic test failed. Description: The bus test failed.

Description: Error log analysis indicates a SCSI bus problem. Description: The electronics card test failed. Description: A SCSI reservation conflict error. Description: A SCSI busy or command error. 441-130 441-132 441-134 441-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Action: Check the levels of the device. Otherwise. Description: The bus test failed. Description: A disk drive hardware error occurred. G G Failing Function Codes 441 190 441 B88 software 441 441 B88 software 441 B88 software 441 441 B88 190 441 Description and Action (Unless otherwise indicated. Description: The media format is corrupted. adapter.Service Request Number 441-128 441-129 SRN Src. and application software to be sure they are all compatible. “MAP 0210: General Problem Resolution” on page 67. Description: The motor failed to restart. Description: A SCSI check condition error occurred. diagnostic software. go to MAP 210. call your support person. Description: Unit attention condition has occurred on the Send Diagnostic command. that no other system environmental warnings are occurring. Description: The adapter failed to configure.) Description: The error log analysis indicates a hardware failure. Description: A SCSI command time-out occurred. 441-138 D 442-102 442-104 442-105 442-106 442-108 442-110 442-112 442-114 442-116 D D D D D D D D D 442 442 442 442 442 442 442 442 442-117 442-118 442-120 442-122 442-124 D D D D D 442 442 B88 442 442 442 Description: A write-protect error occurred. Description: A protocol error. Description: An unrecoverable media error occurred. Description: The drive did not become ready. 268 Diagnostic Information for Multiple Bus Systems . use Chapter 11. Action: Check to be sure none of the air passages in the system covers are blocked. Description: The device failed to configure. Description: An unrecoverable hardware error. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. Description: The diagnostic test failed. 441-136 441-137 D D Description: The certify operation failed. If you do not find a problem.

D G G Failing Function Codes 442 B88 442 190 442 B88 software 442 442 B88 software 442 B88 software 442 442 B88 190 443 443 443 443 443 443 443 443 Description and Action (Unless otherwise indicated. Description: An unrecoverable media error occurred. 442-136 442-137 D D Description: The certify operation failed. SRNs 101-000 through 69d-701 269 . call your support person. If you do not find a problem. use Chapter 11. and application software to be sure they are all compatible. Description: The diagnostic test failed. Chapter 31. Description: The electronics card test failed. Description: An unrecoverable hardware error. Description: Error log analysis indicates a SCSI bus problem. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The error log analysis indicates a hardware failure.Service Request Number 442-126 442-128 442-129 SRN Src. adapter. “MAP 0210: General Problem Resolution” on page 67. Action: Check the levels of the device. Description: A protocol error. Description: The drive did not become ready. Description: A SCSI command time-out occurred. Description: A SCSI reservation conflict error. 443-102 443-104 443-105 443-106 443-108 443-110 443-112 443-114 443-116 D D D D D D D D D 443-117 443-118 443-120 443-122 443-124 443-126 D D D D D D 443 443 B88 443 443 443 443 B88 Description: A write-protect error occurred. diagnostic software. Description: The adapter failed to configure. Description: The media format is corrupted. Description: The bus test failed. 442-130 442-132 442-134 442-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function.) Description: A software error was caused by a hardware failure. Description: A disk drive hardware error occurred. Description: The device failed to configure. Description: A software error was caused by a hardware failure. Description: A SCSI check condition error occurred. Description: The motor failed to restart. Description: A SCSI busy or command error.

Description: External wrap test failed on port 1. Description: Error log analysis indicates a SCSI bus problem. Description: Enhanced error handling failure on adapter.) Description: The error log analysis indicates a hardware failure. Description: EEH failure on Eads chip. Description: The adapter failed to configure. use Chapter 11. Description: A disk drive hardware error occurred. Description: External wrap test failed on port 1. “MAP 0210: General Problem Resolution” on page 67. Description: Enhanced error handling failure on Eads chip. Description: External wrap test failed on port 0. 443-130 443-132 443-134 443-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: Enhanced error handling failure on bus. Description: The device failed to configure. G G Failing Function Codes 443 190 443 B88 software 443 443 B88 software 443 B88 software 443 443 B88 190 2C3 444 2C3 444 227 227 444 776 646 776 646 776 646 444 227 444 227 444 227 2C3 444 2C3 444 Description and Action (Unless otherwise indicated. Description: Enhanced error handling failure on bus. Description: Enhanced error handling failure on adapter. Description: External wrap test failed on port 0. Description: External wrap test failed on port 0. Description: Internal adapter test failed. 444-101 444-102 444-103 444-104 444-105 444-106 444-107 444-108 444-201 444-202 444-203 444-204 444-205 D D D D D D D D D D D D D 270 Diagnostic Information for Multiple Bus Systems .Service Request Number 443-128 443-129 SRN Src. Description: External wrap test failed on port 1. Description: Unit attention condition has occurred on the Send Diagnostic command. 443-136 443-137 D D Description: The certify operation failed.

Description: The External Wrap test failed. 444-207 D Description: External wrap test failed on port 1. “MAP 0210: General Problem Resolution” on page 67. SRNs 101-000 through 69d-701 271 .Service Request Number 444-206 SRN Src. 444-208 444-301 D D Description: Enhanced error handling failure opening the adapter. D Failing Function Codes 2C3 444 software 2C3 444 software 444 227 444 227 software 444 227 software 444 227 software 2C3 444 software 2C3 444 software 444 software 444 227 447 447 447 447 447 447 447 221 221 447 Description and Action (Unless otherwise indicated. Chapter 31. Description: The Internal Wrap test failed. Description: Internal adapter test failed. Description: Enhanced Error Handling Failure on adapter. Description: Enhanced Error Handling Failure on EADs chip. 444-303 D Description: External wrap test failed on port 1. 444-304 D Description: External wrap test failed on port 0. Description: Enhanced Error Handling Failure on bus. 444-302 D Description: External wrap test failed on port 0. Description: Error log analysis indicates that this adapter has failed to initialize due to EEH errors. Description: The Gigabaud Link Module (GLM) Wrap Test Failure.) Description: External wrap test failed on port 0. 444-305 D Description: External wrap test failed on port 1. Description: The Register test failed. use Chapter 11. 444-700 444-701 447-101 447-102 447-103 447-104 447-105 447-106 447-107 447-108 447-109 447-110 D D D D D D D D D D D D Description: Error log analysis indicates a hardware problem. Description: The Fibre Channel Adapter configuration failed. Description: The Reset test failed. Description: The SRAM test failed.

Description: An unrecoverable hardware error. Description: A protocol error. Description: A SCSI busy or command error. use Chapter 11. Description: The motor failed to restart. Description: An unrecoverable media error. Description: Error log analysis indicates that an error has occurred with the adapter. Description: The bus test failed. Description: The PCI Wrap test failed. Description: The drive did not become ready. “MAP 0210: General Problem Resolution” on page 67.) Description: The Configuration Register test failed. Description: The diagnostic test failed. Description: The electronics card test failed. Description: The drive cannot be started. Description: Error log analysis indicates that an adapter error has occurred. Description: The Interrupt test failed. call your support person. Description: The media format is corrupted. Description: Error log analysis indicates that an unknown adapter error has occurred. Action: Check the levels of the device. Description: An 8mm 60GB tape device problem has occurred. Description: A DLT tape device problem has occurred. diagnostic software.Service Request Number 447-201 447-202 447-203 447-204 447-205 447-701 447-703 447-704 541-xxx 542-xxx SRN Src. Description: The Medium Format is corrupted. D D D D D G G G D D Failing Function Codes 447 221 447 221 447 221 447 221 447 221 447 221 447 447 541 542 Description and Action (Unless otherwise indicated. Description: The DMA test failed. If you do not find a problem. Description: A SCSI command time-out. Action: Refer to the 8mm 60GB tape device documentation. adapter. Description: A hardware error occurred. and application software to be sure they are all compatible. Description: I/O error on a read/write operation. 272 Diagnostic Information for Multiple Bus Systems . Action: Refer to the DLT tape device documentation. 57B-105 57D-110 57D-114 58D-102 58D-104 58D-105 58D-106 58D-108 58D-110 58D-112 58D-114 58D-116 D D D D D D D D D D D D 57B 57D 57D 58D 58D 58D 58D 58D 58D 58D 58D 58D-117 58D-118 58D-120 D D D 58D 58D B88 58D Description: A write-protect error occurred.

Chapter 31. Description: The adapter failed to configure. Otherwise. If you do not find a problem. SRNs 101-000 through 69d-701 273 . go to MAP 210. 58D-130 58D-132 58D-134 58D-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: The diagnostic test failed. Description: A SCSI check condition error. Description: The drive did not become ready. that no other system environmental warnings are occurring. Description: A software error was caused by a hardware failure. Description: An unrecoverable media error. Description: The electronics card test failed. Action: Check to be sure none of the air passages in the system covers are blocked. 58D-136 58D-137 D D Description: The certify operation failed. Description: The error log analysis indicates a hardware failure. Description: A protocol error. Description: The bus test failed. Description: The motor failed to restart. call your support person. Action: Check the levels of the device. adapter. Description: A disk drive hardware error occurred. Description: The media format is corrupted. “MAP 0210: General Problem Resolution” on page 67. and application software to be sure they are all compatible. Description: An unrecoverable hardware error.) Description: A SCSI reservation conflict error. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. D D D G G Failing Function Codes 58D 58D 58D B88 58D 190 58D B88 software 58D 58D B88 software 58D B88 software 58D 58D B88 190 58D Description and Action (Unless otherwise indicated. Description: Error log analysis indicates a SCSI bus problem. Description: Unit attention condition has occurred on the Send Diagnostic command. diagnostic software. 58D-138 D 59B-102 59B-104 59B-105 59B-106 59B-108 59B-110 59B-112 59B-114 59B-116 D D D D D D D D D 59B 59B 59B 59B 59B 59B 59B 59B 59B-117 D 59B Description: A write-protect error occurred. use Chapter 11. Description: The device failed to configure.Service Request Number 58D-122 58D-124 58D-126 58D-128 58D-129 SRN Src.

go to MAP 210. Description: A SCSI check condition error. D D D D D G G Failing Function Codes 59B B88 59B 59B 59B 59B B88 59B 190 59B B88 software 59B 59B B88 software 59B B88 software 59B 59B B88 190 59B Description and Action (Unless otherwise indicated. Description: The bus test failed. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. Description: A disk drive hardware error occurred. Description: The diagnostic test failed. use Chapter 11. Otherwise.Service Request Number 59B-118 59B-120 59B-122 59B-124 59B-126 59B-128 59B-129 SRN Src. Action: Check to be sure none of the air passages in the system covers are blocked.) Description: A SCSI command time-out. 59B-138 D 60B-102 60B-104 60B-105 60B-106 60B-108 60B-110 60B-112 60B-114 D D D D D D D D 60B 60B 60B 60B 60B 60B 60B 60B 274 Diagnostic Information for Multiple Bus Systems . Description: The electronics card test failed. Description: The drive did not become ready. Description: An unrecoverable media error. 59B-130 59B-132 59B-134 59B-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: An unrecoverable hardware error. Description: The device failed to configure. Description: The motor failed to restart. Description: The media format is corrupted. “MAP 0210: General Problem Resolution” on page 67. Description: A software error was caused by a hardware failure. that no other system environmental warnings are occurring. Description: Error log analysis indicates a SCSI bus problem. Description: A SCSI reservation conflict error. Description: The adapter failed to configure. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: A SCSI busy or command error. 59B-136 59B-137 D D Description: The certify operation failed. Description: The error log analysis indicates a hardware failure.

Service Request Number 60B-116 SRN Src. Description: The error log analysis indicates a hardware failure. Description: A software error was caused by a hardware failure. “MAP 0210: General Problem Resolution” on page 67. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. diagnostic software. Description: The device failed to configure. Description: An unrecoverable media error. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The motor failed to restart. 60B-138 D 601-102 601-104 601-105 601-106 601-108 601-110 D D D D D D 601 601 601 601 601 601 Chapter 31. Description: The electronics card test failed. and application software to be sure they are all compatible. use Chapter 11.) Description: A protocol error. go to MAP 210. Otherwise. Description: The drive did not become ready. Description: A SCSI reservation conflict error. Description: The bus test failed. 60B-117 60B-118 60B-120 60B-122 60B-124 60B-126 60B-128 60B-129 D D D D D D G G 60B 60B B88 60B 60B 60B 60B B88 60B 190 60B B88 software 60B 60B B88 software 60B B88 software 60B 60B B88 190 60B Description: A write-protect error occurred. SRNs 101-000 through 69d-701 275 . Description: A SCSI busy or command error. adapter. D Failing Function Codes Description and Action (Unless otherwise indicated. that no other system environmental warnings are occurring. 60B-130 60B-132 60B-134 60B-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: A SCSI command time-out. Description: A SCSI check condition error. Description: A disk drive hardware error occurred. Description: The media format is corrupted. Description: The adapter failed to configure. If you do not find a problem. Action: Check the levels of the device. call your support person. Description: Error log analysis indicates a SCSI bus problem. Action: Check to be sure none of the air passages in the system covers are blocked. 60B-136 60B-137 D D Description: The certify operation failed.

601-117 601-118 601-120 601-122 601-124 601-126 601-128 601-129 D D D D D D G G 601 601 B88 601 601 601 601 B88 601 190 601 B88 software 601 601 B88 software 601 B88 software 601 601 B88 190 601 Description: A write-protect error occurred. Description: The motor failed to restart. Description: A disk drive hardware error occurred. go to MAP 210. Description: A protocol error. Otherwise.Service Request Number 601-112 601-114 601-116 SRN Src. 601-130 601-132 601-134 601-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. adapter. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The drive did not become ready. If you do not find a problem. D D D Failing Function Codes 601 601 Description and Action (Unless otherwise indicated. 601-136 601-137 D D Description: The certify operation failed. Description: A software error was caused by a hardware failure. that no other system environmental warnings are occurring. “MAP 0210: General Problem Resolution” on page 67.) Description: The diagnostic test failed. Description: A SCSI busy or command error. Description: A SCSI check condition error. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. Action: Check the levels of the device. Description: A SCSI command time-out. Description: The electronics card test failed. Description: The error log analysis indicates a hardware failure. Description: A SCSI reservation conflict error. 601-138 D 61B-102 61B-104 61B-105 61B-106 D D D D 61B 61B 61B 61B 276 Diagnostic Information for Multiple Bus Systems . diagnostic software. Action: Check to be sure none of the air passages in the system covers are blocked. Description: An unrecoverable media error. Description: The device failed to configure. Description: Error log analysis indicates a SCSI bus problem. use Chapter 11. and application software to be sure they are all compatible. Description: An unrecoverable hardware error. call your support person. Description: The adapter failed to configure.

Description: A SCSI busy or command error. that no other system environmental warnings are occurring. Description: Unit attention condition has occurred on the Send Diagnostic command. Action: Check to be sure none of the air passages in the system covers are blocked. If you do not find a problem. Description: The device failed to configure. Description: A protocol error. Description: The media format is corrupted. Description: A SCSI command time-out. 61B-138 D 61D-098 J 61D B88 Chapter 31. Description: Error log analysis indicates a SCSI bus problem.) Description: The bus test failed. Description: A disk drive hardware error occurred. “MAP 0210: General Problem Resolution” on page 67. 61B-136 61B-137 D D Description: The certify operation failed. call your support person. Description: The adapter failed to configure. SRNs 101-000 through 69d-701 277 . Description: An unrecoverable hardware error. diagnostic software. Description: A software error was caused by a hardware failure. Description: A SCSI reservation conflict error. use Chapter 11. Otherwise. adapter. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. go to MAP 210. Description: A SCSI check condition error. 61B-130 61B-132 61B-134 61B-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. and application software to be sure they are all compatible.Service Request Number 61B-108 61B-110 61B-112 61B-114 61B-116 SRN Src. Action: Check the levels of the device. 61B-117 61B-118 61B-120 61B-122 61B-124 61B-126 61B-128 61B-129 D D D D D D G G 61B 61B B88 61B 61B 61B 61B B88 61B 190 61B B88 software 61B 61B B88 software 61B B88 software 61B 61B B88 190 61B Description: A write-protect error occurred. Description: The diagnostic test failed. Description: Disk drive indicates an error. D D D D D Failing Function Codes 61B 61B 61B 61B Description and Action (Unless otherwise indicated. Description: The error log analysis indicates a hardware failure.

61D-130 61D-132 61D-134 61D-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: Error log analysis indicates a SCSI bus problem. adapter. Description: The bus test failed. Description: A SCSI busy or command error. If you do not find a problem. “MAP 0210: General Problem Resolution” on page 67. Description: A protocol error. Description: An unrecoverable media error. Description: The motor failed to restart. Description: The device failed to configure.Service Request Number 61D-099 61D-102 61D-104 61D-105 61D-106 61D-108 61D-110 61D-112 61D-114 61D-116 SRN Src. call your support person. Description: The adapter failed to configure. Description: A SCSI reservation conflict error. use Chapter 11. J D D D D D D D D D Failing Function Codes 61D B88 61D 61D 61D 61D 61D 61D 61D 61D Description and Action (Unless otherwise indicated.) Description: Disk drive not found. Description: A SCSI check condition error. Description: A software error was caused by a hardware failure. Description: Unit attention condition has occurred on the Send Diagnostic command. 61D-117 61D-118 61D-120 61D-122 61D-124 61D-126 61D-128 61D-129 D D D D D D G G 61D 61D B88 61D 61D 61D 61D B88 61D 190 61D B88 software 61D 61D B88 software 61D B88 software 61D 61D B88 190 Description: A write-protect error occurred. 61D-136 61D-137 D D Description: The certify operation failed. Description: A SCSI command time-out. Description: The drive did not become ready. and application software to be sure they are all compatible. Action: Check the levels of the device. Description: An unrecoverable hardware error. Description: A disk drive hardware error occurred. Description: The diagnostic test failed. 278 Diagnostic Information for Multiple Bus Systems . diagnostic software. Description: The electronics card test failed. Description: The error log analysis indicates a hardware failure. Description: The media format is corrupted.

Description: The diagnostic test failed. D Failing Function Codes 61D Description and Action (Unless otherwise indicated. Description: A protocol error. Description: Error log analysis indicates a SCSI bus problem. diagnostic software. Description: A software error was caused by a hardware failure. Action: Check the levels of the device.) Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. Description: The electronics card test failed. Chapter 31. adapter. Description: An unrecoverable media error. Description: The drive did not become ready. Description: A SCSI command time-out. Description: A SCSI check condition error. 61E-136 D Description: The certify operation failed. and application software to be sure they are all compatible. 61E-130 61E-132 61E-134 61E-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Action: Check to be sure none of the air passages in the system covers are blocked. Description: An unrecoverable hardware error. go to MAP 210. Description: The adapter failed to configure. Description: The media format is corrupted. Description: The device failed to configure. Description: The error log analysis indicates a hardware failure. Otherwise. “MAP 0210: General Problem Resolution” on page 67. 61E-102 61E-104 61E-105 61E-106 61E-108 61E-110 61E-112 61E-114 61E-116 D D D D D D D D D 61E 61E 61E 61E 61E 61E 61E 61E 61E-117 61E-118 61E-120 61E-122 61E-124 61E-126 61E-128 61E-129 D D D D D D G G 61E 61E B88 61E 61E 61E 61E B88 61E 190 61E B88 software 61E 61E B88 software 61E B88 software 61E Description: A write-protect error occurred.Service Request Number 61D-138 SRN Src. use Chapter 11. Description: A SCSI busy or command error. call your support person. Description: The bus test failed. Description: The motor failed to restart. If you do not find a problem. that no other system environmental warnings are occurring. SRNs 101-000 through 69d-701 279 . Description: A disk drive hardware error occurred. Description: A SCSI reservation conflict error.

D Failing Function Codes 61E B88 190 61E Description and Action (Unless otherwise indicated. Description: A disk drive hardware error occurred. Description: The diagnostic test failed. 280 Diagnostic Information for Multiple Bus Systems . Description: A SCSI reservation conflict error. If you do not find a problem. 61E-138 D 621-102 621-104 621-105 621-106 621-108 621-110 621-112 621-114 621-116 D D D D D D D D D 621 621 621 621 621 621 621 621 621-117 621-118 621-120 621-122 621-124 621-126 621-128 621-129 D D D D D D G G 621 621 B88 621 621 621 621 B88 621 190 621 B88 software 621 621 B88 software Description: A write-protect error occurred. Description: A SCSI busy or command error. Description: A software error was caused by a hardware failure. Description: The error log analysis indicates a hardware failure. Description: The adapter failed to configure. Action: Check the levels of the device. Description: A protocol error. “MAP 0210: General Problem Resolution” on page 67. Description: The bus test failed. go to MAP 210. Description: Error log analysis indicates a SCSI bus problem. 621-130 621-132 621-134 G D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: The motor failed to restart.Service Request Number 61E-137 SRN Src. and application software to be sure they are all compatible.) Description: Unit attention condition has occurred on the Send Diagnostic command. diagnostic software. Otherwise. Description: An unrecoverable hardware error. Description: The drive did not become ready. adapter. Action: Check to be sure none of the air passages in the system covers are blocked. Description: The electronics card test failed. Description: An unrecoverable media error. use Chapter 11. call your support person. Description: The media format is corrupted. Description: A SCSI check condition error. Description: A SCSI command time-out. that no other system environmental warnings are occurring. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature.

Action: Check the levels of the device. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: A disk drive hardware error occurred. Description: A SCSI command time-out. Description: The motor failed to restart. Description: An unrecoverable hardware error. “MAP 0210: General Problem Resolution” on page 67. Description: The bus test failed.) Description: The device failed to configure. Description: An unrecoverable media error. Description: A SCSI check condition error. 621-136 621-137 D D Description: The certify operation failed. Description: Error log analysis indicates a SCSI bus problem. SRNs 101-000 through 69d-701 281 . go to MAP 210. call your support person. Description: A SCSI reservation conflict error. diagnostic software. Description: A software error was caused by a hardware failure. and application software to be sure they are all compatible. Chapter 31. Description: A protocol error. 621-138 D 623-102 623-104 623-105 623-106 623-108 623-110 623-112 623-114 623-116 D D D D D D D D D 623 623 623 623 623 623 623 623 623-117 623-118 623-120 623-122 623-124 623-126 623-128 623-129 D D D D D D G G 623 623 B88 623 623 623 623 B88 623 190 623 B88 software 623 623 Description: A write-protect error occurred.Service Request Number 621-135 SRN Src. adapter. use Chapter 11. Otherwise. If you do not find a problem. Description: The error log analysis indicates a hardware failure. D Failing Function Codes 621 B88 software 621 621 B88 190 621 Description and Action (Unless otherwise indicated. Description: A SCSI busy or command error. Action: Check to be sure none of the air passages in the system covers are blocked. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. Description: The electronics card test failed. Description: The drive did not become ready. Description: The media format is corrupted. Description: The diagnostic test failed. 623-130 623-132 G D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. that no other system environmental warnings are occurring.

Description: An unrecoverable media error.Service Request Number 623-134 623-135 SRN Src. 282 Diagnostic Information for Multiple Bus Systems . Description: The bus test failed. adapter. Description: A SCSI busy or command error. Description: The media format is corrupted. Description: Error log analysis indicates a SCSI bus problem. and application software to be sure they are all compatible. call your support person. Description: A protocol error. Action: Check the levels of the device. Description: The diagnostic test failed. that no other system environmental warnings are occurring. Description: A software error was caused by a hardware failure. “MAP 0210: General Problem Resolution” on page 67. Description: The electronics card test failed. Description: A SCSI command time-out. Description: An unrecoverable hardware error. use Chapter 11. D D Failing Function Codes B88 software 623 B88 software 623 623 B88 190 623 Description and Action (Unless otherwise indicated.) Description: The adapter failed to configure. Action: Check to be sure none of the air passages in the system covers are blocked. Description: A SCSI check condition error. 623-138 D 624-102 624-104 624-105 624-106 624-108 624-110 624-112 624-114 624-116 D D D D D D D D D 624 624 624 624 624 624 624 624 624-117 624-118 624-120 624-122 624-124 624-126 624-128 624-129 D D D D D D G G 624 624 B88 624 624 624 624 B88 624 190 624 B88 software Description: A write-protect error occurred. If you do not find a problem. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. go to MAP 210. Description: The motor failed to restart. Description: The device failed to configure. Description: Unit attention condition has occurred on the Send Diagnostic command. 623-136 623-137 D D Description: The certify operation failed. Description: A SCSI reservation conflict error. Description: The drive did not become ready. Otherwise. Description: The error log analysis indicates a hardware failure. diagnostic software.

Description: The electronics card test failed. Description: The media format is corrupted. call your support person. Action: Check to be sure none of the air passages in the system covers are blocked. Description: A protocol error. Description: Unit attention condition has occurred on the Send Diagnostic command.Service Request Number 624-130 624-132 624-134 624-135 SRN Src. Description: The drive did not become ready. G D D D Failing Function Codes 624 624 B88 software 624 B88 software 624 624 B88 190 624 Description and Action (Unless otherwise indicated. 624-136 624-137 D D Description: The certify operation failed. “MAP 0210: General Problem Resolution” on page 67. 624-138 D 62D-102 62D-104 62D-105 62D-106 62D-108 62D-110 62D-112 62D-114 62D-116 D D D D D D D D D 62D 62D 62D 62D 62D 62D 62D 62D 62D-117 62D-118 62D-120 62D-122 62D-124 62D-126 62D-128 D D D D D D G 62D 62D B88 62D 62D 62D 62D B88 62D Description: A write-protect error occurred. Description: The error log analysis indicates a hardware failure. Description: A SCSI check condition error. Action: Check the levels of the device. diagnostic software. Description: A disk drive hardware error occurred.) Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: The device failed to configure. Description: The bus test failed. Description: A software error was caused by a hardware failure. Chapter 31. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. Description: The motor failed to restart. Description: A SCSI busy or command error. that no other system environmental warnings are occurring. adapter. go to MAP 210. Otherwise. Description: An unrecoverable media error. SRNs 101-000 through 69d-701 283 . Description: The adapter failed to configure. use Chapter 11. Description: The diagnostic test failed. Description: An unrecoverable hardware error. If you do not find a problem. and application software to be sure they are all compatible. Description: A SCSI command time-out. Description: A SCSI reservation conflict error.

Description: A SCSI check condition error. use Chapter 11.) Description: Error log analysis indicates a SCSI bus problem. G Failing Function Codes 190 62D B88 software 62D 62D B88 software 62D B88 software 62D 62D B88 190 62D Description and Action (Unless otherwise indicated. 62D-136 62D-137 D D Description: The certify operation failed. Description: The motor failed to restart. Description: The diagnostic test failed. Description: A disk drive hardware error occurred. Description: The drive did not become ready. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. diagnostic software. 284 Diagnostic Information for Multiple Bus Systems . Description: An unrecoverable hardware error. adapter. and application software to be sure they are all compatible. 62D-130 62D-132 62D-134 62D-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. go to MAP 210. Description: A protocol error. Description: The device failed to configure. Description: A SCSI reservation conflict error. Description: The adapter failed to configure. Description: The electronics card test failed. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The bus test failed. If you do not find a problem. Description: A SCSI busy or command error.Service Request Number 62D-129 SRN Src. call your support person. Description: A software error was caused by a hardware failure. Description: A SCSI command time-out. Otherwise. that no other system environmental warnings are occurring. Description: An unrecoverable media error. Description: The media format is corrupted. “MAP 0210: General Problem Resolution” on page 67. Action: Check the levels of the device. 62D-138 D 62E-102 62E-104 62E-105 62E-106 62E-108 62E-110 62E-112 62E-114 62E-116 D D D D D D D D D 62E 62E 62E 62E 62E 62E 62E 62E 62E-117 62E-118 62E-120 62E-122 62E-124 62E-126 D D D D D D 62E 62E B88 62E 62E 62E 62E B88 Description: A write-protect error occurred. Action: Check to be sure none of the air passages in the system covers are blocked.

Description: Adapter SDRAM failure. 62E-136 62E-137 D D Description: The certify operation failed. that no other system environmental warnings are occurring. Description: Adapter buffer test failure. “MAP 0210: General Problem Resolution” on page 67. Description: Adapter cache test failure. Description: Adapter memory test failure. Description: Adapter checksum failure. Description: Interrupt test failure. 62E-138 D 636-101 636-102 636-103 636-104 636-105 636-106 636-107 636-108 636-109 636-110 636-111 636-201 636-202 D D D D D D D D D D D D D 636 636 636 636 636 636 636 636 221 221 636 636 221 636 221 Chapter 31. G G Failing Function Codes 62E 190 62E B88 software 62E 62E B88 software 62E B88 software 62E 62E B88 190 62E Description and Action (Unless otherwise indicated. go to MAP 210. Description: Internal loop-back test failure. Description: The device failed to configure. Description: EPROM test failure. Description: A disk drive hardware error occurred. Description: External wrap test failure. Description: Hardware failure opening adapter. Description: Enhanced error handling failure on the adapter.Service Request Number 62E-128 62E-129 SRN Src. SRNs 101-000 through 69d-701 285 . use Chapter 11.) Description: The error log analysis indicates a hardware failure. Description: Unit attention condition has occurred on the Send Diagnostic command. 62E-130 62E-132 62E-134 62E-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Otherwise. Description: Enhanced error handling failure on the bus. Action: Check to be sure none of the air passages in the system covers are blocked. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. Description: The adapter failed to configure. Description: Error log analysis indicates a SCSI bus problem. Description: Enhanced error handling failure on the Eads chip.

“MAP 0050: SCSI Bus Problems” on page 51. “MAP 0210: General Problem Resolution” on page 67. Description: FIFO data miscompare. Description: Enhanced error handling failure opening the adapter. Description: Error during the write/read of the memory register. Description: Enhanced error handling failure on the bus. “MAP 0050: SCSI Bus Problems” on page 51. Description: SCSI FIFO flags error. Action: Go to Chapter 8. Description: SCSI bus data miscompare. Description: SCSI parity error. Description: Arbitration test failed. “MAP 0050: SCSI Bus Problems” on page 51. Action: Go to Chapter 8. Description: Enhanced error handling failure on the adapter.) Description: Adapter DMA test failure. Action: Go to Chapter 8. Description: FIFO empty bit set. Description: Adapter POST failed. Description: Miscompare during the write/read of the configuration register. Description: ELA indicates an I/O failure on the adapter. Description: Function could not complete. Description: SCSI configuration register read or write error. Description: FIFO full bit clear. Description: SCSI wrap or PTC failure. Description: FIFO empty bit clear. “MAP 0050: SCSI Bus Problems” on page 51. Action: Go to Chapter 8. Description: Enhanced error handling failure on a PCI-PCI Bridge. D D G D D D D D D D D D D D D D D D Failing Function Codes 636 221 636 221 636 221 293 637 221 637 637 637 637 637 637 637 637 637 637 221 637 637 Description and Action (Unless otherwise indicated. Description: Miscompare during the write/read of the memory I/O register. Description: SCSI FIFO underflow.Service Request Number 636-203 636-204 636-701 637-101 637-102 637-103 637-212 637-213 637-214 637-215 637-216 637-217 637-218 637-219 637-220 637-221 637-222 637-223 SRN Src. use Chapter 11. Description: FIFO full bit set. 286 Diagnostic Information for Multiple Bus Systems . “MAP 0050: SCSI Bus Problems” on page 51. Action: Go to Chapter 8. Description: SCSI FIFO data miscompare. 637-224 637-225 637-226 637-227 637-230 637-231 637-232 D D D D D D D 637 221 637 637 221 Description: SCSI adapter test failure.

use the SRN to resolve the problem. call your support person. If an SRN is not reported. Description: The electronics card test failed. Description: A protocol error. If an SRN is reported. Action: Check the levels of the device. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. If an SRN is reported. 638-117 638-118 D D 638 638 B88 Description: A write-protect error occurred. use Chapter 11. 637-802 G 637-803 G 638-102 638-104 638-105 638-106 638-108 638-110 638-112 638-114 638-116 D D D D D D D D D 638 638 638 638 638 638 638 638 Description: An unrecoverable media error occurred. Action: Go to Chapter 8. Description: The motor failed to restart. Description: The media format is corrupted. Description: SCSI bus problem. Description: The bus test failed. “MAP 0210: General Problem Resolution” on page 67. and application software to be sure they are all compatible. use the SRN to resolve the problem. Chapter 31. If an SRN is reported. “MAP 0050: SCSI Bus Problems” on page 51. Description: The diagnostic test failed. Description: Error log analysis indicates that multiple attempts to reset the SCSI bus have timed out. Action: Run the diagnostics on the adapter in System Verification mode.) Description: No terminal power. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. D D D G G Failing Function Codes Description and Action (Unless otherwise indicated. use the SRN to resolve the problem. Action: Run the diagnostics on the adapter in System Verification mode. Description: Error log analysis indicates a terminator problem. “MAP 0050: SCSI Bus Problems” on page 51. adapter. 637 221 637 Description: The parent device open failed. Description: An unrecoverable hardware error. Action: Go to Chapter 8. Description: Error log analysis indicates that multiple SCSI bus errors have occurred. If an SRN is not reported. If you do not find a problem. If an SRN is not reported. diagnostic software. Description: Error log analysis indicates a PCI SCSI adapter failure. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. Description: A SCSI command time-out occurred. SRNs 101-000 through 69d-701 287 .Service Request Number 637-240 637-242 637-301 637-701 637-801 SRN Src. Action: Run the diagnostics on the adapter in System Verification mode. Description: The drive did not become ready.

Description: A software error was caused by a hardware failure.) Description: A SCSI busy or command error. Description: A disk drive hardware error occurred. Description: The drive did not become ready. use Chapter 11. 638-130 638-132 638-134 638-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: Error log analysis indicates a SCSI bus problem. Description: A SCSI reservation conflict error.Service Request Number 638-120 638-122 638-124 638-126 638-128 638-129 SRN Src. D D D D G G Failing Function Codes 638 638 638 638 B88 638 190 638 B88 software 638 638 B88 software 638 B88 software 638 638 B88 190 639 639 639 639 639 639 639 639 Description and Action (Unless otherwise indicated. adapter. 639-102 639-104 639-105 639-106 639-108 639-110 639-112 639-114 639-116 D D D D D D D D D 639-117 639-118 639-120 639-122 D D D D 639 639 B88 639 639 Description: A write-protect error occurred. Description: A SCSI command time-out occurred. 288 Diagnostic Information for Multiple Bus Systems . Description: An unrecoverable media error occurred. “MAP 0210: General Problem Resolution” on page 67. and application software to be sure they are all compatible. Description: The device failed to configure. diagnostic software. Description: A SCSI busy or command error. If you do not find a problem. call your support person. Description: The motor failed to restart. Description: The error log analysis indicates a hardware failure. Description: The bus test failed. Description: A SCSI check condition error occurred. Description: The diagnostic test failed. Description: The media format is corrupted. Description: The adapter failed to configure. 638-136 638-137 D D Description: The certify operation failed. Description: A SCSI reservation conflict error. Action: Check the levels of the device. Description: A protocol error. Description: The electronics card test failed. Description: An unrecoverable hardware error.

) Description: A SCSI check condition error occurred. Action: Check to be sure none of the air passages in the system covers are blocked. Description: The drive did not become ready. SRNs 101-000 through 69d-701 289 . Description: The device failed to configure. Description: A software error was caused by a hardware failure. diagnostic software. go to MAP 210. Description: An unrecoverable hardware error. “MAP 0210: General Problem Resolution” on page 67. adapter. that no other system environmental warnings are occurring. call your support person. Otherwise. Description: The bus test failed. Description: Use the SRN value 62D-xxx. Description: Unit attention condition has occurred on the Send Diagnostic command. 639-138 D 63A-xxx 63B-102 63B-104 63B-105 63B-106 63B-108 63B-110 63B-112 63B-114 63B-116 D D D D D D D D D D 63B 63B 63B 63B 63B 63B 63B 63B Description: An unrecoverable media error.Service Request Number 639-124 639-126 639-128 639-129 SRN Src. Description: The error log analysis indicates a hardware failure. Description: A disk drive hardware error occurred. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. Action: Check the levels of the device. D D G G Failing Function Codes 639 639 B88 639 190 639 B88 software 639 639 B88 software 639 B88 software 639 639 B88 190 639 Description and Action (Unless otherwise indicated. 63B-117 D 63B Description: A write-protect error occurred. Description: The motor failed to restart. Description: The diagnostic test failed. Chapter 31. use Chapter 11. Description: Error log analysis indicates a SCSI bus problem. and application software to be sure they are all compatible. 639-136 639-137 D D Description: The certify operation failed. Description: The adapter failed to configure. Description: A protocol error. Description: The electronics card test failed. Description: The media format is corrupted. If you do not find a problem. 639-130 639-132 639-134 639-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function.

Description: The adapter failed to configure. 63C-xxx 63D-102 63D-104 63D-105 63D-106 63D-108 63D-110 63D-112 63D-114 63D-116 D D D D D D D D D D 63D 63D 63D 63D 63D 63D 63D 63D Description: An unrecoverable media error. 290 Diagnostic Information for Multiple Bus Systems . “MAP 0210: General Problem Resolution” on page 67. Description: A SCSI reservation conflict error. Description: The device failed to configure. If you do not find a problem. 63B-130 63B-132 63B-134 63B-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. and application software to be sure they are all compatible. Description: The electronics card test failed. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The drive did not become ready. adapter. Description: An unrecoverable hardware error. 63D-117 63D-118 D D 63D 63D B88 Description: A write-protect error occurred. Description: A disk drive hardware error occurred. 63B-136 63B-137 D D Description: The certify operation failed. use Chapter 11.) Description: A SCSI command time-out. Description: The error log analysis indicates a hardware failure. D D D D D G G Failing Function Codes 63B B88 63B 63B 63B 63B B88 63B 190 63B B88 software 63B 63B B88 software 63B B88 software 63B 63B B88 190 Description and Action (Unless otherwise indicated. Description: Error log analysis indicates a SCSI bus problem. Description: The media format is corrupted. Description: A protocol error. Description: The motor failed to restart. Description: A SCSI busy or command error. Description: The diagnostic test failed. Action: Check the levels of the device. Description: A SCSI command time-out. call your support person.Service Request Number 63B-118 63B-120 63B-122 63B-124 63B-126 63B-128 63B-129 SRN Src. Description: The bus test failed. Description: A SCSI check condition error. diagnostic software. Description: Use the SRN value 60B-xxx. Description: A software error was caused by a hardware failure.

) Description: A SCSI busy or command error. Description: The adapter failed to configure. Description: A protocol error. If you do not find a problem. Description: The diagnostic test failed. 63D-138 D 63E-102 63E-104 63E-105 63E-106 63E-108 63E-110 63E-112 63E-114 63E-116 D D D D D D D D D 63E 63E 63E 63E 63E 63E 63E 63E 63E-117 D 63E Description: A write-protect error occurred. Description: An unrecoverable media error. that no other system environmental warnings are occurring. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature.Service Request Number 63D-120 63D-122 63D-124 63D-126 63D-128 63D-129 SRN Src. Action: Check to be sure none of the air passages in the system covers are blocked. Description: A SCSI reservation conflict error. Description: The motor failed to restart. Description: A software error was caused by a hardware failure. 63D-136 63D-137 D D Description: The certify operation failed. go to MAP 210. Description: The device failed to configure. Description: An unrecoverable hardware error. Chapter 31. adapter. Description: Unit attention condition has occurred on the Send Diagnostic command. and application software to be sure they are all compatible. “MAP 0210: General Problem Resolution” on page 67. Otherwise. 63D-130 63D-132 63D-134 63D-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: The media format is corrupted. Description: A disk drive hardware error occurred. diagnostic software. use Chapter 11. Description: The error log analysis indicates a hardware failure. Description: The drive did not become ready. D D D D G G Failing Function Codes 63D 63D 63D 63D B88 63D 190 63D B88 software 63D 63D B88 software 63D B88 software 63D 63D B88 190 63D Description and Action (Unless otherwise indicated. Action: Check the levels of the device. call your support person. Description: A SCSI check condition error. Description: The bus test failed. SRNs 101-000 through 69d-701 291 . Description: The electronics card test failed. Description: Error log analysis indicates a SCSI bus problem.

Description: The diagnostic test failed. Description: The device failed to configure. Description: The bus test failed. Description: The motor failed to restart. Description: Unit attention condition has occurred on the Send Diagnostic command. D D D D D G G Failing Function Codes 63E B88 63E 63E 63E 63E B88 63E 190 63E B88 software 63E 63E B88 software 63E B88 software 63E 63E B88 190 63E Description and Action (Unless otherwise indicated. Description: The drive did not become ready. Action: Check to be sure none of the air passages in the system covers are blocked. 63E-136 63E-137 D D Description: The certify operation failed. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. Description: An unrecoverable hardware error. Description: The adapter failed to configure. Description: Use the SRN value 61B-xxx. Description: A SCSI busy or command error. 292 Diagnostic Information for Multiple Bus Systems . Description: Error log analysis indicates a SCSI bus problem. Description: The electronics card test failed. Description: A SCSI check condition error. that no other system environmental warnings are occurring. go to MAP 210. Description: The media format is corrupted. “MAP 0210: General Problem Resolution” on page 67. 63E-130 63E-132 63E-134 63E-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function.Service Request Number 63E-118 63E-120 63E-122 63E-124 63E-126 63E-128 63E-129 SRN Src.) Description: A SCSI command time-out. Otherwise. Description: A software error was caused by a hardware failure. Description: A SCSI reservation conflict error. Description: The error log analysis indicates a hardware failure. Description: A disk drive hardware error occurred. 63E-138 D 63F-xxx 640-102 640-104 640-105 640-106 640-108 640-110 640-112 640-114 D D D D D D D D D 640 640 640 640 640 640 640 640 Description: An unrecoverable media error occurred. use Chapter 11.

Description: A disk drive hardware error occurred. go to MAP 210. Description: The adapter failed to configure. Description: The electronics card test failed.Service Request Number 640-116 SRN Src. Description: The media format is corrupted. Description: The error log analysis indicates a hardware failure. D Failing Function Codes Description and Action (Unless otherwise indicated. use Chapter 11. that no other system environmental warnings are occurring. Description: A SCSI busy or command error. and application software to be sure they are all compatible. Description: Error log analysis indicates a SCSI bus problem. diagnostic software. Description: A SCSI check condition error occurred. Description: The device failed to configure. 640-130 640-132 640-134 640-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. 640-136 640-137 D D Description: The certify operation failed. Description: Unit attention condition has occurred on the Send Diagnostic command. SRNs 101-000 through 69d-701 293 . “MAP 0210: General Problem Resolution” on page 67. Description: The motor failed to restart. Description: A software error was caused by a hardware failure. 640-138 D 643-102 643-104 643-105 643-106 643-108 643-110 D D D D D D 643 643 643 643 643 643 Chapter 31. Description: A SCSI command time-out occurred. Description: The bus test failed. Description: A SCSI reservation conflict error. adapter. Description: An unrecoverable media error occurred. If you do not find a problem. call your support person. Action: Check to be sure none of the air passages in the system covers are blocked.) Description: A protocol error. 640-117 640-118 640-120 640-122 640-124 640-126 640-128 640-129 D D D D D D G G 640 640 B88 640 640 640 640 B88 640 190 640 B88 software 640 640 B88 software 640 B88 software 640 640 B88 190 640 Description: A write-protect error occurred. Description: The drive did not become ready. Otherwise. Action: Check the levels of the device.

643-136 643-137 D D Description: The certify operation failed. Description: Unit attention condition has occurred on the Send Diagnostic command. 643-117 643-118 643-120 643-122 643-124 643-126 643-128 643-129 D D D D D D G G 643 643 B88 643 643 643 643 B88 643 190 643 B88 software 643 643 B88 software 643 B88 software 643 643 B88 190 644 644 644 644 644 644 644 644 Description: A write-protect error occurred.) Description: The diagnostic test failed. Description: The adapter failed to configure. Description: The error log analysis indicates a hardware failure. call your support person. Description: A software error was caused by a hardware failure. 643-130 643-132 643-134 643-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: An unrecoverable hardware error. use Chapter 11. Description: The media format is corrupted.Service Request Number 643-112 643-114 643-116 SRN Src. Description: Error log analysis indicates a SCSI bus problem. Description: A protocol error. Description: An unrecoverable hardware error. Description: A SCSI reservation conflict error. Description: The drive did not become ready. Description: The device failed to configure. Description: A SCSI busy or command error. Description: The electronics card test failed. If you do not find a problem. Description: An unrecoverable media error occurred. Description: A SCSI command time-out occurred. Description: The bus test failed. adapter. and application software to be sure they are all compatible. D D D Failing Function Codes 643 643 Description and Action (Unless otherwise indicated. diagnostic software. Description: A disk drive hardware error occurred. Description: The motor failed to restart. Description: The diagnostic test failed. “MAP 0210: General Problem Resolution” on page 67. Action: Check the levels of the device. 644-102 644-104 644-105 644-106 644-108 644-110 644-112 644-114 D D D D D D D D 294 Diagnostic Information for Multiple Bus Systems . Description: A SCSI check condition error occurred.

Description: A SCSI busy or command error. Description: The error log analysis indicates a hardware failure. Description: A SCSI check condition error occurred. D Failing Function Codes Description and Action (Unless otherwise indicated. diagnostic software. Action: Check the levels of the device. Description: I/O Test Failure. Description: Enhanced Error Handling failure on bus. Description: Wrap Test Failure. “MAP 0210: General Problem Resolution” on page 67. 646-101 646-102 646-103 646-104 646-105 646-106 646-107 646-108 646-201 D D D D D D D D D Chapter 31. If you do not find a problem. Description: Error log analysis indicates a SCSI bus problem. Description: Unit attention condition has occurred on the Send Diagnostic command. 644-130 644-132 644-134 644-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: External Test Failure. Description: The device failed to configure. Description: A software error was caused by a hardware failure. Description: The adapter failed to configure. SRNs 101-000 through 69d-701 295 . 644-117 644-118 644-120 644-122 644-124 644-126 644-128 644-129 D D D D D D G G 644 644 B88 644 644 644 644 B88 644 190 644 B88 software 644 644 B88 software 644 B88 software 644 644 B88 190 D46 240 646 646 221 646 646 646 646 646 221 Description: A write-protect error occurred. use Chapter 11. Description: A SCSI command time-out occurred. Description: EEH failure on Eads chip.Service Request Number 644-116 SRN Src. call your support person. Description: A disk drive hardware error occurred. and application software to be sure they are all compatible. Description: Configuration Register Test Failure. Description: A SCSI reservation conflict error. Description: External Test Failure. 644-136 644-137 D D Description: The certify operation failed. Description: Enhanced Error Handling failure on adapter. adapter.) Description: A protocol error. Description: Adapter On-card Test Failure.

Description: The electronics card test failed. Description: ELA indicates an internal adapter error has occurred. Action: Run advanced diagnostics with wrap test for this resource to obtain a correct problem resolution. 296 Diagnostic Information for Multiple Bus Systems . Description: Error log analysis indicates that a Programmed I/O error has occurred. Action: Run advanced diagnostics with wrap test for this resource to obtain a correct problem resolution. Description: Error log analysis indicates that an adapter error has occurred. Description: Error log analysis indicates that a PCI Bus error has occurred. D F F Failing Function Codes 646 221 D46 240 D46 646 240 646 240 D46 221 D46 646 221 240 D46 646 221 646 646 646 221 646 221 646 221 646 646 Description and Action (Unless otherwise indicated. Description: External Test Failure. Description: External Test Failure. Description: The diagnostic test failed. “MAP 0210: General Problem Resolution” on page 67. Action: Run advanced diagnostics with wrap test for this resource to obtain a correct problem resolution. 646-206 F 646-302 F 646-303 F 646-401 F 646-701 646-702 646-703 646-704 646-705 646-706 646-707 64A-xxx 64B-102 64B-104 64B-105 64B-106 64B-108 64B-110 64B-112 G G G G G G G D D D D D D D D 64B 64B 64B 64B 64B 64B 64B Description: An unrecoverable media error. use Chapter 11. Description: External Test Failure.Service Request Number 646-202 646-204 646-205 SRN Src. Description: The motor failed to restart. Description: External Test Failure. Action: Run advanced diagnostics with wrap test for this resource to obtain a correct problem resolution. Description: External Test Failure. Description: The bus test failed.) Description: Wrap Test Failure. Description: The media format is corrupted. Description: Error log analysis indicates that a DMA failure has occurred. Action: Run advanced diagnostics with wrap test for this resource to obtain a correct problem resolution. Description: ELA indicates a command write failure occurred. Description: The drive did not become ready. Description: Use the SRN value 62E-xxx. Description: External Test Failure. Description: Error log analysis indicates that an adapter check has occurred.

Description: The adapter failed to configure. Description: A software error was caused by a hardware failure. Description: The error log analysis indicates a hardware failure. diagnostic software. Description: The device failed to configure. Description: A SCSI busy or command error. D D Failing Function Codes 64B Description and Action (Unless otherwise indicated.Service Request Number 64B-114 64B-116 SRN Src. Description: The electronics card test failed. Description: The motor failed to restart. 64B-138 D 64C-xxx 64D-102 64D-104 64D-105 64D-106 D D D D D 64D 64D 64D 64D Description: An unrecoverable media error. adapter. Otherwise. Description: A SCSI reservation conflict error. 64B-130 64B-132 64B-134 64B-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: A disk drive hardware error occurred. If you do not find a problem. Description: A SCSI command time-out.) Description: An unrecoverable hardware error. Description: The drive did not become ready. use Chapter 11. 64B-136 64B-137 D D Description: The certify operation failed. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. “MAP 0210: General Problem Resolution” on page 67. Action: Check the levels of the device. call your support person. SRNs 101-000 through 69d-701 297 . Action: Check to be sure none of the air passages in the system covers are blocked. Description: Unit attention condition has occurred on the Send Diagnostic command. that no other system environmental warnings are occurring. Description: A protocol error. Description: Error log analysis indicates a SCSI bus problem. Description: A SCSI check condition error. and application software to be sure they are all compatible. go to MAP 210. Description: Use the SRN value 61E-xxx. 64B-117 64B-118 64B-120 64B-122 64B-124 64B-126 64B-128 64B-129 D D D D D D G G 64B 64B B88 64B 64B 64B 64B B88 64B 190 64B B88 software 64B 64B B88 software 64B B88 software 64B 64B B88 190 64B Description: A write-protect error occurred. Chapter 31.

Description: A SCSI reservation conflict error. that no other system environmental warnings are occurring. call your support person.) Description: The bus test failed. Description: An unrecoverable hardware error. Otherwise. Description: Error log analysis indicates a SCSI bus problem. Description: A protocol error. Description: A SCSI command time-out. Description: An unrecoverable media error. 64D-117 64D-118 64D-120 64D-122 64D-124 64D-126 64D-128 64D-129 D D D D D D G G 64D 64D B88 64D 64D 64D 64D B88 64D 190 64D B88 software 64D 64D B88 software 64D B88 software 64D 64D B88 190 64D Description: A write-protect error occurred. 64D-136 64D-137 D D Description: The certify operation failed. and application software to be sure they are all compatible. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The media format is corrupted. go to MAP 210. Description: A disk drive hardware error occurred. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. Description: A software error was caused by a hardware failure. 64D-130 64D-132 64D-134 64D-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. adapter. 64D-138 D 64E-102 64E-104 D D 64E 64E 298 Diagnostic Information for Multiple Bus Systems .Service Request Number 64D-108 64D-110 64D-112 64D-114 64D-116 SRN Src. Action: Check the levels of the device. If you do not find a problem. Description: The device failed to configure. Description: The motor failed to restart. Description: The adapter failed to configure. Action: Check to be sure none of the air passages in the system covers are blocked. Description: A SCSI busy or command error. “MAP 0210: General Problem Resolution” on page 67. Description: A SCSI check condition error. use Chapter 11. D D D D D Failing Function Codes 64D 64D 64D 64D Description and Action (Unless otherwise indicated. diagnostic software. Description: The diagnostic test failed. Description: The error log analysis indicates a hardware failure.

Description: The diagnostic test failed. that no other system environmental warnings are occurring. call your support person. adapter. 64E-138 D Chapter 31. and application software to be sure they are all compatible. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: A SCSI reservation conflict error. 64E-130 64E-132 64E-134 64E-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. 64E-117 64E-118 64E-120 64E-122 64E-124 64E-126 64E-128 64E-129 D D D D D D G G 64E 64E B88 64E 64E 64E 64E B88 64E 190 64E B88 software 64E 64E B88 software 64E B88 software 64E 64E B88 190 64E Description: A write-protect error occurred. use Chapter 11. Description: A disk drive hardware error occurred. Description: The media format is corrupted. If you do not find a problem. Otherwise.Service Request Number 64E-105 64E-106 64E-108 64E-110 64E-112 64E-114 64E-116 SRN Src. Description: An unrecoverable hardware error. Description: The bus test failed. Description: The error log analysis indicates a hardware failure. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. Action: Check the levels of the device. Description: A SCSI command time-out. Description: A SCSI busy or command error. “MAP 0210: General Problem Resolution” on page 67. go to MAP 210. Description: Error log analysis indicates a SCSI bus problem. Description: The adapter failed to configure.) Description: The drive did not become ready. diagnostic software. 64E-136 64E-137 D D Description: The certify operation failed. SRNs 101-000 through 69d-701 299 . Description: A software error was caused by a hardware failure. Action: Check to be sure none of the air passages in the system covers are blocked. Description: A SCSI check condition error. Description: The device failed to configure. Description: A protocol error. Description: The electronics card test failed. D D D D D D D Failing Function Codes 64E 64E 64E 64E 64E 64E Description and Action (Unless otherwise indicated.

then proceed with Chapter 12. “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77. There are no fan failures. If none of these problems exist. 651-159 D 651-160 D 166 2E0 152 2E2 2E1 Description: Sensor indicates a fan is turning too slowly. “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77. The room ambient temperature is within the system operating environment. 3. Description: Sensor indicates a voltage is outside the normal range. All system covers are closed. Action: Use MAP 1520. 651-161 651-162 D D 300 Diagnostic Information for Multiple Bus Systems . “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77. Description: Sensor indicates a voltage is outside the normal range. 3.) Description: Use the SRN value 61D-xxx. Action: Use MAP 1520. Action: Use Chapter 12. There are no fan failures. 4. Description: Sensor indicates a FRU has failed. 2. 2. 651-151 651-152 D D 651-153 D 152 E19 Description: Sensor indicates a power supply has failed. Description: Sensor indicates a fan has failed. Description: Display Character test failed. Action: Use Chapter 12. If none of these problems exist. The room ambient temperature is within the system operating environment. There is unrestricted air flow around the system. Description: Sensor indicates an abnormally high internal temperature. D D D D Failing Function Codes Description and Action (Unless otherwise indicated. “MAP 0210: General Problem Resolution” on page 67. 650 165 221 166 2E0 152 2E2 2E1 Description: Disk drive configuration failed. Action: Verify that: 1. Action: Verify that: 1. Description: Sensor indicates an abnormally high internal temperature.Service Request Number 64F-xxx 650-xxx 651-140 651-150 SRN Src. 4. There is unrestricted air flow around the system. Action: Use Chapter 12. All system covers are closed. Instead of failing function codes. use the physical location code(s) from the diagnostic problem report screen to determine the FRUs. “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77. “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77. Action: Use MAP 210. then proceed with Chapter 12. use Chapter 11.

) Description: Sensor indicates a power supply has failed.Service Request Number 651-163 SRN Src. Action: Examine the memory modules and determine if they are supported types. Description: Uncorrectable memory or unsupported memory. D Failing Function Codes 152 E19 Description and Action (Unless otherwise indicated. SRNs 101-000 through 69d-701 301 . 651-169 D 651-170 651-171 651-600 D D G 651-601 G 651-602 G 2C5 2C7 2C6 2C7 2C5 Description: Failed memory module. Action: Use Chapter 12. Action: Use MAP 210. Action: Contact your support person. Instead of failing function codes. use Chapter 11. Description: Bad L2 Cache. Contact your support center to determine if a newer level of firmware is available for your system. Description: Failed memory module. Description: Missing or bad memory Action: If the installed memory matches the reported memory size. “MAP 0240: Memory Problem Resolution” on page 93 to identify the paired module. Refer to the Service Processor menus to determine if the processor was manually deconfigured.2) or IY01606 (4. “MAP 0240: Memory Problem Resolution” on page 93. Description: Sensor status not available Action: Contact your support person. Use Chapter 15. If the modules are supported. “MAP 0240: Memory Problem Resolution” on page 93. Description: Memory module has no matched pair.3). 651-603 G 651-604 G 651-605 G 2C6 651-608 G D01 651-609 G D01 Chapter 31. “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77. then replace the memory: otherwise. Use Chapter 15. Action: The most probable failure is the memory module paired with the memory module identified by the location code. Action: Use Chapter 15. “MAP 0210: General Problem Resolution” on page 67. use the physical location code(s) from the diagnostic problem report screen to determine the FRUs. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93 to identify the paired module. Action: The most probable failure is the memory module paired with the memory module identified by the location code. If the processor was manually deconfigured and you got this SRN. then replace the appropriate memory module(s). Description: Sensor indicates a FRU has failed. add the missing memory. Description: Memory module has no matched pair. Note: Disregard this SRN if the processor for this cache was manually deconfigured. Description: Missing L2 Cache. Description: Sensor status not available. you need to apply AIX APAR IY01637 (4.

“MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. 302 Diagnostic Information for Multiple Bus Systems . Description: System bus time-out error. Action: Use MAP 210. use the physical location code(s) from the diagnostic problem report screen to determine the FRUs. Action: Use MAP 210.r Description: External cache parity or multi-bit ECC error. Description: Error log analysis indicates an error detected by the memory controller. Description: Memory address error (invalid address or access attempt). Description: Time-out error waiting for I/O. Description: System bus protocol/transfer error.Service Request Number 651-610 651-611 651-612 651-613 651-614 651-615 651-619 SRN Src. G G G G G G G Failing Function Codes 210 210 D01 D01 214 292 Description and Action (Unless otherwise indicated. 651-633 G Description: I/O Expansion Unit not in an operating state. Description: Memory Control Subsystem internal error. Description: CPU internal cache controller erro. Description: Error log analysis indicates an error detected by the CPU. Description: Correctable error threshold exceeded Action: Use Chapter 15. Description: I/O Expansion Bus Time-out Error. Description: ECC correctable error Action: Use Chapter 15. Description: Internal Device Error. Description: Correctable error threshold exceeded Action: Use Chapter 15. 651-620 G 2C5 Description: ECC correctable error Action: Use Chapter 15. use Chapter 11. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. use the physical location code(s) from the diagnostic problem report screen to determine the FRUs.) Description: CPU internal error. Description: System bus time-out error. Description: Memory Data error (Bad data going to memory). Instead of failing function codes. Description: External cache ECC single-bit error. 651-621 G 2C6 651-622 G 2C5 651-623 G 2C6 651-624 651-625 651-626 651-627 651-628 651-629 G G G G G G 214 214 214 214 210 651-630 651-631 651-632 G G G 307 307 306 307 308 307 306 Description: I/O Expansion Bus Parity Error. Instead of failing function codes. “MAP 0210: General Problem Resolution” on page 67.

Action: Use Chapter 15. Action: Use Chapter 15. Description: Internal Service Processor firmware error. “MAP 0210: General Problem Resolution” on page 67.Service Request Number 651-634 651-639 SRN Src. Description: ECC correctable error. 651-651 G E18 651-653 G 301 651-654 G 302 651-655 G 303 651-656 G 304 651-657 G 305 651-658 G 30A 651-659 G 2CD 651-65A G 2CE Chapter 31. Action: Use Chapter 15. use the physical location code(s) from the diagnostic problem report screen to determine the FRUs. Action: Use Chapter 15. Description: ECC correctable error. “MAP 0240: Memory Problem Resolution” on page 93. Description: Other internal Service Processor hardware error. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. Description: ECC correctable error. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. Description: Internal Service Processor memory error. Action: Use Chapter 15. Description: Secondary I/O general bus error. action: Use Chapter 15. 651-640 651-641 651-642 651-643 651-644 651-650 G G G G G G 2D5 2D6 2D3 2D3 2D3 E17 Description: I/O general bus error. Description: ECC correctable error. “MAP 0240: Memory Problem Resolution” on page 93. Description: ECC correctable error. Description: ECC correctable error. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93.) Description: Internal Device Error. Description: ECC correctable error. Description: Error log analysis indicates an error detected by the I/O. Instead of failing function codes. Action: Use Chapter 15. Description: ECC correctable error. use Chapter 11. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. Description: ECC correctable error. G G Failing Function Codes 307 Description and Action (Unless otherwise indicated. “MAP 0240: Memory Problem Resolution” on page 93. Description: ECC correctable error. Action: Use Chapter 15. SRNs 101-000 through 69d-701 303 . Action: Use Chapter 15. Action: Use MAP 210.

“MAP 0240: Memory Problem Resolution” on page 93. Description: Correctable error threshold exceeded. Description: Correctable error threshold exceeded. Description: Correctable error threshold exceeded. Description: Correctable error threshold exceeded. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. Action: Use Chapter 15. Action: Use Chapter 15. Action: Use Chapter 15. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93.Service Request Number 651-65B SRN Src. “MAP 0210: General Problem Resolution” on page 67. 651-65C G 30B 651-660 G E17 651-661 G E18 651-663 G 301 651-664 G 302 651-665 G 303 651-666 G 304 651-667 G 305 651-668 G 30A 651-669 G 2CD 651-66A G 2CE 651-66B G 2CC 651-66C G 30B 651-670 G E17 2C7 304 Diagnostic Information for Multiple Bus Systems . “MAP 0240: Memory Problem Resolution” on page 93. Description: Correctable error threshold exceeded. G Failing Function Codes 2CC Description and Action (Unless otherwise indicated. Action: Use Chapter 15. Description: Failed memory module. “MAP 0240: Memory Problem Resolution” on page 93.) Description: ECC correctable error. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. Description: Correctable error threshold exceeded. “MAP 0240: Memory Problem Resolution” on page 93. Description: Correctable error threshold exceeded. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. use Chapter 11. Description: Correctable error threshold exceeded. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. Description: ECC correctable error. Action: Use Chapter 15. Description: Correctable error threshold exceeded. Action: Use Chapter 15. Description: Correctable error threshold exceeded. Description: Correctable error threshold exceeded. Description: Correctable error threshold exceeded. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93.

Service Request Number 651-671 SRN Src.) Description: Failed memory module. “MAP 0240: Memory Problem Resolution” on page 93. Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93 to identify the paired module. Description: Failed memory module. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. SRNs 101-000 through 69d-701 305 . “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0210: General Problem Resolution” on page 67. “MAP 0240: Memory Problem Resolution” on page 93. Description: Failed memory module. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. Action: The most probable failure is the memory module paired with the memory module identified by the location code. Description: Memory module has no matched pair. Description: Failed memory module. Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Description: Failed memory module. 651-673 G 651-674 G 302 651-675 G 303 651-676 G 304 651-677 G 305 651-678 G 30A 651-679 G 2CD 651-67A G 2CE 651-67B G 2CC 651-67C G 30B 651-680 G E17 651-681 G E18 Chapter 31. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. Action: The most probable failure is the memory module paired with the memory module identified by the location code. Description: Failed memory module. “MAP 0240: Memory Problem Resolution” on page 93 to identify the paired module. G Failing Function Codes E18 2C7 301 Description and Action (Unless otherwise indicated. Action: Use Chapter 15. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. Description: Failed memory module. Description: Failed memory module. Description: Failed memory module. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. Description: Failed memory module. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. Action: Use Chapter 15. Action: Use Chapter 15. Description: Memory module has no matched pair. use Chapter 11. Description: Failed memory module.

Use the system Service Guide to determine how the memory cards are grouped. Description: Memory card has no matched pair. then use Chapter 15. use Chapter 11. Use the system Service Guide to determine how the memory cards are grouped. Use Chapter 15. Description: Memory module has no matched pair. Action: The most probable failure is the memory module paired with the memory module identified by the location code. Description: Memory card has no matched pair. Action: The most probable failure is the memory module paired with the memory module identified by the location code.Service Request Number 651-683 SRN Src. then use Chapter 15.) Description: Memory module has no matched pair. 651-684 G 302 651-685 G 303 651-686 G 304 651-687 G 305 651-688 G 30A 651-689 G 2CD 651-68A G 2CE 306 Diagnostic Information for Multiple Bus Systems . “MAP 0240: Memory Problem Resolution” on page 93 to replace the paired card. Action: The most probable failure is the memory module paired with the memory module identified by the location code. “MAP 0240: Memory Problem Resolution” on page 93 to replace the paired card. Action: The most probable failure is the memory card paired with the memory card identified by the location code. “MAP 0240: Memory Problem Resolution” on page 93 to identify the paired module. Use the system Service Guide to determine how the memory cards are grouped. Use Chapter 15. Action: The most probable failure is the memory card paired with the memory card identified by the location code. Action: The most probable failure is the memory module paired with the memory module identified by the location code. then use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93 to identify the paired module. Description: Memory module has no matched pair. Action: The most probable failure is the memory module paired with the memory module identified by the location code. Description: Memory module has no matched pair. “MAP 0240: Memory Problem Resolution” on page 93 to identify the paired module. “MAP 0240: Memory Problem Resolution” on page 93 to replace the paired card. Action: The most probable failure is the memory card paired with the memory card identified by the location code. “MAP 0240: Memory Problem Resolution” on page 93 to identify the paired module. Use Chapter 15. Use Chapter 15. “MAP 0210: General Problem Resolution” on page 67. Use Chapter 15. Description: Memory module has no matched pair. “MAP 0240: Memory Problem Resolution” on page 93 to identify the paired module. G Failing Function Codes 301 Description and Action (Unless otherwise indicated. Description: Memory card has no matched pair.

“MAP 0240: Memory Problem Resolution” on page 93. 651-726 G Description: I/O Host Bridge timeout caused by software. Action: Refer to the Error Code to FRU Index in the system unit’s service guide. Description: System bus parity error. SRNs 101-000 through 69d-701 307 . 651-713 651-714 G G Description: System bus protocol/transfer error. 651-725 G Description: I/O Host Bridge address/data parity error. “MAP 0210: General Problem Resolution” on page 67. 651-724 G Description: I/O Host Bridge time-out error. G G Failing Function Codes 214 2C4 214 210 2C4 214 210 210 2C4 214 2C4 214 210 2C4 214 210 210 2C4 2C5 2C7 214 2C6 2C7 214 210 2C4 214 210 2C4 214 292 2C8 214 763 292 2C8 214 763 Software Description and Action (Unless otherwise indicated. 651-720 G Description: Uncorrectable Memory Error Action: Use Chapter 15. use Chapter 11. Description: System bus protocol/transfer error. 651-712 G Description: System bus parity error. Contact software support for assistance. Description: Uncorrectable Memory Error Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93.Service Request Number 651-710 651-711 SRN Src. 651-721 G 651-722 G 651-723 G Description: System bus protocol/transfer error. Description: System bus parity error. 651-730 G Chapter 31. Description: I/O error on the ISA bus. 651-715 G Description: System bus protocol/transfer error.) Description: System bus parity error. Action: This error is caused by a software or operating system attempt to access an invalid memory address.

Description: Service Processor error accessing Power Controller. “MAP 0210: General Problem Resolution” on page 67. Description: Intermediate or System Bus Address Parity Error. Description: Intermediate or System Bus Data Parity Error. Description: Intermediate or System Bus Time-out Error. Description: Time-out on communication response from Service Processor Description: Service Processor error accessing special registers. 651-732 G 651-733 G 651-734 G 651-735 651-736 G G 651-740 G Note: Ensure that the system IPLROS and Service Processor are at the latest firmware level before removing any parts from the system.Service Request Number 651-731 SRN Src. Description: Service Processor error accessing Operator Panel. Description: Intermediate or System Bus Time-out Error. Description: Service Processor error accessing Vital Product Data EEPROM. Description: Service Processor reports unknown communication error. Description: Intermediate or System Bus Data Parity Error. Description: Service Processor detected NVRAM error. Description: Service Processor error accessing Serial Port. G Failing Function Codes 2C8 292 763 2C8 292 763 214 2C8 292 214 2C8 292 2D2 292 2D2 292 214 2D3 2D4 Description and Action (Unless otherwise indicated. use Chapter 11. 651-741 651-742 651-743 651-744 G G G G 2D3 2D4 2D3 2D4 2D7 2D5 165 2D5 2D3 2D9 2D5 2E0 2D4 2E1 2D5 2E2 2D5 2E3 2D4 814 2D4 651-745 651-746 651-747 651-748 651-749 651-750 G G G G G G 308 Diagnostic Information for Multiple Bus Systems .) Description: Intermediate or System Bus Address Parity Error. Description: Service Processor error accessing Fan Sensor. Description: Service Processor error accessing Voltage Sensor. Description: Service Processor error accessing Thermal Sensor.

Description: Intermediate or System Bus Address Parity Error. G G G G Failing Function Codes 817 2D4 2E4 2D4 151 2D4 Description and Action (Unless otherwise indicated. Verify that the problem is not related to hardware by running diagnostics. Action: Use Chapter 15. Action: Use Chapter 15. Also. Description: Power Control Network general connection failure. on all resources which have not already been run. “MAP 0240: Memory Problem Resolution” on page 93.Service Request Number 651-751 651-752 651-753 651-754 SRN Src. check the cable connections at that location. The most likely cause is a software or operating system failure. Action: Use Chapter 15. Description: Service Processor detects loss of voltage from the Time-of-Day Clock backup battery. the system administrator should look for other symptoms that would indicate a software or operating system problem. Description: Uncorrectable Memory Error. Description: Service Processor error accessing JTAG/COP controller/hardware. SRNs 101-000 through 69d-701 309 . use Chapter 11. “MAP 0240: Memory Problem Resolution” on page 93. in Problem Determination Mode. “MAP 0210: General Problem Resolution” on page 67. Description: Uncorrectable Memory Error. check all the power distribution cable connections starting at the processor drawer then through each I/O drawer. 651-760 G software hardware Description: Service Processor detected a surveillance time-out. 651-781 G 651-783 G 651-784 G Chapter 31. Action: If a location code is present. “MAP 0240: Memory Problem Resolution” on page 93. Description: Intermediate or System Bus Time-out Error. Action: A surveillance time-out is caused by lack of response from the operating system. Description: Uncorrectable Memory Error. Action: Use Chapter 15. If there is no location code. “MAP 0240: Memory Problem Resolution” on page 93. 651-770 G 2C8 292 306 2C8 292 306 2D2 292 306 227 E17 2C7 214 E18 2C7 214 301 214 302 214 651-771 G 651-772 G 651-773 651-780 G G Description: Intermediate or System Bus Data Parity Error. Contact the software support structure for assistance in needed.) Description: Service Processor error accessing Real-Time Clock/Time-of-Day Clock. Description: Uncorrectable Memory Error. Description: Intermediate or System Bus Data Parity Error.

use the physical location code(s) from the diagnostic problem report screen to determine the FRUs. Action: Verify the following: v nothing is obstructing the fan rotation v the fan power connection is tight v the fan speed sensing cable is tight If the fan still is not turning replace the fan. If the fan is turning. Action: Use Chapter 15. 651-786 G 651-787 G 651-788 G 651-789 G 651-78A G 651-78B G 651-78C G 651-800 651-801 G G 651-802 G Description: Fan failure. replace the fan sensor FRU. Instead of failing function codes. Instead of failing function codes.) Description: Uncorrectable Memory Error. Description: Uncorrectable Memory Error. use the physical location code(s) from the diagnostic problem report screen to determine the FRUs. 651-809 G 310 Diagnostic Information for Multiple Bus Systems . “MAP 0240: Memory Problem Resolution” on page 93. use Chapter 11. Action: Use Chapter 15. Action: Use Chapter 15. Description: Fan is turning slower than expected. Description: Uncorrectable Memory Error. Description: Uncorrectable Memory Error. “MAP 0240: Memory Problem Resolution” on page 93. Description: Fan stop was detected. G Failing Function Codes 303 214 304 214 305 214 30A 214 2CD 214 2CE 214 2CC 214 30B 214 166 2E0 166 2E0 Description and Action (Unless otherwise indicated. Action: Use MAP 210. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Description: Uncorrectable Memory Error. Description: Uncorrectable Memory Error. Action: Use Chapter 15. Description: Power fault warning due to unspecified cause. Action: Use Chapter 15. Description: Uncorrectable Memory Error. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0210: General Problem Resolution” on page 67. Description: Uncorrectable Memory Error. Action: Use Chapter 15. Action: Use Chapter 15.Service Request Number 651-785 SRN Src. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use MAP 210.

651-814 G Chapter 31. 651-811 G 152 2E2 Description: Under voltage condition was detected Action: Shut the system down and do the following before replacing any FRUs. 1. Action: If reasons 1 and 2 can be ruled out than replace the power supply FRU. Loss of AC power 2. When the Resource Repair Action menu displays.) Description: Over voltage condition was detected Action: Shut the system down and do the following before replacing any FRUs. 2. Loss of AC power to the CEC Rack 2. “MAP 0210: General Problem Resolution” on page 67. Open or disconnected SPCN cable between racks 3. Run the following command diag -Avd sysplanar0. When the Resource Repair Action menu displays. 651-812 G 152 Description: System shutdown due to: 1. no action required. Visually inspect the power cables and reseat the connectors. Power button was pushed without proper system shutdown 3. select sysplanar0. Power supply failure. Action: System resumed normal operation. select sysplanar0. Run the following command diag -Avd sysplanar0. 2. 152 Description: CEC Rack shutdown due to one of the following: 1. 1. try the power supply related FRUs one at a time to isolate the problem. Action: If 1 and 2 can be ruled out and the problem can be recreated. regulator or SPCN card failure. Visually inspect the power cables and reseat the connectors. G Failing Function Codes 152 2E2 Description and Action (Unless otherwise indicated. AC module.Service Request Number 651-810 SRN Src. SRNs 101-000 through 69d-701 311 . Bulk power. use Chapter 11. 651-813 G Description: System shutdown due to loss of AC Power to the site.

G Failing Function Codes 287 289 Description and Action (Unless otherwise indicated. If all conditions are met. Description: An over temperature condition was detected Action: Verify the following: v the room ambient temperature is within the system operating environment v there is unrestricted air flow around the system v all system covers are closed If all conditions are met.) Description: I/O Rack shutdown due to one of the following: 1. 651-823 G 312 Diagnostic Information for Multiple Bus Systems . Description: Power fault due to manual activation of power-off request. v All system covers are closed. 651-816 651-817 651-818 651-819 651-820 G G G G G 287 289 Description: Power fault due to internal power supply failure. Description: Power fault due to internal power supply failure. then replace the power supply FRU. use the physical location code(s) from the diagnostic problem report screen to determine the FRUs. 651-821 G 2E1 Description: System shutdown due to an over maximum temperature condition being reached. then replace the temperature sensor FRU. Action: Resume normal operation. 651-822 G 166 2E1 Description: System shutdown due to over temperature condition and fan failure. “MAP 0210: General Problem Resolution” on page 67. v There is unrestricted air flow around the system.Service Request Number 651-815 SRN Src. Action: Verify the following: v The room ambient temperature is within the system operating environment. 152 2E1 Description: Power fault due to internal power supply failure. Use the physical FRU location(s) as the probable cause(s). then replace the temperature sensor FRU. use Chapter 11. Open or disconnected SPCN cable between racks 3. Action: Use the physical location codes to replace the FRUs that are identified on the diagnostics problem report screen. Action: If 1 and 2 can be ruled out. Loss of AC power to the I/O Rack 2. Description: System shutdown due to fan failure. Power supply failure. Action: Use MAP 210. Instead of failing function codes.

“MAP 0210: General Problem Resolution” on page 67.) Description: System shutdown due to power fault warning with an unspecified cause. Description: Sensor detected a voltage outside of the normal range. “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77. Description: Sensor detected a FRU that has failed. Description: Sensor detected a voltage outside of the normal range. 3. Action: Use MAP 1520.Service Request Number 651-824 SRN Src. 651-839 G 651-840 G 166 2E0 152 2E2 Description: Sensor detected a fan failure. Instead of failing function codes. If none of these problems exist. Action: Verify that: 1. use the physical location code(s) from the diagnostic problem report screen to determine the FRUs. Action: Use Chapter 12. If no physical location codes are reported. then proceed with Chapter 12. Action: Use Chapter 12. 651-830 G 166 2E0 152 2E2 2E1 Description: Sensor detected a fan failure. SRNs 101-000 through 69d-701 313 . There is unrestricted air flow around the system. 651-841 G Chapter 31. use Chapter 11. There are no fan failures. Action: Use MAP 210. “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77. Action: Use MAP 210. All system covers are closed. use the physical location code(s) from the diagnostic problem report screen to determine the FRUs. 2. Description: Sensor detected an abnormally high internal temperature. The room ambient temperature is within the system operating environment. “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77. 4. G Failing Function Codes Description and Action (Unless otherwise indicated. Action: Use Chapter 12. Action: Use MAP 1520. Instead of failing function codes. the shutdown was caused by using the power off button or there was a loss of power to the system. 651-831 651-832 G G 651-833 G 152 E19 Description: Sensor detected a power supply failure. “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77.

The room ambient temperature is within the system operating environment. Action: Schedule deferred maintenance.Service Request Number 651-842 SRN Src. “MAP 0210: General Problem Resolution” on page 67. Description: Platform specific error Action: Call your support center. 3. 2. Action: Refer to the entry MAP in this system unit’s system service guide. Action: Verify that: 1. Instead of failing function codes. then replace the appropriate memory module(s). Description: The CEC or SPCN reported an error. for the necessary repair action. There are no fan failures. 651-849 G 651-88x G 651-89x G 651-90x 652-600 G G 652-610 G 210 Description: A non-critical error has been detected: CPU internal error. If none of these problems exist. for the necessary repair action. 4. If the 8 digit error and location codes were NOT reported. use the physical location code(s) from the diagnostic problem report screen to determine the FRUs. then run Advanced Diagnostics in Problem Determination mode and record and report the 8 digit error and location codes for this SRN. “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77. then proceed with Chapter 12. 314 Diagnostic Information for Multiple Bus Systems . There is unrestricted air flow around the system. 651-843 G 152 E19 Description: Sensor detected a power supply failure. with the 8 digit error and location codes.) Description: Sensor detected an abnormally high internal temperature. Description: Sensor detected a FRU that has failed. All system covers are closed. Description: The CEC or SPCN reported an error. Action: Use MAP 210. Action: Refer to the entry MAP in this system unit’s system service guide. Description: A non-critical error has been detected: Uncorrectable memory or unsupported memory. “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77. then run Advanced Diagnostics in Problem Determination mode and record and report the 8 digit error and location codes for this SRN. If the modules are supported. Examine the memory modules and determine if they are supported types. Action: Schedule deferred maintenance. G Failing Function Codes 2E1 Description and Action (Unless otherwise indicated. Use MAP 210. with the 8 digit error and location codes. If the 8 digit error and location codes were NOT reported. use Chapter 11. Action: Use Chapter 12.

Action: Schedule deferred maintenance. Description: A non-critical error has been detected: I/O Expansion Bus Parity Error. Use MAP 210. SRNs 101-000 through 69d-701 315 . 652-612 G D01 652-613 G D01 652-622 G 2C5 652-623 G 2C6 652-630 G 307 652-631 G 307 652-632 G 306 307 308 307 306 307 652-633 G 652-634 G 652-660 G E17 652-661 G E18 652-663 G 301 Chapter 31. Description: A non-critical error has been detected: Correctable error threshold exceeded. G Failing Function Codes 210 Description and Action (Unless otherwise indicated. Description: A non-critical error has been detected: Correctable error threshold exceeded.Service Request Number 652-611 SRN Src. Description: A non-critical error has been detected: External cache ECC single-bit error. Description: A non-critical error has been detected: Internal Device Error. Description: A non-critical error has been detected: Correctable error threshold exceeded. Use MAP 210. Description: A non-critical error has been detected: I/O Expansion Bus Connection Failure. Use MAP 210. Use MAP 210. Action: Schedule deferred maintenance. Action: Schedule deferred maintenance. “MAP 0210: General Problem Resolution” on page 67. Use MAP 210. Action: Schedule deferred maintenance. Action: Schedule deferred maintenance. Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Description: A non-critical error has been detected: Correctable error threshold exceeded. Description: A non-critical error has been detected: I/O Expansion Unit not in an operating state. Action: Schedule deferred maintenance. Action: Schedule deferred maintenance. Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Action: Schedule deferred maintenance. Action: Schedule deferred maintenance. Use MAP 210. Use MAP 210. Action: Schedule deferred maintenance. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. use Chapter 11. Description: A non-critical error has been detected: External cache parity or multi-bit ECC error. Use Chapter 15. Use MAP 210. Action: Schedule deferred maintenance.) Description: A non-critical error has been detected: CPU internal cache or cache controller error. Use Chapter 15. Action: Schedule deferred maintenance. Description: A non-critical error has been detected: I/O Expansion Bus Time-out Error. “MAP 0240: Memory Problem Resolution” on page 93. Action: Schedule deferred maintenance. Use Chapter 15. Description: A non-critical error has been detected: Correctable error threshold exceeded.

Use MAP 210. Description: A non-critical error has been detected: Correctable error threshold exceeded. “MAP 0240: Memory Problem Resolution” on page 93. Action: Schedule deferred maintenance. Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Use Chapter 15. Description: A non-critical error has been detected: Correctable error threshold exceeded. Action: Schedule deferred maintenance. Use Chapter 15. Description: A non-critical error has been detected: Intermediate or System Bus Address Parity Error. Action: Schedule deferred maintenance. Use Chapter 15. Description: A non-critical error has been detected: Correctable error threshold exceeded. Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Description: A non-critical error has been detected: Intermediate or System Bus Data Parity Error. Description: A non-critical error has been detected: Correctable error threshold exceeded. Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Use Chapter 15. Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. 652-665 G 303 652-666 G 304 652-667 G 305 652-668 G 30A 652-669 G 2CD 652-66A G 2CE 652-66B G 2CC 652-66C G 30B 652-731 G 2C8 292 2C8 292 214 2C8 292 652-732 G 652-733 G 316 Diagnostic Information for Multiple Bus Systems . Action: Schedule deferred maintenance. Action: Schedule deferred maintenance. Description: A non-critical error has been detected: Correctable error threshold exceeded. Action: Schedule deferred maintenance. “MAP 0210: General Problem Resolution” on page 67. G Failing Function Codes 302 Description and Action (Unless otherwise indicated. Description: A non-critical error has been detected. Action: Schedule deferred maintenance. Description: A non-critical error has been detected: Intermediate or System Bus Address Parity Error. Action: Schedule deferred maintenance.Service Request Number 652-664 SRN Src. “MAP 0240: Memory Problem Resolution” on page 93. Action: Schedule deferred maintenance. Description: A non-critical error has been detected: Correctable error threshold exceeded. Use Chapter 15. Action: Schedule deferred maintenance. Correctable error threshold exceeded. Action: Schedule deferred maintenance. Description: A non-critical error has been detected: Correctable error threshold exceeded. Use MAP 210. “MAP 0240: Memory Problem Resolution” on page 93. use Chapter 11. Use MAP 210.) Description: A non-critical error has been detected: Correctable error threshold exceeded. “MAP 0240: Memory Problem Resolution” on page 93. Action: Schedule deferred maintenance. “MAP 0240: Memory Problem Resolution” on page 93.

Action: Schedule maintenance. Use the physical location codes to replace the FRUs that are identified on the diagnostics problem report screen. Use MAP 210. loss of redundant fan. Use MAP 210. loss of redundant supply. Action: Schedule deferred maintenance. Instead of failing function codes. Action: Schedule deferred maintenance. 652-735 G 652-736 G 652-770 G 652-771 G 652-772 G 652-773 G 652-810 G 152 652-819 652-820 G G 166 Description: Non-critical cooling problem. Use MAP 210. “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77. Description: Sensor detected a redundant FRU failure. Use the physical FRU location(s) as the probable cause(s).use the physical location code(s) from the diagnostic problem report screen to determine the FRUs. Action: Schedule deferred maintenance. Use MAP 210. Description: A non-critical error has been detected: Intermediate or System Bus Data Parity Error.Service Request Number 652-734 SRN Src. Use the physical FRU location(s) as the probable cause(s). Description: A non-critical error has been detected: Intermediate System Bus Address Parity Error. Description: Sensor detected a redundant power supply failure. Action: Schedule deferred maintenance. G Failing Function Codes 214 2C8 292 2D2 292 2D2 292 214 2C8 292 306 2C8 292 306 2D2 292 306 227 Description and Action (Unless otherwise indicated. 652-830 G 166 2E0 152 E19 652-833 G 652-839 G Chapter 31. Description: A non-critical error has been detected: Intermediate or System Bus Time-out Error. Use the physical location codes to replace the FRUs that are identified on the diagnostics problem report screen. Action: Use MAP 210.) Description: A non-critical error has been detected: Intermediate or System Bus Data Parity Error. Description: Power fault due to internal redundant power supply failure. “MAP 0220: Hot-Swap FRU Problem Resolution” on page 77. Action: Use Chapter 12. Description: A non-critical error has been detected: Intermediate or System Bus Time-out Error. “MAP 0210: General Problem Resolution” on page 67. SRNs 101-000 through 69d-701 317 . Use MAP 210. Action: Schedule deferred maintenance. Description: Sensor detected a redundant fan failure. Action: Schedule maintenance. Description: Non-critical power problem. Description: A non-critical error has been detected: Intermediate or System Bus Data Parity Error. Action: Schedule deferred maintenance. Action: Use Chapter 12. use Chapter 11. Use MAP 210. Description: A non-critical error has been detected: Intermediate or System Bus Time-out Error. Action: Schedule deferred maintenance. Use MAP 210.

for the necessary repair action. then run Advanced Diagnostics in Problem Determination mode and record and report the 8 digit error and location codes for this SRN. diagnostic software. If the 8 digit error and location codes were NOT reported. and application software to be sure they are all compatible. call your support person. Description: An unrecoverable hardware error. Action: Schedule deferred maintenance. Description: The CEC or SPCN reported a non-critical error. Refer to the entry MAP in this system unit’s system service guide. Description: The diagnostic test failed. If you do not find a problem. Description: A SCSI busy or command error.) Description: The CEC or SPCN reported a non-critical error. adapter. Description: The motor failed to restart.Service Request Number 652-88x SRN Src. 652-89x G 653-102 653-104 653-105 653-106 653-108 653-110 653-112 653-114 653-116 D D D D D D D D D 653 653 653 653 653 653 653 653 Description: An unrecoverable media error occurred. “MAP 0210: General Problem Resolution” on page 67. Description: A SCSI command time-out occurred. with the 8 digit error and location codes. 653-117 653-118 653-120 653-122 653-124 653-126 653-128 D D D D D D G 653 653 B88 653 653 653 653 B88 653 Description: A write-protect error occurred. Description: A protocol error. Description: A SCSI check condition error occurred. Description: The bus test failed. 318 Diagnostic Information for Multiple Bus Systems . use Chapter 11. then run Advanced Diagnostics in Problem Determination mode and record and report the 8 digit error and location codes for this SRN. If the 8 digit error and location codes were NOT reported. Description: The error log analysis indicates a hardware failure. Description: A SCSI reservation conflict error. Refer to the entry MAP in this system unit’s system service guide. with the 8 digit error and location codes. Description: The media format is corrupted. Action: Schedule deferred maintenance. Description: A software error was caused by a hardware failure. G Failing Function Codes Description and Action (Unless otherwise indicated. for the necessary repair action. Description: The drive did not become ready. Description: The electronics card test failed. Action: Check the levels of the device.

657-005 D Description: Adapter failure. Description: A disk drive hardware error occurred. Description: Software error. Description: The adapter failed to configure. SRNs 101-000 through 69d-701 319 . 653-130 653-132 653-134 653-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: Enhanced error handling failure on the adapter. Description: Adapter failure. Description: Enhanced error handling failure on a PCI-PCI Bridge. “MAP 0210: General Problem Resolution” on page 67. 655-003 657-001 657-002 657-003 657-004 D D D D D Description: Software error. Description: Adapter problem. 653-136 653-137 D D Description: The certify operation failed. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: Display failure. G Failing Function Codes 190 653 B88 software 653 653 B88 software 653 B88 software 653 653 B88 190 655 221 Monitor/ Cable 655 Monitor/ Cable software 655 software 657 657 software 657 227 657 Monitor/ Cable 657 227 Monitor/ Cable 221 293 662 221 Description and Action (Unless otherwise indicated. use Chapter 11. Description: Adapter failure.) Description: Error log analysis indicates a SCSI bus problem. Chapter 31. 655-001 D 655-002 D Description: Display problem. 662-101 662-102 662-103 D D D Description: Enhanced error handling failure on the bus.Service Request Number 653-129 SRN Src. Description: The device failed to configure.

“MAP 0050: SCSI Bus Problems” on page 51. Action: Go to Chapter 8. “MAP 0050: SCSI Bus Problems” on page 51. D D D D D D D D D D D D Failing Function Codes 662 662 662 662 662 662 662 662 662 662 221 662 662 Description and Action (Unless otherwise indicated. Description: Miscompare during the write/read of the configuration register. Description: Arbitration test failed. Action: Go to Chapter 8. Description: FIFO full bit set. Description: FIFO empty bit clear. Description: Error log analysis indicates a PCI SCSI adapter failure. “MAP 0050: SCSI Bus Problems” on page 51. 662 221 662 Description: The parent device open failed. Description: SCSI FIFO data miscompare. Description: SCSI FIFO underflow. Action: Go to Chapter 8. Description: SCSI FIFO flags error. 320 Diagnostic Information for Multiple Bus Systems . Action: Go to Chapter 8. “MAP 0050: SCSI Bus Problems” on page 51. Description: SCSI wrap or PTC failure. “MAP 0050: SCSI Bus Problems” on page 51. Action: Go to Chapter 8. Description: FIFO full bit clear. Description: Miscompare during the write/read of the memory I/O register. Description: SCSI parity error. Description: Error during the write/read of the memory register. Action: Go to Chapter 8. Description: No terminal power. “MAP 0050: SCSI Bus Problems” on page 51. “MAP 0210: General Problem Resolution” on page 67. Description: SCSI configuration register read or write error. Action: Go to Chapter 8.) Description: FIFO empty bit set. 662-224 662-225 662-226 662-227 662-230 662-231 662-232 662-240 662-242 662-301 662-701 D D D D D D D D D D G 662 221 662 662 221 Description: SCSI adapter test failure. Description: Adapter POST failed. “MAP 0050: SCSI Bus Problems” on page 51. use Chapter 11. Description: SCSI bus data miscompare.Service Request Number 662-212 662-213 662-214 662-215 662-216 662-217 662-218 662-219 662-220 662-221 662-222 662-223 SRN Src. Description: Function could not complete. Description: FIFO data miscompare. Description: SCSI bus problem.

If an SRN is reported. Action: Run the diagnostics on the adapter in System Verification mode. If an SRN is not reported. G Failing Function Codes Description and Action (Unless otherwise indicated. use the SRN to resolve the problem. Description: Error log analysis indicates that multiple attempts to reset the SCSI bus have timed out. use Chapter 11. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. If an SRN is not reported. Description: Error log analysis indicates that multiple SCSI bus errors have occurred. Action: Run the diagnostics on the adapter in System Verification mode. 662-802 G 662-803 G 663-101 D 663 C94 C95 663 C94 C95 663 C94 C95 C94 663 C95 663 C94 C95 663 C94 C95 C95 66 C97 C94 663 C95 Description: IBM ARTIC960RxD or RxF PCI Adapter Central Processing Unit test failure. Description: IBM ARTIC960RxD or RxF PCI Adapter Timer test failure. Description: IBM ARTIC960RxD or RxF PCI Adapter Dynamic Random Access Memory test failure. Description: Interface board wrap test failure. 663-102 D 663-103 D 663-104 D 663-105 D 663-106 D 663-107 D 663-110 D Description: IBM ARTIC960RxD or RxF PCI Adapter Download Diagnostics test failure. use the SRN to resolve the problem. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem.Service Request Number 662-801 SRN Src. Chapter 31. Description: IBM ARTIC960RxD or RxF PCI Adapter Memory Protection test failure. Description: IBM ARTIC960RxD or RxF PCI Adapter Bus Interface test failure. If an SRN is reported. SRNs 101-000 through 69d-701 321 . If an SRN is reported. use the SRN to resolve the problem. “MAP 0210: General Problem Resolution” on page 67.) Description: Error log analysis indicates a terminator problem. Description: IBM ARTIC960RxD PCI Adapter Debug Port test failure. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. If an SRN is not reported. Action: Run the diagnostics on the adapter in System Verification mode.

Service Request Number 663-123 SRN Src. Description: The CD-ROM drive indicates an error. Description: IBM ARTIC960RxD or RxF PCI Adapter initialization failure. 663-154 D 663-155 D 663-156 D 663-157 D 664-111 664-112 664-113 664-121 664-122 664-123 664-125 664-126 664-127 664-128 664-129 D D D D D D D D D D D Description: Unable to reserve device. Description: Unable to open the device driver. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error. 663-151 D Description: Device driver indicates a hardware failure. Description: The CD-ROM drive indicates an error. Description: Error log analysis indicates a IBM ARTIC960RxD or RxF PCI Adapter failure. D Failing Function Codes C95 663 C94 663 software 227 663 software 227 663 663 227 C94 software C94 663 C95 663 C94 C95 C95 663 C94 C98 C97 C95 664 B88 664 B88 664 B88 664 664 664 664 B88 664 664 664 664 Description and Action (Unless otherwise indicated. “MAP 0210: General Problem Resolution” on page 67. 663-150 D Description: Device configuration failure. 322 Diagnostic Information for Multiple Bus Systems . Description: Unable to do configuration. use Chapter 11. Action: Use the errpt command to check error log. 663-152 663-153 D D Description: Failure and error in determining which type of IBM ARTIC960RxD PCI Adapter. Description: IBM ARTIC960RxD or RxF PCI Adapter initialization failure.) Description: Interface board non-wrap test failure. Description: The CD-ROM drive indicates an error. Description: IBM ARTIC960RxD or RxF PCI Adapter initialization failure. Description: Cable wrap test failure. Description: The CD-ROM drive indicates an error.

Description: The POST indicates an adapter failure. Action: Go to Chapter 18. Action: Go to Chapter 18. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. D D D D D D D D D D D D G G D Failing Function Codes Test Disc 664 664 B88 664 664 664 664 664 664 664 B88 664 664 664 664 664 B88 667 227 667 Description and Action (Unless otherwise indicated. Description: The PCI wrap test failed. Action: Go to Chapter 18. Action: Go to Chapter 18. Description: The CD-ROM drive indicates an error. Description: No tone during audio test. Description: Enhanced error handling failure on bus. Description: The CD-ROM drive indicates an error. Description: Errors found during ELA. Description: The NVRAM test indicates an adapter failure. Description: The POST indicates the last disk drive reconnected caused a channel failure. Action: Go to Chapter 18. use Chapter 11. SRNs 101-000 through 69d-701 323 . Description: A command timeout was detected. Description: The POST indicates an adapter channel failure.) Description: A media error was detected. “MAP 0210: General Problem Resolution” on page 67. 667-102 D 667-103 D 667 667-104 667-105 667-106 D D D 190 B3A 722 667-108 667-109 D D 221 667 Chapter 31. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: A command reservation conflict was detected. Description: The LED test failed. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: Unable to do configuration. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103.Service Request Number 664-150 664-151 664-152 664-162 664-171 664-172 664-173 664-175 664-198 664-199 664-211 664-281 664-301 664-302 667-101 SRN Src. Description: The POST indicates a defective backplane or external enclosure. Description: The POST indicates a defective cable. Description: Undefined error detected. Description: Unable to open device driver. Description: Unable to reserve device. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: Undefined error detected. Description: Errors found during ELA.

Action: Go to Chapter 18.) Description: The disk reported a Predictive Failure Analysis error (PFA). Action: Go to Chapter 18. Action: Go to Chapter 18. use Chapter 11. Action: Go to Chapter 18. Action: Go to Chapter 18. 667-111 D 722 667-112 G 722 667-113 G 722 667-114 G E29 667-115 G E30 667-116 D 667 667-117 D E29 667-118 D E29 667-119 D E29 667-120 D E29 667-121 D E30 667-122 D E30 324 Diagnostic Information for Multiple Bus Systems . Description: Adapter test indicates that the cache battery is low on power. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: The disk drive has been failed by the adapter. Description: ELA indicates that the cache battery is either low on power or has failed. Action: Go to Chapter 18. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: Adapter test indicates cache battery failure. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: NVRAM test indicates that cache size is invalid. Action: Go to Chapter 18. Description: ELA indicates a cache failure. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: ELA indicates that the disk reported a hard equipment error. Description: ELA indicates that the disk reported a hard data error. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: NVRAM test indicates that write cache is missing. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: POST indicates cache failure. Action: Go to Chapter 18. Action: Go to Chapter 18. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. D Failing Function Codes 722 Description and Action (Unless otherwise indicated. Action: Go to Chapter 18. Action: Go to Chapter 18. “MAP 0210: General Problem Resolution” on page 67. Action: Go to Chapter 18. Description: NVRAM test indicates cache failure. Description: Failed to disable data scrub.Service Request Number 667-110 SRN Src. Action: Go to Chapter 18. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103.

Description: Enhanced error handling failure on Eads chip.Service Request Number 667-123 SRN Src. Description: Enhanced error handling failure on adapter. Description: Enhanced error handling failure on adapter. Description: Error Log Analysis indicates that this device has failed to initialize due to firmware download error. use SRN 66C-201 instead. SRNs 101-000 through 69d-701 325 . Description: I/O register test failure. look at the label on the adapter. D Failing Function Codes 667 Description and Action (Unless otherwise indicated. Description: Adapter memory test failure. “MAP 0210: General Problem Resolution” on page 67. Description: POST indicates a channel failure. Description: Enhanced error handling failure on Eads chip. Description: Enhanced error handling failure on bus. Description: Configuration register test failure. Description: Enhanced error handling failure on adapter. use Chapter 11. Action: Go to Chapter 18. Description: External wrap test failure (1000 Mbps). Description: Adapter initialization test failure. Action: Before going to MAP 210. Description: Error Log Analysis indicates that this device has failed to initialize due to a self-test failure. AIX operating system cannot configure this non-IBM version of the adapter. Description: Error Log Analysis indicates that this device failed to initialize due to a problem with the EEPROM on the adapter.) Description: ELA indicates an adapter failure. Description: Error Log Analysis indicates that this device failed to initialize because it is not the IBM version of this adapter. 667-124 667-125 667-400 D D F 221 667 221 667 190 B3A 722 667 221 221 221 669 669 667-701 669-101 669-102 669-103 669-201 G D D D D 221 669-202 669-203 669-204 669-205 669-206 669-701 D D D D D G 669 669 669 669 669 669 669-702 G 669 669-703 669-704 66C-101 66C-102 66C-103 G G D D D 669 669 221 221 66C Chapter 31. Description: Internal loopback test failure. Description: Enhanced error handling failure on PCI-PCI Bridge. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Action: Go to Chapter 18. Description: Error Log Analysis indicates an EEH error. Description: Enhanced error handling failure on bus. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. If the label is A-A.

Description: The POST indicates a defective backplane or external enclosure. Description: Adapter memory test failure. “MAP 0210: General Problem Resolution” on page 67. Description: Error Log Analysis indicates that this device failed to initialize due to a problem with the EEPROM on the adapter. Action: Go to Chapter 18. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Action: Go to Chapter 18. Description: The POST indicates an adapter failure. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Action: Go to Chapter 18. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: The POST indicates a defective cable. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: Internal loopback test failure. Description: The POST indicates an adapter channel failure. Description: I/O register test failure.Service Request Number 66C-201 66C-202 66C-203 66C-204 66C-205 66C-206 66C-207 66C-208 66C-702 SRN Src. Description: Error Log Analysis indicates that this device has failed to initialize due to firmware download error. 66C-703 66C-704 66D-101 G G D 66C 66C 66D 227 66D E2A 66D 66D-102 D 66D-103 D 66D-104 66D-105 66D-106 D D D 190 B3A 722 66D-108 66D-109 D D 221 66D 66D-110 D 722 326 Diagnostic Information for Multiple Bus Systems . Action: Go to Chapter 18. Description: External wrap test failure (100 Mbps). use Chapter 11. Description: External wrap test failure (10 Mbps). Description: External wrap test failure (1000 Mbps). Description: Enhanced error handling failure on bus. Description: Adapter initialization test failure. Action: Go to Chapter 18. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: The POST indicates the last disk drive reconnected caused a channel failure. Description: The test indicates an adapter failure. Description: The PCI wrap test failed. Description: The disk reported a Predictive Failure Analysis error (PFA). Action: Go to Chapter 18.) Description: Configuration register test failure. D D D D D D D D G Failing Function Codes 66C 221 66C 66C 66C 66C 66C 66C 66C 66C Description and Action (Unless otherwise indicated. Description: Error Log Analysis indicates that this device has failed to initialize due to a self-test failure.

“MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0210: General Problem Resolution” on page 67. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: Failed to disable data scrub. Action: Go to Chapter 18. Description: POST indicates cache failure.) Description: The disk drive has been failed by the adapter. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: Adapter test indicates a cache failure. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. 66D-112 G 722 66D-113 G 722 66D-114 G E2A 66D-115 G E3A 66D-116 D 66D 66D-117 D E2A 66D-118 D E2A 66D-119 D E2A 66D-120 D E2A 66D-121 D E3A 66D-122 D E3A 66D-123 D 66D 66D-124 D 221 Chapter 31. Description: Adapter test indicates that the cache battery is low on power. Action: Go to Chapter 18. Action: Go to Chapter 18.Service Request Number 66D-111 SRN Src. use Chapter 11. Description: ELA indicates that the cache battery is either low on power or has failed. D Failing Function Codes 722 Description and Action (Unless otherwise indicated. Action: Go to Chapter 18. Description: ELA indicates an adapter failure. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Action: Go to Chapter 18. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: Adapter test indicates that write cache is missing. Action: Go to Chapter 18. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Action: Go to Chapter 18. Description: Adapter test indicates that cache size is invalid. Description: Enhanced error handling failure on PCI-PCI Bridge. Description: ELA indicates a cache failure. Description: Adapter test indicates cache battery failure. SRNs 101-000 through 69d-701 327 . “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Action: Go to Chapter 18. Action: Go to Chapter 18. Action: Go to Chapter 18. Action: Go to Chapter 18. Action: Go to Chapter 18. Description: ELA indicates that the disk reported a hard data error. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Action: Go to Chapter 18. Description: ELA indicates that the disk reported a hard equipment error.

Description: Unable to configure the device. Description: Undetermined hardware error has occurred. Unable to get Additional Vital Product Data. Otherwise. Description: SCSI command Release has failed. Run the test with another Test Media. Description: SCSI command Mode Sense has failed. “MAP 0210: General Problem Resolution” on page 67. Clean the drive. Description: SCSI command Test Unit Ready has failed. Description: DVD-RAM drive is unable to eject the tray. Description: DVD-RAM drive is unable to load the tray. Description: Error Log Analysis indicates an EEH error. Otherwise . Action: Verify that no external object prevents the drive from ejecting the tray. Otherwise. Description: SCSI command Mode Select has failed. Description: SCSI command Reserve has failed. D F Failing Function Codes 66D 221 66D 190 B3A 722 66D 221 66E 66E 66E 66E 66E 66E 66E 66E 66E 66E 66E 66E 66E B88 media 66E Description and Action (Unless otherwise indicated. Description: DVD-RAM drive is unable to detect the Test Media. use MAP-0210. Verify that the Test Media is inserted properly in the tray. use Chapter 11. Description: SCSI command Send Diagnostic has failed. Description: SCSI command Prevent Media Removal has failed. Description: SCSI command Allow Media Removal has failed. 66D-701 66E-100 66E-102 66E-103 66E-104 66E-105 66E-106 66E-107 66E-108 66E-109 66E-10A 66E-10B 66E-10F 66E-200 66E-201 G D D D D D D D D D D D D D D 66E-202 D media 66E 66E-203 D media 66E 66E-204 D 66E B88 328 Diagnostic Information for Multiple Bus Systems .) Description: Enhanced error handling failure on adapter. Description: Unable to configure the parent device.Service Request Number 66D-125 66D-400 SRN Src. Action: Go to Chapter 18. Description: SCSI command Inquiry has failed. Description: A SCSI reservation conflict has occurred. use MAP-0210. use MAP-0210. Action: Verify that no external object prevents the drive from loading the tray. Description: The POST test indicates a channel failure. Verify that no media is stuck inside the drive. Action: Verify that the Test Media is inserted properly. Description: SCSI command Start Stop Unit has failed. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103.

D Failing Function Codes media 66E Description and Action (Unless otherwise indicated. Description: The Random Write/Read/Compare Test has detected a hardware error while testing the DVD-RAM Test Media. Description: DVD-RAM drive is unable to determine the media type. 66E-700 66E-701 670-102 to 670-114 G G D Description: ELA indicates an irrecoverable hardware error. Description: 18. Use MAP-0210. Use MAP-0210.2GB Differential SCSI disk drive problem. Description: DVD-RAM drive has faulty write-protect-detection mechanism. Action: Run Diagnostic on this drive with another DVD-RAM Test Media. SRNs 101-000 through 69d-701 329 . Description: SCSI command timeout has occurred. Action: Verify that the DVD-RAM Test Media is inserted properly. Clean the drive. use Chapter 11. Run Diagnostic on this drive with another Test Media. Action: Run Diagnostic on this drive with another CD-ROM Test Media. Chapter 31. Use MAP-0210. Action: Run Diagnostic on this drive with another CD-ROM Test Media. Use MAP-0210. Description: ELA indicates an undetermined hardware error. Description: DVD-RAM drive has detected a media error. Description: The Random Read Test has detected a medium error while testing the CD-ROM Test Media. 66E-206 D 66E media 66E-207 D media 66E 66E-208 D 66E media 66E-209 D media 66E 66E-20A D media 66E 66E-20B D media 66E 66E-300 D 66E B88 190 B88 190 66E 66E 66E 670 66E-301 D Description: Description: Unit Attention has occurred.Use MAP-0210. Run Diagnostic on this drive with another DVD-RAM Test Media. Action: Verify that the proper Test Media is inserted. Action: Verify that the DVD-RAM Test Media is not write-protected. Run Diagnostic on this drive with another DVD-RAM Test Media. Action: Run Diagnostic on this drive with another DVD-RAM Test Media.) Description: The Random Write/Read/Compare Test has detected a medium error while testing the DVD-RAM Test Media. Use MAP-0210. Use MAP-0210. Description: The Random Read Test has detected a hardware error while testing the CD-ROM Test Media.Service Request Number 66E-205 SRN Src. “MAP 0210: General Problem Resolution” on page 67.

call your support person. Action: Check the levels of the device. “MAP 0210: General Problem Resolution” on page 67. Description: 18. D Failing Function Codes Description and Action (Unless otherwise indicated. Description: Unit attention condition has occurred on the Send Diagnostic command. use Chapter 11.Service Request Number 670-116 SRN Src. Description: A SCSI error. Description: A disk drive hardware error occurred. D G G 670 B88 670 190 670 B88 software 670 670 B88 software 670 B88 software 670 670 B88 190 671 Description: A software error was caused by a hardware failure. adapter. 670-130 670-132 670-134 670-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. If you do not find a problem. 670-136 670-137 D D Description: The certify operation failed. 671-102 to 671-114 671-116 D D Description: A protocol error. and application software to be sure they are all compatible. Description: The device failed to configure. If you do not find a problem. 670-117 670-118 670-120 to 670-124 670-126 670-128 670-129 D D D 670 670 B88 670 Description: A write-protect error occurred. Description: The adapter failed to configure.) Description: A protocol error. 671 671 B88 671 Description: A write-protect error occurred. diagnostic software. Description: The error log analysis indicates a hardware failure. Action: Check the levels of the device. adapter. call your support person. Description: A SCSI command time-out.2GB Differential SCSI disk drive problem. Description: Error log analysis indicates a SCSI bus problem. and application software to be sure they are all compatible. Description: A SCSI command time-out. diagnostic software. 671-117 671-118 671-120 to 671-124 D D D 330 Diagnostic Information for Multiple Bus Systems . Description: A SCSI error.

and application software to be sure they are all compatible.2 GB Differential SCSI disk drive problem. Description: Error log analysis indicates a SCSI bus problem. D G G Failing Function Codes 671 B88 671 190 671 B88 software 671 671 B88 software 671 B88 software 671 671 B88 190 672 Description and Action (Unless otherwise indicated. Description: The adapter failed to configure. Chapter 31. 672-102 to 672-114 672-116 D D 672-117 672-118 672-120 to 672-124 672-126 672-128 672-129 D D D 672 672 B88 672 Description: A write-protect error occurred. Action: Check the levels of the device. “MAP 0210: General Problem Resolution” on page 67. 672-130 G Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: A SCSI command time-out. use Chapter 11. D G G 672B88 672 190 672 B88 software 672 Description: A software error was caused by a hardware failure. Description: The error log analysis indicates a hardware failure. Description: A disk drive hardware error occurred.Service Request Number 671-126 671-128 671-129 SRN Src. Description: The error log analysis indicates a hardware failure. Description: The device failed to configure. Description: A SCSI error. Description: 18. Description: Unit attention condition has occurred on the Send Diagnostic command. If you do not find a problem. 671-130 671-132 671-134 671-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: Error log analysis indicates a SCSI bus problem. Description: A protocol error. call your support person. adapter. SRNs 101-000 through 69d-701 331 . 671-136 671-137 D D Description: The certify operation failed.) Description: A software error was caused by a hardware failure. diagnostic software.

If you do not find a problem. Description: A SCSI command time-out. Description: Unit attention condition has occurred on the Send Diagnostic command. diagnostic software. adapter. 673-102 to 673-114 673-116 D D Description: A protocol error.Service Request Number 672-132 672-134 672-135 SRN Src. Description: Unit attention condition has occurred on the Send Diagnostic command. “MAP 0210: General Problem Resolution” on page 67. Action: Check the levels of the device. 673-130 673-132 673-134 673-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: The adapter failed to configure. 332 Diagnostic Information for Multiple Bus Systems .2GB Differential SCSI disk drive problem. and application software to be sure they are all compatible. use Chapter 11. 672-136 672-137 D D Description: The certify operation failed. Description: A SCSI error. Description: A disk drive hardware error occurred.) Description: A disk drive hardware error occurred. D D D Failing Function Codes 672 B88 software 672 B88 software 672 672 B88 190 673 Description and Action (Unless otherwise indicated. Description: Error log analysis indicates a SCSI bus problem. 673-117 673-118 673-120 to 673-124 673-126 673-128 673-129 D D D D G G 673B88 673 190 673 B88 software 673 673 B88 software 673 B88 software 673 673 B88 190 Description: A software error was caused by a hardware failure. Description: 18. call your support person. 673 673 B88 673 Description: A write-protect error occurred. 673-136 673-137 D D Description: The certify operation failed. Description: The adapter failed to configure. Description: The error log analysis indicates a hardware failure. Description: The device failed to configure. Description: The device failed to configure.

Description: IBM ARTIC960Rx PCI Adapter Bus Interface test failure. 674-152 674-153 D D Description: Failure and error in determining which type of IBM ARTIC960Rx PCI Adapter. Description: Error log analysis indicates a IBM ARTIC960Rx PCI Adapter failure. Description: IBM ARTIC960Rx PCI Adapter Debug Port test failure. Description: IBM ARTIC960Rx PCI Adapter Dynamic Random Access Memory (DRAM) test failure. Description: Interface board non-wrap test failure. 674-123 674-150 D D 674-151 D Description: Device driver indicates a hardware failure. Description: IBM ARTIC960Rx PCI Adapter Memory Protection test failure. Description: Device configuration failure. Description: Interface board wrap test failure.Service Request Number 674-101 SRN Src. Description: IBM ARTIC960Rx PCI Adapter Timer test failure. 674-102 D 674-103 D 674-104 D 674-105 D 674-106 D 674-107 D 674-110 D Description: IBM ARTIC960Rx PCI Adapter Download Diagnostics test failure. Description: IBM ARTIC960Rx PCI Adapter initialization failure. “MAP 0210: General Problem Resolution” on page 67. 674-154 D 674-155 D Chapter 31. Action: Use the errpt command to check error log. use Chapter 11. SRNs 101-000 through 69d-701 333 . Description: IBM ARTIC960Rx PCI Adapter initialization failure. D Failing Function Codes 674 C94 C95 674 C94 C95 674 C94 C95 C94 674 C95 674 C94 C95 674 C94 C95 C95 674 C97 C94 674 C95 C95 C97 674 software 227 674 software 227 674 674 227 C94 software C94 674 C95 674 C94 C95 Description and Action (Unless otherwise indicated.) Description: IBM ARTIC960Rx PCI Adapter Central Processing Unit (CPU) test failure.

“MAP 0210: General Problem Resolution” on page 67. 675-123 D 675-150 D Description: Device configuration failure. 674-157 675-101 D D 675-102 D 675-103 D Description: IBM ARTIC960Hx Adapter Bus Interface test failure. use Chapter 11. Description: IBM ARTIC960Hx Adapter Debug Port test failure. Description: IBM ARTIC960Hx Adapter Memory Protection test failure.) Description: IBM ARTIC960Rx PCI Adapter initialization failure. Description: IBM ARTIC960Hx Adapter Dynamic Random Access Memory (DRAM) test failure. 334 Diagnostic Information for Multiple Bus Systems . 675-104 D 675-105 D 675-106 D 675-107 D 675-110 D Description: IBM ARTIC960Hx Adapter Download Diagnostics test failure. 675-152 675-153 D D Description: Failure and error in determining which type of IBM ARTIC960Hx Adapter. 675-151 D Description: Device driver indicates a hardware failure. Description: IBM ARTIC960Hx Adapter Timer test failure. Description: Interface board wrap test failure. Action: Use the errpt command to check error log. D Failing Function Codes C95 674 C94 C97 C95 675 C94 C95 675 C94 C95 675 C94 C95 C94 675 C95 675 C94 C95 675 C94 C95 C95 675 C97 C94 675 C95 C95 675 C94 675 software 227 675 software 227 675 675 227 C94 software Description and Action (Unless otherwise indicated. Description: Cable wrap test failure. Description: IBM ARTIC960Hx Adapter Central Processing Unit (CPU) test failure. Description: Error log analysis indicates a IBM ARTIC960Hx Adapter failure.Service Request Number 674-156 SRN Src. Description: Interface board non-wrap test failure.

Description: Cable wrap test failure. SRNs 101-000 through 69d-701 335 . Description: The Register test failed. Description: IBM ARTIC960Hx Adapter initialization failure. Description: Error log analysis indicates that an adapter error has occured.) Description: IBM ARTIC960Hx Adapter initialization failure. Description: The Interrupt test failed. D Failing Function Codes C94 675 C95 675 C94 C95 C95 675 C94 C98 C97 C95 677 677 677 677 677 677 677 221 221 677 677 221 677 221 677 221 677 221 677 221 677 221 677 677 Description and Action (Unless otherwise indicated. Description: Error log analysis indicates that an unknown adapter error has occurred. Description: The Reset test failed. Description: Enhanced Error Handling Failure on EADs chip. Description: The Gigabaud Link Module (GLM) Wrap Test Failure. Description: Error log analysis indicates that an error has occurred with the adapter. Description: I/O error on a read/write operation. “MAP 0210: General Problem Resolution” on page 67. Description: The DMA test failed. Chapter 31. Description: Enhanced Error Handling Failure on bus.Service Request Number 675-154 SRN Src. Description: The Configuration Register test failed. Description: The SRAM test failed. Description: IBM ARTIC960Hx Adapter initialization failure. Description: The Internal Wrap test failed. Description: The PCI Wrap test failed. Description: The External Wrap test failed. Description: Enhanced Error Handling Failure on adapter. use Chapter 11. 675-155 D 675-156 D 675-157 D 677-101 677-102 677-103 677-104 677-105 677-106 677-107 677-108 677-109 677-110 677-201 677-202 677-203 677-204 677-205 677-701 677-703 677-704 D D D D D D D D D D D D D D D G G G Description: The Fibre Channel Adapter configuration failed.

Description: The Unload command failed. Description: Timeout while attempting to communicate with the SCSI device. Description: The Send Diagnostic command failed. Description: An error is detected in request sense data.Service Request Number 678-098 678-099 678-101 678-102 678-103 678-104 678-105 678-107 678-110 678-111 678-112 678-113 678-114 678-120 678-130 678-134 678-135 678-140 678-150 678-160 678-161 678-163 678-164 SRN Src. J J D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 678 678 B88 678 678 678 678 678 678 678 678 678 678 678 678 678 media B88 software 678 media 678 678 media 678 media 678 B88 678 B88 678 B88 Description and Action (Unless otherwise indicated. Description: The Test Unit Ready command failed. Description: The Mode Select command failed. Description: The SCSI device indicates a reservation conflict. Description: The write-protect sensor test failed. Description: Invalid condition from drive after a request sense. 336 Diagnostic Information for Multiple Bus Systems . Description: The Inquiry command failed. Description: Tape drive not found. “MAP 0210: General Problem Resolution” on page 67. Description: Invalid condition from the drive after a request sense. Description: The Reserve command failed. Description: Timeout while attempting to communicate with the SCSI device. Description: Invalid condition from the drive after a reserve. Description: The Load command failed.) Description: Tape drive indicates an error. Description: Invalid condition from the drive after a reserve. use Chapter 11. Description: The SCSI device indicates busy. Description: Sense data from the SCSI drive has unexpected data. Description: The adapter failed to configure. Description: The SCSI device indicates a check condition. Description: Timeout while attempting to communicate with SCSI device.

Description: SCSI adapter configuration failed. Description: The adapter failed to configure. Description: The device open failed. Description: The Openx command failed. Description: The Unload command failed. “MAP 0210: General Problem Resolution” on page 67. Description: The device configuration failed. Description: The Request Sense command failed. D Failing Function Codes 678 B88 276 678 B88 software 678 B88 B88 software 678 media 678 B88 media 678 media 678 media 678 678 media 678 B88 678 B88 678 B88 678 678 678 678 678 678 software B88 678 software 678 media Description and Action (Unless otherwise indicated. Description: The Mode Select command failed. Description: The Read. Description: The Send Diagnostic command failed. 678-166 D Description: Unable to configure the device. 678-167 678-168 678-169 678-170 D D D D Description: An unexpected SCSI error occurred. Chapter 31. Description: The Test Unit Ready command failed. Description: The device open failed. 678-180 678-185 678-190 678-200 678-201 678-210 678-211 678-220 678-230 678-240 678-260 678-261 678-300 678-310 D D D D G D D D D D D D D D Description: The Load command failed.) Description: Write. use Chapter 11. 678-320 G Description: Error log analysis indicates a failure. SRNs 101-000 through 69d-701 337 . Description: Error diagnosed from error log analysis. Write and Compare test failed. Description: The device configuration failed.Service Request Number 678-165 SRN Src. Description: The Release command failed. Read and Compare Test failed. Description: The device configuration failed.

338 Diagnostic Information for Multiple Bus Systems . Description: The bus test failed. Description: A SCSI check condition error occurred. D D Description: A device timeout error occurred. Description: The error log analysis indicates a hardware failure. D D D D D D D D D Description: An unrecoverable media error occurred. Description: A software error was caused by a hardware failure. Description: The electronics card test failed. call your support person.Service Request Number 678-411 to 678-423 678-511 to 678-523 678-611 to 678-623 678-711 to 678-723 679-102 679-104 679-105 679-106 679-108 679-110 679-112 679-114 679-116 SRN Src. If you do not find a problem. use Chapter 11. Description: An unrecoverable hardware error. adapter. Description: A SCSI command time-out occurred. Description: The motor failed to restart. D Failing Function Codes 678 B88 software 678 B88 678 B88 software 678 B88 software 679 679 679 679 679 679 679 679 Description and Action (Unless otherwise indicated. 679-130 679-132 G D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: A SCSI busy or command error. Description: Error log analysis indicates a SCSI bus problem.) Description: A reservation conflict occurred. Description: A protocol error. diagnostic software. Description: The media format is corrupted. and application software to be sure they are all compatible. Action: Check the levels of the device. D Description: The drive returned bad or non-extended sense data. Description: A SCSI reservation conflict error. Description: The diagnostic test failed. 679-117 679-118 679-120 679-122 679-124 679-126 679-128 679-129 D D D D D D G G 679 679 B88 679 679 679 679 B88 679 190 679 B88 software 679 679 Description: A write-protect error occurred. Description: The drive did not become ready. Description: An adapter or bus I/O error occurred. Description: A disk drive hardware error occurred. “MAP 0210: General Problem Resolution” on page 67.

67B-100 67B-601 67B-602 67B-603 67B-604 67B-605 67B-606 67B-607 67E-001 D G G G G G G G D 67E-002 D Description: Display problem. Description: The diagnostic test failed.tamper. Description: The bus test failed. 681-102 681-104 681-105 681-106 681-108 681-110 681-112 681-114 D D D D D D D D Description: An unrecoverable media error occurred. use Chapter 11. Description: The motor failed to restart. Description: ELA indicates a X-ray or dead battery condition. Description: ELA indicates an out-of-temperature specification. Chapter 31. SRNs 101-000 through 69d-701 339 . Description: ELA indicates a mesh violation . 67E-003 67E-004 D D Description: Software error. Description: Adapter problem.Service Request Number 679-134 679-135 SRN Src. Description: The electronics card test failed. Description: ELA indicates the coprocessor is held in a reset condition. or +12 V over-voltage condition. “MAP 0210: General Problem Resolution” on page 67. D D Failing Function Codes B88 software 679 B88 software 679 679 B88 190 67B 11A 67B 67B 67B 67B 67B 67B 67E 221 Monitor/ Cable 67E Monitor/ Cable software 67E 67E Monitor/ Cable 681 681 681 681 681 681 681 681 Description and Action (Unless otherwise indicated. Description: ELA indicates a low battery warning. Description: The device failed to configure. Description: An unrecoverable hardware error. Description: The disk drive indicates an error. Description: The media format is corrupted. 679-136 679-137 D D Description: The certify operation failed. Description: The monitor test failed. +5. Description: Unit attention condition has occurred on the Send Diagnostic command.) Description: The adapter failed to configure. Description: ELA indicates a +3. Description: The drive did not become ready. Description: POST failed: Catastrophic error detected.

D Failing Function Codes Description and Action (Unless otherwise indicated. Description: The CD-ROM drive indicates an error. Description: A SCSI command time-out occurred. Description: Unable to reserve device. Description: Error log analysis indicates a SCSI bus problem. 681-136 681-137 D D Description: The certify operation failed. Description: Unable to do configuration. 681-130 681-132 681-134 681-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. use Chapter 11. Description: The adapter failed to configure. Action: Check the levels of the device. that no other system environmental warnings are occurring. If you do not find a problem. use MAP 210. call your support person. Description: A software error was caused by a hardware failure. 681-117 681-118 681-120 681-122 681-124 681-126 681-128 681-129 D D D D D D G G 681 681 B88 681 681 681 681 B88 681 190 681 B88 software 681 681 B88 software 681 B88 software 681 681 B88 190 681 Description: A write-protect error occurred. and application software to be sure they are all compatible.) Description: A protocol error. Description: A disk drive hardware error occurred. adapter. Description: The error log analysis indicates a hardware failure. “MAP 0210: General Problem Resolution” on page 67. 681-138 D 682-111 682-112 682-113 682-121 D D D D 682 B88 682 B88 682 B88 682 340 Diagnostic Information for Multiple Bus Systems . Description: The device failed to configure. Description: A SCSI reservation conflict error. Description: A SCSI check condition error occurred. Description: Unable to open the device driver. Action: Check to be sure none of the air passages in the system covers are blocked. Description: Error log analysis indicates that the disk drive is operating at a higher than recommended temperature. Otherwise. diagnostic software. Description: A SCSI busy or command error.Service Request Number 681-116 SRN Src. Description: Unit attention condition has occurred on the Send Diagnostic command.

) Description: The CD-ROM drive indicates an error. Description: Undefined error detected. Description: Error Log Analysis Indicates hardware failure VSS2105 Model B09. Description: No tone during audio test. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error. Description: Unable to open device driver. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error. Description: A command timeout was detected. Description: A command reservation conflict was detected. D D D D D D D D D D D D D D D D D D D G G G D Failing Function Codes 682 682 682 B88 682 682 682 682 Test Disc 682 682 B88 682 682 682 682 682 682 682 B88 682 682 682 682 682 B88 683 685 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable Description and Action (Unless otherwise indicated. use Chapter 11. Description: The LED test failed. Description: The CD-ROM drive indicates an error. Description: Unable to do configuration. Description: Undefined error detected. Description: Unable to reserve device. SRNs 101-000 through 69d-701 341 . Description: The CD-ROM drive indicates an error. Description: A media error was detected. Description: RGB_SCREEN_USER_FAIL 685-040 D Description: STATUS_POLL_TIMEOUT_ERROR 685-041 D Description: CRC_POLL_TIMEOUT_ERROR Chapter 31. Description: Errors found during ELA.Service Request Number 682-122 682-123 682-125 682-126 682-127 682-128 682-129 682-150 682-151 682-152 682-162 682-171 682-172 682-173 682-175 682-198 682-199 682-211 682-281 682-301 682-302 683-128 685-001 SRN Src. Description: Errors found during ELA. “MAP 0210: General Problem Resolution” on page 67. Description: The CD-ROM drive indicates an error.

use Chapter 11. Description: INTERNAL_ERROR_DATA_SIZE_0 Description: INTERNAL_ERROR_DATA_SIZE_1 Description: INTERNAL_ERROR_DATA_SIZE_2 Description: INTERNAL_ERROR_DATA_SIZE_3 Description: ODM INIT FAILED Description: ODM_OBJECT_SEARCH_FAILED Description: ODM_GET_OBJECT_FAILED Description: ODM_TERM_FAILED Description: ILLEGAL_RESOLUTION_SPECIFIED Description: AIXGSC_MGA_START_INTERRUPT_FAILED Description: AIXGSC_MGA_STOP_INTERRUPT_FAILED Description: MDD_OPEN_BUS_FAILED Description: MDD_IOCTL_ERROR Description: OPEN_RCM_ERROR Description: IOCTL_GSC_HANDLE_FAILED Description: AIXGSC_MAKE_GP_FAILED 342 Diagnostic Information for Multiple Bus Systems .Service Request Number 685-060 685-081 685-082 685-0B0 685-0B1 685-0D0 685-0D1 685-0D2 685-0D3 685-0D5 685-0D6 685-0D8 685-0D9 685-0DB 685-0E5 685-0E6 685-0E7 685-0E8 685-0E9 685-0EA 685-0EB SRN Src.) Description: SVC_AIDS_INPUT_ERROR Description: LOOP_COUNT_WAS_ZERO Description: INVALID_TU_NUMBER Description: ROM test failed. D D D D D D D D D D D D D D D D D D D D D Failing Function Codes software 685 software 685 software 685 software 685 software 685 softwar 685 software 685 software 685 software 685 software 685 software 685 software 685 software 685 software 685 software 685 software 685 software 685 software 685 software 685 software 685 software 685 Description and Action (Unless otherwise indicated. “MAP 0210: General Problem Resolution” on page 67. Description: ROM test failed.

use Chapter 11. SRNs 101-000 through 69d-701 343 . “MAP 0210: General Problem Resolution” on page 67.) Description: AIXGSC_UNMAKE_GP_FAILED Description: DEVICE_BUSY_ERROR Description: AIXGSC_MGA_SET_DISPLAY_FAILED Description: REG_32_BIT_PRTN_ERROR 685-101 D Description: REG_32_BIT_ADDR_UNIQ_ERROR 685-102 D Description: REG_8_BIT_PTRN_ERROR 685-103 D Description: REG_8_BIT_ADDR_UNIQ_ERROR 685-104 D Description: CRTC_REGS_PTRN_ERROR 685-105 D Description: CRTC_REGS_ADDR_UNIQ_ERROR 685-106 D Description: CRTCEXT_REGS_PTRN_ERROR 685-107 D Description: CRTCEXT_REGS_ADDR_UNIQ_ERROR 685-108 D Description: RAMDAC_REGS_PTRN_ERROR 685-109 D Description: RAMDAC_REGS_ADDR_UNIQ_ERROR Chapter 31. D D D D Failing Function Codes software 685 software 685 software 685 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable Description and Action (Unless otherwise indicated.Service Request Number 685-0EC 685-0ED 685-0EE 685-100 SRN Src.

Description: ROM test failed. Description: ROM test failed. Description: ROM test failed.) Description: PALETTE_REGS_PTRN_ERROR 685-10B D Description: PALETTE_REGS_ADDR_UNIQ_ERROR 685-200 685-201 685-202 685-203 685-204 685-205 685-206 685-207 685-208 685-209 685-20B 685-400 D D D D D D D D D D D D Description: ROM test failed. Description: ROM test failed. Description: ROM test failed.Service Request Number 685-10A SRN Src. Description: ROM test failed. Description: ROM test failed. “MAP 0210: General Problem Resolution” on page 67. Description: ROM test failed. Description: ROM test failed. use Chapter 11. Description: ROM test failed. D Failing Function Codes 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 685 227 685 227 685 227 685 227 685 227 685 227 685 227 685 227 685 227 685 227 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable Description and Action (Unless otherwise indicated. Description: SGRAM_RED_SCREEN_ERROR 685-401 D Description: SGRAM_GREEN_SCREEN_ERROR 685-402 D Description: SGRAM_BLUE_SCREEN_ERROR 344 Diagnostic Information for Multiple Bus Systems .

D Failing Function Codes 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable software 685 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable Description and Action (Unless otherwise indicated.) Description: SGRAM_WHITE_SCREEN_ERROR 685-404 D Description: SGRAM_INCREMENTING_SCREEN_ERROR 685-500 D Description: BLIT_TEST_ERROR_640 x 480 685-501 D Description: BLIT_TEST_ERROR_800 x 600 685-502 D Description: BLIT_TEST_ERROR_1024 x 768 685-503 D Description: BLIT_TEST_ERROR_1280 x 1024 685-504 685-600 D D Description: INTERNAL_ERROR_DATA_SIZE_4 Description: DRAW_TEST_ERROR_640 x 480_A 685-601 D Description: DRAW_TEST_ERROR_800 x 600_A 685-602 D Description: DRAW_TEST_ERROR_1024 x 768_A 685-603 D Description: DRAW_TEST_ERROR_1280 x 1024_A 685-604 D Description: INTERNAL_ERROR_DATA_SIZE_5 Chapter 31. use Chapter 11. SRNs 101-000 through 69d-701 345 .Service Request Number 685-403 SRN Src. “MAP 0210: General Problem Resolution” on page 67.

Description: The modem control line test failed.) Description: DRAW_TEST_ERROR_640 x 480_B 685-606 D Description: DRAW_TEST_ERROR_800 x 600_B 685-607 D Description: DRAW_TEST_ERROR_1024 x 768_B 685-608 D Description: DRAW_TEST_ERROR_1280 x 1024_B 685-609 685-60A D D Description: INTERNAL_ERROR_DATA_SIZE_6 Description: DRAW_TEST_ERROR_640 x 480_C 685-60B D Description: DRAW_TEST_ERROR_800 x 600_C 685-60C D Description: DRAW_TEST_ERROR_1024 x 768_C 685-60D D Description: DRAW_TEST_ERROR_1280 x 1024_C 685-60E 686-114 686-124 686-152 686-153 686-252 686-253 686-501 D D D D D D D D Description: INTERNAL_ERROR_DATA_SIZE_7 Description: The register verification test failed. Description: The data wrap communication test failed. D Failing Function Codes 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable software 685 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable 685 227 Monitor/ cable software 685 686 686 686 D57 686 686 686 686 Description and Action (Unless otherwise indicated. “MAP 0210: General Problem Resolution” on page 67. Description: Adapter Reset failed 346 Diagnostic Information for Multiple Bus Systems . Description: The adapter RAM verification test failed. use Chapter 11.Service Request Number 685-605 SRN Src. Description: The modem control line test failed. Description: The data wrap communication test failed.

use MAP 210 with a FFC of 686. Chapter 31. Description: Port async external loopback test failed (general). SRNs 101-000 through 69d-701 347 . Description: Adapter BIOS POST Timer failed. Description: Adapter BIOS Reset failed. Description: Adapter BIOS RAM test failed. Description: Adapter BIOS Command failed. Description: Port async external loopback test failed (data signals). Description: Adapter BIOS POST Async Ports failed. Action: Run diagnostics from a source other than from the disk or a network. Description: Port async internal loopback test failed (no response from the port). Description: Adapter BIOS POST Checksum failed.Service Request Number 686-511 686-512 686-513 686-514 686-521 686-522 686-523 686-524 686-526 686-527 686-528 686-529 686-531 686-533 686-534 686-541 686-542 686-551 686-552 686-553 686-554 686-555 686-901 to 686-920 SRN Src. otherwise. Description: Adapter BIOS Download failed. Description: Adapter BIOS Timer test failed. Description: An unexpected error occurred that can be attributed to software or hardware. use Chapter 11. “MAP 0210: General Problem Resolution” on page 67. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Description: Port async external loopback test failed (no response from port). Description: Adapter to host memory test failed (byte pattern test). suspect a software problem. Description: Port async external loopback test failed (modem signals). D D D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 686 686 686 686 686 686 686 686 686 686 686 686 686 686 686 686 686 686 686 686 686 686 software 686 Description and Action (Unless otherwise indicated. Description: Adapter to host memory test failed (word pattern test). Description: Adapter BIOS POST CPU failed. Description: Adapter BIOS POST RAM failed. Description: Port async internal loopback test failed (general).) Description: Adapter to host memory test failed (byte tag test). Description: Adapter to host memory test failed (word tag test). Description: Port async external loopback test failed (control signals). Description: Adapter BIOS test failed.

Description: The data wrap communication test failed. Description: The adapter failed to configure software Description: An unexpected error occurred that can be attributed to software or hardware. D D Failing Function Codes 686 software software 686 Description and Action (Unless otherwise indicated. Action: Run diagnostics from a source other than from the disk or a network. Action: Run diagnostics from a source other than from the disk or a network. 348 Diagnostic Information for Multiple Bus Systems . Description: Adapter to host memory test failed (byte tag test).) Description: The adapter failed to configure. otherwise. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Description: The sync line test failed. Description: Adapter BIOS POST Checksum failed. Description: Adapter to host memory test failed (word tag test). use Chapter 11.Service Request Number 686-921 686-922 to 686-924 SRN Src. Description: Adapter Reset failed. Description: The modem control line test failed. 686-925 686-926 to 686-950 D D 686 software 686 687-111 687-114 687-124 687-144 687-152 D D D D D 687 687 687 687 837 684 687 152 687 687 687 687 687 687 687 687 687 687 687 687 687 687-153 687-244 687-252 687-253 687-501 687-502 687-511 687-512 687-513 687-514 687-521 687-522 687-523 D D D D D D D D D D D D D Description: The modem control line test failed. Description: The controller register test failed. Description: The register verification test failed. Description: Adapter BIOS POST CPU failed. Description: Adapter BIOS POST Timer failed. use MAP 210 with a FFC of 686. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. otherwise. Description: Adapter to host memory test failed (word pattern test). use MAP 210 with a FFC of 686. Description: Adapter Fuse failed. Description: The adapter RAM verification test failed. Description: Adapter to host memory test failed (byte pattern test). Description: The data wrap communication test failed. “MAP 0210: General Problem Resolution” on page 67. suspect a software problem. Description: The sync line test failed. Description: An unexpected error occurred that can be attributed to software or hardware. suspect a software problem.

) Description: Adapter BIOS POST RAM failed. use MAP 210 with a FFC of 687. Action: Run diagnostics from a source other than from the disk or a network. suspect a software problem. Description: Adapter BIOS Timer test failed. Description: Adapter BIOS test failed. Description: The electronics card test failed. Description: An unexpected error occurred that can be attributed to software or hardware. Description: Adapter BIOS Command failed. Description: Port sync external loopback test failed. Description: The bus test failed.Service Request Number 687-524 687-525 687-527 687-528 687-529 687-531 687-533 687-534 687-541 687-551 687-600 687-700 687-901 to 687-920 SRN Src. Description: Adapter BIOS Reset failed. 687-921 687-922 to 687-924 D D software 687 software 687 687-925 687-926 to 687-950 D D 687 software software 687 689-102 689-104 689-105 689-106 689-108 D D D D D 689 689 689 689 689 Chapter 31. otherwise. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. suspect a software problem. use MAP 210 with a FFC of 687. Description: An unrecoverable media error occurred. Description: Port sync internal loopback test failed. SRNs 101-000 through 69d-701 349 . suspect a software problem. Description: Adapter BIOS RAM test failed. “MAP 0210: General Problem Resolution” on page 67. use MAP 210 with a FFC of 687. D D D D D D D D D D D D D Failing Function Codes 687 687 687 687 687 687 687 687 687 687 837 684 software 687 Description and Action (Unless otherwise indicated. Action: Run diagnostics from a source other than from the disk or a network. Description: An unexpected error occurred that can be attributed to software or hardware. Description: The adapter failed to configure. Action: Run diagnostics from a source other than from the disk or a network. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Description: An unexpected error occurred that can be attributed to software or hardware. Description: Adapter BIOS POST Sync Line failed. Description: The adapter failed to configure. Description: Adapter BIOS Download failed. Description: 422RAN status test failed. otherwise. Description: The motor failed to restart. Description: The drive did not become ready. Description: 232RAN status test failed. otherwise. use Chapter 11.

Description: The diagnostic test failed. 689-130 689-132 689-134 689-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: An error is detected in request sense data. Description: A protocol error. Description: A disk drive hardware error occurred.) Description: The media format is corrupted. 68C-101 68C-102 68C-103 68C-104 68C-105 D D D D D 350 Diagnostic Information for Multiple Bus Systems . Description: The device failed to configure.Service Request Number 689-110 689-112 689-114 689-116 SRN Src. Description: A SCSI busy or command error. Description: The adapter failed to configure. Description: A software error was caused by a hardware failure. 689-117 689-118 689-120 689-122 689-124 689-126 689-128 689-129 D D D D D D G G 689 689 B88 689 689 689 689 B88 689 190 689 B88 software 689 689 B88 software 689 B88 software 689 689 B88 190 68C 68C 68C 68C 68C Description: A write-protect error occurred. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The SCSI device indicates busy. Description: Timeout while attempting to communicate with SCSI device. Description: The SCSI device indicates a reservation conflict. Description: A SCSI command time-out occurred. call your support person. Action: Check the levels of the device. Description: The SCSI device indicates a check condition. diagnostic software. Description: The error log analysis indicates a hardware failure. Description: An unrecoverable hardware error. Description: Error log analysis indicates a SCSI bus problem. Description: A SCSI check condition error occurred. “MAP 0210: General Problem Resolution” on page 67. 689-136 689-137 D D Description: The certify operation failed. adapter. Description: A SCSI reservation conflict error. If you do not find a problem. and application software to be sure they are all compatible. use Chapter 11. D D D D Failing Function Codes 689 689 689 Description and Action (Unless otherwise indicated.

68C-167 68C-168 68C-169 D D D Description: An unexpected SCSI error occurred. Description: Timeout while attempting to communicate with the SCSI device. Description: The Mode Select command failed. Description: The Reserve command failed. Description: The Send Diagnostic command failed. Description: Invalid condition from drive after a request sense. Description: Invalid condition from the drive after a reserve. Description: The Unload command failed. use Chapter 11. 68C-166 D Description: Unable to configure the device. D D D D D D D D D D D D D D D D D Failing Function Codes 68C 68C 68C 68C 68C 68C 68C 68C media B88 software 68C media 68C 68C media 68C media 68C B88 68C B88 68C B88 68C B88 276 68C B88 software 68C B88 B88 software 68C media Description and Action (Unless otherwise indicated. Description: The Load command failed. Description: The write-protect sensor test failed. Description: The adapter failed to configure. Description: Invalid condition from the drive after a reserve. Description: The Test Unit Ready command failed.) Description: Sense data from the SCSI drive has unexpected data. Description: The Inquiry command failed. SRNs 101-000 through 69d-701 351 . Chapter 31. Description: The adapter failed to configure.Service Request Number 68C-107 68C-110 68C-111 68C-112 68C-113 68C-114 68C-120 68C-130 68C-134 68C-135 68C-140 68C-150 68C-160 68C-161 68C-163 68C-164 68C-165 SRN Src. Read and Compare Test failed. Description: Timeout while attempting to communicate with the SCSI device. Description: Write. Description: Invalid condition from the drive after a request sense. Description: The Send Diagnostic command failed. “MAP 0210: General Problem Resolution” on page 67.

D D Description: A device timeout error occurred.Service Request Number 68C-170 SRN Src. D Description: Software error. Description: The Release command failed.) Description: The Read. 352 Diagnostic Information for Multiple Bus Systems . Description: The device configuration failed. Description: The Request Sense command failed. Write and Compare test failed. Description: The Mode Select command failed. 68C-180 68C-185 68C-190 68C-200 68C-201 68C-210 68C-211 68C-220 68C-230 68C-240 68C-260 68C-261 68C-300 68C-310 D D D D G D D D D D D D D D Description: The Load command failed. Description: An adapter or bus I/O error occurred. Description: Error diagnosed from error log analysis. “MAP 0210: General Problem Resolution” on page 67. Description: The device open failed. Description: A reservation conflict occurred. D Description: The drive returned bad or non-extended sense data. use Chapter 11. D Failing Function Codes 68C B88 media 68C media 68C media 68C 68C media 68C B88 68C B88 68C B88 68C 68C 68C 68C 68C 68C software B88 68C software 68C media 68C B88 software 68C B88 68C B88 software 68C B88 software Software 68E Description and Action (Unless otherwise indicated. Description: The Openx command failed. 68C-320 68C-411 to 68C-423 68C-511 to 68C-523 68C-611 to 68C-623 68C-711 to 68C-723 68E-001 G D Description: Error log analysis indicates a failure. Description: The device configuration failed. Description: The Unload command failed. Description: SCSI adapter configuration failed. Description: The Test Unit Ready command failed. Description: The device open failed. Description: The device configuration failed.

Description: An unrecoverable hardware error. Description: The motor failed to restart. call your support person. 68E-005 D Description: Adapter failure. Description: Adapter failure. Description: The drive did not become ready. 690-117 690-118 690-120 690-122 690-124 690-126 690-128 690-129 D D D D D D G G 690 690 B88 690 690 690 690 B88 690 190 690 B88 software 690 690 Description: A write-protect error occurred. Description: A SCSI command time-out occurred. 690-130 690-132 G D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. “MAP 0210: General Problem Resolution” on page 67. Action: Check the levels of the device.Service Request Number 68E-002 68E-003 68E-004 SRN Src. Description: A SCSI check condition error occurred. Chapter 31. Description: A SCSI busy or command error. Description: The media format is corrupted. Description: The electronics card test failed. Description: The error log analysis indicates a hardware failure. Description: A disk drive hardware error occurred. Description: A SCSI reservation conflict error. Description: Error log analysis indicates a SCSI bus problem. Description: Display failure. 690-102 690-104 690-105 690-106 690-108 690-110 690-112 690-114 690-116 D D D D D D D D D Description: An unrecoverable media error occurred. D D D Failing Function Codes 68E Software 68E 227 68E Monitor/ Cable 68E 227 Monitor/ Cable 690 690 690 690 690 690 690 690 Description and Action (Unless otherwise indicated. Description: The bus test failed.) Description: Adapter failure. SRNs 101-000 through 69d-701 353 . Description: A software error was caused by a hardware failure. Description: The diagnostic test failed. adapter. diagnostic software. use Chapter 11. and application software to be sure they are all compatible. Description: A protocol error. If you do not find a problem.

Description: The ATM 25Mbps Adapter register test failed. Description: The Load command failed. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The ATM 25Mbps Adapter open test failed. Description: The Test Unit Ready command failed. 690-136 690-137 D D Description: The certify operation failed. Action: Re-install the ATM 25Mbps Adapter and re-run the test. If the error continues. If the error continues.Service Request Number 690-134 690-135 SRN Src.) Description: The adapter failed to configure. “MAP 0210: General Problem Resolution” on page 67. Description: The ATM 25Mbps Adapter was not found. Description: The ATM 25Mbps Adapter wrap test failed. Description: The Inquiry command failed. Description: Error log analysis reported a hardware error. 691-200 691-202 691-203 691-204 691-205 691-206 691-210 691-220 D D D D D D D D 691-300 D 691-700 692-110 692-120 692-130 692-135 692-140 692-150 692-160 G D D D D D D D 354 Diagnostic Information for Multiple Bus Systems . use MAP 210. Description: The Reserve command failed. Description: The device failed to configure. use Chapter 11. use MAP 210. Description: The ATM 25Mbps Adapter interrupt test failed. Description: The ATM 25Mbps Adapter NVRAM test failed. Description: The ATM 25Mbps Adapter wrap test failed. Action: Re-install the wrap plug and re-run the test. D D Failing Function Codes B88 software 690 B88 software 690 690 B88 190 691 227 691 227 691 227 691 227 691 227 691 227 691 227 691 227 Wrap Plug 691 227 691 227 692 692 692 media 692 media 692 692 media 692 media Description and Action (Unless otherwise indicated. Description: The ATM 25Mbps Adapter memory test failed. Description: The Mode Select command failed. Description: The Unload command failed. Description: The Send Diagnostic command failed. Description: The ATM 25Mbps Adapter close test failed.

Description: Adapter config register test failed. Description: The Mode Select command failed. Description: The Test Unit Ready command failed. D D Description: A device timeout error occurred. “MAP 0210: General Problem Resolution” on page 67. Description: The Unload command failed. use Chapter 11.) Description: The Send Diagnostic command failed.Service Request Number 692-169 692-170 SRN Src. D Description: The drive returned bad or non-extended sense data. Description: An adapter or bus I/O error occurred. Description: The Openx command failed. Description: The Release command failed. Description: The device configuration failed. SRNs 101-000 through 69d-701 355 . Description: SCSI adapter configuration failed. Write and Compare test failed. D D D Description: Adapter open failed. Description: The device configuration failed. Description: Adapter reset failed. 692-320 692-411 to 692-423 692-511 to 692-523 692-611 to 692-623 692-711 to 692-723 693-100 693-101 693-102 G D Description: Error log analysis indicates a failure. Chapter 31. 692-180 692-185 692-190 692-200 692-210 692-220 692-230 692-240 692-300 692-310 D D D D D D D D D D Description: The Load command failed. Description: The Read. Description: The Request Sense command failed. D D Failing Function Codes 692 media 692 B88 media 692 media 692 media 692 692 media 692 B88 692 692 692 692 software B88 692 software 692 media 692 B88 software 692 B88 692 B88 software 692 B88 software 693 227 693 227 693 227 Description and Action (Unless otherwise indicated. Description: A reservation conflict occurred.

Description: Suni detected bad parity. D D D D D Failing Function Codes 693 227 693 227 693 227 693 227 697 software 227 697 software 227 697 software 227 697 software 227 697 software 227 697 software 227 697 697 697 Wrap Plug 697 Wrap Plug 697 697 software 227 697 227 software 697 697 697 Description and Action (Unless otherwise indicated. Description: Loss of light detected in Link test. Description: Internal wrap test failure 356 Diagnostic Information for Multiple Bus Systems . Description: Adapter close failed. “MAP 0210: General Problem Resolution” on page 67. Description: Charm memory write failure. 697-10D D Description: DMS failed. Description: Internal Loopback failed. Description: Adapter microcode download test failed. Description: Adapter checksum failure. 697-101 D Description: Charm memory read failure. Description: Suni initialization failure. use Chapter 11. 697-104 D Description: Packet memory error. Action: Check wrap plug installation. 697-103 D Description: Charm software reset failure.) Description: Adapter I/O register test failed. Description: Adapter internal wrap test failed. Description: External Loopback failed Action: Check wrap plug installation.Service Request Number 693-103 693-104 693-105 693-106 697-100 SRN Src. 697-105 D Description: Control memory failure. 697-106 697-107 697-108 697-109 697-10B 697-10C D D D D D D Description: Link-R detected bad parity. 697-102 D Description: PCI configuration register write failure. 697-121 697-122 697-123 D D D Description: Adapter memory test failure.

Service Request Number 697-124 697-125 697-126 697-127 697-1FF SRN Src. SRNs 101-000 through 69d-701 357 . D D D D D Failing Function Codes 697 221 221 697 697 software 227 software 697 227 software 697 227 software 697 227 software 697 227 software 697 227 software 697 227 697 221 697 221 697 221 697 221 697 221 697 698 software 227 Description and Action (Unless otherwise indicated. 697-206 D Description: Error in releasing adapter 697-221 697-222 697-223 697-224 697-701 697-702 698-100 D D D D G G D Description: Hardware failure opening the adapter Description: Enhanced Error Handling failure opening the adapter Description: Interrupt test failure Description: Adapter DMA test failure Description: Error Log Analysis indicates an I/O failure on the adapter. Description: Error Log Analysis indicates an unrecovered interrupt error. “MAP 0210: General Problem Resolution” on page 67.) Description: External wrap test failure Description: Enhanced Error Handling failure on bus Description: Enhanced Error Handling failure on EADS chip Description: Enhanced Error Handling failure on adapter Description: EPROM checksum failed 697-200 D Description: Klog error 697-201 D Description: ASL error 697-202 D Description: ODM Initialization error 697-203 D Description: Diagnostic configuration failure. Description: Charm memory write failure. Chapter 31. use Chapter 11. 697-205 D Description: Error in diag open.

) Description: Charm memory read failure. Description: External Loopback failed Action: Check wrap plug installation. Description: Internal Loopback failed. Description: EPROM checksum failed. D Failing Function Codes 698 software 227 698 software 227 698 software 227 698 software 227 698 software 227 698 698 698 Wrap Plug 698 Wrap Plug 698 698 software 227 698 227 software 698 698 698 698 221 221 698 698 software 227 software 698 227 Description and Action (Unless otherwise indicated. 698-10D D Description: DMS failed. 698-200 D Description: Klog error. 358 Diagnostic Information for Multiple Bus Systems . Description: Enhanced Error Handling failure on bus. 698-121 698-122 698-123 698-124 698-125 698-126 698-127 698-1FF D D D D D D D D Description: Adapter memory test failure. Description: External wrap test failure. 698-103 D Description: Charm software reset failure. Description: Loss of light detected in Link test. Description: Internal wrap test failure. Description: Enhanced Error Handling failure on adapter. use Chapter 11. Description: Suni detected bad parity. 698-104 D Description: Packet memory error 698-105 D Description: Control memory failure. Description: Suni initialization failure.Service Request Number 698-101 SRN Src. 698-102 D Description: PCI configuration register write failure. “MAP 0210: General Problem Resolution” on page 67. Description: Adapter checksum failure. Action: Check wrap plug installation. Description: Enhanced Error Handling failure on EADS chip. 698-106 698-107 698-108 698-109 698-10B 698-10C D D D D D D Description: Link-R detected bad parity.

Description: Adapter checksum failure. Description: Internal loopback test failure. Description: External wrap test failure. 698-206 D Description: Error in releasing adapter.) Description: ASL error. SRNs 101-000 through 69d-701 359 . Description: An error was found on the adapter Description: Error Log analysis indicates a hardware error. Description: Error Log Analysis indicates an I/O failure on the adapter. Description: Adapter DMA test failure. Description: EPROM test failure. use Chapter 11. Description: Adapter buffer test failure. Description: Enhanced Error Handling failure on bus. Description: Adapter memory test failure. D Failing Function Codes software 698 227 software 698 227 software 698 227 software 698 227 software 698 227 698 221 698 221 698 221 698 221 698 221 698 699 699 699 69b 69b 69b 69b 69b 69b 69b 69b 221 Description and Action (Unless otherwise indicated. Description: Adapter SDRAM failure. Description: Adapter hardware has caused a software failure. Description: Error Log Analysis indicates an unrecovered interrupt error. Description: Enhanced Error Handling failure opening the adapter. 698-205 D Description: Error in diag open. 698-221 698-222 698-223 698-224 698-701 698-702 699-100 699-110 699-120 69b-101 69b-102 69b-103 69b-104 69b-105 69b-106 69b-107 69b-108 69b-109 D D D D G G D G D D D D D D D D D D Description: Hardware failure opening the adapter. Description: Interrupt test failure.Service Request Number 698-201 SRN Src. 698-203 D Description: Diagnostic configuration failure. “MAP 0210: General Problem Resolution” on page 67. Chapter 31. 698-202 D Description: ODM Initialization error. Description: Adapter cache test failure.

) Description: Enhanced Error Handling failure on Eads chip. Description: Enhanced Error Handling failure on Eads chip. “MAP 0210: General Problem Resolution” on page 67. Description: Adapter cache test failure. Description: Adapter checksum failure. use Chapter 11. Description: Interrupt test failure. Description: Error Log Analysis indicates an I/O failure on the adapter. Description: Hardware failure opening adapter. Description: Hardware failure opening adapter. Description: EPROM test failure. Description: Interrupt test failure. Description: Adapter SDRAM failure. Description: Enhanced Error Handling failure on adapter. Description: Adapter DMA test failure. Description: Adapter memory test failure. Description: Enhanced Error Handling failure on adapter. Description: Internal loopback test failure. D D D D D D G D D D D D D D D D D D D D D D G Failing Function Codes 221 69b 69b 221 69b 221 69b 221 69b 221 69b 69d 69d 69d 69d 69d 69d 69d 69d 221 221 69d 69d 221 69d 221 69d 221 69d 221 69d Description and Action (Unless otherwise indicated. Description: Adapter buffer test failure. Description: Error Log Analysis indicates an I/O failure on the adapter. Description: Enhanced error handling failure opening the adapter. Description: Enhanced Error Handling failure on bus. 360 Diagnostic Information for Multiple Bus Systems . Description: Adapter DMA test failure. Description: Enhanced error handling failure opening the adapter. Description: External wrap test failure.Service Request Number 69b-110 69b-111 69b-201 69b-202 69b-203 69b-204 69b-701 69d-101 69d-102 69d-103 69d-104 69d-105 69d-106 69d-107 69d-108 69d-109 69d-110 69d-111 69d-201 69d-202 69d-203 69d-204 69d-701 SRN Src.

SRNs 700-102 through 89c-302 Note: Some SRNs in this chapter may have 4 rather than 3 digits after the dash (-). diagnostic software. adapter.1 GB 16-bit single-ended disk drive problem.Chapter 32. Description: Unit attention condition has occurred on the Send Diagnostic command. adapter. call your support person. Action: Check the levels of the device.1 GB single-ended disk drive problem. Description: A SCSI command time-out. Description: A disk drive hardware error occurred.) Description: 1. Description: The adapter failed to configure. Description: The error log analysis indicates a hardware failure. If you do not find a problem. use Chapter 11. call your support person. Description: The device failed to configure. Description: 1. “MAP 0210: General Problem Resolution” on page 67. 700 700 B88 700 Description: A write-protect error occurred. and application software to be sure they are all compatible. If you do not find a problem. diagnostic software. 700-130 700-132 700-134 700-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. D Description: A protocol error. Description: A protocol error. 700-136 700-137 D D Description: The certify operation failed. 701-102 to 701-114 701-116 D D 361 . Description: A SCSI error. Action: Check the levels of the device. 700-117 700-118 700-120 to 700-124 700-126 700-128 700-129 D D D D G G 700 B88 700 190 700 B88 software 700 700 B88 software 700 B88 software 700 700 B88 190 701 Description: A software error was caused by a hardware failure. Description: Error log analysis indicates a SCSI bus problem. D Failing Function Codes 700 Description and Action (Unless otherwise indicated. and application software to be sure they are all compatible. Service Request Number 700-102 to 700-114 700-116 SRN Src.

Description: 1. Description: The device failed to configure. Description: A SCSI command time-out. Description: Error log analysis indicates a SCSI bus problem. 701-130 701-132 701-134 701-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: A SCSI error.) Description: A write-protect error occurred. Description: The adapter failed to configure. 701-136 701-137 D D Description: The certify operation failed. D D D D G G Failing Function Codes 701 701 B88 701 701 B88 701 190 701 B88 software 701 701 B88 software 701 B88 software 701 701 B88 190 702 Description and Action (Unless otherwise indicated. call your support person. Action: Check the levels of the device. use Chapter 11. If you do not find a problem. Description: The error log analysis indicates a hardware failure. “MAP 0210: General Problem Resolution” on page 67. 702 702 B88 702 Description: A write-protect error occurred. Description: A software error was caused by a hardware failure. 702-117 702-118 702-120 to 702-124 702-126 702-128 D D D D G 702B88 702 Description: A software error was caused by a hardware failure. diagnostic software.Service Request Number 701-117 701-118 701-120 to 701-124 701-126 701-128 701-129 SRN Src.1 GB 16-bit differential disk drive problem. 702-102 to 702-114 702-116 D D Description: A protocol error. Description: Unit attention condition has occurred on the Send Diagnostic command. 362 Diagnostic Information for Multiple Bus Systems . Description: A disk drive hardware error occurred. Description: A SCSI command time-out. Description: The error log analysis indicates a hardware failure. and application software to be sure they are all compatible. adapter. Description: A SCSI error.

702-136 702-137 D D Description: The certify operation failed. G Failing Function Codes 190 702 B88 software 702 702 B88 software 702 B88 software 702 702 B88 190 703 Description and Action (Unless otherwise indicated.Service Request Number 702-129 SRN Src. 703-102 to 703-114 703-116 D D Description: A protocol error. diagnostic software. 703-130 703-132 703-134 G D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: The device failed to configure.2 GB single-ended disk drive problem. Description: A SCSI command time-out. Description: A SCSI error. Description: 2. Action: Check the levels of the device. Description: A disk drive hardware error occurred. 703 703 B88 703 Description: A write-protect error occurred. call your support person. “MAP 0210: General Problem Resolution” on page 67. Description: The adapter failed to configure. Description: Error log analysis indicates a SCSI bus problem. SRNs 700-102 through 89c-302 363 . Description: The error log analysis indicates a hardware failure.) Description: Error log analysis indicates a SCSI bus problem. Chapter 32. Description: A disk drive hardware error occurred. use Chapter 11. Description: Unit attention condition has occurred on the Send Diagnostic command. If you do not find a problem. and application software to be sure they are all compatible. adapter. Description: The adapter failed to configure. 703-117 703-118 703-120 to 703-124 703-126 703-128 703-129 D D D D G G 703 B88 703 190 703 B88 software 703 703 B88 software Description: A software error was caused by a hardware failure. 702-130 702-132 702-134 702-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function.

D G G 704 B88 704 190 704 B88 software 704 704 B88 software 704 B88 software 704 704 B88 190 705 Description: A software error was caused by a hardware failure. Description: A disk drive hardware error occurred. and application software to be sure they are all compatible. Description: Unit attention condition has occurred on the Send Diagnostic command. 704-102 to 704-114 704-116 D D 704-117 704-118 704-120 to 704-124 704-126 704-128 704-129 D D D 704 704 B88 704 Description: A write-protect error occurred. diagnostic software. Description: A protocol error. Description: Error log analysis indicates a SCSI bus problem. 704-130 704-132 704-134 704-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function.2 GB 16-bit single-ended disk drive problem.) Description: The device failed to configure.Service Request Number 703-135 SRN Src. Description: 2. Description: A SCSI command time-out.2 GB 16-bit differential disk drive problem. Description: The error log analysis indicates a hardware failure. Description: The adapter failed to configure. “MAP 0210: General Problem Resolution” on page 67. Action: Check the levels of the device. use Chapter 11. Description: Unit attention condition has occurred on the Send Diagnostic command. If you do not find a problem. 703-136 703-137 D D Description: The certify operation failed. Description: 2. adapter. Description: A SCSI error. 704-136 704-137 D D Description: The certify operation failed. Description: The device failed to configure. 705-102 to 705-114 D 364 Diagnostic Information for Multiple Bus Systems . call your support person. D Failing Function Codes 703 B88 software 703 703 B88 190 704 Description and Action (Unless otherwise indicated.

) Description: A protocol error. and application software to be sure they are all compatible. Chapter 32. Description: The error log analysis indicates a hardware failure. Description: Error log analysis indicates a SCSI bus problem. Action: Check the levels of the device. 705-136 705-137 D D Description: The certify operation failed. Description: A SCSI error.Service Request Number 705-116 SRN Src. Description: A SCSI error. Description: The adapter failed to configure. call your support person. Description: A SCSI command time-out. call your support person. Description: A disk drive hardware error occurred. use Chapter 11.5 GB 16-bit single-ended disk drive problem. If you do not find a problem. Description: 4. Description: A protocol error. and application software to be sure they are all compatible. Description: The device failed to configure. diagnostic software. D G G 705 B88 705 190 705 B88 software 705 705 B88 software 705 B88 software 705 705 B88 190 706 Description: A software error was caused by a hardware failure. D Failing Function Codes Description and Action (Unless otherwise indicated. 705-130 705-132 705-134 705-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. If you do not find a problem. Description: Unit attention condition has occurred on the Send Diagnostic command. 705-117 705-118 705-120 to 705-124 705-126 705-128 705-129 D D D 705 705 B88 705 Description: A write-protect error occurred. diagnostic software. 706-102 to 706-114 706-116 D D 706-117 706-118 706-120 to 706-124 D D D 706 706 B88 706 Description: A write-protect error occurred. adapter. Action: Check the levels of the device. Description: A SCSI command time-out. SRNs 700-102 through 89c-302 365 . adapter. “MAP 0210: General Problem Resolution” on page 67.

Service Request Number 706-126 706-128 706-129 SRN Src. 706-136 706-137 D D Description: The certify operation failed. electronics card test failed. Description: Unit attention condition has occurred on the Send Diagnostic command. 366 Diagnostic Information for Multiple Bus Systems . call your support person. use Chapter 11. Description: The error log analysis indicates a hardware failure. 707-102 to 707-114 D 707-116 D 707-117 707-118 707-120 to 707-124 707-126 707-128 707-129 D D D 707 707 B88 707 Description: A write-protect error occurred. bus test failed. “MAP 0210: General Problem Resolution” on page 67. adapter.) Description: A software error was caused by a hardware failure. Description: The adapter failed to configure. Description: A SCSI command time-out. motor failed to restart. D G G 707 B88 707 190 707 B88 software Description: A software error was caused by a hardware failure. Description: A SCSI error. or diagnostic test failed. diagnostic software. media format failed. 706-130 706-132 706-134 706-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: A disk drive hardware error occurred. Description: Error log analysis indicates a SCSI bus problem. Description: The error log analysis indicates a hardware failure. Description: A protocol error. If you do not find a problem. and application software to be sure they are all compatible. the drive did not become ready. Description: Any of the following may have occurred: an unrecoverable media error. Description: Error log analysis indicates a SCSI bus problem. Description: The device failed to configure. D G G Failing Function Codes 706 B88 706 190 706 B88 software 706 706 B88 software 706 B88 software 706 706 B88 190 707 Description and Action (Unless otherwise indicated. Action: Check the levels of the device.

Chapter 32. Description: The modem control line test failed. Description: A disk drive hardware error occurred. Description: The VPD verification test failed. 707-136 707-137 D D Description: The certify operation failed.) Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. G D D D Failing Function Codes 707 707 B88 software 707 B88 software 707 707 B88 190 709 709 221 709 221 709 709 709 D57 709 684 837 709 837 837 836 837 684 709 684 709 152 266 266 266 D06 Description and Action (Unless otherwise indicated. Description: Remote async node test failed. use Chapter 11. Description: The register verification test failed. Description: The 128-port controller line test failed. Diagnostics: Cannot run the test because the device driver detected a hardware error. Description: Could not do the test because the device driver detected a hardware error. Description: The device failed to configure. Diagnostics: The data wrap communications test failed. Diagnostics: Remote Async Node test failed. Description: Sync line termination test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: The data wrap communication test failed. Description: The VPD verification test failed.Service Request Number 707-130 707-132 707-134 707-135 SRN Src. Description: The modem control line test failed. Description: Could not perform because the device driver detected a hardware error. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The adapter failed to configure. Description: Unable to determine the type of adapter from the VPD. “MAP 0210: General Problem Resolution” on page 67. SRNs 700-102 through 89c-302 367 . Description: The data wrap communication test failed. 709-101 709-111 709-112 709-113 709-114 709-115 709-116 709-117 709-118 709-119 709-151 709-152 709-153 709-154 709-155 D D D D D D D D D F D D D D D 709-161 709-162 709-163 709-164 D D D D Description: Could not perform because the device driver detected a hardware error. Description: The data wrap communication test failed.

Description: The data wrap communication test failed. Diagnostics: Cannot run the test because the device driver detected a hardware error while running the Remote Async Node wrap test. Description: The modem control line test failed. “MAP 0210: General Problem Resolution” on page 67. Description: The modem control line test failed. Description: The data wrap communication test failed. Description: The data wrap communication test failed. 709-255 709-271 709-272 709-273 709-274 D D D D D 709-275 709-281 709-282 709-283 709-481 709-482 D D D D D D 368 Diagnostic Information for Multiple Bus Systems . Description: The data wrap communication test failed.) Description: Could not perform because the device driver detected a hardware error. Description: The modem control line test failed. D D D D D D D D D D D D Failing Function Codes 259 259 259 263 263 261 261 261 709 837 709 837 709 837 709 684 709 684 709 837 709 837 709 837 709 684 709 684 709 837 709 837 709 837 D56 D56 Description and Action (Unless otherwise indicated. Description: The modem control line test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: Could not perform because the device driver detected a hardware error. use Chapter 11. Diagnostics: The data wrap communications test failed while running the Printer/Terminal cable wrap test. Diagnostics: The data wrap communications test failed while running the Remote Async Node wrap test. Diagnostics: Cannot run the test because the device driver detected a hardware error while running the Printer/Terminal cable wrap test. Description: The modem control line test failed. Description: Could not perform because the device driver detected a hardware error. Description: Could not do the test because the device driver detected a hardware error. Description: Could not perform because the device driver detected a hardware error. Description: The data wrap communications test failed. Description: The data wrap communication test failed.Service Request Number 709-171 709-172 709-173 709-174 709-175 709-181 709-182 709-183 709-251 709-252 709-253 709-254 SRN Src. Description: The data wrap communication test failed. Description: Could not perform because the device driver detected a hardware error.

Description: The electronics card test failed. use MAP 210 with a FFC of 709. use MAP 210 with a FFC of 709. Description: A SCSI busy or command error. diagnostic software.Service Request Number 709-483 709-901 to 709-920 SRN Src. Description: The motor failed to restart. D D Failing Function Codes D56 software 709 Description and Action (Unless otherwise indicated. suspect a software problem. Description: The diagnostic test failed. Description: The media format is corrupted. If you do not find a problem. otherwise. suspect a software problem. 709-921 709-922 to 709-924 D D 709 software software 709 709-925 709-926 to 709-943 D D 709 software software 709 721-102 721-104 721-105 721-106 721-108 721-110 721-112 721-114 721-116 D D D D D D D D D 721 721 721 721 721 721 721 721 721-117 721-118 721-120 721-122 D D D D 721 721 B88 721 721 Description: A write-protect error occurred. and application software to be sure they are all compatible. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Description: An unrecoverable media error occurred. Description: The bus test failed. Description: An unexpected error occurred that can be attributed to software or hardware. Description: A SCSI command time-out occurred. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Action: Run diagnostics from a source other than from the disk or a network. Description: An unexpected error occurred that can be attributed to software or hardware. Description: A protocol error. Description: An unrecoverable hardware error. otherwise. SRNs 700-102 through 89c-302 369 . Action: Check the levels of the device. call your support person. otherwise. Description: A SCSI reservation conflict error. suspect a software problem. Action: Run diagnostics from a source other than from the disk or a network. use Chapter 11. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. use MAP 210 with a FFC of 709. Description: The adapter failed to configure Description: An unexpected error occurred that can be attributed to software or hardware. adapter. Chapter 32. “MAP 0210: General Problem Resolution” on page 67. Description: The adapter failed to configure. Action: Run diagnostics from a source other than from the disk or a network.) Description: The modem control line test failed. Description: The drive did not become ready.

721-136 721-137 D D Description: The certify operation failed. Description: Error log analysis indicates a SCSI bus problem. Description: The Read. use Chapter 11. Description: The Load command failed. Description: Unit attention condition has occurred on the Send Diagnostic command. “MAP 0210: General Problem Resolution” on page 67. Description: The device failed to configure.) Description: A SCSI check condition error occurred. or the Inquiry command failed. Description: The Mode Select command failed. Description: The adapter failed to configure. Description: The error log analysis indicates a hardware failure. D 370 Diagnostic Information for Multiple Bus Systems . 722-xxx 723-xxx 724-xxx 733-110 to 733-120 733-130 to 733-135 733-140 733-150 to 733-169 733-170 D D D D D 733 media 733 733 media 733 B88 media 733 media 733 D D D 733-180 to 733-185 733-190 D Description: The Load command failed. Description: The Mode Select command failed. Description: A software error was caused by a hardware failure. or the Unload command failed. Description: Unknown disk drive type is failing. or the Unload command failed. 721-130 721-132 721-134 721-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: The Reserve command failed. or the Send Diagnostic command failed. Description: A disk drive hardware error occurred. Description: Unknown CD-ROM type is failing. Description: Unknown tape drive failure.Service Request Number 721-124 721-126 721-128 721-129 SRN Src. D D G G Failing Function Codes 721 721 B88 721 190 721 B88 software 721 721 B88 software 721 B88 software 721 721 B88 190 722 723 724 733 Description and Action (Unless otherwise indicated. Description: The Test Unit Ready command failed. Write and Compare test failed.

or bus I/O error occurred. Description: SCSI adapter configuration failed. Description: Unable to do configuration. Description: Unable to reserve device. Description: An adapter. Description: The CD-ROM drive indicates an error. Description: 140 GB 8 mm tape drive failed. D D D D D D D D D D D D D D Chapter 32. 733-320 733-411 to 733-423 733-511 to 733-523 733-611 to 733-723 734-111 734-112 734-113 734-121 734-122 734-123 734-125 734-126 734-127 734-128 734-129 734-150 734-151 G D Description: Error log analysis indicates a failure. Description: A media error was detected. Description: A command timeout was detected. D Description: The drive returned bad or non-extended sense data. “MAP 0210: General Problem Resolution” on page 67. Description: The device configuration failed. SRNs 700-102 through 89c-302 371 .) Description: The Test Unit Ready command failed. device. Description: The CD-ROM drive indicates an error. D D D Failing Function Codes 733 media 733 B88 733 Description and Action (Unless otherwise indicated. Description: The CD-ROM drive indicates an error. Description: A reservation conflict occurred. D D 733 software B88 733 software 733 media 733 B88 software 733 B88 733 B88 software 734 B88 734 B88 734 B88 734 734 734 734 B88 734 734 734 734 Test Disc 734 734 B88 Description: The device configuration failed. Description: Unable to open the device driver. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error. use Chapter 11.Service Request Number 733-200 733-210 733-220 to 733-240 733-300 733-310 SRN Src.

Description: Undefined error detected. Description: The keyboard layout ID test failed. Description: An unexpected device or adapter error occurred. Description: An unexpected adapter error occurred. Description: The keyboard light-off test failed. 372 Diagnostic Information for Multiple Bus Systems . Description: The LED test failed. Description: Unknown keyboard. D D D D D D D D D D G G D D D D D D D D D D D D D D D Failing Function Codes 734 734 734 734 734 734 734 B88 734 734 734 734 734 B88 821 736 821 736 821 736 736 821 736 821 821 736 821 736 821 736 736 821 736 821 821 736 821 736 Description and Action (Unless otherwise indicated. Description: An unexpected device or adapter error occurred. Description: An unexpected adapter error occurred. Description: Undefined error detected. Description: The read keyboard ID test failed. Description: The CD-ROM drive indicates an error.) Description: A command reservation conflict was detected. Description: The CD-ROM drive indicates an error. Description: The keyboard reset failed. Description: The select scan code set test failed. Description: The keyboard light-on test failed. “MAP 0210: General Problem Resolution” on page 67. Description: Errors found during ELA. Description: Unable to reserve device. Description: Unable to open device driver. Description: An error occurred in turning on the lamps. Description: No tone during audio test. Description: Errors found during ELA. Description: Unable to do configuration.Service Request Number 734-152 734-162 734-171 734-172 734-173 734-175 734-198 734-199 734-211 734-281 734-301 734-302 736-101 736-102 736-103 736-104 736-105 736-106 736-201 736-202 736-203 736-204 736-205 736-206 736-301 736-302 736-303 SRN Src. Description: An unexpected adapter error occurred. use Chapter 11. Description: The keyboard echo test failed. Description: An unexpected device or adapter error occurred.

Action: Check the levels of the device. Description: An unexpected adapter error occurred. SRNs 700-102 through 89c-302 373 . Description: Error configuring the device. 741-130 741-132 741-134 G D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. 741 741 B88 741 Description: A write-protect error occurred.Service Request Number 736-304 736-401 736-402 736-403 736-404 736-701 736-901 736-902 736-903 741-102 to 741-114 741-116 SRN Src. Chapter 32. If you do not find a problem.) Description: An error occurred in turning off the lamps. Description: The error log analysis indicates an adapter failure. Description: Error log analysis indicates a SCSI bus problem. Description: SCSI disk drive problems. “MAP 0210: General Problem Resolution” on page 67. Description: The keyboard is failing. Description: The error log analysis indicates a device failure. 741-117 741-118 741-120 to 741-124 741-126 741-128 741-129 D D D D G G 741 B88 741 190 741 B88 software 741 741 B88 software Description: A software error was caused by a hardware failure. adapter. Description: SCSI disk drive problems. D Description: A protocol error. use Chapter 11. Description: The adapter failed to configure. Description: The error log analysis indicates an unknown failure. diagnostic software. Description: An unexpected device or adapter error occurred. Description: A disk drive hardware error occurred. Description: The error log analysis indicates a hardware failure. call your support person. Description: A SCSI command timeout. D D D D D D G G G D Failing Function Codes 736 821 736 821 736 736 821 736 821 821 736 821 736 821 741 Description and Action (Unless otherwise indicated. Description: Unable to recognize the keyboard. and application software to be sure they are all compatible.

741-137 D Description: Unit attention condition has occurred on the Send Diagnostic command. Description: 10 Base-T transceiver test failed. Description: Internal loopback test failed. Description: I/O register test failed. Description: 10Base-2 transceiver test failed. Description: Error log analysis indicates a hardware problem. Description: 10Base-T transceiver test failed. Description: External loopback test failed. use Chapter 11. Description: I/O register test failed.Service Request Number 741-135 SRN Src. Description: Device configuration failed. Description: I/O register test failed. Description: Internal loopback test failed. Description: Configuration register test failed. “MAP 0210: General Problem Resolution” on page 67. Description: Internal loopback test failed. Description: Device configuration failed. D Failing Function Codes 741 B88 software 741 B88 190 742 742 742 742 742 D59 D59 D59 D59 D59 D60 D60 D60 D60 B08 B09 742 software D59 software B08 D59 B09 D59 D60 software 742 software D59 software D60 software media 745 Description and Action (Unless otherwise indicated. Description: 10 Base-2 transceiver test failed. Description: Configuration register test failed.) Description: The device failed to configure. Description: Internal loopback test failed. Action: No action required. Description: Configuration register test failed. 742-101 742-102 742-104 742-105 742-106 742-121 742-122 742-124 742-125 742-126 742-141 742-142 742-144 742-145 742-160 742-161 742-203 742-223 742-224 742-225 742-243 742-700 742-720 742-740 745-100 D D D D D D D D D D D D D D D D D D D D D G G G D 374 Diagnostic Information for Multiple Bus Systems . Description: Device configuration failed. Description: Internal loopback test failed. Description: Error log analysis indicates a hardware problem. Description: Internal loopback test failed. Description: Recovered error. Description: Error log analysis indicates a hardware problem. Description: External loopback test failed.

refer to the tape autoloader service guide. Description: Blank Media Action: Check media. replace media. clean rollers. refer to the tape autoloader service guide. Description: Magazine Movement Failure Action: Check magazine and media. refer to the tape autoloader service guide. Description: Drawer Open/Close Failure Action: Check magazine and media. refer to the tape autoloader service guide. Action: Install media. refer to the tape autoloader service guide. replace media. media changed.) Description: Drive Not Ready. Description: Illegal request to drive Action: Software conflict. Action: Replace drive. Description: 4mm Tape Auto Loader problem. use Chapter 11. refer to the tape autoloader service guide. refer to the tape autoloader service guide. Action: Replace media. refer to the tape autoloader service guide. D D Failing Function Codes media 745 media 745 745 magazine media 745 media 745 SCSI Adapter 745 media 745 environment media clean media drive 745 magazine media 745 magazine media 745 magazine media 745 system 745 system 745 media 745 media Description and Action (Unless otherwise indicated. clean drive. Description: Media Insert/Eject Failure Action: Check clean magazine and media. refer to the tape autoloader service guide. refer to the tape autoloader service guide. refer to the tape autoloader service guide. clean rollers. refer to the tape autoloader service guide. Description: Drive Requires Cleaning Action: Clean drive. D 745-410 to 745-435 745-440 D D 745-441 to 745-443 745-444 D D 745-445 D 745-460 to 745-465 745-470 to 745-475 745-480 to 745-485 745-500 745-600 D D D D D 745-700 745-800 D D Chapter 32. Action: Replace media. Description: Not Writeable Action: Check media for write-protect. Description: SCSI Hardware Failure. refer to the tape autoloader service guide. Description: Unit Attention Action: Software conflict. clean drive. refer to the tape autoloader service guide.Service Request Number 745-200 745-300 to 745-350 745-400 SRN Src. Action: Replace drive. Description: Internal Hardware Failure Action: Replace drive. “MAP 0210: General Problem Resolution” on page 67. SRNs 700-102 through 89c-302 375 . refer to the tape autoloader service guide. Description: General Hardware Failure. Description: 4mm Tape Auto Loader problem. Description: Humidity too High Action: Lower humidity.

Description: Enhanced error handling failure on the adapter. Description: Error during the write/read of the memory register. Action: Go to Chapter 8. Description: SCSI FIFO flags error. Description: Adapter POST failed. Action: Go to Chapter 8. Description: SCSI FIFO underflow. Action: Go to Chapter 8. “MAP 0050: SCSI Bus Problems” on page 51. “MAP 0050: SCSI Bus Problems” on page 51. Description: FIFO full bit clear. Action: Go to Chapter 8. Description: FIFO full bit set.) Description: SCSI Interface Failure Action: Check SCSI interface. Description: SCSI wrap or PTC failure. Description: Arbitration test failed. use Chapter 11. “MAP 0050: SCSI Bus Problems” on page 51. Description: FIFO data miscompare. Description: Function could not complete. Description: No terminal power. 376 Diagnostic Information for Multiple Bus Systems . “MAP 0050: SCSI Bus Problems” on page 51. Description: SCSI configuration register read or write error. Description: Enhanced error handling failure on a PCI-PCI Bridge. Description: Tape Full Action: Check replace media. Description: Miscompare during the write/read of the configuration register. 745-D00 746-101 746-102 746-103 746-212 746-213 746-214 746-215 746-216 746-217 746-218 746-219 746-220 746-221 746-222 746-223 D D D D D D D D D D D D D D D D 746-224 746-225 746-226 746-227 746-230 746-231 746-232 746-240 D D D D D D D D 746 221 746 746 221 Description: SCSI adapter test failure. Description: FIFO empty bit set. D Failing Function Codes 745 SCSI Adapter 745 media 221 293 746 221 746 746 746 746 746 746 746 746 746 746 221 746 746 Description and Action (Unless otherwise indicated. Action: Go to Chapter 8. refer to the tape autoloader service guide. Description: Miscompare during the write/read of the memory I/O register. “MAP 0050: SCSI Bus Problems” on page 51. Description: SCSI FIFO data miscompare. “MAP 0050: SCSI Bus Problems” on page 51. “MAP 0210: General Problem Resolution” on page 67. Description: SCSI parity error. refer to the tape autoloader service guide. Description: FIFO empty bit clear. Description: Enhanced error handling failure on the bus.Service Request Number 745-B00 SRN Src. Action: Go to Chapter 8. Description: SCSI bus data miscompare.

Description: Enhanced error handling failure on a PCI-PCI Bridge. Action: Run the diagnostics on the adapter in System Verification mode. Description: FIFO data miscompare.) Description: SCSI bus error. Action: Go to Chapter 8. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. If an SRN is reported. Description: Error log analysis indicates that multiple SCSI bus errors have occurred. Description: SCSI parity error. “MAP 0050: SCSI Bus Problems” on page 51. Description: Error log analysis indicates a PCI SCSI adapter failure. Chapter 32. Description: FIFO empty bit clear. D D G G Failing Function Codes Description and Action (Unless otherwise indicated. Description: Miscompare during the write/read of the configuration register.Service Request Number 746-242 746-301 746-701 746-801 SRN Src. Description: FIFO empty bit set. If an SRN is reported. 746-802 G 746-803 G 747-101 747-102 747-103 747-212 747-213 747-214 747-215 747-216 747-217 747-218 747-219 747-220 747-221 D D D D D D D D D D D D D 221 293 747 221 747 747 747 747 747 747 747 747 747 747 221 Description: Enhanced error handling failure on the bus. 746 221 746 Description: The parent device open failed. Description: SCSI FIFO underflow. use the SRN to resolve the problem. SRNs 700-102 through 89c-302 377 . “MAP 0210: General Problem Resolution” on page 67. Description: FIFO full bit set. use Chapter 11. If an SRN is not reported. Description: SCSI FIFO data miscompare. Action: Run the diagnostics on the adapter in System Verification mode. Description: SCSI FIFO flags error. Description: Error log analysis indicates a terminator problem. If an SRN is not reported. Action: Run the diagnostics on the adapter in System Verification mode. Description: Enhanced error handling failure on the adapter. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. use the SRN to resolve the problem. If an SRN is reported. Description: Error log analysis indicates that multiple attempts to reset the SCSI bus have timed out. use the SRN to resolve the problem. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. If an SRN is not reported. Description: FIFO full bit clear.

“MAP 0210: General Problem Resolution” on page 67. Action: Go to Chapter 8. Description: Function could not complete. Description: Error log analysis indicates a terminator problem. If an SRN is reported. “MAP 0050: SCSI Bus Problems” on page 51. 747-224 747-225 747-226 747-227 747-230 747-231 747-232 747-240 747-242 747-301 747-701 747-801 D D D D D D D D D D G G 747 221 747 747 221 Description: SCSI adapter test failure.) Description: Error during the write/read of the memory register. “MAP 0050: SCSI Bus Problems” on page 51. If an SRN is not reported. Action: Run the diagnostics on the adapter in System Verification mode. “MAP 0050: SCSI Bus Problems” on page 51. Action: Go to Chapter 8. Description: Miscompare during the write/read of the memory I/O register. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. Action: Run the diagnostics on the adapter in System Verification mode. Action: Go to Chapter 8. Action: Go to Chapter 8. “MAP 0050: SCSI Bus Problems” on page 51. Description: SCSI wrap or PTC failure. Description: Error log analysis indicates a PCI SCSI adapter failure. Action: Go to Chapter 8. “MAP 0050: SCSI Bus Problems” on page 51. Description: SCSI bus error. If an SRN is reported. Description: Adapter POST failed. Description: Error log analysis indicates that multiple attempts to reset the SCSI bus have timed out. 747-802 G 378 Diagnostic Information for Multiple Bus Systems . use the SRN to resolve the problem. use the SRN to resolve the problem. Description: SCSI configuration register read or write error. Action: Go to Chapter 8. Description: SCSI bus data miscompare. “MAP 0050: SCSI Bus Problems” on page 51. “MAP 0050: SCSI Bus Problems” on page 51. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. If an SRN is not reported.Service Request Number 747-222 747-223 SRN Src. 747 221 747 Description: The parent device open failed. Description: No terminal power. Action: Go to Chapter 8. use Chapter 11. Description: Arbitration test failed. D D Failing Function Codes 747 747 Description and Action (Unless otherwise indicated.

Description: Config register test failed. “MAP 0210: General Problem Resolution” on page 67. Refer to service documentation for this device.) Description: Error log analysis indicates that multiple SCSI bus errors have occurred. G Failing Function Codes Description and Action (Unless otherwise indicated. 750-403 D Token-ring initialization test failure. 750-401 D Token-ring internal wrap test failure. Action: Run the diagnostics on the adapter in System Verification mode. 749-xxx 750-100 750-200 750-201 750-202 750-300 D D D D D D 749 750 750 221 750 221 750 221 256 750 221 256 750 221 256 750 221 256 750 221 240 256 750 221 240 256 750 221 240 256 750 221 240 256 750 221 Description: 7331 Model 205 Tape Library. 750-303 D Description: Token-ring initialization test failure. Description: The adapter open test failed. SRNs 700-102 through 89c-302 379 . If an SRN is reported. Description: I/O register test failed. use the SRN to resolve the problem. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. If an SRN is not reported. 750-302 D Description: Token-ring external wrap failure. Description: The connect test failed. 750-301 D Description: Token-ring internal wrap test failure. 750-400 D Description: The connect test failed. Chapter 32. 750-402 D Token-ring external wrap test failure. use Chapter 11. Description: Adapter self-test failed.Service Request Number 747-803 SRN Src.

“MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Action: Go to Chapter 18. Description: The POST indicates an adapter channel failure. Description: Enhanced error handling failure on the bus. Description: The POST indicates a disk failure. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: POST indicates cache failure 751-102 D 751-103 D 751 751-104 751-105 751-106 D D D 190 B3A 722 751-108 751-109 D D 221 751 751-110 D 722 751-111 D 722 751-112 G 722 751-113 G 722 751-114 G E29 751-115 G E30 751-116 751-117 D D 751 E29 380 Diagnostic Information for Multiple Bus Systems . Description: The disk reported a Predictive Failure Analysis error (PFA). Description: The POST indicates an adapter failure. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: The disk drive has been failed by the adapter. “MAP 0210: General Problem Resolution” on page 67. G D Failing Function Codes 750 221 751 227 751 Description and Action (Unless otherwise indicated. Description: The POST indicates a defective backplane or external enclosure. Action: Go to Chapter 18. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Action: Go to Chapter 18. Description: ELA indicates that the disk reported a hard data error. Action: Go to Chapter 18. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: ELA indicates a cache failure. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Action: Go to Chapter 18.Service Request Number 750-700 751-101 SRN Src.Action: Go to Chapter 18. Description: The POST indicates a defective cable. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: Failed to disable data scrub. Description: ELA indicates that the cache battery is either low on power or has failed. Description: The NVRAM test indicates an adapter failure. Action: Go to Chapter 18. use Chapter 11. Description: ELA indicates that the disk reported a hard equipment error. Action: Go to Chapter 18. Action: Go to Chapter 18. Action: Go to Chapter 18. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103.) Description: Error Log analysis indicated a hardware failure. Description: The PCI wrap test failed. Action: Go to Chapter 18.

Description: NVRAM test indicates that write cache is missing. Action: Go to Chapter 18. SRNs 700-102 through 89c-302 381 . Write and Compare test failed. Description: The Unload command failed. Description: NVRAM test indicates cache battery failure. Description: NVRAM test indicates that cache size is invalid. use Chapter 11. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Action: Go to Chapter 18. D D Failing Function Codes E29 E29 Description and Action (Unless otherwise indicated. Description: Enhanced error handling failure on adapter. Description: The Send Diagnostic command failed. Action: Go to Chapter 18. Description: The Reserve command failed.) Description: NVRAM test indicates cache failure. Description: The Load command failed. 751-120 D E29 751-121 D E30 751-122 D E30 751-123 D 751 751-124 751-125 751-400 D D F 221 751 221 751 190 B3A 722 751 221 757 757 757 media 757 media 757 757 media 757 media 757 media 757 B88 media 751-701 757-110 757-120 757-130 757-135 757-140 757-150 757-160 757-169 757-170 G D D D D D D D D D Chapter 32. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: ELA indicates an adapter failure. “MAP 0210: General Problem Resolution” on page 67. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: The Inquiry command failed. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103. Description: The Test Unit Ready command failed. Description: POST indicates a channel failure. Description: The Mode Select command failed. Description: The Read. Action: Go to Chapter 18. Description: NVRAM test indicates that the cache battery is low on power. Description: Error Log Analysis indicates an EEH error. Description: The Send Diagnostic command failed. Action: Go to Chapter 18.Service Request Number 751-118 751-119 SRN Src. Description: Enhanced error handling failure on PCI-PCI Bridge. Action: Go to Chapter 18. “MAP 0270: SCSI RAID Problem Resolution and Verification” on page 103.

757-320 757-411 to 757-423 757-511 to 757-523 757-611 to 757-623 757-711 to 757-723 763-1xx D D Description: Error log analysis indicates a failure. The wrap plug FRU part number is listed under the 763 FFC. Description: The Request Sense command failed. 763-200 to 763-299 D 382 Diagnostic Information for Multiple Bus Systems . Description: The Release command failed. Description: A reservation conflict occurred. D Description: Problem detected with a device or device data corrupted. 2. Description: The Openx command failed. Description: The Mode Select command failed. Description: The device configuration failed. use Chapter 11. D D D D D D D D D D Failing Function Codes 757 media 757 media 757 757 media 757 B88 757 757 757 757 software B88 757 software 757 media 757 B88 software 757 B88 757 B88 software 757 B88 software 763 software 221 ext clock 763 wrap plug Description and Action (Unless otherwise indicated. Description: An adapter or bus I/O error occurred. Description: The Unload command failed. Description: Problem detected with the external clock (SP switch). Note: You may need to reinstall ssp. Description: The device configuration failed.) Description: The Load command failed. Refer to your SP Maintenance Information manual for the external clock FRU part number. D D Description: A device timeout error occurred. Description: The Test Unit Ready command failed.Service Request Number 757-180 757-185 757-190 757-200 757-210 757-220 757-230 757-240 757-300 757-310 SRN Src. Description: SCSI adapter configuration failed. “MAP 0210: General Problem Resolution” on page 67.css software. Notes: 1. D Description: The drive returned bad or non-extended sense data.

Note: The terminator FRU part number is listed under the 763 FFC. Refer to your SP Maintenance Information manual for the switch cable FRU part number. Notes: 1. D 764 221 Description: Problem detected with the POS registers. Chapter 32.Service Request Number 763-2A0 to 763-2A9 763-3xx 763-4xx 763-5xx 763-6xx 763-7xx 763-8xx 763-9xx SRN Src. Description: TBIC test failed. 2. Description: Card wrap test failed. Description: DMA engine test failed. Description: Microprocessor test failed.) Description: Problem detected with the internal clock. use Chapter 11. Description: FIFO test failed. Note: Refer to your SP Maintenance Information manual for the switch cable FRU part number.css software. Notes: 1. 2. The wrap plug FRU part number is listed under the 763 FFC. Note: You may need to reinstall ssp. D Failing Function Codes 763 Description and Action (Unless otherwise indicated. The wrap plug FRU part number is listed under the 763 FFC. Description: SRAM test failed. D D D D D D D 763 221 763 software 763 763 763 763 763 221 Switchcable 763 terminator Switchcable wrap plug Description: Problem detected with the POS registers. Description: Problem detected with the external clock (SP switch). Description: Problem detected with a device or device data corrupted. Description: Card wrap test failed. Refer to your SP Maintenance Information manual for the external clock FRU part number. SRNs 700-102 through 89c-302 383 . “MAP 0210: General Problem Resolution” on page 67. Description: Interrupt test failed. 764-200 to 764-299 D 764-2A0 to 764-2A9 764-3xx D 764 Description: Problem detected with the internal clock. (except for SRN 763-282) Action: Replace the SP Switch MX Adapter. 763-Ax3 D 763-Ax4 D 763-xx2 764-1xx D D 763 764 software 221 ext clock 764 wrap plug Description: Bad adapter card.

Description: The electronics card test failed. Description: Microprocessor test failed. Description: FIFO test failed. Description: A SCSI busy or command error. Description: DMA engine test failed. 2. Note: The terminator FRU part number is listed under the 763 FFC. adapter. The wrap plug FRU part number is listed under the 763 FFC. 772-117 772-118 772-120 772-122 772-124 D D D D D 772 772 B88 772 772 772 Description: A write-protect error occurred. Refer to your SP Maintenance Information manual for the switch cable FRU part number. Description: Card wrap test failed. use Chapter 11. and application software to be sure they are all compatible. If you do not find a problem. “MAP 0210: General Problem Resolution” on page 67. D D D D D D Failing Function Codes 764 software 764 764 764 764 764 221 switchcable 764 terminator Switchcable wrap plug Description and Action (Unless otherwise indicated. Description: SRAM test failed. Description: The drive did not become ready. Description: Card wrap test failed. (except for SRN 764-282) Action: Replace the SP Switch MX Adapter. Action: Check the levels of the device. Notes: 1.Service Request Number 764-4xx 764-5xx 764-6xx 764-7xx 764-8xx 764-9xx SRN Src. Description: Interrupt test failed. Description: A protocol error. diagnostic software. 384 Diagnostic Information for Multiple Bus Systems . Description: The diagnostic test failed. Description: The bus test failed. call your support person. Description: A SCSI command time-out.) Description: TBIC test failed. Description: The media format is corrupted. Description: A SCSI reservation conflict error. Description: An unrecoverable media error. Description: The motor failed to restart. Description: A SCSI check condition error. Description: An unrecoverable hardware error. Note: Refer to your SP Maintenance Information manual for the switch cable FRU part number. 764-Ax3 D 764-Ax4 D 764-xx2 772-102 772-104 772-105 772-106 772-108 772-110 772-112 772-114 772-116 D D D D D D D D D D 764 772 772 772 772 772 772 772 772 Description: Bad adapter card.

Description: The media format is corrupted. adapter. Description: An unrecoverable hardware error. Description: A protocol error. Description: The bus test failed. 772-136 772-137 D D Description: The certify operation failed. D G G Failing Function Codes 772 B88 772 190 772 B88 software 772 772 B88 software 772 B88 software 772 772 B88 190 773 773 773 773 773 773 773 773 Description and Action (Unless otherwise indicated. Description: The electronics card test failed. Description: A software error was caused by a hardware failure. Description: The drive did not become ready. use Chapter 11. Action: Check the levels of the device. Description: A disk drive hardware error occurred. and application software to be sure they are all compatible. diagnostic software.Service Request Number 772-126 772-128 772-129 SRN Src. Description: Error log analysis indicates a SCSI bus problem. Description: The device failed to configure. Description: A SCSI command time-out. Description: The adapter failed to configure. Description: A SCSI busy or command error. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: A SCSI check condition error. SRNs 700-102 through 89c-302 385 . Description: A SCSI reservation conflict error. Description: The diagnostic test failed. If you do not find a problem. Description: The error log analysis indicates a hardware failure. call your support person. Description: An unrecoverable media error. Chapter 32.) Description: A software error was caused by a hardware failure. “MAP 0210: General Problem Resolution” on page 67. 773-102 773-104 773-105 773-106 773-108 773-110 773-112 773-114 773-116 D D D D D D D D D 773-117 773-118 773-120 773-122 773-124 773-126 D D D D D D 773 773 B88 773 773 773 773 B88 Description: A write-protect error occurred. 772-130 772-132 772-134 772-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: The motor failed to restart.

diagnostic software. G G Failing Function Codes 773 190 773 B88 software 773 773 B88 software 773 B88 software 773 773 B88 190 774 774 774 774 774 774 774 774 Description and Action (Unless otherwise indicated. Description: Error log analysis indicates a SCSI bus problem. 773-130 773-132 773-134 773-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. call your support person. Description: An unrecoverable hardware error. Description: Unit attention condition has occurred on the Send Diagnostic command. 773-136 773-137 D D Description: The certify operation failed. Description: The diagnostic test failed. Description: The adapter failed to configure. and application software to be sure they are all compatible. Description: A software error was caused by a hardware failure. Description: The media format is corrupted.Service Request Number 773-128 773-129 SRN Src. Description: A SCSI check condition error. Description: The motor failed to restart. Description: A SCSI command time-out. Description: The drive did not become ready. Description: An unrecoverable media error. Description: A SCSI reservation conflict error. Description: A protocol error. Action: Check the levels of the device. 386 Diagnostic Information for Multiple Bus Systems . Description: The error log analysis indicates a hardware failure. Description: A SCSI busy or command error. Description: The bus test failed. adapter. Description: The electronics card test failed. Description: The device failed to configure. 774-102 774-104 774-105 774-106 774-108 774-110 774-112 774-114 774-116 D D D D D D D D D 774-117 774-118 774-120 774-122 774-124 774-126 774-128 D D D D D D G 774 774 B88 774 774 774 774 B88 774 Description: A write-protect error occurred. If you do not find a problem. Description: A disk drive hardware error occurred. use Chapter 11.) Description: The error log analysis indicates a hardware failure. “MAP 0210: General Problem Resolution” on page 67.

774-136 774-137 D D Description: The certify operation failed. Description: MALLOC_ERROR Description: Loop count value in rules file is zero. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: Clipping error.Service Request Number 774-129 SRN Src. Description: A disk drive hardware error occurred. use Chapter 11. Description: Rectangle fill test failed. Description: ″NO″ to color panel 775-001 D 775-002 775-007 775-009 775-064 775-101 775-102 775-103 775-128 775-161 775-191 775-193 775-1FF 775-201 D D D D D D D D D D D D D Description: ″NO″ to cursor panel Description: The EMC_SCROLLING_17_H_TEST failed Description: The EMC_SCROLLING_21_H_TEST failed Description: TRIO64V+_TIMEOUT Description: Color miscompare.) Description: Error log analysis indicates a SCSI bus problem. SRNs 700-102 through 89c-302 387 . 774-130 774-132 774-134 774-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: The device failed to configure. Chapter 32. G Failing Function Codes 190 774 B88 software 774 774 B88 software 774 B88 software 774 774 B88 190 775 227 Monitor 775 Monitor Info code Info code 775 227 775 227 775 227 775 227 software 775 software 775 227 775 227 775 227 775 227 Description and Action (Unless otherwise indicated. Description: Rectangle fill test failed. “MAP 0210: General Problem Resolution” on page 67. Description: Green screen error. Description: The adapter failed to configure. Description: Red screen error. Description: Color miscompare.

Description: A write of ″0x2A″ to the palette register failed. “MAP 0210: General Problem Resolution” on page 67. use Chapter 11. Description: The test of the palette registers failed. Description: The EMC_SCROLLING_21_H_TEST failed Description: Image transfer across Plane Test failed.Service Request Number 775-202 775-203 775-211 775-212 775-215 775-217 775-233 775-234 775-235 775-236 775-237 775-241 775-263 775-2FF 775-301 775-302 775-303 775-304 775-305 775-3FF 775-401 775-402 775-403 775-404 775-447 SRN Src. Description: A write of ″0x15″ to the palette register failed. Description: INTERNAL_ERROR_DATA_SIZE Description: INTERNAL_ERROR_NO_ACCESS Description: Black screen error Description: 9 x 7 Cross hatch grid failed.) Description: Clipping error. Description: A write of ″0x3F″ to the palette register failed. D D D D D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 775 227 775 227 software software 775 227 775 227 software software software software software Info code Info code 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 Description and Action (Unless otherwise indicated. 388 Diagnostic Information for Multiple Bus Systems . Description: VRAM inaccessible. Description: A write of ″0x00″ to the palette register failed. Description: Frame buffer base address inconsistent. Description: Miscompare found in VRAM. Description: The test of the palette registers failed. Description: Green screen error. Description: OPEN_RCM_ERROR Description: IOCTL_GSC_HANDLE_FAILED Description: AIXGSC_MAKE_GP_FAILED Description: AIXGSC_UNMAKE_GP_FAILED Description: DEVICE_BUSY_ERROR Description: The SCROLLING_17_H_TEST failed. Description: The test of the VRAM failed. Description: Image transfer across Plane Test failed.

Description: 315 Degree Short Stroke Draw failed Description: Short Stroke Vector Function test failed. Description: White screen error.) Description: Blue Screen error. Chapter 32. Description: Video Stream Register test failed. or 180 Degree Short Stroke Draw failed. Description: 0 Degree Short Stroke Draw failed. Description: The SCROLLING_17_H_TEST failed. use Chapter 11. Description: Color miscompare. Description: The SCROLLING_21_H_TEST failed. or 90 Degree Short Stroke Draw failed. Description: Video Stream hardware test failed. SRNs 700-102 through 89c-302 389 . Description: 45 Degree Short Stroke Draw failed. Description: 9 x 7 Cross hatch grid failed. Description: 135 Degree Short Stroke Draw failed. Description: 11 x 9 Cross hatch grid failed. “MAP 0210: General Problem Resolution” on page 67. Description: Direct Frame Buffer test failed.Service Request Number 775-449 775-471 775-473 775-495 775-497 775-4FF 775-501 775-502 775-503 775-5FF 775-601 775-602 775-6FF 775-701 775-702 775-703 775-704 775-705 775-706 775-707 775-708 775-709 SRN Src. D D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 775 227 775 227 775 227 Info code Info code 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 Description and Action (Unless otherwise indicated. Description: 225 Degree Short Stroke Draw failed. Description: Blue Screen error. Description: The test of the VRAM failed. Description: Clipping error. Description: Video Stream hardware test failed. Description: 270 Degree Short Stroke Draw failed. Description: Direct Frame Buffer test failed.

Description: Short Stroke Vector Function test failed. Description: Clipping for PatBlt Across screen failed. Description: Color for PatBlt Across screen failed. 775-801 775-802 775-803 775-804 775-805 775-8FF 775-901 775-902 775-903 775-904 775-905 775-906 775-907 775-908 775-909 775-937 D D D D D D D D D D D D D D D D Description: Color for PatBlt thru screen failed. Description: Bad vector detected. D D D D D Failing Function Codes 775 227 Info code Info code 775 227 software 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 Description and Action (Unless otherwise indicated. Description: Clipping miscompare of white boxes detected. use Chapter 11. Description: Color miscompare of white boxes detected. 390 Diagnostic Information for Multiple Bus Systems . Description: Pattern Fill Across the Plane test failed. Description: Color miscompare of white boxes detected. “MAP 0210: General Problem Resolution” on page 67.) Description: 11 x 9 Cross hatch grid failed. Description: Clipping error of white boxes detected. Description: The Area fill test (color bars) failed. Description: Color miscompare of white boxes detected. Description: Pattern Fill Across the Plane test failed. Description: The EMC_SCROLLING_17_H_TEST failed. Description: Clipping error of white boxes detected. Description: Clipping error of white boxes detected. Description: Clipping for PatBlt thru screen failed.Service Request Number 775-727 775-750 775-753 775-7FE 775-7FF SRN Src. Description: The SCROLLING_21_H_TEST failed. Description: Red screen error. Description: Color miscompare of color bars detected.

Description: Color miscompare of horizontal center line. Chapter 32. Description: Color miscompare of vertical left line. Description: Line Drawing Function test failed. Description: Clipping error of textured top line. D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 Description and Action (Unless otherwise indicated. Description: Clipping error of horizontal bottom line. SRNs 700-102 through 89c-302 391 . Description: Color miscompare of horizontal bottom line. Description: Clipping error of horizontal top line. Description: Reserved Description: Reserved Description: Color miscompare of textured top line. Description: Clipping error of horizontal center line. Description: Clipping error of vertical right line.) Description: White screen error. Description: Clipping error of vertical left line.Service Request Number 775-959 775-961 775-9FF 775-A01 775-A02 775-A03 775-A04 775-A05 775-A06 775-A07 775-A08 775-A09 775-A0A 775-A0B 775-A0C 775-A0D 775-A0F 775-A10 775-A11 775-A12 775-AFF SRN Src. Description: Line Drawing Function test failed. Description: Color miscompare of horizontal top line. Description: Black screen error. Description: Clipping error of vertical center line. Description: The Area fill test (color bars) failed. “MAP 0210: General Problem Resolution” on page 67. Description: Color miscompare of vertical right line. Description: Color miscompare of vertical center line. use Chapter 11.

Description: Wrap Test Failure. Description: Adapter On-card Test Failure. Description: Clipped Area Horizontal clip miscompare (clip of background line wrong). Description: External Test Failure. Description: I/O Test Failure. Description: Rectangle Area Clip error detected. Description: The BIOS function test failed. 392 Diagnostic Information for Multiple Bus Systems . Description: The BIOS read failed.Service Request Number 775-B01 775-B02 775-B03 775-B04 775-B05 775-B06 775-B07 775-BFF 775-C01 775-C02 775-CFF 775-D01 775-DFF 776-101 776-102 776-103 776-104 776-105 776-106 776-106 776-107 776-108 776-201 776-202 SRN Src. Description: The clipping function test failed. Description: Wrap Test Failure. Description: The HW cursor function test failed. Description: The clipping function test failed. Description: Enhanced Error Handling failure on adapter.) Description: Rectangle Area Color miscompare detected. use Chapter 11. “MAP 0210: General Problem Resolution” on page 67. D D D D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 775 227 D46 240 776 776 221 776 D46 776 776 776 776 221 776 221 Description and Action (Unless otherwise indicated. Description: External Test Failure. Description: Clipped Area Horizontal color miscompare (background line color wrong). Description: The BIOS function test failed. Description: Clipped Area Vertical color miscompare (background line color wrong). Description: Clipped Area Vertical clip error (clip of background line wrong). Description: Wrap Test Failure. Description: Configuration Register Test Failure. Description: Enhanced Error Handling failure on bus. Description: The HW cursor function test failed. Description: EEH failure on Eads chip.

Description: External Test Failure.) Description: Wrap Test Failure. 776-306 D Description: Wrap Test Failure. Description: Wrap Test Failure. 776-303 F 776-304 D 776-305 D Description: Wrap Test Failure. Action: Run advanced diagnostics with wrap test for this resource to obtain correct problem isolation. Action: Run advanced diagnostics with wrap test for this resource to obtain correct problem isolation. 776-206 776-301 D D 776-302 F Description: External Test Failure. Description: External Test Failure. D D F Failing Function Codes D46 776 776 221 D46 776 776 221 D46 240 776 D46 776 221 240 D46 776 D46 776 221 D46 776 221 D46 776 221 240 D46 776 221 240 D46 776 221 240 D46 776 221 240 D46 776 221 Description and Action (Unless otherwise indicated. Chapter 32. 776-401 F Description: External Test Failure. Action: Run advanced diagnostics with wrap test for this resource to obtain correct problem isolation. 776-404 D 776-405 D Description: Wrap Test Failure. Description: Connect Test Failure. Action: Run advanced diagnostics with wrap test for this resource to obtain correct problem isolation. Description: External Test Failure. use Chapter 11. SRNs 700-102 through 89c-302 393 . Description: Connect Wrap Test Failure.Service Request Number 776-203 776-204 776-205 SRN Src. Description: Connect Test Failure. “MAP 0210: General Problem Resolution” on page 67. 776-406 D Description: Wrap Test Failure.

Description: Adapter initialization test failure. Description: Configuration Register Test Failure. “MAP 0210: General Problem Resolution” on page 67. Description: Wrap Test Failure. Description: Enhanced Error Handling logic failure. This failure occurs if not connected to a functional Token-Ring network. This failure occurs if not connected to a functional Token-Ring network. Action: Run advanced diagnostics for this resource to obtain correct problem isolation. Description: Internal wrap test failure. Description: ELA indicates a PCI bus failure occurred. Description: ELA indicates an adapter error occurred. Description: ELA indicates a Programmed I/O failure occurred. Description: Internal wrap test failure. Action: Run advanced diagnostics for this resource to obtain correct problem isolation. Action: Run advanced diagnostics for this resource to obtain correct problem isolation. Description: I/O Test Failure. Description: Enhanced Error Handling failure on bus.Service Request Number 776-414 SRN Src. Description: Wrap Test Failure. Description: ELA indicates an adapter check occurred. Description: Configuration Register Test Failure. 776-415 F 776-416 F 776-701 776-702 776-703 776-704 776-705 776-706 776-707 777-101 777-102 777-103 777-104 777-105 777-106 777-107 777-108 777-110 777-201 777-202 777-203 777-204 G G G G G G G D D D D D D D D D D D D D 394 Diagnostic Information for Multiple Bus Systems . Description: ELA indicates a command write failure occurred. This failure occurs if not connected to a functional Token-Ring network. F Failing Function Codes 240 D46 776 221 240 D46 776 221 240 D46 776 221 776 776 221 776 221 776 221 776 221 776 776 777 777 777 777 777 777 221 221 777 777 221 777 221 777 221 777 221 Description and Action (Unless otherwise indicated. Description: External wrap (100 Mbps) test failure. Description: Enhanced Error Handling failure on adapter. Description: ELA indicates an internal adapter error has occurred. Description: Adapter initialization test failure. use Chapter 11.) Description: Connect Test Failure. Description: ELA indicates a DMA failure occurred. Description: I/O Test Failure. Description: External wrap (10 Mbps) test failure.

Description: Error log analysis indicates that the adapter is not responding to initialization commands. Description: Error Log Analysis indicates that the device driver has detected a PIO error which it was unable to correct. Description: Software error. Description: Error Log Analysis indicates a problem with the EEPROM on the adapter Description: Error Log Analysis indicates that this adapter has failed to initialize due to EEH errors. use Chapter 11. Description: Adapter failure. Description: Adapter failure. Description: Software error. Description: Software error. Description: Software error. “MAP 0210: General Problem Resolution” on page 67. D D D D G G Failing Function Codes 777 221 777 221 777 221 777 221 777 221 777 221 777 221 777 221 777 221 software 778 software 778 software 778 software 778 software 778 778 software 778 221 software 778 software 778 778 software software 778 Description and Action (Unless otherwise indicated. Description: External wrap (100 Mbps) test failure. Description: Software error.Service Request Number 777-205 777-206 777-207 777-208 777-701 777-702 SRN Src. Description: Internal wrap test failure. Description: Software error.) Description: Internal wrap test failure. Description: Software error. 777-703 777-704 777-707 778-002 778-004 778-009 778-011 778-017 778-019 778-030 778-032 778-033 778-035 778-036 to 778-072 G G G D D D D D D D D D D D Chapter 32. Description: External wrap (10 Mbps) test failure. SRNs 700-102 through 89c-302 395 . Description: Error log analysis indicates that the adapter has been shut down due to an unrecoverable error. Description: Software error. Description: Adapter failure.

) Description: Adapter failure.Service Request Number 778-073 778-075 778-076 778-301 to 778-D02 778-E01 778-E02 to 778-1401 778-1402 778-1403 to 778-1405 778-1500 778-1600 to 778-1604 778-2501 to 778-2508 778-2509 to 778-2511 778-2601 to 778-2602 778-2603 77B-101 77B-102 77B-103 77B-104 77B-105 77B-106 77B-110 SRN Src. D Description: Software error. Description: Software error. Description: Adapter failure. Description: Adapter failure. D D D D D D D D Description: Software error. D Description: Adapter error. Description: External wrap (10 Mbps) test failure. Description: Configuration Register Test Failure. Description: I/O Test Failure. D D Description: Adapter failure. Description: Adapter initialization test failure. D D Description: Software error. 396 Diagnostic Information for Multiple Bus Systems . “MAP 0210: General Problem Resolution” on page 67. Description: Adapter failure. Description: Adapter failure. Description: External wrap (100 Mbps) test failure. Description: Enhanced Error handling failure. Description: Software error. D D D D Failing Function Codes 778 221 software 778 778 software 778 221 software 778 778 221 software 778 778 221 778 software 778 902 778 221 software 778 778 221 software 778 77B 77B 77B 77B 77B 77B 77B Description and Action (Unless otherwise indicated. Description: Internal wrap test failure. use Chapter 11. D Description: Adapter error. D D Description: Software error.

Description: The adapter card hardware failed.35 interface adapter cable. G G Failing Function Codes 77B 77B Description and Action (Unless otherwise indicated. SRNs 700-102 through 89c-302 397 . Description: An error was found with the X. Description: Adapter Serial Communication Controller (SCC) test failure. Description: The adapter card hardware failed. Description: An error was found on the adapter. Description: Adapter logic test failure. Description: The adapter hardware failed. Description: Error Log Analysis indicates a problem with the EEPROM on the adapter Description: Error Log Analysis indicates a non-critical problem with the VPD and the EEPROM on the adapter Action: Schedule deferred maintenance. Description: Adapter channel Input/Output test failure. Description: An error was found on the adapter. Description: The adapter hardware failed. Description: Error Log Analysis indicates that the device driver has detected a PIO error which it was unable to correct.21 interface adapter cable.24 interface adapter cable. Description: The adapter hardware failed. “MAP 0210: General Problem Resolution” on page 67. Description: Error log analysis indicates that the adapter has been shut down due to an unrecoverable error.) Description: Error log analysis indicates that the adapter is not responding to initialization commands. Description: The adapter card POST test failed. Description: An error was found with the X. Description: Adapter logic test failure. Description: Adapter logic test failure. Description: Adapter could not be detected or configured. use Chapter 11. Description: The adapter card hardware failed. Chapter 32. 77B-703 77B-704 77B-705 G G G 77B 77B 77B 780-101 780-102 780-109 780-113 780-114 780-120 D D D D D D 780 227 780 780 780 780 227 780 227 software 271 780 272 780 273 780 780 780 780 780 185 780 227 780 849 227 780 185 780 780-140 780-150 780-160 780-170 780-180 780-190 780-210 780-211 780-230 780-232 780-240 780-250 D D D D D D D D D D D D Description: An error was found with the X.Service Request Number 77B-701 77B-702 SRN Src.

Adapter download diagnostics failed Description: Memory size test failed. Description: ROS POST adapter software initialization error. Description: External wrap test failed.Service Request Number 780-260 780-270 780-280 780-290 780-300 780-310 780-320 780-330 780-400 780-700 SRN Src. Description: An adapter error was found during error log analysis. Description: DMA register test failed. Description: ROS checksum test failed. D D D D G G G G D D Failing Function Codes 780 780 780 780 780 780 185 780 227 780 227 780 227 780 227 software 780 780 780 781 227 781 781 781 227 781 227 781 227 781 227 781 227 781 781 781 781 781 227 Description and Action (Unless otherwise indicated. Description: ROS version test failed. Description: An adapter error was found during error log analysis. use Chapter 11. Description: EIB ID test failed. Description: The adapter failed to configure. 780-720 780-721 780-722 781-101 781-102 781-103 781-104 781-105 781-106 781-107 781-108 781-109 781-111 781-112 781-113 781-114 D D D D D D D D D D D D D D D D Description: Cable wrap test failed.21 PAL test failed. Description: An adapter error was found during error log analysis. Description: Extended DRAM SIP test failed. Description: Twin tail logic test failed. Description: The adapter card hardware failed. Description: Error log analysis indicates a hardware problem. Description: Port wrap test failed. Description: The adapter card hardware failed. “MAP 0210: General Problem Resolution” on page 67. Description: A software error was caused by a hardware failure. Description: Cable wrap test failed.) Description: The adapter card hardware failed. Description: The adapter card hardware failed. Description: Interface ID test failed. Description: DUSCC register test failed. 398 Diagnostic Information for Multiple Bus Systems . Description: X.

Description: The V. Description: The error log analysis indicates the adapter failed. 4-port multiprotocol cable Description: The Reserve command failed. D D D D D Failing Function Codes 254 253 257 260 781 227 software 781 227 software 781 781 227 855 227 B77 B69 227 B77 781 227 B69 B71 B69 B72 B69 B73 B69 B74 B69 B77 B69 B69 B77 258 781 783 783 783 media Description and Action (Unless otherwise indicated. Description: No interface card detected.) Description: The RS-232 cable wrap test failed. use Chapter 11. 781-121 D 781-200 781-221 781-231 781-501 G G D D 781-502 781-503 781-504 781-505 781-506 781-507 781-508 781-516 781-517 781-720 783-110 783-120 783-130 D D D D D D D D D D D D D Description: The memory module failed. Description: Adapter hardware failure. Description: The X.21 cable wrap test failed. Description: Adapter Test Failure. Description: The error log analysis indicates the adapter hardware failed. Description: The power-on self-test (POST) failed. Description: The RS-422A cable wrap test failed. Description: Adapter hardware failure. Description: Adapter hardware failure. “MAP 0210: General Problem Resolution” on page 67.Service Request Number 781-116 781-117 781-118 781-119 781-120 SRN Src. Description: The adapter was not detected or could not be configured. Description: Adapter hardware failure. Description: The Inquiry command failed.35 cable wrap test failed. Chapter 32. Description: The Load command failed. Description: Adapter hardware failure. Description: Adapter hardware failure. Description: The 4-port jumper cable assembly wrap test failed. SRNs 700-102 through 89c-302 399 . Description: Adapter Test Failure. test failed.

use Chapter 11. D 400 Diagnostic Information for Multiple Bus Systems . Description: The Release command failed. D D D D D D Failing Function Codes 783 media 783 783 media 783 media 783 media 783 B88 media 783 media 783 media 783 783 media 783 B88 783 783 783 783 software B88 783 software 783 media 783 B88 software 783 B88 783 B88 software Description and Action (Unless otherwise indicated. Description: SCSI adapter configuration failed. Description: The Unload command failed.) Description: The Unload command failed. Description: An adapter or bus I/O error occurred. Description: The Openx command failed. Description: The Test Unit Ready command failed. “MAP 0210: General Problem Resolution” on page 67. 783-180 783-185 783-190 783-200 783-210 783-220 783-230 783-240 783-300 783-310 D D D D D D D D D D Description: The Load command failed. 783-320 783-411 to 783-423 783-511 to 783-523 783-611 to 783-623 G D Description: Error log analysis indicates a failure. Description: The Test Unit Ready command failed. Description: The device configuration failed. Description: A reservation conflict occurred. Write and Compare test failed. Description: The device configuration failed. D Description: The drive returned bad or non-extended sense data. Description: The Send Diagnostic command failed. Description: The Request Sense command failed.Service Request Number 783-135 783-140 783-150 783-160 783-169 783-170 SRN Src. Description: The Mode Select command failed. Description: The Mode Select command failed. Description: The Send Diagnostic command failed. Description: The Read.

Description: A SCSI reservation conflict error. use Chapter 11. 784-117 784-118 784-120 784-122 784-124 784-126 784-128 784-129 D D D D D D G G 784 784 B88 784 784 784 784 B88 784 190 784 B88 software 784 784 B88 software 784 B88 software 784 784 B88 190 Description: A write-protect error occurred. 784-130 784-132 784-134 784-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. diagnostic software. Description: The diagnostic test failed. Description: A disk drive hardware error occurred. D D D D D D D D D Description: An unrecoverable media error. Description: The adapter failed to configure. Description: A SCSI command time-out. “MAP 0210: General Problem Resolution” on page 67. D Failing Function Codes 783 B88 software 784 784 784 784 784 784 784 784 Description and Action (Unless otherwise indicated. Description: A protocol error. SRNs 700-102 through 89c-302 401 . Description: Unit attention condition has occurred on the Send Diagnostic command. Description: A software error was caused by a hardware failure.Service Request Number 783-711 to 783-723 784-102 784-104 784-105 784-106 784-108 784-110 784-112 784-114 784-116 SRN Src. Description: The motor failed to restart. Description: The device failed to configure. adapter. 784-136 784-137 D D Description: The certify operation failed. and application software to be sure they are all compatible. If you do not find a problem. Description: The electronics card test failed. Description: The drive did not become ready. call your support person. Action: Check the levels of the device. Description: An unrecoverable hardware error. Description: A SCSI busy or command error. Description: The error log analysis indicates a hardware failure. Description: Error log analysis indicates a SCSI bus problem. Description: The media format is corrupted. Description: A SCSI check condition error.) Description: A device timeout error occurred. Description: The bus test failed. Chapter 32.

The modem control line test failed. The modem control line test failed. 402 Diagnostic Information for Multiple Bus Systems . D D D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 785 227 785 785 227 785 227 785 227 785 785 D57 785 D57 785 D57 259 259 259 261 261 261 785 D57 785 D57 785 D57 785 D57 785 D57 785 D57 785 D57 785 D57 Description and Action (Unless otherwise indicated. The memory test failed. use Chapter 11. Could not perform because the device driver detected a hardware error. Could not do the test because the device driver detected a hardware error. Could not do the test because the device driver detected a hardware error. The data wrap communication test failed. The data wrap communication test failed. The modem control line test failed. Could not perform because the device driver detected a hardware error. Could not do the test because the device driver detected a hardware error. The data wrap communication test failed. Could not perform because the device driver detected a hardware error. The modem control line test failed. The data wrap communication test failed. The register verification test failed. The data wrap communication test failed. Could not do the test because the device driver detected a hardware error. The modem control line test failed. The modem control line test failed.Service Request Number 785-111 785-114 785-121 785-122 785-123 785-124 785-151 785-152 785-153 785-171 785-172 785-173 785-181 785-182 785-183 785-251 785-252 785-253 785-271 785-272 785-273 785-281 785-282 SRN Src. The data wrap communication test failed. The data wrap communication test failed.) Could not do the test because the device driver detected a hardware error. “MAP 0210: General Problem Resolution” on page 67.

Description: The adapter failed to configure. Description: The display test failed. Description: The adapter test failed. suspect a software problem. Description: Initiation failed. The data wrap communication test failed. use MAP 210 with a FFC of 785. Action: Run diagnostics from a source other than from the disk or a network.) The modem control line test failed. SRNs 700-102 through 89c-302 403 . Chapter 32. D D D D D Failing Function Codes 785 D57 D57 D57 D57 software 785 Description and Action (Unless otherwise indicated. otherwise. Description: An unexpected error occurred that can be attributed to software or hardware. “MAP 0210: General Problem Resolution” on page 67. Description: The adapter failed to configure. use MAP 210 with a FFC of 785. use MAP 210 with a FFC of 785. otherwise.Service Request Number 785-283 785-481 785-482 785-483 785-901 to 785-920 SRN Src. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Could not do the test because the device driver detected a hardware error. Description: An unexpected error occurred that can be attributed to software or hardware. suspect a software problem. Description: An unexpected error occurred that can be attributed to software or hardware. use Chapter 11. otherwise. 785-921 785-922 to 785-924 D D 785 software software 785 785-925 785-926 to 785-943 D D 785 software software 785 786-200 D 786 D96 227 786 227 D96 227 786 Cable Monitor D96 Cable Monitor 786-210 786-211 786-220 D D D 786-221 D Description: The display test failed. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. The modem control line test failed. Note: You must determine which of the first two FFCs is installed in the system unit. suspect a software problem. Description: The adapter test failed. Action: Run diagnostics from a source other than from the disk or a network. Action: Run diagnostics from a source other than from the disk or a network.

If the error reoccurs use MAP 210. otherwise. Description: Failed to reserve the device. D D D D D Failing Function Codes 786 227 D96 227 787 787 227 787 RGB Cable Display 787 D95 D95 227 D95 RGB Cable Display D95 788 227 software 788 software 788 788 software 789 789 789 789 789 789 789 789 OpticalDisk Description and Action (Unless otherwise indicated. “MAP 0210: General Problem Resolution” on page 67. The ELA indicates HW failure. Run diagnostics on the changed media in System Verification mode. Description: GXT500P Graphics Adapter. Action: Change the media. Description: Failed to release the device. GXT500P Graphics Adapter. use Chapter 11. Description: System Error. Description: GXT550P Graphics Adapter. Description: The optical disk failed to load. 787-1xx 787-200 787-201 787-2AA D D D D Description: GXT500P Graphics Adapter. Description: Failed to get the inquiry data.) Description: The ELA indicates HW failure. Description: The Prevent Media Removal command failed. Description: System Error. Description: Adapter Error. Description: The Allow Media Removal command failed. Description: GXT550P Graphics Adapter.Service Request Number 786-710 786-711 787-100 787-101 787-1AA SRN Src. Description: System Error. Description: The device motor failed to start. replace the media. Description: GXT500P Graphics Adapter. 787-2xx 788-001 788-002 788-003 788-004 789-101 789-102 789-103 789-104 789-105 789-106 789-107 789-200 D D D D D D D D D D D D D Description: GXT550P Graphics Adapter. Description: Failed to make the device ready. 404 Diagnostic Information for Multiple Bus Systems . Description: GXT550P Graphics Adapter.

and rerun diagnostics. use Chapter 11. Run diagnostics on the changed media in System Verification mode. run the drive cleaning procedures if applicable. otherwise. Description: The Mode Sense command failed. and rerun diagnostics. If errors reoccur. use MAP 210. or the drive does not support cleaning procedures. or the drive does not support cleaning procedures. or the drive does not support cleaning procedures. If the errors reoccur use MAP 210. Description: A hardware error occurred. replace the media. replace the media. use MAP 210. Run diagnostics on the changed media in System Verification mode. run the drive cleaning procedures if applicable. replace the media. replace the media. or the drive does not support cleaning procedures. 789-202 D 789-204 789-205 D D 789 B88 789 OpticalDisk 789 OpticalDisk 789-206 D 789-207 D 789 OpticalDisk 789-208 D 789 OpticalDisk 789-209 D 789 OpticalDisk Chapter 32. Description: The Mode Select command failed. Action: Change the media. replace the media. replace the media. If the errors reoccur. run the drive cleaning procedures if applicable and rerun the diagnostics. If errors do not reoccur. otherwise. Run diagnostics on the changed media in System Verification mode. Action: Change the media. run the drive cleaning procedures if applicable. Description: The diagnostic test failed. otherwise. otherwise. otherwise. or the drive does not support the cleaning procedures use MAP 210. otherwise. use MAP 210. and rerun diagnostics. Run diagnostics on the changed media in System Verification mode. D Failing Function Codes 789 OpticalDisk 789 OpticalDisk Description and Action (Unless otherwise indicated. Action: Change the media. If the errors reoccur.) Description: Failed to unload the optical disk. Action: Change the media. read and compare test failed. otherwise. If the errors do not reoccur. Description: The device failed to configure. Run diagnostics on the changed media in System Verification mode. If the errors do not reoccur. and rerun diagnostics. SRNs 700-102 through 89c-302 405 . If the errors reoccur. “MAP 0210: General Problem Resolution” on page 67. If the errors reoccur. If the error reoccurs. Description: The random write. Action: Change the media. If the errors do not reoccur. use MAP 210. Action: Change the media. Run diagnostics on the changed media in System Verification mode.Service Request Number 789-201 SRN Src. Run diagnostics on the changed media in System Verification mode. use MAP 210. Description: The Test Unit Ready command failed. Action: Change the media. replace the media. If the errors do not reoccur. run the drive cleaning procedures if applicable.

789-402 D Description: Unit attention condition has occurred. Note: Use the time when the error occurred and the ″Spare Sector Availability″ service aid to identify the disk that has the error. Description: Software error. otherwise. D Failing Function Codes 789 B88 software 789 B88 Cables software OpticalDisk 190 B88 software OpticalDisk 190 B88 software OpticalDisk Description and Action (Unless otherwise indicated. 789-401 D Description: An unknown error has occurred. 789-700 G 789 OpticalDisk 789-701 G OpticalDisk 789 789-702 G 789 B88 Cables Software 78B 78B Software 78B 227 78B-001 78B-002 78B-003 D D D 406 Diagnostic Information for Multiple Bus Systems . Description: The ELA indicates an equipment error. Description: ELA indicates an irrecoverable data error. Description: Adapter failure. Note: Use the time when the error occurred to identify the faulty media. If the unit checks out to be good. Description: ELA indicates that the adapter detected an error.Service Request Number 789-300 SRN Src. Backup the media and then replace it.) Description: A SCSI reservation conflict has occurred. If errors are reported. Action: Run diagnostics in System Verification mode to isolate the problem. use Chapter 11. Backup the media and then replace it. “MAP 0210: General Problem Resolution” on page 67. the error is due to faulty media. the error is due to faulty media. Action: Run diagnostics in System Verification mode to isolate the problem. Action: Use the 7209 Installation and Service Guide. use MAP 210. If errors are reported. Action: Backup the media and replace it. 789-400 D Description: A SCSI command time out has occurred. 789-600 G Description: ELA indicates that the spare sectors on the disk are exhausted. use MAP 210. Note: Use the time when the error occurred to identify the faulty media. use MAP 210. otherwise. Description: Adapter failure.

Service Request Number 78B-004 SRN Src. Description: 10 Base-T transceiver test failure. 78B-005 D Description: Adapter failure. Description: Internal wrap test failure. Description: External wrap (10 Mbps) test failure. Description: Internal loopback test failure. Description: Configuration register test failure. Description: Internal wrap test failure. use Chapter 11. 78D-001 78D-002 78D-003 78D-004 D D D D Description: Software error. Chapter 32. 78D-005 D Description: Adapter failure. Description: Adapter initialization test failure. Description: Display failure. Description: External loopback test failure. Description: External wrap (10 Mbps) test failure. D Failing Function Codes 78B Monitor/ Cable 78B 227 Monitor/ Cable software 78D 78D software 78D 227 78D Monitor/ Cable 78D 227 Monitor/ Cable 790 790 790 790 790 790 790 790 790 790 790 790 790 790 B08 B09 790 software B08 790 Description and Action (Unless otherwise indicated. Description: I/O test failure. Description: 10Base-2 transceiver test failure. Description: Device configuration failure. 790-101 790-102 790-103 790-104 790-105 790-106 790-107 790-108 790-109 790-121 790-122 790-124 790-125 790-126 790-150 790-151 790-223 790-224 D D D D D D D D D D D D D D D D D D Description: Configuration Register Test failure.) Description: Adapter or display failure. Description: Internal loopback test failure. “MAP 0210: General Problem Resolution” on page 67. SRNs 700-102 through 89c-302 407 . Description: Adapter failure. Description: External wrap (100 Mbps) test failure. Description: Adapter failure. Description: I/O register test failure. Description: Internal wrap test failure. Description: 10Base-T transceiver test failure.

and application software to be sure they are all compatible. Description: A SCSI command time-out occurred. Description: A SCSI busy or command error. Description: Error Log Analysis indicates that the device driver has detected a PIO error which it was unable to correct. Description: The media format is corrupted. Description: A SCSI reservation conflict error. Description: The electronics card test failed. Description: The motor failed to restart. Description: The bus test failed. diagnostic software. Description: A protocol error.Service Request Number 790-225 790-250 790-251 790-701 790-702 SRN Src. Description: The drive did not become ready. adapter. Description: Error Log Analysis indicates a problem with EEPROM on the adapter. Description: An unrecoverable media error occurred. Description: A software error was caused by a hardware failure. Description: Error Log Analysis indicates that the adapter is not responding to initialization commands. Description: 10 Base-2 transceiver test failure. Description: An unrecoverable hardware error. Description: Error Log Analysis indicates that the adapter has been shutdown due to an unrecoverable error. Description: Error log analysis indicates a hardware problem. If you do not find a problem. call your support person. Description: The diagnostic test failed. D D D G G Failing Function Codes B09 790 B08 790 B09 790 790 790 Description and Action (Unless otherwise indicated. Description: A SCSI check condition error occurred. use Chapter 11.) Description: 10 Base-2 transceiver test failure. “MAP 0210: General Problem Resolution” on page 67. Description: 10 Base-T transceiver test failure. 408 Diagnostic Information for Multiple Bus Systems . 790-703 790-704 790-720 791-102 791-104 791-105 791-106 791-108 791-110 791-112 791-114 791-116 G G G D D D D D D D D D 790 790 790 software 791 791 791 791 791 791 791 791 791-117 791-118 791-120 791-122 791-124 791-126 791-128 D D D D D D G 791 791 B88 791 791 791 791 B88 791 Description: A write-protect error occurred. Description: The error log analysis indicates a hardware failure. Action: Check the levels of the device.

Description: The motor failed to restart. “MAP 0210: General Problem Resolution” on page 67. Description: The media format is corrupted.) Description: Error log analysis indicates a SCSI bus problem. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: A protocol error. Action: Check the levels of the device. Description: The error log analysis indicates a hardware failure. Description: A SCSI check condition error occurred. Chapter 32. Description: The adapter failed to configure. Description: An unrecoverable hardware error. If you do not find a problem. and application software to be sure they are all compatible. Description: The drive did not become ready. 792-102 792-104 792-105 792-106 792-108 792-110 792-112 792-114 792-116 D D D D D D D D D 792-117 792-118 792-120 792-122 792-124 792-126 792-128 D D D D D D G 792 792 B88 792 792 792 792 B88 792 Description: A write-protect error occurred. G Failing Function Codes 190 791 B88 software 791 791 B88 software 791 B88 software 791 791 B88 190 792 792 792 792 792 792 792 792 Description and Action (Unless otherwise indicated. Description: A software error was caused by a hardware failure. use Chapter 11. SRNs 700-102 through 89c-302 409 . call your support person. Description: A SCSI command time-out occurred. Description: A disk drive hardware error occurred. Description: A SCSI busy or command error. 791-130 791-132 791-134 791-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function.Service Request Number 791-129 SRN Src. 791-136 791-137 D D Description: The certify operation failed. diagnostic software. Description: The device failed to configure. Description: The bus test failed. adapter. Description: An unrecoverable media error occurred. Description: A SCSI reservation conflict error. Description: The electronics card test failed. Description: The diagnostic test failed.

and application software to be sure they are all compatible. call your support person. Description: The bus test failed. Description: An unrecoverable hardware error. Description: The error log analysis indicates a hardware failure. Description: The electronics card test failed. Action: Check the levels of the device. Description: Unit attention condition has occurred on the Send Diagnostic command. “MAP 0210: General Problem Resolution” on page 67. G Failing Function Codes 190 792 B88 software 792 792 B88 software 792 B88 software 792 792 B88 190 793 793 793 793 793 793 793 793 Description and Action (Unless otherwise indicated. 792-130 792-132 792-134 792-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: The media format is corrupted. Description: The motor failed to restart. 410 Diagnostic Information for Multiple Bus Systems . Description: The diagnostic test failed. Description: A SCSI busy or command error. Description: An unrecoverable media error occurred. 793-102 793-104 793-105 793-106 793-108 793-110 793-112 793-114 793-116 D D D D D D D D D 793-117 793-118 793-120 793-122 793-124 793-126 793-128 D D D D D D G 793 793 B88 793 793 793 793 B88 793 Description: A write-protect error occurred. 792-136 792-137 D D Description: The certify operation failed. Description: The adapter failed to configure. Description: A disk drive hardware error occurred. Description: A SCSI reservation conflict error. Description: A protocol error. Description: A software error was caused by a hardware failure. Description: The device failed to configure. diagnostic software. Description: A SCSI check condition error occurred. Description: A SCSI command time-out occurred. If you do not find a problem. adapter.) Description: Error log analysis indicates a SCSI bus problem. use Chapter 11.Service Request Number 792-129 SRN Src. Description: The drive did not become ready.

Description: PROM check test failure. Description: Receive queue handling test failure.) Description: Error log analysis indicates a SCSI bus problem. Description: High memory (ISA) test failure. use Chapter 11. Description: Restricted Token Monitor test failure. Description: DMA measurement test failure. Description: ASIC test failure. 793-130 793-132 793-134 793-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: PLC1 test failure. Description: FORMAC loopback with master access test failure. Description: Special test failure. Description: Config register test failure. Description: Timer and IRQ test failure. Description: PLC2 test failure. Description: FORMAC register test failure. Description: Send long frame test failure. Description: A disk drive hardware error occurred. Description: FORMAC Ring_Op test failure. Description: FORMAC loopback test failure. “MAP 0210: General Problem Resolution” on page 67. 793-136 793-137 D D Description: The certify operation failed. G Failing Function Codes 190 793 B88 software 793 793 B88 software 793 B88 software 793 793 B88 190 795 795 795 795 795 227 795 795 795 795 221 795 227 795 795 795 795 227 795 221 795 221 795 795 Description and Action (Unless otherwise indicated. SRNs 700-102 through 89c-302 411 . 795-201 795-202 795-203 795-204 795-205 795-206 795-207 795-208 795-209 795-210 795-211 795-212 795-213 795-214 795-215 795-216 795-217 795-218 D D D D D D D D D D D D D D D D D D Chapter 32. Description: The device failed to configure. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: RAM check via DMA test failure.Service Request Number 793-129 SRN Src. Description: Adapter RAM check failure. Description: The adapter failed to configure.

“MAP 0210: General Problem Resolution” on page 67. Description: FORMAC loopback external wrap failure. 799-301 D Description: Internal adapter test failed. Description: External wrap test failed on port 0. 799-207 D Description: External wrap test failed on port 1. Description: External wrap test failed on port 1. Description: Error log analysis indicates hardware failure. 799-302 D Description: External wrap test failed on port 0. Description: PLC1 FDDI external wrap failure.) Description: Bypass test failure. Description: External wrap test failed on port 0. Description: PLC2 FDDI external wrap failure. Description: External wrap test failed on port 1. Description: External wrap test failed on port 0. Description: External wrap test failed on port 1. use Chapter 11.Service Request Number 795-219 795-301 795-302 795-303 795-304 795-700 799-101 799-102 799-201 799-202 799-203 799-204 799-205 799-206 SRN Src. Description: Internal adapter test failed. 799-304 D Description: External wrap test failed on port 0. 799-305 D Description: External wrap test failed on port 1. Description: External wrap test failed on port 0. 799-303 D Description: External wrap test failed on port 1. 412 Diagnostic Information for Multiple Bus Systems . D D D D D D D D D D D D D D Failing Function Codes 795 795 795 795 795 795 2C3 799 2C3 799 799 227 799 227 799 227 2C3 799 2C3 799 2C3 799 software 2C3 799 software 799 227 software 799 227 software 799 227 software 2C3 799 software 23C 799 software Description and Action (Unless otherwise indicated. Description: Send long frame FDDI external wrap failure.

“MAP 0080: System Bus Problem Isolation” on page 63. 802-78D 802-80c C C 78D 80c 802-837 C 837 687 E10 227 xxxx E10 227 802-xxxx C Description: The diagnostics did not detect an installed resource. Action: Use Chapter 10. SRNs 700-102 through 89c-302 413 . Description: Loop back failed. “MAP 0210: General Problem Resolution” on page 67. Description: CODEC ID invalid. Description: Clock control failed.) Chapter 32. Description: A potential problem with a SSA adapter exists.) Description: Error log analysis indicates a hardware problem. Description: A resource was not detected that was previously installed.Service Request Number 799-700 7C1-101 7C1-102 7C1-103 7C1-107 7C1-108 7C1-109 7C1-117 802-655 802-657 802-684 802-787 802-78C SRN Src. Description: A potential problem with the RS422 concentrator exists. Description: A resource was not detected that was previously installed. Description: Internal speaker failed. Description: Audio Subsystem failed. Description: SoundBlaster interface failed. use Chapter 11. Description: CS4232 failed. If the system has internal SSA drives. Description: The diagnostics did not detect an installed resource. (The substituted xxxx is the FFC. Description: A resource was not detected that was previously installed. Description: A system bus problem exists. If the system has external SSA drives refer to the SSA Adapters User’s Guide and Maintenance Information or the service guide for your disk subsystem. go to the SSA MAP in either the system unit’s service guide or user’s guide. Note: To obtain the FFC substitute the last three or four digits of the SRN following the dash (-) for xxxx. Description: A potential problem with the Enhanced Remote Async Node exists. D D D D D D D D C C C C C Failing Function Codes 799 software 7C1 software 7C1 7C1 7C1 7C1 7C1 D97 655 657 684 687 787 D95 78C Description and Action (Unless otherwise indicated.

use the last three digits of the 803-xxx as the FFC and got to MAP 210. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error.) Description: A software error occurred while running the diagnostics which could be caused by either hardware or software. Description: The CD-ROM drive indicates an error. Description: Unable to open the device driver. substitute the last three or four digits of the SRN after the dash (-) for xxxx. Description: A command reservation conflict was detected. use Chapter 11. Description: The CD-ROM drive indicates an error. “MAP 0210: General Problem Resolution” on page 67. Description: The CD-ROM drive indicates an error. Description: Unable to do configuration. Description: Unable to do configuration. then proceed to the FFC table using the substituted digits as your FFC. Description: The CD-ROM drive indicates an error. Description: Undefined error detected. contact your support center. If you get no error from the standalone diagnostics. Description: A command timeout was detected. If you get a different SRN. Description: Unable to open device driver. If you get the same SRN. you may have a problem with the software. Description: The CD-ROM drive indicates an error. Description: A media error was detected. Action: Run standalone diagnostics. If your 803-xxxx SRN is not listed. 804-111 804-112 804-113 804-121 804-122 804-123 804-125 804-126 804-127 804-128 804-129 804-150 804-151 804-152 804-162 804-171 804-172 804-173 804-175 804-198 804-199 D D D D D D D D D D D D D D D D D D D D D 804 B88 804 B88 804 B88 804 804 804 804 B88 804 804 804 804 Test Disc 804 804 B88 804 804 804 804 804 804 804 B88 804 414 Diagnostic Information for Multiple Bus Systems . Description: Undefined error detected. Note: xxxx corresponds to the last three or four digits of the SRN. Description: The CD-ROM drive indicates an error. use it in place of the original SRN.Service Request Number 803-xxxx SRN Src. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error. Description: Unable to reserve device. Description: Unable to reserve device. D Failing Function Codes xxxx Description and Action (Unless otherwise indicated.

If your 804-xxxx SRN is not listed. Action: Use Chapter 15. Description: Error log analysis indicates a machine check due to uncorrectable memory error. “MAP 0240: Memory Problem Resolution” on page 93. use Chapter 11. Action: Use Chapter 15. Action: Use Chapter 15. then proceed to the FFC table using the substituted digits as your FFC. “MAP 0240: Memory Problem Resolution” on page 93. Description: Error log analysis indicates a machine check due to uncorrectable memory error. “MAP 0240: Memory Problem Resolution” on page 93.) Description: The LED test failed. Description: Error log analysis indicates a machine check due to uncorrectable memory error. substitute the last three or four digits of the SRN after the dash (-) for xxxx. Description: Error log analysis indicates a machine check due to uncorrectable memory error. Description: No tone during audio test. “MAP 0240: Memory Problem Resolution” on page 93. D D G G H Failing Function Codes 804 804 804 804 B88 xxxx Description and Action (Unless otherwise indicated. Description: Error log analysis indicates a machine check due to uncorrectable memory error. 805-110 G D67 805-111 G D83 805-120 G D68 805-121 G D84 805-130 G D69 805-131 G D85 805-140 G D70 805-141 G D86 Chapter 32. Description: Errors found during ELA. Action: Use Chapter 15. “MAP 0210: General Problem Resolution” on page 67.Service Request Number 804-211 804-281 804-301 804-302 804-xxxx SRN Src. “MAP 0240: Memory Problem Resolution” on page 93. SRNs 700-102 through 89c-302 415 . Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Description: Error log analysis indicates a machine check due to uncorrectable memory error. Description: Errors found during ELA. Action: Use Chapter 15. Description: Error log analysis indicates a machine check due to uncorrectable memory error. Description: Error log analysis indicates a machine check due to uncorrectable memory error. Action: Use Chapter 15. Description: An unexpected halt occurred while running the diagnostics. Note: xxxx corresponds to the last three or four digits of the SRN. “MAP 0240: Memory Problem Resolution” on page 93.

“MAP 0210: General Problem Resolution” on page 67. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Description: Error log analysis indicates a machine check due to uncorrectable memory error. Description: Error log analysis indicates a machine check due to uncorrectable memory error. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Description: Error log analysis indicates a machine check due to uncorrectable memory error. Action: Use Chapter 15. Action: Use Chapter 15. Description: Error log analysis indicates a machine check due to uncorrectable memory error. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. G Failing Function Codes E11 Description and Action (Unless otherwise indicated. Description: Error log analysis indicates a machine check due to uncorrectable memory error. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15.) Description: Error log analysis indicates a machine check due to uncorrectable memory error. Description: Error log analysis indicates a machine check due to uncorrectable memory error. Description: Error log analysis indicates a machine check due to uncorrectable memory error.Service Request Number 805-150 SRN Src. use Chapter 11. Action: Use Chapter 15. Description: Error log analysis indicates a machine check due to uncorrectable memory error. 805-151 G E14 805-210 G D71 805-211 G D87 805-220 G D72 805-221 G D88 805-230 G D73 805-231 G D89 805-240 G D74 805-241 G D90 805-250 G E12 416 Diagnostic Information for Multiple Bus Systems . “MAP 0240: Memory Problem Resolution” on page 93. Description: Error log analysis indicates a machine check due to uncorrectable memory error. Action: Use Chapter 15. Description: Error log analysis indicates a machine check due to uncorrectable memory error. “MAP 0240: Memory Problem Resolution” on page 93.

“MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. Description: Error log analysis indicates a machine check due to uncorrectable memory error.) Description: Error log analysis indicates a machine check due to uncorrectable memory error. then replace the appropriate memory module(s). SRNs 700-102 through 89c-302 805-310 G D75 805-311 G D91 805-320 G D76 805-321 G D92 805-331 G D93 805-340 G D78 805-341 G D94 805-350 G E13 805-351 G E16 805-600 G 417 . Description: Error log analysis indicates a machine check due to uncorrectable memory error or unsupported memory. Description: Error log analysis indicates a machine check due to uncorrectable memory error. “MAP 0240: Memory Problem Resolution” on page 93. Description: Error log analysis indicates a machine check due to uncorrectable memory error. If the modules are supported. Action: Examine the memory modules and determine if they are supported types. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15.Service Request Number 805-251 SRN Src. Action: Use Chapter 15. Action: Use Chapter 15. Description: Error log analysis indicates a machine check due to uncorrectable memory error. “MAP 0210: General Problem Resolution” on page 67. “MAP 0240: Memory Problem Resolution” on page 93. Description: Error log analysis indicates a machine check due to uncorrectable memory error. G Failing Function Codes E15 Description and Action (Unless otherwise indicated. Description: Error log analysis indicates a machine check due to uncorrectable memory error. “MAP 0240: Memory Problem Resolution” on page 93. Description: Error log analysis indicates a machine check due to uncorrectable memory error. Chapter 32. Action: Use Chapter 15. Action: Use Chapter 15. Use Chapter 15. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Description: Error log analysis indicates a machine check due to uncorrectable memory error. use Chapter 11. Description: Error log analysis indicates a machine check due to uncorrectable memory error.

Description: Error log analysis indicates multiple instances of machine check of unknown origin. Description: Error log analysis indicates a machine check due to ISA device error. Action: Use MAP 210.) Description: Error log analysis indicates a machine check due to CPU internal cache error. Action: If the problem is persistent. Action: Run diagnostics on the ISA devices. Description: Error log analysis indicates a machine check due to CPU address/data bus parity error. If multiple devices fail. Description: Error log analysis indicates a machine check due to CPU bus transfer error. but the device could not be identified. contact your service support structure. Description: Error log analysis indicates a machine check due to software. G G G Failing Function Codes 210 214 D01 210 214 D01 210 D01 210 214 210 214 214 217 D01 Description and Action (Unless otherwise indicated. contact your service support structure. Action: If the problem is persistent. use FFC 295. “MAP 0210: General Problem Resolution” on page 67. but the device could not be identified. Description: Error log analysis indicates a machine check due to Integrated PCI device does not respond. Description: Error log analysis indicates a machine check due to a L2 parity error. Description: Error log analysis indicates a machine check of unknown origin. Description: Error log analysis indicates a machine check due to memory address error. Description: Error log analysis indicates a machine check due to memory controller internal error. Description: Error log analysis indicates a machine check due to CPU address/data bus parity error. 805-604 805-605 805-606 805-607 805-608 805-609 805-610 G G G G G G G 805-611 G 805-612 805-616 805-617 G G G 214 software Description: Error log analysis indicates a machine check due to an Illegal L2 copy-back operation. use Chapter 11. Description: Error log analysis indicates a machine check due to EISA/ISA bus time out error. Description: Error log analysis indicates a machine check due to a Flash ROM error. 805-618 G 805-619 G 221 Description: Error log analysis indicates a machine check due to an unidentified source on the I/O subsystem. Description: Error log analysis indicates a machine check due to CPU bus transfer error.Service Request Number 805-601 805-602 805-603 SRN Src. 805-621 805-622 G G 292 293 418 Diagnostic Information for Multiple Bus Systems . Action: Run diagnostics on the ISA devices. Description: Error log analysis indicates a machine check due to Integrated PCI device does not respond.

Description: Slow fan or defective thermal sensor. Description: Error log analysis indicates a machine check due to a system bus error. and spin with power applied. 2) check for obstructions to cooling air flow. Description: Error log analysis indicates a machine check due to a processor bus error. 2 and 3 can be ruled out.Service Request Number 805-623 805-624 805-625 805-631 805-632 805-633 805-634 805-635 805-640 805-641 805-642 805-643 805-644 805-645 805-646 805-649 SRN Src. Description: Error log analysis indicates a machine check due to a cache paradox. If the AC line voltage is correct replace the listed FRUs. If reasons 1. Description: Error log analysis indicates a machine check due to an address/data bus parity error. “MAP 0210: General Problem Resolution” on page 67. Description: Error log analysis indicates a machine check due to Internal error from PCI device. Description: Error log analysis indicates a machine check due to Internal error from PCI device. Action: 1) Check spacing around system enclosure. Description: Error log analysis indicates a machine check due to an internal error. Description: Error log analysis indicates a machine check due to Integrated PCI device does not respond. Description: Error log analysis indicates a machine check due to Internal error from PCI device. Chapter 32. Use any SRN reported. SRNs 700-102 through 89c-302 805-801 G 166 221 805-802 G 152 210 419 . Action: Check AC line voltage per the Power MAP in your service guide. use Chapter 11. suspect a software problem. 3) check that all fans can rotate freely. Description: Error log analysis indicates a machine check due to Internal error from PCI device. Description: Error log analysis indicates a machine check due to a detected L2 hit signal. then replace the listed FRUs. G G G G G G G G G G G G G G G G Failing Function Codes 294 295 868 292 293 294 295 868 2E8 214 2E8 210 2E8 2E8 2E8 2E8 2E8 214 software Description and Action (Unless otherwise indicated. Description: Error log analysis indicates a machine check due to Internal error from PCI device. Action: Run Standalone Diagnostics on all devices. Description: Over/Under voltage condition.) Description: Error log analysis indicates a machine check due to Integrated PCI device does not respond. Description: Error log analysis indicates a machine check due to Integrated PCI device does not respond. Description: Error log analysis indicates a machine check due to a directory parity error. If no other SRN is reported. Description: Error log analysis indicates a machine check due to a disabled I/O address space.

Description: System shutdown due to critical over temperature condition. 805-813 D 2E1 210 806-001 thu 806-017 806-018 806-100 806-505 D 806 Description: GXT800P Graphics Adapter. 2) check for accumulated dust on the CPU and planar. 805-804 G 166 2E1 152 152 805-805 G 805-807 G 166 805-811 D 166 805-812 D 152 210 Description: Over/Under voltage condition. If reasons 1. then replace the listed FRUs. Check for accumulated dust on the CPU and planar. Check that all fans rotate freely. 2. Description: GXT800P Graphics Adapter. D D D 806 806 806 298 Description: GXT800P Graphics Adapter Monitor/Display Cable. If the range switch is set correctly or is not present refer to ″MAP 1520: Power″ in the Service Guide for your system. Description: System shutdown due to loss of AC power. on the power supply and ensure that it is set to match the AC input voltage. 420 Diagnostic Information for Multiple Bus Systems . Action: 1) check for obstructions to cooling air flow. Check spacing around system enclosure 2. Description: Slow fan or defective thermal sensor. Description: GXT800P Graphics Adapter GXT800P Base Memory in slot 0. then replace the listed FRUs. Action: Check the AC line voltage per the Power MAP in your service guide. Check for obstructions to cooling air flow. 2. Action: 1. then replace the listed FRUs. If reasons 1 and 2 can be ruled out. If reasons 1 and 2 can be ruled out. Action: Check the voltage range switch. use Chapter 11.Service Request Number 805-803 SRN Src. If fans are connected. If fans are connected replace the listed FRU. and spin when power is applied. Action: Check to ensure fans are connected. G Failing Function Codes 2E1 210 Description and Action (Unless otherwise indicated. 2. Action: Check to ensure fans are connected. Action: 1.) Description: System shutdown due to non-critical over temperature condition. If the AC line voltage is correct replace the listed FRUs. if present. or 4. Description: System shutdown due to an inoperative fan. and 3 can be ruled out. then replace the listed FRUs. 1. Check for obstructions to cooling air flow 3. “MAP 0210: General Problem Resolution” on page 67. 3. Description: System shutdown due to non-critical over temperature condition.

3. Description: GXT800P Base and Texture Memory in slot 1. Description: GXT800P Base and Texture Memory in slot 3. Description: GXT800P Base Memory in slot 4. “MAP 0210: General Problem Resolution” on page 67.Service Request Number 806-515 806-619 SRN Src. or 4. Description: GXT800P Base Memory in slot 2. Description: GXT800P Base and Texture Memory in slot 1. Description: GXT800P Base and Texture Memory in slot 4. Description: GXT800P Base Memory in slot 3. Description: GXT800P Base Memory in slot 0. Otherwise. Description: Error log analysis indicates a machine check due to an unidentified source on the I/O subsystem. SRNs 700-102 through 89c-302 421 . Description: GXT800P Base and Texture Memory in slot 0. 2. Description: GXT800P Base Memory in slot 3. Description: GXT800P Base Memory in slot 4. Description: GXT800P Base and Texture Memory in slot 3. Description: GXT800P Base Memory in slot 2. use Chapter 11. use the FFCs listed and go to MAP 210. Description: Device configuration error Action: If this SRN is for an externally attached machine or enclosure. Description: GXT800P Base Memory in slot 0.) Description: GXT800P Graphics Adapter GXT800P Base and Texture Memory in slot 0. 806-700 806-701 806-702 806-703 806-704 806-710 806-711 806-712 806-713 806-714 806-e00 806-e01 806-e02 806-e03 806-e04 806-e10 806-e11 806-e12 806-e13 806-e14 807-201 D D D D D D D D D D D D D D D D D D D D D 298 298 298 298 298 297 297 297 297 297 298 298 298 298 298 297 297 297 297 297 199 891 Chapter 32. 1. go to the Service Guide for that unit. Description: GXT800P Base Memory in slot 1. Description: GXT800P Base and Texture Memory in slot 0. Description: GXT800P Base and Texture Memory in slot 4. Description: GXT800P Base Memory in slot 1. Description: GXT800P Base and Texture Memory in slot 2. Description: GXT800P Base and Texture Memory in slot 2. D G Failing Function Codes 806 297 221 Description and Action (Unless otherwise indicated.

Description: I/O Card NVRAM test failed. Description: Time of day clock not running test failed. D Failing Function Codes 199 891 Description and Action (Unless otherwise indicated. replace FFC 199 and go to MAP 210. Otherwise. Description: The VPD test failed. run diagnostics in problem determination mode on sysplanar0. If no problems are found. replace FFC 199 and go to MAP 210. use the FFCs listed and go to MAP 210. use the FFCs listed and go to MAP 210. Description: Redundant power supply or fan failure Action: If this SRN is for an externally attached machine or enclosure. Description: Floating point processor failed. Description: Floating point processor failed. Otherwise. Description: Processor has a status of failed. Processors with a failed status are deconfigured and therefore cannot be tested or used by the system. Description: The I/O planar time-of-day clock test failed. go to the Service Guide for that unit. Description: The four-digit display test failed. Otherwise.) Description: Enclosure failed to open Action: If this SRN is for an externally attached machine or enclosure. Description: The real-time clock is not running. go to the Service Guide for that unit. Otherwise. Description: Time of day POR test failed. 807-203 D 199 891 807-204 D 807-205 D 814-112 814-113 814-114 815-100 815-101 815-102 815-200 815-201 D D D D D D D D 814 221 814 815 815 815 815 7C0 815 Description: The NVRAM test failed. Description: Time of day RAM test failed. run diagnostics in problem determination mode on sysplanar0. Description: Critical power supply or fan failure Action: If this SRN is for an externally attached machine or enclosure. use Chapter 11. go to the Service Guide for that unit. “MAP 0210: General Problem Resolution” on page 67. Description: The floating-point processor test failed. Description: The battery is low. Description: The time-of-day clock is at POR. Description: Power-on self-test indicates a processor failure. Description: Enclosure failed to return inquiry data Action: If this SRN is for an externally attached machine or enclosure. If no problems are found. 816-140 817-123 817-124 817-210 817-211 817-212 817-213 817-215 D D D D D D D D 165 816 817 817 817 817 169 151 816 817 817 422 Diagnostic Information for Multiple Bus Systems . go to the Service Guide for that unit.Service Request Number 807-202 SRN Src.

824-333 824-334 824-441 824-442 824-450 824-461 824-511 824-512 824-522 824-523 824-524 826-111 826-112 826-113 826-114 D D D D D G D D D D D D D D D 824 B10 824 824 824 227 227 824 824 B10 824 824 824 software 221 221 826 826 Chapter 32.) Description: Time of day clock not running. Description: The error log analysis indicates a hardware failure. Description: Cannot run the test because the device driver detected a hardware error.Service Request Number 817-217 821-111 821-332 823-111 823-134 823-211 824-220 824-331 824-332 SRN Src. Description: An unexpected error occurred. Description: An unexpected error occurred. Description: The tablet adapter fuse failed. If the wrap plug was attached. Description: Unable to determine the type of adapter from the VPD. Description: The VPD verification test failed. Description: Cannot open device. Description: An unexpected error occurred. Description: The internal wrap test failed. Description: Standard Mouse adapter failed. “MAP 0210: General Problem Resolution” on page 67. D D D D D D D D D Failing Function Codes 817 169 821 B31 821 software 823 823 software 925 823 B10 824 824 227 824 227 Description and Action (Unless otherwise indicated. Note:Ensure that the wrap plug was not attached when the test was run. Description: Cannot open device. remove it. Description: Software error caused by hardware failure. Description: The wrap test failed. Description: Unexpected results from the test. Description: The enable/disable device test failed. Description: The register verification test failed. Description: The tablet adapter fuse failed. SRNs 700-102 through 89c-302 423 . use Chapter 11. Description: Tablet adapter reset test failed. Description: Adapter fuse failure. Description: Device cannot be configured. Description: Standard mouse adapter failed. and rerun the test. Description: Cannot open device.

Description: The modem control line test failed. Description: The modem control line test failed. Description: The modem control line test failed. Description: The data wrap communications test failed. D D D D D D D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 221 221 221 221 221 221 252 252 252 259 259 259 261 261 261 826 259 826 259 826 259 826 259 826 259 826 259 826 826 826 826 826 826 Description and Action (Unless otherwise indicated.) Description: Cannot run the test because the device driver detected a hardware error. Description: The data wrap communications test failed. “MAP 0210: General Problem Resolution” on page 67. use Chapter 11. Description: The data-wrap communications test failed. Description: The data wrap communications test failed. Description: The data wrap communications test failed. Description: The data wrap communications test failed. Description: Cannot run the test because the device driver detected a hardware error.Service Request Number 826-121 826-122 826-123 826-131 826-132 826-133 826-161 826-162 826-163 826-171 826-172 826-173 826-181 826-182 826-183 826-271 826-272 826-273 826-281 826-282 826-283 826-321 826-322 826-323 826-331 826-332 826-333 SRN Src. Description: The data wrap communications test failed. Description: The modem control line test failed. Description: The modem control line test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: Cannot run the test because the device driver detected a hardware error. Description: The modem control line test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: The modem control line test failed. Description: The modem control line test failed. Description: The data wrap communications test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: The data wrap communications test failed. Description: Cannot run the test because the device driver detected a hardware error. 424 Diagnostic Information for Multiple Bus Systems . Description: The modem control line test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: Cannot run the test because the device driver detected a hardware error.

D D D D D D D D D D D D D Failing Function Codes 826 826 826 826 826 826 D56 D56 D56 826 D56 826 D56 826 D56 software 826 Description and Action (Unless otherwise indicated. Description: The modem control line test failed. Description: Could not do the test because the device driver detected a hardware error. Description: The data wrap communication test failed. Description: The modem control line test failed. suspect a software problem. use MAP 210 with a FFC of 826. Action: Run diagnostics from a source other than from the disk or a network. Description: The modem control line test failed. suspect a software problem. SRNs 700-102 through 89c-302 425 . If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. otherwise. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Description: The adapter failed to configure. suspect a software problem. Description: The data wrap communications test failed. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics.) Description: Cannot run the test because the device driver detected a hardware error. Action: Run diagnostics from a source other than from the disk or a network. Description: An unexpected error occurred that can be attributed to software or hardware. Description: An unexpected error occurred that can be attributed to software or hardware. Description: Could not do the test because the device driver detected a hardware error. 826-921 826-922 to 826-924 D D 826 software software 826 826-925 826-926 to 826-943 D D 826 software software 826 Chapter 32. “MAP 0210: General Problem Resolution” on page 67. use MAP 210 with a FFC of 826. Description: Could not do the test because the device driver detected a hardware error. otherwise. Action: Run diagnostics from a source other than from the disk or a network. Description: The modem control line test failed. otherwise. Description: The data wrap communication test failed.Service Request Number 826-371 826-372 826-373 826-381 826-382 826-383 826-481 826-482 826-483 826-581 826-582 826-583 826-901 to 826-920 SRN Src. use Chapter 11. Description: An unexpected error occurred that can be attributed to software or hardware. use MAP 210 with a FFC of 826. Description: The adapter failed to configure. Description: The data wrap communication test failed.

Description: The parallel port interrupt test failed. Description: The control port register direction bit (write) test with BIDI enabled failed. Description: The parallel port status register read test failed. Description: The control port register direction bit (read) test with BIDI enabled failed. Description: Cannot run the test because the device driver detected a hardware error. 426 Diagnostic Information for Multiple Bus Systems . Description: Cannot run the test because the device driver detected a hardware error. Description: Input/output to the FIFO (with interrupts) failed. Description: Input/output to the FIFO (without interrupts) failed. Description: Cannot run the test because the device driver detected a hardware error. Description: The diskette adapter test failed. “MAP 0210: General Problem Resolution” on page 67. Description: The parallel port control register write/read test with BIDI enabled failed. Description: The parallel port data register read test failed. Description: The parallel port control register read test failed.Service Request Number 827-112 827-121 827-122 827-123 827-124 827-125 827-126 827-131 827-132 827-133 827-141 827-142 827-151 827-152 827-161 827-162 827-163 827-201 827-202 827-203 827-204 828-501 82C-102 SRN Src. Description: Cannot run the test because the device driver detected a hardware error.) Description: The parallel port data register write/read test failed. use Chapter 11. Description: Direct memory access to the FIFO failed. Description: The parallel port interrupt test failed. Description: Adapter test failed. Description: The parallel port control register read test failed. Description: The parallel port data register write/read test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: The parallel port control register write/read test failed. D D D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 221 827 827 827 827 827 827 827 827 827 827 827 221 827 827 221 221 827 827 827 827 828 82C Description and Action (Unless otherwise indicated. Description: The extend control register of the parallel port failed a read/write test.

Description: Could not do the test because the device driver detected a hardware error. Description: Could not do the test because the device driver detected a hardware error. Description: Could not perform because the device driver detected a hardware error.Service Request Number 82C-104 830-111 830-114 830-121 830-122 830-123 830-124 830-151 830-152 830-153 830-171 830-172 830-173 830-181 830-182 830-183 830-251 830-252 830-253 830-271 830-272 830-273 830-281 SRN Src. Description: The data wrap communication test failed. Description: The register verification test failed. Description: The modem control line test failed.) Description: Display test failed. Description: The modem control line test failed. “MAP 0210: General Problem Resolution” on page 67. Description: The modem control line test failed. Description: The data wrap communication test failed. Could not perform the test because the device driver detected a hardware error. Description: The modem control line test failed. Description: The data wrap communication test failed. The data wrap communication test failed. D D D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 82C 725 830 227 830 830 227 830 227 830 227 830 B54 830 B54 830 D54 830 259 259 259 261 261 261 830 D57 830 B54 830 B54 830 B54 830 B54 830 B54 830 D57 Description and Action (Unless otherwise indicated. SRNs 700-102 through 89c-302 427 . Description: Could not run the test because the device driver detected a hardware error. use Chapter 11. Chapter 32. Description: Could not do the test because the device driver detected a hardware error. Description: The modem control line test failed. Description: Could not do the test because the device driver detected a hardware problem. Description: The memory test failed. Description: Could not perform because the device driver detected a hardware error. Description: The data wrap communication test failed. Description: Interposer Wrap test failed. Description: The data wrap communication test failed.

Description: Unable to determine the type of adapter from the VPD. 830-921 830-922 to 830-924 D D 830 software software 830 830-925 830-926 to 830-943 D D 830 software software 830 831-111 831-112 831-113 831-114 831-121 831-122 831-123 D D D D D D D 221 221 831 831 221 221 221 428 Diagnostic Information for Multiple Bus Systems . suspect a software problem. suspect a software problem. Description: The adapter failed to configure. Action: Run diagnostics from a source other than from the disk or a network. Description: An unexpected error occurred that can be attributed to software or hardware. Description: The adapter failed to configure.Service Request Number 830-282 830-283 830-481 830-482 830-483 830-901 to 830-920 SRN Src. use MAP 210 with a FFC of 830. Description: An unexpected error occurred that can be attributed to software or hardware. Description: The data wrap communications test failed. suspect a software problem. “MAP 0210: General Problem Resolution” on page 67. otherwise. Description: The register verification test failed.) Description: The data wrap communication test failed. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Action: Run diagnostics from a source other than from the disk or a network. use MAP 210 with a FFC of 830. Action: Run diagnostics from a source other than from the disk or a network. Description: Could not do the test because the device driver detected a hardware error. D D D D D D Failing Function Codes 830 B54 830 B54 B54 B54 B54 software 830 Description and Action (Unless otherwise indicated. Description: The VPD verification test failed. Description: An unexpected error occurred that can be attributed to software or hardware. Description: Cannot run the test because the device driver detected a hardware error. Description: The modem control line test failed. otherwise. Description: The modem control line test failed. use Chapter 11. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. use MAP 210 with a FFC of 830. Description: Async Cable Wrap Test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: The data wrap communication test failed. otherwise.

Description: The data wrap communications test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: The modem control line test failed. Description: The data wrap communications test failed. Description: The data wrap communications test failed.) Description: Cannot run the test because the device driver detected a hardware error. use Chapter 11. Description: The data wrap communications test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: The modem control line test failed. Description: The data wrap communications test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: The data wrap communication test failed. Description: The data wrap communications test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: Cannot run the test because the device driver detected a hardware error. Description: The modem control line test failed. D D D D D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 221 221 221 252 252 252 221 252 221 252 221 252 259 259 259 261 261 261 831 259 831 259 831 259 831 259 831 259 831 259 831 831 831 831 Description and Action (Unless otherwise indicated. Description: Cannot run the test because the device driver detected a hardware error. Description: The modem control line test failed. Chapter 32. Description: The modem control line test failed. Description: The data wrap communications test failed. Description: The modem control line test failed. “MAP 0210: General Problem Resolution” on page 67. SRNs 700-102 through 89c-302 429 . Description: Cannot run the test because the device driver detected a hardware error.Service Request Number 831-131 831-132 831-133 831-161 831-162 831-163 831-164 831-165 831-166 831-171 831-172 831-173 831-181 831-182 831-183 831-271 831-272 831-273 831-281 831-282 831-283 831-321 831-322 831-323 831-331 SRN Src. Description: The modem control line test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: The modem control line test failed.

use MAP 210 with a FFC of 831. Description: Cannot run the test because the device driver detected a hardware error. suspect a software problem. D D D D D D D D D D D D D D D Failing Function Codes 831 831 831 831 831 831 831 831 D56 D56 D56 831 D56 831 D56 831 D56 software 831 Description and Action (Unless otherwise indicated. Description: An unexpected error occurred that can be attributed to software or hardware. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Description: The data wrap communications test failed. “MAP 0210: General Problem Resolution” on page 67. Description: The modem control line test failed. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Description: The modem control line test failed. Description: The modem control line test failed. use MAP 210 with a FFC of 831. Description: The data wrap communications test failed. 831-921 831-922 to 831-924 D D 831 software software 831 831-925 D 831 software 430 Diagnostic Information for Multiple Bus Systems . suspect a software problem. Description: Could not do the test because the device driver detected a hardware error. otherwise. Description: The modem control line test failed. Description: An unexpected error occurred that can be attributed to software or hardware. Description: The modem control line test failed. use Chapter 11. Action: Run diagnostics from a source other than from the disk or a network.) Description: The data wrap communications test failed. Description: Cannot run the test because the device driver detected a hardware error.Service Request Number 831-332 831-333 831-371 831-372 831-373 831-381 831-382 831-383 831-481 831-482 831-483 831-581 831-582 831-583 831-901 to 831-920 SRN Src. Description: The adapter failed to configure. Action: Run diagnostics from a source other than from the disk or a network. Description: The data wrap communication test failed. otherwise. Description: The adapter failed to configure. Description: Could not do the test because the device driver detected a hardware error. Description: The data wrap communication test failed.

Description: Cannot run the test because the device driver detected a hardware error. Note: xxxx represents the last 3 or 4 digits of the SRN after the dash (-). “MAP 0210: General Problem Resolution” on page 67.Service Request Number 831-926 to 831-943 SRN Src. Description: The modem control line test failed. use Chapter 11. Description: The data wrap communications test failed. The diagnostics screen indicates the actual error. or PCI device abort error. use MAP 210 with a FFC of 831. Description: The modem control line test failed. Description: The data wrap communications test failed. Description: I/O bridge/device internal error Note: xxxx represents the last 3 or 4 digits of the SRN after the dash (-). Chapter 32. Description: Sync line termination test failed. Description: Remote Async Node test failed. Description: Remote async node test failed. Description: The register verification test failed. 832-xxxx G xxxx 833-xxxx G xxxx 296 2C9 836-101 836-111 836-112 836-113 836-114 836-115 836-116 836-117 836-118 836-119 836-151 836-152 836-153 836-154 836-155 D D D D D D D D D F D D D D D 836 836 227 836 227 836 836 836 B54 836 684 837 836 837 837 837 684 836 684 836 152 C22 C22 C22 836-161 836-162 836-163 D D D Description: Cannot run the test because the device driver detected a hardware error. Description: The 128-port controller line test failed. SRNs 700-102 through 89c-302 431 . Action: Run diagnostics from a source other than from the disk or a network.) Description: An unexpected error occurred that can be attributed to software or hardware. Description: Cannot run the test because the device driver detected a hardware error. Description: Unable to determine the type of adapter from the VPD. Description: Cannot run test because the device driver detected a hardware error. D Failing Function Codes software 831 Description and Action (Unless otherwise indicated. Description: The VPD verification test failed. otherwise. PCI device data parity error. Description: The data wrap communications test failed. Description: The VPD verification test failed. Description: PCI device address parity error. Description: Cannot run the test because the device driver detected a hardware error. suspect a software problem. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics.

Description: The data wrap communications test failed while running the Remote Async Node wrap test. Description: The data wrap communications test failed while running the Printer/Terminal cable wrap test. Description: Cannot run the test because the device driver detected a hardware error while running the Printer/Terminal cable wrap test.Service Request Number 836-164 836-171 836-172 836-173 836-174 SRN Src. Description: The data wrap communications test failed. Description: The data wrap communication test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: Cannot run the test because the device driver detected a hardware error. Description: The data wrap communications test failed. Description: The modem control line test failed. Description: Cannot run the test because the device driver detected a hardware error. D D D D D Failing Function Codes D06 259 259 259 263 Description and Action (Unless otherwise indicated. “MAP 0210: General Problem Resolution” on page 67. Description: Cannot run the test because the device driver detected a hardware error while running the Remote Async Node wrap test. Description: Cannot run the test because the device driver detected a hardware error. 836-175 836-181 836-182 836-183 836-251 836-252 836-253 836-254 D D D D D D D D 263 261 261 261 836 837 836 837 836 837 836 837 836 684 836 837 836 837 836 837 836 684 836 684 836 837 836 837 836 837 836-255 836-271 836-272 836-273 836-274 D D D D D 836-275 836-281 836-282 836-283 D D D D 432 Diagnostic Information for Multiple Bus Systems . Description: Cannot run the test because the device driver detected a hardware error. Description: The data wrap communications test failed while running the Printer/Terminal cable wrap test. Description: The modem control line test failed. Description: The modem control line test failed. Description: The data wrap communications test failed. Description: The data wrap communications test failed.) Description: The data wrap communication test failed. Description: The modem control line test failed. use Chapter 11. Description: The modem control line test failed. Description: Cannot run the test because the device driver detected a hardware error while running the Printer/Terminal cable wrap test.

Description: FIFO empty bit set. use Chapter 11. SRNs 700-102 through 89c-302 433 . otherwise. Action: Run diagnostics from a source other than from the disk or a network.) Description: Could not do the test because the device driver detected a hardware error. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Description: SCSI FIFO underflow. D D D D Failing Function Codes D56 D56 D56 software 836 Description and Action (Unless otherwise indicated. Description: FIFO empty bit clear. Description: SCSI parity error. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Description: The adapter failed to configure. otherwise. use MAP 210 with a FFC of 836. suspect a software problem. Description: FIFO data miscompare. Description: The data wrap communication test failed. Description: An unexpected error occurred that can be attributed to software or hardware. use MAP 210 with a FFC of 836. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Action: Run diagnostics from a source other than from the disk or a network. “MAP 0210: General Problem Resolution” on page 67. otherwise. Description: The modem control line test failed. Description: FIFO full bit set.Service Request Number 836-481 836-482 836-483 836-901 to 836-920 SRN Src. Description: SCSI FIFO data miscompare. Action: Run diagnostics from a source other than from the disk or a network. 836-921 836-922 to 836-924 D D 836 software software 836 836-925 836-926 to 836-943 D D 836 software software 836 840-101 840-102 840-103 840-212 840-213 840-214 840-215 840-216 840-217 840-218 840-219 840-220 D D D D D D D D D D D D 221 293 840 221 840 840 840 840 840 840 840 840 840 Chapter 32. suspect a software problem. use MAP 210 with a FFC of 836. Description: An unexpected error occurred that can be attributed to software or hardware. Description: Enhanced error handling failure on a PCI-PCI Bridge. Description: Enhanced error handling failure on the bus. Description: SCSI FIFO flags error. Description: The adapter failed to configure. Description: Enhanced error handling failure on the adapter. Description: FIFO full bit clear. Description: An unexpected error occurred that can be attributed to software or hardware. suspect a software problem.

“MAP 0050: SCSI Bus Problems” on page 51. use the SRN to resolve the problem. Description: Error during the write/read of the memory register. Description: Error log analysis indicates a PCI SCSI adapter failure. “MAP 0050: SCSI Bus Problems” on page 51. Action: Go to Chapter 8.Service Request Number 840-221 840-222 840-223 SRN Src. “MAP 0050: SCSI Bus Problems” on page 51. “MAP 0050: SCSI Bus Problems” on page 51. If an SRN is reported. Action: Go to Chapter 8. “MAP 0050: SCSI Bus Problems” on page 51. Action: Go to Chapter 8. Description: SCSI wrap or PTC failure. 840 221 840 Description: The parent device open failed. Action: Go to Chapter 8. Description: Function could not complete. Action: Go to Chapter 8. Description: SCSI bus data miscompare. If an SRN is not reported. Description: Error log analysis indicates that multiple attempts to reset the SCSI bus have timed out. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. 840-224 840-225 840-226 840-227 840-230 840-231 840-232 840-240 840-242 840-301 840-701 840-801 D D D D D D D D D D G G 840 221 840 840 221 Description: SCSI adapter test failure. D D D Failing Function Codes 840 221 840 840 Description and Action (Unless otherwise indicated. Description: Adapter POST failed. “MAP 0050: SCSI Bus Problems” on page 51. If an SRN is not reported. Description: No terminal power. “MAP 0210: General Problem Resolution” on page 67. “MAP 0050: SCSI Bus Problems” on page 51. Description: Miscompare during the write/read of the memory I/O register. Action: Run the diagnostics on the adapter in System Verification mode. Description: SCSI configuration register read or write error.) Description: Miscompare during the write/read of the configuration register. Action: Go to Chapter 8. Description: Arbitration test failed. use the SRN to resolve the problem. Description: SCSI bus error. Action: Run the diagnostics on the adapter in System Verification mode. 840-802 G 434 Diagnostic Information for Multiple Bus Systems . use Chapter 11. Description: Error log analysis indicates a terminator problem. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. Action: Go to Chapter 8. If an SRN is reported.

844-xxx series 845-xxx series 846-xxx series 868-101 868-102 868-103 868-110 868-130 868-140 868-150 868-160 868-170 868-180 868-190 868-191 868-192 868-193 868-194 868-200 868-201 868-202 868-203 D D D D D D D D D D D D D D G G G G D D D D 844 845 846 221 293 868 221 221 279 868 868 868 868 279 868 221 868 221 279 868 868 868 868 868 Description: A 7135 controller problem is indicated. Description: The adapter command timed out. SRNs 700-102 through 89c-302 435 . If an SRN is not reported. If an SRN is reported. Description: Analysis of the error log indicates a problem with the hardware. Description: A software error was caused by a hardware failure. Action: Run the diagnostics on the adapter in System Verification mode. Description: Analysis of the error log indicates a problem with the hardware. Description: The internal/external reset test failed. Action: Use 7135 documentation. Description: The control logic failed. Action: Use 7135 documentation.Service Request Number 840-803 SRN Src. Description: The wrap test failed. Description: The BCR registers write/read test failed. use the SRN to resolve the problem. Description: Enhanced error handling failure on the adapter. use Chapter 11. Description: A 7135 DASD drawer problem is indicated. Chapter 32. Description: A 7135 DASD drawer problem is indicated. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. Description: Adapter RAM error. Description: The control logic failed. Description: The POS registers write/read test failed. G Failing Function Codes Description and Action (Unless otherwise indicated. Description: The adapter diagnostic subcommand test failed. Description: Enhanced error handling failure on the bus. Action: Use 7135 documentation. “MAP 0210: General Problem Resolution” on page 67.) Description: Error log analysis indicates that multiple SCSI bus errors have occurred. Description: Analysis of the error log indicates a problem with the hardware. Note: Check the fuse before replacing. Description: ROM CRC error. Description: Analysis of the error log indicates a problem with the hardware. Description: The adapter fuse test failed. Description: Enhanced error handling failure on a PCI-PCI Bridge.

Description: Diagnostics completed with a previous error. “MAP 0050: SCSI Bus Problems” on page 51. Description: Error during the write/read of the memory register. “MAP 0050: SCSI Bus Problems” on page 51. Description: The control logic failed. 868-212 868-213 868-214 868-215 868-216 868-217 868-218 868-219 868-220 868-221 868-222 868-223 D D D D D D D D D D D D Description: FIFO empty bit set. Description: FIFO full bit set. 436 Diagnostic Information for Multiple Bus Systems . Action: Go to Chapter 8. Description: Adapter POST failed. Description: SCSI FIFO underflow. 868-224 868-225 868-226 868-227 868-230 868-231 868-232 868-240 868-242 D D D D D D D D D 868 221 868 868 221 Description: SCSI adapter test failure. Action: Go to Chapter 8. Description: The device failed to configure.) Description: The control logic failed. Description: SCSI FIFO flags error. Action: Go to Chapter 8. Description: Function could not complete. Description: No terminal power. Description: FIFO full bit clear. Description: Miscompare during the write/read of the configuration register. Action: Go to Chapter 8. Description: SCSI bus error. Description: SCSI configuration register read or write error. Description: Miscompare during the write/read of the memory I/O register. “MAP 0050: SCSI Bus Problems” on page 51. Description: Arbitration test failed. Action: Go to Chapter 8.Service Request Number 868-204 868-205 868-206 868-211 SRN Src. Action: Go to Chapter 8. Description: FIFO data miscompare. Description: SCSI bus data miscompare. Description: SCSI FIFO data miscompare. “MAP 0050: SCSI Bus Problems” on page 51. use Chapter 11. “MAP 0210: General Problem Resolution” on page 67. D D D D Failing Function Codes 868 868 868 279 868 software 868 868 868 868 868 868 868 868 868 868 221 868 868 Description and Action (Unless otherwise indicated. “MAP 0050: SCSI Bus Problems” on page 51. “MAP 0050: SCSI Bus Problems” on page 51. Description: FIFO empty bit clear. Action: Go to Chapter 8. Description: SCSI wrap or PTC failure. “MAP 0050: SCSI Bus Problems” on page 51. Description: SCSI parity error.

Description: External loopback fairness test failed. Description: Ethernet loopback (twisted pair) fairness test failed. Description: Local RAM test failed. Action: Run the diagnostics on the adapter in System Verification mode. If an SRN is not reported. Description: External loopback test failed.) Description: Configuration open failed for parent bus. Description: External loopback fairness and parity tests failed. use the SRN to resolve the problem. If an SRN is reported. Description: External loopback parity tests failed. Action: Run the diagnostics on the adapter in System Verification mode. Description: I/O register test failed. Chapter 32. Description: Error log analysis indicates a PCI SCSI adapter failure. Description: Vital Product Data (VPD) failed. Description: External loopback (twisted pair) test failed. SRNs 700-102 through 89c-302 437 . If an SRN is not reported. Description: Error log analysis indicates that multiple SCSI bus errors have occurred. 868-802 G 868-803 G 887-101 887-102 887-103 887-104 887-105 887-106 887-107 887-108 887-109 887-110 887-111 887-112 887-113 887-114 887-115 D D D D D D D D D D D D D D D 887 887 887 887 887 887 887 887 887 887 887 887 887 887 887 Description: POS register test failed. Action: Run the diagnostics on the adapter in System Verification mode. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. Description: External loopback (twisted pair) parity test failed. Description: External loopback test failed. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. use Chapter 11. “MAP 0210: General Problem Resolution” on page 67. If an SRN is reported. Description: External loopback (twisted pair) fairness and parity tests failed. Description: LAN coprocessor internal tests failed. If an SRN is reported.Service Request Number 868-301 868-701 868-801 SRN Src. use the SRN to resolve the problem. D G G Failing Function Codes 868 221 868 Description and Action (Unless otherwise indicated. use the SCSI service hints in “General SCSI Configuration Checks” on page 3 to resolve the problem. Description: Error log analysis indicates that multiple attempts to reset the SCSI bus have timed out. Description: Internal loopback test failed. If an SRN is not reported. use the SRN to resolve the problem. Description: Error log analysis indicates a terminator problem.

Description: Unable to reserve device. Description: External loopback test failed. Description: Internal loopback test failed. Description: RJ-45 converter test failed. Description: Vital product data test failed. Description: Device configuration fails.) Description: Twisted pair wrap data failed. Description: Circuit breaker for Ethernet test failed. Description: Vital product data test failed. Description: The CD-ROM drive indicates an error. D G G D D D D D D D D D D D D D F 887 887 software 887 887 887 887 887 887 887 887 887 software 887 887 B09 887 B08 887 C29 887 Ethernetnetwork 887 89c B88 89c B88 89c B88 89c 89c 89c-111 89c-112 89c-113 89c-121 89c-122 D D D D D 438 Diagnostic Information for Multiple Bus Systems . Description: The CD-ROM drive indicates an error. Description: Unable to do configuration. Description: RJ-45 converter test failed. Description: Rerun diagnostics in advanced mode for accurate problem determination. D D D D D Failing Function Codes 887 887 software 887 887 B08 B09 Description and Action (Unless otherwise indicated. Description: Ethernet 10 Base-T transceiver test failed. use Chapter 11. Description: Internal loopback test failed. Description: Ethernet transceiver test failed. Description: Fuse test failed. Description: Fuse test failed. Description: Error log indicates a hardware problem. Description: Internal loopback test failed. Description: Device driver indicates a hardware problem. “MAP 0210: General Problem Resolution” on page 67.Service Request Number 887-116 887-117 887-118 887-120 887-121 887-122 887-123 887-124 887-125 887-202 887-203 887-209 887-304 887-305 887-306 887-307 887-319 887-400 887-401 887-402 887-403 887-404 887-405 SRN Src. Description: Unable to open the device driver. Description: Coprocessor internal test failed. Description: Ethernet 10 Base-2 transceiver test failed. Description: Device driver indicates a hardware failure. Description: Ethernet 10 Base-2 transceiver test failed. Description: Device driver indicates a hardware problem.

Description: Unable to open device driver. Description: Unable to reserve device. Description: The CD-ROM drive indicates an error.) Description: The CD-ROM drive indicates an error. Description: A command reservation conflict was detected. Description: A media error was detected. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error. Description: Errors found during ELA. Description: Errors found during ELA. Description: No tone during audio test. Chapter 32. Description: The CD-ROM drive indicates an error. Description: The LED test failed. use Chapter 11. Description: The CD-ROM drive indicates an error. Description: Unable to do configuration. Description: The CD-ROM drive indicates an error. D D D D D D D Failing Function Codes 89c 89c B88 89c 89c 89c 89c TestDisc 89c 89c D88 89c 89c 89c 89c 89c 89c 89c B88 89c 89c 89c 89c 89c B88 Description and Action (Unless otherwise indicated. Description: Undefined error detected. SRNs 700-102 through 89c-302 439 . “MAP 0210: General Problem Resolution” on page 67. Description: The CD-ROM drive indicates an error. Description: Undefined error detected. 89c-151 89c-152 89c-162 89c-171 89c-172 89c-173 89c-175 89c-198 89c-199 89c-211 89c-281 89c-301 89c-302 D D D D D D D D D D D G G Description: A command timeout was detected.Service Request Number 89c-123 89c-125 89c-126 89c-127 89c-128 89c-129 89c-150 SRN Src.

440 Diagnostic Information for Multiple Bus Systems .

900-002 900-007 900-009 900-064 900-101 900-102 900-103 900-128 900-161 900-191 900-193 900-1FF 900-201 900-202 900-203 900-211 900-212 900-215 900-217 900-233 D D D D D D D D D D D D D D D D D D D D Description: ″NO″ to cursor panel. Service Request Number 900-001 SRN Src. Description: Image transfer across Plane Test failed. Description: OPEN_RCM_ERROR. Description: TRIO64V+_TIMEOUT. Description: 9 x 7 Cross hatch grid failed. Description: Red screen error. Description: The EMC_SCROLLING_21_H_TEST failed.Chapter 33. Description: MALLOC_ERROR. Description: Loop count value in rules file is zero. Description: The EMC_SCROLLING_17_H_TEST failed. use Chapter 11. “MAP 0210: General Problem Resolution” on page 67. Description: INTERNAL_ERROR_DATA_SIZE. Description: Black screen error. D Failing Function Codes 900 227 Monitor 900 Monitor Info code Info code 900 227 900 227 900 227 900 227 software 900 software 900 227 900 227 900 227 900 227 900 227 900 227 software software 900 227 900 227 software Description and Action (Unless otherwise indicated. Description: Green screen error. Description: Clipping error. Description: Clipping error. 441 . Description: Rectangle fill test failed. Description: Color miscompare. Description: Color miscompare. SRNs 900-001 through xxxxxxx Note: Some SRNs in this chapter may have 4 rather than 3 digits after the dash (-).) Description: ″NO″ to color panel. Description: INTERNAL_ERROR_NO_ACCESS. Description: Rectangle fill test failed.

D D D D D D D D D D D D D D D D D D D D D D D D Failing Function Codes software software software software Info code Info code 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 Info code Info code 900 227 Description and Action (Unless otherwise indicated. Description: A write of ″0x2A″ to the palette register failed. Description: Miscompare found in VRAM. use Chapter 11. Description: A write of ″0x00″ to the palette register failed. Description: AIXGSC_MAKE_GP_FAILED. Description: Green screen error.) Description: IOCTL_GSC_HANDLE_FAILED. Description: The SCROLLING_21_H_TEST failed. Description: 9 x 7 Cross hatch grid failed. Description: The SCROLLING_17_H_TEST failed. Description: The test of the palette registers failed. Description: The test of the VRAM failed. Description: The SCROLLING_17_H_TEST failed.Service Request Number 900-234 900-235 900-236 900-237 900-241 900-263 900-2FF 900-301 900-302 900-303 900-304 900-305 900-3FF 900-401 900-402 900-403 900-404 900-447 900-449 900-471 900-473 900-495 900-497 900-4FF SRN Src. Description: Frame buffer base address inconsistent. 442 Diagnostic Information for Multiple Bus Systems . Description: AIXGSC_UNMAKE_GP_FAILED. Description: A write of ″0x3F″ to the palette register failed. Description: DEVICE_BUSY_ERROR. Description: The test of the palette registers failed. Description: VRAM inaccessible. Description: The test of the VRAM failed. Description: The EMC_SCROLLING_21_H_TEST failed. Description: A write of ″0x15″ to the palette register failed. Description: Blue Screen error. “MAP 0210: General Problem Resolution” on page 67. Description: Image transfer across Plane Test failed. Description: 11 x 9 Cross hatch grid failed.

Description: 45 Degree Short Stroke Draw failed. Description: Direct Frame Buffer test failed. Description: 11 x 9 Cross hatch grid failed. Description: Bad vector detected. Description: 135 Degree Short Stroke Draw failed. D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 Info code Info code 900 227 software 900 227 Description and Action (Unless otherwise indicated. use Chapter 11. Description: Clipping error. or 180 Degree Short Stroke Draw failed. Description: Blue Screen error. or 90 Degree Short Stroke Draw failed.) Description: Color miscompare. “MAP 0210: General Problem Resolution” on page 67. Description: 225 Degree Short Stroke Draw failed. Description: Video Stream hardware test failed. Description: Video Stream Register test failed. Description: Direct Frame Buffer test failed. Description: 270 Degree Short Stroke Draw failed. Description: Video Stream hardware test failed. Description: The EMC_SCROLLING_17_H_TEST failed. Description: 315 Degree Short Stroke Draw failed. Description: White screen error. Description: Short Stroke Vector Function test failed. Description: The SCROLLING_21_H_TEST failed.Service Request Number 900-501 900-502 900-503 900-5FF 900-601 900-602 900-6FF 900-701 900-702 900-703 900-704 900-705 900-706 900-707 900-708 900-709 900-727 900-750 900-753 900-7FE 900-7FF SRN Src. Description: 0 Degree Short Stroke Draw failed. Chapter 33. Description: Short Stroke Vector Function test failed. SRNs 900-001 through xxxxxxx 443 .

Description: Clipping error of white boxes detected. Description: Color miscompare of white boxes detected. Description: Clipping error of white boxes detected. Description: The Area fill test (color bars) failed. Description: Pattern Fill Across the Plane test failed.Service Request Number 900-801 900-802 900-803 900-804 900-805 900-8FF 900-901 900-902 900-903 900-904 900-905 900-906 900-907 900-908 900-909 900-937 900-959 900-961 900-9FF 900-A01 900-A02 SRN Src. use Chapter 11. “MAP 0210: General Problem Resolution” on page 67. Description: Color miscompare of color bars detected. Description: The Area fill test (color bars) failed. D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 Description and Action (Unless otherwise indicated. Description: Clipping miscompare of white boxes detected. Description: Clipping error of white boxes detected. Description: Clipping for PatBlt thru screen failed. Description: White screen error. Description: Color for PatBlt Across screen failed. Description: Pattern Fill Across the Plane test failed. 444 Diagnostic Information for Multiple Bus Systems . Description: Clipping error of horizontal top line.) Description: Color for PatBlt thru screen failed. Description: Black screen error. Description: Color miscompare of white boxes detected. Description: Red screen error. Description: Color miscompare of horizontal top line. Description: Clipping for PatBlt Across screen failed. Description: Color miscompare of white boxes detected.

Description: Reserved. Description: Color miscompare of horizontal bottom line. Description: Color miscompare of horizontal center line. Description: Clipping error of textured top line. Description: Clipped Area Vertical color miscompare (background line color wrong).Service Request Number 900-A03 900-A04 900-A05 900-A06 900-A07 900-A08 900-A09 900-A0A 900-A0B 900-A0C 900-A0D 900-A0F 900-A10 900-A11 900-A12 900-AFF 900-B01 900-B02 900-B03 900-B04 900-B05 SRN Src. Description: Rectangle Area Color miscompare detected. Description: Clipped Area Horizontal color miscompare (background line color wrong). Description: Rectangle Area Clip error detected. Description: Line Drawing Function test failed. Description: Color miscompare of vertical center line. Description: Clipping error of vertical right line. D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 Description and Action (Unless otherwise indicated. use Chapter 11. Description: Clipping error of vertical center line. Chapter 33. “MAP 0210: General Problem Resolution” on page 67. Description: Clipped Area Horizontal clip miscompare (clip of background line wrong).) Description: Color miscompare of vertical right line. Description: Clipping error of horizontal center line. Description: Reserved. Description: Clipping error of vertical left line. Description: Color miscompare of textured top line. Description: Color miscompare of vertical left line. Description: Clipping error of horizontal bottom line. SRNs 900-001 through xxxxxxx 445 . Description: Line Drawing Function test failed.

Description: Vendor display problem. Refer to the service documentation for this device. “MAP 0210: General Problem Resolution” on page 67. Description: The HW cursor function test failed. Refer to the service documentation for this device. Refer to the service documentation for this display. Description: The clipping function test failed. use Chapter 11. Description: Vendor device problem. Description: The clipping function test failed. Description: The BIOS function test failed. Description: Vendor Async device problem. 908-112 D Description: DMA failed to complete a transfer. Description: The BIOS function test failed. Refer to the service documentation for this device. Description: The BIOS read failed. 908-111 D Description: Loader check sum error. D D D D D D D D Failing Function Codes 900 227 900 227 900 227 900 227 900 227 900 227 900 227 900 227 Description and Action (Unless otherwise indicated. Description: The HW cursor function test failed.) Description: Clipped Area Vertical clip error (clip of background line wrong). Description: Vendor SCSI device problem.Service Request Number 900-B06 900-B07 900-BFF 900-C01 900-C02 900-CFF 900-D01 900-DFF 901-xxx 902-xxx 903-xxx 904-xxx 905-xxx 908-001 to 908-010 908-016 to 908-019 908-020 SRN Src. Description: MCIC failed reading header. Refer to the service documentation for this device. 446 Diagnostic Information for Multiple Bus Systems . D D C33 908 C36 908 C33 C36 C33 908 C36 C34 Description: Error closing 7250 DD. Description: Vendor Parallel device problem. D 908 C33 C48 908 Description: Invalid function request or bad parameters passed.

D Description: DMA transfer or PFCA data error. D Failing Function Codes 908 C33 C36 C33 908 C36 908 C33 C36 908 Description and Action (Unless otherwise indicated. D Description: Base 16M CHAP0 SIMM bad. D Description: CP NMI bus timeout interrupt error. 908-200 to 908-254 908-255 D Description: GPSS board failure. D 908 C33 System C36 C33 908 C36 C33 C34 908 C48 C33 908 C36 C33 908 C34 C48 C33 908 C36 C34 C33 C48 C35 C34 C44 C34 C33 C48 C46 D66 Description: 7250 is not available. 908-114 to 908-118 908-120 to 908-150 908-151 to 908-158 908-160 D Description: Errors in loading ASCII registers.Service Request Number 908-113 SRN Src. D Description: SPAN board error.) Description: Errors in loading ASCII registers. 908-256 to 908-454 908-455 D Description: GPSS board failure. Chapter 33. SRNs 900-001 through xxxxxxx 447 . D Description: BLT or RATTLER error. D Description: VOO feature error. 908-456 to 908-699 908-700 to 908-766 908-767 to 908-769 908-770 to 908-799 908-800 D Description: GPSS board failure. use Chapter 11. D Description: CP NMI bus timeout interrupt error. “MAP 0210: General Problem Resolution” on page 67. D Description: RSS BIST failure.

Description: RSS AG 16M CHAP0 SIMM bad (802). Description: RSS AG 12M CHAP3 SIMM bad (818).Service Request Number 908-801 908-802 908-803 908-804 908-805 908-806 908-807 908-808 908-809 908-810 908-811 908-812 908-813 908-814 908-815 908-816 908-817 908-818 908-819 908-820 908-821 SRN Src. Description: RSS AG 12M CHAP2 SIMM bad (813). Description: RSS AG 16M CHAP2 SIMM bad (812). Description: RSS base 12M CHAP4 SIMM bad (821). Description: Base 16M CHAP 1 SIMM bad (805). 448 Diagnostic Information for Multiple Bus Systems . Description: RSS AG 12M CHAP1 SIMM bad (808). Description: RSS base 12M CHAP2 SIMM bad (811). Description: RSS AG 16M CHAP3 SIMM bad (817). D D D D D D D D D D D D D D D D D D D D D Failing Function Codes C45 D66 C46 D66 C45 D66 C47 D66 C46 D66 C45 D66 C46 D66 C45 D66 C47 D66 C46 D66 C45 D66 C46 D66 C45 D66 C47 D66 C46 D66 C45 D66 C46 D66 C45 D66 C47 D66 C46 D66 C45 D66 Description and Action (Unless otherwise indicated.) Description: RSS base 12M CHAP0 SIMM bad (801). Description: RSS TX 16M CHAP1 SIMM bad (809). Description: RSS base 12M CHAP3 SIMM bad (816). Description: RSS AG 16M CHAP1 SIMM bad (807). “MAP 0210: General Problem Resolution” on page 67. Description: RSS base 16M CHAP3 SIMM bad (815). Description: RSS TX 16M CHAP3 SIMM bad (819). Description: RSS TX 16M CHAP2 SIMM bad (814). Description: RSS base 12M CHAP1 SIMM bad (806). Description: RSS base 16M CHAP4 SIMM bad (820). Description: RSS base 16M CHAP2 SIMM bad (810). use Chapter 11. Description: RSS AG 12M CHAP0 SIMM bad (803). Description: RSS TX 16M CHAP0 SIMM bad (804).

D Description: VOO error. and application software to be sure they are all compatible.) Description: RSS AG 16M CHAP4 SIMM bad (822). D D66 C33 C48 C35 D66 C48 D66 C33 C48 912 912 912 912 912 912 912 912 Description: RSS error. Action: Check the levels of the device. Description: The bus test failed. Chapter 33. Description: A SCSI check condition error. Description: RSS AG 12M CHAP4 SIMM bad (823). Description: An unrecoverable hardware error. Description: A protocol error. D D D D D D D D D Description: An unrecoverable media error.Service Request Number 908-822 908-823 908-824 908-825 908-830 to 908-870 908-871 to 908-899 908-900 to 908-966 908-967 to 908-969 908-970 to 908-999 912-102 912-104 912-105 912-106 912-108 912-110 912-112 912-114 912-116 SRN Src. Description: The media format is corrupted. Description: The electronics card test failed. use Chapter 11. Description: A SCSI busy or command error. 912-117 912-118 912-120 912-122 912-124 D D D D D 912 912 B88 912 912 912 Description: A write-protect error occurred. Description: The motor failed to restart. D D66 Description: RSS error. Description: The drive did not become ready. D D D D D Failing Function Codes C46 D66 C45 D66 C47 D66 C34 C34 Description and Action (Unless otherwise indicated. “MAP 0210: General Problem Resolution” on page 67. If you do not find a problem. SRNs 900-001 through xxxxxxx 449 . Description: The diagnostic test failed. D Description: RSS error. call your support person. Description: Multiple SIMMs failed. adapter. Description: A SCSI command time-out. diagnostic software. Description: RSS TX 16M CHAP4 SIMM bad (824). Description: RSS error. Description: A SCSI reservation conflict error.

use Chapter 11. Description: A SCSI reservation conflict error. Description: A protocol error. If you do not find a problem. Description: The diagnostic test failed. Description: The media format is corrupted. Description: A SCSI check condition error. Description: An unrecoverable hardware error. 913-102 913-104 913-105 913-106 913-108 913-110 913-112 913-114 913-116 D D D D D D D D D 913-117 913-118 913-120 913-122 913-124 913-126 913-128 D D D D D D G 913 913 B88 913 913 913 913 B88 913 Description: A write-protect error occurred. Description: The bus test failed. call your support person. Action: Check the levels of the device. Description: The adapter failed to configure. Description: Error log analysis indicates a SCSI bus problem. “MAP 0210: General Problem Resolution” on page 67. 912-130 912-132 912-134 912-137 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: A SCSI command time-out. adapter. Description: A software error was caused by a hardware failure. Description: A disk drive hardware error occurred. 450 Diagnostic Information for Multiple Bus Systems . Description: The error log analysis indicates a hardware failure.Service Request Number 912-126 912-128 912-129 SRN Src. Description: The error log analysis indicates a hardware failure.) Description: A software error was caused by a hardware failure. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The electronics card test failed. and application software to be sure they are all compatible. Description: The motor failed to restart. Description: The drive did not become ready. D G G Failing Function Codes 912 B88 912 190 912 B88 software 912 912 B88 software 912 B88 190 913 913 913 913 913 913 913 913 Description and Action (Unless otherwise indicated. diagnostic software. Description: An unrecoverable media error. Description: A SCSI busy or command error.

use Chapter 11. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The Read. Description: The Unload command failed. G Failing Function Codes 190 913 B88 software 913 913 B88 software 913 B88 190 914 914 914 media 914 media 914 914 media 914 media 914 B88 media 914 media 914 media 914 914 media 914 B88 914 914 914 914 software Description and Action (Unless otherwise indicated. 914-110 914-120 914-130 914-135 914-140 914-150 914-160 914-170 D D D D D D D D 914-180 914-185 914-190 914-200 914-210 914-220 914-230 914-240 914-300 D D D D D D D D D Description: The Load command failed. 913-130 913-132 913-134 913-137 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function.) Description: Error log analysis indicates a SCSI bus problem. Description: The Send Diagnostic command failed. Description: The Mode Select command failed. Description: The adapter failed to configure. Description: The Load command failed. Description: The Reserve command failed. Description: The Openx command failed. Description: The Unload command failed. Description: The Test Unit Ready command failed. Description: A disk drive hardware error occurred. Write and Compare test failed.Service Request Number 913-129 SRN Src. Description: The Mode Select command failed. Description: The Inquiry command failed. Description: The Test Unit Ready command failed. SRNs 900-001 through xxxxxxx 451 . Chapter 33. Description: The device configuration failed. “MAP 0210: General Problem Resolution” on page 67. Description: The Request Sense command failed. Description: The device configuration failed. Description: The Release command failed.

) Description: SCSI adapter configuration failed. Description: The Mode Select command failed. 914-320 914-411 to 914-423 914-511 to 914-523 914-611 to 914-623 914-711 to 914-723 915-110 915-120 915-130 915-135 915-140 915-150 915-160 915-169 915-170 G D Description: Error log analysis indicates a failure. D D Description: A device timeout error occurred. Description: A reservation conflict occurred. D Failing Function Codes B88 914 software 914 media 914 B88 software 914 B88 914 B88 software 914 B88 software 915 915 915 media 915 media 915 915 media 915 media 915 media 915 B88 media 915 media 915 media 915 915 media 915 B88 Description and Action (Unless otherwise indicated. Description: The Send Diagnostic command failed. Description: The device configuration failed. Description: The Send Diagnostic command failed. Description: The Test Unit Ready command failed. Description: An adapter or bus I/O error occurred. Description: The Read. Description: The Mode Select command failed. “MAP 0210: General Problem Resolution” on page 67. Description: The Test Unit Ready command failed. 452 Diagnostic Information for Multiple Bus Systems . D D D D D D D D D Description: The Reserve command is corrupted. use Chapter 11. 915-180 915-185 915-190 915-200 915-210 D D D D D Description: The Load command failed. Description: The Unload command failed. Description: The Load command failed. D Description: The drive returned bad or non-extended sense data. Write and Compare test failed. Description: The Inquiry command failed. Description: The Unload command failed.Service Request Number 914-310 SRN Src.

D Description: The drive returned bad or non-extended sense data. Chapter 33. 915-320 915-411 to 915-423 915-511 to 915-523 915-611 to 915-623 915-711 to 915-723 917-102 917-104 917-105 917-106 917-108 917-110 917-112 917-114 917-116 G D Description: Error log analysis indicates a failure. adapter. Description: SCSI adapter configuration failed. Description: The motor failed to restart. Description: A reservation conflict occurred. Description: The diagnostic test failed. D D Description: A device timeout error occurred. Description: The Openx command failed. Description: The electronics card test failed. Description: The device configuration failed. Description: A protocol error. Description: A SCSI command time-out.Service Request Number 915-220 915-230 915-240 915-300 915-310 SRN Src. use Chapter 11. SRNs 900-001 through xxxxxxx 453 . call your support person. diagnostic software. Description: A SCSI reservation conflict error. Description: The drive did not become ready. Description: A SCSI busy or command error. D D D D D Failing Function Codes 915 915 915 915 software B88 915 software 915 media 915 B88 software 915 B88 915 B88 software 915 B88 software 917 917 917 917 917 917 917 917 Description and Action (Unless otherwise indicated. Description: The media format is corrupted. D D D D D D D D D Description: An unrecoverable media error. Action: Check the levels of the device. Description: An adapter or bus I/O error occurred.) Description: The Replace command failed. 917-117 917-118 917-120 917-122 917-124 D D D D D 917 917 B88 917 917 917 Description: A write-protect error occurred. Description: A SCSI check condition error. Description: An unrecoverable hardware error. “MAP 0210: General Problem Resolution” on page 67. If you do not find a problem. Description: The bus test failed. Description: The Request Sense command failed. and application software to be sure they are all compatible.

917-136 917-137 D D Description: The certify operation failed. Description: A disk drive hardware error occurred. “MAP 0210: General Problem Resolution” on page 67. adapter. Description: The media format is corrupted. Description: The adapter failed to configure. Description: A SCSI reservation conflict error. Description: The diagnostic test failed. Description: The device failed to configure. 918-102 918-104 918-105 918-106 918-108 918-110 918-112 918-114 918-116 D D D D D D D D D 918-117 918-118 918-120 918-122 918-124 918-126 D D D D D D 918 918 B88 918 918 918 918 B88 Description: A write-protect error occurred. Description: The drive did not become ready. and application software to be sure they are all compatible. use Chapter 11. Description: A SCSI check condition error. Description: The motor failed to restart. D G G Failing Function Codes 917 B88 917 190 917 B88 software 917 917 B88 software 917 B88 software 917 917 B88 190 918 918 918 918 918 918 918 918 Description and Action (Unless otherwise indicated.) Description: A software error was caused by a hardware failure. Description: An unrecoverable media error. 454 Diagnostic Information for Multiple Bus Systems . Description: A software error was caused by a hardware failure. Action: Check the levels of the device. 917-130 917-132 917-134 917-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function.Service Request Number 917-126 917-128 917-129 SRN Src. Description: The error log analysis indicates a hardware failure. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The bus test failed. Description: An unrecoverable hardware error. If you do not find a problem. Description: A SCSI busy or command error. call your support person. Description: Error log analysis indicates a SCSI bus problem. Description: A protocol error. diagnostic software. Description: A SCSI command time-out. Description: The electronics card test failed.

Description: An unexpected adapter error occurred. Chapter 33. Description: An unexpected device or adapter error occurred. SRNs 900-001 through xxxxxxx 921-101 921-102 921-103 921-104 921-105 921-106 921-201 921-202 921-203 921-204 921-205 921-206 921-301 921-302 921-303 D D D D D D D D D D D D D D D 455 . Description: An unexpected adapter error occurred. Description: The keyboard echo test failed. Description: The adapter failed to configure. Description: Unknown keyboard. “MAP 0210: General Problem Resolution” on page 67. Description: An error occurred in turning on the lamps. 918-130 918-132 918-134 918-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: An unexpected adapter error occurred. Description: The keyboard light-off test failed. Description: The keyboard light-on test failed. Description: A disk drive hardware error occurred. Description: The keyboard reset failed. Description: Error log analysis indicates a SCSI bus problem.Service Request Number 918-128 918-129 SRN Src. Description: An unexpected device or adapter error occurred. Description: An unexpected device or adapter error occurred. G G Failing Function Codes 918 190 918 B88 software 918 918 B88 software 918 B88 software 918 918 B88 190 821 921 821 921 821 921 921 821 921 821 821 921 821 921 821 921 921 821 921 821 821 921 821 921 Description and Action (Unless otherwise indicated. Description: The read keyboard ID test failed. Description: The device failed to configure. Description: The keyboard layout ID test failed. Description: Unit attention condition has occurred on the Send Diagnostic command.) Description: The error log analysis indicates a hardware failure. use Chapter 11. 918-136 918-137 D D Description: The certify operation failed. Description: The select scan code set test failed.

Description: Unable to recognize the keyboard. Description: An unexpected adapter error occurred. Description: An unexpected device or adapter error occurred. Description: The keyboard reset failed. Description: The auto-click cannot be enabled. Description: Unknown keyboard. Description: The auto-click cannot be disabled. Description: An unexpected device or adapter error occurred.Service Request Number 921-304 921-401 921-402 921-403 921-404 921-501 921-502 921-503 921-504 921-505 921-601 921-602 921-603 921-701 921-901 921-902 921-903 922-101 922-102 922-103 922-104 922-105 922-106 922-201 922-202 922-203 SRN Src. Description: An unexpected device or adapter error occurred. Description: An unexpected device or adapter error occurred. Description: The error log analysis indicates a device failure. Description: The speaker test failed. Description: Error configuring the device. Description: An unexpected adapter error occurred. use Chapter 11. Description: The error log analysis indicates an unknown failure. D D D D D D D D D D D D D D G G G D D D D D D D D D Failing Function Codes 921 821 921 821 921 921 821 821 921 821 921 921 921 821 921 821 921 921 821 821 921 821 921 821 821 922 821 922 821 922 922 821 922 821 821 922 821 922 821 Description and Action (Unless otherwise indicated. Description: An unexpected device or adapter error occurred. 456 Diagnostic Information for Multiple Bus Systems . Description: Unable to recognize the keyboard. Description: The error log analysis indicates an adapter failure. Description: An unexpected adapter error occurred. Description: The keyboard is failing.) Description: An error occurred in turning off the lamps. Description: The keyboard light-off test failed. Description: An unexpected adapter error occurred. Description: The keyboard light-on test failed. “MAP 0210: General Problem Resolution” on page 67. Description: An unexpected adapter error occurred. Description: The read keyboard id test failed.

Description: Error configuring the device. Description: The select scan code set test failed. Description: The auto-click cannot be enabled. Description: An unexpected device or adapter error occurred. Description: An unexpected device or adapter error occurred. Description: The error log indicates an adapter failed. Description: An unexpected device or adapter error occurred. Description: An error occurred in turning off the lamps. Description: Unknown keyboard. Description: The keyboard is failing. Description: The error log indicates a device failed. Description: An unexpected adapter error occurred. Description: An unexpected adapter error occurred. Description: The keyboard reset failed.Service Request Number 922-204 922-205 922-206 922-301 922-302 922-303 922-304 922-401 922-402 922-403 922-404 922-501 922-502 922-503 922-504 922-505 922-601 922-602 922-603 922-701 922-901 922-902 922-903 923-101 923-102 923-103 923-104 SRN Src. Description: The error log analysis indicates an unknown failure. D D D D D D D D D D D D D D D D D D D D G G G D D D D Failing Function Codes 922 922 821 922 821 821 922 821 922 922 821 922 821 922 922 821 821 922 821 921 922 922 821 922 821 922 922 821 821 922 821 922 821 821 923 821 923 821 923 Description and Action (Unless otherwise indicated. Description: An error occurred in turning on the lamps. use Chapter 11. Description: An unexpected adapter error occurred. Description: The speaker test failed. Description: An unexpected device or adapter error occurred. “MAP 0210: General Problem Resolution” on page 67. Description: The keyboard echo test failed. Chapter 33. Description: The auto-click cannot be disabled. Description: An unexpected device or adapter error occurred.) Description: The keyboard layout id test failed. Description: Unable to recognize the keyboard. Description: An unexpected adapter error occurred. Description: Unable to recognize the keyboard. Description: An unexpected adapter error occurred. SRNs 900-001 through xxxxxxx 457 .

Description: An unexpected adapter error occurred. Description: The error log analysis indicates a device failure. Description: Error configuring the device. Description: The keyboard is failing. Description: An unexpected adapter error occurred. Description: An error occurred in turning on the lamps. Description: An unexpected device or adapter error occurred. Description: An error occurred in turning off the lamps. Description: The select scan code set test failed. Description: The read keyboard id test failed. Description: The auto-click cannot be disabled. Description: The speaker test failed. Description: An unexpected device or adapter error occurred. Description: Unable to recognize the keyboard. Description: The keyboard echo test failed. 458 Diagnostic Information for Multiple Bus Systems .) Description: The keyboard light-on test failed. “MAP 0210: General Problem Resolution” on page 67. Description: The auto-click cannot be enabled. Description: An unexpected device or adapter error occurred. Description: An unexpected device or adapter error occurred. Description: An unexpected adapter error occurred. Description: An unexpected adapter error occurred. Description: The keyboard light-off test failed. Description: Unable to recognize the keyboard. Description: An unexpected adapter error occurred. Description: An unexpected device or adapter error occurred. D D D D D D D D D D D D D D D D D D D D D D D D D G G Failing Function Codes 923 821 923 821 821 923 821 923 821 923 923 821 923 821 821 923 821 923 923 821 923 821 923 923 821 821 923 821 923 923 923 821 923 821 923 923 821 821 923 821 Description and Action (Unless otherwise indicated. Description: The keyboard layout id test failed.Service Request Number 923-105 923-106 923-201 923-202 923-203 923-204 923-205 923-206 923-301 923-302 923-303 923-304 923-401 923-402 923-403 923-404 923-501 923-502 923-503 923-504 923-505 923-601 923-602 923-603 922-701 923-901 923-902 SRN Src. Description: The error log indicates an adapter failed. use Chapter 11.

“MAP 0210: General Problem Resolution” on page 67. D D D D D Description: The input device cable is not attached. Description: The Read Status command failed. Description: An unexpected device error occurred. Description: Adapter error. Description: The device disable test failed.) Description: The error log analysis indicates an unknown failure. use Chapter 11. G D D D D D D D D D Failing Function Codes 923 821 925 823 925 823 925 925 823 925 925 925 823 925 823 925 Description and Action (Unless otherwise indicated. Description: The error log analysis indicates a hardware failure. Description: Device. Description: Input device cable is not attached. Chapter 33. D 824 926 Description: Adapter error. SRNs 900-001 through xxxxxxx 459 . Description: Adapter error. Description: Mouse wrap mode failed. Description: Unknown Mouse type. Description: The error log analysis indicates a hardware failure. Description: Error setting mouse parameters. Description: The device test failed. Description: The input device cable is not attached.Service Request Number 923-903 925-111 925-112 925-113 925-114 925-115 925-116 925-117 925-118 925-121 to 925-171 925-200 925-300 925-301 926-104 926-111 926-112 to 926-115 926-116 926-119 926-121 926-131 926-132 to 926-135 926-141 SRN Src. Description: Could not reset the device. Description: Adapter error. Description: Device or adapter error. adapter or tablet reset failed. D G G D D D 925 823 925 925 823 926 159 824 926 824 159 188 824 824 926 926 Description: A software error was caused by a hardware failure. Description: The device test failed.

Description: Device or adapter error. Description: The input device cable is not attached. use Chapter 11. Description: Error in incremental data mode test. Description: The input device cable is not attached. Description: The input device cable is not attached. Description: Device or adapter error. Description: The input device cable is not attached. Description: Error in turning on input device switch. D D D D D D D D D D D D D D D D D D D D D D 159 926 159 926 159 926 159 188 926 188 926 188 926 188 159 926 159 926 159 926 159 188 926 188 926 188 926 188 824 926 159 926 159 926 159 188 926 188 926 Description: Device or adapter error.Service Request Number 926-142 to 926-161 926-162 926-163 926-164 926-165 926-166 926-167 926-168 926-169 926-172 926-173 926-174 926-175 926-176 926-177 926-178 926-179 926-181 926-182 926-183 926-184 926-186 926-187 SRN Src. Description: Error in turning on input device switch. 460 Diagnostic Information for Multiple Bus Systems . Description: Error in turning off input device switch. Description: Device or adapter error.) Description: Device or adapter error. Description: Error in turning off input device LED. Description: The input device cable is not attached. Description: Error in turning off input device LED. Description: Error in turning off input device LED. Description: Adapter error. D Failing Function Codes 926 Description and Action (Unless otherwise indicated. “MAP 0210: General Problem Resolution” on page 67. Description: Device or adapter error. Description: Error in turning on input device LED. Description: Device or adapter error. Description: The incremental data mode test failed. Description: Error in turning off input device switch.

Description: Device or adapter error. Description: Device or adapter error. Description: Error in input device switch test. Description: Input device cable is not attached. Description: Device or adapter error. Description: Error in disabling tablet. Description: The input device cable is not attached. Chapter 33. Description: Adapter error. Description: Error in input device switch test. use Chapter 11. Description: Adapter error. D D D D D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 188 926 824 926 824 926 824 926 824 824 926 824 159 188 926 159 926 159 159 188 926 188 926 188 824 926 159 926 159 926 159 188 926 188 926 188 927 159 824 Description and Action (Unless otherwise indicated. Description: Error in incremental data mode test. Description: Enabled/disabled test failed. Description: Adapter error.) Description: The input device cable is not attached.Service Request Number 926-188 926-203 926-204 926-207 926-208 926-221 926-222 926-225 926-229 926-271 926-272 926-273 926-274 926-276 926-277 926-278 926-281 926-282 926-283 926-284 926-286 926-287 926-288 927-104 927-111 SRN Src. Description: Error in incremental data mode test. Description: Device or adapter error. Description: Enabled/disabled test failed. Description: Device or adapter error. Description: Error in enabling tablet. Description: The input device cable is not attached. Description: The input device cable is not attached. Description: Adapter error. “MAP 0210: General Problem Resolution” on page 67. Description: The input device cable is not attached. Description: The input device cable is not attached. SRNs 900-001 through xxxxxxx 461 . Description: The input device cable is not attached.

Service Request Number 927-112 927-113 927-114 927-115 927-116 927-119 927-121 927-122 927-125 927-131 927-132 927-133 927-134 927-135 927-141 927-142 927-143 927-161 927-162 927-163 927-164 927-165 927-166 927-167 927-168 927-169 SRN Src. 462 Diagnostic Information for Multiple Bus Systems . Description: Device or adapter error. Description: Error in tablet indicator. Description: Error in turning off input device LED. Description: The input device cable is not attached. Description: Adapter error. Description: The input device cable is not attached.) Description: Device or adapter error. Description: Adapter error. D D D D D D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 927 824 927 824 927 824 927 824 159 188 824 927 824 927 824 824 927 927 927 927 927 824 927 927 927 927 159 927 159 927 159 927 159 188 927 188 927 188 927 188 Description and Action (Unless otherwise indicated. Description: Adapter error. Description: Device or adapter error. Description: Device or adapter error. Description: Error in turning off input device LED. Description: The input device cable is not attached. Description: Tablet reset failed. Description: The read status test failed. Description: Error in turning on input device LED. Description: Adapter error. Description: Device or adapter error. Description: The input device cable is not attached. Description: The read status test failed. Description: The input device cable is not attached. Description: The set conversion mode test failed. use Chapter 11. “MAP 0210: General Problem Resolution” on page 67. Description: Device or adapter error. Description: Error in turning on input device LED. Description: The read configuration test failed. Description: The set resolution test failed.

Description: The input device cable is not attached. Description: Error in turning off input device switch. Description: The input device cable is not attached. D D D D D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 927 159 927 159 927 159 927 159 188 927 188 927 188 927 188 824 927 159 927 159 927 159 188 927 188 927 188 927 824 927 824 824 927 824 159 188 927 159 927 159 927 Description and Action (Unless otherwise indicated. Description: Device or adapter error. Description: Error in disabling tablet. Description: Adapter error. Description: Error in incremental data mode test. Description: Device or adapter error. Description: Error in incremental data mode test. Chapter 33. use Chapter 11. Description: Error in turning on input device switch. Description: Device or adapter error. Description: The input device cable is not attached. Description: Error in enabling tablet. Description: Adapter error. Description: Device or adapter error. SRNs 900-001 through xxxxxxx 463 .) Description: Adapter error. Description: Error in turning off input device switch. Description: Error in input device switch test. Description: The input device cable is not attached. Description: Adapter error.Service Request Number 927-171 927-172 927-173 927-174 927-175 927-176 927-177 927-178 927-179 927-181 927-182 927-183 927-184 927-186 927-187 927-188 927-203 927-204 927-221 927-222 927-225 927-229 927-271 927-272 927-273 SRN Src. Description: Device or adapter error. Description: Error in turning on input device switch. “MAP 0210: General Problem Resolution” on page 67. Description: The input device cable is not attached. Description: Device or adapter error. Description: The input device cable is not attached.

Description: Cable test failed. Description: The input device cable is not attached. Description: Unable to turn the lights off hardware failure. Description: Device or adapter failure. Description: Device or adapter error. Description: Failed to register input ring. 464 Diagnostic Information for Multiple Bus Systems . Description: Device or adapter error. Description: The input device cable is not attached. Description: Unable to turn the lights on. Description: Error unconfiguring the device. Description: Cannot set the device to LOW granularity. “MAP 0210: General Problem Resolution” on page 67. Description: Adapter error. Description: Error in input device switch test. Description: Unable to communicate with the device. D D D D D D D D D D D D D D D D D D D D D G G D D D D D D Failing Function Codes 159 188 927 188 927 188 824 927 159 927 159 927 159 188 927 188 927 188 929 929 929 929 929 929 929 software 929 software 929 930 930 930 930 930 930 930 930 930 Description and Action (Unless otherwise indicated.) Description: The input device cable is not attached. Description: Cannot set the device to HIGH granularity. Description: Cannot set the device granularity.Service Request Number 927-274 927-276 927-277 927-278 927-281 927-282 927-283 927-284 927-286 927-287 927-288 929-201 929-202 929-203 929-204 929-210 929-212 929-213 929-299 929-301 930-201 930-210 930-220 930-230 930-241 930-242 930-243 930-261 930-262 SRN Src. Description: Error configuring the device. use Chapter 11. Description: Device or adapter error. Description: Unable to turn the lights off. Description: Unable to turn a single light-on. Description: Unable to read event from the device. Description: Error in incremental data mode test. Description: Device or adapter failure. Description: Error in incremental data mode test. Description: Device or adapter failure. Description: Device or adapter failure. Description: The input device cable is not attached. Description: Cable test failed.

Description: HIPPI Adapter test failed.) Description: Error unconfiguring the device.Service Request Number 930-299 930-301 935-101 to 935-102 935-103 to 935-107 935-108 935-109 to 935-110 935-111 to 935-114 935-115 to 935-121 935-122 935-123 935-124 938-101 938-104 938-105 938-108 938-109 938-10A 938-10B 938-10C SRN Src. D D D Description: The diskette read test failed. Description: HIPPI Adapter test failed. D D D Failing Function Codes software 930 software 930 935 828 935 828 935 935 828 935 Description and Action (Unless otherwise indicated. Chapter 33. Description: Unable to configure the device. Description: HIPPI Adapter test failed. Description: The error log analysis indicates a hardware failure. SRNs 900-001 through xxxxxxx 465 . Description: HIPPI Adapter test failed. Description: HIPPI Adapter test failed. Description: HIPPI Adapter test failed. Description: The diskette failed. Description: The read/write on the diskette drive failed. Description: HIPPI Adapter test failed. use Chapter 11. Description: Error configuring the device. D 935 828 935 828 935 935 software 938 227 938 227 938 227 938 227 938 227 938 227 938 227 WrapPlug 938 Description: The diskette drive test failed. Description: The diskette-drive select or deselect test failed. “MAP 0210: General Problem Resolution” on page 67. Description: HIPPI Adapter test failed. G G D D D D D D D D D Description: The error log analysis indicates a hardware failure. D Description: A diskette drive test failed.

D G G 990 B88 990 950 B88 software 990 B88 software 990 946 227 946 946 227 946 227 946 227 946 945-132 945-134 945-136 946-111 946-114 946-121 946-122 946-123 946-131 D D D D D D D D D 466 Diagnostic Information for Multiple Bus Systems .Service Request Number 938-124 938-600 SRN Src. Description: A disk drive hardware error occurred. Description: The certify operation failed. Description: Cannot run the test because the device driver detected a hardware error. 938-800 945-102 to 945-114 945-116 D D Description: HIPPI Adapter test failed. and application software to be sure they are all compatible. Description: A protocol error.) Description: HIPPI Adapter test failed. Description: The adapter failed to configure. If you do not find a problem. Description: Error log analysis indicates a SCSI bus problem. Action: Check the levels of the device. Description: The register verification test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: Cannot run the test because the device driver detected a hardware error. Description: 1 GB 16-bit SCSI differential disk drive problem. D 945-117 945-118 945-120 to 945-124 945-126 945-128 945-129 D D D 990 990 B88 990 Description: A write-protect error occurred. D D Failing Function Codes 938 227 938 227 software 938 227 990 Description and Action (Unless otherwise indicated. adapter. “MAP 0210: General Problem Resolution” on page 67. Description: The data wrap communications test failed. diagnostic software. Description: HIPPI Adapter test failed. Description: A software error was caused by a hardware failure. Description: A SCSI command time-out. Description: 1 GB 16-bit SCSI differential disk drive problem. use Chapter 11. call your support person. Description: The error log analysis indicates a hardware failure. Description: The modem control line test failed.

Chapter 33. Description: The data wrap communications test failed. Description: The modem control line test failed. Description: The data wrap communications test failed. Description: The modem control line test failed. Description: The modem control line test failed. Description: The data wrap communications test failed.) Description: The data wrap communications test failed. SRNs 900-001 through xxxxxxx 467 . Description: The data wrap communications test failed. Description: The modem control line test failed. Description: Cannot run the test because the device driver detected a hardware error.Service Request Number 946-132 946-133 946-161 946-162 946-163 946-171 946-172 946-173 946-181 946-182 946-183 946-271 946-272 946-273 946-281 946-282 946-283 946-321 946-322 946-323 946-331 946-332 946-333 946-371 946-372 946-373 SRN Src. Description: Cannot run the test because the device driver detected a hardware error. Description: The data wrap communication test failed. “MAP 0210: General Problem Resolution” on page 67. Description: The modem control line test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: Could not do the test because the device driver detected a hardware error. Description: The modem control line test failed. Description: The data wrap communications test failed. Description: Cannot run the test because the device driver detected a hardware error. Description: Cannot run the test because the device driver detected a hardware error. Description: The modem control line test failed. Description: Cannot run the test because the device driver detected a hardware error. use Chapter 11. Description: The data wrap communications test failed. Description: The modem control line test failed. Description: The data wrap communication test failed. Description: The modem control line test failed. D D D D D D D D D D D D D D D D D D D D D D D D D D Failing Function Codes 946 227 946 252 252 252 259 259 259 261 261 261 946 259 946 259 946 259 946 261 946 261 946 261 946 946 946 946 946 946 946 946 946 Description and Action (Unless otherwise indicated. Description: Cannot run the test because the device driver detected a hardware error.

use MAP 210 with a FFC of 946. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. D D D D D D D D D D Failing Function Codes 946 946 946 D56 D56 D56 946 D56 946 D56 946 D56 software 946 Description and Action (Unless otherwise indicated. otherwise. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Description: The modem control line test failed. use MAP 210 with a FFC of 946. suspect a software problem. Description: The adapter failed to configure. Action: Run diagnostics from a source other than from the disk or a network. Description: Power supply problem. suspect a software problem. Description: The data wrap communication test failed. otherwise. suspect a software problem. Description: An unexpected error occurred that can be attributed to software or hardware. Description: Could not do the test because the device driver detected a hardware error. Description: The data wrap communications test failed. Action: Run diagnostics from a source other than from the disk or a network. Description: PCI bus was not found. Description: An unexpected error occurred that can be attributed to software or hardware. use MAP 210 with a FFC of 946. “MAP 0210: General Problem Resolution” on page 67. Description: Could not do the test because the device driver detected a hardware error. Description: An unexpected error occurred that can be attributed to software or hardware. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics.) Description: Cannot run the test because the device driver detected a hardware error. Action: Rerun diagnostics in Advanced Mode for additional problem isolation. Action: Use the service documentation for the portable disk.Service Request Number 946-381 946-382 946-383 946-481 946-482 946-483 946-581 946-582 946-583 946-901 to 946-920 SRN Src. Description: The modem control line test failed. use Chapter 11. Description: The data wrap communication test failed. 946-921 946-922 to 946-924 D D 946 software software 946 946-925 946-926 to 946-943 D D 946 software software 946 950-100 950-101 C F 192 2C9 153 468 Diagnostic Information for Multiple Bus Systems . otherwise. Description: The adapter failed to configure. Action: Run diagnostics from a source other than from the disk or a network. Description: The modem control line test failed.

950-442 C Description: Device does not respond. use Chapter 11. Description: The device is not responding. Chapter 33. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: Device does not respond. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. Description: PCI bus was not found. “MAP 0210: General Problem Resolution” on page 67. Description: The device is not responding. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. Action: Use Chapter 21. Action: Use the service documentation for the drawer/tower containing the failing power supply. 950-103 950-105 C C 2C9 2C9 221 2C9 950-106 C 950-107 C 153 165 190 199 153 165 152 SCSI Bus 950-108 C 950-200 950-201 C C 950-400 C 153 950-440 C 440 B88 190 199 152 440 B88 190 199 152 440 B88 190 199 152 950-441 C Description: Device does not respond. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117.Service Request Number 950-102 SRN Src. Description: SCSI bus problem. Action: Use the service documentation for the external device.) Description: PCI bus was not found. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Refer to MAP 2010 in the 7134 High Density SCSI Disk Subsystem Installation and Service Guide. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. SRNs 900-001 through xxxxxxx 469 . Action: Use Chapter 21. C Failing Function Codes 2C9 Description and Action (Unless otherwise indicated. Action: Use Chapter 21. Description: Power supply problem. If the drawer/deskside unit service documentation does not isolate the problem. Action: Use Chapter 21. Description: Power supply problem. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. go to MAP 1520 in the system unit installation and service guide. Action: Use Chapter 21. Description: Multiple adapters on bus were not found. Description: PCI bus was not found.

Action: Use Chapter 21.) Description: Device does not respond. Action: Use Chapter 21. 950-63A C 950-63B C 950-63C C 950-63D C 950-63E C 470 Diagnostic Information for Multiple Bus Systems . Action: Use Chapter 21. Description: The device is not responding. Description: Device does not respond. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. C Failing Function Codes 440 B88 190 199 152 152 Description and Action (Unless otherwise indicated. Description: Device does not respond. Action: Use Chapter 21. Action: Use Chapter 21. rack. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. or drawer that contains the missing device. Action: Use Chapter 21. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. Description: Device does not respond. 950-500 C Description: Power supply problem. Description: The device is not responding. Description: Device does not respond. Description: Device does not respond.Service Request Number 950-443 SRN Src. Description: The SCSI device is not responding. Action: Use the service documentation for the system unit. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0210: General Problem Resolution” on page 67. use Chapter 11. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. 950-58D C 58D B88 190 152 61D B88 190 152 638 B88 277 190 152 639 B88 190 152 63A B88 190 152 63B B88 190 152 63C B88 190 152 63D B88 190 152 63E B88 277 190 152 950-61D C 950-638 C 950-639 C Description: The device is not responding. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117.

Description: The device is not responding. Action: Use Chapter 21. Action: Use Chapter 21. Action: Use Chapter 21. Action: Use Chapter 21. Action: Use Chapter 21. Action: Use Chapter 21. Description: The device is not responding. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117.Service Request Number 950-63F SRN Src. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0210: General Problem Resolution” on page 67. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. use Chapter 11. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: The SCSI Disk Drive is not responding. Description: The device is not responding. SRNs 900-001 through xxxxxxx 471 . “MAP 0291: Missing Device or Bus Problem Resolution” on page 117.) Description: Device does not respond. Description: The device is not responding. Action: Use Chapter 21. C Failing Function Codes 63F B88 190 152 640 B88 190 152 664 B88 190 152 678 B88 190 152 679 B88 190 152 681 2E7 190 152 700 B88 190 152 701 B88 190 152 702 B88 190 152 703 B88 190 152 704 B88 190 152 Description and Action (Unless otherwise indicated. Action: Use Chapter 21. 950-640 C 950-664 C 950-678 C 950-679 C 950-681 C 950-700 C 950-701 C 950-702 C 950-703 C 950-704 C Chapter 33. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: The device is not responding. Description: The device is not responding. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: The SCSI Tape Drive is not responding. Action: Use Chapter 21. Description: The SCSI Disk Drive is not responding. Description: The device is not responding.

“MAP 0291: Missing Device or Bus Problem Resolution” on page 117.Service Request Number 950-705 SRN Src. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. 950-706 C 950-707 C 950-721 C 950-722 C 950-723 C 950-724 C 950-734 C 950-741 C 950-772 C 950-773 C 472 Diagnostic Information for Multiple Bus Systems . Action: Use Chapter 21. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. “MAP 0210: General Problem Resolution” on page 67. use Chapter 11. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: The device is not responding. Action: Use Chapter 21. Action: Use Chapter 21. C Failing Function Codes 705 B88 190 152 706 B88 190 152 707 B88 190 152 721 B88 190 152 722 B88 190 152 723 B88 190 152 724 B88 190 152 734 B88 190 152 741 B88 190 152 772 B88 190 152 773 B88 190 152 Description and Action (Unless otherwise indicated. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. Description: The device is not responding. Description: Device does not respond. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: An unknown drive type is not responding. Description: The device is not responding. Description: The device is not responding. Description: Device does not respond. Description: The device is not responding. Action: Use Chapter 21. Description: Device does not respond. Description: The device is not responding. Action: Use Chapter 21. Action: Use Chapter 21. Action: Use Chapter 21.) Description: The device is not responding. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117.

Description: Device does not respond. Description: Device does not respond. Action: Use Chapter 21. Action: Use Chapter 21. Description: Device does not respond. SRNs 900-001 through xxxxxxx 473 . “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0210: General Problem Resolution” on page 67. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. Action: Use Chapter 21. Action: Use Chapter 21. 950-792 C 950-793 C 950-804 C 950-912 C 950-914 C 950-915 C 950-917 C 950-918 C 950-935 C 950-936 C Chapter 33. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: Device does not respond. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. Action: Use Chapter 21. Description: Device does not respond.Service Request Number 950-789 SRN Src. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: Device does not respond. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117.) Description: Device does not respond. C Failing Function Codes 789 B88 190 152 792 B88 190 152 793 B88 190 152 804 B88 190 152 912 B88 190 152 914 B88 190 152 915 B88 190 152 917 B88 190 152 918 B88 190 152 935 B88 190 152 936 B88 190 152 Description and Action (Unless otherwise indicated. use Chapter 11. Description: The device is not responding. Description: Device does not respond. Description: Device does not respond. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: Device does not respond. Action: Use Chapter 21.

Description: Device does not respond. Action: Use Chapter 21. Action: Use Chapter 21. Description: Device does not respond. Action: Use Chapter 21. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: Device does not respond. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: The SCSI Tape Drive is not responding.) Description: Device does not respond. use Chapter 11. Description: Device does not respond. Description: Device does not respond. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: Device does not respond.Service Request Number 950-951 SRN Src. Action: Use Chapter 21. Description: Device does not respond. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. C Failing Function Codes 951 B88 190 152 952 B88 190 152 953 B88 190 152 954 B88 190 152 955 B88 190 141 152 956 B88 190 152 959 B88 190 152 960 B88 190 152 964 B88 190 152 968 B88 190 152 970 B88 190 152 Description and Action (Unless otherwise indicated. Action: Use Chapter 21. Description: Device does not respond. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. 950-952 C 950-953 C 950-954 C 950-955 C 950-956 C Description: Device does not respond. “MAP 0210: General Problem Resolution” on page 67. 950-959 C 950-960 C 950-964 C 950-968 C 950-970 C 474 Diagnostic Information for Multiple Bus Systems . Action: Use Chapter 21. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117.

use Chapter 11. “MAP 0210: General Problem Resolution” on page 67. Description: Device does not respond. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: Device does not respond. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117.) Description: Device does not respond. Description: Device does not respond. Description: Device does not respond. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. SRNs 900-001 through xxxxxxx 475 . Action: Use Chapter 21. 950-972 C 950-974 C 950-981 C 950-984 C 950-986 C 950-987 C 950-989 C 950-990 C 950-991 C 950-994 C Chapter 33. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: Device does not respond. Action: Use Chapter 21.Service Request Number 950-971 SRN Src. Description: Device does not respond. C Failing Function Codes 971 B88 190 152 972 B88 190 152 974 B88 190 152 981 B88 190 152 984 B88 190 152 986 B88 190 152 987 B88 190 152 989 B88 190 152 990 B88 190 152 991 B88 190 152 994 B88 190 152 Description and Action (Unless otherwise indicated. Action: Use Chapter 21. Description: Device does not respond. Action: Use Chapter 21. Action: Use Chapter 21. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Action: Use Chapter 21. Description: Device does not respond. Description: Device does not respond. Action: Use Chapter 21. Description: Device does not respond.

substitute the last three or four digits of the SRN for xxxx. Action: Check the levels of the device.Service Request Number 950-995 SRN Src. Description: An unrecoverable hardware error. 950-998 C 950-xxxx C 951-102 951-104 951-105 951-106 951-108 951-110 951-112 951-114 951-116 D D D D D D D D D 951 951 951 951 951 951 951 951 951-117 951-118 951-120 951-122 951-124 951-126 951-128 951-129 D D D D D D G G 951 951 B88 951 951 951 951 B88 951 190 951 B88 software Description: A write-protect error occurred. call your support person. Action: Use Chapter 21. Description: A SCSI command timeout. Description: A protocol error. Action: Use Chapter 21. “MAP 0210: General Problem Resolution” on page 67. Description: The drive did not become ready. use Chapter 11. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: A SCSI busy or command error. Description: The motor failed to restart. C Failing Function Codes 995 B88 190 152 998 B88 190 152 xxxx B88 190 152 Description and Action (Unless otherwise indicated. Description: Error log analysis indicates a SCSI bus problem. If you do not find a problem. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Description: An unrecoverable media error. Description: The media format is corrupted. Description: A SCSI check condition error. 476 Diagnostic Information for Multiple Bus Systems . Description: The error log analysis indicates a hardware failure. Action: Use Chapter 21.) Description: Device does not respond. Description: Device does not respond. Description: A software error was caused by a hardware failure. adapter. Description: The electronics card test failed. “MAP 0291: Missing Device or Bus Problem Resolution” on page 117. Note: xxxx corresponds to the last three or four digits of the SRN after the dash (-). Description: The bus test failed. Description: A SCSI reservation conflict error. Description: The device does not respond. If your 950-xxxx SRN is not listed. and application software to ensure they are all compatible. diagnostic software. Description: The diagnostic test failed.

SRNs 900-001 through xxxxxxx 477 . adapter. If you do not find a problem. diagnostic software. Description: An unrecoverable hardware error. Description: The device failed to configure. Chapter 33. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The drive did not become ready. Description: The media format is corrupted. Action: Check the levels of the device. 952-130 952-132 G D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. use Chapter 11. Description: The electronics card test failed. Description: A SCSI check condition error. Description: Error log analysis indicates a SCSI bus problem. Description: A disk drive hardware error occurred. Description: The adapter failed to configure. Description: The motor failed to restart.Service Request Number 951-130 951-132 951-134 951-135 SRN Src. Description: A SCSI reservation conflict error.) Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: A software error was caused by a hardware failure. and application software to be sure they are all compatible. Description: A disk drive hardware error occurred. Description: An unrecoverable media error. 952-102 952-104 952-105 952-106 952-108 952-110 952-112 952-114 952-116 D D D D D D D D D 952-117 952-118 952-120 952-122 952-124 952-126 952-128 952-129 D D D D D D G G 952 952 B88 952 952 952 952 B88 952 190 952 B88 software 952 952 Description: A write-protect error occurred. Description: A protocol error. 951-136 951-137 D D Description: The certify operation failed. “MAP 0210: General Problem Resolution” on page 67. Description: A SCSI busy or command error. Description: A SCSI command timeout. call your support person. Description: The bus test failed. Description: The error log analysis indicates a hardware failure. Description: The diagnostic test failed. G D D D Failing Function Codes 951 951 B88 software 951 B88 software 951 951 B88 190 952 952 952 952 952 952 952 952 Description and Action (Unless otherwise indicated.

If you do not find a problem. “MAP 0210: General Problem Resolution” on page 67. Description: The disk drive did not become ready. D D Failing Function Codes B88 software 952 B88 software 952 952 B88 190 953 953 953 953 953 953 953 953 Description and Action (Unless otherwise indicated. Description: A disk drive hardware error occurred. call your support person. Description: A SCSI busy or command error. use Chapter 11. Description: A software error was caused by a hardware failure. Description: The device failed to configure. and application software to be sure they are all compatible.Service Request Number 952-134 952-135 SRN Src. Description: Error log analysis indicates a SCSI bus problem. Description: The bus test failed. Description: A SCSI check condition error. Description: The media format is corrupted. Description: The adapter failed to configure. Action: Check the levels of the device. Description: A SCSI command timeout. Description: The motor failed to restart. Description: The diagnostic test failed. Description: The electronics card test failed. Description: An unrecoverable hardware error. Description: Unit attention condition has occurred on the Send Diagnostic command. 953-130 953-132 953-134 G D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. 952-136 952-137 D D Description: The certify operation failed. Description: The error log analysis indicates a hardware failure. Description: An unrecoverable media error. Description: A protocol error.) Description: The adapter failed to configure. 953-102 953-104 953-105 953-106 953-108 953-110 953-112 953-114 953-116 D D D D D D D D D 953-117 953-118 953-120 953-122 953-124 953-126 953-128 953-129 D D D D D D G G 953 953 B88 953 953 953 953 B88 953 190 953 B88 software 953 953 B88 software Description: A write-protect error. Description: A SCSI reservation conflict error. adapter. 478 Diagnostic Information for Multiple Bus Systems . diagnostic software.

use Chapter 11. Description: A disk drive hardware error occurred. D Failing Function Codes 953 B88 software 953 953 B88 190 954 954 954 954 954 954 954 954 Description and Action (Unless otherwise indicated. 954-130 954-132 954-134 954-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. 953-136 953-137 D D Description: The certify operation failed. Description: The media format is corrupted. 954-102 954-104 954-105 954-106 954-108 954-110 954-112 954-114 954-116 D D D D D D D D D 954-117 954-118 954-120 954-122 954-124 954-126 954-128 954-129 D D D D D D G G 954 954 B88 954 954 954 954 B88 954 150 954 B88 software 954 954 B88 software 954 B88 software Description: write-protect error. Description: An unrecoverable media error. Description: The device failed to configure. Description: SCSI command timeout. call your support person. adapter. Description: Error log analysis indicates a SCSI bus problem. ensure that they are all compatible. “MAP 0210: General Problem Resolution” on page 67. Description: An unrecoverable hardware error. diagnostic software. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: Software error caused by hardware failure. Action: Check the levels of the device. Description: Bus failure.) Description: The device failed to configure. Description: The adapter failed to configure. Description: SCSI reservation conflict error. Description: A protocol error was detected. SRNs 900-001 through xxxxxxx 479 .Service Request Number 953-135 SRN Src. Description: Error log analysis indicates hardware failure. Description: SCSI busy/command error. Chapter 33. Description: Diagnostic failure. Description: Electronics card failure. If you do not find a problem. and application software. Description: Motor failed to restart. Description: The disk drive did not become ready. Description: SCSI check condition error.

go to MAP 0210. If the electronics card has been exchanged. Description: The bus test failed. Description: The error log analysis indicates a hardware failure. use the drawer/deskside unit documentation. 480 Diagnostic Information for Multiple Bus Systems . go to MAP 0210. diagnostic software. If the drawer/deskside unit documentation does not isolate the problem. If you do not find a problem. Description: A media error was encountered. Description: The motor failed to restart. Action: Check the levels of the device. adapter. Description: An unrecoverable hardware error.Service Request Number 954-136 954-137 SRN Src.) Description: The certify operation failed. D D Failing Function Codes 954 954 B88 190 955 141 955 141 Description and Action (Unless otherwise indicated. Description: Unit attention condition has occurred on the Send Diagnostic command. 955-102 955-104 D D 955-105 955-106 955-108 955-110 955-112 955-114 955-116 D D D D D D D 955 141 955 141 955 955 141 955 141 955 141 955-118 955-120 955-122 955-124 955-126 955-128 955-129 D D D D D G G 955 B88 955 B88 955 955 B88 955 B88 955 141 190 955 B88 software Description: A SCSI command timeout. Description: The diagnostic test failed. Refer to ″Drawer/Deskside Unit Documentation″ under Hints in Chapter 1. Description: A software error was caused by a hardware failure. Description: A SCSI busy or command error. “MAP 0210: General Problem Resolution” on page 67. Action: For devices installed in a drawer/deskside unit. For other locations. exchange the adapter first. Description: The electronics card failed. Description: A SCSI reservation conflict error. Description: A protocol error. and application software to be sure they are all compatible. Description: The disk drive did not become ready. Description: The media format is corrupted. Description: Error log analysis indicates a SCSI bus problem. Description: A SCSI check condition error. call your support person. use Chapter 11.

call your support person. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: A disk drive hardware error occurred. Description: The media format is corrupted. If you do not find a problem. Description: The electronics card test failed. Description: The error log analysis indicates a hardware failure.) Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: A SCSI reservation conflict error. G D D D Failing Function Codes 955 955 B88 software 955 B88 software 955 141 955 B88 190 956 956 956 956 956 956 956 956 Description and Action (Unless otherwise indicated. 956-102 956-104 956-105 956-106 956-108 956-110 956-112 956-114 956-116 D D D D D D D D D 956-117 956-118 956-120 956-122 956-124 956-126 956-128 956-130 956-132 956-134 D D D D D D G G D D 956 956 B88 956 956 956 956 B88 956 956 B88 956 B88 software Description: A write-protect error occurred. Description: The error log analysis indicates a hardware failure. Description: An unrecoverable media error. Description: The device failed to configure. “MAP 0210: General Problem Resolution” on page 67. Action: Check the levels of the device. SRNs 900-001 through xxxxxxx 481 . Description: An unrecoverable hardware error. Description: A SCSI busy or command error. Description: The adapter failed to configure. Description: The drive did not become ready. Description: A SCSI check condition error. Description: The motor failed to restart. diagnostic software. Chapter 33. Description: A software error was caused by a hardware failure. Description: A disk drive hardware error occurred. Description: The diagnostic test failed. 955-136 955-137 D D Description: The certify operation failed. Description: A SCSI command time-out. adapter. Description: The bus test failed. and application software to be sure they are all compatible. Description: A protocol error. use Chapter 11. Description: The adapter failed to configure.Service Request Number 955-130 955-132 955-134 955-135 SRN Src.

“MAP 0210: General Problem Resolution” on page 67. 960-102 960-104 960-105 D D D 482 Diagnostic Information for Multiple Bus Systems . Description: Electronics card failure. Description: SCSI command timeout. Description: Error log analysis indicates hardware failure. diagnostic and application software.Service Request Number 956-136 959-102 959-104 959-105 959-106 959-108 959-110 959-112 959-114 959-116 SRN Src. Description: Diagnostic failure. D D D D D D D D D D Failing Function Codes 956 959 959 959 959 959 959 959 959 Description and Action (Unless otherwise indicated. Description: A protocol error was detected.) Description: The certify operation failed. If you do not find a problem. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: An unrecoverable media error. Description: SCSI busy/command error. 959-136 959-137 D D Description: The certify operation failed. Description: SCSI check condition error. Description: Bus failure. Description: SCSI reservation conflict error. adapter. use Chapter 11. Action: Check the levels of the device. Description: The adapter failed to configure. Description: The drive did not become ready. Description: Error log analysis indicates a SCSI bus problem. Description: Motor failed to restart. 959-130 959-134 959-135 G D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. 959-117 959-118 959-120 959-122 959-124 959-126 959-128 959-129 D D D D D D G G 959 959 B88 959 959 959 959 B88 959 190 959 B88 software 959 B88 software 959 B88 software 959 959 B88 190 960 960 960 Description: write-protect error. and ensure they are all compatible. Description: The media format is corrupted. Description: The device failed to configure. Description: The drive did not become ready. call your support person. Description: Non-recoverable hardware error. Description: Non-recoverable medium error. Description: The motor failed to restart. Description: Software error caused by hardware failure.

Description: A SCSI busy or command error. Description: The media format is corrupted. “MAP 0210: General Problem Resolution” on page 67. 960-117 960-118 960-120 960-122 960-124 960-126 960-128 960-129 D D D D D D G G 960 960 B88 960 960 960 960 B88 960 190 960 B88 software 960 960 B88 software 960 B88 software 960 960 B88 190 964 964 964 Description: A write-protect error occurred. adapter. Description: The device failed to configure. diagnostic software. SRNs 900-001 through xxxxxxx 483 . Action: Check the levels of the device. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The error log analysis indicates a hardware failure. use Chapter 11. 960-136 960-137 D D Description: The certify operation failed. Description: The SCSI device indicates busy. If you do not find a problem. Description: The adapter failed to configure. Description: Timeout while attempting to communicate with SCSI device. 964-101 964-102 964-103 D D D Chapter 33. D D D D D D Failing Function Codes 960 960 960 960 960 Description and Action (Unless otherwise indicated. Description: A protocol error. Description: An unrecoverable hardware error. and application software to be sure they are all compatible. Description: A disk drive hardware error occurred. Description: A software error was caused by a hardware failure. Description: The bus test failed.Service Request Number 960-106 960-108 960-110 960-112 960-114 960-116 SRN Src. 960-130 960-132 960-134 960-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: A SCSI check condition error. Description: A SCSI command time-out. Description: The diagnostic test failed. Description: The SCSI device indicates a reservation conflict. call your support person.) Description: The electronics card test failed. Description: A SCSI reservation conflict error. Description: Error log analysis indicates a SCSI bus problem.

Description: The Mode Select command failed. Description: Timeout while attempting to communicate with the SCSI device. Description: The Unload command failed. Description: The adapter failed to configure. Description: Sense data from the SCSI drive has unexpected data. 484 Diagnostic Information for Multiple Bus Systems . Description: An error is detected in request sense data. Description: Write. use Chapter 11. Description: The Inquiry command failed. Description: Timeout while attempting to communicate with the SCSI device. Description: Invalid condition from the drive after a request sense. Description: The adapter failed to configure. Description: The Load command failed.Service Request Number 964-104 964-105 964-107 964-110 964-111 964-112 964-113 964-114 964-120 964-130 964-134 964-135 964-140 964-150 964-160 964-161 964-163 964-164 964-165 SRN Src.) Description: The SCSI device indicates a check condition. Description: Invalid condition from the drive after a reserve. Description: The Reserve command failed. Description: Invalid condition from drive after a request sense. Description: The Test Unit Ready command failed. “MAP 0210: General Problem Resolution” on page 67. Read and Compare Test failed. 964-166 D Description: Unable to configure the device. Description: The Send Diagnostic command failed. D D D D D D D D D D D D D D D D D D D Failing Function Codes 964 964 964 964 964 964 964 964 964 964 media B88 software 964 media 964 964 media 964 media 964 B88 964 B88 964 B88 964 B88 276 964 B88 software 964 B88 B88 software Description and Action (Unless otherwise indicated. Description: The write-protect sensor test failed. Description: Invalid condition from the drive after a reserve. 964-167 964-168 D D Description: An unexpected SCSI error occurred.

Description: The Read. D D Failing Function Codes 964 media 964 B88 media 964 media 964 media 964 964 media 964 B88 964 B88 964 B88 964 964 964 964 964 964 software B88 964 software 964 media 964 B88 software 964 B88 964 B88 software 964 B88 software Description and Action (Unless otherwise indicated. SRNs 900-001 through xxxxxxx 485 . use Chapter 11. Description: The Request Sense command failed.Service Request Number 964-169 964-170 SRN Src. Description: The device configuration failed. Description: The Release command failed. D D Description: A device timeout error occurred. Chapter 33. Description: A reservation conflict occurred. 964-180 964-185 964-190 964-200 964-201 964-210 964-211 964-220 964-230 964-240 964-260 964-261 964-300 964-310 D D D D G D D D D D D D D D Description: The Load command failed. Description: An adapter or bus I/O error occurred. “MAP 0210: General Problem Resolution” on page 67. Description: SCSI adapter configuration failed. Description: The Test Unit Ready command failed. 964-320 964-411 to 964-423 964-511 to 964-523 964-611 to 964-623 964-711 to 964-723 G D Description: Error log analysis indicates a failure. Description: Error diagnosed from error log analysis. Description: The device configuration failed. Description: The Unload command failed. Description: The device open failed. Description: The device configuration failed. Write and Compare test failed. Description: The Openx command failed. Description: The device open failed. D Description: The drive returned bad or non-extended sense data.) Description: The Send Diagnostic command failed. Description: The Mode Select command failed.

Description: The drive did not become ready. Audio error in interactive test. Test pattern failed. Description: The diagnostic test failed. Description: The motor failed to restart. The test pattern failed. Description: The bus test failed. 968-102 968-104 968-105 968-106 968-108 968-110 968-112 968-114 D D D D D D D D Description: An unrecoverable media error. 966-306 D Audio error in interactive test. Description: The media format is corrupted. use Chapter 11.Service Request Number 966-101 966-103 966-201 966-203 966-205 966-207 966-208 966-209 966-211 966-213 966-304 SRN Src. Description: Error in non-interactive tests on card. “MAP 0210: General Problem Resolution” on page 67. Description: Test pattern failed. Description: An unrecoverable hardware error. Error in non-interactive tests. 966-310 966-312 966-400 D D D Video error in interactive test. 486 Diagnostic Information for Multiple Bus Systems . Description: The test pattern failed. Description: Error in non-interactive test on card. Description: Test pattern failed. Video error in interactive test. D D D D D D D D D D D Failing Function Codes 966 966 966 190 966 190 966 190 966 190 190 190 190 190 E22 725 966 E23 725 966 E22 725 E22 725 152 190 E24 166 190 E23 E22 968 968 968 968 968 968 968 968 Description and Action (Unless otherwise indicated. Description: The electronics card test failed. Test pattern failed.) Error in non-interactive tests. Description: Test pattern failed. 966-402 D Test pattern failed.

Description: Residual Data Analysis indicates memory error. Description: The device failed to configure. “MAP 0240: Memory Problem Resolution” on page 93. call your support person. “MAP 0240: Memory Problem Resolution” on page 93. Description: Residual Data Analysis indicates memory error. “MAP 0240: Memory Problem Resolution” on page 93. Description: Error log analysis indicates a SCSI bus problem. “MAP 0240: Memory Problem Resolution” on page 93. Action: Check the levels of the device. D Failing Function Codes Description and Action (Unless otherwise indicated. 968-130 968-132 968-134 968-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. SRNs 900-001 through xxxxxxx 487 . Description: Residual Data Analysis indicates memory error. If you do not find a problem.) Description: A protocol error. Action: Use Chapter 15. 968-136 968-137 D D Description: The certify operation failed. “MAP 0210: General Problem Resolution” on page 67. Description: Residual Data Analysis indicates memory error. Description: A SCSI reservation conflict error. adapter. Description: A SCSI command time-out. Description: Unit attention condition has occurred on the Send Diagnostic command. 968-117 968-118 968-120 968-122 968-124 968-126 968-128 968-129 D D D D D D G G 968 968 B88 968 968 968 968 B88 968 190 968 B88 software 968 968 B88 software 968 B88 software 968 968 B88 190 D67 Description: A write-protect error occurred. 969-110 G 969-111 G D83 969-120 G D68 969-121 G D84 Chapter 33. Description: A disk drive hardware error occurred. diagnostic software. Action: Use Chapter 15. Action: Use Chapter 15. and application software to be sure they are all compatible. use Chapter 11. Description: The error log analysis indicates a hardware failure. Description: A SCSI busy or command error. Description: The adapter failed to configure. Action: Use Chapter 15. Description: A SCSI check condition error.Service Request Number 968-116 SRN Src. Description: A software error was caused by a hardware failure.

Action: Use Chapter 15. Action: Use Chapter 15. Action: Use Chapter 15. Description: Residual Data Analysis indicates memory error. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. Description: Residual Data Analysis indicates memory error.Service Request Number 969-130 SRN Src. 969-131 G D85 969-140 G D70 969-141 G D86 969-150 G E11 969-151 G E14 969-206 G D72 969-208 G D73 969-210 G D71 969-211 G D87 969-212 969-220 G G E12 D72 969-221 G D88 969-230 G D73 969-231 G D89 488 Diagnostic Information for Multiple Bus Systems . Description: Residual Data Analysis indicates memory error. Action: Use Chapter 15. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. Description: Residual Data Analysis indicates memory error. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Description: Residual Data Analysis indicates memory error. G Failing Function Codes D69 Description and Action (Unless otherwise indicated. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. Description: Residual Data Analysis indicates memory error.) Description: Residual Data Analysis indicates memory error. Description: Residual Data Analysis indicates memory error. Description: Residual Data Analysis indicates memory error. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Description: Residual Data Analysis indicates memory error. Description: Residual Data Analysis indicates memory error. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. Description: Residual Data Analysis indicates memory error. Description: Residual Data Analysis indicates memory error. Action: Use Chapter 15. use Chapter 11. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0210: General Problem Resolution” on page 67. Description: Residual Data Analysis indicates memory error. Description: Residual Data Analysis indicates memory error. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93.

“MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. “MAP 0210: General Problem Resolution” on page 67. “MAP 0240: Memory Problem Resolution” on page 93. Description: Residual Data Analysis indicates memory error. Action: Use Chapter 15. Description: Residual Data Analysis indicates memory error. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. Description: Residual Data Analysis indicates memory error. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. Action: Use Chapter 15. use Chapter 11. Action: Use Chapter 15. Action: Use Chapter 15. Description: Residual Data Analysis indicates memory error. Description: Residual Data Analysis indicates memory error. Description: Residual Data Analysis indicates memory error. Action: Use Chapter 15. Action: Use Chapter 15. Action: Use Chapter 15. Description: Residual Data Analysis indicates memory error. 969-241 G D90 969-250 G E12 969-251 G E15 969-310 G D75 969-311 G D91 969-320 G D76 969-321 G D92 969-330 G D77 969-331 G D93 969-340 G D78 969-341 G D94 969-350 G E13 969-351 G E16 Chapter 33. Action: Use Chapter 15.) Description: Residual Data Analysis indicates memory error. Description: Residual Data Analysis indicates memory error. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. G Failing Function Codes D74 Description and Action (Unless otherwise indicated.Service Request Number 969-240 SRN Src. Description: Residual Data Analysis indicates memory error. Description: Residual Data Analysis indicates memory error. Action: Use Chapter 15. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. Description: Residual Data Analysis indicates memory error. Action: Use Chapter 15. Description: Residual Data Analysis indicates memory error. Action: Use Chapter 15. Description: Residual Data Analysis indicates memory error. “MAP 0240: Memory Problem Resolution” on page 93. “MAP 0240: Memory Problem Resolution” on page 93. SRNs 900-001 through xxxxxxx 489 .

Description: The Unload command failed. Description: The adapter failed to configure. Description: The Load command failed. If the modules are supported. Description: The Mode Select command failed. use Chapter 11. Description: Invalid condition from the drive after a reserve. 490 Diagnostic Information for Multiple Bus Systems . Description: Sense data from the SCSI drive has unexpected data.Service Request Number 969-600 SRN Src. G Failing Function Codes Description and Action (Unless otherwise indicated. Description: The SCSI device indicates a check condition. Description: The Inquiry command failed. Description: Memory problems indicate System Planar failure. then replace the appropriate memory module(s). “MAP 0240: Memory Problem Resolution” on page 93. Description: L2 cache test failed. Description: An error is detected in request sense data. 969-701 969-702 969-703 969-800 969-900 970-101 970-102 970-103 970-104 970-105 970-107 970-110 970-111 970-112 970-113 970-114 970-120 970-130 970-134 970-135 970-140 970-150 D D D G G D D D D D D D D D D D D D D D D D 814 151 817 221 D01 970 970 970 970 970 970 970 970 970 970 970 970 970 media B88 software 970 media 970 970 media Description: NVRAM test failed. “MAP 0210: General Problem Resolution” on page 67.) Description: Residual Data Analysis indicates memory error or unsupported memory. Description: Time of Day Chip test failed. Description: Timeout while attempting to communicate with SCSI device. Description: The Reserve command failed. Description: Time of Day Battery test failed. Description: Timeout while attempting to communicate with the SCSI device. Use Chapter 15. Description: The Test Unit Ready command failed. Description: The SCSI device indicates busy. Description: The SCSI device indicates a reservation conflict. Action: Examine the memory modules and determine if they are supported types. Description: Invalid condition from drive after a request sense. Description: The write-protect sensor test failed.

Description: Invalid condition from the drive after a request sense. SRNs 900-001 through xxxxxxx 491 . Chapter 33. Description: The device configuration failed. Description: Write. D D D D D Failing Function Codes 970 media 970 B88 970 B88 970 B88 970 B88 276 970 B88 software 970 B88 B88 software 970 media 970 B88 media 970 media 970 media 970 970 media 970 B88 970 B88 970 B88 970 970 970 970 970 Description and Action (Unless otherwise indicated. 970-167 970-168 970-169 970-170 D D D D Description: An unexpected SCSI error occurred. Description: Timeout while attempting to communicate with the SCSI device. Description: Error diagnosed from error log analysis. Description: The Read. Description: The device configuration failed. Description: Invalid condition from the drive after a reserve. Description: The adapter failed to configure. 970-180 970-185 970-190 970-200 970-201 970-210 970-211 970-220 970-230 970-240 970-260 970-261 D D D D G D D D D D D D Description: The Load command failed. Description: The Send Diagnostic command failed. use Chapter 11.) Description: The Send Diagnostic command failed. Description: The device open failed. Description: The Test Unit Ready command failed. Description: The Unload command failed. 970-166 D Description: Unable to configure the device.Service Request Number 970-160 970-161 970-163 970-164 970-165 SRN Src. Description: The Release command failed. Description: The Mode Select command failed. Description: The Openx command failed. Read and Compare Test failed. “MAP 0210: General Problem Resolution” on page 67. Description: The device open failed. Write and Compare test failed. Description: The Request Sense command failed.

use Chapter 11. Description: Timeout while attempting to communicate with the SCSI device. Description: SCSI adapter configuration failed. Description: The SCSI device indicates a check condition. D Description: The drive returned bad or non-extended sense data. “MAP 0210: General Problem Resolution” on page 67. Description: Invalid condition from the drive after a reserve.Service Request Number 970-300 970-310 SRN Src. Description: The SCSI drive returned unexpected sense data. 492 Diagnostic Information for Multiple Bus Systems . Description: The write-protect sensor test failed. Description: The Reserve command failed. Description: The SCSI device indicates busy. Description: A reservation conflict occurred. D D Failing Function Codes 970 software B88 970 software 970 media 970 B88 software 970 B88 970 B88 software 970 B88 software 971 971 971 971 971 971 971 971 971 971 971 971 971 media Description and Action (Unless otherwise indicated.) Description: The device configuration failed. Description: The Load command failed. Description: The SCSI device is indicating a reservation conflict. Description: The Inquiry command failed. Description: Invalid condition from the drive after a request sense. 970-320 970-411 to 970-423 970-511 to 970-523 970-611 to 970-623 970-711 to 970-723 971-101 971-102 971-103 971-104 971-105 971-107 971-110 971-111 971-112 971-113 971-114 971-120 971-130 G D Description: Error log analysis indicates a failure. Description: An adapter or bus I/O error occurred. D D Description: A device timeout error occurred. Description: Sense data from the SCSI device shows an error. D D D D D D D D D D D D D Description: Timeout while attempting to communicate with SCSI device.

Service Request Number 971-135 971-140 971-150 971-160 971-161 971-163 971-164 971-165 SRN Src. Description: Timeout while attempting to communicate with the SCSI device. 971-166 D Description: Unable to configure the device.) Description: The Unload command failed. Description: An error is diagnosed from the error log analysis. “MAP 0210: General Problem Resolution” on page 67. D D D D D D D D Failing Function Codes 971 media 971 971 media 971 media 971 B88 971 B88 971 B88 971 B88 276 971 B88 software 971 B88 B88 software 971 media 971 B88 media 971 media 971 media 971 971 media 971 B88 971 B88 971 B88 971 Description and Action (Unless otherwise indicated. Chapter 33. 971-167 971-168 971-169 971-170 D D D D Description: An unexpected SCSI error occurred. Description: The adapter failed to configure. Description: The Send Diagnostic command failed. Read and Compare Test failed. Description: The Test Unit Ready command failed. Description: The Mode Select command failed. Description: The device open test failed. Description: Invalid condition from the drive after a request sense. Write and Compare test failed. Description: The Mode Select command failed. Description: The device configuration failed. Description: The Unload command failed. Description: The Send Diagnostic command failed. 971-180 971-185 971-190 971-200 971-201 971-210 971-211 971-220 D D D D G D D D Description: The Load command failed. SRNs 900-001 through xxxxxxx 493 . Description: Invalid condition from the drive after a reserve. Description: The Read. use Chapter 11. Description: The Release command failed. Description: Write. Description: The Test Unit Ready command failed.

D Description: The drive returned bad or non-extended sense data. Description: SCSI adapter configuration failed. Description: An error is detected in request sense data. use Chapter 11. Description: The SCSI device indicates a check condition.Service Request Number 971-230 971-240 971-260 971-261 971-300 971-310 SRN Src. Description: The device configuration failed. Description: The SCSI device indicates busy. Description: The Inquiry command failed. Description: The device open test failed.) Description: The Request Sense command failed. Description: The write-protect sensor test failed. Description: The SCSI device indicates a reservation conflict. Description: A reservation conflict occurred. 971-320 971-411 to 971-423 971-511 to 971-523 971-611 to 971-623 971-711 to 971-723 972-101 972-102 972-103 972-104 972-105 972-107 972-110 972-111 972-112 972-113 972-114 972-120 G D Description: Error log analysis indicates a failure. Description: Invalid condition from the drive after a request sense. Description: Timeout while attempting to communicate with the SCSI device. D D Description: A device timeout error occurred. Description: The Openx command failed. D D D D D D D D D D D D Description: Timeout while attempting to communicate with SCSI device. Description: The drive has returned unexpected sense data. Description: The Reserve command failed. Description: Invalid condition from the drive after a reserve. 494 Diagnostic Information for Multiple Bus Systems . Description: An adapter or bus I/O error occurred. “MAP 0210: General Problem Resolution” on page 67. Description: The device configuration failed. D D D D D D Failing Function Codes 971 971 971 971 971 software B88 971 software 971 media 971 B88 software 971 B88 971 software 971 B88 software 972 972 972 972 972 972 972 972 972 972 972 972 Description and Action (Unless otherwise indicated.

Description: Invalid condition from the drive after a request sense. Description: The Test Unit Ready command failed. 972-167 972-168 972-169 972-170 D D D D Description: An unexpected SCSI error occurred. Description: The Mode Select command failed. Chapter 33. Description: Timeout while attempting communication with SCSI device. Description: The device configuration failed. Description: The Unload command failed. Description: An error is diagnosed from the error log analysis.) Description: The Load command failed. Description: The Mode Select command failed. D D D D D D D D Failing Function Codes 972 media 972 media 972 972 media 972 media 972 B88 972 B88 972 B88 276 972 B88 276 972 B88 software 972 B88 B88 software 972 media 972 B88 media 972 media 972 media 972 972 media 972 B88 972 B88 Description and Action (Unless otherwise indicated. “MAP 0210: General Problem Resolution” on page 67. Description: The Unload command failed.Service Request Number 972-130 972-135 972-140 972-150 972-160 972-161 972-163 972-164 SRN Src. Description: The Read. Read and Compare Test failed. SRNs 900-001 through xxxxxxx 495 . use Chapter 11. 972-165 D 972-166 D Description: Unable to configure the device. Description: The Test Unit Ready command failed. Description: The Send Diagnostic command failed. Description: The Send Diagnostic command failed. 972-180 972-185 972-190 972-200 972-201 972-210 D D D D G D Description: The Load command failed. Write and Compare test failed. Description: Invalid condition from the drive after a reserve. Description: The adapter failed to configure. Description: Write.

Description: The Load command failed. Description: The Request Sense command failed. Description: The device open test failed. Description: An adapter or bus I/O error occurred. Description: The Unload command failed. D D D D D D D D Failing Function Codes 972 B88 972 972 972 972 972 972 software B88 972 software 972 media 972 B88 software 972 B88 972 B88 software 972 B88 software 973 973 973 media 973 media 973 973 media 973 media 973 media 973 B88 media Description and Action (Unless otherwise indicated. Write and Compare test failed. use Chapter 11. “MAP 0210: General Problem Resolution” on page 67. Description: The Send Diagnostic command failed. 972-320 972-411 to 972-423 972-511 to 972-523 972-611 to 972-623 972-711 to 972-723 973-110 973-120 973-130 973-135 973-140 973-150 973-160 973-169 973-170 G D Description: Error log analysis indicates a failure. Description: The Send Diagnostic command failed. Description: The Mode Select command failed. D D D D D D D D D Description: The Reserve command failed. Description: The device configuration failed. Description: SCSI adapter configuration failed. Description: The device configuration test failed. D D Description: The drive returned bad or non-extended sense data.Service Request Number 972-211 972-220 972-230 972-240 972-260 972-261 972-300 972-310 SRN Src. Description: The Inquiry command failed. 496 Diagnostic Information for Multiple Bus Systems . Description: The Openx command failed. Description: The Test Unit Ready command failed. Description: The Release command failed. Description: A reservation conflict occurred. Description: The Read.) Description: The device open test failed. D Description: A device timeout error occurred.

Description: The CD-ROM drive indicates an error. “MAP 0210: General Problem Resolution” on page 67.) Description: The Load command failed. Description: The Release command failed. Description: SCSI adapter configuration failed. Description: Unable to open the device driver. SRNs 900-001 through xxxxxxx 497 . Chapter 33. Description: The CD-ROM drive indicates an error. D D D D D D D D D D Failing Function Codes 973 media 973 media 973 973 media 973 B88 973 973 973 973 software B88 973 software 973 media 973 B88 software 973 B88 973 B88 software 973 B88 software 974 B88 974 B88 974 B88 974 974 974 974 B88 Description and Action (Unless otherwise indicated. Description: The CD-ROM drive indicates an error.Service Request Number 973-180 973-185 973-190 973-200 973-210 973-220 973-230 973-240 973-300 973-310 SRN Src. D D D D D D D Description: Unable to reserve device. Description: The CD-ROM drive indicates an error. Description: The Request Sense command failed. Description: Unable to do configuration. Description: An adapter or bus I/O error occurred. Description: The device configuration failed. Description: The Test Unit Ready command failed. 973-320 973-411 to 973-423 973-511 to 973-523 973-611 to 973-623 973-711 to 973-723 974-111 974-112 974-113 974-121 974-122 974-123 974-125 G D Description: Error log analysis indicates a failure. D D Description: A device timeout error occurred. use Chapter 11. Description: The Openx command failed. D Description: The drive returned bad or non-extended sense data. Description: A reservation conflict occurred. Description: The Unload command failed. Description: The Mode Select command failed. Description: The device configuration failed.

Description: The CD-ROM drive indicates an error. Description: A protocol error. Description: The drive did not become ready. Description: The LED test failed. 981-117 981-118 D D 981 981 B88 Description: A write-protect error occurred. call your support person. use Chapter 11. Description: The media format is corrupted. Action: Check the levels of the device. Description: An unrecoverable media error. If you do not find a problem. Description: The CD-ROM drive indicates an error. Description: Errors found during ELA. adapter. Description: A media error was detected. Description: Unable to open device driver. 498 Diagnostic Information for Multiple Bus Systems . Description: The motor failed to restart. Description: No tone during audio test. Description: A SCSI command time-out. Description: The CD-ROM drive indicates an error. “MAP 0210: General Problem Resolution” on page 67.Service Request Number 974-126 974-127 974-128 974-129 974-150 SRN Src. Description: Unable to reserve device. Description: Undefined error detected. Description: Errors log analysis indicates hardware failure. 974-151 974-152 974-162 974-171 974-172 974-173 974-175 974-198 974-199 974-211 974-281 974-301 974-302 981-102 981-104 981-105 981-106 981-108 981-110 981-112 981-114 981-116 D D D D D D D D D D D G G D D D D D D D D D Description: A command timeout was detected. and application software to be sure they are all compatible. Description: Undefined error detected. Description: A command reservation conflict was detected.) Description: The CD-ROM drive indicates an error. Description: Unable to do configuration. Description: The bus test failed. Description: An unrecoverable hardware error. Description: The CD-ROM drive indicates an error. D D D D D Failing Function Codes 974 974 974 974 TestDisc 974 974 D88 974 974 974 974 974 974 974 B88 974 974 974 974 974 B88 981 981 981 981 981 981 981 981 Description and Action (Unless otherwise indicated. diagnostic software. Description: The diagnostic test failed. Description: The CD-ROM drive indicates an error. Description: The electronics card test failed.

Description: A software error was caused by a hardware failure. Description: A SCSI check condition error. Description: An unrecoverable media error. 981-130 981-132 981-134 981-136 981-137 G D D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: A SCSI busy or command error. Description: Error log analysis indicates a SCSI bus problem. Description: An unrecoverable hardware error. diagnostic software.Service Request Number 981-120 981-122 981-124 981-126 981-128 981-129 SRN Src. Description: The motor failed to restart. call your support person. and application software to be sure they are all compatible. Description: The bus test failed. Description: The drive did not become ready. Description: A SCSI reservation conflict error. Description: A SCSI reservation conflict error. Action: Check the levels of the device. Chapter 33. Description: A SCSI check condition error. use Chapter 11. SRNs 900-001 through xxxxxxx 499 . Description: The adapter failed to configure. adapter. Description: The electronics card test failed. 984-102 984-104 984-105 984-106 984-108 984-110 984-112 984-114 984-116 D D D D D D D D D 984-117 984-118 984-120 984-122 984-124 984-126 D D D D D D 984 984 B88 984 984 984 984 B88 Description: A write-protect error occurred. Description: The media format is corrupted. Description: The error log analysis indicates a hardware failure.) Description: A SCSI busy or command error. “MAP 0210: General Problem Resolution” on page 67. Description: A protocol error. D D D D G G Failing Function Codes 981 981 981 981 B88 981 190 981 B88 software 981 981 B88 software 981 981 B88 190 984 984 984 984 984 984 984 984 Description and Action (Unless otherwise indicated. Description: A SCSI command time-out. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The certify operation failed. Description: The diagnostic test failed. If you do not find a problem. Description: A software error was caused by a hardware failure. Description: A disk drive hardware error occurred.

Description: The error log analysis indicates a hardware failure. Description: The motor failed to restart. 500 Diagnostic Information for Multiple Bus Systems . Description: A SCSI reservation conflict error. use Chapter 11. Description: Error log analysis indicates a SCSI bus problem. call your support person. Description: The media format is corrupted.) Description: The error log analysis indicates a hardware failure. “MAP 0210: General Problem Resolution” on page 67. 984-130 984-132 984-134 984-137 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: A software error was caused by a hardware failure. Description: The bus test failed. G G Failing Function Codes 984 190 984 B88 software 984 984 B88 software 984 B88 190 986 986 986 986 986 986 986 986 Description and Action (Unless otherwise indicated. Description: An unrecoverable hardware error. Description: A disk drive hardware error occurred. Description: A SCSI busy or command error. Description: The adapter failed to configure. Description: The drive did not become ready. 986-102 986-104 986-105 986-106 986-108 986-110 986-112 986-114 986-116 D D D D D D D D D 986-117 986-118 986-120 986-122 986-124 986-126 986-128 986-129 D D D D D D G G 986 986 B88 986 986 986 986 B88 986 190 986 B88 software Description: A write-protect error occurred. Action: Check the levels of the device. diagnostic software. and application software to be sure they are all compatible. Description: An unrecoverable media error.Service Request Number 984-128 984-129 SRN Src. Description: Error log analysis indicates a SCSI bus problem. Description: The diagnostic test failed. Description: A SCSI command time-out. adapter. Description: The electronics card test failed. Description: A protocol error. If you do not find a problem. Description: A SCSI check condition error.

Service Request Number 986-130 986-132 986-134 986-136 986-137 SRN Src. use Chapter 11. Description: The CD-ROM drive indicates an error. Description: The certify operation failed. Description: The CD-ROM drive indicates an error.) Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: The CD-ROM drive indicates an error. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: Unable to do configuration. Description: Undefined error detected. SRNs 900-001 through xxxxxxx 501 . Description: The CD-ROM drive indicates an error. Description: Unable to open the device driver. Description: The CD-ROM drive indicates an error. Description: The adapter failed to configure. Description: A media error was detected. Description: Undefined error detected. “MAP 0210: General Problem Resolution” on page 67. Description: A command reservation conflict was detected. Description: Unable to reserve device. Description: The CD-ROM drive indicates an error. Description: A disk drive hardware error occurred. Description: Unable to do configuration. Description: Unable to reserve device. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error. G D D D D Failing Function Codes 986 986 B88 software 986 C11 986 B88 190 987 B88 987 B88 987 B88 987 987 987 987 B88 987 987 987 987 TestDisc 987 987 B88 987 987 987 987 987 987 987 B88 987 Description and Action (Unless otherwise indicated. Description: The CD-ROM drive indicates an error. Description: The CD-ROM drive indicates an error. Chapter 33. Description: Unable to open device driver. 987-111 987-112 987-113 987-121 987-122 987-123 987-125 987-126 987-127 987-128 987-129 987-150 D D D D D D D D D D D D 987-151 987-152 987-162 987-171 987-172 987-173 987-175 987-198 987-199 D D D D D D D D D Description: A command timeout was detected.

Description: The device failed to configure. 502 Diagnostic Information for Multiple Bus Systems . Description: The media format is corrupted. Description: A SCSI busy or command error. use Chapter 11. Description: The adapter failed to configure. Description: The error log analysis indicates a hardware failure. Description: The bus test failed. 989-117 989-118 989-120 989-122 989-124 989-126 989-128 989-129 D D D D D D G G 989 989 B88 989 989 989 989 B88 989 190 989 B88 software 989 989 B88 software 989 B88 software 989 Description: A write-protect error occurred.Service Request Number 987-211 987-281 987-301 987-302 989-102 989-104 989-105 989-106 989-108 989-110 989-112 989-114 989-116 SRN Src. D D G G D D D D D D D D D Failing Function Codes 987 987 987 987 B88 989 989 989 989 989 989 989 989 Description and Action (Unless otherwise indicated. diagnostic software. Description: A protocol error. Description: Error log analysis indicates a SCSI bus problem. “MAP 0210: General Problem Resolution” on page 67. Description: A SCSI reservation conflict error. 989-130 989-132 989-134 989-135 G D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. 989-136 D Description: The certify operation failed. call your support person. Description: A software error was caused by a hardware failure. and application software to be sure they are all compatible. If you do not find a problem. adapter. Description: A SCSI check condition error. Description: A non-recoverable hardware error. Description: Errors found during ELA. Description: The drive did not become ready. Action: Check the levels of the device. Description: A SCSI command time-out. Description: An unrecoverable media error Description: The motor failed to restart. Description: Errors found during ELA. Description: The diagnostic test failed. Description: A disk drive hardware error occurred. Description: No tone during audio test. Description: The electronics card test failed.) Description: The LED test failed.

and application software to be sure they are all compatible. Description: The adapter failed to configure. Description: A SCSI reservation conflict error. Description: The motor failed to restart. D Failing Function Codes 989 B88 190 990 990 990 990 990 990 990 990 Description and Action (Unless otherwise indicated. Description: The certify operation failed. Description: The diagnostic test failed. Description: A disk drive hardware error occurred. Description: A protocol error. Description: A SCSI busy or command error. Description: The media format is corrupted. use Chapter 11. Description: Error log analysis indicates a SCSI bus problem. diagnostic software. If you do not find a problem. Description: Timeout while attempting to communicate with SCSI device. SRNs 900-001 through xxxxxxx 991-101 991-102 D D 503 . Description: An unrecoverable hardware error. Description: A SCSI command time-out. “MAP 0210: General Problem Resolution” on page 67. Description: The SCSI device indicates busy. Description: A SCSI check condition error. call your support person. Description: The electronics card test failed. Chapter 33. adapter. Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The error log analysis indicates a hardware failure. Description: The drive did not become ready. Action: Check the levels of the device.) Description: Unit attention condition has occurred on the Send Diagnostic command. Description: The bus test failed.Service Request Number 989-137 SRN Src. Description: An unrecoverable media error. 990-102 990-104 990-105 990-106 990-108 990-110 990-112 990-114 990-116 D D D D D D D D D 990-117 990-118 990-120 990-122 990-124 990-126 990-128 990-129 D D D D D D G G 990 990 B88 990 990 990 990 B88 990 190 990 B88 software 990 990 B88 software 990 990 B88 190 991 991 Description: A write-protect error occurred. 990-130 990-132 990-134 990-136 990-137 G D D D D Description: Error log analysis indicates a problem reported by the disk drive’s self-monitoring function. Description: A software error was caused by a hardware failure.

Description: Write. Read and Compare Test failed.Service Request Number 991-103 991-104 991-105 991-107 991-110 991-111 991-112 991-113 991-114 991-120 991-130 991-135 991-140 991-150 991-160 991-161 991-163 991-164 991-165 SRN Src.) Description: The SCSI device is indicating a reservation conflict. Description: Timeout while attempting to communicate with the SCSI device. Description: The SCSI drive returned unexpected sense data. Description: The write-protect sensor test failed. Description: The Load command failed. Description: Timeout while attempting to communicate with the SCSI device. Description: The Unload command failed. Description: The SCSI device indicates a check condition. Description: The Mode Select command failed. “MAP 0210: General Problem Resolution” on page 67. Description: Invalid condition from the drive after a request sense. use Chapter 11. Description: The Send Diagnostic command failed. 991-167 991-168 D D Description: An unexpected SCSI error occurred. 504 Diagnostic Information for Multiple Bus Systems . 991-166 D Description: The device failed to configure. Description: Invalid condition from the drive after a request sense. Description: The adapter failed to configure. Description: Invalid condition from the drive after a reserve. Description: The Inquiry command failed. Description: The Test Unit Ready command failed. Description: The Reserve command failed. D D D D D D D D D D D D D D D D D D D Failing Function Codes 991 991 991 991 991 991 991 991 991 991 991 media 991 media 991 991 media 991 media 991 B88 991 B88 991 B88 991 B88 276 991 B88 software 991 B88 B88 software Description and Action (Unless otherwise indicated. Description: Invalid condition from the drive after a reserve. Description: Sense data from the SCSI device shows an error.

Write and Compare test failed. Description: An adapter or bus I/O error occurred. D Description: The drive returned bad or non-extended sense data. Description: The Release command failed. Description: The Request Sense command failed. Description: The Mode Select command failed. Description: The Openx command failed.Service Request Number 991-169 991-170 SRN Src. Description: The Test Unit Ready command failed. Description: A reservation conflict occurred. Description: The Unload command failed. Description: An error is diagnosed from the error log analysis. Description: SCSI adapter configuration failed. Description: The device configuration failed. D D Description: A device timeout error occurred. Description: The device configuration failed. “MAP 0210: General Problem Resolution” on page 67. 991-320 991-411 to 991-423 991-511 to 991-523 991-611 to 991-623 991-711 to 991-723 G D Description: Error log analysis indicates a failure. SRNs 900-001 through xxxxxxx 505 . Chapter 33.) Description: The Send Diagnostic command failed. use Chapter 11. Description: The device configuration failed. Description: The Read. Description: The device open test failed. D D Failing Function Codes 991 media 991 B88 media 991 media 991 media 991 991 media 991 B88 991 B88 991 B88 991 991 991 991 991 991 software B88 991 software 991 media 991 B88 software 991 B88 991 B88 software 991 B88 software Description and Action (Unless otherwise indicated. 991-180 991-185 991-190 991-200 991-201 991-210 991-211 991-220 991-230 991-240 991-260 991-261 991-300 991-310 D D D D G D D D D D D D D D Description: The Load command failed. Description: The device open test failed.

Description: The Openx command failed. Write and Compare test failed. Description: The Mode Select command failed. Description: The Mode Select command failed. D D D D D D D D D Failing Function Codes 994 994 994 media 994 media 994 994 media 994 media 994 media 994 B88 media 994 media 994 media 994 994 media 994 B88 994 994 994 994 software B88 994 software 994 media 994 B88 software 994 B88 Description and Action (Unless otherwise indicated. Description: The Request Sense command failed. Description: The Test Unit Ready command failed. 994-180 994-185 994-190 994-200 994-210 994-220 994-230 994-240 994-300 994-310 D D D D D D D D D D Description: The Load command failed. Description: The Unload command failed. 994-320 994-411 to 994-423 994-511 to 994-523 G D Description: Error log analysis indicates a failure. use Chapter 11. D Description: The drive returned bad or non-extended sense data. Description: The device configuration failed. 506 Diagnostic Information for Multiple Bus Systems . Description: The Test Unit Ready command failed.) Description: The Reserve command failed. “MAP 0210: General Problem Resolution” on page 67. Description: The Read. Description: The Unload command failed.Service Request Number 994-110 994-120 994-130 994-135 994-140 994-150 994-160 994-169 994-170 SRN Src. Description: The Send Diagnostic command failed. Description: A reservation conflict occurred. Description: The Send Diagnostic command failed. Description: The Release command failed. Description: The Load command failed. Description: The Inquiry command failed. Description: SCSI adapter configuration failed. Description: The device configuration failed.

Description: The device configuration failed. D Failing Function Codes 994 B88 software 994 B88 software 995 995 995 media 995 media 995 995 media 995 media 995 media 995 B88 media 995 media 995 media 995 995 media 995 B88 995 995 995 995 software B88 995 software 995 media Description and Action (Unless otherwise indicated. Description: The Request Sense command failed. Description: The device configuration failed. Description: The Openx command failed. 995-320 G Description: Error log analysis indicates a failure. Description: The Read. Description: The Load command failed. Description: The Test Unit Ready command failed. Description: The Inquiry command failed. Description: The Unload command failed. Description: The Test Unit Ready command failed. Description: The Unload command failed.) Description: An adapter or bus I/O error occurred. use Chapter 11. Description: The Send Diagnostic command failed. Chapter 33. Description: The Release command failed. Description: The Mode Select command failed. 995-180 995-185 995-190 995-200 995-210 995-220 995-230 995-240 995-300 995-310 D D D D D D D D D D Description: The Load command failed. D D D D D D D D D Description: The Reserve command failed. “MAP 0210: General Problem Resolution” on page 67.Service Request Number 994-611 to 994-623 994-711 to 994-723 995-110 995-120 995-130 995-135 995-140 995-150 995-160 995-169 995-170 SRN Src. Description: SCSI adapter configuration failed. SRNs 900-001 through xxxxxxx 507 . Description: The Send Diagnostic command failed. Write and Compare test failed. Description: The Mode Select command failed. D Description: A device timeout error occurred.

Description: The Send Diagnostic command failed. Description: The Load command failed. Description: The Release command failed. Description: The Read. “MAP 0210: General Problem Resolution” on page 67. Description: The Test Unit Ready command failed. Description: The device configuration failed. Description: The Unload command failed. 508 Diagnostic Information for Multiple Bus Systems . Write and Compare test failed. Description: An adapter or bus I/O error occurred. Description: The Openx command failed.) Description: A reservation conflict occurred. Description: The Mode Select command failed. 998-180 998-185 998-190 998-200 998-210 998-220 998-230 998-240 998-300 D D D D D D D D D Description: The Load command failed. Description: The Test Unit Ready command failed. D D Description: A device timeout error occurred. Description: The Mode Select command failed. D Failing Function Codes 995 B88 software 995 B88 995 B88 software 995 B88 software 998 998 998 media 998 media 998 998 media 998 media 998 media 998 B88 media 998 media 998 media 998 998 media 998 B88 998 998 995 995 software Description and Action (Unless otherwise indicated. Description: The Request Sense command failed. Description: The device configuration failed. Description: The Unload command failed.Service Request Number 995-411 to 995-423 995-511 to 995-523 995-611 to 995-623 995-711 to 995-723 998-110 998-120 998-130 998-135 998-140 998-150 998-160 998-169 998-170 SRN Src. use Chapter 11. Description: The Inquiry command failed. D Description: The drive returned bad or non-extended sense data. Description: The Send Diagnostic command failed. D D D D D D D D D Description: The Reserve command failed.

Description: You have a six-digit error code (like an SRN) containing no dash (-) between the third and fourth digits. xxxxxx G xxxxxxxx G none Chapter 33.) Description: SCSI adapter configuration failed. SRNs 900-001 through xxxxxxx 509 . Action: Use the ″Error Code to FRU Index″ in the service guide. D Description: The drive returned bad or non-extended sense data. Description: An adapter or bus I/O error occurred. or Time-out error. Description: Refer to the Error Code to FRU Index in the system unit’s service guide. D Description: A 7137 or 3514 disk array subsystem problem is indicated. Note: xx represents the last 2 digits of the SRN. G 9CC-xxx G xxx 2C9 none Description: I/O Bus Data. Action: Use 7137 or 3514 documentation. Address Parity Error. Action: Refer to the Bus SRN to FRU Reference Table in the system unit’s service guide. D D Description: A device timeout error occurred. 998-320 998-411 to 998-423 998-511 to 998-523 998-611 to 998-623 998-711 to 998-723 999-xxx series 9CC-1xx G D Description: Error log analysis indicates a failure. D Failing Function Codes B88 995 software 995 media 998 B88 software 998 B88 998 B88 software 998 B88 software 999 Description and Action (Unless otherwise indicated. Note: xxx represents the last 3 digits of the SRN. Description: A reservation conflict occurred. Action: Use the ″Error Code to FRU Index″ in the service guide. use Chapter 11. “MAP 0210: General Problem Resolution” on page 67. Description: I/O Error on PCI bus.Service Request Number 998-310 SRN Src.

510 Diagnostic Information for Multiple Bus Systems .

“MAP 0230: Platform Error Problem Resolution” on page 83. Action: Use Chapter 13. “MAP 0230: Platform Error Problem Resolution” on page 83. Action: Use Chapter 13. Description: System bus time-out error. For more detailed information refer to Chapter 13. “MAP 0230: Platform Error Problem Resolution” on page 83. Description: External cache parity or multi-bit ECC error. Service Request Number A00-FF0 SRN Src. “MAP 0230: Platform Error Problem Resolution” on page 83. Description: CPU internal error. Description: System bus protocol/transfer error.Chapter 34. “MAP 0230: Platform Error Problem Resolution” on page 83. Description: External cache ECC single-bit error. “MAP 0230: Platform Error Problem Resolution” on page 83. Action: Use Chapter 13. Description: System bus parity error. Action: Use Chapter 13. but the failure could not be isolated. Description: CPU internal cache or cache controller error. Action: Use Chapter 13. “MAP 0230: Platform Error Problem Resolution” on page 83. Action: Use Chapter 13. G Description and Action Description: Error log analysis is unable to determine the error. Description: Time-out error waiting for I/O. A01-00x G A01-01x A01-02x G G A01-03x G A01-04x G A01-05x A01-06x A01-07x A01-08x G G G G 511 . “MAP 0